Database Info

[HOWTO] INSTALL STOCK FIRMWARE USING CWM/TWRP even w/a DEAD USB Port

GUIDE TO FLASHING STOCK FIRMWARE FOR ATT AND ROGERS I727 SKYROCKET PHONES WITHOUT USING ODIN OR KIES ​
THIS METHOD APPLYS TO:
ONLY FOR PHONES THAT CAN BOOT INTO A CUSTOM RECOVERY CWM/TWRP
USERS WHO CANT USE ODIN AND/OR KIES FOR WHATEVER REASON
PHONES WITH A BAD USB PORT
HAVE USB CONNECTIVITY ISSUES
MAC USERS WITH A CUSTOM RECOVERY ALREADY INSTALLED.
YOU ARE ON A CUSTOM ROM WITH USB PROBLEMS AND NEED TO RETURN TO STOCK FOR WARRANTY REPAIRS
NOTE: USING THIS GUIDE TO RETURN TO STOCK WILL PERMANENTLY UNROOT THE PHONE, BUT CAN BE REROOTED AFTER IF NEEDED.
Disclaimer: I am not responsible for your devices, follow guide at your own risk!
READ THE WHOLE POST
HOW TO ENTER INTO RECOVERY MODE, INSTRUCTIONS HERE STEP #4
GUIDE PRESUMES YOU ALREADY KNOW HOW TO INSTALL/FLASH FILES FROM RECOVERY
YOU NEED TO HAVE ONE OF THE RECOMMENDED CUSTOM RECOVERIES ALREADY INSTALLED ON THE PHONE SUCH AS CWM OR TWRP, LINKS IN THE DOWNLOAD SECTION BELOW
IN THIS GUIDE YOU WILL BE INSTALLING THE STOCK FIRMWARE ZIP FILE
OPTIONAL: INSTALLING THE STOCK RECOVERY ZIP FILE ONLY IF YOU NEED TO RETURN FOR WARRANTY, OTHERWISE NOT RECOMMENDED TO INSTALL
GETTING THE STOCK FIRMWARE TO YOUR PHONE
OPTION 1: IF YOUR ABLE TO BOOT INTO ANY ROM:
YOU HAVE A WORKING USB CONNECTION:
Download the files and transfer the files from your computer to your internal or external sdcard
YOU DONT HAVE A WORKING USB CONNECTION: USE EITHER METHOD "A" OR "B" OR "C":
METHOD A: From the phone use xda app or browser and navigate to this page and download the files directly to your device from the links provided below, then move them to the root of your internal or external sdcard, it will make it easier to find.
METHOD B: Use airdroid wirelwss appor kies air to transfer your files from your computer to your phone through your wifi connection and place them in the root of your internal or external sdcard
METHOD C: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
OPTION 2: YOUR NOT ABLE TO BOOT BUT CAN GET INTO A CUSTOM RECOVERY: USE EITHER METHOD "A" OR "B":
METHOD A: If usb port works: enable usb mount in custom recovery and transfer files to the root of your sdcard
METHOD B: If usb port doesnt work: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
FLASHING THE FILES
FIRMWARE
ENTER INTO RECOVERY MODE
PERFORM A RESET AND WIPE BOTH CACHES
INSTALL THE STOCK FIRMWARE ZIP FILE
ONLY INSTALL THE STOCK FIRMWARE(NOT THE STOCK RECOVERY ZIP FILE) THEN REBOOT THE PHONE INTO ANDROID TO CHECK IF IT BOOTS PROPERLY
YOUR GOOD LIKE THIS IF YOU JUST WANTED STOCK BACK ON YOUR PHONE
STOCK RECOVERY: ONLY RECOMMENDED IF RETURNING FOR WARRANTY REPAIR AND NEED TO SHOW FULL STOCK
TO GET THE STOCK RECOVERY ZIP FILE ONTO THE SDCARD FOLLOW THE INSTRUCTIONS FOR THE FIRMWARE GUIDE ABOVE
ENTER INTO RECOVERY MODE
INSTALL THE STOCK RECOVERY ZIP FILE, ONCE YOU DO THIS YOU WILL LOSE THE CUSTOM RECOVERY
IF YOU CANT USE ODIN THERE IS NO WAY TO REINSTALL A CUSTOM RECOVERY ON THE SKYROCKET ONCE THE STOCK RECOVERY HAS BEEN INSTALLED.
REBOOT PHONE INTO RECOVERY TO SEE IF THE STOCK RECOVERY FLASHED PROPERLY.
DOWNLOADS
MOVED TO THE 1STOP STICKY
USE CWM/TWRP FLASHABLE FIRMWARES

This really work. Can you write one for unlocking also?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

chasama said:
This really work. Can you write one for unlocking also?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
you have to buy unlock code, and you have to be on stock when entering code, read this http://forum.xda-developers.com/showpost.php?p=28439204&postcount=10

Samsugn galaxy s2 GT-I9100 help!!
vincom said:
you have to buy unlock code, and you have to be on stock when entering code, read this http://forum.xda-developers.com/showpost.php?p=28439204&postcount=10
Click to expand...
Click to collapse
i am running on RR Jelly bean rom 3.0.6, suddenly my comp stopped detecting my phone nd now its not detected by any comp!!
wen i connect it only charges but the phone is not recognised!! i want to install stock ics firmware plz help me!

Hey thanks for the comprehensive list. One question. I can't boot, but I can access recovery. I can access USB, however, I don't have an external sd card. What are my options, besides buying one.

zgibbyson said:
Hey thanks for the comprehensive list. One question. I can't boot, but I can access recovery. I can access USB, however, I don't have an external sd card. What are my options, besides buying one.
Click to expand...
Click to collapse
use internal if you have usb access to it

thanks

the SD card from my other phone has some folders:.android secure, data; LOST.DIR; DCIM; LGsys.....which folder should I put TWRP2.2.0 & stock firmware in ? which folder is considered A ROOT of the external SD card ? so I can boot the device.I couldn't boot it. I am newbi. please help. Thankss.

Re: [HOWTO] INSTALL STOCK ICS USING CWM/TWRP even w/a DEAD USB Port
PhoneTay11 said:
the SD card from my other phone has some folders:.android secure, data; LOST.DIR; DCIM; LGsys.....which folder should I put TWRP2.2.0 & stock firmware in ? which folder is considered A ROOT of the external SD card ? so I can boot the device.I couldn't boot it. I am newbi. please help. Thankss.
Click to expand...
Click to collapse
Don't put it in any folder, just copy to the SD card.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

I did copy TWRP2.2.0 and stock firmware zip in SD card and hold volume up+down + power button to get recovery mode but I only see pictures of phone & monitor with yellow
triangle at center.( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again.)
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
I upgraded my samsung s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)

PhoneTay11 said:
I did copy TWRP2.2.0 and stock firmware zip in SD card and hold volume up+down + power button to get recovery mode but I only see pictures of phone & monitor with yellow
triangle at center.( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again.)
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
I upgraded my samsung s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)
Click to expand...
Click to collapse
that screen is also odin/download mode
try flashing again
check odin troubleshooting section in the "install cwm/twrp" link in my sig

vincom said:
GUIDE TO FLASHING STOCK FIRMWARE FOR ATT AND ROGERS I727 SKYROCKET PHONES WITHOUT USING ODIN OR KIES ​
THIS METHOD APPLYS TO:
PHONES THAT CAN BOOT INTO A CUSTOM RECOVERY CWM/TWRP
USERS WHO CANT USE ODIN AND/OR KIES FOR WHATEVER REASON
PHONES WITH A BAD USB PORT
HAVE USB CONNECTIVITY ISSUES
MAC USERS WITH A CUSTOM RECOVERY ALREADY INSTALLED.
YOU ARE ON A CUSTOM ROM WITH USB PROBLEMS AND NEED TO RETURN TO STOCK FOR WARRANTY REPAIRS
NOTE: USING THIS GUIDE TO RETURN TO STOCK WILL PERMANENTLY UNROOT THE PHONE, BUT CAN BE REROOTED AFTER IF NEEDED.
Disclaimer: I am not responsible for your devices, follow guide at your own risk!
READ THE WHOLE POST
HOW TO ENTER INTO RECOVERY MODE, INSTRUCTIONS HERE STEP #4
GUIDE PRESUMES YOU ALREADY KNOW HOW TO INSTALL/FLASH FILES FROM RECOVERY
YOU NEED TO HAVE ONE OF THE RECOMMENDED CUSTOM RECOVERIES ALREADY INSTALLED ON THE PHONE SUCH AS CWM OR TWRP, LINKS IN THE DOWNLOAD SECTION BELOW
IN THIS GUIDE YOU WILL BE INSTALLING THE STOCK FIRMWARE ZIP FILE
OPTIONAL: INSTALLING THE STOCK RECOVERY ZIP FILE ONLY IF YOU NEED TO RETURN FOR WARRANTY, OTHERWISE NOT RECOMMENDED TO INSTALL
GETTING THE STOCK FIRMWARE TO YOUR PHONE
OPTION 1: IF YOUR ABLE TO BOOT INTO ANY ROM:
YOU HAVE A WORKING USB CONNECTION:
Download the files and transfer the files from your computer to your internal or external sdcard
YOU DONT HAVE A WORKING USB CONNECTION: USE EITHER METHOD "A" OR "B" OR "C":
METHOD A: From the phone use xda app or browser and navigate to this page and download the files directly to your device from the links provided below, then move them to the root of your internal or external sdcard, it will make it easier to find.
METHOD B: Use airdroid wirelwss appor kies air to transfer your files from your computer to your phone through your wifi connection and place them in the root of your internal or external sdcard
METHOD C: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
OPTION 2: YOUR NOT ABLE TO BOOT BUT CAN GET INTO A CUSTOM RECOVERY: USE EITHER METHOD "A" OR "B":
METHOD A: If usb port works: enable usb mount in custom recovery and transfer files to the root of your sdcard
METHOD B: If usb port doesnt work: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
FLASHING THE FILES
FIRMWARE
ENTER INTO RECOVERY MODE
PERFORM A RESET AND WIPE BOTH CACHES
INSTALL THE STOCK FIRMWARE ZIP FILE
ONLY INSTALL THE STOCK FIRMWARE(NOT THE STOCK RECOVERY ZIP FILE) THEN REBOOT THE PHONE INTO ANDROID TO CHECK IF IT BOOTS PROPERLY
YOUR GOOD LIKE THIS IF YOU JUST WANTED STOCK BACK ON YOUR PHONE
STOCK RECOVERY: ONLY RECOMMENDED IF RETURNING FOR WARRANTY REPAIR AND NEED TO SHOW FULL STOCK
TO GET THE STOCK RECOVERY ZIP FILE ONTO THE SDCARD FOLLOW THE INSTRUCTIONS FOR THE FIRMWARE GUIDE ABOVE
ENTER INTO RECOVERY MODE
INSTALL THE STOCK RECOVERY ZIP FILE, ONCE YOU DO THIS YOU WILL LOSE THE CUSTOM RECOVERY
IF YOU CANT USE ODIN THERE IS NO WAY TO REINSTALL A CUSTOM RECOVERY ON THE SKYROCKET ONCE THE STOCK RECOVERY HAS BEEN INSTALLED.
REBOOT PHONE INTO RECOVERY TO SEE IF THE STOCK RECOVERY FLASHED PROPERLY.
DOWNLOADS
MOVED TO THE 1STOP STICKY
USE CWM/TWRP FLASHABLE FIRMWARES
Click to expand...
Click to collapse
Do you have the Stock ROM for GB 2.3.6 (SkyRocket) which i can flash using TWRP? My PC doesn't recognize my Skyrocket. The only way for me is to flash using TWRP but I can't find the GB ROM for it. There's a lot of ROM of GB but it is for ODIN (with extension .tar.md5) instead.

ntd0626 said:
Do you have the Stock ROM for GB 2.3.6 (SkyRocket) which i can flash using TWRP? My PC doesn't recognize my Skyrocket. The only way for me is to flash using TWRP but I can't find the GB ROM for it. There's a lot of ROM of GB but it is for ODIN (with extension .tar.md5) instead.
Click to expand...
Click to collapse
no, why do u need gb, just flash the ics or jb roms, or if your usb is not dead go through the odin trouble shooting section in the restore to stock sticky to try to solve the connection issue, link to restore to stock is in my sig

Stock Rom Android M.
Hi, could you help me i have TWRP Custom recovery and cm12.1 android lollipop, i want to
Flash Stock Rom Android Marshmallow using TWRP is it possible using this method ,
my Device is Galaxy Tab S 8.4 wi-fi.

invalid zip
I am a mac user without access to a PC (no odin). I have TWRP recovery installed. I used android file transfer to move the stock firmware zip in the download section to the internal SD (root folder). I wiped the system and cache, then install zip - but it fails every time with "invalid zip file format". I have tried a half dozen other versions of the stock ROM from various sources and they all fail with the same error. ZIP signature verification is disabled. Just when I thought that i was doing something completely dumb and not flashing correctly at all - I tried re-flashing the lineageOS ROM i have and that worked fine. I've read a bit about unpacking and re-zipping these zips to get them to work, but that requires 7zip (which I don't have on mac). Help! am I doing something dumb or do I not have the correct zip files? I really need to get back to stock so I can activate my cellular service.

champagne_problems said:
I am a mac user without access to a PC (no odin). I have TWRP recovery installed. I used android file transfer to move the stock firmware zip in the download section to the internal SD (root folder). I wiped the system and cache, then install zip - but it fails every time with "invalid zip file format". I have tried a half dozen other versions of the stock ROM from various sources and they all fail with the same error. ZIP signature verification is disabled. Just when I thought that i was doing something completely dumb and not flashing correctly at all - I tried re-flashing the lineageOS ROM i have and that worked fine. I've read a bit about unpacking and re-zipping these zips to get them to work, but that requires 7zip (which I don't have on mac). Help! am I doing something dumb or do I not have the correct zip files? I really need to get back to stock so I can activate my cellular service.
Click to expand...
Click to collapse
AFAIK all devhosts files are bad/fake, i cant even dl my own files.
if i find them all reup to androidfilehost

Stock Rom
champagne_problems said:
I am a mac user without access to a PC (no odin). I have TWRP recovery installed. I used android file transfer to move the stock firmware zip in the download section to the internal SD (root folder). I wiped the system and cache, then install zip - but it fails every time with "invalid zip file format". I have tried a half dozen other versions of the stock ROM from various sources and they all fail with the same error. ZIP signature verification is disabled. Just when I thought that i was doing something completely dumb and not flashing correctly at all - I tried re-flashing the lineageOS ROM i have and that worked fine. I've read a bit about unpacking and re-zipping these zips to get them to work, but that requires 7zip (which I don't have on mac). Help! am I doing something dumb or do I not have the correct zip files? I really need to get back to stock so I can activate my cellular service.
Click to expand...
Click to collapse
Just use "Flashfire" and do everything from your phone no need for a computer.

Using this to flash 1.7 gb file
I have a moto g5s plus (sanders) and have installed unofficial lineage 15.0 build. before installation , I didn't took backup in TWRP. Now i am downloading stock firmware zip file. can that be installed using TWRP?

ParaSpl01t said:
I have a moto g5s plus (sanders) and have installed unofficial lineage 15.0 build. before installation , I didn't took backup in TWRP. Now i am downloading stock firmware zip file. can that be installed using TWRP?
Click to expand...
Click to collapse
you mean this zip file when you unzip it show you 5 files that you can use with Odin?

I tried and says fail , why would tarp fail to flash a stock firm ?

[Released][ROM][ODIN] ICS Stock firmware XXLQ9 repacked with CWM 6

Q. Why there is a need to repack the firmware?
A. As you may know, the stock kernel in the stock firmware has the emmc hard brick feature enabled which is believed to be the reason of 2 hard brick incident reported in the forum. And even worse, the emmc hard brick bug (mmc_erase) can be called @ anytime after the system is booted with a buggy kernel, which means that your device can immediately get bricked after the first reboot.
Q. So is it okay to flash the ROM via odin with a different bootloader (i.e. boot.img)?
A. Theoretically, yes. But the problem is that when we repack the odin package with a modified boot.img. The download counter will rise and a yellow triangle will appear on every boot.
Q. So is there any way to flash the stock bootloader but without letting it get booted?
A. Yes. There is a way to do so. After you have successfully flashed a package via odin, the odin bootloader (based on BCT partition) will invoke the recovery bootloader to finish the install process. And if you are not using the stock recovery, the process will get halted and then leave you at the recovery (CWM) screen. And then you can flash a kernel via CWM at this point.
Q. Is there anything that I should aware of?
A. Yes. Just like flashing any firmware, After flashing the ICS package, it is important for you to backup all the important files before flashing.
Guideline 1 [For people who is willing to use CWM6 (provided by Adam77Root)] (prefered way) :
1. Turn on your device and connect it to a computer
2. Place the kernel file, superuser file (which can be flashed via CWM) and new_sec_csc.zip into your internal SD card first and make sure all your important data on /sdcard are backed up (You are free to select any kernel but make sure the mmc erase part get disabled from the kernel completely)
3. Turn it off and remove the external sdcard from the device
4. Download the ICS firmware files which contains GB kernel and CWM6
5. Put the device into download mode and flash the above package via odin 3.07. Place the package file (*.tar.md5) into PDA part (You can now flash with pit file as well, however the internal sdcard data will get wiped so it is important for you to make a backup for important files before flashing) (DO NOT attemp to flash any ICS package via odin 1.85 as there is a high risk that the download process get stuck in odin v1.x series, and you have to unbrick your device with nvflash tool if error occurs)
6. After the device is restarted, it will get into recovery (CWM) mode. And the script provided by Samsung will be failed to execute due to a assert call. (Don't worry, you can execute the script again by using the patched new_sec_csc.zip)
7. Backup any important data in /sdcard (external sdcard) now if you didn't do so. You can do this @ 'Mount and storage' -> 'Mount USB devices'.
8. 'Wipe cache' and 'Wipe data / factory reset' (make sure you have all your important data on /sdcard backed up and your have removed your external sdcard device)
9. If the above stage has wiped your CWM flashable zip file as well, you can mount the device to a computer via mount menu and you can place the zip file to the phone as mass storage again.
10. Install the CWM flashable zip file (superuser, new_sec_csc.zip and your kernel file) from sdcard (For an unknown odd reason, all the packages you gonna install in this step will have signature verification error, but it is safe to proceed. Just switch off the signature verification from the menu or choose to 'Install untrusted package'.)
11. After you flashed kernel, you are free to flash anything and free to reboot now.
12. If you have used a pit file for flashing the package in odin, a message will be appeared in notification center telling you the filesystem on /sdcard cannot be recognized. Just click on it to format the sdcard and then you are free to use anything now.
13. If you are still afraid of breaking system integrity as you were not using the samsung recovery script to finish the update process, navigate to 'Options -> Back up and reset -> Factory data reset' and totally reset the device there.
P.S. If you accidentally pressed reboot the system now in CWM 6, don't worry, the system will not be able to boot into normal mode. And you can redo all the things since the beginning.
Update #1 : During testing the flash process, I have found that the repacked firmware cannot be flashed with odin 1.83. It is important to get all the ICS firmware being flashed with odin 3.07 (or 3.x sereis) instead v1.x series. Otherwise you have made a risk that your partition (PIT) table is messed up so srsly that you have to use nvflash tool to restore everything. I will tell this to cooleagle to get everyone knows of it.
XXLQ9 :
Stock package with GB kernel and CWM6 which is based on safe stock GB ZSLE6 kernel (just extract the file in the splited zip files) : http://www.mediafire.com/?uq5tg9o7nli04b2 and http://www.mediafire.com/?b5i571br0x07c38
CWM flashable package :
- Superuser CWM flashable package : http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip or Superuser-3.2-RC3-arm-signed.zip in attachments (But you will be unable to update with the 3.2 RC3 build, use 3.1.3 one if you want)
- My own kernel (flashable via CWM) : UnknownzD_Kernel_with_superuser.zip (with superuser, good for first time install) and UnknownzD_Kernel.zip in the attachments
- Patched Samsung install script (the one which failed to run) : new_sec_csc.zip in the attachments
Odin v3.07 : Odin307.zip in the attachments
Credits go to Adam77Root for his CWM image and someone(!?) who has uploaded odin 3.07 to xda forum. Will try to check his name later.
Short change log about my kernel (The longer one will get posted when I start another thread for it) :
4 IO scheduler added
Voodoo sound patch added
Full fp calculation based on hardware fp opcode only (which should makes the device consumes less energy while providing the same performance level)
MMC erase function tootally disabled
Default.prop get modified to increase the performance
Based on ICS 3.x kernel src code released by Samsung
If you gonna use my kernel, please make sure that you have efs_backup.img backed up safely after flashing my kernel package, as it contains your device's IEMI info, which can save you from future disaster as you can use the unbrick tool with it. You can backup the efs_backup.img by :
1. Flash my kernel in CWM
2. Mount and storage -> Mount USB devices
3. Copy the efs_backup.img from the sdcard to your own computer (it is vital for you as you can use the unbrick tool later)

Now I am stuck @ finding a proper file host to upload the files.

waiting for this!

Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2

Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.

coldbeermt said:
Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2
Click to expand...
Click to collapse
You can root it on your own with superuser zip file. And busybox binary is not yet dropped into /sbin/ as I believe it comprise the system integrity back in GB kernel. Init.d will be supported in near feature. All the things that I changed is just inside the kernel and recovery and provide a safe envrionment for user to continue to flash their own desired kernel. Nothing more.
For kernel development, I will make a separate thread in dev section later.
Sorry I have to postpone the release as I have to repack everything with the nordic release (XXLQ9) now.

Ok, I'm sure you know I asked just for general information. I supposed your answer yet
Anyway, I'm sure its a good job. With the new version (nordic) I suggest you to upload releases to dropbox our something easier. Anybody could make a mirror in other servers later :thumbup:
Sent from an GT-I9103 with ICS and Tapatalk 2

UnknownzD said:
Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.
Click to expand...
Click to collapse
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.

xlm13x said:
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.
Click to expand...
Click to collapse
Yea I just saw the PM, it is really useful for me tbh. Thanks for your help.

Okay after many hours of testing, I am happy to release the ICS XXLQ9 package with GB kernel and CWM 6 (based on the one posted by Adam77Root) that should be able to let you flash your own kernel after flashing it. Download links will be up shortly.

So after 5~6 times of srs bricking, I finally get it working correctly after working overnight.

Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.

UnknownzD said:
Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.
Click to expand...
Click to collapse
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??

vipul12389mehta said:
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??
Click to expand...
Click to collapse
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.

Nice work! Thanks!
Sent from my GT-I9103

nedooo said:
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.
Click to expand...
Click to collapse
Basically the things you mentioned above are included in the package / guide already. Tbh this should not be dangerous. But I want more people to test it first because last time when I released the GB kernel, a lot of people complained about the things that do not occur on my phone.
oh btw about the zero free space in system space, I believe it is just a bug in the filesystem. You can fix it easily by using e2fsck, which is actually included in my kernel script.

This is just explanation about staying stock. Your work and effort is well above this. Thanks in name of all flash addicts

So after many times of tests, I guess it is safe to use the build already, just make sure you have everything backed up before updating (actually you should do this for any fimrnware update). If you have found any problem, just report the problem here. I will repack every stock firmware following the same method until Samsung acknowledge that the MMC_CAP_ERASE is removed from stock kernel.
If you have found your device bricked after using any ICS update (for example, unable to flash the device any more via odin protocol), please let me know via pm please so that I can guide you to fix your phone in IRC.

pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
Click to expand...
Click to collapse
When you are updating the ROM from GB to ICS better to wipe data or else you face some Force Closes and other issues....

pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
"I like spelling my name backwards"
Click to expand...
Click to collapse
The wiping cache part is actually a part of odin download process. Everytime when you flash a new firmware in odin, the odin bootloader will invoke some scripts stored in /cache within recovery mode, and then wipe out these scripts / the whole partition as they are no longer needed.
However the wiping /data part is actually an essential part of firmware update and you should do it on your own if you are using CWM based firmware. This is because if you flash a firmware via odin, the data partition gets wiped after the device rebooted.
tbh it should be safe if you didn't wipe the /cache partition but not for the /data partition. Just some usls scripts and T9DB left behind in /cache. But incompatible binaries may still stays in /data if you didn't wipe it.
Sent from my GT-I9103 using xda app-developers app

Want to use CM for the 1st time

I'm still on official firmware (15.3.A.1.17). Now I want to use the best custom rom (Kitkat). To do so, I have checked most of the posts in this forum. But, I'm confused about where I should start from. Could anyone please tell me the whole process in brief? May be names of the steps? I also want to know about the bugs in this rom (if any). A lot of thanks in advance!!

1. root your device
2. backup the TA
3. unlock the bootloader
4. flash the stock firmware.tft(/.ftf - i don't remember right now what the extension was) via FlashTool
5. root the device again
6. flash the boot.img file (from zip of the rom that you downloaded)
7. do a full wipe from recovery
8. install the rom.zip and gapps.zip from recovery
9. reboot your device and enjoy!
I just tried to show you an overall view. I know that you maybe don't understand some of this, but these are the steps you should take. there's a thread for every step.. you'll find them. (^_-)
Sent from my Phone using Tapatalk.

[ROM] Pantech SKY Vega Racer 3 IM-850K (and L/S) ROM based on Latest Stock Kitkat

Instead of rooting, installing CWM and then installing the ROM, it’s better to just:
• Copy the downloaded ROM to Internal Memory or SDCard (modem file also for L/S versions)
• Download universal fastboot/adb drivers (link provided)
• Turn Off the phone, Press VolUp+VolDown and press power until you are in the bootloader
• From there select Fastboot
• Browse for drivers when prompted and install them (you may have to forcefully install them)
• Download recovery (link provided) and run CWM 6.0.4.8.bat (recommended) or TWRP 2.8.6.0 (may not work well with stock based roms) and the phone should boot straight into recovery
• Factory Reset, Wipe Cache and Dalvik
• Formatting System, Data and Cache is up to you
• Install ZIP and when you are about to reboot it’ll ask to disable flash recovery, select NO to keep the stock recovery as you can boot into custom recovery directly anyways
• Stock recovery is a better option for factors resets and adds a little more security of data in case phone is lost/stolen
• Doesn’t matter if you are coming from AOSP or any other ROM. This ROM also installs Modem, Stock Recovery etc…
Enjoy the stock KitKat sweetness 
NOTE: You may also try installing the ROM on L/S versions but make sure to install Modem file right after installing the ROM. Links for modem files are also provided here for convenience
Here are links to download:
1. Fastboot/ADB Drivers
http://forum.xda-developers.com/attachment.php?attachmentid=3446458&stc=1&d=1440144523
2. Recovery
https://drive.google.com/file/d/0B8_wtN-YXTxndkhkZ2QwcTR1d2c/view?usp=sharing
3. ROM
https://drive.google.com/file/d/0B8_wtN-YXTxnTGRBWnpyZmlzd1E/view?usp=sharing
4. Link Modem: 850L
https://drive.google.com/file/d/0BxveGwot73rCYmZlem5JbXJDQkE/view?usp=sharing
5. Link Modem: 850S
https://drive.google.com/file/d/0BxveGwot73rCTkV1amFpVHVJR1k/view?usp=sharing

[GUIDE][20-MAY-2019]HOW TO FLASH Z010D ROMs on Z010DD (8.1 and 9.0 ROMs).

This guide is specifically aimed for Z010DD users who want to flash custom ROMs:​If you want to stay on stock and only wanna flash TWRP and root the Stock ROM, please skip this thread and refer to @jide1 's guide here instead: https://forum.xda-developers.com/as...ot-asus-zenfone-max-zc550kl-qualcomm-t3652518​
Things to be noted beforehand:
1. Make sure you are on the latest/final stock rom/firmware
2. Need Unlocked bootloader (Linked below, install the apk and follow the steps)
3. Take backup of all of your data from the internal storage. (To avoid depression if accidentally wiped your precious data)
4. Minimal ADB and Fastboot (Thread Linked below, Download from there and follow on-screen steps).
Steps:
A. To flash TWRP:
1. Once you have unlocked the bootloader, download 'minimal adb and fastboot zip' and PBRP zip(extract img from it).
2. Boot into fastboot by switching off the device, then POWER + VOLUME 'UP'. (You'll enter CSC ode screen, which is fastboot so don't worry)
3. Place the recovery image into the fastboot folder and open a command window there.
4. Connect your device, then type 'fastboot devices' and Enter, just to verify if your device is shown.
5. type: fastboot flash recovery recoveryname.img
THE NEXT STEP IS IMPORTANT, Pay Attention.
6. Now REBOOT Directly to twrp by holding POWER + VOLUME 'DOWN'. Don't boot into system else stock recovery will get restored.
B. Preparing for Flashing ROMs:
Once you have booted to twrp successfully, you will need to 'format' all the partitions, which includes:
System, Data, Cache, Dalvik/ART Cache, & Internal Storage.
HERE YOU WILL LOSE ALL OF YOUR DATA, YOU HAVE BEEN WARNED ALREADY SO, yeah.
Click to expand...
Click to collapse
1. In TWRP, go to WIPE -> ADVANCED WIPE;
2. Select the above listed partitions and then SWIPE TO WIPE.
Note: You will notice a partition called 'ASDF' ,wipe/skip, doesn't matter.
3. Come back to home, go to REBOOT -> RECOVERY
C. Flashing ROMs:
1. Download the ROM, Patch, and Kernel zip (Linked Below).
2. Flash them in the mentioned order.
3. Flash Opengapps (if needed) (Nano Gapps recomended).
4. Reboot.
(NOTE: FOR MAGISK, FLASH IT 'AFTER FIRST BOOT ONLY', AND IF FLASHING ZIP NOT WORKING, THEN see POST #3)
Bugs and Notes:
1. Notification LED doesn't BLINK when a notification arrives, it stays on (colors are correct though).
2. VoLTE is broken on pie roms (ignore the volte logo), stick to Oreo if you want VoLTE. (LTE data works fine).
3. Reboot Sometimes get stuck in black screen, its RANDOM, LONG Press the power button for 15 secs instead if that happens.
4. If any ROM contains 'Always On' functionality, disable it as the feature doesn't work properly. (Ambient display has no issues)
Links: Refer POST #2 .
Credits:
@SakilMondal for roms.
@YaAlex for kernel and patch for Z010DD.
Myself for testing.
Created 2019-04-22
Last Updated 2019-05-20

Links:
ROMs: https://sourceforge.net/projects/zenfone-max-updates/files/Z010D/ (Please flash the latest ones only, don't use old ones)
Patch (link updated): https://anonymousfiles.io/3WLplRtD/
Kernel (link updated + new kernel update): https://anonymousfiles.io/m4oKP6wL/
TWRP Recovery (Image file, Flash via fastboot): https://drive.google.com/file/d/1txHT0vRNo0gTMkD0Sb5kpuQQT0dAiphH/view
ASUS Official Bootloader Unlock Tool for 8939 Devices: http://dlcdnet.asus.com/pub/ASUS/Ze...513.74708998.1502054577-2083321676.1502054577
Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790

Troubleshooting:
Instructions for Magisk:
1. Extract boot image from the rom zip
2. Go to Magisk Manager app
3. Tap 'Install' next to 'Magisk is not installed' line.
4. Tap 'Select and patch a file'
5. Navigate to the extracted boot image. It will now create a new boot image and save it in mentioned location.
6. Reboot to recovery, Flash the Boot image + KERNEL zip.
7. Reboot to system.
To fix CTS Mismatch in Magisk:
Open /system/build.prop, replace the line 'ro.build.fingerprint=' with:
Code:
ro.build.fingerprint=asus/WW_Phone/ASUS_Z010_2:6.0.1/MMB29P/13.8.26.80-20161230:user/release-keys
Open /system/vendor/build.prop , replace the line 'ro.vendor.build.fingerprint=' with:
Code:
ro.vendor.build.fingerprint=asus/WW_Phone/ASUS_Z010_2:6.0.1/MMB29P/13.8.26.80-20161230:user/release-keys

Patch is required for sd410 devices??

koushik99 said:
Patch is required for sd410 devices??
Click to expand...
Click to collapse
Nope, patch is only for DD.

Guide has been updated. Please check.

unable to flash GAPPS
Hai , i got a problem , phone shutdowns after flashing GAPPS (opengapps) , i tried Many RAMS(DOT OS, lineage-16.0-20190514-Z010D, BootleggersROM-Pie4Z010D.4.1-Stable-Unshishufied-20190421-170442 ,RR-P-v7.0.2-20190505-Z010D-Unofficial ) , without GAPPS Flashing it is , ROM working good , please let us know how to fl

I cant turn off the phone with pie,
i need to go in recovery first to power off otherwise after a while it turns back on
is it a known bug?

PRASAD.ASRS said:
Hai , i got a problem , phone shutdowns after flashing GAPPS (opengapps) , i tried Many RAMS(DOT OS, lineage-16.0-20190514-Z010D, BootleggersROM-Pie4Z010D.4.1-Stable-Unshishufied-20190421-170442 ,RR-P-v7.0.2-20190505-Z010D-Unofficial ) , without GAPPS Flashing it is , ROM working good , please let us know how to fl
Click to expand...
Click to collapse
Looks like you're using aroma gapps..
Use micro gapps or below. Here everything works fine.

ihatebarrels said:
I cant turn off the phone with pie,
i need to go in recovery first to power off otherwise after a while it turns back on
is it a known bug?
Click to expand...
Click to collapse
In both oreo and pie, for both z010d and dd, reboot and shutdown is an issue
It doesn't happen everytime, its random, and no fix is found yet.

Is it working on asus zenfone max 2016 sd 615?

Can anyone give me the updated link for the dd-fix-r5.zip and GUNMetal-R3.zip files

james_imch said:
Can anyone give me the updated link for the dd-fix-r5.zip and GUNMetal-R3.zip files
Click to expand...
Click to collapse
I just saw that the link was no longer working (would have been better if you pointed out that first instead)
Anyways,
Link is updated, check again (kernel is updated,patch remains the same).

Kaustav365 said:
Is it working on asus zenfone max 2016 sd 615?
Click to expand...
Click to collapse
Hope you have read the OP properly
This thread is only for sd615/Z010DD/MSM8939, and its clearly mentioned.

TechNova said:
I just saw that the link was no longer working (would have been better if you pointed out that first instead)
Anyways,
Link is updated, check again (kernel is updated,patch remains the same).
Click to expand...
Click to collapse
PBRP Recovery (flashable zip) link is also not working. Please update it.

james_imch said:
PBRP Recovery (flashable zip) link is also not working. Please update it.
Click to expand...
Click to collapse
Done,
Removed pbrp and now Twrp link posted.

TechNova said:
Looks like you're using aroma gapps..
Use micro gapps or below. Here everything works fine.
Click to expand...
Click to collapse
Hey! I am also facing the same issue. I tried the nano version of Gapps on my Asus Zenfone Max Z010D and my phone is still crashing it keeps restarting and then automatically turns off. Is there any issue to fix this?

unable to flash roms it shows up no digest found or invalid zip or update error 7
please help how do i find correct rom for sd615 8939

Eric0000 said:
unable to flash roms it shows up no digest found or invalid zip or update error 7
please help how do i find correct rom for sd615 8939
Click to expand...
Click to collapse
I too facing same problem

Unlocking the apk no longer works