I have the F3213 Single Sim
My phone was rooted with marshmallow thus used flashtool.
Series of steps I took.
Installed Nougat with Flashtool and everything worked perfectly. Enabled usb debugging, OEM Unlock was greyed out but enabled,
Booted into fastboot mode. With the files I downloaded from Android infotech, copied superuser to the device before flashing. I flashed Boot img, recovery img and
Flashed both images fine. Went to restart and bam, flashing Sony logo. I tried every method to boot into recovery to no avail.
Did I go wrong somewhere or forget a step? I followed the guide on And Infotech to the letter. Or was that my mistake for getting these files from them in the first place.
Any insight would be appreciated.
I spent 8 hours trying to fix this but nothing worked. So I just decided to give up and use flashtool all over again and start from scratch.
I am not a noob to flashing phones but by God this phone is by the hardest I've ever tried to flash. I hope someone can point me in the right direction if they know what I did wrong in my previous post.
Related
Hi! I've managed to brick my device (d610ar) badly, i think
the device doesn't boot normally (message "Secure booting error! Cause: boot certification verify.", and i am stuck there), can't charge it with the wall charger, and the only thing that works is download mode; but flashing a kdz with LG FlashTool (the way i went back to stock a few times) says flashing and at 2% (or 3% sometimes) it says that doesn't find the device, that i have pull out the battery to reconnect my device again and when i do that it does the same thing on a loop, asking to do it again later..
the funny thing is that it appears on device manager on windows, on com port 11 for example, but the FlashTool doesn't recognize it..
so, i can't flash any kdz and doesn't boot.. i've read around here in xda to enter fastboot to fix it, but.. can this device enter fastboot? i couldn't do it, tried adb too and couldn't make the device visible..
i, before this happened, had multirom installed, rebooted to recovery and deleted secondary roms to install in primary rom cm12.1.. there started to happen strange things when rebooted normally to configure it..
after a while trying to boot found around here in xda too that i could enter twrp recovery via hardware keys to reinstall again, so got into it and installed a flashable zip to come back to stock KitKat directly, that have worked for me before..
after that rebooted and i can't do anything else than download mode..
i kinda figured that the problem must be that multirom injected the boot sector after installing the stock flashable zip, and when i did that restored the stock aboot and abootb (these, modified carefully, allowed us to unlock bootloader and flash recoveries, etc, etc.. ; by the way, many thanks to the devs that discovered it and made the guides!)..
now i have read the instructions for flash via fastboot the stock boot.img and so pass the security verification, but i can't enter it..
so, what do you think that could be the next step? or is it really hard bricked and i should forget about it? i'm really hoping to recover it but i don't know what else to do..
sorry for the bad english, not my primary language
thanks for reading and i am hoping to hear some suggestions!
He is not hard bricked you need to flash stock boot and reunlock bootloader if you have custom recovery still installed, but go first with the eazy way search xda about lg flash tool stuck at 2% there some guides to help you get kdz flashed
Thank you very much!
numpea said:
He is not hard bricked you need to flash stock boot and reunlock bootloader if you have custom recovery still installed, but go first with the eazy way search xda about lg flash tool stuck at 2% there some guides to help you get kdz flashed
Click to expand...
Click to collapse
Thank you very much! You made me realize why wasn't working..
Because of you, i started to search threads related with the "flashtool stuck at 2%" and one of the things to look at was a txt file to see what was the problem.. there i found out that the lg FlashTool recognized my device as LGD618..
That's when i realized that i must've messed up when i flashed a lollipop flashable zip for the D618(a while ago), "converting" my cellphone on that model.. so when i connected on download mode and put the LGD610 kdz the comparison of cellphone model and binary model didn't match..
Solution was to flash LGD618 kdz, boot up normally, install towelroot, install supersu, edit a line on build.prop
from persist.multisim.config=dsds to persist.multisim.config=none
rebooted and that's it.. everything works perfectly now! i won't be doing stuff to it for a while
probably will stay stock like that, because now i will be using an OnePlus One in a few days and the G2 mini will be used by my mother, i think..
Thanks again! You saved my device for being bricked forever
i glad i could helped you :good:
I tried installing kitkat having installed lollipop and did not work, also I tried installing lollipop and nothing. Well I think this update lollipop are adding some kind of lock to disallow downgrade or upgrade by KDZ. I try other methods, unlocking bootloader, and install a aboot.img, bricked my phone. I recommend that you do not attempt to unlock the bootloader and install any system image that is not official, or may end up with a dead device.
Hi experts!
Is there an available factory image of the latest firmware for griffin xt1650-03 for download? I unlocked my boot loader and tried to flash custom firmware now I am stuck in boot loop. My phone was nougat and updated via OTA last week before I decided to unlock boot loader. I tried loading the latest image I got from firmware.center but I am getting Downgrade version and verification failed when flashing stock partition and not loader. Please help
Note: I did this my wifi became unusable after my last OTA (mac 02:00:00:00) and thought using custom firmware would help
And I did not make a back up
Get it in fastboot mode, flash TWRP and root it. That might work.
I am in exactly the same position as OP, although I have successfully installed TWRP and have open bootloader from which I can boot into TWRP no probs. I didnt do a backup (will never again make this error!!)
The problem arises when I try to flash (any) files over to device I get the "Downgrade version and verification failed" like OP when flashing stock Telus rom (telus phone) or any other rom/files.
Rebooting brings me back to the moto unlocked bootloader page (horrible!) and the only way out is to get key combo or fastboot into bootloader/recovery etc.
Tried flashing multiple images as whole or bit by bit, always get the same bad validation message. Finding it hard to believe this 700dollar phone is a brick after literally following MotoS own 'unlock your bootloader' instructions. Never had issues like this on OPO, S6, S7, LG etc.
PC shows android device connected, nothing in the two empty folders that appear. TWRP confirms I have no OS installed and throws me back to bootloader.Wondering if locking bootloader again will allow me to install 'stock' ROM or at least recovery? I have reached my android knowledge limit and am not sure where to go from here, any help much appreciated!
OK. This happened to me. The way that I solved it was by flashing the RETUS NPL86.25.15 and then flashing the OTA 25.17-3-3 through twrp. Although I think I could've saved the headache if the original instructions included flashing the OEM.bin but anyways. That's what I did. Hope it helps.
Thanks. I did try flashing the oem.bin but got partition name error.
Can you link to the files you mention I think it's a kernel and then an OTA image? Thanks again in advance.
What I mean is that when I first started flashing the RETUS rom the instructions skipped that part so I ended up flashing most of the file system without something so it would never boot but it wouldn't loop it'd just hang. So basically you flash everything and then include the OEM.bin after you do the system chunks
Hello!
Thanks for reading this thread, there's a lot that I'm about to say based on what has happened for the past 8 hours of troubleshooting.
I hope you'll be able to help me regarding my issue.
Everything was going well as I on my way to unlock my bootloader (done) and root my device.
After rooting via TWRP, I'm stuck on the white XPERIA logo screen.
Proceeded to wipe my phone, and thanks to my stupidity, loss of OS.
Downloaded an GLOBAL OS online, tried to flash into my device with FlashTool.
Error came to me as I needed flash script.
Search online, to no avail, I went to my final option
I saw a tutorial of creating a pre-rooted ROM : https://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
I attached my OS I previously downloaded which i tried to flash with FlashTool, attached SuperSu into the application and a flashablezip (as instructed).
Flashed this pre-rooted ROM into my device using TWRP, rebooted.
New problem: Stuck at white Sony logo, couldn't enter TWRP.
Flashed in via cmd.exe a working boot.img & recovery.img.
TWRP now works, but I'm back to square one : stuck at the white XPERIA logo screen.
If you've read all of that, I thank you so much for doing so.
I hope that you'll be able to help me after these gruesome 8-hours of researching, trial & error session.
It's about time I requested help from professionals.
Thank you!
Edit : I can boot up my phone now, however that's achievable by removing SuperSu via TWRP.
This is no longer an urgent need for help, but it will be nice if I could get an idea why would I be stuck at the XPERIA logo screen when SuperSu is installed.
Mercuryus said:
Hello!
Thanks for reading this thread, there's a lot that I'm about to say based on what has happened for the past 8 hours of troubleshooting.
I hope you'll be able to help me regarding my issue.
Everything was going well as I on my way to unlock my bootloader (done) and root my device.
After rooting via TWRP, I'm stuck on the white XPERIA logo screen.
Proceeded to wipe my phone, and thanks to my stupidity, loss of OS.
Downloaded an GLOBAL OS online, tried to flash into my device with FlashTool.
Error came to me as I needed flash script.
Search online, to no avail, I went to my final option
I saw a tutorial of creating a pre-rooted ROM : https://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
I attached my OS I previously downloaded which i tried to flash with FlashTool, attached SuperSu into the application and a flashablezip (as instructed).
Flashed this pre-rooted ROM into my device using TWRP, rebooted.
New problem: Stuck at white Sony logo, couldn't enter TWRP.
Flashed in via cmd.exe a working boot.img & recovery.img.
TWRP now works, but I'm back to square one : stuck at the white XPERIA logo screen.
If you've read all of that, I thank you so much for doing so.
I hope that you'll be able to help me after these gruesome 8-hours of researching, trial & error session.
It's about time I requested help from professionals.
Thank you!
Edit : I can boot up my phone now, however that's achievable by removing SuperSu via TWRP.
This is no longer an urgent need for help, but it will be nice if I could get an idea why would I be stuck at the XPERIA logo screen when SuperSu is installed.
Click to expand...
Click to collapse
Hi, without any logcat it will be very hard to help you
Just a little disclaimer: I am an ABSOLUTE NOOB at this stuff and I just followed tutorials and guides; no experience whatsoever and I badly need your help
It all started when I wanted to root my phone. So I decided to install a custom recovery on the phone first(CWM to be exact). I flashed the recovery.img file and soft bricked my phone. I managed to fix it easily just by erasing recovery by using adb. Afterwards, recovery was accessible again. Since I couldn't do it that way, I tried downloading the phone's latest firmware from ASUS' website and pulled the boot.img out of it and patched it with Magisk. Flashed it and boom, bricked my phone. I tried fixing it the same way I did with the recovery.img but it didn't work. I even tried erasing it and flashing the original boot.img file I pulled out of the firmware file I got from ASUS' website, but it wouldn't work; it would boot up, show the ASUS logo, then shut off. Please, tell me there's a way through this, and btw the phone's bootloader was unlocked for sure; I used ASUS bootloader unlocker from the website. I have all firmware files already downloaded in case I need 'em.
UPDATE: I flashed a boot.img form an older firmware file from the same website and it kinda worked. It boots now and it seems to be stuck on the Zenfone logo now :/
Hey. I remember that you can boot into adb mode and then do
adb sideload "yourfirmware.zip"
The instruction holds true for earlier zenfones. See if it works here.
I have the same phone, but is dead, no recovery, no fastboot mode, no screen.
What can i do?. My pc just detect QDloader driver help plz.
Try this
msoliveras said:
What can i do?. My pc just detect QDloader driver help plz.
Click to expand...
Click to collapse
You need unbrick with: stock ROM
addrom.com/raw-rom-unbrick-for-asus-zenfone-live-l1-za550kl
QFIL program 1.0.0.2 versión
androidmtk.com/download-qualcomm-flash-image-loader-qfil
And valid version of QDloader driver
gsmusbdrivers.com/download/android-qualcomm-usb-driver
watch this video: youtube.com/watch?v=Ao5FB9mVZCU
Important if you zenfone live l1 is 2/3Gb Ram or is Go version 1Gb Ram to download correct stock ROM
Deceinard said:
Just a little disclaimer: I am an ABSOLUTE NOOB at this stuff and I just followed tutorials and guides; no experience whatsoever and I badly need your help
It all started when I wanted to root my phone. So I decided to install a custom recovery on the phone first(CWM to be exact). I flashed the recovery.img file and soft bricked my phone. I managed to fix it easily just by erasing recovery by using adb. Afterwards, recovery was accessible again. Since I couldn't do it that way, I tried downloading the phone's latest firmware from ASUS' website and pulled the boot.img out of it and patched it with Magisk. Flashed it and boom, bricked my phone. I tried fixing it the same way I did with the recovery.img but it didn't work. I even tried erasing it and flashing the original boot.img file I pulled out of the firmware file I got from ASUS' website, but it wouldn't work; it would boot up, show the ASUS logo, then shut off. Please, tell me there's a way through this, and btw the phone's bootloader was unlocked for sure; I used ASUS bootloader unlocker from the website. I have all firmware files already downloaded in case I need 'em.
UPDATE: I flashed a boot.img form an older firmware file from the same website and it kinda worked. It boots now and it seems to be stuck on the Zenfone logo now :/
Click to expand...
Click to collapse
I had the same problem and qfil didn’t worked. Try mi flash tool( try all versions, because not all work). It was able to flash my phone.(zenfone l1)
So I just rooted my pixel 6 using the correct original img from google and Magisk. This worked great and I got root access (active boot partition was a if it’s somehow relevant). Now I wanted to use all the functions of nethunter (which I downloaded and installed from nethunter store or something like that), so I wanted to install the nethunter Kernel for my device. Pixel 6 is not officialy supported by kali or not leaked yet so I found pre build nethunter kernel for pixel 6 on xda developers.: https://forum.xda-developers.com/t/...o-oriole-raven-kernel-kali-nethunter.4461589/
So I went in to the mega folder and into the mad-kali-maxhunter-kernel folder. Then into the p6_p6pro folder. Then I just downloaded the maxhunter zip thing for oriole because it stands for p6 ig. Then I flashed this zip file using the Franco kernel manager as recommended in the thread. My device restart and didn’t start up again. So I just tried getting in fast boot and I got it. Now I thought i would just flash the patched magisk img I made for rooting the device previousl. So I did that using fastboot flash boot and so on. Next my device was in an bootloop still, so then I flashed the very original google official img for the device. Still boot loop, so then I wanted to do recovery from fastboot on the phone when I started factory reset mode the phone was just stuck in the google logo. Then I wiped all data using the fast boot tools from my computer. It wiped it but said stuff like the file system is not formatted or not the right format or so but still wiped the data. Still boot loop. So now I switched the active boot partition from a to b. This time the phone said like waiting for command and so on. So I watched a tutorial and got further, now I was able to get to the factory reset mode did. a reset and started. Nothing realy happened and it jumped back to fastboot mode. I thought maybe because in boot b is no img to boot. So I flashed the official google img again but on b. Still bootloop. Now I have a problem. Pls help me.
You should consider trying Google's official Android Flash Tool, it might succeed where your manual flashing failed -- especially considering it was set up by Google and might have better/further checks and such...
Yes, I would recommend Android Flash Tool also. Its helped me a couple times to recover when I couldn't boot. It gives you options for boot.img right before flashing your phone so everything you'll need should be there
@simplepinoi177 i would really like to use it but its using adb and adb is not passible only fastboot so my device isnt available. EDIT: Nvermind i didnt read correctly.
Thank y'all so much it worked!!!
Great. Android Flash tool ftw again