Develop Bugs

[SOLVED] Soft-bricked my device

Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.

with flashtool impossible to rollback . and impossible to flash kdz 6.0... a lot of people with this issue

Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.

gregor.eesmaa said:
Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.
Click to expand...
Click to collapse
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back

rotoko said:
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back
Click to expand...
Click to collapse
There you go. Can't do any better as I am not an expert in how Android precisely works at this level.

have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815

leegreggs said:
have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815
Click to expand...
Click to collapse
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.

gregor.eesmaa said:
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.
Click to expand...
Click to collapse
No I've decided to go back to my LG g2 till either flashtool gets updated or till a tot & dll comes out

gregor.eesmaa said:
Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.
Click to expand...
Click to collapse
:crying::crying: i forget to enable usb debugging, now my pc can not connect to phone under downloadmode. And i can not use adb to let it reboot bootloader.

I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..

rav0r said:
I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..
Click to expand...
Click to collapse
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.

AndHD2 said:
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.
Click to expand...
Click to collapse
Same here, only a software issue. I cannot boot to download mode, and my device is locked.

System corrupted, laf removed, fastboot doesnt work, stock recovery is useless.

Alright here's the story. I was trying to put CM on this rooted LP 5.0.1 tmobile d851 (20e i think). I backed up and removed the LAF in order to access fastboot so i could flash the custom recovery. fastboot would send the recovery, but the phone would never actually flash the img to the device and report done. Even "fastboot reboot" did nothing. "fastboot devices" reported the serial as "?" and no driver or Arch/CentOS/other windows installs would get fastboot working. fastboot showed up as Marshal london bootloader in device manager.
So then i tried using flash_image from inside of rooted LP to flash the recovery however i ran into PIE errors that could be fixed by replacing /usr/bin/linker. So I found a patched version, rm -rf the old one and tried to cp in the new one. This seemed like a totally valid idea from my linux experience. Buuuut crap. Nothing works. No commands are accepted because I deleted linker. I rebooted cause I had no better alternative and i get a dead android "no command".... Looks like I found the single best way to kill an android installation.
Now im really stuck because i cant use download mode (LAF) to restore because it has been deleted to access fastboot and fastboot wont actually do anything so I can't restore the laf. There is no custom recovery. The stock recovery adb sideload will only let me install OTAs and far as i know there isn't a FULL OTA that will restore the entire system. I even tried the qualcomm 9008 hard brick method with boardDiag, but that doesnt work on tmobile.
I see a few options:
Somehow get fastboot and then download mode working
Wait for a 6.0 OTA and hope it updates the linker bin
advise?
also, the LG logo appears on screen and the LG serial port (the one used for the LG flasher tool) is present in my device manager for a good 15secs before the no command android shows up. I tried lg flasher tool with this time window but it always cut out before the tool could get anywhere.
Edit: This is what the fastboot process would look like:
Screen right after fastboot boot:
[500] Fastboot mode started
[600] -- reset --
[610] -- portchange --
[710] fastboot: processing commands
fastboot erase aboot brings:
erasing 'aboot' ... on command prompt
and
[346290] fastboot: getvarartition-type:aboot
[346350] fastboot: erase:aboot
after those appear it just hangs like that
unplugging it after that command gives me:
FAILED (status read failed (Too many links))
finished. total time: 164.350s
on cmd
and
[514820] -- reset --
[514820] EP1/out FAIL nfo=40 p0=f90bao0
[514830] -- portchange --
[514840] usb_read(0) transaction failed
[514890] fastboot: oops!
[514940] fastboot: processing commands
Click to expand...
Click to collapse

Did you ever find a fix for this?

No, its either professional jtag, or maybe the MM stock ota update zip will fix it if it includes the linker. i havent found this ota on the Internets yet though.

i just had the same problem. any fixes?

flash laf via fastboot
sirbow2 said:
Alright here's the story. I was trying to put CM on this rooted LP 5.0.1 tmobile d851 (20e i think). I backed up and removed the LAF in order to access fastboot so i could flash the custom recovery. fastboot would send the recovery, but the phone would never actually flash the img to the device and report done. Even "fastboot reboot" did nothing. "fastboot devices" reported the serial as "?" and no driver or Arch/CentOS/other windows installs would get fastboot working. fastboot showed up as Marshal london bootloader in device manager.
So then i tried using flash_image from inside of rooted LP to flash the recovery however i ran into PIE errors that could be fixed by replacing /usr/bin/linker. So I found a patched version, rm -rf the old one and tried to cp in the new one. This seemed like a totally valid idea from my linux experience. Buuuut crap. Nothing works. No commands are accepted because I deleted linker. I rebooted cause I had no better alternative and i get a dead android "no command".... Looks like I found the single best way to kill an android installation.
Now im really stuck because i cant use download mode (LAF) to restore because it has been deleted to access fastboot and fastboot wont actually do anything so I can't restore the laf. There is no custom recovery. The stock recovery adb sideload will only let me install OTAs and far as i know there isn't a FULL OTA that will restore the entire system. I even tried the qualcomm 9008 hard brick method with boardDiag, but that doesnt work on tmobile.
I see a few options:
Somehow get fastboot and then download mode working
Wait for a 6.0 OTA and hope it updates the linker bin
advise?
also, the LG logo appears on screen and the LG serial port (the one used for the LG flasher tool) is present in my device manager for a good 15secs before the no command android shows up. I tried lg flasher tool with this time window but it always cut out before the tool could get anywhere.
Edit: This is what the fastboot process would look like:
Click to expand...
Click to collapse
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.

nibedankaran said:
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
Click to expand...
Click to collapse
thanks for the reply, but as i mentioned in my post, fastboot commands don't work. i wish it was that easy.

nibedankaran said:
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
Click to expand...
Click to collapse
I think you have a serious problem
You have to see google fix lg g3 on Qualcomm mode...I mean hard brick fix....
Download as instructed
I think it will be fixed
Recently I fixed lg g3 from only led blink no signal to pc and only vibrate and others

That doesn't work on tmobile G3s, thanks though. I did try it anyways btw.

Getting the update.zip from a friend. its in the SD card but its not showing up in MTP so were trying to figure that out. once i have the zip ill try flashing it. if it doesnt work, itll get a octoplus jtag flash.

Well the update did not like the fact that this phone was missing the linker bin or the previous root because it fails when checking the current system. Looks like octoplus is the only way cause i'm an idiot.
Anyone know where i can send this to get it done? i thought some people on ebay did it but i cant find them.

I have same problem, no download mode, system corrupted and recovery is useless.

mysteryjeans said:
I have same problem, no download mode, system corrupted and recovery is useless.
Click to expand...
Click to collapse
If it's a tmobile G3 (d851) you have no choice but send it to someone for an octoplus jtag service because the DIY jtag method doesn't work. Got mine done for $42 after shipping from an ebay service.

sirbow2 said:
If it's a tmobile G3 (d851) you have no choice but send it to someone for an octoplus jtag service because the DIY jtag method doesn't work. Got mine done for $42 after shipping from an ebay service.
Click to expand...
Click to collapse
Finally I recovered it, I have to short testpoint then connect cable to PC, my device is dual sim therefore different logic board, see this http://forum.xda-developers.com/lg-g3/help/lg-d858-qualcomm-test-location-t3293440 for D856/7/8 testpoint to get device into Qualcomm 9008 mode, then I had flash F400K (yes korean rom) tot from thread http://forum.xda-developers.com/showthread.php?t=2785089 using BoardDiagv2.99 http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 to get it live and get into download mode.
Now finally flashed stock KDZ using this post http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
If I knew there is new tool to flash MM stock, I wouldn't brick my device. :silly:

Thats exactly what i tried but didn't work because D851

H815: No recovery mode (bootloader unlocked, TWRP 3.0.1 installed)

Hey guys,
I'm trying to root my G4 loaded with MM 6.0. I cannot get into Recovery Mode no matter what I do.
I have tried the key combo (power+down, etc) - it does nothing. If I use adb reboot recovery, I just get the dead Android guy with the exclamation in red triangle. (which is perhaps a hint as to why the key combo doesn't work.)
I followed steps to unlock the phone's bootloader via LG's dev site (success) and I've installed TWRP 3.0.2-0-H815.img but I can't get into Recovery mode. **The phone continues to work fine** and I can get it into Download Mode.
After having no success with TWRP, I thought, f*ck it, since I've gone this far, let's go with CyanogenMod instead of stock, so I installed cm-13.0-20160415-NIGHTLY-h815-recovery.img
I was also able to use adb to push CM 13 (nightly build 20160415) and Gapps (arm64 6.0 20160416) successfully to phone, but it's obviously no use since I can't get to Recovery Mode.
I'm wondering if someone can please suggest a solution or at least a next step.
When I use fastboot flash recovery twrp-3.0.2-0-h815.img it takes 0.718s 'send recovery' and 0.282s 'writing recovery'.
[solved - probably Win10's no-ask driver update policy] New problem: After going back to TWRP, fastboot devices shows nothing and my device is showing up in Device Manager as LGE Mobile USB Composite Device, whereas I specifically changed it from the LG drivers I installed to Android ADB drivers. The device doesn't even list the Android ADB driver as an available option now. WTAF?!? Maybe this is more Win10 driver-auto-update malarkey?
OS = Win10x64
Kernal = 3.10.84
Build number = MRA58K
Software version = V20d-EUR-XX
Developer options are available
USB debug is enabled
OEM unlock is enabled
I'm using the stock USB cable
Additional question - tutorials say to back up NVRAM and IMEI before doing anything risky, but I can't get those without root. How does this make sense?
EDIT: NOTE: You should be using the arm64 version of Gapps on LG G4 H815.
Thank you very much to everyone who stops in to take a look at my questions.
All the best,
Dax.

Hi
I had the same problem with Win 10 not seeing my H815 properly (same device name in Device Mgr as yours) I reverted to the older Lge drivers, 4.0.3 if I remember correctly and the phone showed up properly and I was able to use LG UP to update/downgrade etc.
Like you I have since tried to install TWRP but I cannot new get root with Kingroot 480 although it worked previously on V81520D it does not now.
Sent from my iPad using Tapatalk

try fastboot boot recovery twrp-3.0.2-0-h815.img
then tap IMG instead of ZIP (bottom) -> install img and flash the twrp img

Hi Stransky, I reinstalled the adb-setup-1.4.2.exe package which also contains drivers and now ADB will see the phone (which is good), but Fastboot still says waiting for devices (bad). Thanks!
I also changed the default driver from 'LGE Mobile ADB Interface' to 'Android ADB Interface' (as per tutorial instructions).
Hi Bender_007, thanks so much for the tip, I'll try it as soon as I can get Fastboot working again. Cheers!

Okay, so I learned ADB is for Android or Recovery mode, Fastboot is for 'HBOOT' (bootloader) mode.
As expected:
adb devices returns "List of attached devices: LGH81579d3bc56 device".
If I use the command adb reboot-bootloader, phone restarts in bootloader mode.
Then adb devices does nothing, but fastboot devices returns "79d3bc56 fastboot".
When device is in bootloader mode, it shows up in Windows Device Manager as 'Marshall London Bootloader Device'.
Bender_007, the command "fastboot boot recovery twrp-3.0.2-0-h815.img" doesn't work. It's invalid syntax. "fastboot flash recovery twrp-3.0.2-0-h815.img" works as per original post.
Any other suggestions?

Hm, put the twrp inside the same folder where your fastboot and adb are. Then start command prompt in the very same folder and type fastboot boot twrp... And that should be it. That means if everything is normal and the system is bootable.
Pardon, fastboot boot twrp(whatever the name is)
Not: fastboot boot recovery twrp..
Sent from my LG-H815 using Tapatalk

Hi Bender_007, that's exactly where the .IMG files are already. No dice. :/

May I see this via teamviewer please ? (teamviewerQS via private message)
I´ll gladly help you (if it´s in my possibilities ofc)
@daxliniere
EDIT: 21.04.2016 - we have fixed this, had a nice talk, almost a beer. It´s nice to meet new cool people , keep it up my friend

I am stuck probably on the same issue with win10. It seams like I was able to flash twrp recovery but I can't enter it. Already factory reseted it 3 times while trying to enter into custom recovery.
Any advices what to do?

madik_ said:
I am stuck probably on the same issue with win10. It seams like I was able to flash twrp recovery but I can't enter it. Already factory reseted it 3 times while trying to enter into custom recovery.
Any advices what to do?
Click to expand...
Click to collapse
The best solution there is:
1. put adb, fastboot into a directory (let´s say c:\adb), put the twrp-3......img into the same folder
2. adb reboot bootloader
3. open command prompt, cd c:\adb
4. fastboot boot twrp-3.....img (where twrp-3....img is the actual name of the twrp img)
it will boot to twrp, now you can either copy the twrp img to the phone and flash it(it will ask where to flash - tap on recovery--don´t tap on boot)
You might have to tap on zip/img toggle to enable img flashing first
should you need more help just post in here

Yep that did the trick. thank you! I was able to load recovery with the fastboot boot twrp.. but didnt realize that i can install it by the loaded twrp lol. Now I can finally confirm 2x YES and it gets me into TWRP. thanks again!

Can I make one little tip for everyone else? Follow this guide to the end: http://www.technobuzz.net/unlock-lg-g4-bootloader/
Step 1 is the easiest way to install adb, fastboot and drivers in one go.

Same problem here:
Software version = V20d-EUR-XX, Developer options are available, USB debug is enabled, OEM unlock is enabled
I can boot into recovery via bootloader: fastboot boot twrp-3.0.2-0-h815.img but:
1. had I to allow to modify system partition modifications?
2. how can I boot in recovery from system? with adb I always get the red-triangle Android on its back und with hardwarekeys after shut down the devise, I#m coming to stock recovery: factory restet no/yes

1. Yes
2. While you are in twrp just flash the twrp IMG again via twrp itself. It has the option to flash img instead of zip.
Poslano sa mog SM-G930F koristeći Tapatalk

thx, a lot...
Now im running a full system update to exsdcard and afterwards I try to "re-"install the twrp in twrp-applikation.
When i boot into recovery at the moment, the "modify-dialog" is away...
But I will see after "re-"install the twrp how it works...
---------- Post added at 03:48 PM ---------- Previous post was at 03:00 PM ----------
UPDATE:
Did it, worked!!!
on system: "adb reboot recovery" leads to twrp!
there are no hardware-key-solutions to get to recovery...
with the hardware-keys (after shutdown -> power + vol down -> release power for a second when LG-logo pops up) I get to the factory reset no/yes dialog...

On the factory reset choose yes twice. Normal for lg
Poslano sa mog SM-G930F koristeći Tapatalk

I got nervous to choose yes the second time....

sejmand said:
I got nervous to choose yes the second time....
Click to expand...
Click to collapse
Install Quick Boot from the Play Store,you can boot straight to Twrp with it

fastboot erase recovery
fastboot flash recovery xxx.img (xxx=twrp.img)

Hello,
I am still struggling with my h815 on 7.0:
I am getting the error sign with "no commands".
I cannot force it to boot to the twrp but I can flash it (unknown command):
HTML:
student:~/Downloads$ sudo fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (32992 KB)...
OKAY [ 1.106s]
writing 'recovery'...
OKAY [ 0.931s]
finished. total time: 2.037s
student:~/Downloads$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.104s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.121s
using ubuntu 16.04.
Thanks for your feedback in advance.

Find 7 (x9076) soft bricked, misread by device manager,

Hey Everyone,
I have a Find 7 (X9076). A while back I updated to the "stable version " of ColorOSi and ever since my usb doesn't charge the phone and vol down key doesn't work. Additionally it is being misread by the computer device manager as a "Samsung Android Device" when it is in boot loader mode.
I suspected it was a software/kernel issue because when I checked the registry I found the original oppo drivers, so I attempted to flash a new kernel to the device and ended up soft bricking it (no image). Now even though it is soft bricked I am still able to get into boot loader mode (no image). Please Help?
I have used Find 7 recovery installer and FASTBOOT (CMD) as well as trying to use ADB and a Find 7 unbricking tool in Windows 7 test mode the last two didn't work/didn't recognize my phone at all. I refuse to abandon my device so what do I do?

Given you have adb access, you could extract the contents of the current (2.x?) color os image, and fastboot flash the partitions manually.
I recently did this and 'recovered' my device.

adb didnt recognize my device -but how do I do that just in case I'm able to get it working?

Midnight247 said:
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Click to expand...
Click to collapse
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.

ADB, FastBoot and the USB
I don't know if I was clear in my explanation as to how and when my device (FIND7 X9076) is recognized ONLY by the following: my Computer (Windows 7), the Device Manager, Fast-Boot and on the FIND7 Recovery Installer. I have been able to enter fast-boot mode on any version of the ColorOS I flashed, 1.2 - 2.5.1, (stable version) and work within the confines of that mode. However when the USB is connected in anything other mode (recovery-main OS) it ceases functionality (sending information to comp for recognition, charging, etc.). Also the charger doesn't work and nor does the notification light. Now I may be wrong, but for these reasons I believe the problem is likely software related. I am open to any opinions and advice.
-Thank You Everyone

tropical cactus said:
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
Click to expand...
Click to collapse
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??

Midnight247 said:
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Click to expand...
Click to collapse
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.

tropical cactus said:
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
Click to expand...
Click to collapse
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.

Midnight247 said:
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Click to expand...
Click to collapse
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.

tropical cactus said:
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
Click to expand...
Click to collapse
hmm okay, i see I will keep you posted

**IMPORTANT UPDATE**
***MAKE OPPO FIND 7 OPERABLE****
following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
By using the afformentioned commands in fastboot (of course) I was able to restore my phone to almost full functionality. It operates noramally and I fixed the notication light, But I say almost because I cannot charge my phone or have it recognized by my computer through any charger or usb connection when it is on normally or in recovery mode so if any one is familiar with this problem please respond or simply voice ideas.

If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.

RobboW said:
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
Click to expand...
Click to collapse
I do, have full functionality : ) everything but the USB is performing properly, but to be honest I dont know what AOSP is.....also this will repair functionality to the USB?

Recovering data on a DEAD Redmi Note 8 PRO

Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.

how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.

Thanks for the hint, but I am not happy with the idea of someone playing with my data

1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC

Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.

Any idea? Should I give up?

If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info

Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.

Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.

If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?

So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?

Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons

MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?

You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b

I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.

Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.

Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?

Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.

Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?

Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5