I am using ARROW Os (pie), Now i want to get back to official stock rom with locked bootloader plox help me how to do so.
JUST now I HAVE FLASHED Lenovo_Z2_Z2132_Q01017.1_M_ZUI_2.0.093_ST_160811_QPST with QFIL and it is showing error ownload Fail:Sahara Fail:QSaharaServer Fail:The directory name is invalid. plz help me
having exactly same issue
hilarioustiwari said:
I am using ARROW Os (pie), Now i want to get back to official stock rom with locked bootloader plox help me how to do so.
JUST now I HAVE FLASHED Lenovo_Z2_Z2132_Q01017.1_M_ZUI_2.0.093_ST_160811_QPST with QFIL and it is showing error ownload Fail:Sahara Fail:QSaharaServer Fail:The directory name is invalid. plz help me
Click to expand...
Click to collapse
keep posting so that solution come out
hilarioustiwari said:
I am using ARROW Os (pie), Now i want to get back to official stock rom with locked bootloader plox help me how to do so.
JUST now I HAVE FLASHED Lenovo_Z2_Z2132_Q01017.1_M_ZUI_2.0.093_ST_160811_QPST with QFIL and it is showing error ownload Fail:Sahara Fail:QSaharaServer Fail:The directory name is invalid. plz help me
Click to expand...
Click to collapse
Dude, this post is not a valid one.
To solve your error, extract the stock ROM files in a close directory to the pathname like ( c:\Stock\) .
ANd the next error you did was u did not launch qfil using admin rights.
do both the steps and try flashing stock.
hope I helped you. press the thanks button if so.:laugh:
@Az Biker
Try QFIL 2.7.460.
Here is the link https://www.google.co.in/amp/s/www....atest-qualcomm-flasher-qfil-qpst-2-7-460/amp/
Bro this post is a valid one
akshay pro said:
Dude, this post is not a valid one.
To solve your error, extract the stock ROM files in a close directory to the pathname like ( c:\Stock\) .
Andd the next error you did was u did not launch qfil using admin rights.
do both the steps and try flashing stock.
hope I helped you. press the thanks button if so.:laugh:
@Az Biker
Click to expand...
Click to collapse
Ok after successfully flashing my zuk z2 plus this is what i have to say about sahara.
I Still dont know why this error happens, i reinstalled new windows after which i followed the whole step. basically a fresh start.
although there are lots of tutorial available in youtube and xda dev forms the one i suggest is attached below:
https://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
and for youtube walkthrough there is this link:
https://www.youtube.com/watch?v=wSHX-9S_oRc
now there are multiple workaround mentioned which i don't claim to be not useful or useful, but may workout for you:
shortening the path of zui rom from where it will be flashed: they recommend to past it directly to root of a drive
running the QPST Application with admin privileges which i would personally recommend
Disable Driver Signature Verification through out the process:
Click the Start Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.
You can search in google for more accurate steps, but one of the issue i faced was in latest version of window 10 i couldn't see the startup setting straight away. but at the bottom there is a link for additional option where you will find it.
[*]Downgrading to lower version or Upgrading to Higher Version QPST which for me, personally seems misleading and suggest you to stay with latest version
[*] and Last which i think made mine work, that is to reinstall Zuk Driver if there is an error which is persistent
HAPPY FLASHING
Anthony Finix said:
Ok after successfully flashing my zuk z2 plus this is what i have to say about sahara.
...
HAPPY FLASHING
Click to expand...
Click to collapse
A really simple solution is to use MiFlash @mi-globe.com/download-xiaomi-mi-flash-tool-all-versions instead of any others along with the Qualcomm QDLoader drivers @AndroidFileHost.com
I had the problem but when i flashed the proper firmware in order, the problem resolved itself
ps i used an old version of qfil 2.0.xxx or something idk
Related
Good to hear that Official Lineage OS 16 has been released for violet and so is TWRP but that's not issue....
The issue is that whenever I try to flash the ROM it shows *treble zip compatibility error*.....to get over this I also tried to delete the compatibility.zip file in the main ROM zip file...but nothing happened and it fails to flash the ROM showing process failed>error:7,I did try to look for a workaround by using the TwrpBuilder recovery and still the same issue pops up
can you guys pls help me get this over with?
Pls list down the instructions with the required zip/IMG files as well the links to these files,can you pls point out the issue as to why the error showed up....I mean since Qualcomm released the CAF files of Snapdragon 675 for further ROM development and knowing that violet's processor is the exact same 675 then why the compatibility error in twrp?
D.L.Tejas said:
Good to hear that Official Lineage OS 16 has been released for violet and so is TWRP but that's not issue....
The issue is that whenever I try to flash the ROM it shows *treble zip compatibility error*.....to get over this I also tried to delete the compatibility.zip file in the main ROM zip file...but nothing happened and it fails to flash the ROM showing process failed>error:7,I did try to look for a workaround by using the TwrpBuilder recovery and still the same issue pops up
can you guys pls help me get this over with?
Pls list down the instructions with the required zip/IMG files as well the links to these files,can you pls point out the issue as to why the error showed up....I mean since Qualcomm released the CAF files of Snapdragon 675 for further ROM development and knowing that violet's processor is the exact same 675 then why the compatibility error in twrp?
Click to expand...
Click to collapse
I think you can find help there. But first read OP
https://forum.xda-developers.com/redmi-note-7-pro/development/rom-lineageos-16-0-t3951524
Hi, after an error 7 when flashing a custom rom via recovery, I tried to flash the actual stock rom with MiFlash.
Tried it serveral time, get allways the error message as shown in the attachement.
Is there any solution?
robert_b said:
Hi, after an error 7 when flashing a custom rom via recovery, I tried to flash the actual stock rom with MiFlash.
Tried it serveral time, get allways the error message as shown in the attachement.
Is there any solution?
Click to expand...
Click to collapse
Re-download custom ROM again. Use file manager if needed. Most likely a corrupt download.
usgaap said:
Re-download custom ROM again. Use file manager if needed. Most likely a corrupt download.
Click to expand...
Click to collapse
I tried downloads from several places. This is not the reason for the problem, sorry.
robert_b said:
I tried downloads from several places. This is not the reason for the problem, sorry.
Click to expand...
Click to collapse
Hi Robert,
My apologies for the short answer earlier.
Your device does not seem te be bricked. Yet. At least, not with the info you provided thus far. I am guessing you already googled "MiFlash crc check fail." Some of the options were; use a different archiver, re-download, sideload, rename file and folder into short names or boot a custom recovery (instead of flashing) and install that way.
I've had this exact same problem before (see bottom of post), hence my short reply.
Do you have custom recovery? Can you tell me what happens if you flash custom ROM for the Mi Max 3 that way?
It seems your goals is to flash official. Out of the top of my head, you could also install Official Global ROM through adb & fastboot. This needs unlocked bootloader though if I'm not mistaken, not sure if that's the case here. Alternatively, you can try using another computer. Or don't use MiFlash.
My issue with installing Global ROM was that the first 85% of the download took 3 minutes. The last 15% 5 seconds. I downloaded from official site. Install gave CRC Check Fail everytime. I tried 3 times. Nothing seemed out of the ordinary. I then used a Google Drive link with matching size and details and everything worked like a charm.
I sincerely hope any of this helps. As with everything Mi Max 3 related, please be aware of arb. Sorry for the generic warning but you can never be sure.
Regards
Here used to be a bad guide please don't follow it I learned that people where rightfully pissed at me and I have decided to replace it with this Im gonna flash lineage again and document my exact procedure and try to make a better guide than the garbage I posted here.
error : can't load losq-v
hey man,
Thanks for the effort but I only got one problem that whenever I enter this command "fastboot flash system losq-v lineage.img" I get the error saying "can't load losq-v" so what should I do.
Thanks in advance
KFC99 said:
hey man,
Thanks for the effort but I only got one problem that whenever I enter this command "fastboot flash system losq-v lineage.img" I get the error saying "can't load losq-v" so what should I do.
Thanks in advance
Click to expand...
Click to collapse
The reason is losq-v is the start of the filename pretty sure you can just press tab and it will autocomplete so the command would be "fastboot flash system losq-v"(after losq-v type rest of your filename or press tab to autocomplete (do not add a space in between losq-v and rest of filename))
Sry for forgetting that I did it like that to future proof the guide
camera not working
kamilkamjy said:
camera not working
Click to expand...
Click to collapse
Well it should. Ask the guys in the a71 group
Can it flash on U3 ui2.5 or 2.1?
Blocklisted said:
Well it should. Ask the guys in the a71 group
Click to expand...
Click to collapse
LoL
Posting "tutorials" in XDA is something else than copy and paste things you expect to work but never tested yourself.
Two persons get in trouble by the crap you copy and pasted here, and instead of take responsibility when things go bad, the only crap you can say is: ask THE GUYS in telegram rofl
What age are you? 12?
I hope no one follow this crappy " tutorial" here...
Odin Recovery Fails
I go step by step but when I hit start on Odin to flash recovery I get two error messages
1. one in Odin in the log section with the following message "failed (auth)"
2. the other on the phone in the download mode in red something along the lines "you can only install official binaries"
I searched the forums and found a few suggestions, turning on USB debugging, applying magisk patches etc.... I never saw anyone confirming any method that would have worked. Whatever I tried to do it either didn't work or I couldn't do it because of lack of skills or it wasn't possible. For example when I tried to use magisk in the descriptions I had install buttons in the manger but I'm missing these on my phone so I suspect that recovery is required first to make those patches or there's something that I don't know how to do it. Either way following the instructions doesn't work for me and I tried a bunch of things and none worked. Different versions of Odin 3.14.1, 3.14.4. If anyone has any idea please help. I reset the whole phone to factory hoping it would help, there's no data on it right now but I still get the same error.
Thanks
rb1979 said:
I go step by step but when I hit start on Odin to flash recovery I get two error messages
1. one in Odin in the log section with the following message "failed (auth)"
2. the other on the phone in the download mode in red something along the lines "you can only install official binaries"
I searched the forums and found a few suggestions, turning on USB debugging, applying
《Cutting》
Either way following the instructions doesn't work for me and I tried a bunch of things and none worked. Different versions of Odin 3.14.1, 3.14.4. If anyone has any idea please help. I reset the whole phone to factory hoping it would help, there's no data on it right now but I still get the same error.
Thanks
Click to expand...
Click to collapse
To back to original Android:
-Odindownload.com last Odin
- https://github.com/ivanmeler/SamFirm_Reborn/releases download samfirm reborn and use it to get latest original Samsung firmware
Unzip it with 7-ZIP !!!!!! www.7-zip.org
On the Odin website there is a YouTube video how to proceed. But do NOT use any PIT file you find somewhere like the vid shows in example, you will almost for sure brick it if you don't know exact exactly what you r doing! Be warned!
After unzipping you see files beginning with AP BL CP CSC , put them in Odin where they should be.
Under options ONLY mark AutoReboot and F reset time and nothing else.
I hope you get your phone back to working state with this, remember you will not be able to get updates OTA any more since you broke the Efuse.
From there on if I were you I only would root the phone and wait till official TWRP is out, or hopefully some day an official LineageOS.
So far nothing official means lack of maintanance after a while, no updates, bugs, bad assistance and more crap, just like this thread is written by someone who gathered info from just here and there and made this "tutorial" with copy and paste and added b.s. for trying to become a star on Telegram-ish group and look populair there.
Just Root it, debloat it and live with it.
andreoide said:
To back to original Android:
-Odindownload.com last Odin
- https://github.com/ivanmeler/SamFirm_Reborn/releases download samfirm reborn and use it to get latest original Samsung firmware
Unzip it with 7-ZIP !!!!!! www.7-zip.org
On the Odin website there is a YouTube video how to proceed. But do NOT use any PIT file you find somewhere like the vid shows in example, you will almost for sure brick it if you don't know exact exactly what you r doing! Be warned!
After unzipping you see files beginning with AP BL CP CSC , put them in Odin where they should be.
Under options ONLY mark AutoReboot and F reset time and nothing else.
I hope you get your phone back to working state with this, remember you will not be able to get updates OTA any more since you broke the Efuse.
From there on if I were you I only would root the phone and wait till official TWRP is out, or hopefully some day an official LineageOS.
So far nothing official means lack of maintanance after a while, no updates, bugs, bad assistance and more crap, just like this thread is written by someone who gathered info from just here and there and made this "tutorial" with copy and paste and added b.s. for trying to become a star on Telegram-ish group and look populair there.
Just Root it, debloat it and live with it.
Click to expand...
Click to collapse
Thanks andreoide for your honest answer :good:
My phone's working, I didn't get far with it, never broke it, just unlocked it. I guess the installation failed during the validation before actually doing any physical changes because my Samsung stock system still runs. The phone is given to me by my company. I just took out the sim card and put it in my private dual-sim phone. So this phone is on the shelf, it's been there for the last few months. I wish I could use it it's higher end than my personal but can't deal with Samsung stock system. I had two phones with lineage (and whatever the name was before) and loved it so I'm hoping I can use it again.
Anyway, it was just explaining my situation, I guess I'll be checking this forum and hoping for more positive news. Meanwhile the phone goes back on the shelf and waits for better times, thanks again for straitening things up for me. :good:
Blocklisted said:
Here used to be a bad guide please don't follow it I learned that people where rightfully pissed at me and I have decided to replace it with this Im gonna flash lineage again and document my exact procedure and try to make a better guide than the garbage I posted here.
Click to expand...
Click to collapse
Well, since you come clear and admit the guide you posted before was pure crap, i have to rise my thumbs up to you.
I think this is a mature respond.
:good:
good evening. hopefully someone can help. i jodated to android 14 ( Bad idea ) and was having a lot of problems so went to go back to 13 and then asked me to format. i deleted and cleared everything including the data. completely empty. i can get into fastboot and recovery though. thats it. tried to put factory 13 build on but nothing. cant get past fast boot. any help would be greatly appeciated
use flash.android.com
Faszfreddy said:
good evening. hopefully someone can help. i jodated to android 14 ( Bad idea ) and was having a lot of problems so went to go back to 13 and then asked me to format. i deleted and cleared everything including the data. completely empty. i can get into fastboot and recovery though. thats it. tried to put factory 13 build on but nothing. cant get past fast boot. any help would be greatly appeciated
Click to expand...
Click to collapse
Druboo666 said:
use flash.android.com
Click to expand...
Click to collapse
^^^this...exactly what I was going to suggest. This will get you back up and running...
Or one can also use pixel flasher... Right?
amritpal2489 said:
Or one can also use pixel flasher... Right?
Click to expand...
Click to collapse
Flash.andriod.com can do more than pixel flasher. have had the same issue with my phone seemingly dead being brought back to life using that website. (note i haven't tried andriod 14 it was when a rom flash went wrong)
amritpal2489 said:
Or one can also use pixel flasher... Right?
Click to expand...
Click to collapse
PixelFlasher does have a lot of the same capabilities as Android Flash Tool, but PF is more for rooting/kernel/ROM flashing than it is for recovery purposes -- which is the primary reason for AFT. PF has various different checks and protocols, while AFT has protocols more for properly flashing/resetting device to stock or recovery repair.
So while PF can flash the stock Full Factory image (to both slots and/or platform-tools checks and/or adding various arguments [without wiping, disabling verity&verification, etc.]), AFT links directly to Google's developers page that holds the Full Factory images and works just on flashing those.
Flash Tool saved my butt after I flashed the wrong kernel...
Visit this site on a PC, edit the settings and check the boxes 'wipe' and 'force flash partitions'
Android Flash Tool
flash.android.com
simplepinoi177 said:
^^^this...exactly what I was going to suggest. This will get you back up and running...
Click to expand...
Click to collapse
i tried this it cant find anything to install
Faszfreddy said:
i tried this it cant find anything to install
Click to expand...
Click to collapse
It's not a tool you install...it's all "run" through what browser you are using (Chrome, Firefox, Edge, etc.).
You click "Get Started", make sure you download and install the USB Drivers it suggests you should (if you have already, you can click "Already installed"), allow the browser "ADB access", click "Add new device" and then it will wait until you connect your device to the computer and the tool (within the browser) will detect it and continue on from there...
Try to particularly read & pay close attention to any steps or suggestions the site states as it will assist in connecting and/or any problem/troubleshooting you might need to do to get it working with the tool...
simplepinoi177 said:
It's not a tool you install...it's all "run" through what browser you are using (Chrome, Firefox, Edge, etc.).
You click "Get Started", make sure you download and install the USB Drivers it suggests you should (if you have already, you can click "Already installed"), allow the browser "ADB access", click "Add new device" and then it will wait until you connect your device to the computer and the tool (within the browser) will detect it and continue on from there...
Try to particularly read & pay close attention to any steps or suggestions the site states as it will assist in connecting and/or any problem/troubleshooting you might need to do to get it working with the tool...
Click to expand...
Click to collapse
this is all it will do. keeps trying to find a build to flash
Faszfreddy said:
this is all it will do. keeps trying to find a build to flash
Click to expand...
Click to collapse
Had you checked what's under that pull-down option (down arrow) on the right of your device ("Pixel 6 Pro (raven)")? or searching "raven" in the search box?
In any case, I went ahead and searched the latest (non-Verizon) build number for your device (raven), and you should be able to find the latest (May Full Factory Image) as: TQ2A.230505.002.
If you are using your device on Verizon's network, the "build" would be: TQ2A.230505.002.G1
These will update it to Android 13 (latest); in case you are still on Android 12 and/or do not wish to upgrade (for whatever reason).
simplepinoi177 said:
It's not a tool you install...it's all "run" through what browser you are using (Chrome, Firefox, Edge, etc.).
You click "Get Started", make sure you download and install the USB Drivers it suggests you should (if you have already, you can click "Already installed"), allow the browser "ADB access", click "Add new device" and then it will wait until you connect your device to the computer and the tool (within the browser) will detect it and continue on from there...
Try to particularly read & pay close attention to any steps or suggestions the site states as it will assist in connecting and/or any problem/troubleshooting you might need to do to get it working with the tool...
Click to expand...
Click to collapse
thank you. Android Flash Tool fixed it thanks again guys
Hi everyone, I have a problem in the downgrade procedure to emui10 of a matepad pro (MRX-W09), using hisuite and hisuite proxy the rome is downloaded correctly but then the installation fails, i attach the hisuit log file with errors.
Can everyone help me?
Thanks
lele78c said:
Hi everyone, I have a problem in the downgrade procedure to emui10 of a matepad pro (MRX-W09), using hisuite and hisuite proxy the rome is downloaded correctly but then the installation fails, i attach the hisuit log file with errors.
Can everyone help me?
Thanks
Click to expand...
Click to collapse
I managed to complete the installation from hisuite but now the installation from the tablet fails, furthermore hiproxy as soon as the download finishes gives me a message that says "Apparently Firm(s) is/are not approved for installation and proccess will most likely fail in phone. You might want to consider canceling it to avoid time waste." I have tried several roms but they all fail.
Can anyone help me?
lele78c said:
I managed to complete the installation from hisuite but now the installation from the tablet fails, furthermore hiproxy as soon as the download finishes gives me a message that says "Apparently Firm(s) is/are not approved for installation and proccess will most likely fail in phone. You might want to consider canceling it to avoid time waste." I have tried several roms but they all fail.
Can anyone help me?
Click to expand...
Click to collapse