After countless hours of searching over all related posts I am still confused and pretty much intimidated on the flashing aspect. From all my searching expeditions till now I managed to outline some of the points but I don't know how to move forward with them. Also I am concerned with the possibilities of getting the device unresponsive just because of my stupidity, want to gain full knowledge before going forward with the process.
So as per my findings, for installing a CFW like CM12, I require the following things,
1. Unlocked Bootloader.
The Bootloader on my XM SS can be unlocked, I did a check on that but the thing that's bugging me is the occurrence of bootloop.
Question for this point: What is the proper method to unlock the bootloader?
2. Rooted phone.
This is the step that has confused me from the beginning. Some posts mention that rooting is essential requirement to get a fully functional CFW and in some posts there is a not a single mention for the requirement of a rooted phone.
Question for this point: Is rooting essential? What is the best step by step method that you use to root your device?
3. Back up data.
I read somewhere that unlocking the bootloader erases some of the important information like the IMEI number, DRM keys and other important stuff? Also the importance of backing up data like contacts and other stuff externally.
Question for this point: How to do a proper backup? How to go on backing up contacts, whatsapp databases etc?
4. Installing a custom recovery?
Honestly I am totally confused with this topic. What does custom recovery actually do? Best custom recover for CM12?
Question for this point: How to select and install a custom recovery?
5. Adb, Fastboot drivers.
Is it essential to actually download the full adb package that google provides to develop android apps? And are fastboot drivers available for windows 8.1? Will the phone management software provided by Sony work as a driver?
Question for this point: ADB, Fastboot driver installation?
6. Flashing the CM12.
The most important step in the whole process? How to go on with this step so as to successfully flash the firmware? Restoring the backed up data?
Question for this point: Steps to properly flash the CM12?
7. Link2SD, App2SD?
Which one will you suggest and how to go on installing it?
I know that most of you will find it bothersome to answer so many questions in a single go but I intend this topic to be a guiding thread for noobs like me who are beginners that want to flash some CFW on their devices.
So all the posts that you make are really appreciated! Please link in the posts that you think will answer the questions in layman terms for everyone to understand.
Thanks for taking your time to read this thread
Have a good day! :fingers-crossed:
Can anyone please help? :crying:
1. http://forum.xda-developers.com/showthread.php?t=2484622 Follow everything he said, while using some common sense. Just to avoid you in doing so much research on some common problems I faced, :
i) If any errors occur, just close flashtool and re-open it, even if the errors continue to happen, just close and open flashtool again.
ii) You will experience bootloop and the end of the procedure, so just flash the tft http://forum.xda-developers.com/showthread.php?t=2779412
2. Just stay rooted, better safe than sorry Here's the guide: http://forum.xda-developers.com/xperia-m/general/towel-root-steps-to-root-t2789990 Understand the procedure first then continue.
3. You can export your contacts into your sim card tho, just open up the telephony app and go to contacts and open up the option or menu thingy in it (I think the icon was a 3 dot to access the options menu) and you'll see the Export/Import tab on it. You know what to do after this After root, I suggest getting the app Titanium Backup, really helpful. If possible, after the backup, move the folder to the sdcard, so it will never be lost (or to your pc, much safer).
4. Custom recovery.. well, I'm no expert but just think it this way, you're life saver when you do something wrong to your phone (and that it can still turn on, but couldn't get pass the boot animation) and provided that you had made a Nandroid backup before(a system backup). It can restore your phone back to the last time you've backuped it. This one for Stock 4.3 http://forum.xda-developers.com/xperia-m/development/recovery-philz-touch-6-41-6-xm-dual-t2795778 and this one for afteryou've installed CM12 http://forum.xda-developers.com/xpe...very-cwm-twrp-recoveries-custom-roms-t3016507
5. I'm not sure on this one, sorry:crying: ADB drivers and the fastboot drivers installed automatically for me:silly:
6. I think this video would be a bit helpful https://www.youtube.com/watch?v=DkNu0tiNro8
7. I don't know on this, I never used them. Soz :C
All the best:fingers-crossed: though my advice would be to stay Rooted for awhile before unlocking the bootloader, so you'd at least familiarize yourself with the terms that'll you'll most probably face.
The fastboot driver from google didnt work for me, use the ones from the sony bootloader unlock site. For win8.1 you need to disable signature verification to install them.
Thank you so much @AndyPhoenix9879
You are a lifesaver! I was finally able to flash CM2.1 on my Xperia M
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
My brother flashed android marsmallow via the kdz methot, and then followed this threat to root and install twrp,http://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268, but i dont know what he did, since he told me he skipped the autorec step and did that particular step as last, after rooting.
Now the phone is death, no charge indicator, no recovery, no download mode.
In device manager it shows as qhusb_bulk.
I followed the same guide with my own g3, and i had no problems, so i think my brother messed up somewhere in those steps with his phone.
Can any body help me to revive his phone?
I would be glad, and happy to donate if any solution.
werkman2 said:
My brother flashed android marsmallow via the kdz methot, and then followed this threat to root and install twrp,http://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268, but i dont know what he did, since he told me he skipped the autorec step and did that particular step as last, after rooting.
Now the phone is death, no charge indicator, no recovery, no download mode.
In device manager it shows as qhusb_bulk.
I followed the same guide with my own g3, and i had no problems, so i think my brother messed up somewhere in those steps with his phone.
Can any body help me to revive his phone?
I would be glad, and happy to donate if any solution.
Click to expand...
Click to collapse
Question goes in the Q/A.
Have you tried this?
Greetings,
Hopefuly I can get help. I updated my Oneplus 3 last night from 3.2.5 ver. To 4.0.2 ver. And after that my signal droppedd to zero. I tried reseting the phone but no luck. Im using a CDMA SIM card. It works in another phone. But no more in my oneplus 3 . Whats weird is that when I inserted a GSM SIM it worked but not my CDMA SIM. I checked the bands so its not the problem.
I tried contacting support. The told me they will scedual me for remote support. I asked what they will do. They said they will downgrade it. If any one have any idea of how they will downgrade it. I never unlocked bootloader or flashed any ROM or custom recovery. Is there a way to downgrade it without TWRP or unlocking bootloader. Can I use sideload mode to just adb install the older Oxygen OS. I found some instruction on the downloads.oneplus.net . but nothing about downgrading. Only manually flashing the ROM. I was thinking what if I just download the same ROM I'm on and just flash it that way. That if the problem was the ota update is corrupt and i need to reinstalling it.
Please someone who has experienced these methods help.
I dont want to brick my phone. Dont want to unlock the bootloader. I need to fix my problem if not the same way customer support planing to do but even less messy.
I have never tried any of these methods so please someone help. Either buy answering here or just give me some ref. Links that will give me some intel.
Thanks a lot
Use this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Go to section D and begin from #7 and finish at #11.
Instead of using OOS v4.0.2 OTA, use the OOS v3.2.8 OTA (provided in the guide).
If you have questions, post them in that guide.
Good luck!
hi Wolf2231
i have same your problem
please if u find a solution Please tell me
thank u
Thanks alot. I didnt use this guide. Because I have a locked bootloader. And in my question I needed a way that doesnt involve unlocking bootloader, rooting,... Etc.
Eventually my problem was caused partially to an old SIM card ( I'm confused my self ). Anyways I went through a lot of work. And what I also did is restored my phone to the very first stock OOS.
But first do the most basic troubleshooting. Factory reset try it from recovery. And anything that sounds obvious.
Follow the instructions here https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I downloaded and sideloaded OOS 3.2.8 .
I just posted the answer. If you went through any trouble using the instructions. Just ask.
I used the method (I believe method 2) that restored it to OOS 3.1.2
I also used the code *#*#4636#*#* (in dialpad )
Go to phone information and change prefered network to what is suitable.