well .. I messed up my 5x and sent it to be fixed and everything was fine but when I tried to install linageos 16 or any custom rom the phone did not pass the logo or it threw error 7 or 1 (in twrp 3.4.0-0) and when I came back to the factory rom I have the following errors:
-my ROM goes from 16GB to 2GB to use
-my serial number appears in 00000000
-my bluetooth works halfway since I can't send or receive files or connect to devices
I also want to highlight that I am using the stock rom of the KIW-24 being that mine is a KII-L33 (I use that since I did not find the original on the internet)
thanks in advance and regards <3
What a risky action you did
I found this guide for flashing stock rom (using QFIL tool) on your device (not tried myself also not having this model so be careful)
Guide: https://aiomobilestuff.com/stock-rom-huawei-gr5-kii-l33-firmware/
Firmware download link (found these two):
https://androidfilehost.com/?fid=11410963190603860740
http://www.mediafire.com/file/y8eru...6_Chile_EMUI_3.1_05021WXE_5.1.1_QFIL.zip/file
Do it at your own risk !!!
Related
hi , today i'm bringing to you a new marshmallow rom for this device.
link and screenshots : https://goo.gl/GVSrzK
How to flash :
1-download the firmware package to your pc , and extract it
2-download latest sp flashtool ,open it and choose scatter file from you extracted firmware:
link: https://mega.nz/#!u1ZwCCrI!_s3eHJdJykRLyInH8BDy-SFiH3VqJU4BTG2yo9DZ8HM
3-select “download only” and DON’T select “userdata” (by selecting “download only” you will not loose emei , and by unselecting “userdata” you will not loose you internal storage files, so be carefull )
4-press start , and power off your device and plug it in , wait till it finishes (green image shows up) ,unplug and power on your device, that’s all
Don't forget to hit thanks
Rom informations :
Android Version : android marshmallow 6.0
Kernel Version : 3.18.19
Rom release : version of october 27th, 2016
Credits:
me : for porting it to this device
zoppo : for the firmware
gionee s plus/s6 facebook group
Only getting 1.45 gb of storage on my blu vivo 5, not sure what I did wrong. But I can go back to this BLU_V0050UU_V09_REPAIR and it has the full amount of storage.
work fine with me , are you sure
see attachment
This rom NOT recognize my IMEI / SIM card...
What did I do wrong?
yeah I am sure the the storage was only showing a total 1.45gb, and I also messed up my IMEI, slowly looking at trying different things to get it straightened out.
Really looking forward to getting android 6.0, hope I can figure it out soon.
thanks
Ok I got gionee s6 stock on it and did the ota update and that is working and showing the full 32gb. Now i just need to fix my imei and maybe see if i can put asop on it and still keep it working.
Sent from my SM-G920F using XDA-Developers mobile app
Gaidheil said:
Ok I got gionee s6 stock on it and did the ota update and that is working and showing the full 32gb. Now i just need to fix my imei and maybe see if i can put asop on it and still keep it working.
Click to expand...
Click to collapse
see "how to flash?" if you didn't already do that
Any mirror? Google Drive maybe? Mega doesn't play well with VPNs.
Lost IMEI and storage shows weird. I hope it didn't corrupt my backup. Did exactly as told. Trying to download stock Gionee S6 now.
Edit: Got storage working coming from Gionee S6 software. Still no IMEI though. SN Writer didn't work, and MAUI didn't detect my phone. App-based solutions (such as engineermode) didn't work as well.
any one can tell me if it work for gionee s6s clone (condor A8, blu vivo 5R, qmobile z12 pro)
we realy are in need for aosp for gionee s6s qmobile z12 pro
so by clones do you mean phones like the 5R? im sorry for the newb question but i cant seem to find an answer
Note for others attempting this ROM: In order to get SD card storage right, you need to be on stock Marshmellow prior to flashing. Stock Marshmellow (through OTA) will reformat the sdcard storage into Marshmellow's way of doing things, and then the card storage will show up as 32 instead of 1.5GB.
I'm still missing IMEI and am unable to obtain root now. I can flash TWRP and do backups, but when I flash SuperSu it works but root is not obtained. Any ideas about how I can solve both so I can run with this ROM on the Blu Vivo 5?
Why is the download in 4 parts?
Hello , Guys
Since you all probably know, Lenovo A7020a48 has Android 6.0 Marshmallow which cannot be rooted because of the following :
1 - We got a locked bootloader, we can't flash or boot into custom recoveries and sadly at the moment I couldn't find a way to unlock it.
2 - We don't even have a custom recovery made for that model yet, I tried different version of TWRP for A7020a40 ~ A7020a46 models and they all crashed upon booting to them.
3 - Kingroot and similiar apps can't root Android 6.0.
So the only way to root your phone would be to downgrade it to Android 5.1 Lolipop which is easy.
Here is download links for the stock roms :
A7020a48_LL_S125_160419_ROW.rar.7z
A7020a48_S259_160721_ROW.7z
When you finish downloading please don't forget that we are going to use the SP Flash Tool provided in the rom as only that version "SP_Flash_Tool_5.1552.00" worked for me with no errors however with latest versions i got problems.
Obviously you are going to install the USB drivers and CDC drivers located at the "DRV_Tools" folder in the rom you downloaded.
after installing the drivers correctly turn off your phone, open SP flash tool, and choose the scatter file located at : "\SW\target_bin\MT6755_Android_scatter.txt" and then choose "Download Mode" then wait for it to finish checking the files, then click on the download button on the top left corner.
Then connect your device and wait for it to detect the device .
Wait until the flashing is complete Then After the green circle appears, simply disconnect your phone and boot into system normally.
Note: You might see a black box in the bottom left corner saying "efuse flash done or similar stuff" don't worry about it" it won't appear again however if you got an error saying "DL image failed" then you did something wrong repeat the previous steps again and make sure you choose everything correct especially your rom.
Now to the last part, finish the first time setup screens by skipping most of them and DO NOT UPDATE YOUR SYSTEM AT ALL
if you got a notification to update, simply ignore it or press cancel, and open google chrome, download king root and wait for it to simply root you phone.
Congratulations that's the first part for rooting your phone.
Now to Fixing Your IMEI
Simply Enable USB debugging in options and enable OEM unlocking.
Then power off your phone.
Download this tool : MauiMETA_v9.1635.23.rar
Yes Again it has to be that specific versions, with other versions i couldn't connect to my device however with this version i could.
Extract it to a random location on your pc and MauiMeta.exe and click on options and enable "enable composite kernel usb (adb)" then click on reconnect.
Now you have to connect your device with usb and turn it on, don't worry MauiMeta will change the boot to META mode automatically after it starts booting leave it as it's and wait for the tool to connect to your phone.
***After it connects simply choose IMEI download and a new window should appear, first click on upload from flash button then click yes to retrieve the modem file from your phone, then simply type your IMEI ( Please note that changing your IMEI is illegal however you should only use this method to fix your IMEI not change it ! , you have been warned)
Note : IMEI numbers should be 15 numbers however with MauiMeta you should only type the first 14 number as the 15th number is only a checksum number and will be added automatically.
After typing the IMEIs and checking them simply click on download to flash.
After it says "flashing is successful" then close the window and click Disconnect, and your phone should turn off automatically and you should start it up again.
*** Note : If you have a corrupted NVRAM file on your phone then you are lucky since that rom comes with the modem db file as well to fix NVRAM issues, simply click "Change NVRAM database file" then click No to choose the file, The file exists in the ROM package you downloaded earlier in the following location : "SW\modemdb\MDDB_InfoCustomApp....etc.EDB" and continue the rest of the steps normally.
Please Note that I won't provide support for this, I have only created this tutorial to save time for other people and I'm not expert yet to fix all the problem you may face however after following these steps i managed to root my device and even fix the invalid imei errors i got.
Also if you found errors in my thread or mistakes Please let me know so i can fix them.
Good luck and Don't hard brick your phone XD
I get this error in SP FLASH TOOL 5.1552.00- STATUS_SEC_PL_VFY_FAIL (-10*****)
Any idea ?
Error coming?
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
nishkarshxda said:
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
Click to expand...
Click to collapse
Use This Version Of Flash tool enable usb and storage checksum hit download ( Use different usb port better use backside of CPU )
Sp-flash-tool-V5-1548
10000% Working
mobile not getting switched on after downgrading
Hi, I tried to flash my Lenovo vibe K5 note (a7020a48 4 GB RAM). It was done without any error but I couldn't switch on my mobile nor it was detected in my computer. Please help me
Bro i download and flashed successfully but phone cant turn on but i flashed again marshmallow phone will turn on...Why lollipop cant boot... Second link for rom is lollipop or not
Any proof?
Bro where did you get these two rooms from? Tell us the source. Otherwise, how will we know?
after flash mobile no on anybody can u help me to how to flash 5.0 in lenovo k5 note
It worked great thanks .......though minor glitches may occur such as not playing any sound and not supporting JIO sim card. These can be fixed by System Updating your phone to the latest version preferably through a sound wifi connection.
Code:
**** DISCLAIMER ****
This post is an EXPERT-LEVEL Post.
I am NOT RESPONSIBLE for what you do to your device.
Please not that I am still working on a solution to this brick.
Hello XDA-Developers,
I recently got my hands on a Meizu M3 note and, of course, wanted the newest - nougat - firmware on it. It seems I accidently flashed a incompatible (or currupted) Update (flashed an A Firmware on a G version phone). Sadly it broke down and showed only vertical stripes on it's display.
Image here: https://ibb.co/cpGunm
After some hours research I found some information on how to reflash the M3 note via SP Flash Tool here and here. Since the first tutorial is for the M3 and M3s and the second tutorial is for the M model of the device (I've got the L model) there are some changes needed for it to somehow magically work.
I exchanged files provided (such as preloader.bin, lk.bin etc) with the matching ones from the latest Official Global Firmware from Meizu. Just extracted them out of the update.zip. (Don't forget to select the Authentication File!)
Image here: https://ibb.co/k3zYDR
Short flashing tutorial: make sure your device is turned off and disconneced then click "Download" and connect your device via USB. Don't worry if it now shows an error like "Download DA Failed", just dismiss the error and click "Download" again. It should flash the device now.
Sadly it is not possible to flash the boot.img provided in the latest official update.zip from Meizu (you'll get an security mismatch error). BUT the boot-verified.img provided by the chinese archive is flashable and is accepted by the device. The device is now in a bootloop, fastboot is accessible via holding Vol - and Power, but no recovery access via Vol+ and Power
The files seem to be repaired now but the display still shows these stripes - I think the firmware actually fried something on the display chipset. I bought a replacement screen and then will update this thread as soon as possible. If you have any Ideas of how to unbrick the device feel free to discuss.
Update 18.11.2017
Thanks to @ncristian !
I did as he suggested, downloaded and flashed the files from the russian forum here (if you do not speak russian and want to get straight to the point: Direct Download Link)
I still have the stripes on my screen but the device booted up successfully and got recognized again by my computer! While booting up I could see the stripes changing their color slightly as the bootanimation of flyme was playing. I guess I will have to replace the screen to make the display error go away... I will update this post as soon as I did so
Update 10.11.2018
Sadly I never actually exchanged the screen, I'm running a Pro 7 Plus as a daily driver now and I'm loving it
Update 19.05.2019
I have attached the boot-verified.img as someone requested it
I had the same problem and I solved thanks to this: https://4pda.ru/forum/index.php?showtopic=739028&st=24480#entry65580668 and Google Translate; I downloaded the .zip, installed drivers, launched the flash tool and flashed files contained in the folder L691H (Remember to install drivers and disable antivirus or it will not work). Then I downloaded FlyMe 6.1.0.0G, went into recovery with vol up + power, copied the update.zip into the device "Recovery" and flashed it; the only problem I had is that the phone charged but he didn't recognize the battery level; by reflashing the files contained in the 4pda .zip, the battery level went up (obviously, after leaving the phone charging for about an hour).
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Rajdas26 said:
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Click to expand...
Click to collapse
Try reflashing via the original recovery, that might be your easiest solution. If that doesn't work you might try your luck with something like SP flash tool
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
shawn_mendes said:
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
Click to expand...
Click to collapse
I have attached the file to the first post. Good thing I never delete anything :angel:
m3shat said:
I have attached the file to the first post. Good thing I never delete anything :angel:
Click to expand...
Click to collapse
First of all, thank you mate I successfully downloaded the boot verified. But still it didn't turned on. Just no power but recognized by the sp tool. I'm starting to think that downloaded again the wrong firmware. I also found out that their are two main board(or whatever is that). So this global firmware can be flashed in the both L and M series. I'm wondering what firmware you used to flash. Again, thank you in advance ^_^
l got same problem .. (because I'm not read careful )l tired to flash using many firmware or using boot verified .. i tired that for 2 Days.. So l give up.. take my device to profesional service . and solved. solved with Emmc repair ..
my device is L681H.
Hello everybody I am after some help please.
I own an Abox a1 plus android box s905x. Somehow the original firmware became currupt but there are no original firmwares on the net that I can find to get this box up and running again. With this said i have managed to get it running again through trial and error with a different rom.
The only thing is I am in need of the original remote.conf file to get the remote working again can anybody help as I fear i have run out of options.
Hi, Same request, i have remove many apps on original firmware and don't work after reboot, i flash nexbox 7.1 firmware all work fine but miss remote.conf original (Abox A1 plus 8gb/2gb - s905x, firmware original is marshmallow).
Thanks in advance.
djmagma59 said:
Hi, Same request, i have remove many apps on original firmware and don't work after reboot, i flash nexbox 7.1 firmware all work fine but miss remote.conf original (Abox A1 plus 8gb/2gb - s905x, firmware original is marshmallow).
Thanks in advance.
Click to expand...
Click to collapse
This exactly the firmware I got my Abox A1 plus running with too. It works brilliantly with no mods. I just needs that remote.conf file afaik.
I can't get any firmware to work on my Abox A1 Plus. It always gets stuck on the logo. Where did you download your firmware from?
samuau said:
I can't get any firmware to work on my Abox A1 Plus. It always gets stuck on the logo. Where did you download your firmware from?
Click to expand...
Click to collapse
Hi, take one firmware here but respect your memory configuration (2Gb ram and 8 Gb rom = 2-8G).
mega.nz/#F!F9xjTSSa!R0vJfTC2U6Qc2skNMrr1iQ!hlJDxRxQ
(add https before for full address, i don't have acces post link ^^ )
But if you have original again work backup your remote.conf in system/etc/, or remote dont work after upgrade. (and if you can backup, please post here your remote.conf file) thanks.
Sorry for bad english, i'm french.
Edit : I search for repair and i found we don't have a remote.conf but our file named remote_mouse2.tab
i found my factory code via dmesg –c on ssh and it's recognized, now i remap function one by one
The power on keycode is hardcoded in bootloader (and with this rom is different from original). All key work but if box off, power on with remote don't work.
Delete this please :/
djmagma59 said:
Hi, take one firmware here but respect your memory configuration (2Gb ram and 8 Gb rom = 2-8G).
mega.nz/#F!F9xjTSSa!R0vJfTC2U6Qc2skNMrr1iQ!hlJDxRxQ
(add https before for full address, i don't have acces post link ^^ )
Click to expand...
Click to collapse
Thanks for the link djmagma59! I already tried this specific firmware, but I get the burning tool error at 98% (see above). I'll try again tho. If I install the 6.0 version of the firmware the installation goes through, but the box gets stuck on boot (logo).
Did you have any issues installing it? Any ideas for me to try to solve it?
Again, I appreciate the help.
Hey I don't know if you still need it but I was looking for help myself and foud this thread, I have this box, it came with with 7.1.2 tho, I'm attaching the remote.conf file for you.
Need Basic Help for Resolving REboot Problem
Hi All,
I am facing loading my Abox A1 Plus . The screen is stuck reboot (bootloading). I can see options like Update using EXT , Update using ADB and so on. I tried Loading Zipped img files onto the USB and then update using EXt. But getting Signature Verification Failed Error. What are the basic steps as I could not find my device even after using AMLogic USB Tool.
Thanks in Advnace
Hi there, if you don't mind please read carefully what I write below.
I really need help on flashing Vsmart Joy 1 Plus (PQ4002) stock Vsmart OS 2.0 (VOS) - android 8 firmware.
This is device info: https://www.devicespecifications.com/en/model/92b24f11
Story begin when I was on VOS 2.5 - android 9. After running these stock firmwares of it through Miracle Box + QFIL, the phone NEVER turn on at all, remain as HARDBRICK no matter I trying to flash it. QFIL still report as "Succeed" result, no error, but still brick. So far I have tried these sources:
1. https://www.fshare.vn/file/6E9QOWBIF8N9
2. http://www.mediafire.com/file/lgh7g..._1_Plus_PQ4002_8.1.0OPM1.171019_QPST.zip/file
3. https://www.fshare.vn/file/QJ6Y244X29T2
None of them worked. I even took this phone to warranty center but they claimed broken emmc somehow. Furthermore, I format all partition table in QFIL, still no help.
But when I flash this Infinix HOT S3X X622 firmware, it worked https://firmwarefile.com/infinix-hot-s3x-x622; because PQ4002 and X622 identical hardware specification.
So my question is what I have to do to flash the original firmware? Something wrong with it?
Update: i solved myself after found the correct QFIL firmware and android 8 fastboot firmware for it.