Related
Hello Guyzzz!!!!!
A Great Newzz for ALL!!!!! First the recovery was not compiled by me!
But NOW I am BACK with a FULLY WORKING RECOVERY AND FULLY COMPILED BY ME :good:
We have now a FULLY WORKING CLOCKWORKMOD RECOVERY v5.0.2.8.
The CLOCKWORKMOD RECOVERY is TESTED on :-
1. LG OPTIMUS 3D MAX P725
2. LG OPTIMUS 3D MAX P720H
I HELD NO RESPONSIBILITIES FOR BRICKED PHONES. YOU MAY TRY ON P720 BUT AT YOUR OWN RISK.
Credit Goes to :-
1. I, Me and Myself ( For taking the initiative,compiling testing and removing all bugs )
2.. Cynogenmod for the SOURCES.
3. P720H tester ZOOM.
According to me, the CWM RECOVERY is fully working.
HERE ARE THE STEPS TO INSTALL THE CWM RECOVERY :-
Download the CWM RECOVeRY FINAL.zip from the link given below :
http://www.mediafire.com/?p59d9ppjlhkcp67
Copy the cwm5.0.2.8.img on the ROOT OF THE SDCARD not the External SDCARD ( Root of SDCARD means not in any folder )
The BIGGEST REQUIREMENT IS YOUR OPTIMUS 3D MAX should be ROOTED!!!
Now download ANY TERMINAL EMULATOR from the GOOGLE PLAY!!!!!
You can try this :-
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
And install it.
Type the following commands in TERMINAL EMULATOR :-
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/cwm5.0.2.8.img of=/dev/block/mmcblk0p6 bs=4096
Once complete.
Turn off your phone.
1st hold 3d key then volume down button and at last power button.
Keep holding till the LG LOGO appears and leave when it appears.
You will enter the CWM Recovery
Proof of the Recovery :-
Worked like a charm! First I couldn't get the # to appear (the phone WAS rooted) so I just used the terminal emulator you specified, and that solved it.
lordasphyxia said:
Worked like a charm! First I couldn't get the # to appear (the phone WAS rooted) so I just used the terminal emulator you specified, and that solved it.
Click to expand...
Click to collapse
Happy to help you.
"HITTING THANKS WILL ENCOURAGE ME MORE":good:
Eklovya said:
IT TOOK MORE TIME TO DEVELOP THIS RECOVERY THAN THE TIME YOU WILL TAKE TO JUST " HIT THANKS".
Click to expand...
Click to collapse
dude you are not developed this recovery, it's created by me, you only unpacked my recovery using kitchen , that not call develop
Where did i mentioned that I DEVELOPED???
I clear mentioned that you compiled and i removed all bugs...
Sent from my LG-P725 using xda premium
Thread for this exists from original dev
http://forum.xda-developers.com/showthread.php?t=1889468
Thread closed
Edit: Thread reopened for a newly compiled version
HELP!!!!
After downloading an update from LG it allways boots to recovery!!
TommyX235 said:
HELP!!!!
After downloading an update from LG it allways boots to recovery!!
Click to expand...
Click to collapse
Try doing a factory reset.!!!
Sent from my LG-P725 using xda premium
tryed everything .. factory reset .. i have a backup from my original rom.. when i restore it i also boot into cwm.
i can start sw update mode (vol +) but either there nor in cwm i have adb access..
i tryed kdz but i don't know the dev type .. i tryed TI / 3GQCT etc. the program crashes
its breaking my heart .. i have this device the first day and now its broken!
ARRGG!!!
I still have the backup of the mmcblk0p6.backup
can i do anything with it?
maybe it is possible to install it via zip in cwm?
TommyX235 said:
tryed everything .. factory reset .. i have a backup from my original rom.. when i restore it i also boot into cwm.
i can start sw update mode (vol +) but either there nor in cwm i have adb access..
i tryed kdz but i don't know the dev type .. i tryed TI / 3GQCT etc. the program crashes
its breaking my heart .. i have this device the first day and now its broken!
ARRGG!!!
I still have the backup of the mmcblk0p6.backup
can i do anything with it?
maybe it is possible to install it via zip in cwm?
Click to expand...
Click to collapse
Install LG SUPPORT TOOL IN PC.
KEEP YOUR PHONE IN DOWNLOAD MODE.
CONNECT TO PC.
OPEN LG SUPPORT TOOL.
IN TOOLS SELECT RECOVER PHONE.
INPUT YOUR IMEI.
AND WAIT FOR THE RECOVEY PROCESS TO FINISH.
ALL WILL BE DONE SAFELY AND YOU WILL GET THE PHONE WORKING
Sent from my LG-P725 using xda premium
this damn tool doesn't recognize my IMEI also when i enter my device type p720 & Serial a small window pops open showin my device and my serial .. when i click ok .. another popup telling .. please check your device or something.
---------- Post added at 08:36 AM ---------- Previous post was at 07:42 AM ----------
also why is adb not working?
Is there a way to get it workin in CWM?
In CWM in section advanced you can do show log.
CWM-based Recovery v5.0.2.8
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=omap4430
ro.revision=7
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:checking for extendedcommand...
I:Skipping execution of extendedcommand file not found...
Does this mean something?
Also this lg Tool only worked for me when adb also was working.
TommyX235 said:
this damn tool doesn't recognize my IMEI also when i enter my device type p720 & Serial a small window pops open showin my device and my serial .. when i click ok .. another popup telling .. please check your device or something.
---------- Post added at 08:36 AM ---------- Previous post was at 07:42 AM ----------
also why is adb not working?
Is there a way to get it workin in CWM?
In CWM in section advanced you can do show log.
CWM-based Recovery v5.0.2.8
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=omap4430
ro.revision=7
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:checking for extendedcommand...
I:Skipping execution of extendedcommand file not found...
Does this mean something?
Also this lg Tool only worked for me when adb also was working.
Click to expand...
Click to collapse
is it somehow possible to activate nable adb access in CWM 5.0.2.8?
or can i flash a zip to do this?
Again .. i can enter S/W Upgrade Mode
There i only see S/W Upgrade
Please wait
while upgrading....
(NO ADB ACCESS! But the Tool recognize the phone but won't let me start the sw upgrade.)
In CWM i can mount & unmount storage and flash zip files or backup / Restore.
BUT no ADB access and Restoring the backup i made doesnt work either)
What breaking my head is that the LG Update must had set a flag to boot into recovery after i downloaded it so mindless.
Since then i stuck in cwm bootloop. There mus be a way to reset this flag. Somehow!!!)
Its over .. i flashed CWM-Loop-DeLooper -> now i stuck @ LG Logo.. also vol+ to enter S/W Upgrade not working anymore. Now its bricked! ARGH!
TommyX235 said:
is it somehow possible to activate nable adb access in CWM 5.0.2.8?
or can i flash a zip to do this?
Again .. i can enter S/W Upgrade Mode
There i only see S/W Upgrade
Please wait
while upgrading....
(NO ADB ACCESS! But the Tool recognize the phone but won't let me start the sw upgrade.)
In CWM i can mount & unmount storage and flash zip files or backup / Restore.
BUT no ADB access and Restoring the backup i made doesnt work either)
What breaking my head is that the LG Update must had set a flag to boot into recovery after i downloaded it so mindless.
Since then i stuck in cwm bootloop. There mus be a way to reset this flag. Somehow!!!)
Its over .. i flashed CWM-Loop-DeLooper -> now i stuck @ LG Logo.. also vol+ to enter S/W Upgrade not working anymore. Now its bricked! ARGH!
Click to expand...
Click to collapse
Can you come on chat? So that i can help you!!
Sent from my LG-P725 using xda premium
can this tutorial work on ICS su870?
joseph168 said:
can this tutorial work on ICS su870?
Click to expand...
Click to collapse
Nop this will not work. As the bootloader is locked for su870
Sent from my LG-P725 using xda premium
LG P725 CWM Problem
Hi guys need help, i installed this cwm recovery with no problems, when i start it i see menu, can move up and down but i can`t launch anything. I read at different sites that i should to use shutdown key or 3d key but they don`t work. Also i install newer version 6.... but there are this problem too. I have LG 3D max (P725) version o firmware v10f.
Andrelius1 said:
Hi guys need help, i installed this cwm recovery with no problems, when i start it i see menu, can move up and down but i can`t launch anything. I read at different sites that i should to use shutdown key or 3d key but they don`t work. Also i install newer version 6.... but there are this problem too. I have LG 3D max (P725) version o firmware v10f.
Click to expand...
Click to collapse
use volume keys to move up and down.
and capacutive keys to select
Sent from my LG-P725 using xda premium
CWM problem
Eklovya said:
use volume keys to move up and down.
and capacutive keys to select
Sent from my LG-P725 using xda premium
Click to expand...
Click to collapse
Thanks a lot! Its strange that in any instruction not says this way of use CWM, i read a lot differents cwm instructions, but the always the same - use power off key ot use 3d button.
Who don`t how to use CWM menu :
"properties button" - up
"home button" - down
"back button" - back
"search button" - ENTER
Cannot select options in cwm
Hi Eklovya,
Brilliant job done!!
I have successfully rooted and installed CWM following your method.
However, when i go boot to CWM, I can use the volume buttons to highlight the options (I wanted to backup), but I am not able to select the options. i tried the power button and the 3D button, no go. What do i do?
I just exchanged my P920 and got myself this P725 today!!!
schubeir
EDIT: my bad!!! found the solution in the post just above!!!!
schubeir
(possibly long post , I will try to make a post at least a little fun to read).
Guys, I humbly come before you, kneeling and desperate, trying to solve my problem .
I've serarched XDA and a lot (!!) of others forums and comunities to revive my P720H (LG optimus 3D Max in Brazil).
I am not a complete noob in custom firmwares for Android, but this time, the LG phone gave me a hell of a headache (and almost a divorce, for the 3 days going too late to bed, trying to solve it).
I will explain what happened and what I've already tried to do and the results.
Causes:
I've tried to install ClockworkMod in my P720H because it still was in Android 2.3.6 (I think).
I've successfully rooted the phone using this thread: http://forum.xda-developers.com/showthread.php?t=1886057 with the SuperSU app on GooglePlay.
When I asked CWM app to reboot in recovery mode (to wipe things and install the .zip file on the sdcard root) things got bad.
My phone could not get passed the LG logo anymore.
So far we have a cause: CWM app did something to the phone. I am not able to boot the recovery menu nor to pass the LG logo on the screen.
Over the communities we may find that it's a common issue.
It is important to say that I am able to enter the 'S/W updating' state. When I connect the phone to the computer, holding VOL+ and placing the battery, I got the S/W screen.
What can I do? In several posts (even here in xda) we may find 3 or 4 different solutions to restore the phone. I think I've already tried everything, but I am sure that the steps became fuzzy in my read and I mixed the solutions in the end.
Drivers:
- I have already the drivers installed: When I connect the phone (with or without battery and with or without vol+ pressed) my Device Manager recognizes everything. I don't have any component marked as 'unknown device' or with exclamations points or anything. This is a good thing, I guess. I had to install more than one thing to solve every driver problem. I don't remember exactly, but I think that the LGDriver-something and the omap4430 something too.
Solutions:
- I have tried the LG Support Tool and so far it appears to be the closest to a solution that I've reached. With the phone connected (in S/W mode or no), I insert the IMEI and the software recognizes the model and starts downloading something (500mb approx.). But after decompressing, during the installation phase, it gets stuck at 4%. I waited for more than 20min and still got nothing better than 4%. It appears to be a common issue too.
- The LG_FlashTool (version 1.2) does not work either. In fact, it does not even recognizes the phone. I've changed the COMport to 41 (according to some guide) on Windows Device Manager and chose the port 1 on LGFlashTool. Even after selecting the kdz, bin and fls files, the software does not connect to the phone. I don't have a screenshot here, but I've seen here in xda that the software displays the model of the phone on the top and a READY message on port 1. Mine does not do it.
- KKDZ_FW_UPD_EN: I've tried this one but it does not even start working. The interface is not that good, so I don't know where I may be failing. I need to 'read phone information' or not? What do I have to chose on each combobox? How to proceed?
And why the hell is there so much .exe on this thing? Do I have to run a apache server to do something?!
- OMAP4BOOT: This one connects to the phone and works, I think. But I don't know its purpose. It's just to place the phone on 'S/W updating' mode? If so, it's useless, because I can enter it easily. If no, maybe I am missing something. Either way, I don't have a version for the P720H. If I remeber correctly, it proposes P999, P760, P870, ... I choose P760 to test it and it works (apparently, again).
- SmartFlashTool: I don't remember if I have already tried this one. As I said, it was too much already.
- NVFlash: I've found it only to G2X, so I didn't know if I should try forcing it to my model. I can give it a try if you help me.
Other softwares and downloads:
KDZ:
- V10B_00 and V1A_00: found today and downloaded for my model and country (will try to extract things and use it later).
- LG_P725_V10F_00: I was using this one until yesterday, because I didn't have the one to P720H
- LGP700AT-01-V10d-232-03-SEP-11-2012+0.dz : Found in an indian repository of some kind of LG data leak. Apparently is useless. DZextract gave me nothing.
DLL: LGP720_20120330_LGFLASHv1377: Needed in some of the softwares above (LG FLashTool? I don't remeber).
BIN and FLS: LGP725_LG_P725_V10F_00_AP.bin and LGP725_LG_P725_V10F_00_CP.fls, extracted from LG_P725_V10F_00.kdz. I don't know, but I should try extracting these from the V10A_00, because apparently is the correct one for my model/country (I am not in my house right now).
Well... :crying:
tl;dr version:
I am facing a LG logo boot loop in P720H. I've tried to reboot CWM in recovery mode but it didn't work. I've tried several approaches but I don't even know what is the point of each one. I found that this is the best topic to use, because is one of the fews that covers the P720H.
I have all those softwares and almost 5gb of downloaded material (kdz, img, bin, exe, ...) but I don't know what I am supposed to use.
In the end, I want my P720H in android 4.x if possible. If not, I just want the crap 2.3.6 again. :crying:
Can you help me? I am not a total noob in custom firmwares and roms, and I am willing to pass all the information that I can :fingers-crossed:
Hello there,
Today I will teach you how to make a full backup of your Spreadtrum phone !
This tutorial may also work on several other phones.
CWM can make a nearly full backup of your Spreadtrum, but it's not enough unfortunately.
Android is compartmented in 4 main partitions. You have theses partition:
* boot - It contains the Linux kernel
* System - It contains Android
* Recovery - It contains the recovery system, CWM if you installed it.
* DATA - It contain your personal datas, and should not be published online if you share your backup online.
But Android is one thing, your phone also have a lot of bios, firmwares, and bootloaders. Theses are not saved by traditional backup utilities such as CWM.
Theses partitions includes:
* UBoot - Very important, this thing is the low level bootloader. It starts Linux !
* Modem Firmware - used to dial with your GSM provider
* DSP Firmware - Make video playback smoother using DSP resources.
* NV - It's some kind of encryption key with some low levels parameters. Very important !
* Lots of misc stuffs - Like the boot logo, the kernel panics logs (record the boot-up errors to help the debugging process), etc ...
* Lots of important misc stuffs - For example what start-up the device even before handing the phone to Uboot.
This thread will cover a new way to backup your device, working "only" on rooted Spreadtrum devices.
With this you can recreate your original firmware file, and then rescue your phone even on the worst case you can find. (And help those with the same phone as you but have made a big flashing mistake)
So first, you will need to root your device. It may be simple or difficult, it all depends of the device you have. The instructions on how to root your device are here: http://forum.xda-developers.com/showthread.php?t=2165554
When you are rooted, you will have to install the Spreadtrum drivers if it's not already the case and log into your device with ADB.
You can download the drivers here:
http://www.mediafire.com/download.php?c5nf3rlhxmxhu4x
http://www.mediafire.com/download.php?2tyg0k2xp3ejgyg
You can download ADB and learn how it work here: http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Then you will have to tell adb what phone to use. By that I mean adding the PCI ID to a text file to tell adb that this peripheral is compatible.
The Spreadtrum PCI ID is 0x1782
add this line to "Your user directory/.android/adb_usb.ini"
Code:
0x1782
So when you are ready to go, you have to download this file: http://www.mediafire.com/download.php?y6wmegkc22gkr97
Then with adb, push it on your device with this command:
Code:
adb push backuptools.tar /data/local/tmp
Now we will extract the tools with this command:
Code:
adb shell su -c "tar -xvpf /data/local/tmp/backuptools.tar"
And now, let's start the backup process:
Code:
adb shell su -c "./mkbackup.sh"
and here we go, just wait a while and every partitions on your phone will be saved in the backup directory on the sd card !
You will never have to backup this way again as those partitions are read only, if you don't do crazy things they will never change. But if you want to make another backup I suggest you go with CWM (read this page if you don't have it: http://forum.xda-developers.com/showthread.php?t=2165554).
Please do another backup with CWM even if everything as gone right with this method. Just to double check !
PS: if CWM does not work for you, you just have to send me your boot.img file from your backup and I will make one compatible with your phone.
To restore your backups you will also need to have CWM, you also can use ResearchDownload if you manage to entirely brick your phone or if any attempts to make a CWM recovery fails. I will have to do a tutorial about that too.
Thanks a lot :good:
this is my boot.img after a full backup :www .mediafire.com/?gmnm65rn65b28c3
i need a CWM image for my GT-I9300 clone.
all the best.
monster-exodia said:
Thanks a lot :good:
this is my boot.img after a full backup :www .mediafire.com/?gmnm65rn65b28c3
i need a CWM image for my GT-I9300 clone.
all the best.
Click to expand...
Click to collapse
Hi,
Can I have the exact name of your device ? (it must be in the battery compartment)
Did you tried all the CWM already in the rooting tutorial ? (I added one this morning)
If none of them work, I made this recovery with the boot.img you provided: http://www.mediafire.com/download.php?aj2nman38j5cfip
Please don't forget to tell me what CWM work for you so I can add the name of your phone on the tutorial.
@ElectronikHear
phone model (in battery) : N9300
phone model : (system info) GT-I9300
Build number : MT6515M_C909_HT_V14
cpu hardware : SP6820A
..........
I never tried ... firslty how to to flash CMW recovery ?
thanks in advance.
deleted
monster-exodia said:
how to to flash CMW recovery ?
Click to expand...
Click to collapse
Well it's explained in the rooting tutorial.
If your phone have Fastboot you can flash using it. If you don't you can use the Spreadtrum flash utility called ResearchDownload.
Everything is here:
http://forum.xda-developers.com/showthread.php?t=2165554
As your phone is already rooted it will be a lot more simple to flash using "dd" or some android flashing utilities. Actually it doesn't work that way on theses phones, sorry ... So just do as the rooting tutorial explains.
Hi, I'm succesfully rooted my phone with the "rooted system partition image" method, but none of the CWM images work, so I would be grateful if you can send me the recovery image.
Device Info:
Phone model (in battery) : S6500-TV
Phone model : (system info) S560
Android Version: 4.0.3
Baseband Version: DM_BASE_12A_W12.32|sc8810_modem|08-9-2012 16:47:10
Kernel Version: 2.6.35.7 [email protected] #3
Software Version: T162_JYY_G2_P2_1_W1220P12_DNY_V0.8.1_20121015
Hardware Version: 1.1.0
boot.img : www .dropbox.com/s/ka43sd45em9lu9k/mtd9.boot.img
Thanks in advance.
monster-exodia said:
I never tried ... firslty how to to flash CMW recovery ?
thanks in advance.
Click to expand...
Click to collapse
Don't even try!
Backup first.
janzlev said:
Hi, I'm succesfully rooted my phone with the "rooted system partition image" method, but none of the CWM images work, so I would be grateful if you can send me the recovery image.
Device Info:
Phone model (in battery) : S6500-TV
Phone model : (system info) S560
Android Version: 4.0.3
Baseband Version: DM_BASE_12A_W12.32|sc8810_modem|08-9-2012 16:47:10
Kernel Version: 2.6.35.7 [email protected] #3
Software Version: T162_JYY_G2_P2_1_W1220P12_DNY_V0.8.1_20121015
Hardware Version: 1.1.0
boot.img : www .dropbox.com/s/ka43sd45em9lu9k/mtd9.boot.img
Thanks in advance.
Click to expand...
Click to collapse
Hi there,
Here is your new recovery: http://www.mediafire.com/download.php?iahnncpjhm44etn
Please tell me if it works so I can add it to the rooting tutorial ^^
Thank you very much !
Not working, after flashing the recovery, the phone enters into a boot loop.
Anyway thank you.
janzlev said:
Not working, after flashing the recovery, the phone enters into a boot loop.
Anyway thank you.
Click to expand...
Click to collapse
A boot loop ?
You mean the recovery is looping ? and if you try to boot as normal everything working ok ?
I don't know what has gone wrong ... Where did you find your boot.img ? Did you extract it from the rom as the tutorial said or extracted from a .pac file ?
Have you flashed it with fastboot or with ResearchDownload ?
ElectronikHeart said:
A boot loop ?
You mean the recovery is looping ? and if you try to boot as normal everything working ok ?
I don't know what has gone wrong ... Where did you find your boot.img ? Did you extract it from the rom as the tutorial said or extracted from a .pac file ?
Have you flashed it with fastboot or with ResearchDownload ?
Click to expand...
Click to collapse
Recovery does not start, normal boot enters into a boot loop, the boot.img is extracted from the rom as in the tutorial.
Flashed with ResearchDownload.
janzlev said:
Recovery does not start, normal boot enters into a boot loop, the boot.img is extracted from the rom as in the tutorial.
Flashed with ResearchDownload.
Click to expand...
Click to collapse
That's weird, really weird. Because the recovery partition is not involved in the normal boot procedure. So flashing a new recovery should not harm in any way the normal boot procedure.
I really don't know what have brought your phone in such state I'm afraid.
Maybe you should try to flash the recovery again. and see if everything is the same.
As the recovery is not involved in the normal boot process, it surely will not change anything, but as you have tried the over ones (CWM I mean), and that have not screwed your booting process, you may try to flash one of the non working ones again (but known for sure to not harm the boot process) to see if it work again.
Have you used the same FDL set as when you flashed the system partition and the over CWM ?
It's a good thing you have the full backup on your hand. Because you may surely be able to recover from that. I just have to make a tutorial about flashing the backup with ResearchDownload and explaining what file goes where from the backup.
ElectronikHeart said:
That's weird, really weird. Because the recovery partition is not involved in the normal boot procedure. So flashing a new recovery should not harm in any way the normal boot procedure.
I really don't know what have brought your phone in such state I'm afraid.
Maybe you should try to flash the recovery again. and see if everything is the same.
As the recovery is not involved in the normal boot process, it surely will not change anything, but as you have tried the over ones (CWM I mean), and that have not screwed your booting process, you may try to flash one of the non working ones again (but known for sure to not harm the boot process) to see if it work again.
Have you used the same FDL set as when you flashed the system partition and the over CWM ?
It's a good thing you have the full backup on your hand. Because you may surely be able to recover from that. I just have to make a tutorial about flashing the backup with ResearchDownload and explaining what file goes where from the backup.
Click to expand...
Click to collapse
Thanks would be really helpful, and yes I used the same FDL.
janzlev said:
Thanks would be really helpful, and yes I used the same FDL.
Click to expand...
Click to collapse
I made another CWM recovery for your phone, please try it: http://www.mediafire.com/download.php?lg7m6v49efzpnjk
Apparently was an error of ResearchDownload (It seems was flashing recovery.img into boot.), so I tried with another copy of ResearchDownload and FDL files and now works like a charm.
Thank you very much!
janzlev said:
Apparently was an error of ResearchDownload (It seems was flashing recovery.img into boot.), so I tried with another copy of ResearchDownload and FDL files and now works like a charm.
Thank you very much!
Click to expand...
Click to collapse
Can you tell me what version of ResearchDownload have this bug. It's a pretty scary one. I have to be sure I don't have it on my computer ...
By the way what CWM image is working ? The first or the second one ? (the two should work but I want to be sure before adding it to the main tutorial)
Thank you very much ! That's one more phone to the list of easily rootable Spreadtrums thanks to you !
Edit: And what FDLs you use precisely so I can rename the folder to reflect the use of this set for this phone (Is this the ones on the .pac firmware you've uploaded on the over topic ?)
RESEARCHDOWNLOAD R2.9.6010, with the R2.9.7002 everything's fine. Respect to the CWM images, after the error I tried with the second one, so maybe the first one also works, the FDLs that I used was extracted from the .pac dropbox.com/s/69yl8hn9361qpy5/FDLs-S6500-TV.tar
That's it, if I can help more, let me know.
janzlev said:
RESEARCHDOWNLOAD R2.9.6010, with the R2.9.7002 everything's fine. Respect to the CWM images, after the error I tried with the second one, so maybe the first one also works, the FDLs that I used was extracted from the .pac dropbox.com/s/69yl8hn9361qpy5/FDLs-S6500-TV.tar
That's it, if I can help more, let me know.
Click to expand...
Click to collapse
I think I have every informations I need ^^
I have added the recovery for S6500-TV to the main tutorial and will add in a short while the fdls to the FDL pack file.
Thanks again !
Backup
attached is my boot.img
to follow: entire backup
Hey,
I've been messing around with flashify app to see if it will install a custom TWRP or CWM as a recovery image but made sure i backed up my recovery using ES File Explorer (as root) /dev/block/platform/msm_sdcc.1/by-name/ recovery and by all intents and purposes it would work if there was a custom recovery out there that would support the Amazon Fire Phone.
When i install a random phones custom recovery and boot up into recovery it will show the amazon screen then with power and up button pressed it will go to a plain black screen.
I would the recover my original recovery file to area mentioned above after this not working and i would have my normal recovery again.
Just wondering if anyone can utilize this info as i know that the Kindle HDX managed to have a custom recovery installed on with with a locked bootloader.
I am currently looking at building a custom CWM recovery for device but if anyone else has better understanding of how to do this it might save a lot of time lol
TheDynamo said:
Hey,
I've been messing around with flashify app to see if it will install a custom TWRP or CWM as a recovery image but made sure i backed up my recovery using ES File Explorer (as root) /dev/block/platform/msm_sdcc.1/by-name/ recovery and by all intents and purposes it would work if there was a custom recovery out there that would support the Amazon Fire Phone.
When i install a random phones custom recovery and boot up into recovery it will show the amazon screen then with power and up button pressed it will go to a plain black screen.
I would the recover my original recovery file to area mentioned above after this not working and i would have my normal recovery again.
Just wondering if anyone can utilize this info as i know that the Kindle HDX managed to have a custom recovery installed on with with a locked bootloader.
I am currently looking at building a custom CWM recovery for device but if anyone else has better understanding of how to do this it might save a lot of time lol
Click to expand...
Click to collapse
I'm doing experiments, I flashed the TWRP version of the Galaxy Note 3 HLTE as they share processor but has not worked, I keep trying.
Best regards,
Just spent hours trying to make a custom CWM recovery image in Ubuntu 14.04 following the guide below but didn't have much luck. May try again at the weekend. If anyone else wants to have a go i have attached recovery and boot images
http://forum.xda-developers.com/android/development/guide-how-to-build-cwm-based-recovery-t2973804
On my KDFIRE Soho is the bootloader Locked and Stock recovery. But you can Flash Roms with the Stock Recovery. There is something with the signature. But only custom Roms based on FireOS Are Working. The FireOS Statusbar is my Personal Nightmare
Well I ported a custom CWM recovery but unfortunately it still does not work when installing with Flashify get the same black screen - Attached.
This made me laugh today
Amazon.co.uk
Your Account Amazon.co.uk
Message From Customer Service
Hello,
I understand that you are not happy, as bootloader is locker for Amazon Fire Phone and would like to have a Key to unlock Bootloader.
I realise that you have been greatly inconvenienced by this situation, it is never our intention to cause inconvenience to our valued customers like you. Please accept my apologies.
Unfortunately, at this time we do not have option to provide Key to unlock Bootloader.
Customer feedback like yours is very important in helping us continue to improve the Fire phone experience. I've forwarded your message to our Fire Phone Team for consideration as we make further improvements.
Thanks for taking the time to provide your feedback.
We look forward to seeing you again soon.
Warmest regards,
Sravanthi
Your feedback is helping us build Earth's Most Customer-Centric Company.
Amazon.co.uk
here's something you should consider.. make a single byte modification to the original bootloader and see if it boots.. if it does.. then we're clear.. if not we're ****ed.. if we're ****ed, then we need to deal with the procedure authenticating (and probably hashing) the recovery.. the bootloader.. or hashcode's hijack it is...
AbdouRetro said:
here's something you should consider.. make a single byte modification to the original bootloader and see if it boots.. if it does.. then we're clear.. if not we're ****ed.. if we're ****ed, then we need to deal with the procedure authenticating (and probably hashing) the recovery.. the bootloader.. or hashcode's hijack it is...
Click to expand...
Click to collapse
So did anyone tried this? It's very easy to do.
Pull your recovery image
Code:
adb shell
su
cat /dev/block/platform/msm_sdcc.1/by-name/recovery > /sdcard/recovery.img
exit
adb pull /sdcard/recovery.img .
then open it up in a hex editor (hdx - windows/ vi - linux) and change a useless byte (probably at the end of the file) or unpack/repack the image using unmkbbotimg/mkbootimg. Then push it back
Code:
adb push recovery.img /sdcard/recovery-new.img
adb shell
su
cat /sdcard/recovery-new.img /dev/block/platform/msm_sdcc.1/by-name/recovery
exit
Then try rebooting to your recovery
Code:
adb reboot recovery
If it works, We might be able to replace stock recovery with a custom built CWM recovery or something since we have the kernel source available. As it seems in update-script, recovery has access to everything weather bootloader is unlocked or not. If you can't modify recovery image yourself, post it here. I'll modify it for you.
madushan1000 said:
So did anyone tried this? It's very easy to do.
Pull your recovery image
Code:
adb shell
su
cat /dev/block/platform/msm_sdcc.1/by-name/recovery > /sdcard/recovery.img
exit
adb pull /sdcard/recovery.img .
then open it up in a hex editor (hdx - windows/ vi - linux) and change a useless byte (probably at the end of the file) or unpack/repack the image using unmkbbotimg/mkbootimg. Then push it back
Code:
adb push recovery.img /sdcard/recovery-new.img
adb shell
su
cat /sdcard/recovery-new.img /dev/block/platform/msm_sdcc.1/by-name/recovery
exit
Then try rebooting to your recovery
Code:
adb reboot recovery
If it works, We might be able to replace stock recovery with a custom built CWM recovery or something since we have the kernel source available. As it seems in update-script, recovery has access to everything weather bootloader is unlocked or not. If you can't modify recovery image yourself, post it here. I'll modify it for you.
Click to expand...
Click to collapse
so this works i just tested it, I used the method you posted about changed the last bit with the hex editor, changed the last octet from 00 to 01, used flashify to flash the recovery
Heres the link to the recovery I modded if you want to test/verify:
https://drive.google.com/file/d/0Bw62MrywuCbwNUZ3Sm05b3FBMGM/view?usp=sharing
thoughtlesskyle said:
so this works i just tested it, I used the method you posted about changed the last bit with the hex editor, changed the last octet from 00 to 01, used flashify to flash the recovery
Heres the link to the recovery I modded if you want to test/verify:
https://drive.google.com/open?id=0Bw62MrywuCbwNUZ3Sm05b3FBMGM
Click to expand...
Click to collapse
You changed a bit at the end of the image right? Then that doesn't make any difference. Sorry I was misleading the last time. I didn't know any better myself then. Recovery partition doesn't contain the recovery image in its entirety. There is extra space. What bootloader does is, it reads the image Heder from the first few bytes of the partition, header contains the length of the recovery image. Then the bootloader verify that length of the recovery partition against some encrypted hash. So to check if this really works (My bet is it doesn't) we have to change a bit inside the length of the recovery image. The easiest thing to do is, unpack and repack the recovery image. I'll give it a try later and post the results.
madushan1000 said:
You changed a bit at the end of the image right? Then that doesn't make any difference. Sorry I was misleading the last time. I didn't know any better myself then. Recovery partition doesn't contain the recovery image in its entirety. There is extra space. What bootloader does is, it reads the image Heder from the first few bytes of the partition, header contains the length of the recovery image. Then the bootloader verify that length of the recovery partition against some encrypted hash. So to check if this really works (My bet is it doesn't) we have to change a bit inside the length of the recovery image. The easiest thing to do is, unpack and repack the recovery image. I'll give it a try later and post the results.
Click to expand...
Click to collapse
Yeah i changed the one at the end, hopefully your testing does work, the way you explained it did make sense
Sent from my A0001 using Tapatalk
This is a no-go, I unpacked and repacked the stock recovery with bootimg-tools (so that it would have no signature information) and flashed it on to recovery partition. The device hangs on Amazon logo when I reboot to recovery. We need to find a way to unlock the bootloader
Guys: I need your understanding, experience, patience and HEEELP!!!
The history:
2 months ago, I bought a new HUAWEI GR3 (TANGO) TAG-L23. Processor = MT6753T
I tried to root it using KingoRoot. I Messed it up... Got a soft-brick: splash screen boot loop. At that moment, I still had access to Fastboot and Recovery mode (stock recovery).
After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3.
I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm.
Tired of searching a stock/custom firmware for GR3 TAG-L23, I decided to download and flash a GR3 TAG-L22 rom using TWRP.
Result = Messed it up again... this time worst... Hard-bricked I think: the phone didn't show any light, couldn't boot it again in any mode... Dead...
The only hope I had is that it is detected by Windows for about 10 seconds as MEDIATEK USB PORT (COMxx) where xx changes when I connect it from one USB port to another.
Since then, I tried almost every tutorial/video/solution/forum/website over the internet, tried almost every SP Flash tool version from v3.1224 to v5.1628, downloaded every scatter.txt for MT6753 processor, tried changing with/without battery option in SPFT, pressing every phone buttons combos, with no luck...
I always get the same error: S_FT_ENABLE_DRAM_FAIL (0xFC0)
Downloaded and installed almost every driver I found on internet: not overwritting them... I created a Virtual Machine, and test them separately using snapshots. Result = Same DRAM_FAIL error.
last week, got another HUAWEI GR3 TAG-L23, untouched, brand new...
I did the following with the new one:
Flashed TWRP recovery using fastboot commands = OK
Rooted it using SuperSU = OK
executed tons of ADB commands that found over the internet, to dump the partition table and stock rom using dd command = OK (I think... what I got is a bunch of files - system, lk, boot, logo, cache, frp, userdata, secro, recovery, nvdata, protect1 and 2, tee1 and 2, and so on).
Using the partition table information, edited one scatter.txt file for MT6753 and, one by one, adjusted the partition info (start and lenght). I did it because when using any downloaded scatter file, and selecting the files that I got from dd commands, SPFT showed error messages saying them were wrong. After editing it and loading the files that I got from the second phone, SPFT recognized them as good ones.
But.... I'm still getting the d...mn S_FT_ENABLE_DRAM_FAIL (0xFC0) error
Also tried to get a rom backup and scatter file from the second phone using MTK DROID ROOT & TOOLS v2.5.3 with no luck: it shows all phone information (except IMEIs), a green rectangle shows up, but... a weird message appears at right: "ERROR: TotalBytesPerChunk Not Found. Set Default Page/Spare=2048/64 !!!". Then I click on "BLOCKS MAP" button, a new window appears showing the partition info (that already got using adb command prompt) and "create scatter file" button is grayed out... And if I try to perform the backup, it starts fine, but ends with error, and no file is backed up...
Let me mention that I already read and googled the totalbytesperchunk error and the grayed out button stuff and tried all alternatives too, and nothing worked.
My work environment:
PC = Laptop With 8 GB RAM / Windows 10 pro x64
Virtual Machines: Windows 7 pro 32 bits, Windows XP 32 bits, Ubuntu 32 and 64 bits...
What else can I do?
How can I use the second, rooted and working phone to get a rom/firmware working dump? it is possible?
If someone decides to help me, let me know what do you need (dumped files, downloaded scatter.txt files, screenshots, whatever you need...)
COM## is a COM port. You can use a terminal program to directly interact with the device.
You are not completely bricked yet.
I do not have any further details to help you, but I can tell you there is still hope.
Connect the dead device to PC, load up a terminal app (if on windows, just load up the app named Terminal)
See where you can get with that.
good luck
Please Help cesarr4: my TAG-L23 bricked - Need your TWRP
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
antonioroa said:
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
Click to expand...
Click to collapse
I attached the recovery I'm currently using in the second GR3. I'm still looking forward the stock rom and a way to recover the first one... have u found a way to unbrick it?
Here you can find the recovery too: http://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-0-huawei-tag-l01-p8-t3433520
I have the same problem with kingroot, and cannot find TAG-L23 rom.
I sent my phone to huawei support and they said it's a board problem and need to replace, the cost is near to the phone's original price.... No way!
In clangsm web page there's a stock rom but you need to pay for vip membership.
Please help with this issue.
I'm still trying to get a working rom image from the 2nd GR3 that I bought... No luck yet... I'm plenty sure that there is no need to do hardware replacement... can anyone point me to a tool/step-by-step guide to readback and save a flashable rom image from GR3 phone, and a SP tools that works with GR3 chipset/PCB?
Hi, i have a TAG-L01 and i got the same problem, i've tried a lot with no lucky, it seems sp flash tool don't support our device(or is huawei that don't want).
If you have some ideas please tell me, i will help(our devices are exactly the same, all TAG-Lxx are the same)
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
srgg01 said:
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
Click to expand...
Click to collapse
Done. Where can I share it for you?
cesarr4 said:
Done. Where can I share it for you?
Click to expand...
Click to collapse
please share your ROM in google drive. i've got same problem here.
Any link to the TAG-L23 ROM? please share as I believe mine is corrupted.
EDIT:SOLVED -- READ BELOW:
I finally got it flashed by following a few guides here which I will link, and try to break it down easier for someone else to come across and follow. I thought I bricked my phone (flashed LineageOS then rebooted, phone did not show anything on screen, full black screen) but after following a few guides I got it solved.
If you get bricked, or just want to follow a clean perfect install, please start below (Skip to step 2 if you are starting fresh, if you have soft-bricked your device start from step 1)
1. Bricked it and had to execute QDLoader 9008 fix again.
Tutorial is easier than it looks, do not fear, if you have soft-bricked your device and see a black screen, go ahead and go through the qdloader brick solution.
2. From factory recovery updated to Version WW-16.1220.1909.193.
If you have started fresh, I would highly recommend updating to the more updated firmware first. For me this worked, and I suggest updating to get a more current kernel, which may play better with Lineage OS install. To install a newer stock firmware linked above, download the ~2GB Firmware above, and save it to your Minimal ADB / Fastboot folder. Power off your device, after it has been successfully restored (if you bricked it) or you want to start off fresh and get the install right the first time. With your device powered off, Hold Volume UP and then Hold Power Button until the Fastboot menu appears. Use your volume keys to select Recovery, then press Power button to enter the STOCK Recovery (we are still on stock firmware with stock recovery). When in stock recovery select install from ADB. We are going to push the install via ADB (I tried dragging the firmware to the internal and selecting install ZIP and that didnt work).
Go into your Minimal ADB / Fastboot folder on your computer and open command prompt by holding Shift+Control and Right clicking and then selecting open command prompt here.
Now, enter the following command in the command prompt and hit enter:
adb devices
This command will show if any fastboot device is connected. If it doesn’t show, then please check the drivers are installed properly and try again.
If your device is listed, then type the command given below and press enter:
adb sideload File_name.zip
^^This will be the ~2GB Firmware file downloaded above
Wait until the installation process completes.
Once the installation process is complete, restart your device.
Done. You have successfully upgraded the Asus ZenFone 6 to the newer firmware, please continue.
3. Downloaded OTA 16.1220.1909.193 to 16.1220.1909.194, renamed it to UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip and placed into root of internal memory.
When I disconnected USB cable (or rebooted, not sure), I was prompted with update notification. I have updated it. Either way, reboot your device if you don't see the notification, and look in your notifications to see something saying: System Update Detected Proceed with Update - and select it and update.
4. Now that your phone is 100% Updated with the newest firmware, let's follow another guide I found here:
I assume you're on a fresh Android 9 stock ROM, or just finished restoring your phone with the Flashall_AFT.cmd from this tutorial.
You should at least boot once on the system, and disable any PIN or password to unlock your phone (hence putting a default password for the FBE).
Download the latest OFFICIAL TWRP.x.x.img (which we'll use to boot on it), and it's installer to install it later (TWRP.x.x.zip) if you want to use it.
LineageOS installation steps :
Reboot to bootloader (=fastboot mode), connect to your PC and boot on TWRP :
Command:
fastboot boot TWRP.x.x.img
Once on TWRP, you can see that we're on slot A (Menu > Reboot). Now go to wipe > factory reset and then wipe system (technically I suspect this only wipes slot A, but do it anyway, don't worry about the errors!)
Now go to Install > flash the newest official LOS_latest.zip. What happens here is that the LOS installer will flash LOS on the inactive slot (slot B in our case). And will also install the LOS recovery (on both slots it seems).
Reboot to recovery : your phone automatically switches slots and will boot the LineageOS recovery (Don't fear, we don't need TWRP right now, just go along with this step) on slot B.
On the LineageOS recovery, do factory reset (which seems to be a full /data format in fact, thus removing any previous encryption AND all your data on internal storage). If you want to use Magisk, go to the recovery's install menu and sideload it now
Use code:
adb sideload Magisk-v20.3.zip
Now reboot to system. It might take a while (one or 2 loops in my case), but your phone should boot, or in some cases will end up on LOS recovery asking for a 'factory data reset' (then do it and reboot again).
Once booted on your LOS rom, you can define a pin or password to lock your phone (that'll be the FBE decryption password).
Now if you want to use TWRP, reboot to bootloader and boot again on TWRP.img (step 1)
From TWRP > Install > flash TWRP.x.x.zip (that is, the TWRP installer). It installs on both slots by default. If you had installed Magisk, you have to flash it again (because anything modifying the boot.img - like the TWRP installer in our case - will erase it).
You can now reboot to system and enjoy LOS
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
abprie said:
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
Click to expand...
Click to collapse
Haven't actually put my sim in yet to make calls, will let you know later today, sorry about the delay!
I had previously attempted this a number of months ago, and managed to soft brick my Zenfone 6 several times, eventually kind of giving up and just using the stock firmware.
I tried again back on Memorial Day in the US. This time around, I bricked it hard. Could not get device to power on in any fashion. PC would not "see" USB connection at all.
I returned it to ASUS for service, and they've charged me a little over $200 to repair it. The only problem they noted was, "Device is rooted/unlock". So I have no way of knowing if their diagnosis is based on actual inspection of the device, or if they're just replacing the SOC on the basis that I used their official bootloader unlock tool, thus registering my phone's S/N.
Just a little caveat emptor for anyone attempting to use this guide. I was able to get TWRP to load, and succesfully updated the stock firmware, but any and all attempts to load the Lineage image failed.
Eventually one of them soft bricked my phone as before, and I think my mistake was interrupting the soft brick rewrite procedure by prematurely unplugging my phone from the PC.
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realised the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I couldn't switch completely off, access recovery/fastboot, and my computer wouldn't recognise the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
~SilverLad~ said:
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realized the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I could switch completely off, access recovery/fastboot, and my computer wouldn't recognize the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
Click to expand...
Click to collapse
Can you post a link to where you purchased the cable?
abprie said:
Can you post a link to where you purchased the cable?
Click to expand...
Click to collapse
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Since the thread is already on topic, could I flash lineage os while being on a custom rom? I have Bliss ROM on partition A and stock on B. Is it possible to have both Bliss and Lineage in dual boot?
Also, maybe a little off topic, the partition A/B scheme was intended to be used as a dual OS boot like normal PCs? Because right now I can select A and boot Bliss, select B and boot stock, I don't get why the procedure for flashing Lineage OS is so convoluted(requires having stock both on B and A?!) since both partition seems to be standalone and separated from each other.
~SilverLad~ said:
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Click to expand...
Click to collapse
Hey there, what's the process around using this cable?
vikashhero said:
Hey there, what's the process around using this cable?
Click to expand...
Click to collapse
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
~SilverLad~ said:
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
Click to expand...
Click to collapse
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
vikashhero said:
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
Click to expand...
Click to collapse
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
~SilverLad~ said:
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
Click to expand...
Click to collapse
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
Click to expand...
Click to collapse
Happy to hear that Indeed be careful - this is a tricky phone...
vikashhero said:
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
Same here. It was so easy to do the Samsungs "back in the day", and you always had ODIN as a fallback if things went south. But this "A/B" partition nonsense (as well as other useless changes they introduce every time they "upgrade" Android, or certain structure modifications every so often when a new phone comes out) are a pain in the butt! Changes clearly aimed at making things more annoying/difficult for us people who don't want standard/corporate/unnecessarily bloated phones... Actually (as a former Blackberry user) I was tempted to get one of these Android based Blackberrys (the KEY2), but I didn't in the end precisely due to the fact that the bootloader can't be touched, and it can be rooted...
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
I want to switch to because the latest security update (August 2020) by Asus is soft bricking the phone for many users,
but I am seeing a few reports about some bugs (like the phone is stuck in the lineage boot symbol and cellular errors) in lineage os and also seeing few post with a lot of installation errors (like soft and total bricking) etc. and for me in developers options I'm not seeing the OEM and advanced boot options.(in my asus stock os) I just found out that I have to download the Unlock Boot loader apk separately from asus and install it using command prompt so I don't know how to proceed.
Can you please elaborate on how you actually did it with your Asus Zenfone 6(2019), I am a total noob in this and I also couldn't understand the partition a and b parts too.