Database Develop

[Q] Flashing assistance

Hey guys!
I swear I must be the only idiot out there who can't work out the Flashtool interface. I have rooted, installed CWM and readied my FTF file ready to flash. My problem is actually connecting the phone and getting the interface to recognize the Z.
When booting the program I plug the device in, it loads up and installs the ADB interface drivers and provides me with a prompt giving me a list of phones to choose from. The Z just isn't in there and I don't want to proceed by choosing another device 'by default'...
I have well and truely searched the hell out of this question with as many different queries as I could imagine to no avail. I have flashing experience and consider myself quite computer savvy but this has more then got me stumped!
Any suggestions?
Regards,
Josh

gibilator said:
Hey guys!
I swear I must be the only idiot out there who can't work out the Flashtool interface. I have rooted, installed CWM and readied my FTF file ready to flash. My problem is actually connecting the phone and getting the interface to recognize the Z.
When booting the program I plug the device in, it loads up and installs the ADB interface drivers and provides me with a prompt giving me a list of phones to choose from. The Z just isn't in there and I don't want to proceed by choosing another device 'by default'...
I have well and truely searched the hell out of this question with as many different queries as I could imagine to no avail. I have flashing experience and consider myself quite computer savvy but this has more then got me stumped!
Any suggestions?
Regards,
Josh
Click to expand...
Click to collapse
This is how I installed the driver for my XZ:
Install the driver first
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select the XZ driver:
Now update the driver because your PC probably can't find the driver:
Now you have to select the driver yourself. So you have to pick it from the list
This the updated driver:
I hope that helps a little.

shadowboy23 said:
This is how I installed the driver for my XZ:
Click to expand...
Click to collapse
Thanks heaps!! I managed to get the drivers installed but the application still doesn't recognise the Z? any thoughts?

try changing the usb settings to mass storage instead of media mode or the other way round

gibilator said:
Thanks heaps!! I managed to get the drivers installed but the application still doesn't recognise the Z? any thoughts?
Click to expand...
Click to collapse
Is this what you are talking about?
To flash any stock ROM you don't need CWM. Flashtool is all I use to flash .ftf files
I download the ftf file I want and place it in the firmware folder:
I then start the flashtool app while the phone is unplugged, turned off and make sure it's in "Flashmode"
Once you click "Ok" this window should show up:
And then choose the ftf you placed in the folder. You should see this window:
And flashing will begin.
Just make sure you have full charge on your XZ before you do all this.

Wow, shadowboy23, you really went above and beyond with your assistance given here! You should really consider copying those posts over to the general thread and make a driver installation and flash tool guide (unles there is one...) But yeah, Kudos!:good::laugh::good:

Thanks!
I cannot believe that post shadowboy23 seriously thank you so much I can see the amount of time you have put in there! I myself haven't had any time to check the computer or even think about flashing my phone but will have another attempt this coming weekend and will defiantly bring you results (hopefully good news!)
Cheers again!!
Josh

I had a crack this afternoon and successfully got everything to the stage where your last step ends (on one of my 3 computers only!) and then the flashboot spits out an error message telling me the device drivers are not loaded. I will persist tomorrow afternoon when I have a fast internet connection and can download the latest version of flashboot (I have beta 4 I believe).
Incredibly frustrating process though!!
Josh

SUCCESS!!
Cheers shadowboy!! your new version fixed the issues I was having with the loader and it was all plug and play... but most of all thanks for letting me know to untick those boxes!! saved me the nightmare of having to reinstall everything
Cheers!!
Josh

xt1254 hangs on bootloader/recovery

Hi all, ive been running custom roms on my phone ever since sunshine was released for it.
In the past 6 months or so, my phone has gotten horrendously bad at booting.
When i turn it on, it will hang on the bootloader warning screen for 2 to 3 minutes before showing any sign that anything is happening.
Im really at a loss, ive done everything but a complete format and sideload.
Not really sure what other information would be required.
what should i do?
also every few days i have to go into apns and click one of the verizon ones again before my data will work, but that might just be a rom issue.

jombo2323 said:
xt1254 hangs on bootloader/recovery
Hi all, ive been running custom roms on my phone ever since sunshine was released for it.
In the past 6 months or so, my phone has gotten horrendously bad at booting.
When i turn it on, it will hang on the bootloader warning screen for 2 to 3 minutes before showing any sign that anything is happening.
Im really at a loss, ive done everything but a complete format and sideload.
Not really sure what other information would be required.
what should i do?
Click to expand...
Click to collapse
At first I thought you were saying your phone was booting to the bootloader screen or even booting to TWRP recovery, which would be very strange. That's happened to people before... which means the phone is really messed up.
But reading your actual write-up, (if you wrote it correctly) instead your phone is just NORMALLY booting. It's just taking a long time. Your phone is just staying stuck on the boot image, which is not the bootloader or recovery screens. It's just an image you see before the boot animation starts until finally you see your normal Android system GUI. In your case, it's the "bootloader warning screen" which is something you should replace.
THIS is the bootloader screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But instead you're seeing this, right?
It's the boot image Motorola has replaced to warn you your bootloader is unlocked. Yeah, I did it on purpose! As did you. No need to see it every day. You can flash a replacement boot image very easily in TWRP or ADB. <There's several to choose from.
WHY is it hanging on the boot image? You are right that something is wrong, but I don't think your phone is very messed up -- at least it's not booting to the bootloader screen!
You've tried clearing all the caches in TWRP? You've tried dirty flashing your ROM again? Sometimes something can get slightly corrupted and re-flashing your ROM over itself can fix the issue. Clearing all the caches in TWRP and letting all the apps re-optimize can also fix some issues.
Do you have any add-on xposed modules? I would temporarily disable all exposed modules, reboot a couple of times, see what happens? You can always re-enable them later. Xposed modules can conflict with your normal ROM functions and should be used very sparingly. Some modules like Gravity Box are really another ROM and settings in Gravity Box can conflict with settings in your ROM. But to a lesser degree so can almost any other xposed module.
Have you restored your TWRP backup which you made before all this happened? You do have a good TWRP backup, right?
Last, yeah, if none of that works, factory reset and reinstall the ROM.

Are you encrypted? I've noticed that once you encrypt the storage that the phone takes forever to boot. I haven't found any way around that and someone with more knowledge of the hardware than me mentioned that it's because the drivers for HW decrypt acceleration are missing.

I will add to this as I am having the same issue and have moved to another 32GB Turbo for the time being but now I'm having Radio issues with this one.
My 64 was encrypted, running CF's 1.0.8, xposed. Doing restoring the factory image did the same thing. Only thing is now that i think about it TWRP didn't ask for my pin for encryption though like it was before so it may not be encryped. I'm going to be doing some factory images this weekend and see if i can find out the issue and if I find anything I'll post back. Only thing that sucks is I only have one good screen between the two phones lol

Ugh, sorry for the lack of response. Ive been really busy.
To answer all questions. Ive done everything but wipe some crap with fastboot commands and performing a clean flash of the rom. Im on resurrection remix right now, i think i want to change though because my battery life is kinda ****.
Also no xposed, etc, just the basic rom.
Sorry for taking so long and thanks for the responses!

Le S3 x626 bricked issue

Hi, I have checked this thread as I experienced the same issue(If confused what I'm talking about read
www chinaphonearena com/forum/Thread-Question-LeEco-Le-S3-X626-Helio-X20-Bricked ), I was able to get past the phone buttons not working and was able to flash a new firmware. But this led to another issue considering the system.
For one, I am unable to unlock my bootloader, I just receive the error : FAILED (remote: unlock operation is not allowed), and there is no way fro me to get in my android as it always stays on the LeEco POWERED BY ANDROID screen, which then shuts down and reboots.#
As well as this, the display is now very unusual: the LeEco logo is coloured green white and yellow, the display is flipped horizontally and mirrored vertically.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The image above shows this.
It's VERY annoying and I hope it can be solved.
NOTE!! I can still use locked bootloader/fastboot, can't use adb and can use SP FLASH TOOL

You need to power the phone and wait till boots. Enter the flipped UI enable developer mode and unlock the bootloader.
All the control are flipped so be patient.
After that enter fastboot and flash the original rom

damtrx_ said:
You need to power the phone and wait till boots. Enter the flipped UI enable developer mode and unlock the bootloader.
All the control are flipped so be patient.
After that enter fastboot and flash the original rom
Click to expand...
Click to collapse
Thanks for the reply, I fixed the issue the same day, I just fixed it using the second part to tickernel's red light unbrick tutorial, I completely missed it out. The rom I was using where everything was inverted was just to unbrick the phone, then after I'd have to flash the rom provided by tickernel to fix. It worked again and an advantage was that there was no more ORANGE state, I didn't have to patch to hide the message nor wait the 5 seconds, so now I can flash custom roms on my phone without the message. The method you provided wasn't the fix, before opening this thread I double checked and saw your method, but thanks anyway .

it was necessary to use a mirror. for example, in the bathroom

after brick and ressurect what write in (telephone settings) model?

Shekor said:
after brick and ressurect what write in (telephone settings) model?
Click to expand...
Click to collapse
it depends on which model is taken ROM. It does not play any role. Can be changed to Build.prop

Kychera22 said:
it depends on which model is taken ROM. It does not play any role. Can be changed to Build.prop
Click to expand...
Click to collapse
after bad ressurects i return my device le x626. to le x620 with eui 5.8.018S (stab.) it works normal. But was some bugs with 4g on (turn phone off) and google programs don's start.
But i fixed it all, now it works great, but i think is it bad?

take the stock firmware 28. and install. why use the old version? maybe get my firmware.
to use google apps. you need to download google installer, then after installation, in the settings give permissions to all Google apps.
and correctly to do so: to install firmware, then to start system and to configure it. and then only install the google gapps.

Update on unbrick
With my phone unbricked, it now works perfectly. But now the battery drains very fast. It drops by around 25% in less than half an hour with normal use such as watching videos on youtube in "360p" with all my apps closed, but still the battery drains. I have tried flashing different roms and clearing all partitions in twrp and flashing the CUOCO AND WOLFRED x.28s custom stock roms, but still the issue persists. This is very unusual as before my phone bricked, the battery would hold up for at least an hour before falling by 10 to 20 %. Does anyone have any speculations on why or any fixes? Please help.
UPDATE: I fixed by flashing the international version system.img only if you need it send me a message and I'll put up a link.

Critical Partition Flashing is not allowed on Xiaomi Redmi 4x help me

Hi everyone, my cell phone works normally, but when i put to recharge the battery my phone was brick. The Edl mode doesn´t works and when i put to fastboot mode to flash the official rom i get that message "Critical Partition Flashing is not allowed". My cellphone is unlocked with twrp and i have the pixel experience installed. I try install the twrp again but nothing happens, i try install the official rom and i get that message Critical Partition Flashing is not allowed, some can help if i have a chance to put to work again? Anyway, thanx :good:

make backup of everything and then make clean flash with formatting internal storage. try different rom if possible.

metelhammer said:
make backup of everything and then make clean flash with formatting internal storage. try different rom if possible.
Click to expand...
Click to collapse
Hi matey, how u doing?
I don´t have acess on twrp, i´m trying isntall again but i get error like the locked again. When i run the program of xiaomi to check if the cellphone still unlocked, seems is lock again. I don´t know how this happens, maybe when i put the official rom of santoni to try install again, i try use the clip to edl mode work but nothing happen, i put fastboot mode on but still with that message.

Andinho-system said:
Hi matey, how u doing?
I don´t have acess on twrp, i´m trying isntall again but i get error like the locked again. When i run the program of xiaomi to check if the cellphone still unlocked, seems is lock again. I don´t know how this happens, maybe when i put the official rom of santoni to try install again, i try use the clip to edl mode work but nothing happen, i put fastboot mode on but still with that message.
Click to expand...
Click to collapse
I doing great, The phone shouldn't have been locked itself on pixel experience, since only way to lock it is on official global/china MIUI rom.
try downloading different version of mi flash tools (maybe a older one) download latest fastboot rom again and try flashing it again.
here it is video for reference https://www.youtube.com/watch?v=a1jHh4MnXs0
you may need to connect edl points.

metelhammer said:
I doing great, The phone shouldn't have been locked itself on pixel experience, since only way to lock it is on official global/china MIUI rom.
try downloading different version of mi flash tools (maybe a older one) download latest fastboot rom again and try flashing it again.
here it is video for reference https://www.youtube.com/watch?v=a1jHh4MnXs0
you may need to connect edl points.
Click to expand...
Click to collapse
I put my cellphone yesterday on garbage, weeks trying, geting stress a lot with that... But i don´t was try what u post here matey, i believe can really helps. I´ll buy another Xiaomi Redmi 4x, i´m checking it out on shop and see models above the redmi4x but with the same storage 32gb, hardware and memory ram too, but more expensive u know. I like this model Redmi 4x and i will keep for a long time.
Anyway, thanx a lot. God bless u

Andinho-system said:
I put my cellphone yesterday on garbage, weeks trying, geting stress a lot with that... But i don´t was try what u post here matey, i believe can really helps. I´ll buy another Xiaomi Redmi 4x, i´m checking it out on shop and see models above the redmi4x but with the same storage 32gb, hardware and memory ram too, but more expensive u know. I like this model Redmi 4x and i will keep for a long time.
Anyway, thanx a lot. God bless u
Click to expand...
Click to collapse
If you still have your device then put your device in fastboot mode and then flash the fastboot rom by following video via mi flash tools.

Critical Partition Flashing is not allowed on Xiaomi Redmi 5 help me, when i want to flah
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ASUS ROG Phone 2 E:Failed...

Hello, I was watching YT a few weeks ago and the phone (ASUS ROG Phone 2 tencent edition version 8/128) decided to reboot by itself. It done it before but this time it wouldn't get past the starting logo and restart again! It would keep looping until the battery ran empty... SO I booted in recovery mode, tried to factory reset and get E:Failed to save locale.
A friend has been trying to help me fix the phone and this was the result (screenshot). He can't figure it out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried searching the forum with no luck. Anyone know if this problem is fixable and could guide us in the right direction?

did you backup your phone precautiously before
if you havent u lost all your important files
is your phone under warranty

Lavithiran -=-=-= said:
if you havent u lost all your important files
Click to expand...
Click to collapse
Hey, haven't backed up before at any point and don't have warrenty. Is there a way to get the phone working again?
Can't find old screenshot; if I remember correctly the first time I tried to factory reset after looping it said "driver E missing" something along that line. Up to that point never tried to change anything on the device by using a usb or PC.

mosa00 said:
Hello, I was watching YT a few weeks ago and the phone (ASUS ROG Phone 2 tencent edition version 8/128) decided to reboot by itself. It done it before but this time it wouldn't get past the starting logo and restart again! It would keep looping until the battery ran empty... SO I booted in recovery mode, tried to factory reset and get E:Failed to save locale.
A friend has been trying to help me fix the phone and this was the result (screenshot). He can't figure it out.
View attachment 5640881
I've tried searching the forum with no luck. Anyone know if this problem is fixable and could guide us in the right direction?
Click to expand...
Click to collapse
Do it this way:
1. Make a Wipe
2. Download this file https://androidfilehost.com/?fid=8889791610682901175
3. Run fastboot bootloader and connect to computer (side port)
4. Unpack and run "flashall_AFT.cmd" wait for the phone to reset and start up.
Should help.

mosa00 said:
Hey, haven't backed up before at any point and don't have warrenty. Is there a way to get the phone working again?
Can't find old screenshot; if I remember correctly the first time I tried to factory reset after looping it said "driver E missing" something along that line. Up to that point never tried to change anything on the device by using a usb or PC.
Click to expand...
Click to collapse
i dont think so you can retrive your old files