[Help] XT1768 wont load into bootloader or recovery - Moto E4 Questions & Answers

Hey,
So yesterday I decided to finally tinker with my phone. My main issue was that the Wifi kept disconnecting on it's own for no damn reason but no other device would do it. Found out it's a thing with the E4 and the option for disconnecting on a bad connection wasn't there.
At anyrate, I unlocked the bootloader and flashed TWRP. Then things started to go sour. While trying to root the phone, I ended up with no ROM. Tried a couple of different ones. Lineage OS, Resurrection Remix but none could get past the boot animation. Eventually I found the correct (I think) ROM for my phone. I'm in Canada and on Freedom Mobile so I went with the Retail Perry OS from here: https://mirrors.lolinet.com/firmware/moto/perry/official/RETAIL/
I tried installing with TWRP but it said invalid ZIP file so I found another way. Using instructions from https://forum.xda-developers.com/moto-e4/help/rsd-lite-device-connecting-t3671647 I used the rsdlite motorola xml to batch script file thing mentioned. Phone finally worked again! Went about installing the bits and bobs. Was working for a few hours and then I decided to update. I had used an older version of the firmware when the zip file was coming up as invalid in TWRP. The first two or three updates went fine. Downloaded, installed, restarted, fine. Then during one it just... stopped. I think it was restarting last I saw but I didn't even see the "Updating" animation page. The battery was over 60% minimum.
I've tried holding down all the buttons for 4 minutes, I've tried booting into recovery, into bootloader. Nothing. The screen stays black. Not even an animation for charging.
About a half an hour ago I tried plugging it into my computer. Initially there was a response by the PC. A popup came up and said something about Qualcomm <name> being successfully installed or updated. It went so quickly I didn't get a chance to read it. I went looking through My PC trying to find the device and see if I could access the files on it but there was nothing. So I unplugged it. Now I don't even get the Qualcomm thing. Device manager says that it was unable to be identified and I just get a notification saying USB is unrecognized. I've tried uninstalling and updating drivers in Device Manager to no avail. I'm out of ideas. Any thoughts from anyone?
Edit: While having the phone plugged into my PC if I try to access the bootloader mode by holding down the buttons for a longer period of time, my computer responds with noises. Mostly it's just the USB removed noise, but occasionally one sounds off if a new USB device is plugged in.

Resdrak said:
Hey,
So yesterday I decided to finally tinker with my phone. My main issue was that the Wifi kept disconnecting on it's own for no damn reason but no other device would do it. Found out it's a thing with the E4 and the option for disconnecting on a bad connection wasn't there.
At anyrate, I unlocked the bootloader and flashed TWRP. Then things started to go sour. While trying to root the phone, I ended up with no ROM. Tried a couple of different ones. Lineage OS, Resurrection Remix but none could get past the boot animation. Eventually I found the correct (I think) ROM for my phone. I'm in Canada and on Freedom Mobile so I went with the Retail Perry OS from here: https://mirrors.lolinet.com/firmware/moto/perry/official/RETAIL/
I tried installing with TWRP but it said invalid ZIP file so I found another way. Using instructions from https://forum.xda-developers.com/moto-e4/help/rsd-lite-device-connecting-t3671647 I used the rsdlite motorola xml to batch script file thing mentioned. Phone finally worked again! Went about installing the bits and bobs. Was working for a few hours and then I decided to update. I had used an older version of the firmware when the zip file was coming up as invalid in TWRP. The first two or three updates went fine. Downloaded, installed, restarted, fine. Then during one it just... stopped. I think it was restarting last I saw but I didn't even see the "Updating" animation page. The battery was over 60% minimum.
I've tried holding down all the buttons for 4 minutes, I've tried booting into recovery, into bootloader. Nothing. The screen stays black. Not even an animation for charging.
About a half an hour ago I tried plugging it into my computer. Initially there was a response by the PC. A popup came up and said something about Qualcomm <name> being successfully installed or updated. It went so quickly I didn't get a chance to read it. I went looking through My PC trying to find the device and see if I could access the files on it but there was nothing. So I unplugged it. Now I don't even get the Qualcomm thing. Device manager says that it was unable to be identified and I just get a notification saying USB is unrecognized. I've tried uninstalling and updating drivers in Device Manager to no avail. I'm out of ideas. Any thoughts from anyone?
Edit: While having the phone plugged into my PC if I try to access the bootloader mode by holding down the buttons for a longer period of time, my computer responds with noises. Mostly it's just the USB removed noise, but occasionally one sounds off if a new USB device is plugged in.
Click to expand...
Click to collapse
Sounds like you hard bricked it. I had the same thing happen with my E4 Plus. Not sure why this is happening with certain updates even without being rooted or trying to install ota's with stock recovery as you should do. I managed to get mine working again with this tutorial here but you need the right files for your specific device
https://www.google.com/amp/s/forum....-moto-g5-run-morning-post-image-t3776012/amp/
The correct img may be floating around these threads somewhere.

Related

[Q] Bell D803 constant re-boot

A bit of an SOS situation if anyone knows the right steps please
Well, I restored a Titanium Backup and mistakenly toggled the "restore system apk". It ran fine, all restored and then when I rebooted got stuck.
By "stuck", it re-boots constantly. It shows the LG animation, then all I can see is two messages before it starts booting again:
1) "Unfortunately, Google Play Services Has Stopped"
2) "Unfortunately, System UI has stopped
... and then it does the entire boot sequence, animation, again, and again.
Here is what I can do:
* It is in USB debug mode.
* I have drivers on laptop
* I am able to connect with adb and also shell into phone.
* With adb, I have output to the file an "adb bugreport" as well as an "adb logcat".
* I have several backups:
a) The modemsst1.img and modemsst2.img created by Titanium Backup
b) Titanium backups (full apps and data)
c) an "adb backup - all" backup
* I managed to get it into firmware update mode by pressing the volume up button and the power button and then when it flashed red a few times, just the up button. So, I can get it into Firmware update mode.
Of course, I have never really used adb before, except to dabble a bit. So, I am encouraged that I can somehow get into with shell.
I am not unplugging it until I know what to do!
Since then I have been able to turn the phone off and also put it into charging on USB.
This is what worked:
* Hold down power and volume down button until booting stops and phone turns off completely.​
When it does shut down, I kept buttons down until it flashes logo again and then shuts down again. Then I let go. Phone is off and when I plugged in the charger it shows charging animation.
Now, after inspecting the bugreport, I noticed a lot of these messages for all the system apps like this one:
"I/PackageManager(21318): Expecting better updatd system app for com.lge.sizech"​
I think the cause of all this shralp is this, I did a LG Mobile Support Tool "Upgrade Recovery" and then in Titanium Backup I restored an older backup (incl system apks). At least that makes sense seeing all the "Expecting better apdat system app" messages in the bugreport.
Still not sure what to do next
I tried the very good instructions here:
[Guide] Unroot/Unbrick - flash official factory firmware with LG Launche
http://forum.xda-developers.com/showthread.php?t=2471370
The update succeeded. However, when I rebooted the phone it is in the same boot-loop with message that it was before.
I used the BELL D803B10D_00.kdz file. Now I will try with the earlier version BELL D803BA_00.kdz file.
We will see what happens ...
do you have nandroid backup from previous rom?
I have three backups:
1) Titanium Backup (full)
* This was my first backup performed right after rooting device and installing Titanium Backup.
2) Titanium Backup (full)
* Did this 2 days ago. Device was working OK and did as precaution.
3) ADB BACKUP. I did this one before my Titanium restore.
I restored the first titanium backup and that (ooooppps!) was after I did an LG Firmware update.
ALSO:
I am on Windows 7 64 and although adb works fine, fastboot does not. I understand that might be a problem with windows 7 64.
So, unless anyone objects, I am going to redo on my windows 32 machine and also "fastbook oem unlock".
Since firmware is OK, if I do the fastboot oem unlock, that will wipe everything. But I can still boot and re-setip the phone, right?
Just checking before I fudge everything up here ..
ALSO ALSO:
I had antivirus/theft security installed and I disabled it partway through last restore.
Maybe that has somethng to do with this all .
But I am still cool because I can ADB and also firmware install seems ok.
ADB works and that is the one good sign.
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
zekurosu said:
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I don't (didn't) have TWRP installed. How can I sideload without it?
Also, should I adb oem unlock to get it wiped at this point?
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
asdfvtn said:
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
Click to expand...
Click to collapse
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
I used adb uninstall package for many user packages and it was success. But I still see the packages listed in the bugreport?
For example: I already uninstalled "com.benhirashima.skiplock" and also "com.lookout".
Why? What to do to really zap them for good?
Sorry, I posted the wrong link earlier.
This was the guide I used which succeeded but made no difference to the boot-loop.
LG G2 Stock Firmware (Go Back to Stock)
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=d803
Just figured out how to do a factory reset.
http://www.youtube.com/watch?v=3ogBvzbPikc
The hard reset worked and now I am configuring the phone settings!
So, again, this is what I did:
1) http://forum.xda-developers.com/showthread.php?p=45293512
2) http://www.youtube.com/watch?v=3ogBvzbPikc
Not sure if it all worked but I am setting the phone up as we speak (or as I type)
natureburger said:
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
Click to expand...
Click to collapse
Hmm that's strange. Unfortunately for me, I'm already on 64-bit and it still isn't picking it up.
ALL FIXED UP
WORKING 110%
:good:
natureburger said:
ALL FIXED UP
WORKING 110%
:good:
Click to expand...
Click to collapse
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
zprovo said:
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
Click to expand...
Click to collapse
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Then .. do hard reset, exactly like this:
http://www.youtube.com/watch?v=3ogBvzbPikc
Does the hard reset screen show and give you hard reset options?
natureburger said:
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Click to expand...
Click to collapse
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
zprovo said:
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
Click to expand...
Click to collapse
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
4) Which kpz version did you restore to?
5) Did your "adb devices" ever work? Did your "adb shell" ever work?
natureburger said:
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
Click to expand...
Click to collapse
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
zprovo said:
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
Click to expand...
Click to collapse
Hmmmm..... why your adb devices is not working? But the re-pair works and you can then do hard reset.
But that is good information you shared.
Maybe someone else can chime in.
From my experience:
1) adb usb access seems spotty. My win 7 64 connected fine and it even kept the shell through the reboot cycle. But on my win 7 32 machine it was only detecting device and then not able to shell.
2) I was also able to use from the LG website LG MOBILE SUPPORT TOOLS.
Download the LG MOBILE SUPPORT TOOL
I downloaded the most recent one from the LG website and make sure to select your options >> country and then the correct phone model at the upper right hand corner of the tool.
Then install USB driver for correct phone model.
Then see if USB works, "adb device" should return the device code.
"adb shell" should show the shell prompt.
3) There is always fastboot. But I an noob and know 0% about how to properly connect and use it.
Some others please chime in and help this droid bro!

Probable brickage of TN7

Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Evil Penguin said:
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Click to expand...
Click to collapse
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
DJDON1302 said:
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
Click to expand...
Click to collapse
Lol that site ripped my Tutorial! how nice of them, You should of linked the person to https://forum.xda-developers.com/nvidia-tegra-note-7/general/nvidia-tegra-note-7-apx-images-t3149839

Non Hacked/Rooted 6p Shut Off And Will Not Turn On

bought this phone used and I don't think it was rooted but never checked, confirmed. Last night it turned off and will not turn on anymore..
Tried the pwr button for several minutes and no change. Plugged it in with several different cables and no change.
Any other suggestions or options? USB to computer detects something but says it can't install the driver.
Any ideas?
oNe
Can you enter to the bootloader menu? Maybe you can enter recovery and wipe the cache and dalvik
martinfarrell11 said:
Can you enter to the bootloader menu? Maybe you can enter recovery and wipe the cache and dalvik
Click to expand...
Click to collapse
negative, either the phone is totally dead or the screen is dead but NOTHING happens when pwr is pressed
here is what I have tried:
1. Press and hold PWR button for over 3minutes
- Plugged in and unplugged into ac - no change
2. Press and hold volume DOWN + Pwr for over 3minutes
- Plugged in and unplugged into ac - no change
3. Plugged into different a/c power outlets with 2 different chargers - no change
NOT sure what else to try or do?
Funny thing is if ya plug into a computer it does indeed detect "something'
However it says it can't load the USB drivers something about QU_***
Open to any ideas and suggestions.. WHILE I would love to get the phone working whats more high priority for me now is the 20gb's of pics that apparently did NOT back up.
oNe
Sean Price said:
Funny thing is if ya plug into a computer it does indeed detect "something' However it says it can't load the USB drivers something about QU_***
Click to expand...
Click to collapse
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
v12xke said:
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
Click to expand...
Click to collapse
Several threads with no solution. I went through the same "something" . Can't be fixed
v12xke said:
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
Click to expand...
Click to collapse
fixed that issue, aka QHSUSB_BULK is now working properly according to Device Manager.. but Nexus 6P is not detected, and doesn't even show up in Disk Management either.
Any other ideas?
please advise..
oNe
Sean Price said:
fixed that issue, aka QHSUSB_BULK is now working properly according to Device Manager.. but Nexus 6P is not detected, and doesn't even show up in Disk Management either. Any other ideas? please advise.. oNe
Click to expand...
Click to collapse
If you found the right EDL_9008 thread, there is Qualcomm software to download for your PC. If your phone is in the right downloader mode you can use the PC software with a special recovery.img. I don't know anything about it, just read through the threads long ago. It's a mixed bag with some success stories, some not. Keep looking though, I think you are on the right track. The original poster was "Tenfar" if I recall correctly. Good luck.
Try cleaning out the charging port.
Hi there,
I think we are in the same/similar boat. My phone shut off while using it (screen froze, then went black) and seems to have bricked itself. I *am* able to get mine to turn on, but only about once per day after it has been left plugged in for a few hours (although there is no indication it is charging while plugged in - never gets warm, no lights, etc.) I can get into recovery if I am lucky (usually get to the android bot laying on its back, then PWR+VOLUP just causes the phone to shut off instead of actually getting into recovery menu.) I've been able to clear cache/factory wipe from recovery menu with no luck. I never did unlock the bootloader so I am unable to use fastboot to do anything. I tried to flash a few OTA (full and incremental) images using adb when I am able to get into recovery, but they always failed in one way or another.
I've been trying the methods described in the 'tenfar' threads - using the xiaomi flasher and QPST tools. The xiaomi tool always fails for me. I have been able to get the QFIL tool to successfully 'download' about 3 times now, with tenfar's recovery images. However, after the success message, the phone doesn't do anything (I read in other threads it should reboot itself) - and after unplugging, the behavior of the device seems to be the same - just stuck and won't turn on at all.
Right now I think I am stuck in 'EDL' mode where the only evidence that the device isn't completely dead is that it shows up in device manager as 'Qualcomm HS-USB QDLoader 9008 (COM3)', and the factory imager tools do recognize it.
It *seems* like the only way forward is to somehow get one of these factory tools to flash the right set of files onto the device - I've tried a few now with no luck. I even tried extracting the relevant *.img files out of the google factory image download and replacing tenfar's image files with them. I was able to load those onto the device with QFIL. This morning my attempt at turning on the device has me stuck on the white google logo, which is new behavior for me - usually it shows the logo for ~5-10 seconds then the device powers off. I've left it on for a while stuck on the white google image, but I'm not sure if I'm doing anything useful here.
Here are my reference threads:
tenfar's 'debrick' thread
QFIL thread
If anyone has any crazy ideas, I am open to try them. Thank you.
Maybe disable big cores?
apples1678 said:
Hi there,
I think we are in the same/similar boat. My phone shut off while using it (screen froze, then went black) and seems to have bricked itself. I *am* able to get mine to turn on, but only about once per day after it has been left plugged in for a few hours (although there is no indication it is charging while plugged in - never gets warm, no lights, etc.) I can get into recovery if I am lucky (usually get to the android bot laying on its back, then PWR+VOLUP just causes the phone to shut off instead of actually getting into recovery menu.) I've been able to clear cache/factory wipe from recovery menu with no luck. I never did unlock the bootloader so I am unable to use fastboot to do anything. I tried to flash a few OTA (full and incremental) images using adb when I am able to get into recovery, but they always failed in one way or another.
I've been trying the methods described in the 'tenfar' threads - using the xiaomi flasher and QPST tools. The xiaomi tool always fails for me. I have been able to get the QFIL tool to successfully 'download' about 3 times now, with tenfar's recovery images. However, after the success message, the phone doesn't do anything (I read in other threads it should reboot itself) - and after unplugging, the behavior of the device seems to be the same - just stuck and won't turn on at all.
Right now I think I am stuck in 'EDL' mode where the only evidence that the device isn't completely dead is that it shows up in device manager as 'Qualcomm HS-USB QDLoader 9008 (COM3)', and the factory imager tools do recognize it.
It *seems* like the only way forward is to somehow get one of these factory tools to flash the right set of files onto the device - I've tried a few now with no luck. I even tried extracting the relevant *.img files out of the google factory image download and replacing tenfar's image files with them. I was able to load those onto the device with QFIL. This morning my attempt at turning on the device has me stuck on the white google logo, which is new behavior for me - usually it shows the logo for ~5-10 seconds then the device powers off. I've left it on for a while stuck on the white google image, but I'm not sure if I'm doing anything useful here.
Here are my reference threads:
tenfar's 'debrick' thread
QFIL thread
If anyone has any crazy ideas, I am open to try them. Thank you.
Click to expand...
Click to collapse
I have the 100% same issue. Screen froze,then went black and now its stuck in EDL mode. I need my data. Recovery access or anything else would be fine/enough for me. I have had LineageOS and TWRP on the device. With TWRP i can access my data.
How have you got your device on? Mine dont start once a day or so. Its always in EDL mode ( 9008 ).
ncc8uetou5et said:
I have the 100% same issue. Screen froze,then went black and now its stuck in EDL mode. I need my data. Recovery access or anything else would be fine/enough for me. I have had LineageOS and TWRP on the device. With TWRP i can access my data.
How have you got your device on? Mine dont start once a day or so. Its always in EDL mode ( 9008 ).
Click to expand...
Click to collapse
Sorry bud - I never was able to get any further than when I posted this. I eventually gave up, got a full out of warranty refund through my CC after the manufacturer wouldn't help me at all, and upgraded to a Pixel XL. I still do have the device, I should try to boot it up again . I didn't have any data concerns on my device so I was able to give up... good luck!

Trying to get CF-Auto-Root working on Core Prime SM-G360G

Hi guys. So I managed to locate what looks like the only mod out there for a G360G. A CF-Auto-Root image!
I downloaded the root mod and used Odin to successfully flash the images to my phone. I pulled the USB cable out and let it be. It vibrated a few times and I heard the message sound a while later. I plugged it into the computer and confirmed it was all working.
I then used AirDroid to examine the internal file system. I searched for SuperSU but I saw no sign of it. Is it in a protected area where I can't see? I also tried to AirMirror and it said it wasn't rooted.
Since my screen is blank and unresponsive I can't see anything on screen. So although the system works I don't know if any messages popped up telling me it detected a mod and erased it.
Are there any other steps that should be followed after the flash? Software to install before or after? I didn't see anything that said recovery mode needs to be booted or the phone needs turning off after for this particular model.

LG G2 won't turn on

Hi.
To start off, I'd like to say im no expert with phones, I had phones mostly to call, watch videos and listen to music, and this is my first attempt at doing all the stuff I will be describing now.
From the beginning:
I bought a seller refurbished LG G2, which worked fine when I received it, I had to do some updates which my phone found automatically, and it ended at OS version 4.4.2.
I wanted to finally have a decent but cheap phone, however it couldn't play some games I wanted to play and thought "Maybe if I update OS to something new, it will work, and it looks better"
Here my journey to update the phone to Android 11 started.
I was looking at many different videos and guide and everything, how to root, first time I rooted was by accident, only later a better video instructed me how to do it properly, then I installed the trww or whatever its called. then it didnt work properly after using that recovery to install android 11, so I had to flash it to some old version I found for my device (My version is LG D802 btw). For some reason it now had only 11gb of space, instead of 32gb. Anyway, I tried installing root and twrw thing again. After getting root and the recovery program I clicked reboot in its options and now my phone is having an issue.
First off, I left it to charge over 9 hours. If its NOT connected via usb it does nothing, power button, volume buttons do nothing.
I tried connecting it to my phone to flash it, but nope, after few seconds it says my phone disconnected from the usb and try again, even tho it is connected and I can see in device manager that it's seen by my PC. Now, I tried to enter the download mode manually, and it worked.
It says that it's rooted and B0 above it (this number was going down over different roots, twrw installs and flashes and such, no idea what it is.
I tried to flash it again since Im in download mod, however now the main issue appeared. It goes well for 40% of the flash using the LG flash tool 2014, I can see the progress in the download mode on the phone's screen, however once it reaches that certain point it just resets and the program treats it as disconnected.
Now when I have the phone connected via usb it just flashes red between 1 and 3 times, LG logo shows up for several seconds, then it turns off, and repeats the whole process.
During the flashing, software instructed me to remove the batter and try again, so I looked up how to remove it, did it, put everything back together, and its still the same.
Please tell me what to do, I've already spent over 10 hours trying to fix it and I just bought this phone...
hi... if your phone flashes LG logo - i'd recommend a full TOT flash of the original Lollipop image as a starting point...
just make sure you download a proper TOT file for your d802 device (32gb model)...
you'll end up with a working stock Lollipop rom which you can later root and flash a custom rom (i.e. Lineage 18)
Stock TOT file is usually about 2.6-2.7GB in size (at least for my 16gb model)
this youtube video shows how to do it and what is required for the process...
i think there is also an older thread here on XDA on how to TOT flash a G2 device (try to search it)

Categories

Resources