Related
Hey!
Im pretty new into this subject about rooting and install custom Roms to your phone on android but i was thinking i should give it a try!
I have succesfully unlocked the bootloader but i dont know what i shall do next. I want to install this rom: http://forum.xda-developers.com/sony-xperia-z1-compact/development/xperia-z1c-resurrection-remix-lollipop-t2996231[/url]
What shall i do first? Ive tried reading a couple of guys but i dont really know what i shall do next, as far as i know you should unlock the bootloader (already done) and then root the phone (i've read this guide and it seems quite good: http://techchomps.com/root-14-4-a-0-157-android-4-4-4-kitkat-on-xperia-z1-z1-compact-and-z-ultra/) and then i can install a custom rom? Shouldn't you install a custom recovery like clockworkmod first? When and how do i install that?
Im currently at firmware 14.4.a.0.157 btw.
I have understood that you might brick you device if you do this and that's the last thing i want too do, as im studying student i dont really have enough money for a new phone/reparation.
I hope i dont seem to confusing to you
Thanks in advance!
http://forum.xda-developers.com/showthread.php?t=2631291
this is all you need, read it carefully
p.s. i hope you backuped your DRM-keys before you unlocked your bootloader, otherwise they went away and never come back...
Tars741 said:
Hey!
Im pretty new into this subject about rooting and install custom Roms to your phone on android but i was thinking i should give it a try!
I have succesfully unlocked the bootloader but i dont know what i shall do next. I want to install this rom: http://forum.xda-developers.com/sony-xperia-z1-compact/development/xperia-z1c-resurrection-remix-lollipop-t2996231[/url]
What shall i do first? Ive tried reading a couple of guys but i dont really know what i shall do next, as far as i know you should unlock the bootloader (already done) and then root the phone (i've read this guide and it seems quite good: http://techchomps.com/root-14-4-a-0-157-android-4-4-4-kitkat-on-xperia-z1-z1-compact-and-z-ultra/) and then i can install a custom rom? Shouldn't you install a custom recovery like clockworkmod first? When and how do i install that?
Im currently at firmware 14.4.a.0.157 btw.
I have understood that you might brick you device if you do this and that's the last thing i want too do, as im studying student i dont really have enough money for a new phone/reparation.
I hope i dont seem to confusing to you
Thanks in advance!
Click to expand...
Click to collapse
LOL beaten to it
There is a sticky thread dedicated to your needs Z1 Compact Resource Thread -|-Rooting-BL Unlocking-Firmware & More...
Don't use guides from any other place as they sometimes leave out important information.
If you read (and read again) the guides, go slowly, then there is no chance you will damage your phone.
I hope you made a backup of your TA partition.
Didgesteve said:
There is a sticky thread dedicated to your needs Z1 Compact Resource Thread -|-Rooting-BL Unlocking-Firmware & More...
Don't use guides from any other place as they sometimes leave out important information.
If you read (and read again) the guides, go slowly, then there is no chance you will damage your phone.
I hope you made a backup of your TA partition.
Click to expand...
Click to collapse
And what´s the difference to my post one above?
Just joking, everything is good.
moonryder said:
And what´s the difference to my post one above?
Just joking, everything is good.
Click to expand...
Click to collapse
Didgesteve said:
LOL beaten to it
There is a sticky thread dedicated to your needs Z1 Compact Resource Thread -|-Rooting-BL Unlocking-Firmware & More...
Don't use guides from any other place as they sometimes leave out important information.
If you read (and read again) the guides, go slowly, then there is no chance you will damage your phone.
I hope you made a backup of your TA partition.
Click to expand...
Click to collapse
Hey!
Yeah i saw that thread and as i read, he seemed to link this guide for the root: http://forum.xda-developers.com/xperia-z1/general/root-14-4-0-157-lb-ubl-t2933298
The thing i find strange is that is says D690X devices but my Z1C is D5503 will that still work if they are on the same firmware at the moment? One guy said so in the thread but i just wanted to ask you guys about it.
Tars741 said:
Hey!
Yeah i saw that thread and as i read, he seemed to link this guide for the root: http://forum.xda-developers.com/xperia-z1/general/root-14-4-0-157-lb-ubl-t2933298
The thing i find strange is that is says D690X devices but my Z1C is D5503 will that still work if they are on the same firmware at the moment? One guy said so in the thread but i just wanted to ask you guys about it.
Click to expand...
Click to collapse
NOOOOO, don´t flash this ones or you will brick your phone.
Download the files for D5503 - in the post you mentiondes is only explained how to do it!
Here are the right files for D5503: CLICK
moonryder said:
NOOOOO, don´t flash this ones or you will brick your phone.
Download the files for D5503 - in the post you mentiondes is only explained how to do it!
Here are the right files for D5503: CLICK
Click to expand...
Click to collapse
Thanks alot!
Ive successfully rooted the phone and everything seems to work fine with that!
The thing is that i was going to install recovery now and i thought i could use the guide provided by the author of the thread you linked before which is this: http://forum.xda-developers.com/showthread.php?t=2261606
As i downloaded the recovery and installed it said it was succesfull but i cant seem to get into recovery. The guide also said that the device should reboot after the installtion, which it didnt! I ran install.bat with the phone on, not in flashmode or anything. Was i doing anything wrong? I installed the recovery from http://nut.xperia-files.com/ in the XZDualRecovery section, not the kernal section. Should i also install the kernal Recovery? Im confused
Tars741 said:
Thanks alot!
Ive successfully rooted the phone and everything seems to work fine with that!
The thing is that i was going to install recovery now and i thought i could use the guide provided by the author of the thread you linked before which is this: http://forum.xda-developers.com/showthread.php?t=2261606
As i downloaded the recovery and installed it said it was succesfull but i cant seem to get into recovery. The guide also said that the device should reboot after the installtion, which it didnt! I ran install.bat with the phone on, not in flashmode or anything. Was i doing anything wrong? I installed the recovery from http://nut.xperia-files.com/ in the XZDualRecovery section, not the kernal section. Should i also install the kernal Recovery? Im confused
Click to expand...
Click to collapse
shutdown your device!
At boot, once you feel the phone vibrate and while you see the green led burn:
- press VOL-UP for PhilZ Touch;
- press VOL-DOWN for TWRP.
- flash the custom rom you want (but copy the zip to your extSD card before)
moonryder said:
shutdown your device!
At boot, once you feel the phone vibrate and while you see the green led burn:
- press VOL-UP for PhilZ Touch;
- press VOL-DOWN for TWRP.
- flash the custom rom you want (but copy the zip to your extSD card before)
Click to expand...
Click to collapse
Ive tried that but i dont get into recovery. Do i need to have a extSD card before install the recovery? I also dont see any green led burning. I feel the phone vibrate shortly after i pressed and hold the power button, but no green led.
When i installed the recovery i had the phone powered on, was that right? It said in the guide it would restart but it didn't.
I dont think ext card is necessary, it is rather option.
Question:
Did you install both zips - installer and flashable?
If yes - I'd try other version.
I rooted my phone a little while ago but didn't do anything with it. Am I able to use a custom rom on it now? Are there any recommended apps to get on it now that it's rooted?
Repromise said:
I rooted my phone a little while ago but didn't do anything with it. Am I able to use a custom rom on it now? Are there any recommended apps to get on it now that it's rooted?
Click to expand...
Click to collapse
For starters, open up a terminal and run:
Code:
su
reboot nvbackup
This will write your IMEI and carrier identification stuff stored in nvram to backup partitions. Your phone has built in backup partitions for this data and it will try to restore from them under certain circumstances (usually a flash gone wrong), but by default the backups are blank . Your phone will reboot, you'll see a couple of real quick flashes of little blue text, then it will boot up again normally.
Some other good terminal commands to note the output of would be:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
That will tell you what bootloader and modem your phone is running on. You need to know this if you plan on doing any custom rom flashing. As a general rule don't ever attempt to downgrade bootloaders on this phone; the older ones can actually be downgraded but the newer ones will hard brick if you try it. Research, research, research before you do anything, and don't be afraid to ask questions. XDA forums are a great source of information, but beware of old information. Knox and the secure bootloaders changed how we have to treat this phone around Fall 2013, so following old forum posts or old articles on lifehacker or somewhere like that can be dangerous. Mostly custom rom zips won't touch your bootloader or modem. Its Odin you have to be most careful with, as those packages tend to be full firmware updates.
You're not ready to flash custom roms just yet unless you already flashed a custom recovery too like twrp or philz. You can use an Play store app called flashify to flash a custom recovery too since you're already rooted.
Flashify and Titanium Backup (pro version is very worth the money) are the only root apps I have on my S3.
jason2678 said:
For starters, open up a terminal and run:
Code:
su
reboot nvbackup
This will write your IMEI and carrier identification stuff stored in nvram to backup partitions. Your phone has built in backup partitions for this data and it will try to restore from them under certain circumstances (usually a flash gone wrong), but by default the backups are blank . Your phone will reboot, you'll see a couple of real quick flashes of little blue text, then it will boot up again normally.
Some other good terminal commands to note the output of would be:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
That will tell you what bootloader and modem your phone is running on. You need to know this if you plan on doing any custom rom flashing. As a general rule don't ever attempt to downgrade bootloaders on this phone; the older ones can actually be downgraded but the newer ones will hard brick if you try it. Research, research, research before you do anything, and don't be afraid to ask questions. XDA forums are a great source of information, but beware of old information. Knox and the secure bootloaders changed how we have to treat this phone around Fall 2013, so following old forum posts or old articles on lifehacker or somewhere like that can be dangerous. Mostly custom rom zips won't touch your bootloader or modem. Its Odin you have to be most careful with, as those packages tend to be full firmware updates.
You're not ready to flash custom roms just yet unless you already flashed a custom recovery too like twrp or philz. You can use an Play store app called flashify to flash a custom recovery too since you're already rooted.
Flashify and Titanium Backup (pro version is very worth the money) are the only root apps I have on my S3.
Click to expand...
Click to collapse
++ 1
"all i can really do , is stay out of my own way and let the will of heaven be done"
jason2678 said:
For starters, open up a terminal and run:
Code:
su
reboot nvbackup
This will write your IMEI and carrier identification stuff stored in nvram to backup partitions. Your phone has built in backup partitions for this data and it will try to restore from them under certain circumstances (usually a flash gone wrong), but by default the backups are blank . Your phone will reboot, you'll see a couple of real quick flashes of little blue text, then it will boot up again normally.
Some other good terminal commands to note the output of would be:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
That will tell you what bootloader and modem your phone is running on. You need to know this if you plan on doing any custom rom flashing. As a general rule don't ever attempt to downgrade bootloaders on this phone; the older ones can actually be downgraded but the newer ones will hard brick if you try it. Research, research, research before you do anything, and don't be afraid to ask questions. XDA forums are a great source of information, but beware of old information. Knox and the secure bootloaders changed how we have to treat this phone around Fall 2013, so following old forum posts or old articles on lifehacker or somewhere like that can be dangerous. Mostly custom rom zips won't touch your bootloader or modem. Its Odin you have to be most careful with, as those packages tend to be full firmware updates.
You're not ready to flash custom roms just yet unless you already flashed a custom recovery too like . You can use an Play store app called flashify to flash a custom recovery too since you're already rooted.
Flashify and Titanium Backup (pro version is very worth the money) are the only root apps I have on my S3.
Click to expand...
Click to collapse
How do I open a terminal? I feel silly asking that. I downloaded an app that says what bootloader version I have
Repromise said:
How do I open a terminal? I feel silly asking that. I downloaded an app that says what bootloader version I have
Click to expand...
Click to collapse
You can use adb shell if you have adb set up. Otherwise install a terminal emulator from the play store. Jack palevich's is a good one.
jason2678 said:
For starters, open up a terminal and run:
Code:
su
reboot nvbackup
This will write your IMEI and carrier identification stuff stored in nvram to backup partitions. Your phone has built in backup partitions for this data and it will try to restore from them under certain circumstances (usually a flash gone wrong), but by default the backups are blank . Your phone will reboot, you'll see a couple of real quick flashes of little blue text, then it will boot up again normally.
Some other good terminal commands to note the output of would be:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
That will tell you what bootloader and modem your phone is running on. You need to know this if you plan on doing any custom rom flashing. As a general rule don't ever attempt to downgrade bootloaders on this phone; the older ones can actually be downgraded but the newer ones will hard brick if you try it. Research, research, research before you do anything, and don't be afraid to ask questions. XDA forums are a great source of information, but beware of old information. Knox and the secure bootloaders changed how we have to treat this phone around Fall 2013, so following old forum posts or old articles on lifehacker or somewhere like that can be dangerous. Mostly custom rom zips won't touch your bootloader or modem. Its Odin you have to be most careful with, as those packages tend to be full firmware updates.
You're not ready to flash custom roms just yet unless you already flashed a custom recovery too like. You can use an Play store app called flashify to flash a custom recovery too since you're already rooted.
Flashify and Titanium Backup (pro version is very worth the money) are the only root apps I have on my S3.
Click to expand...
Click to collapse
I downloaded a terminal and used those commands. They came up with the same thing: I747MVLUFNH2. Knowing that if I flash twrp using flashify, do you have any suggestions for a stable custom Rom to use? Thanks for the help!
Repromi64433 said:
I downloaded a terminal and used those commands. They came up with the same thing: I747MVLUFNH2. Knowing that if I flash twrp using flashify, do you have any suggestions for a stable custom Rom to use? Thanks for the help!
Click to expand...
Click to collapse
I like pacman and slim. Candy is good too, but the newest kitkat builds don't work with my modem.
jason2678 said:
I like pacman and slim. Candy is good too, but the newest kitkat builds don't work with my modem.
Click to expand...
Click to collapse
Do you know which slimkat I would use? under s3 I only see i9300 adnd d2lte.
Repromise said:
Do you know which slimkat I would use? under s3 I only see i9300 adnd d2lte.
Click to expand...
Click to collapse
Never flash an i9300 ROM or you'll have a bad day.
You want d2lte.
jason2678 said:
Never flash an i9300 ROM or you'll have a bad day.
You want d2lte.
Click to expand...
Click to collapse
Alright, anything else I should know or am I good just following the instructions posted on the website?
Also I see that it says to install gapps, what is that? and when it says SD card is that just onto my phone storage or an external SD card? Sorry for all the questions lol
Repromise said:
Alright, anything else I should know or am I good just following the instructions posted on the website?
Also I see that it says to install gapps, what is that? and when it says SD card is that just onto my phone storage or an external SD card? Sorry for all the questions lol
Click to expand...
Click to collapse
Please read up some more before you attempt to install a custom rom. Most of the questions you are asking have been covered extensively throughout XDA and other forums. While you are at it, please don't limit yourself to just learning how to install a custom rom, but also learn what you should do in the event of issues. Some issues are general across all android devices and others are phone model specific.
Gapps is one of those basic things that you learn in the process of learning about rooting and installing custom roms and it is constantly being covered in discussions, wikis, and what not. But just to answer what is it: it is a necessary piece for installing most AOSP roms (If you do not know what AOSP is then please do some heavy research) if you want the Google Play store and other Google apps..
aybarrap1 said:
Please read up some more before you attempt to install a custom rom. Most of the questions you are asking have been covered extensively throughout XDA and other forums. While you are at it, please don't limit yourself to just learning how to install a custom rom, but also learn what you should do in the event of issues. Some issues are general across all android devices and others are phone model specific.
Gapps is one of those basic things that you learn in the process of learning about rooting and installing custom roms and it is constantly being covered in discussions, wikis, and what not. But just to answer what is it: it is a necessary piece for installing most AOSP roms (If you do not know what AOSP is then please do some heavy research) if you want the Google Play store and other Google apps..
Click to expand...
Click to collapse
Will do, sorry for trying to be spoonfed. I'll try to do some research, but I'm not really sure where to start. Which is mostly why I'm asking so much
Repromise said:
Will do, sorry for trying to be spoofed. I'll try to do some research, but I'm not really sure where to start. Which is mostly why I'm asking so much
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1802160
this a thread to explain some basics if you want. and as @aybarrap1 explained earlier , if you want direct access to the play store then you have to have the gapps pkg also. it is not necessary for the ROM to run and there are other markets to obtain apps., fdroid , aptoid , etc. ( bundling gapps with AOSP roms is a license thing , which i obviously dont have firm knowledge about. lol ).
as far as stable custom ROMs go it can really vary from device to device. i would suggest to read thru the threads and you can get a general feel for the stability of the ROM.
but once again , you'll probably just have to try some out and see.
some ROMs also require a certain level bootloader/modem to be able to be flashed , but it should state that in the first post.
good luck and happy flashing.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Repromise said:
Will do, sorry for trying to be spoonfed. I'll try to do some research, but I'm not really sure where to start. Which is mostly why I'm asking so much
Click to expand...
Click to collapse
No problem. I just want to make sure you know enough that you can hopefully avoid hard bricking your phone as well as how to fix (or search for fixes) should something happen such as a soft brick or boot loop. If we were just to tell step by step how to install a specific ROM now, you would not be prepared to fix your phone should something go wrong.
The link mentioned by mrrocketdog is an excellent place to start. For the specifics with the d2att, just start reading through the AT&T Galaxy S3 forums by choosing topics about various issues. Make sure you read the stickies...they are there for good reason. If you see a ROM you might be interested in, please make sure you read the OP thoroughly and completely. If you don't understand something stated, go look for what it means. Read through the forum for the ROM...especially posts dated on and after the last modification and updated ROM by the OP. This will give you good information on any issues individuals are running into and what not.
It seems that few ever talk about the ZE500CL variant of the zenfone 2. I've read a whole lot of posts on rooting, unlocking the bootloader, and installing TWRP, but most do not even mention this variant.
I started this thread to collect some information about this device. I would like to know from those who have this device, what has worked for you so far, and what hasn't? I'm especially interested in finding out the 3 things mentioned above.
I've only recently bought the device, and I only rooted it (though I did first get one bootloop already). The method that worked for me is described in this thread: http://forum.xda-developers.com/zenfone2/general/root-ze500cl-z00d-t3116531
The OP of the thread linked above also said that the second method on this thread: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 works as well.
Btw, make sure the drivers are installed, else the computer won't be able to recognize the device when it is in bootloader mode.
Installing Xposed works as well using the ADB method mentioned in the thread linked below:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476
I can add any info you find to the device index in the general section for the 500CL.
Djalaal said:
I've only recently bought the device, and I only rooted it (though I did first get one bootloop already). The method that worked for me is described in this thread: http://forum.xda-developers.com/zenfone2/general/root-ze500cl-z00d-t3116531
The OP of the thread linked above also said that the second method on this thread: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 works as well.
Btw, make sure the drivers are installed, else the computer won't be able to recognize the device when it is in bootloader mode.
Click to expand...
Click to collapse
How did you fix/handle the bootloop?
Do you know if it is possible to update the phone after rooting it?
cmendonc2 said:
I can add any info you find to the device index in the general section for the 500CL.
Click to expand...
Click to collapse
Sure, that post is much more likely to be noticed than this one. Although I might not find out much. I'm a lot less daring without custom recovery. Hence this thread.
crisbal said:
How did you fix/handle the bootloop?
Do you know if it is possible to update the phone after rooting it?
Click to expand...
Click to collapse
Well, seeing that I do not have a custom recovery (bootloader is still locked), I had to do it the hard way, reflash stock rom. Good news is, apparently your userdata (installed apps+settings and internal memory) is not wiped in the process.
First, you gotta download the rom. Get it from http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748. Although I got mine here: http://www.asus-zenfone.com/2015/03/asus-zenfone-2-stock-rom-ze500cl-ze550ml-ze551ml.html, which is the old version.
Second, go into recovery mode (from bootloader mode), and use adb sideload ("apply update from ADB") to flash the .zip downloaded before. This is described under "Flashing Zenfone 2 via ADB" on this thread: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Btw, the bootloop was caused by a mistake I made, not the rooting process.
any news update in our bootloader? hope someone could work for that..
How to get rid off couldn't add widget?
crisbal said:
Do you know if it is possible to update the phone after rooting it?
Click to expand...
Click to collapse
After more than a week of feeling unsure to update mine to WW_12.16.5.118, updating it today after finish uninstalling SuperSU. This is what I have done.
1 - uninstall SuperSU from SuperSU setting - reboot.
2 - update firmware.
3 - re-root using Temporary_CWM method as describe here
Chinaphonearena said:
Method 2: Root through temporary CWM
This is a temporary CWM with the primary purpose of injecting SuperSU onto your Asus Zenfone 2. It doesn't permanently replace recovery. This process looks long, but really is bam 1,2,3 done. Just laid out step by step for the newbie.
link removed due to post count limitation
Unzip the package
Copy SuperSU.zip to the base of your SD card
Enable USB debugging (Settings > Phone info > Tap build 7x > Back button > Developer options > USB debugging)
If you don't already have ADB drivers installed, you may need to [post count restriction] and install them (most PCs have them already, but trying installing these if you're having trouble getting your PC to issue commands to the phone via USB)
With your phone on, attach it to PC via USB
Run 'cai_dat_CWM.bat' from the CWM package
In the black command window that opens, type ACCEPT
Type T4
Phone will reboot into fastboot and you'll see commands being issued from the PC cmd window copying the temporary recovery
You may see some funked up images on your display for a bit. Remove the USB cable and within 30 seconds should then see it booted into CWM
Select install update
Navigate to SuperSU.zip and install
Bam, done.
Click to expand...
Click to collapse
4 - Success!!! now my phone are rooted and all rooted apps installed previously are working.
Note: Previously (before updating FOTA) I also root my ZE500CL using Temporary_CWM since One Click root method aren't working for me.
Recover from bootfreeze while fully stock
Well, after getting a bootfreeze being on a fully (old version) stock ze500cl (Z00D), I figured out something useful. How to recover from a bootfreeze with locked bootloader, non rooted stock rom, without loosing what was saved on your internal storage.
Given that you have not messed with system files (since you aren't rooted), I'm assuming you got either corrupted userdata files or your internal storage is so full, the phone fails to even boot. I had the latter. If system files are the problem, this method might (or probably?) not work. The trick is to use tethered TWRP for backing up your internal storage.
1: Download CWM_Zenfone_2_Intel.zip here: https://www.mediafire.com/folder/w70w7r1a65840/Zenfone_2 (gotten from source 1)
2: Download Recovery.zip here: https://drive.google.com/folderview...T0xRMVRkcTg3MHdlc1o0cVFBc3RPeTQ&usp=drive_web (gotten from source 2)
3: Extract the zip from Step 1.
4: Go to the FB_RecoveryLauncher folder you have extracted, and replace the recovery.zip there with the one downloaded in Step 2.
5: Boot into your stock recovery and connect your phone to the computer. Make sure you have adb and the phone's drivers installed (gotten from source 3).
6. Run the cai_dat_CWM.bat script and you should boot into temporary TWRP recovery after a minute or so.
7. Use TWRP to copy your sdcard folder (internal storage) into your ext_sdcard folder (external storage/microsd) for the sake of backing it up.
8a. In the case of having too full internal storage, simply delete some things in there, and you should be able to boot it again.
8b. Not tested, but in case of corrupted userdata, a factory reset is probably necessary, and will solve the bootfreeze issue.
source 1: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 (method 2)
source 2: http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532
source 3: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
@cmendonc2 , if you want, you can add this to your index.
Djalaal said:
It seems that few ever talk about the ZE500CL variant of the zenfone 2. I've read a whole lot of posts on rooting, unlocking the bootloader, and installing TWRP, but most do not even mention this variant.
I started this thread to collect some information about this device. I would like to know from those who have this device, what has worked for you so far, and what hasn't? I'm especially interested in finding out the 3 things mentioned above.
Click to expand...
Click to collapse
Thank you so much for providing this thread. Found it after hours of scouring the internet in search of help after somehow getting my phone locked in boot-loop. There isn't much support for the ZE500CL, but I will be posting on some blogs while I begin work on mine, and I will reference others to this thread and the few others I've found. Thanks again! :good:
Xanathide said:
Thank you so much for providing this thread. Found it after hours of scouring the internet in search of help after somehow getting my phone locked in boot-loop. There isn't much support for the ZE500CL, but I will be posting on some blogs while I begin work on mine, and I will reference others to this thread and the few others I've found. Thanks again! :good:
Click to expand...
Click to collapse
Sorry, was out of town for 3 months. Glad to be of help. You know where the thanks button is .
I should note that the this phone is now the daily driver of both my parents so I stopped tinkering with it, although I left one of them rooted (and the other not lol). So don't expect more updates from me sadly.
Djalaal said:
Sorry, was out of town for 3 months. Glad to be of help. You know where the thanks button is .
I should note that the this phone is now the daily driver of both my parents so I stopped tinkering with it, although I left one of them rooted (and the other not lol). So don't expect more updates from me sadly.
Click to expand...
Click to collapse
That's quite alright, I've had my fun with Z00D, got myself a LG V10 to break now
I dont ask for directions...
This is my first time asking questions as I have always been able to reverse-engineer (R-E) or as the hacker in swordfish would say "the code just comes to me". Ive been around computers since my dad took me to work at UT and commands were issued with punch out cards....I've been a long time android self taught enthusiast turned professional. ITT Alum etc. I research, I surf, I R-E, and I try every possible option etc...only this has me stumped. And this is the first android that has stumped me. I double checked everything but I keep getting this error in BBQLinux: I followed all pre-update instructions to the T.
fw: ATT_12.16.10.92
adb sideload
This package is not for ATT (WW)
E: Error in /sideload/package.zip
(Status 7)
yes I did with root cmd line, yes cd to zip file location, yes I verified correct fw, even tried different fw zips ZE500CL downloaded officially and from here.
I greatly appreciate any help and I do apologize for "asking for directions"
Computer John dba Austin Computer Techs
cuervo233 said:
This is my first time asking questions as I have always been able to reverse-engineer (R-E) or as the hacker in swordfish would say "the code just comes to me". Ive been around computers since my dad took me to work at UT and commands were issued with punch out cards....I've been a long time android self taught enthusiast turned professional. ITT Alum etc. I research, I surf, I R-E, and I try every possible option etc...only this has me stumped. And this is the first android that has stumped me. I double checked everything but I keep getting this error in BBQLinux: I followed all pre-update instructions to the T.
fw: ATT_12.16.10.92
adb sideload
This package is not for ATT (WW)
E: Error in /sideload/package.zip
(Status 7)
yes I did with root cmd line, yes cd to zip file location, yes I verified correct fw, even tried different fw zips ZE500CL downloaded officially and from here.
I greatly appreciate any help and I do apologize for "asking for directions"
Computer John dba Austin Computer Techs
Click to expand...
Click to collapse
?? Is that att ota youre trying to sideload? Att doesn't have fw, ze500cl does. But just unlock your bootloader, flash twrp, then install whatever, cm, aicp, custom stock or straight stock. http://forum.xda-developers.com/showthread.php?p=64991762
Sent from my MotoG3 using Tapatalk
Cool, I didn't read anywhere about unlocking BL first otherwise Ida made that "turn at the first light". We will ULO thru Asus and continue on our journey. These little Asus trinkets are little buggers being Intel based. Only line of Android devices that have ever stumped me. I am much obliged, fellow XDA brethren. Much obliged.
After pondering a little I came to this conclusion:
UL BL is basically the first step one should take when doing any kind of flashing of internal partitions be it a boot.img, recovery.img, FW etc... at least for the higher end devices. I don't recall having to do that for my sm-n900t recently. Does it only apply for flashing back to stock and not custom roms? Although I didn't have to UL BL first when I heim-dall/Odin flashed my note3 back to stock rom after being boot-looped. Cause once I did that I was able to try out a majority of custom roms available for it whether flashed thru HD/fastboot, Odin, via twrp update zip, or adb sideload. Hmmm, I might understand once I think it thru and look at all the different variables.
Good day gentlemen.
Be vewy vewy quiet, I'm hunting androids...
:good:
@cuervo233 Yes most devices you have to unlock the bootloader first. But there are some devices that already come unlocked. And then there are even some that have bootloaders that cannot be unlocked due to carrier restrictions. In order to get custom recovery to boot you must unlock the bootloader or it must come unlocked. With a custom recovery you can Flash the stock zip file from the Asus website or a custom ROM have fun
Sent from my MotoG3 using Tapatalk
Thank you. I was able to ULBL, flash TWRP, flash to ww 118, root, and now its time to explore the neat wonderful world of custom ROMs. This was by far the hardest yet. Next in line is the cricket Stylo which was also giving me hell, but now I dont think I should have any problem getting it done. I'll keep ya'll posted.:good:
Lg stylo should have way more development, have fun brother. Remember tmobile phones( cricket, walmart family mobile, and metro pcs) you can easily unlock the bootloader . att on the other hand usually has locked down bl.
Sent from my MotoG3 using Tapatalk
Hi all! I've been reading along with many an XDA thread for years now, and most people have asked my questions and found answers to them without me becoming active in any way. This will now change - I hope you can help me.
I own an unbranded Sony Xperia Z1 compact (amami). Upon receiving it, I backed up the TA partition, unlocked the bootloader and followed the steps to install Cyanogenmod (currently running the latest available nightly, CM12.1). All has worked well for a nice, long time now. I know, never touch a running system, but for a variety of reasons, I want to do the following:
Update the bootloader to make use of the proper recovery partition Sony has made available.
Install either TWRP or CWM (rather the former than the latter) to a proper recovery partition.
Be able to fool around for real once I have a proper NANDroid backup that I can actually use.
I've been able to make a NANDroid backup, that's easy. However, as far as I know, I can't use that backup with my current CM recovery. I can replace CM recovery with TWRP or CWM (with some tinkering, which is fine), but the fact that there's a way to get a proper recovery partition and that I'm currently not able to use it irks me. Perhaps some of you will understand
Now, when I install the official Sony Flash Tool (Emma), I'm offered two "services":
D5503 14.5.A.0.270 Customized_NCB 1279-4149 R2D User COM
D5503 14.6.A.1.236 Customized_NCB 1279-4149 R3D User COM
Neither of which are the "Open Devices" bootloaders listed by the FXP folks on their blog entry (sorry about the improper links, but I have no choice): ttp://fxpblog.co/2015/05/01/finally-boot-to-recovery-enabled-in-special-bootloaders-from-sony.html, and according to Sony itself, the Z1 compact should be supported: ttp://developer.sonymobile.com/2015/05/18/recovery-mode-now-available-for-a-range-of-unlocked-xperia-devices-video/
So my question to you all is this: Do I need to flash a complete stock ROM (losing my data, etc.) in order to make the new bootloader possible on amami? And if so, should I restore the TA partition I backed up in the very beginning before doing any of that? Or is what I'm trying to do pointless? If it's not pointless, is there a way to update the bootloader without wiping the phone?
Thanks for your input, guys!
tinuthir said:
Hi all! I've been reading along with many an XDA thread for years now, and most people have asked my questions and found answers to them without me becoming active in any way. This will now change - I hope you can help me.
I own an unbranded Sony Xperia Z1 compact (amami). Upon receiving it, I backed up the TA partition, unlocked the bootloader and followed the steps to install Cyanogenmod (currently running the latest available nightly, CM12.1). All has worked well for a nice, long time now. I know, never touch a running system, but for a variety of reasons, I want to do the following:
Update the bootloader to make use of the proper recovery partition Sony has made available.
Install either TWRP or CWM (rather the former than the latter) to a proper recovery partition.
Be able to fool around for real once I have a proper NANDroid backup that I can actually use.
I've been able to make a NANDroid backup, that's easy. However, as far as I know, I can't use that backup with my current CM recovery. I can replace CM recovery with TWRP or CWM (with some tinkering, which is fine), but the fact that there's a way to get a proper recovery partition and that I'm currently not able to use it irks me. Perhaps some of you will understand
Now, when I install the official Sony Flash Tool (Emma), I'm offered two "services":
D5503 14.5.A.0.270 Customized_NCB 1279-4149 R2D User COM
D5503 14.6.A.1.236 Customized_NCB 1279-4149 R3D User COM
Neither of which are the "Open Devices" bootloaders listed by the FXP folks on their blog entry (sorry about the improper links, but I have no choice): ttp://fxpblog.co/2015/05/01/finally-boot-to-recovery-enabled-in-special-bootloaders-from-sony.html, and according to Sony itself, the Z1 compact should be supported: ttp://developer.sonymobile.com/2015/05/18/recovery-mode-now-available-for-a-range-of-unlocked-xperia-devices-video/
So my question to you all is this: Do I need to flash a complete stock ROM (losing my data, etc.) in order to make the new bootloader possible on amami? And if so, should I restore the TA partition I backed up in the very beginning before doing any of that? Or is what I'm trying to do pointless? If it's not pointless, is there a way to update the bootloader without wiping the phone?
Thanks for your input, guys!
Click to expand...
Click to collapse
Check the other drop-down boxes on Emma. There should be one for 'ta update'. That's the one you want. It's been several months, so I might not be remembering right, but I'm pretty sure. Once you do that, use fastboot or Rashr to flash a compatible recovery img, and you can access the new recovery.
levone1 said:
Check the other drop-down boxes on Emma. There should be one for 'ta update'. That's the one you want. It's been several months, so I might not be remembering right, but I'm pretty sure. Once you do that, use fastboot or Rashr to flash a compatible recovery img, and you can access the new recovery.
Click to expand...
Click to collapse
Nope, no drop-down boxes. The only one is labeled "Filter", but that's empty. I can enter something, but entering "ta update" gets me nothing new. If I leave it empty, I get shown two "services", but they both seem to be complete stock re-flashings, so no dice.
tinuthir said:
Nope, no drop-down boxes. The only one is labeled "Filter", but that's empty. I can enter something, but entering "ta update" gets me nothing new. If I leave it empty, I get shown two "services", but they both seem to be complete stock re-flashings, so no dice.
Click to expand...
Click to collapse
Interesting. Is that with the phone connected? If so, are you sure that it's not already updated, (have you had it since new)? I did it while on 270, (or maybe sooner), and there were a couple of options to update rom, but I didn't update, and there was also a 'ta update' option.
levone1 said:
Interesting. Is that with the phone connected? If so, are you sure that it's not already updated, (have you had it since new)? I did it while on 270, (or maybe sooner), and there were a couple of options to update rom, but I didn't update, and there was also a 'ta update' option.
Click to expand...
Click to collapse
Yup, right after I connect the phone. It's recognized immediately as well, so I'm not sure there's anything I could have mucked up in that regard
I've had the phone since August 2014, so well before the bootloader upgrade was made public. I have no idea whether this might have been part of some CM update or something? I doubt it, but I don't know enough about these things to assess that to any reasonable degree.
At any rate, I know that I've done nothing with the phone's bootloader besides unlocking it after getting the phone. So if it was updated somehow in the meantime, it must have been someone very sneaky (and none of my friends, that's for sure - my limited experience makes me the "smartphone nerd" among them).
I will add this: In order to backup the TA partition back in the day, I did have to flash numerous official stock firmware downgrades to get to the point where I could use a root exploit to even get at the TA partition. Perhaps that got something mixed up, I dunno. But that's kinda what I'm trying to figure out - whether there's any point in going back to stock (completely, mind - including the TA partition), and if this might work then. I could then just unlock the bootloader again and go back to CM with a proper recovery partition, not the current workaround.
What's the "270" that you mean? One of the official Sony firmwares I posted earlier?
tinuthir said:
Yup, right after I connect the phone. It's recognized immediately as well, so I'm not sure there's anything I could have mucked up in that regard
I've had the phone since August 2014, so well before the bootloader upgrade was made public. I have no idea whether this might have been part of some CM update or something? I doubt it, but I don't know enough about these things to assess that to any reasonable degree.
At any rate, I know that I've done nothing with the phone's bootloader besides unlocking it after getting the phone. So if it was updated somehow in the meantime, it must have been someone very sneaky (and none of my friends, that's for sure - my limited experience makes me the "smartphone nerd" among them).
I will add this: In order to backup the TA partition back in the day, I did have to flash numerous official stock firmware downgrades to get to the point where I could use a root exploit to even get at the TA partition. Perhaps that got something mixed up, I dunno. But that's kinda what I'm trying to figure out - whether there's any point in going back to stock (completely, mind - including the TA partition), and if this might work then. I could then just unlock the bootloader again and go back to CM with a proper recovery partition, not the current workaround.
What's the "270" that you mean? One of the official Sony firmwares I posted earlier?
Click to expand...
Click to collapse
Yes. I can't remember if it was the last 5.0 or the first 5.1. Anyway, I'm not sure why it's not showing. I would try maybe connecting in fastboot mode, and see if anything changes, or flash a newer fw, and see... It does say on Sony development site to flash fw first - http://developer.sonymobile.com/201...for-a-range-of-unlocked-xperia-devices-video/ Hope that helps.
no "TA update"
levone1 said:
Yes. I can't remember if it was the last 5.0 or the first 5.1. Anyway, I'm not sure why it's not showing. I would try maybe connecting in fastboot mode, and see if anything changes, or flash a newer fw, and see... It does say on Sony development site to flash fw first - http://developer.sonymobile.com/201...for-a-range-of-unlocked-xperia-devices-video/ Hope that helps.
Click to expand...
Click to collapse
Hi,
After flashing my z3 "TA update (open device) doesn't appear. According to this post new bootloader is included on all stock firmware > .200 but doesn't contain recovery image.
So after flashing the stock 24.x.x.x.200 and flashing recovery via 'fastboot flash recovery recovery.img' my phone boot the recovery without problem.
Hope this information can help.
P.S.: FOTAKernel recovery should be compatible (under some conditions) with this boot process according to my tests on z3 and some forum reads.
Hi tinuthir,
I have the same problem and also see only the two services you mentioned in your initial post. Have you found any solution yet how to install the "Open Devices" bootloader?
Regards
Tobias
Hi Tobias, I have not yet tried it. Basically, I'm too scared to use the NAND backup (which I make daily anyway)
I'm fairly sure that, with the NAND backup, not too much can go horribly wrong. But I'd need to make sure I either have a backup phone in case I do run into problems (this is currently not the case). Then, what I would do is this:
NAND backup
Restore TA partition/stock software that was originally on the phone
See whether the "open device" is now available via official Sony tool
Flash latest firmware via official Sony tool (regardless whether it says "open device" or not)
See whether the "open device" is now available via official Sony tool
Flash recovery
Flash NAND backup
As I said, the only reason I haven't done this yet is because I can't find the time to make sure I can run troubleshooting in case there are any issues... And because I'm a little wary of touching a running system
Just started the process, finally was courageous enough. The old saying is true: Never touch a running system
Restoring the TA partition soft-bricked my phone. Am now trying to reset the phone by using the official Sony PC Companion software. We'll see what's up then.
Sony PC Companion didn't work. Instead, what apparently happened is that the bootloader, recovery, and OS didn't like being confronted with the restored backup partition - at all. Can't use the Flashtool to re-unlock, can't use Emma to flash new software, because the phone's locked...
Using the command line got the phone unlocked again, standard procedure as detailed here: *ttps://talk.sonymobile.com/t5/Android-development/Unable-to-unlock-bootloader/td-p/461477
Now I can re-flash and do whatever I like. Glad I had my NAND!
tinuthir said:
So my question to you all is this: Do I need to flash a complete stock ROM (losing my data, etc.) in order to make the new bootloader possible on amami? And if so, should I restore the TA partition I backed up in the very beginning before doing any of that? Or is what I'm trying to do pointless? If it's not pointless, is there a way to update the bootloader without wiping the phone?
Click to expand...
Click to collapse
Sorry I'm too late.
After reading some posts about new bootloader and some ta partition analysis bootloaders versions and TA partitions should never mix: they are incompatible.
Did you backup your ta partition after upgrading bootloader?
I am currently trying to help someone with a bad bootloader (supposed s1) on the phone, and maybe there is a way to reflash full emmc in a 'serial' way. I try to find quickly this time
Otherwise, maybe if you are able to access flashmode you can reflash your ta-with-upgraded-bootloader with it?
If you don't have ta backup after the upgrade, and your phone is still bricked, fell free to contact me, maybe we can found another solution based on this thread.
Good luck!
P.S. I try to write a guide about bootloader upgrade.
I have an old Sony Xperia M C1905 that I want to root/load a custom, cut-down ROM to free up space for the Apps that seem to be growing with every update. I am a NOOB (as you say) to installing custom F/W on my phone, BUT I am tech-savvy. What I need is access to a set of instructions/tools that I can use with my phone and PC combination. I realise that this is an old phone and you are trying to help, but for me it is frustrating when all the links to tools from the threads seem to be dead or don't work. Please can someone have a read and let me know a way to do this that has a set of working tools. Thanks
My PC is a MS Windows 10 laptop – If necessary, I could resurrect an old laptop and install Linux on it, if that is a simpler approach.
I have had a look at what is available and will probably load the ROM from:
https://forum.xda-developers.com/xperia-m/orig-development/rom-slim6-marshmallow-t3418258
What I think I need to do (and have tried to start) is:
1. Root the phone.
2. Backup the current ROM.
3. Unlock the boot-loader.
4. Load the Slim6 ROM.
To do 1. I have tried two methods, the first recommended from the backup thread and a second found by searching.
i. Easy Rooting toolkit: https://forum.xda-developers.com/showthread.php?t=2292598 but the download link for DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit.zip. The Download site for this tool tells me (eventually) that the file has expired or has been deleted by the owner - so i can't get this tool. Any Ideas How to get this?
ii. Also tried: https://forum.xda-developers.com/showthread.php?t=2529561 but for me, the cydia impactor tool does not see my phone or have any options. Yes, I have enabled - and allowed USB debug mode, before you ask. And yes the PC can see the phone so the connection is good.
To do 2. I am proposing to use the instructions from this thread: http://forum.xda-developers.com/showthread.php?t=2292598 Please confirm this is still valid.
iii. [Update] Also tried rooting by using this thread: https://forum.xda-developers.com/showthread.php?t=2457174 but this requires Framaroot 1.5.3, When I try and download this, the download site says: "The file link that you requested is not valid. Please contact link publisher or try to make a search."
Update 2. Managed to get a download of Framaroot, installed, but does not work for Xperia M with Android 4.3. Any idea of a way forward?
To do 3. I am proposing to use: https://forum.xda-developers.com/showthread.php?t=2484622 Please confirm this thread is still valid - and the best approach.
To do 4. https://forum.xda-developers.com/xperia-m/orig-development/rom-slim6-marshmallow-t3418258 - Please let me know if there is a more appropriate ROM to install to free up some space.
You can follow this link :
And for root, I think slim6 is pre rooted. Means in Developer options, select root for adb and apps.
What about backing up the current ROME?
Thanks for your reply, but to my understanding this just does 2. & 3. from my list. Most of the ROM installation guides say to take a backup of the current ROM so that you can restore the original system.
To do this I need to get root access with the current build. Is this now impossible?
Maybe I just need to bite the bullet and just not bother with the backup.
You should definitely take a backup.
This is because of the TA partition. As soon as you unlock the bootloader of your phone it will format the TA partition, so without the backup you won't be able to restore it which might be needed. Using a TA backup from another phone will NOT work.
So you are right about the steps, you need to root the phone, backup, unlock the boot loader and flash the new ROM. I didn't check all of the links you posted now, but if Framearoot is not working for you you might want to try out iovyroot. Also check that you downloaded the right tool to root for your Android version.
If it's still relevant and you need any additional help I'll post some instructions for you another day.
Thanks for the confirmation of the process.
Iovyroot is not a root method I have tried. I will Investigate tomorrow.
I will post back here when I have tried it.
I have tried a couple of versions of Framaroot, one recommended version for the phone, and the latest version I could find. Neither worked.
Maninfrontofpc said:
Thanks for your reply, but to my understanding this just does 2. & 3. from my list. Most of the ROM installation guides say to take a backup of the current ROM so that you can restore the original system.
To do this I need to get root access with the current build. Is this now impossible?
Maybe I just need to bite the bullet and just not bother with the backup.
Click to expand...
Click to collapse
You don't need to get root access to have a backup. Just unlock your bootloader and install cwm or twrp through fastboot and take backup with help of it. Now if you are on stock rom and you need root anyway, you can use towelroot. And then install supersu from playstore. OR flash superSU through cwm. In that case no need to install towelroot.
Is nidhoegg mistaken?
Please can you confirm that the TA partition will Be NOT be formatted when I unlock the boot loader?
Maninfrontofpc said:
Please can you confirm that the TA partition will Be NOT be formatted when I unlock the boot loader?
Click to expand...
Click to collapse
Why are you so much worried about TA partition?
My understanding is that this contains various sets of system data including: S/W signatures for the Sony Apps (if I want to restore the Sony ROM to the phone); calibration data of the various devices on the phone - accelerometer etc. So surely, even if just for the calibration data, I would not want to lose this data even if I loaded a custom ROM - I have no way of re-calibrating the devices, so would need the factory acceptance calibration values.
Am I mistaken?
TA backup for our device isn't necessary. Actually I don't know anyone from xda taking TA backup. TA backup is for newer sony devices and z series devices. In those devices, somethings like sony camera wouldn't work if you lose drm keys. It's not the case with our mobile.
Are you saying that all the threads from when this was the current phone are wrong, and I don't need to backup this partition?
TA = Trim Area; as well as holding the DRM Keys/S/W signatures, my understanding is that at contains Trim data to adjust the various sensors on the phone to read accurately. I have been led to believe that these are written during the automated Factory Acceptance Testing to adjust for small differences in the components on the phone, and are unique to the device. Surely if I lose this data the sensors will not read accurately.
Is this wrong?