yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] hamhead:
wow my nexus 7 was in boot loop and i had an old NRT tool which wouldnt work at all.

computer wouldnt detect next 7 2013 thru usb cable

cannot mount usb-otg in TWRP

boot loop in custom rom

your tool fixed it so fast and easy.

THANKS SO MUCH FOR YOUR TOOL!!!
[Nexus 7 (2013) General] Tmzdroid:
Thanks for this k23m although I hope to never have to use it. My Kingston equipped Nexus 7 is still going strong and it's my most used android device. If I run the emmc memory test and diagnostics would it tell me if the emmc is about to die and determine its overall wear and health?
[Nexus 7 (2013) General] k23m:
Hello Tmzdroid, your Kingston was from a newer production batch and probably is OK but maybe do not try any major OS/ROM changes as this most recent case demonstrates. The eMMC generation used in N7 has no "SMART" flash wear diagnostics like in SSD. This feature was introduced in eMMC v5+. Restock can identify Kingston if it has standard partitions and checks for the terminal, most common, read-only condition Kingstons suffer from. In short, the test can not indicate eMMC degradation level. The only forewarning you may get is a period of slow-downs prior to going read-only. If you feel it is happening, do fastboot format cache and if it takes longer than 2 seconds, it is almost the end and time to get your data out of the tablet, while you still can.

:highfive:
[Nexus 7 (2013) General] AiRMaX-360:
Thank you for this! It fixed my deb model <3
[Nexus 7 (2013) General] drinkypoo:
I'm getting "Incorrect device" trying to use Restock to recover from flo-deb_clamor_repartition. It's definitely flo, I am looking at the bootloader right now. fastboot format cache completes in 0.086 seconds. flo 32G, rev_e, bootloader FLO-04.08, no carrier, secure boot enabled, lock state unlocked.

edit: got going again with https://xdaforums.com/showthread.php?t=2381582
[Nexus 7 (2013) General] k23m:
Thank you for confirming that it works on deb. I have 3 flo's but no deb to test.

Would you be able to post a log from the attached script? Unzip and run it in Restock's folder.

:fingers-crossed:
[Nexus 7 (2013) General] drinkypoo:
Strangely, it won't run unless I run as administrator. I double-click it and nothing happens. If I run as administrator then it runs in c:\windows\system32 and doesn't list the contents of the directory you want... I even tried moving restock's folder into my user dir instead of under downloads just in case something about the path was causing problems. No idea WTF that is about. Perms look good. I went ahead and just ran the commands manually from a CMD shell in the proper directory, looks like they produced the output you were looking for... except the find command doesn't work there. Maybe it would work in command.com, dunno.

I'm not sure how much help this will be since I used other tools since trying to use restock, but here it is anyway.
[Nexus 7 (2013) General] k23m:
It seems your Path env exceeds the limit:

Path=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Python27\;C:\Python27\Scripts;C:\ProgramData\Oracle\Java\javapath;C:\WinAVR-20100110\bin;C:\WinAVR-20100110\utils\bin;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\PuTTY;C:\Programs\Argyll_V1.7.0\bin;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files (x86)\GitExtensions\;C:\Program Files\Git\cmd;C:\Windows;C:\ProgramData\ComposerSetup\bin;C:\Program Files\Calibre2\;C:\Program Files (x86)\sbt\bin;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Users\drink\AppData\Local\Android\Sdk\platform-tools;C:\Program Files (x86)\GNU Tools ARM Embedded\5.4 2016q3\bin;C:\Users\drink\AppData\Local\Android\Sdk\platform-tools;C:\Program Files (x86)\Nmap;C:\Programs\ffmpeg-20190208\bin;C:\Program Files (x86)\Atmel\Flip 3.4.7\bin;c:\programs\fastboot;C:\programs;"%~dp0data"

My path has only:

Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\

Please do:

Edit the path - Control Panel / System / Advanced System Settings / Advanced tab / Environment Variables button / in System Variables select Path / click Edit

copy original and save for reuse later

replace it with: C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\

save

reboot

run Restock

It should work now. As your N7 is already fixed, just close the window when it stops at "Note: Android flash takes 2 minutes, initial boot takes 7 minutes" and nothing will be flashed. Also, don't go ahead with "Restore original partitions? [y/n]" if it is offered.

If it still does not work, login to Windows with an admin account and then run Restock.
[Nexus 7 (2013) General] drinkypoo:
Sigh. Windows is garbage in so many ways.
[Nexus 7 (2013) General] Jay Rock:
I was just thinking I want to restore my Nexus back to 100% stock, and magically this recent thread appears. Worked perfectly. Thank you.
[Nexus 7 (2013) General] bamsbamx:
Strangely, only custom ROMs are working for me. I always get bootloop whenever I flash any of the razor Nexus Factory Images. I also tried the script you provided and finishes successfully, but when booting, it always end in bootloop with Google logo on it. I have access to fastboot and even can flash and boot to TWRP with no problemas. Any idea?

EDIT: Attached logs after re-running the script
[Nexus 7 (2013) General] k23m:
It is a very interesting case. We need internal logs, please 'install' get-logs-sdcard.zip in TWRP, find 'logs.tgz' in the root of internal storage and post it here.
[Nexus 7 (2013) General] bamsbamx:
Thanks for the quick reply, here I attach the logs... Seems like the /persist partition is empty, maybe thats the cause of the problem?

However, I can understand why that happened, maybe because I used the /system partition script for increasing its size...

EDIT: Somehow the XDA file uploader says invalid file for .tgz format, I recompressed the folder to a .zip file
[Nexus 7 (2013) General] k23m:
The 'persist' partition is not empty, you can see its contents in the log's 'ls_persist' file, but its SELinux contexts appear incorrect. Try this:

in TWRP backup your original 'persist' with the attached p4-backup-int.zip

go to my old post here, get those files and restore my 'persist' partition

boot stock ROM

:fingers-crossed:
[Nexus 7 (2013) General] bamsbamx:
Still no luck. I have re-run the get-logs script and some file permissions have changed in le_persist (checked with a diff comparer), as well as new file called settings. Flashed factory image MOB30X and bootloop, then flash UnLegacy rom android 8.1.0 and boots with no problem. Cant understand what is happening... Maybe it is possible to use UART debugging to get some logs?

EDIT: Attached the new logs
[Nexus 7 (2013) General] k23m:
This new log is much better. The timing was right and it had captured 'last_kmsg' with mob30x bootloop log, note:

[ 4.865234] init: Starting service 'logd'...
[ 4.873748] EXT4-fs error (device mmcblk0p23): ext4_mb_generate_buddy:741: group 1, 32282 clusters in bitmap, 32356 in gd
[ 4.873962] Aborting journal on device mmcblk0p23-8.
[ 4.874664] Kernel panic - not syncing: EXT4-fs (device mmcblk0p23): panic forced after error
...
[ 7.987304] Rebooting in 5 seconds..
[ 12.994476] Going down for restart now
[ 12.994628] in panic

It can't use mmcblk0p23 - the cache partition, and has to restart. New custom ROMs no longer use the cache partition and that's why they work. For comparison here is my 'last_kmsg' with mob30x...

[ 7.072235] EXT4-fs (mmcblk0p23): recovery complete
[ 7.077087] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
[ 7.086883] fs_mgr: check_fs(): mount(/dev/block/platform/msm_sdcc.1/by-name/cache,/cache,ext4)=0: Success
[ 7.162567] fs_mgr: check_fs(): unmount(/cache) succeeded
[ 7.171722] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/cache
[ 7.264678] e2fsck: e2fsck 1.42.9 (28-Dec-2013)
[ 7.269744] e2fsck: /dev/block/platform/msm_sdcc.1/by-name/cache: clean, 23/35840 files, 4726/143360 blocks
[ 7.285522] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,errors=panic
[ 7.296874] fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/cache,target=/cache,type=ext4)=0
...
[ 8.289031] init: Starting service 'logd'...
[ 8.302368] SELinux: Context u:object_r:cache_recovery_file:s0 is not valid (left unmapped).
[ 8.312286] SELinux: Context u:object_r:cache_private_backup_file:s0 is not valid (left unmapped).
[ 8.342254] init: (Loading properties from /system/build.prop took 0.01s.)
[ 8.348266] init: (Loading properties from /vendor/build.prop took 0.00s.)
[ 8.355133] init: (Loading properties from /factory/factory.prop took 0.00s.)
[ 8.369842] init: Starting service 'vold'...
[ 8.373321] logd.auditd: start

Run fastboot format cache and compare it to the 'sample output' from the first post.

There may be a partial eMMC hardware fault affecting the cache partition.

If you wish to investigate it with UART, please check my post on the subject.

:highfive:
[Nexus 7 (2013) General] bamsbamx:
Yeah, I had the idea of checking last_kmsg just after my previous post. Saw that mounting mmcblk0p30 was causing kernel panic. Ran TWRP Format Cache and err well... Bootloop was now in the boot animation (maybe I had to reflash factory image, which I didnt). Didnt see about mmcblk0p24, will format cache and post feedback. Thank you!

:highfive:
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] kuba929:
Does Google work for you? It works for me only for a while after uninstalling the Google update and installing it back from the Google store position, but after 10/15 minutes when I say ok google doesn't work. And when I click on access to voice natch it pops up something like on screenshoot. It helps what I described literally for 5 minutes before. In the nova prime launcher settings "ok google" is also enabled. Do you know how to resolve it? Newest xiaomi.eu.

Wysłane z mojego Redmi K20 Pro przy użyciu Tapatalka
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] efakkawy98:
I am having the same problem on Xiaomi.EU Rom. But I will try later with Indian Rom and see if it works properly.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] heynando:
to be really honest, in general xiaomi.eu roms suck, I remember since the old days nobody knew about Xiaomi, 4 5 6 years ago, the EU Roms have always existed, but their distinct characteristic is to almost always be very very very buggy, after learning that i've always tried to stay far away from them
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] sam00561:
The Eu based roms are based on chinese firmware so generally ok google or long press google assistant wont work on them.
[Xiaomi Mi 9 Questions & Answers] GabriusD:
So recently I noticed that zoom in and out is actually delayed about half a second.

Anyone experiencing same issue ?

What are the fixes for this?

It's really frustrating

Thank you for all of your responds
[Xiaomi Mi 9 Questions & Answers] _Nexus8_:
When you say that the zoom is lagging, are you talking about switching from the 1x camera to the 2x one?
[Xiaomi Mi 9 Questions & Answers] GabriusD:
Exactly, pinch zooming is delaying for a half second
[Xiaomi Mi 9 Questions & Answers] gerhard_wa:
You don't pinch to switch between the 1X and 2X cameras, you point to the 1X/2X icon in the lower middle. No need to pinch before you take a photo, this will only mask the outer areas. It's better to crop the image afterwards, this will achieve the same thing and is easier to do with the picture already taken.

In short, pinching in the viewfinder will not zoom, it will crop the picture.
[Xiaomi Mi 9 Questions & Answers] GabriusD:
I think there was a misunderstanding. By pinch to zoom I mean that for example I am taking a video with front camera and let's say I zoom to my nose. So zoom process takes about 0.5 second to react to my pinch to zoom gestion. Hope that will help.
[LG G7 ThinQ  Questions & Answers] Olvers974:
Hello,

Bootloop on my phone ...

I've a problem with my phone.

Impossible for a Refurbish / update / Partition DL via LGUP

Message : Error : 0x81000302, Please use latest DLL LAF Protocol version is not match DLL = 0 Device = 116342816

And on my phone on the Download Mode :

633A B67

Modified / E / L / RO

I think that flash boot_a and boot_b stock manually via Fastboot ?

For the Good update on LGUP ?

Sorry For my english, i'm french ^^

Best regards,

thanks :)
[LG G7 ThinQ  Questions & Answers] nicoilboss:
I think you got a wrong version of LGUP. Try this one : https://xdaforums.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303

If you get an error also with this one just update with LG MOBILE SUPPORT TOOL ( it can be downloaded from support section in the official LG website. For the recover process you only need YOUR IMEI or S/N).
[LG G7 ThinQ  Questions & Answers] Olvers974:
[MENTION=7108373]nicoilboss[/MENTION]

Thanks a lot, I will test this, I'll let you know;) !

Edit : It's doesn't works ... :(
[LG G7 ThinQ  Questions & Answers] nicoilboss:
did you tried also with Lg Support Tool ?

You have to reboot your phone into the download mode and then use the IMEI for an advanced restore.

You can find the tool here : lg DOT com/fr/support/support-mobile/lg-LMG710EM
[LG G7 ThinQ  Questions & Answers] Olvers974:
Yeap ...
[LG G7 ThinQ  Questions & Answers] Olvers974:
Solved !

Octoplus pro JTAG Software ... :)

One solution !
[LG G7 ThinQ  Questions & Answers] tripticonachos:
How much?
[General Questions and Answers] nour12:
my phone screen a line showed up and go green after flash the phone

i tried another firmware but it didn't work and i try flashing with 4 files and also

did't work the device is booting i can hear the sound but the screen just go green

any one can help me please......
[General Questions and Answers] u5l3:
flashei o twrp e tambem de uma tela verde
[Networking] MistahP:
Does anyone have any idea for a good packet sniffer for the HTC P3600?

I tried airscanner mobile sniffer, yet it wouldn't work (kept saying something about not being able to initiallise wifi driver)

I do not only want to search for networks, but I also want to capture the TCP packets.

I tried searching the forum first, but all i got were dead links, so if anyone can help me, i would greatly appreciate it!
[Android General] donnasbrt1:
Updated 11/4/19

Several BLU Factory Service Manuals

https://www.mediafire.com/folder/dhdwcx6doiwr2/BLU Service Manuals

Advance 4.0M

Advance L4

C4

C5

C6

C6L

Dash L4

Flash 2.4

Grand M2

Grand M3

Grand Mini

Grand Mini 2

Life X LTE

Studio G4

Studio J1

Studio J2

Studio Mega

Studio View

Studio View XL

Tank Mega

Tank Plus II

Tank Xtreme Pro

Vivo 5 Mini

Vivo Go

Vivo XI

Vivo XI +

Vivo XL4

Z3 Music

Z4

Z5

Zoey Flex 3G
[LG Spirit Questions & Answers] WoW2ndJob:
Hello,

I really do not remember how I used to flash LG, I've tried everything on google, the LG Flash tool 2014 and LG UP method.

LG flash tool gives me contact system admin thus the LG UP when goes to Com port and saying my phone model it says not compatible or something.

I need to reflash it cause the Twrp is stuck at factory reset on mem cache.

Its H440 aka Spirit 4G LTE (on back it says soo C70 E).
[LG Spirit Questions & Answers] deguzz322:
Occasionally it becomes difficult, but you will achieve it, just read and go learning again to do it! with patience
[G4 Q&A, Help & Troubleshooting] patrick12:
Hello :)

could someone tell me this, please?
[Miscellaneous Android Development] PeterCxy:
Introduction

This is an UNOFFICIAL TWRP port for UMIDIGI F1 that works properly with encrypted /data partition in official ROM. I am aware that the UMIDIGI F1 already has TWRP built for it, but none of them seem to have decryption working properly. In fact, every single TWRP, even official ones, for any MT6771 device, seem to have non-functional decryption support. Through some digging I managed to fix decryption at least for UMIDIGI F1, so here is my version of TWRP for the device.

Known Bugs

- Screen may flash on the password-input UI. Anything else is fine though.

This TWRP has been tested with official ROM and my LineageOS 17 port (https://xdaforums.com/android/development/unofficial-lineageos-17-0-umidigi-f1-t3997827) and it works fine.

This is UNTESTED on the F1 Play. ONLY TESTED on regular F1.

Why Bother

Because security matters. Using a cheap device should not mean giving up security, and more importantly, privacy.

Instructions

1. Unlock bootloader

2. Enable ADB debugging in system

3. Execute "adb reboot bootloader" while having your phone connected to PC

4. Execute "fastboot flash recovery <your_downloaded_recovery>.img"

5. Reboot phone while holding Volume Up + Power buttons

Note: The official ROM may overwrite the recovery, so you may need to re-flash the recovery if this behavior isn't prevented either by TWRP or manually.

Downlaods & Sources

20191103: https://github.com/PeterCxy/android_device_umidigi_F1/releases/tag/20191103-twrp

- Fixed issues with Magisk and OpenGAPPS

20191102: https://github.com/PeterCxy/android_device_umidigi_F1/releases/tag/20191102-twrp

Device Tree: https://github.com/PeterCxy/android_device_umidigi_F1/tree/twrp-9.0

Modified TWRP (Required for decryption to work): https://github.com/PeterCxy/android_bootable_recovery
[Miscellaneous Android Development] PeterCxy:
Updated to 20191103
[Miscellaneous Android Development] mrmazak:
I appreciate your sharing this. I have added "system_image emmc" to the fstab file, so I can flash and backup the system.img

This works good on my F1,

But I tried to make this decrypt work for my other phone with 6771(Bold N1), but couldn't find all same files added to recovery/root from stock firmware.
[Miscellaneous Android Development] PeterCxy:
Those files are extracted from vendor.img, but it can be different on different devices, e.g. keymaster version might be different. Also you will need to patch them using `patchelf` to make them use `/sbin/linker64` instead of `/system/bin/linker64`
[Miscellaneous Android Development] Shadow Of Leaf:
hello

im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???

thanks
[Miscellaneous Android Development] mrmazak:
on other releases, no change was needed to boot on both. I would try as is first.

as long as you have working sp flash tool in case of issue.
[Miscellaneous Android Development] Shadow Of Leaf:
Cause i test it without changes , it reboot to system

I think because they have different kernels
[Miscellaneous Android Development] Quitério:
I am unable to install twrp.

When I run the "fasthboot flash recovery" command, cmd aparace "waiting for de ice" and nothing happens on my phone ...

Am I doing something wrong?
[Miscellaneous Android Development] tarvoke:
no fastboot response

for some reason (most likely pilot error, lol) the phone doesn't show when I do "fastboot devices" - even though the F1's screen shows "fastboot mode" in very tiny letters on the bottom-left.

probably something stupid I'm doing wrong, will keep trying...
[Miscellaneous Android Development] SubwayChamp:
You can operate from adb/fastboot folder and device can stay on fastboot mode but if drivers were not properly installed then no connection with pc.

Try installing:

- https://androidmtk.com/download-15-seconds-adb-installer

- https://androidmtk.com/download-mtk-usb-all-drivers

- https://www.androidweblog.com/download-mediatek-usb-vcom-drivers/

Start the process from device on using adb commands to always allow access to the pc. I mean:

adb devices

and then if device is detected you will see a screen warning to "always allow...." then tap on yes; this suppress future conflicts, then

adb reboot bootloader

while on fastboot follow with

fastboot devices
[Miscellaneous Android Development] tarvoke:
thanks!

adb was already working (is how I made the thing reboot to bootloader, and yes I did tell it to permanently accept the computer I'm using.

this is on linux, so the drivers shouldn't be a problem... although SMH I never put USB IDs into the udev rules. which is interesting, because regular adb already worked fine without it - I have had phones in the past that some did, some did not, require the computer to know about vendor/hardware ID.

(and I know that the adb USB IDs are usually different than the ID for fastboot, as well.)

like I said, pilot error lol. but thank you again for the reply!
[Miscellaneous Android Development] opticyclic:
I have done the following:

Enabled Developer Options

Enabled USB Debugging

Enabled OEM Unlocking

Unlocked the bootloader with:

adb reboot bootloader
fastboot flashing unlock

Rebooted and Enabled USB Debugging again.

Then after downloading your recovery

adb reboot bootloader
fastboot boot ~/Downloads/recovery.img

But nothing happened.

I rebooted and thought I would try flashing

adb reboot bootloader
fastboot flash recovery ~/Downloads/recovery.img

It just paused on the boot screen saying "Your device has been unlocked and can't be trusted".

If I reboot then try to go direct to recovery:

adb reboot recovery

I end up with the broken android screen and "No command"

What am I missing?
[Miscellaneous Android Development] SubwayChamp:
While in fastboot the first you should do is see if device is detected by pc with

fastboot devices

It looks like something is wrong with your path, I ever avoid path copying or moving the file/image to the adb/fastboot directory but anyway if you don´t want to do it you can copy the path from the bar where your recovery file is allocated, for example, if the file is in Downloads directory like it seems actually is, no matter what unit/drive you are in you can set an absolute value to avoid errors, look at this example: C:\Users\your_user\Downloads

If your device is detected then you can flash the recovery as you were trying to do it with

fastboot flash recovery recovery.img

and then you can reboot directly to it without need to reboot to system previously and this will prevent TWRP from being overwritten, with

fastboot boot recovery.img
[Miscellaneous Android Development] tarvoke:
hmm, so when I checked the udev rules, it already had one for MTK/mediatek - and the USB vendor is '08ed' in fastboot as well as in regular adb, so it wasn't a problem with udev/plugdev.

which I guess may mean the lunix generic android drivers for fastboot might be... "lacking" - I'll have to scrounge up a win7 laptop and try the recommended windows drivers.
[Miscellaneous Android Development] opticyclic:
I don't think it was anything to do with the path as it output the file transfer size.

I think it was a combination of the following:

I wasn't pressing the right combinations of buttons after flashing.

i.e. holding VOL UP and pressing POWER on the screen saying "Your device has been unlocked and can't be trusted".

Rebooting might (?) have been reverting the recovery.

I was originally trying this on the firmware that was shipped 2019012414 but after flashing 2019090418 with SPFlashTool I had more success.

I also able to reboot to recovery directly after flashing with fastboot with the following:

fastboot oem reboot-recovery

Whichever was the key I can now reboot to recovery from adb too.

:good:
[Miscellaneous Android Development] LyrielAlk:
Your twrp eliminates fingerprint authentication.

I discovered something interesting, your twrp only works on my device, no other twrp works, but when I install it, I lose my fingerprint, it doesn't work at all.

Simply put, I must choose between the fingerprint or the root.
[Miscellaneous Android Development] BZ0RG:
Try to clean flash last vendor build with spflash tool. First boot need stock recovery.

You don't need custom recovery to achieve root.

Maybe give a try to SNwriter (I never needed it though and can't help here).
[Miscellaneous Android Development] mrjahvi:
Both of those twrp are not sticking. I have flashed with spoken flash tool v5 1944 win and I fastboot cmd with the same results.
[Miscellaneous Android Development] kudangel:
Thanks

Gracias for this master ?
[Miscellaneous Android Development] rsoft3ddev:
good

good idea