yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] necoe66:
Did anyone try? :(
[SuperSU] xpintus:
MOD EDIT: Get SuperSU v-2.79 from https://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 instead. No need to duplicate and to point to another URL
[One (ME) General] zuhairqadir:
Hi:

I have pretty much explained my position in header. so i rooted my htc one me m9ew and on restart it went to bootloop. i flashed recovery from there. now even if i try to flash any rom its still on bootloop. keeping in mind my bootloader is unlocked and S-ON. what should i do? any way to keep this phone alive?
[One (ME) General] king786:
Try Htc Ruu or the software from Htc i thinknit might be emergency flash but theirs something like that
[One (ME) General] zuhairqadir:
Thanks King:

I have managed to install custom ROM basically designed for HTC One M9+ since there is no custom rom for htc one ME edition. this new clean slate rom gives no signal and very buggy. in short i cant run normal phone operations on this rom. i tried installing RUU from htc_fastboot but it gives error 19 and i am unable to flash. i have tried many sources for this RUU file but in vain. any suitable suggestions to make this phone operational will be highly appreciated.
[One (ME) General] zuhairqadir:
One more thing, do i need to relock bootloader to flash firmware???? getting following error:

(bootloader) HOSD CL#549681

(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED

(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19

(bootloader) ERR Update zip file failed.

(bootloader) ERR ZIP ERROR, exit read zip loop

(bootloader) ERR ZIP signature checking failed...

(bootloader) Update zip file OK

(bootloader) ERR ZIP ERROR CODE, 19

(bootloader) end@Done

FAILED (remote: 19: fail to flash via downloadzip)
[One (ME) General] king786:
Try installing something through recovery another functional rom might not be what u want but get that running and then do what u are trying or try its recovery menu.

One of those should work if not try to look for a solution in one of the threads must be something here
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] rberk:
​

Lenovo Vibe K4 Note

​

Hi,

Here is AICP - 12.1 7.1 for the Lenovo Vibe K4 Note

How to install:

From stock or any other rom

Copy the ROM zip on your phone

Reboot to Recovery mode

Format/Wipe system, cache, dalvik, data

Flash/Install ROM

Flash Install Gapps (Any should work)

Reboot

Bugs

Camera 8MP

Stock Video Cam wont work (3rd party video cam works)

Camera with flashlight wont work

No volte

Downloads:

ROM

Gapps

XDA:DevDB Information

AICP-ROM 12.1, ROM for the Lenovo Vibe K4 Note

Contributors

rberk, Teja.K

Source Code: https://github.com/AICP

ROM OS Version: 7.x Nougat

Based On: AOKP, CyanogenMod, Omni-ROM, DirtyUnicorns

Version Information

Status: Stable

Created 2017-04-15

Last Updated 2017-04-15
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] Aarkay0804:
Does it have Volte and Substratum support??
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] lalit387:
Have you read op?
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] edarick:
whats next?
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] rberk:
what whats next?
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] lalit387:
Calm down buddy just a curious kid spamming every thread...

Ignore pl we know you let us informed about any progress.
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] edarick:
yeah any new update to your rom?
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] rberk:
Haha... If any new update come. i sure will update the links.
[Huawei P9 Questions & Answers] Mangono:
Hello,

My P9 is completly Wiped and wont install any Data with dload everytime i try it shows update failed.

I have the Bootloader Code, but the FRP is Locked and i cant unlock it with the DC Unlocker i tryed. The DC Unlocker showed me that my Last Firmware was : EVA-L09432B182

So how can i reinstall my Firmware or which file i should use... please help me

Thank you
[Huawei P9 Questions & Answers] darrr1:
First try upload full c432b136.

Wysłane z mojego EVA-L09 przy użyciu Tapatalka
[Huawei P9 Questions & Answers] Mangono:
I tryed but it says update failed......
[Galaxy S 5 Q&A, Help & Troubleshooting] jdubu420:
Hey guys, so I am sick and tired of the Honor 5X. So I sold that stupid thing and got an S5 as I've used them before and loved them, much snappier.

I'm all about performance. What can I / should I do to make the S5 as fast as possible. Are the custom roms faster? Should I just use Nova Launcher and leave the rest alone? Any recommendations are greatly appreciated.
[Galaxy S 5 Q&A, Help & Troubleshooting] Saber:
Custom ROMs makes my s5 feel snappier when opening apps, navigating UI feels much smoother and switching between tasks is quicker. You do lose some gaming/3d performance because of frequency scaling issues, but if that doesn't concern you too much, you should try either LineageOS or Resurrection Remix Nougat. Both are great options.

As for general bugs, camera lacks 4K recording and HFR (camera app crashes). Three loud beeps can be heard when people hang up during phone call. There are other issues as well but that's what I can think from the top of my head ;)
[Galaxy S 5 Q&A, Help & Troubleshooting] jdubu420:
Thank you for the advice.

The camera is a big deal to me, so I don't want to lose that functionality. I won't be using it for gaming though.
[Galaxy S 5 Q&A, Help & Troubleshooting] koragg97:
I'd advise you to stay on an official Samsung firmware (with no bugs and with a lot of exclusive features) and then install Greenify, Amplify and their xposed modules as well as to try out Boeffla Kernel. My S5 is snappier than ever with my current setup which you may see in my signature below this post. Cheers ;)
[Galaxy S 5 Q&A, Help & Troubleshooting] mrafigf:
Try this. It's custom ROM based on stock ROM without loosing stock camera funcionality.

https://xdaforums.com/galaxy-s5/development/rom-superlite-mini-mm-v1-0-361mb-g900w8-t3497158

I've been using it for couple of months. Combined with Boeffla kernel, Xpossed framework, amplify, greenify even viper4android sound mode, it comes with the best performance for me.
[Galaxy S 5 Q&A, Help & Troubleshooting] jdubu420:
I'm not much into greenify/amplify. Never noticed much difference from using them. Xposed is super useful no doubt.

I'm very interested in Boeffla Kernel. Seems like it might definitely be worthwhile.
[Galaxy S 5 Q&A, Help & Troubleshooting] mrafigf:
Yes, it may be fair enough to just try SuperLite ROM as it does not include bloatware found in original stock rom. Then use Boeffla Kernel.
[ZTE Axon 7 Questions & Answers] Fazedyrus:
can anyone provide the stock weshare apk? My titanium backups are corrupt on Lineage and I would like to restore my WeShare ones
[ZTE Axon 7 Questions & Answers] jimbo77:
You can download it from Aptoide
[ZTE Axon 7 Questions & Answers] Fazedyrus:
Thanks !
[Moto Z Guides, News, & Discussion] Manish54:
.

.

.

.

HOW TO UNBRICK A HARD BRICKED MOTO Z XT1650-03

Note: This is only for Moto Z XT1650-03. Don't use this for any other device, i'm not responsible if anything happens to your device.​

My Moto Z died in January because of flashing a wrong file and it wont power on or charge. And the service center wont help because Motorola voids your warranty the moment you get the unlock code from their website. So i kept digging for 3 months and finally my phone is back from the dead. And i'd like to help other people who are struggling with the same problem.

So, things you'll need:

-A dead Moto Z with no boot/charging at all

-Drivers

-Blankflash file

-Stock Rom/Custom Rom

How To Unbrick:

Step 1: If your PC detecta the phone as QUSB_BULK device, install the drivers provided. If it detects it as qualcomm device 9008 or something, then move directly to step 2.

(If your PC is not detecting your phone then try removing the battery and then plugging it back on. Connect to the PC and press the power+volume down button for 2 minutes. Keep trying this this with different USB ports until the PC detects it.)

Step 2: Now extract the blank flash file and run the 'blank-flash.bat' file. Your phone should boot into fastboot now.

Step 3: Now you can flash your stock ROM or any custom ROM. I suggest you flash TWRP and boot into recovery and flash a custom ROM first. And then flash the Stock ROM later if you want to because flashing stock rom is very tricky in Moto devices and you can end up screwing your device even more during the hardbrick phase.

Cheers :highfive:
[Moto Z Guides, News, & Discussion] martonto:
Thanks, dude, but it didn't work.

My phone is listed in device manager as qualcomm hs-usb qdloader 9008, but when I try to run the batch script it fails.

Here's the log, if it helps:

**** Log buffer [000001] 2017-04-15_15:21:57 ****

[ 0.000] Opening device: \\.\COM4

[ 0.000] Detecting device

[ 3.001] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error

[ 3.001] Check qboot_log.txt for more details

[ 3.001] Total time: 3.016s

[ 3.001]

[ 3.001] qboot version 3.37

[ 3.001]

[ 3.001] DEVICE {

[ 3.001] name = "\\.\COM4",

[ 3.001] flags = "0x64",

[ 3.001] addr = "0x61FE5C",

[ 3.001] api.bnr = "0x8E2C38",

[ 3.001] }

[ 3.001]

[ 3.001]

[ 3.001] Backup & Restore {

[ 3.001] num_entries = 0,

[ 3.001] restoring = "false",

[ 3.001] backup_error = "not started",

[ 3.001] restore_error = "not started",

[ 3.001] }

[ 3.001]
[Moto Z Guides, News, & Discussion] Manish54:
Try a different port. And avoid USB 3.0 ports
[Moto Z Guides, News, & Discussion] martonto:
Still no go. I've been looking for another solution, but I'm yet to have any luck.

It seems there's a qualcomm utility to fix this called BordDiag, but I haven't found one that supports the msm8996 chipset.

Thanks, anyway!
[Moto Z Guides, News, & Discussion] martonto:
Solved!

It finally worked! I've managed to boot into fastboot mode and flash my ROM. My moto Z is now working again!

If anyone ever happens to come across the same error I mentioned in my previous post, there's a trick to solve it that I found in another thread:

Keep your mobile connected using USB, obviously.

2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.

3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.

source: https://xdaforums.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016

Thank you again, Manish54! I wouldn't have done it so soon without your help.
[Moto Z Guides, News, & Discussion] Manish54:
You're welcome :D
[Moto Z Guides, News, & Discussion] twitchfidelis:
Hello. I have a Sheridan XT1650-03 that I cannot get your fix to work for. I had the Motorola drivers installed so my phone appeared as a "Motorola ADB Interface" in the device manager. When I ran your batch file it hung on "waiting for device" and no matter what USB port I plugged into, 2.0 or 3.0, it's stuck at "waiting for device". So I manually uninstalled the Motorola drivers and forced the install of the drivers you provided so that my phone appears in device manager as "Qualcomm HS-USB QDLoader 9008". Same problem no matter where is plug it in. I have tried this on two different computers with the same result. Can you help me get past "waiting for device"?
[Moto Z Guides, News, & Discussion] Manish54:
Are you getting the same "waiting for device error even are it's on Qualcomm..9008 mode?

Do you have universal adb drivers installed?
[Moto Z Guides, News, & Discussion] twitchfidelis:
I am unclear on what you mean by Qualcomm..9008 mode. I have installed the drivers you provided and the phone appears as Qualcomm HS-USB QDLoader 9008 in Device Manager, but still the batch script hangs on waiting for device. The phone is in fastboot bootloader mode, is there a seperate Qaulcomm..9008 mode or is this just a misunderstanding?

I do not know if I have the universal adb drivers you are talking about. Do you have a link? I installed minimal adb and fastboot from here.

https://xdaforums.com/showthread.php?t=2317790
[Moto Z Guides, News, & Discussion] Manish54:
It's the same. I skipped the middle portion. Qualcomm HS-USB QDLoader 9008.

And you said the batch file says waiting for device and then you said the phone is in fastboot bootloader mode. Please confirm if you're phone is dead or not. If it's booting into bootloader then you should flash your rom normally.

Here is the adb driver: http://adbdriver.com/downloads/
[Moto Z Guides, News, & Discussion] twitchfidelis:
Yes the batch file says waiting for device. If I open a command prompt and type "fastboot devices" my device is listed. My phone is not dead the screen is clearly on with the icon of the Android lying on its back with a chest panel open and the first line of text says "AP Fastboot Flash Mode (Secure)".
[Moto Z Guides, News, & Discussion] Manish54:
Well man... Then this thread is not for you. It is for a dead phone with no boot/charging at all. If you're already on the bootloader then what's stopping you from flashing a rom?
[Moto Z Guides, News, & Discussion] twitchfidelis:
I managed to flash it with a different set of instructions. There is an issue it appears with Windows 10 and RSD Lite maybe it's related to this but who knows. Thanks for your help anyway!
[Moto Z Guides, News, & Discussion] The Unknown123:
hello i have a hard bricked moto z and i can't get it detected on the pc. i have tried on multiple different pc's ALOT of times but it never shows up. any advice?
[Moto Z Guides, News, & Discussion] randomthots:
MOTO Z Hardbricked

Hellow everyone,

my moto z also got hard brick.Tried manish's tutorial and I was successful till the end.But my phone even now dead.I will paste the command lines and the responses I got. Thanks

C:\Users\pterion\Desktop\blankflash\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.37
[ 0.000] Opening device: \\.\COM4
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 2375 (0x947)
[ 0.000] ...cpu.sn = 43926045 (0x29e421d)
[ 0.000] Opening singleimage
[ 0.016] Loading package
[ 0.016] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.elf
[ 0.016] Sending programmer
[ 0.094] Handling things over to programmer
[ 0.094] Identifying storage type
[ 0.094] Waiting for firehose to get ready
[ 3.141] ...UFS
[ 3.141] Identifying CPU version
[ 3.156] ...MSM8996 3.1
[ 3.156] Determining target secure state
[ 3.156] ...secure = yes
[ 3.266] Configuring device...
[ 3.297] Skipping UFS provsioning as target is secure
[ 3.297] Configuring device...
[ 3.594] Skipping 'setbootablestoragedrive' as target is secure
[ 3.594] Flashing GPT...
[ 3.594] Flashing partition:0 with gpt_main0.bin
[ 3.594] Initializing storage
[ 3.828] ...blksz = 4096
[ 3.828] ...part = "SAMSUNG KLUBG4G1CE-B0B1 0800 "
[ 4.641] Flashing partition:1 with gpt_main1.bin
[ 4.672] Flashing partition:2 with gpt_main2.bin
[ 4.703] Flashing partition:3 with gpt_main3.bin
[ 4.750] Re-initializing storage...
[ 4.750] Initializing storage
[ 5.781] Flashing bootloader...
[ 5.797] Flashing xbl with xbl.elf
[ 5.938] Flashing cmnlib with cmnlib.mbn
[ 5.985] Flashing cmnlib64 with cmnlib64.mbn
[ 6.047] Flashing prov with prov64.mbn
[ 6.094] Flashing aboot with emmc_appsboot.mbn
[ 6.188] Flashing keymaster with keymaster.mbn
[ 6.250] Flashing rpm with rpm.mbn
[ 6.281] Flashing pmic with pmic.elf
[ 6.313] Flashing hyp with hyp.mbn
[ 6.360] Flashing tz with tz.mbn
[ 6.485] Flashing devcfg with devcfg.mbn
[ 6.512] Rebooting to fastboot
[ 6.528] Waiting for device to disconnect
[ 8.535] Total time: 8.535s
[Moto Z Guides, News, & Discussion] benzinerwin:
If you had Nougat on before, your bootloader was updated to v91.05. However, the currently available unbrick files contain bootloader files of v91.03. The downgraded bootloader detects that and skips right back into the "9008"-download mode.

I've assembled a package with the current v91.05 bootloader and the most recent partition layout I had at hand, see attachment.

unbrick package with bootloader 91.05 files (timestamp: 2017-01-06 02:58:48, build id: git=MBM-NG-V91.05-0-gd081b7e)
[Moto Z Guides, News, & Discussion] randomthots:
Thanks a lot.

Much appreciated
[Moto Z Guides, News, & Discussion] benzinerwin:
In case anyone had a more recent stock rom OTA runnning you'd been updated to bootloader version 91.07, requiring the following unbrick files...

unbrick package with bootloader 91.07 files from 25.221.12 OTA,

GPT seq#0008 (timestamp: 2017-03-30 04:41:31, build id: git=MBM-NG-V91.07-0-gd081b7e)

The package was built from the 25.221.12 OTA update package. Not updated items were taken from when last supplied (i.e. 25.11.14). The GPT sequence counter reached #0008.
[Moto Z Guides, News, & Discussion] lanyao1920:
Will this work on z play? I have a XT1635-02 bricked now and I tried with v91.03, v91.05 and v91.07, they all give me output like below.

Do I need specific blankflash file on different phone models / bootloader versions?

From the cmd:

Motorola qboot utility version 3.40

[ -0.000] Opening device: \\.\COM5

[ 0.002] Detecting device

[ 4.006] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error

[ 4.006] Check qboot_log.txt for more details

[ 4.006] Total time: 4.008s

FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error​

In the log:

[ -0.000] Opening device: \\.\COM5

[ 0.002] Detecting device

[ 4.006] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error

[ 4.006] Check qboot_log.txt for more details

[ 4.006] Total time: 4.008s

[ 4.007]

[ 4.007] qboot version 3.40

[ 4.007]

[ 4.007] DEVICE {

[ 4.007] name = "\\.\COM5",

[ 4.007] flags = "0x64",

[ 4.007] addr = "0x61FE5C",

[ 4.007] api.bnr = "0xFB2920",

[ 4.007] }

[ 4.007]

[ 4.007]

[ 4.007] Backup & Restore {

[ 4.007] num_entries = 0,

[ 4.007] restoring = "false",

[ 4.007] backup_error = "not started",

[ 4.007] restore_error = "not started",

[ 4.007] }

[ 4.007] ​
[Moto Z Guides, News, & Discussion] lozada81:
Hard Brick Moto Z Play

Fellows, I hope you can help me with the Blankflash file for the MZP.

I left it in full brick, I was locating MM and Nougat going down with the script Downgrade and going up with adb sideload and it happened when installing Nougat again.

It should be mentioned that I was with the April patch, I downgraded to MM Brazil patch November, restart and install the apps as always and personalize, then by adb add patch December, restart and reinstalled N but when finished instead of reboot , I chose to boot bootloader and alli brickeo.

All this only with the Bootloader open, no Root or any modification, now it does not turn on anything and if I connect it to the charger or pc only the charging led flashes, when connecting the pc I recognize it as ¨Qualcomm hs-usb qdloader 9008 COM5¨ I used e Blankflash for the bike z and did not finish the process and the 1,2 and 3 dce XDA and neither.

If someone can pass me the Blankflash will thank you, please.

I arrived here:

Blur_Version.25.211.10.addison.retail.en.US - Security April 2017

NPN 25.137-24-1-9

Download here:

Blur_Version.24.221.12.addison.retail.en.US - Security November 2016

MPNS24.104-44-10

Install this:

Blur_Version.24.231.19.addison.retail.en.US - Security December 2016

MPNS24.104-44-16

Then bricke it at the end of the process:

Blur_Version.25.21.2.addison.retail.en.US - Android 7.0 Nougat January 2017

NPN25.137-15.2

By the way a colleague Ali Guzman from the face group I passed this compilation NPN25.137-24-1 with the included blankflash but in the middle of the process notifies me of package error.

I pass the link in case someone serves:

Https://mega.nz/#!nMdEFLxY!4x0BZWr45...anoX16JZv5B5-E

Http://lenovo-forums.ru/files/category/140-moto-z-play/

Here are two archives with blankflash available so far

ATT Channel Software

thank you very much.
[Moto Z Guides, News, & Discussion] koenvds:
Can you post it on a filehosting site and share the link with us?
[Moto Z Guides, News, & Discussion] thewerthon:
+1
[Moto Z Guides, News, & Discussion] thewerthon:
Solution for Hard Brick 7.1.1 Bootloader 91.09

First I would like to say thank you to [MENTION=9022620]w.fortes[/MENTION] for the attention and the files.

Here the method I used to recover my phone from death.

It was hard bricked in latest 7.1.1 patch (bootloader version 91.09).

1. Bring back the phone to life with this blankflash: https://www24.zippyshare.com/v/oiI6fVNn/file.html

2. Download the Oreo OPL27.76-51 ROM (maybe a newer version): https://drive.google.com/file/d/17_uBPwam_t7GBZ3OwoXPgiDR4ulvFypP/view

3. Donwload and install this version of RSD Lite: http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=66115

4. Flash ROM via RSD Lite and voilá! The phone is back to life!

And please! Do not downgrade and update via OTA or you will brick it again and there's no blankflash for oreo brick (as far as I know).

Worked in XT1650-03 BR-Retail version.
[Moto Z Guides, News, & Discussion] Watkins:
Not work for me, im trying all of wersions blankflash and nothing happend, maybe my moto died for good
[Moto Z Guides, News, & Discussion] Boosh63:
Woo Hoo!!! I'm at the Bootloader!!! Thank you thank you thank you!!!

RSD Lite doesn't see the phone but I'll try to work through that.
[Moto Z Guides, News, & Discussion] w.fortes:
Is your phone being recognized by the PC?
[Moto Z Guides, News, & Discussion] Watkins:
Yes

Wysłane z mojego Pixel 2 XL przy użyciu Tapatalka
[Moto Z Guides, News, & Discussion] Finsther:
oh man, thanks :good: , i really appreciate, thanks for this short tutorial, so helpful.
[Moto Z Guides, News, & Discussion] Watkins:
**** Log buffer [000001] 2018-04-22_23:10:48 ****

[ 0.000] Opening device: \\.\COM4

[ 0.002] Detecting device

[ 0.005] ...cpu.id = 2375 (0x947)

[ 0.005] ...cpu.sn = 2818088160 (0xa7f89ce0)

[ 0.005] Opening singleimage

[ 0.005] Loading package

[ 0.010] ...filename = singleimage.pkg.xml

[ 0.012] Loading programmer

[ 0.013] ...filename = programmer.elf

[ 0.013] Sending programmer

[ 0.092] Handling things over to programmer

[ 0.092] Identifying storage type

[ 0.095] Waiting for firehose to get ready

[ 3.132] ...UFS

[ 3.132] Identifying CPU version

[ 3.132] ...MSM8996 3.1

[ 3.132] Determining target secure state

[ 3.132] ...secure = yes

[ 3.226] Configuring device...

[ 3.257] Skipping UFS provsioning as target is secure

[ 3.257] Configuring device...

[ 3.272] Skipping 'setbootablestoragedrive' as target is secure

[ 3.272] Flashing GPT...

[ 3.272] Flashing partition:0 with gpt_main0.bin

[ 3.272] Initializing storage

[ 5.288] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->fh_send()->send_command()->read_response()->buffer_read()->device_read()->IO error

[ 5.288] Check qboot_log.txt for more details

[ 5.288] Total time: 5.290s

[ 5.288]

[ 5.288] qboot version 3.40

[ 5.288]

[ 5.288] DEVICE {

[ 5.288] name = "\\.\COM4",

[ 5.288] flags = "0x144",

[ 5.288] addr = "0x61FE5C",

[ 5.288] sahara.current_mode = "0",

[ 5.288] api.buffer = "0x32C5020",

[ 5.288] cpu.serial = "2818088160",

[ 5.288] cpu.id = "2375",

[ 5.288] cpu.sv_sbl = "0",

[ 5.288] cpu.name = "MSM8996",

[ 5.288] sahara.programmer = "programmer.elf",

[ 5.288] module.firehose = "0x2F78D78",

[ 5.288] api.firehose = "0x2F71110",

[ 5.288] storage.type = "UFS",

[ 5.288] cpu.ver = "769",

[ 5.288] cpu.vername = "3.1",

[ 5.288] fh.max_packet_sz = "1048576",

[ 5.288] fh.storage_inited = "1",

[ 5.288] provisioning_may_hang = "true",

[ 5.288] }

[ 5.288]

any ideas? RETEU 7.1.1