Related
Hi guys.
I flash the fullscreen mode with cmw recovery, and when the system was reebot it stop to a boot screen (white with HTC One written).
I tried to lock bootloader and installing RUU, but it say me who phone is not plug on the pc.
I tried to wipe cache/dalvik/etc etc but I'm not able to restart my phone.
Anyone can help me?
I just try to "fastboot erase cache" and "fastboot reboot-bootloader"...but nothing.
..you need to learn to make a backup in recovery first, when you dont have that much experience yet.
Which rom you was using? The stock or a custom one?
relocking bootloader and try flashing a RUU was completly overkill.
You just need the original android.policy, which was overwritten by flashing the mod you tried to get running.
I'm sure someone can provide a flashable zip for that...just ask in teh thread of the mod.
If you got your rom runnning again, esnure to make a backup in recovery. On that way you can always restore your working rom.
...and btw: brick = cant turn device on
j4n87 said:
..you need to learn to make a backup in recovery first, when you dont have that much experience yet.
Click to expand...
Click to collapse
I learn it yesterday evening, I don't forget to do it next time.
Now I'm trying to flash the RUU, before I didn't enter in fastboot.
Installing complete.........
anxiety....
...it work.
Yeah I had the same issue after installing the full screen patch too. Thankfully I'd done a Nandroid backup just after I rooted so I just did that. Would have installed a custom Rom otherwise
Sent from my Desire HD running Virtuous Affinity Sense 3.5
j4n87 said:
..you need to learn to make a backup in recovery first, when you dont have that much experience yet.
Which rom you was using? The stock or a custom one?
relocking bootloader and try flashing a RUU was completly overkill.
You just need the original android.policy, which was overwritten by flashing the mod you tried to get running.
I'm sure someone can provide a flashable zip for that...just ask in teh thread of the mod.
If you got your rom runnning again, esnure to make a backup in recovery. On that way you can always restore your working rom.
...and btw: brick = cant turn device on
Click to expand...
Click to collapse
Hi, I'm completely new to Android and just upgraded myself from my 3GS to the One X (and what an upgrade at that!). However I'm a bit dissatisfied with the Sense interface and would like to flash it with either vanilla or some cool unofficial rom.
The problem is I'm scared to death of bricking it. Especially since a friend of mine had told me the usual method of being sure you won't get a bricked phone is to simple change the rom on your SD-card. It would seem things get a little trickier when you don't have an SD though.
How does this backup in recovery work? Will it be making a backup of everything on my phone now and place it in backup? Will this ensure a corrupt rom image or whatever won't brick my phone?
From what I understand a launch from recovery is completely separate from the rest of the system, so unless you've broken the memory card (in which case I guess your screwed anyway) it shouldn't be possible to brick the phone should it?
kaminix said:
Hi, I'm completely new to Android and just upgraded myself from my 3GS to the One X (and what an upgrade at that!). However I'm a bit dissatisfied with the Sense interface and would like to flash it with either vanilla or some cool unofficial rom.
The problem is I'm scared to death of bricking it. Especially since a friend of mine had told me the usual method of being sure you won't get a bricked phone is to simple change the rom on your SD-card. It would seem things get a little trickier when you don't have an SD though.
How does this backup in recovery work? Will it be making a backup of everything on my phone now and place it in backup? Will this ensure a corrupt rom image or whatever won't brick my phone?
From what I understand a launch from recovery is completely separate from the rest of the system, so unless you've broken the memory card (in which case I guess your screwed anyway) it shouldn't be possible to brick the phone should it?
Click to expand...
Click to collapse
what you are looking to flash would be called "aosp"...android open source project, this means pure, unadulterated android from Google. At present time there are no aosp roms for the hox. They all have the HTC sense interface. Be patient. I'm sure this device will get a lot of attention from the dev community and we will have plenty of aosp roms to choose from in the near future.
Sent from my Xoom using xda premium
nooomoto said:
what you are looking to flash would be called "aosp"...android open source project, this means pure, unadulterated android from Google. At present time there are no aosp roms for the hox. They all have the HTC sense interface. Be patient. I'm sure this device will get a lot of attention from the dev community and we will have plenty of aosp roms to choose from in the near future.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Ah, yes. This is indeed what I'm looking for. Thanks, guess I'll just wait a little longer then.
my too sgs2 hard bricked becuase one for wrong bootloader and other for synah rc 3.6 kernal, so i bought one x and now lets see......will this work or not?
You have to make sure your RUU is for the same network and country and is newer then your current RUU or the CID will block it
Can I flash a new bootloader using recovery (twrp)? (flashed plenty of ROMs and Kernels wasn't sure if the steps are the same for a bootloader)
So if I plug my rooted Nexus 7(2013) in to any usb cable on any computer, it is just not detected(assuming usb port is dead at this point, only charges), Cannot even get adbd wifi to start and listen on port 5555 went through every possible scenario.( basically tried everything you can will throw at me, (MTP/PTP, usb debugging on/off, new cables, new computers, remove every possible android driver and re-install)
I saw one post where someone seemed to have a similar issue but was able to update the bootloader and his problem was solved!
Now I am not sure how he did it since I can't seem to find any good info on updating the bootloader directly from say TWRP I have no other access into the device remotely or via USB
kernelsandirs said:
Can I flash a new bootloader using recovery (twrp)? (flashed plenty of ROMs and Kernels wasn't sure if the steps are the same for a bootloader)
So if I plug my rooted Nexus 7(2013) in to any usb cable on any computer, it is just not detected(assuming usb port is dead at this point, only charges), Cannot even get adbd wifi to start and listen on port 5555 went through every possible scenario.( basically tried everything you can will throw at me, (MTP/PTP, usb debugging on/off, new cables, new computers, remove every possible android driver and re-install)
I saw one post where someone seemed to have a similar issue but was able to update the bootloader and his problem was solved!
Now I am not sure how he did it since I can't seem to find any good info on updating the bootloader directly from say TWRP I have no other access into the device remotely or via USB
Click to expand...
Click to collapse
Yeah it's possible, I did it for the Nexus 4 before. Usually the bootloader update files are found within the OTA zip updates. Usually the bootloader is composed of multiple files, not just one. You can take those files and put them in a flashable zip and make sure the script flash the files to the correct partition of the device, all the info are in the updater-script file in the zip.
It look like this is the last OTA update for the N7 that have the bootloader files: http://android.clients.google.com/p....signed-razor-KTU84L-from-KOT49H.df43279b.zip
So you can use make a flashable zip for those bootloader files or I can do it later.
I guess a smarter person would be able to dump these partitions from their device, maybe just by using "dd" command while in recovery's ADB.
I previously flashed a pre-rooted 4.4.4 OTA Stock ROM which is what I have been running ever since.
I really don't know if, or why the bootloader would affect my ability to use the USB port or not, but I guess I just had some hope based on one other post that seemed to work with.
I am not sure how to make a flashable zip from an existing ROM image, only flashable zips I made came from Titanium backup producing the flashable files for me
eksasol said:
Yeah it's possible, I did it for the Nexus 4 before. Usually the bootloader update files are found within the OTA zip updates. Usually the bootloader is composed of multiple files, not just one. You can take those files and put them in a flashable zip and make sure the script is flash it to the correct partition of the device, all these infos are usually found in the official OTA zip. The problem is not all OTA zip have bootloader files, just the one that specifically update it.
It look like this is the last OTA update for the N7 that have the bootloader files: http://android.clients.google.com/p....signed-razor-KTU84L-from-KOT49H.df43279b.zip
So you can use make a flashable zip for those bootloader files or I can do it later.
The next one will be for Android 5, so we'll look forward to that also. I guess a smarter person would be able to dump these partitions from their device or something.
Click to expand...
Click to collapse
So your computer doesn't recognize the tablet when it's at the bootloader? Can you even get into bootloader? Tried different cables? Different USB ports?
I can get to TWRP, but no usb not recognized there, cannot use the mount feature in TWRP, tried all items in pretty much every post I could find that were related, inlcuding the items you suggest yes.
Maybe something with the stock rooted ROM has gone wacky, Been very good to this tablet as far as babying the usb port, as I have had other devices have broken ports as my kids would yank cables etc.
So really the only thing I have not done since this trouble started was just do a factory reset and re-flash the ROM, just afraid that is something goes wrong durring flash I will be out of luck restoring anything since I cannot get to the filesystem to put new ROMS etc unless I download them to SD before I begin the process while I have access to the OS and wifi.
nhizzat said:
So your computer doesn't recognize the tablet when it's at the bootloader? Can you even get into bootloader? Tried different cables? Different USB ports?
Click to expand...
Click to collapse
[snip]
Thanks @eksasol I think I may just let this sucker chill until the stock rooted Lollipop ROM, I was already on 4.02 I just thought there was a newer one, I think the Lollipop version has a 4.04 bootloader.
I greatly appreciate your time on this.
So I would assume that if the flash fails for any reason I will be the proud new owner of a nexus 9 shortly after
@eksasol do you have a flashable 4.04 bootloader or know a guide to making a bootloader flashable, I did use your 4.02 and it worked great, but for the Lollipop version I need 4.04 but can only find .img that needs fastboot, which I do not have access to since USB does not seem to work still.
kernelsandirs said:
@eksasol do you have a flashable 4.04 bootloader or know a guide to making a bootloader flashable, I did use your 4.02 and it worked great, but for the Lollipop version I need 4.04 but can only find .img that needs fastboot, which I do not have access to since USB does not seem to work still.
Click to expand...
Click to collapse
You will need to wait until the OTA zip for KitKat to Lollipop become available, it will include the proper 4.04 bootloader files needed for flashing.
OK cool, guess I am just impatient
@eksasol any chance you can throw a flashable 4.04 bootloader together, i see several others looking for one that are in the same boat as me, i looked around for a tutorial on making one but did not find any so far. Anyway if you get a chance or have some info on making one i would be grateful.
Here is the Android 5.0 bootloader version 4.04. For Nexus 7 WiFi only (Flo, Razor), again it will check to see if it's the correct device before proceeding with flashing. Go to this link: http://forum.xda-developers.com/nexus-7-2013/general/flashable-factory-image-zips-android-5-t2939599
kernelsandirs said:
@eksasol any chance you can throw a flashable 4.04 bootloader together, i see several others looking for one that are in the same boat as me, i looked around for a tutorial on making one but did not find any so far. Anyway if you get a chance or have some info on making one i would be grateful.
Click to expand...
Click to collapse
You didn't have to remind me every single day.
Thanks for this. I'm alright with adb and fastboot (i.e. I can follow directions) but I'm running the Windows 10 tech preview and it absolutely does not support either. Drivers are fine, it just won't do it. Won't happen at all. Then I throw it all on a flash, take it to work (Win7 Pro), and it works just as easy as you like, so it's not (likely) user incompetence... I woulda waited but figured someone else might have asked. So, much appreciated!
dragontology said:
Thanks for this. I'm alright with adb and fastboot (i.e. I can follow directions) but I'm running the Windows 10 tech preview and it absolutely does not support either. Drivers are fine, it just won't do it. Won't happen at all. Then I throw it all on a flash, take it to work (Win7 Pro), and it works just as easy as you like, so it's not (likely) user incompetence... I woulda waited but figured someone else might have asked. So, much appreciated!
Click to expand...
Click to collapse
They decided to skip 9?
I posted the full device's image in flashable zip formats here:
http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/
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 just received a Pixel 3XL as a free hand me down and need some assistance. I know it's a couple of years old but still seems to be a solid phone. I basically need to wipe this thing completely clean. The problem is that it's rooted with an unlocked bootloader with TWRP. While that might not be a huge issue it's also on a older Android version 9. I've been reading but I'm not exactly sure where to start in regards to what to do first. I know my share of rooting and flashing ROMs but my knowledge is back with the Nexus and older HTC phones. Any help would be greatly appreciated.
rootbox15 said:
I just received a Pixel 3XL as a free hand me down and need some assistance. I know it's a couple of years old but still seems to be a solid phone. I basically need to wipe this thing completely clean. The problem is that it's rooted with an unlocked bootloader with TWRP. While that might not be a huge issue it's also on a older Android version 9. I've been reading but I'm not exactly sure where to start in regards to what to do first. I know my share of rooting and flashing ROMs but my knowledge is back with the Nexus and older HTC phones. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hi,
Pretty much everything you need to know is here: https://forum.xda-developers.com/t/guide-root-pixel-3-xl-android-11-r.4160447/
You can go ahead and just flash whatever factory image you want from here, (mostly) just like a Nexus device:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Just use the flash-all script, don't flash one partition at a time...
It will remove root and wipe your phone clean. Root on Pixels doesn't work how it used to back in the Nexux days, as TWRP is not fully supported on 10 or 11 yet.
Just be sure the previous owner Google account has been properly removed before you proceed, otherwise you won't be able to log in with yours: FRP (Factory Reset Protection).
Post in the thread i linked you or here if you need further assistance.
Cheers...
Sébastien.
5.1 said:
Hi,
Pretty much everything you need to know is here: https://forum.xda-developers.com/t/guide-root-pixel-3-xl-android-11-r.4160447/
You can go ahead and just flash whatever factory image you want from here, (mostly) just like a Nexus device:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Just use the flash-all script, don't flash one partition at a time...
It will remove root and wipe your phone clean. Root on Pixels doesn't work how it used to back in the Nexux days, as TWRP is not fully supported on 10 or 11 yet.
Just be sure the previous owner Google account has been properly removed before you proceed, otherwise you won't be able to log in with yours: FRP (Factory Reset Protection).
Post in the thread i linked you or here if you need further assistance.
Cheers...
Sébastien.
Click to expand...
Click to collapse
Thanks for the reply, much appreciated. His account is completely gone and mine is the current one. I basically want to update it but I do want to keep root for a few things. I was mainly concerned since it's on an old version of 9 and I know there were some bootloader changes which is what really had me concerned.
rootbox15 said:
Thanks for the reply, much appreciated. His account is completely gone and mine is the current one. I basically want to update it but I do want to keep root for a few things. I was mainly concerned since it's on an old version of 9 and I know there were some bootloader changes which is what really had me concerned.
Click to expand...
Click to collapse
Hi,
You said you have read, but don't know where to start... If you state your goal, it would be easier to help you!
Keep root with stock firmware? What Android version?
Cheers,
Sébastien.
5.1 said:
Hi,
You said you have read, but don't know where to start... If you state your goal, it would be easier to help you!
Keep root with stock firmware? What Android version?
Cheers,
Sébastien.
Click to expand...
Click to collapse
Good point. I'd like to get updated to the most stable android version and keep root with the ability to flash custom kernels. I've been using this for a bit on 9 and it's definitely showing it's need to be updated. The option to flash ROMs would be nice but definitely not necessary. I'm not opposed to doing a complete wipe but if I could keep my data that would obviously be optimal even though I highly doubt that will be possible. Thanks again for the reply.
rootbox15 said:
Good point. I'd like to get updated to the most stable android version and keep root with the ability to flash custom kernels. I've been using this for a bit on 9 and it's definitely showing it's need to be updated. The option to flash ROMs would be nice but definitely not necessary. I'm not opposed to doing a complete wipe but if I could keep my data that would obviously be optimal even though I highly doubt that will be possible. Thanks again for the reply.
Click to expand...
Click to collapse
You should be able to update and save data.
Flash the factory image as mentioned above, however before you run the flash-all bat file edit it with notepad. Near the end of the file remove the -w and save it. Then run the flash all. That will update you and save data.
Then you reroot following one of the rooting guides. Copy boot.img from the factory image to your phone,. Install Magisk Manager and patch the boot.img. Copy that back to your computer and flash it.
TonikJDK said:
You should be able to update and save data.
Flash the factory image as mentioned above, however before you run the flash-all bat file edit it with notepad. Near the end of the file remove the -w and save it. Then run the flash all. That will update you and save data.
Then you reroot following one of the rooting guides. Copy boot.img from the factory image to your phone,. Install Magisk Manager and patch the boot.img. Copy that back to your computer and flash it.
Click to expand...
Click to collapse
Thanks for the reply. I read about doing that but just wasn't sure if that would all work properly since the bootloader was unlocked and TWRP was installed. I'm guessing the factory image flash will get rid of TWRP. It also doesn't matter going to say 11 straight from 9? Sorry for all the dumb questions but this is way different than it used to be when I started back with the original Galaxy S, HTC DesireHD, and Nexus 4.
rootbox15 said:
Thanks for the reply. I read about doing that but just wasn't sure if that would all work properly since the bootloader was unlocked and TWRP was installed. I'm guessing the factory image flash will get rid of TWRP. It also doesn't matter going to say 11 straight from 9? Sorry for all the dumb questions but this is way different than it used to be when I started back with the original Galaxy S, HTC DesireHD, and Nexus 4.
Click to expand...
Click to collapse
Correct, this flash will remove twrp. You are done with twrp it is not working on pixels 10 and up.
9 to 11 should be fine, there is always a risk upgrading a full version. That risk is not any greater because you are jumping two versions.