I have Moto g 2nd Gen Indian edition phone
I have been experiencing a strange issue with my phone from past week, when I lock down my phone via power button or closing the cover of magnetic flip-shell or whether it locks it down itself after 'screen time out' automatically the display just shut downs.
The phone is actually working in background as I can see LED notification sometimes. And when I connect my phone to PC via USB it even shows the Internal storage folder. I can even feel vibration on Powering off the device.
When I try to reboot the device, it boots up normally with Motorola logo animation and everything works fine until device gets lock down and this scenario continues as I reboot it again.
Sometime I can feel the bottom speaker grill getting hotter until I 'Power Off' the device forcefully.
So far I have tried fast booting the phone it boots up normally but issue is still there.
I even tried to run the phone in the safe mode but the issue persist even in safe mode.
I even wiped cache partition and also performed 'Factory Reset' via hard reset and soft reset but nothing is working.
I want to clarify that my phone isn't under warranty and also I have not even tempered my phone's software it is completely stock with android version 5.0.2 (recently updated via OTA).
I'm not allowed to post the image as a new user that's why I have written some software specific detail as below.
System version: 22.56.3.titan_retaildsds.retaildsdsall.en.03 retin
Build No: LXB22.99-16.3
Base band version: MSM8626BP_1032.3112.96.00R EMEA_DSDS_CUST
Kernel version: 3.4.42-g0bea67a
[email protected] #1
Wed Aug 26 00:26:33 CDT 2015
I don't think the 'Power Button' can be faulty as it's working as intended properly and almost all the time I use the official Motorola 'Magnetic flip-shells' so I rarely use the power button.
I suspect that this issue may have been caused by some virus or malware as I had visited some torrent hosting and too much ad hosting sites before the issue started.
I contacted Motorola support via chat session and they asked me to get it to the service center, but I have read very bad reviews about service center near my location and I'm afraid to go there.
Although I'm a software developer but in the area of 'Android development' I'm totally noob so joined the XDA to solve the issue with the help of experts.
Can I have some suggestion, solution on this issue? Any help of yours is appreciated.
Also I want to know that if 'Hard reset' can't solve the issue, does that mean the software of device has corrupted?
Try a hard reset first
If not solved use an easy installer
vaisakmct said:
Try a hard reset first
If not solved use an easy installer
Click to expand...
Click to collapse
Well Hello sir thanks for the prompt reply, as I said earlier:
So far I have tried fast booting the phone it boots up normally but issue is still there.
I even tried to run the phone in the safe mode but the issue persist even in safe mode.
I even wiped cache partition and also performed 'Factory Reset' via hard reset and soft reset but nothing is working.
So hard reset is not working for me which I have performed 2-3 times, I guess I have to go through your another suggestion.
Ok, so by 'easy installer' did you mean this method described in below link?
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
I think method in #Post 1 is for my phone.
Does anyone have other solution or advise? Your guidance will be appreciated.
smartandcool3 said:
Well Hello sir thanks for the prompt reply, as I said earlier:
So far I have tried fast booting the phone it boots up normally but issue is still there.
I even tried to run the phone in the safe mode but the issue persist even in safe mode.
I even wiped cache partition and also performed 'Factory Reset' via hard reset and soft reset but nothing is working.
So hard reset is not working for me which I have performed 2-3 times, I guess I have to go through your another suggestion.
Ok, so by 'easy installer' did you mean this method described in below link?
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
I think method in #Post 1 is for my phone.
Does anyone have other solution or advise? Your guidance will be appreciated.
Click to expand...
Click to collapse
ya this one will be best for u
vaisakmct said:
ya this one will be best for u
Click to expand...
Click to collapse
Thank you,
The Easy installer method requires 'USB debugging enabled and RSA key Allowed', so I have enabled 'USB debugging' but I never get the 'RSA key allowed' dialogue.
I tried to attach cable to the different USB ports but I never get the 'RSA Key allowed' dialogue, How can I overcome this issue?
Thats not a pblm get in just fastboot mode click installer and select option for locked boot loader
vaisakmct said:
Thats not a pblm get in just fastboot mode click installer and select option for locked boot loader
Click to expand...
Click to collapse
but as suggested by @reefuge in post #13 and #post16 in link below
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612/page2
that 'Phone must have USB debugging enabled and RSA key Allowed, Usb cable plugged in and in normal use mode'
1. I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated please click to disable"
2. if I go into the Device Manager I can see Android Device
3. I changed my USB-Setting to PTP
but nothing works.
smartandcool3 said:
Thank you,
The Easy installer method requires 'USB debugging enabled and RSA key Allowed', so I have enabled 'USB debugging' but I never get the 'RSA key allowed' dialogue.
I tried to attach cable to the different USB ports but I never get the 'RSA Key allowed' dialogue, How can I overcome this issue?
Click to expand...
Click to collapse
no it does NOT require USB debugging anymore (that was version 1) You must be able to put phone manually into AP FASTBOOT mode by correct key combo
read instruction in zip file and attached here
reefuge said:
no it does NOT require USB debugging anymore (that was version 1) You must be able to put phone manually into AP FASTBOOT mode by correct key combo
read instruction in zip file and attached here
Click to expand...
Click to collapse
Thank you @reefuge sir for the reply.
Does that mean I don't need Phone with 'USB debugging with RSA key allowed'?
All I have to do is to run the 'Magical batch file' of yours and watch the magic show in PC?
Ok one more question, I don't want to irritate you but I'm helpless and confused,
I wanted to ask you that after following this step in sequence:
1] ALL needed files are in the zip file you downloaded TO PC (not phone) including stock ROM files
2] Install Motorola device manager 2.5.4.exe for correct Usb drivers (choose repair if already installed) and install minimal ADB /fastboot v 1.31.exe
3] plug in Usb cable and PUT phone into AP Fastboot Flash mode
4] by holding power and volume down ( - ) until phone powers off to blank screen (may vibrate)
5] still holding both buttons count 1,2,3,4,5 and release both same time
6] Hopefully you should be in AP Fastboot Flash mode with USb cable plugged in?
7] if No go back to step [3] if YES continue
8] do not select anything on phone or press any more phone buttons - All done via pc no
9] Now run the EASY INSTALLER.bat file and watch both pc screen and phone screen
I assume that your program will show me following different menu options:
1)Flash stock ROM --- will flash stock rom / Logo / boot & recovery.img / modem files and bootloader -- this DOES NOT wipe phone so can upgrade / dirty flash keeping settings
2)Lock bootloader --- as above but locks boot loader --- tbh always better to use option 1)
3)Flash Fixed Logo -- Fixes the unlocked Boot Loader Warning EVEN if unlocked still
4)Reboot Phone -- Reboots phone --
5)Factory Reset --- wipes DATA and CACHE --- IF phone hangs at BOOT LOGO, do this Action. ALWAYS use if DOWNGRADING or Coming from A CUSTOM ROM
6)Exit --- Closes command prompt window and exits
from above 6 menu options, which options do I have to follow(related to my phone's condition) in sequence to revive my phone?
I have moto g which is unrooted, stock and with locked bootloader.
You valuable reply is appreciated
smartandcool3 said:
Thank you @reefuge sir for the reply.
Does that mean I don't need Phone with 'USB debugging with RSA key allowed'?
All I have to do is to run the 'Magical batch file' of yours and watch the magic show in PC?
Ok one more question, I don't want to irritate you but I'm helpless and confused,
I wanted to ask you that after following this step in sequence:
1] ALL needed files are in the zip file you downloaded TO PC (not phone) including stock ROM files
2] Install Motorola device manager 2.5.4.exe for correct Usb drivers (choose repair if already installed) and install minimal ADB /fastboot v 1.31.exe
3] plug in Usb cable and PUT phone into AP Fastboot Flash mode
4] by holding power and volume down ( - ) until phone powers off to blank screen (may vibrate)
5] still holding both buttons count 1,2,3,4,5 and release both same time
6] Hopefully you should be in AP Fastboot Flash mode with USb cable plugged in?
7] if No go back to step [3] if YES continue
8] do not select anything on phone or press any more phone buttons - All done via pc no
9] Now run the EASY INSTALLER.bat file and watch both pc screen and phone screen
I assume that your program will show me following different menu options:
1)Flash stock ROM --- will flash stock rom / Logo / boot & recovery.img / modem files and bootloader -- this DOES NOT wipe phone so can upgrade / dirty flash keeping settings
2)Lock bootloader --- as above but locks boot loader --- tbh always better to use option 1)
3)Flash Fixed Logo -- Fixes the unlocked Boot Loader Warning EVEN if unlocked still
4)Reboot Phone -- Reboots phone --
5)Factory Reset --- wipes DATA and CACHE --- IF phone hangs at BOOT LOGO, do this Action. ALWAYS use if DOWNGRADING or Coming from A CUSTOM ROM
6)Exit --- Closes command prompt window and exits
from above 6 menu options, which options do I have to follow(related to my phone's condition) in sequence to revive my phone?
I have moto g which is unrooted, stock and with locked bootloader.
You valuable reply is appreciated
Click to expand...
Click to collapse
FORGET USB debugging and developer options, NOT required - thats NO - IGNORE , not needed
simply install mdm 2.54.exe and ADB v1.31
get phone into Fastboot mode with usb cable plugged in
run easyinstaller.bat
from menu
fmenu options choose [1] and reboot phone [4] to upgrade keeping settings
or [1], [5] and [4] to FULLY wipe and reset phone as new
reefuge said:
FORGET USB debugging and developer options, NOT required - thats NO - IGNORE , not needed
simply install mdm 2.54.exe and ADB v1.31
get phone into Fastboot mode with usb cable plugged in
run eastinstaller.bat
from menu
fmenu options choose [1] and reboot phone [4] to upgrade keeping settings
or [1], [5] and [4] to FULLY wipe and reset phone as new
Click to expand...
Click to collapse
Thank you @reefuge sir for the prompt reply and for your guidance, which actually makes the task easier for me many thanks to you sir.
I will try step '[1], [5] and [4] to FULLY wipe and reset phone as new' as mentioned, and pray to god that my days of misery gets over, to revive my phone.
Do I have to place the 'extracted folder' in my PC's root folder(which is C: drive) or I can place that 'extracted folder' anywhere on PC and execute the 'eastinstaller.bat' from there?
smartandcool3 said:
Thank you @reefuge sir for the prompt reply and for your guidance, which actually makes the task easier for me many thanks to you sir.
I will try step '[1], [5] and [4] to FULLY wipe and reset phone as new' as mentioned, and pray to god that my days of misery gets over, to revive my phone.
Do I have to place the 'extracted folder' in my PC's root folder(which is C: drive) or I can place that 'extracted folder' anywhere on PC and execute the 'eastinstaller.bat' from there?
Click to expand...
Click to collapse
anywhere as it includes (in extracted folder) ALL the files required to make it work
reefuge said:
anywhere as it includes (in extracted folder) ALL the files required to make it work
Click to expand...
Click to collapse
Thank you @reefuge sir for the reply, and I will try this 'Easy Method' and I will keep you posted on its progress.
Once again thank you very much @reefuge sir and @vaisakmct sir as your replies helped me a lot, I hope this issue get resolved soon.
smartandcool3 said:
Thank you @reefuge sir for the reply, and I will try this 'Easy Method' and I will keep you posted on its progress.
Once again thank you very much @reefuge sir and @vaisakmct sir as your replies helped me a lot, I hope this issue get resolved soon.
Click to expand...
Click to collapse
Ok, Guys I was able to run the 'EasyInstaller' and it worked perfectly and magically as it should supposed to be.
Unfortunately I was not able to resolve my problem so It might be something else.
@reefuge sir your 'EasyInstaller' was awesome, and I will highly recommend it to everyone for 1-step solution in need, please keep making these kind of awesome tools.
Thank you @reefuge sir and @vaisakmct once again for all your help. If you have anymore suggestion or solution regarding my problem please let me know.
Related
Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
ODIN download mode
- Turn your device off and unplug it
- Wait 30 seconds (screen off doesn't mean the device has finished turning off)
- Press-and-hold the power button and very shortly after (0.5 seconds, but not simultaneously) press-and-hold the left volume button
- Release the buttons as soon as you see something on screen. You should be looking at a USB icon and a digging Android.
- Make sure the digging Android is flashing. If the USB icon is flashing, press the left volume button to switch to the Android.
- Press the right volume button to select and enter download mode
Bootloader unlock
Flashing this firmware will also unlock the bootloader.
Included languages
Deutsch
English (UK)
English (US)
Espanol
Italiano
Nederlands
Portugues
Instructions (Windows)
- Download and extract the attached Odin zip file
- Download and extract the ROM (you should end up with three .tar.md5 files)
- Go into bootloader mode, as described above
- Start Odin
- Look at the attached Odin screenshot, make sure of the following:
--- Re-Partition: NOT checked
--- Auto Reboot: checked
--- F. Reset Time: checked
--- Flash Lock: NOT checked
--- Phone EFS clear: NOT checked
--- Phone Bootloader Update: NOT checked
- Press the big BOOTLOADER button on the right and select the "BOOTLOADER_P7100BUKC8.tar.md5" file
- Press the big PDA button on the right and select the "PDA_SIGNED_HRI83_BUKDF.tar.md5" file
- Press the big PHONE button on the right and select the "MODEM_HRI83_BUKDF_REV_03.tar.md5" file
- Connect your device with the USB cable
- Wait a few seconds, Odin should say it is now connected
- Hit the Start button, and wait until the device boots
- Press the Thanks button below this post and/or donate
Random notes
"adb reboot recovery", "adb reboot download" and "adb reboot bootloader" now appear to be working, they weren't on the KD9 ROM my device came with.
Download
Here is the link: http://www.multiupload.com/LWN6RHF8WJ
NOTICE: FLASHING ALSO WIPES YOUR SD-CARD !
Chainfire said:
Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
Click to expand...
Click to collapse
Nice gift!
My bootloader was locked before this update, and I did not attempt to unlock it. Download mode tells me the OEM lock is now unlocked. Please confirm! (I may be a dumbass )
Click to expand...
Click to collapse
Do you see the open padlock on the boot logo screen?
bcmobile said:
Nice gift!
Do you see the open padlock on the boot logo screen?
Click to expand...
Click to collapse
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !
Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.
Chainfire said:
Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.
Click to expand...
Click to collapse
Yay! They do work if you do a adb reboot from the shell, but anyway, that's history now.
If you see the open padlock, you're in business. Im guessing that ROM was not meant for general public... in fact, if it came from where I think it came from, it wasn't
EDIT: So it has the stock recovery menu as well? Can you possibly do a system/boot/recovery dump to save us the pain of Odin?
EDIT2:
Chainfire said:
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !
Click to expand...
Click to collapse
fastboot oem unlock
I love Samsung... now
No Chinese at all, what a pity......
is it android 3.0.1 or android 3.1?
My device (bought in a vodafone ita store) has P7100BUKDF ROM and was already unlocked.
Myeah I was able to flash root after flashing this firmware, so it does unlock, it appears.
EDIT: Someone on twitter confirmed this unlocked the bootloader for him as well.
Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method
gjroeleveld said:
Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method
Click to expand...
Click to collapse
If you press enough buttons the menu appears in recovery
Added the SD-CARD wipe notice for ya
How do root this firmware ?
Thanks
http://forum.xda-developers.com/showthread.php?t=1079781 ?
any one know the difference between this one and stock rom? would be interesting to see if samsung changed anything.
Has anyone tried flashing with Heimdall in Linux?
As for the question about the difference with the original ROM I can tell that as mentioned in the first post more languages are supported.
The rest seems about the same as the previous rom.
Yes, it's also the only change I noticed from the stock room, but in my case is great since now it supports Portuguese (my native language).
I just unlocked my bootloader following your steps. It shows unlocked when booting back up but now it is not recognized by my pc when connecting through usb. I tried rebooting both pc and tablet. I also tried uninstalling the drivers from Samsung and reinstalling it but still no go. I have a Galaxy Tab 10.1v from Google I/O and the usb is gone. I cannot even charge from usb now. Are the files posted the correct ones for this device because it is not working. Does anyone have the correct ones? Any help would be appreciated.
The Google I/O Tab as far as I know is not a 10.1v, thus you shouldn't be using these files on it!
Yeah I figured that out now. I was following the root guide and I thought I was supposed to use this. Everything seems to work but the usb. But I can still connect to Odin and reflash. Is there anyway to get it back?
Hello everyone ,
My phone quite recently got soft bricked. It doesn't get past the initial boot image , and i can't even turn the phone off (It keeps rebooting) . I can manage to boot into the screen when you press power button + volume down , but if i click anything there ( such as recovery) , my phone just turns off. Sometimes when i click on recovery , it gets stuck at the TWRP load screen.
I'd be grateful if anybody could help me solve this problem
Go to fastboot mode and again correct flash twrp recovery
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
Flash official twrp
vaisakmct said:
Go to fastboot mode and again correct flash twrp recovery
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
Flash official twrp
Click to expand...
Click to collapse
What do you mean ?
I didn't get you
Anyways , I can't flash TWRP again because I can't enable USB debugging , my phone is stuck in a boot loop.
Any alternatives?
Thanks in advance
Chathur said:
What do you mean ?
I didn't get you
Anyways , I can't flash TWRP again because I can't enable USB debugging , my phone is stuck in a boot loop.
Any alternatives?
Thanks in advance
Click to expand...
Click to collapse
model xt106x?
reefuge said:
model xt106x?
Click to expand...
Click to collapse
Model XT1068
Chathur said:
Model XT1068
Click to expand...
Click to collapse
my signature contains Stock roms for XT1068 with a easy installer - that allows upgrade keeping data - just pick your region (normally 1st rom in post#1)
reefuge said:
my signature contains Stock roms for XT1068 with a easy installer - that allows upgrade keeping data - just pick your region (normally 1st rom in post#1)
Click to expand...
Click to collapse
Alright , thank you!
I'll check it out and get back to you with the result
reefuge said:
my signature contains Stock roms for XT1068 with a easy installer - that allows upgrade keeping data - just pick your region (normally 1st rom in post#1)
Click to expand...
Click to collapse
Hey , I went through your guide , but like I said , I have no means to enable the USB debugging :/
Any solutions ?
Thanks in advance
Chathur said:
Hey , I went through your guide , but like I said , I have no means to enable the USB debugging :/
Any solutions ?
Thanks in advance
Click to expand...
Click to collapse
well obviously you DID NOT as usb debugging NOT required......... this is flashed from pc via usb cable in AP FASTBOOT mode
INSTRUCTIONS for the firmware(s) in my signature
Make SURE you downloaded the correct firmware for your phone Moto G 2nd Gen, this MUST be for your version i.e XT1068 And region.
HOW TO USE:
1] ALL needed files are in the zip file you downloaded TO PC (not phone) including stock ROM files
2] Install Motorola device manager 2.5.4.exe for correct Usb drivers (choose repair if already installed) and install minimal ADB /fastboot v 1.31.exe
3] plug in Usb cable and PUT phone into AP Fastboot Flash mode
4] by holding power and volume down ( - ) until phone powers off to blank screen (may vibrate)
5] still holding both buttons count 1,2,3,4,5 and release both same time
6] Hopefully you should be in AP Fastboot Flash mode with USb cable plugged in?
7] if No go back to step [3] if YES continue
8] do not select anything on phone or press any more phone buttons - All done via pc no
9] Now run the EASY INSTALLER.bat file and watch both pc screen and phone screen
--- END ---
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
MENU OPTIONS
1)Flash stock ROM --- will flash stock rom / Logo / boot & recovery.img / modem files and bootloader -- this DOES NOT wipe phone so can upgrade / dirty flash keeping settings
2)Lock bootloader --- as above but locks boot loader --- tbh always better to use option 1)
3)Flash Fixed Logo -- Fixes the unlocked Boot Loader Warning EVEN if unlocked still
4)Reboot Phone -- Reboots phone --
5)Factory Reset --- wipes DATA and CACHE --- IF phone hangs at BOOT LOGO, do this Action. ALWAYS use if DOWNGRADING or Coming from A CUSTOM ROM
6)Exit --- Closes command prompt window and exits
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Important Info
Upgrading from STOCK ROM example OPTIONS 1,3,4,6
DOWNGRADING from Custom ROM or HIGHER version of STOCK ROM OPTIONS 1,3,5,4,6 --- NOTE --- FACTORY RESET ALWAYS REQUIRED or phone will HANG
Do not unplug USB cable until phone reboots and remember it take 5 to 10+ mins to set up
So might seem stuck after boot animation... this is normal.
reefuge said:
well obviously you DID NOT as usb debugging NOT required......... this is flashed from pc via usb cable in AP FASTBOOT mode
INSTRUCTIONS for the firmware(s) in my signature
Make SURE you downloaded the correct firmware for your phone Moto G 2nd Gen, this MUST be for your version i.e XT1068 And region.
HOW TO USE:
1] ALL needed files are in the zip file you downloaded TO PC (not phone) including stock ROM files
2] Install Motorola device manager 2.5.4.exe for correct Usb drivers (choose repair if already installed) and install minimal ADB /fastboot v 1.31.exe
3] plug in Usb cable and PUT phone into AP Fastboot Flash mode
4] by holding power and volume down ( - ) until phone powers off to blank screen (may vibrate)
5] still holding both buttons count 1,2,3,4,5 and release both same time
6] Hopefully you should be in AP Fastboot Flash mode with USb cable plugged in?
7] if No go back to step [3] if YES continue
8] do not select anything on phone or press any more phone buttons - All done via pc no
9] Now run the EASY INSTALLER.bat file and watch both pc screen and phone screen
--- END ---
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
MENU OPTIONS
1)Flash stock ROM --- will flash stock rom / Logo / boot & recovery.img / modem files and bootloader -- this DOES NOT wipe phone so can upgrade / dirty flash keeping settings
2)Lock bootloader --- as above but locks boot loader --- tbh always better to use option 1)
3)Flash Fixed Logo -- Fixes the unlocked Boot Loader Warning EVEN if unlocked still
4)Reboot Phone -- Reboots phone --
5)Factory Reset --- wipes DATA and CACHE --- IF phone hangs at BOOT LOGO, do this Action. ALWAYS use if DOWNGRADING or Coming from A CUSTOM ROM
6)Exit --- Closes command prompt window and exits
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Important Info
Upgrading from STOCK ROM example OPTIONS 1,3,4,6
DOWNGRADING from Custom ROM or HIGHER version of STOCK ROM OPTIONS 1,3,5,4,6 --- NOTE --- FACTORY RESET ALWAYS REQUIRED or phone will HANG
Do not unplug USB cable until phone reboots and remember it take 5 to 10+ mins to set up
So might seem stuck after boot animation... this is normal.
Click to expand...
Click to collapse
Worked like a charm.
Thank you so much , you saved me a lot of trouble and money.
Words can't express my gratitude.
Thank you.So.Damn.Much!
:fingers-crossed::fingers-crossed::laugh::laugh::good:
Hi,
Last Sunday (5) my phone turns off with 25% battery and just don´t turn on.
I was with the stock Oxygen OS.
Now when i turn it on, the oneplus logo appears and the next "screen" that should be the android or any other OS loading, just don´t appear. It just go to black and turn off.
Reading the Threads here about "OP3T Bricked" they all requests to hold volume up, and connect the usb cable.
The problem is when i do it, the driver just pop up at Device Manager List, and few seconds later it disappears.
(Try it using 4 different computers (Desktop win7 , laptop win7, laptop win 10 and desktop winxp) and 2 original OP cables.)
I had read a lot of informations that you share here in forum, but no tips helps to solve this issue.
So i contact the OnePlus support, they give me some links to download 2 encrypted files that looks like the files you guys shares here (One is the driver and the other is some kind of unbrick tool called MSM).
They connect at my computer and as soon they see that my driver just pop up and disappear, they stop the process and said to me to send the device to one support center.
Probably i will do it, but first i want to guarantee that its nothing i can do here.
So I try to reach my phone throw ADB and fastboot commands.
When at the screen of Fastboot I have some information about the phone and the last line said:
DEVICE STATE - LOCKED
using the command adb devices, we don´t find anything.
using fastboot devices, my device is listed by the serial number.
Should be possible to recover it using fastboot commands ?
There is a way to analyze my phone throw fastboot commands? Something like "all hardware is ok", like the memory, battery, etc ?
Best Regards
I have encountered the same issue while I was playing around with a beta oreo rom the name of which I wouldn't not want to mention here. Got my phone bricked and it wouldn't boot to recovery. Only fastboot was accessible so what I did was just flash the blusaprk v45 recovery and after booting I was finally successful in booting my phone into recovery where I wiped system, data, cache and dalvik without internal storage and flashed a nougat rom. Thankfully I was able to revive my phone and that solved my issue.
UPDATE:
I try to use the fastboot commands, but to do it i must use "fastboot oem unlock"
And guess what?! i can´t ...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.023s
Click to expand...
Click to collapse
So a lot of answer for the people who get this fail is to use the MSM tool .....
Any tips ?
Have you read THIS thread? Try to follow exactly those instructions...
jonsat said:
Have you read THIS thread? Try to follow exactly those instructions...
Click to expand...
Click to collapse
Hi Jonsat,
Yes, i tested and as i said, i can´t do it because the driver don´t still at device manager list.
So, the problem was solved, i need to use the OnePlus Support and converge them to use the files like "my method":
The Regular method is:
1) Hold volume +
2) When holding, plug the phone at PC
3) The device should appear at device manager, so you can run tools like MSM
This method does not work for me because my device doesn't still at device manager list, it just pops up and disappears.
So to make it work i need to:
1) Turn off the phone
2) Hold power + Volume +
3) Plug the phone
4) The phone should start with fastboot menu
5) Select recovery mode
6) hold volume +
Now the driver still on device list.
Using this solution, the files that we see here in forum does not work.
Need to use the files from OnePlus Support, MSM3.08 + OnePlus3T_A56(A57, or newer) + Driver Qualcomm signed 24/04/2013.
Thanks you
Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.
jonsat said:
Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.
Click to expand...
Click to collapse
Glad to help
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY. DON'T DO ANY OF THESE IF YOU HAVE SOMETHING ELSE!
PLEASE SEE "TROUBLESHOOTING" AT THE END OF THE GUIDE FIRST IF YOU HAVE PROBLEMS IN THE PROCESS BEFORE ASKING!
ALWAYS USE DOWNLOAD ONLY MODE OF SP FLASH TOOL.
DON'T TOUCH ANYTHING RELATED TO FORMAT ON SP FLASH TOOL! (IT'S WRITTEN EVERYWHERE, YOU WILL LOSE YOUR IMEIS IF YOU USE FORMAT ALL + DOWNLOAD. YOU ARE SAFE IF YOU USE DOWNLOAD ONLY.)
VIDEO GUIDES
FOR LINUX METHOD CLICK HERE - Credits to @bx2_nero
Windows Method
Requirements:
Bypass Tools Pack - (SPFLASH TOOL, DRIVER AND BYPASS FILES)
Decrypted OFP (OPPO FIRMWARE PACKAGE) Files:
FULL FIRMWARE - INCLUDES THE "USERDATA" PARTITION, HENCE LARGER.
B.53 - Mega - Google Drive - Mirror3
B.37 - Mega - Google Drive 2
B.23 (First RUI Update for the device) - Mega - Google Drive - Mirror3
A.50[EU] - Mega - Google Drive
A.42[EU] - Google Drive - Mirror2
NOU (NO USERDATA) FIRMWARE - FOR PEOPLE WITH LIMITED DATA PLAN.
B.53 - Google Drive - Mirror 2
B.37 - Google Drive - Mirror 2
B.23 - Google Drive - Mirror 2
A.50[EU] - Mega - Google Drive
A.42[EU] - Google Drive - Mirror2
Please read an explanation of what is userdata partition and how different is this from other firmware here.
Note: All files with available links above are tested.
Python (Must add to PATH during installation, see screenshot if you don't understand)
libusb-win32 - Having Issues? Use this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure to choose the last option.
1)Open command prompt by running cmd,
enter
python -m pip install pyusb pyserial json5
After the installation, you can re-run the command. If it looks like the screenshot above you're ready to go to next step.
after the installation leave CMD.
2) Go to driver folder, find the .inf file right click and press install.
3)Download this file and install it, after installing plug your phone to PC by connecting your phone to PC while doing Vol+- . You might need this driver as well if it's not detected.
Press next, connect your device to PC while holding Vol+- buttons (your device needs to be powered off) and you will see the mtkdriver down below. Install it.
Choose MediaTek USB Port and install it.
4)Turn off your phone and again connect to PC while holding Vol+- buttons then run the brom.bat under Bypass folder. If it says "Protection Disabled" in the end you're ready to go on. (If it's like the screenshot below go on.)
If you had a problem here, please check the end of the guide for it's fix.
5)Go into Flash Tool folder and open the SPFlash tool, after that choose scatter file and also if not set, set your download -agent. You don't need to select auth file as authorization is disabled. Once you do it, it should look like this. ALWAYS MAKE SURE DOWNLOAD ONLY MODE IS SELECTED! DON'T SELECT OTHER MODES!
Click choose DA Agent. (I uploaded an updated bypass tools pack, if you're using older download new one) Go into Bypass Tools Pack > Verified Boot Fix > Choose the "DA_6765_6785_6768_6873_6885_6853.bin" file.
If its giving error go into Options menu and disable option shown below. You will be able to choose a DA file.
Make SURE "Download Only" is selected. Don't select ANYTHING ELSE! You will lose your IMEIs, Serial Numbers, Capability of Hardware Attestation etc. if you choose "Format data + Download" make SURE you selected "Download Only".
After flashing it should look like this. Download has been complete. Enjoy!
Now, you can start downloading with the button and after that a checkmark will appear. You can reboot your phone and use it like before now! All your userdata will (inevitably) be cleared!
Spoiler: TROUBLESHOOTING - FAQ AND FIXES
POSSIBLE ERROR: "Verified boot enabled."
There are 2 fixes to this.
1st Method (DIRECT FIX):
Click choose DA Agent. (I uploaded an updated bypass tools pack, if you're using older download new one) Go into Bypass Tools Pack > Verified Boot Fix > Choose the "DA_6765_6785_6768_6873_6885_6853.bin" file.
If its giving error go into Options menu and disable option shown below. You will be able to choose a DA file.
2nd Method (WORKAROUND):
If you're getting this error, and you are SURE you used "Download Only" mode, there's a way to get rid of this. First, load the scatter then untick/deselect partitions listed below.
opporeserve2,
cdt_engineering,
my_custom,
special_preload,
userdata,
super,
After running brom.bat and flashing all partitions except the ones listed above, your phone will be able to reboot to stock recovery. Now select " Power Off" option then go run brom.bat, bypass authorization and then flash partitions listed below from SPFlash Tool.
super,
dtbo,
userdata
Your device will be able to boot into system after this if you have followed steps correctly.
POSSIBLE ERROR: Issues while disabling protection;
Power off your device Restart the process from 2nd step.
POSSIBLE ERROR: Issues while flashing;
Power off your device, you will need to do the bypass again. Check your USB Cable, there might be a disconnection. If not, start from 3rd step and make sure you did everything right.
Spoiler: FOR PEOPLE WHO WANT TO DOWNGRADE AND FOR PEOPLE WHO WERE ON EU VERSION
So, welcome to hell(!).
For people who want to downgrade:
If you want to downgrade to any version you would like, just use the B23 file as it is the oldest ofp file i could find for extracting process. If you were on EU version before (Any version starting with A) download ozip from here(for EU) , here(for Global) and manually flash from Realme UI recovery and format your data. Your device will be back at A.XY firmware with EU features (No heytap, no ads, no theme store, no bloatware) you had before.
For people on EU who want to unbrick:
So, you can use any version starting with B and it should work. It works in my case, i was on A.48, i flashed B53 and over that flashed B23. No probs at all. If you want to return to EU rom (starting with A) download ozip from here and manually flash from Realme UI recovery and format your data. Your device will be back at A.XY firmware with EU features (No heytap, no ads, no theme store, no bloatware) you had before.
Thanks --
https://github.com/bkerler/oppo_decrypt for decryptor.
https://github.com/MTK-bypass for creating the tool.
Thank you for your efforts. Can you add the decrypted A34 file?
mercan01 said:
Thank you for your efforts. Can you add the decrypted A34 file?
Click to expand...
Click to collapse
Hello! I wasn't able to find factory package (ofp) files for any version that makes sense for versions starting with A. (EU). There are A11 and A08 which according to update trackers, did never exist and the A.11 package is %50 larger than all the other files weirdly. I have contacted owner of some sites that do upload files like these and they asked for money. If it's a resonable price i will get it, decrypt it and upload here! If you were able to find any versions starting with A, feel free to message me on telegram (@ctivity) or email me!
Hi, it gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
mercan01 said:
Hi, I have a website that publishes A24 version only. https://www.getdroidtips.com/realme-6-software-update/. It gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
Click to expand...
Click to collapse
Hello again. According to the site you have just sent, A.11 is the first update to EU version. I was thinking it was a mistakenly uploaded file, since userdata partitions are for some reason 9gb with this one instead of 3. If you Downgrade to A11 using SPFLASH tool and this guide and after that install any version included here using recovery, it will work. Unfortunately, these files you sent in the link are ozip files and update packages while ofp files are firmware packages and they include everything. There are only 2 ofps -decrypted and not decrypted- available for now starting with A(EU), A08 (first ever firmware for EU) and A11(first update to EU version).
Hello again. Yes, I noticed there was an ozip file and deleted it.
daeSundae said:
If you Downgrade to A11 using SPFLASH tool and this guide and after that install any version included here using recovery, it will work.
Click to expand...
Click to collapse
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
cmfan said:
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
Click to expand...
Click to collapse
Hello! I'm sorry for the inconvenience I have tried flashing A11 file and it caused several problems just like in your case, however if you didn't select "Format All+ Download" mode you should be able to recover your phone. So, I had the exact same issue today and due to that I will be removing the A11 file from the links. Also, never forget to select Download Mode only! Several people bricked today and their IMEIs, Serial Numbers are all gone! Never select anything else than Download Mode!
So the solution is to download B53 decrypted files, load the scatter and untick listed partitions
opporeserve
,cdt-engineering,
mycustom,
special-preload,
userdata,
super
and then start the flashing in download mode. Now, you might be wondering "How am I going to go into the download mode again?" It's very simple. All you have to do is to keep pressing on Power and Vol- for some time and then, connecting to the pc with both volume buttons pressed while brom.bat is running. If you get an error, just reinstall device filters and that should fix the problem, then you can start downloading. After downloading these partitions to the phone, you will be able to see a boot animation and as well as a realme logo. Reboot to recovery, power of your device and then go into download mode again and flash userdata, dtbo and super partitions this time around. It should boot into system. However, the version will be B.53 but you can use the latest ozip (A.48), flash it from recovery and then format your data. It will bring you back to EU version.
cmfan said:
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
Click to expand...
Click to collapse
So, i just read your reply again.
"Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device."
i dont think it's an issue caused by the device. Can you install oppo drivers from this link and let me know what happens afterwards? Or if you're fast enough you might prefer going into device manager by right clicking on Windows button and uninstall it's driver? I will also request you to start from step 2 to ensure installing drivers. I had the same black screen but my Windows was able to detect the Download Mode when i connected while both volume buttons pressed.
mercan01 said:
Hi, it gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
Click to expand...
Click to collapse
Hello! I have uploaded B23 files both on google drive and mega. It should work for you, it is working for me at the moment. I also was on A48 firmware and both B23 and B53 versions worked without a problem.
daeSundae said:
I had the same black screen but my Windows was able to detect the Download Mode when i connected while both volume buttons pressed.
Click to expand...
Click to collapse
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
cmfan said:
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
Click to expand...
Click to collapse
Well, as far as my knowledge goes BROM is burnt onto SoC and cannot fall into an inaccessible state. You should still be able to do access download mode even if that firmware was corrupt. Do you know if your phone has any charge or not? Can you try different volume and key combinations? A broken firmware shouldn't make the BROM Download mode inaccessible.
cmfan said:
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
Click to expand...
Click to collapse
Oh wait. Is it identifying as fastboot? Then you should be able to (even if you don't have USB debugging authorization) use minimal ADB and fastboot tools to
use "fastboot reboot" command. Please keep pressing vol - button if you can while rebooting if it works. That should, if possible reboot you into recovery.
Also as you said, keeping pressing on power and vol+ buttons don't work in this state. In fact, in this state nothing visually works, there is no screen output and I'm actually pretty sure it's the same for begonia (RN8 PRO). You will need to ~ if it's detecting it as a fastboot device need to use minimal ADB and fastboot tools to get rid of that state. I didn't have the same issue as you though. While I was in same state, I kept on pressing on Vol - and Power buttons for around 30-40 seconds (obviously without a response from the device) and after that pressed both volume buttons and connected device to PC. Can you also try when your device powers off? Because clearly currently your device isn't powered off and cannot be powered off until the battery dies or you can somehow manage to escape from current situation.
MTK Bypass Universal
My screenshots were used in this post. I don't mind
MEGAFON929 said:
MTK Bypass Universal
My screenshots were used in this post. I don't mind
Click to expand...
Click to collapse
I'm sorry for not letting you know Dinolek. I tried to create a guide but my Windows is Single Language and since it's not global version or something I cannot change its language. I had to find an English screenshot. If it's a problem, I'll just remove them.
No, I'm not Dinolek. I just talked to him and he accepted my instructions. Let the screenshots lie, I don't mind.
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Well, as far as my knowledge goes BROM is burnt onto SoC and cannot fall into an inaccessible state. You should still be able to do access download mode even if that firmware was corrupt.
Click to expand...
Click to collapse
Sounds reasonable and I hope it's true.
daeSundae said:
Do you know if your phone has any charge or not? Can you try different volume and key combinations?
Click to expand...
Click to collapse
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
daeSundae said:
Oh wait. Is it identifying as fastboot? Then you should be able to (even if you don't have USB debugging authorization) use minimal ADB and fastboot tools to use "fastboot reboot" command.
Click to expand...
Click to collapse
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
daeSundae said:
Can you also try when your device powers off? Because clearly currently your device isn't powered off and cannot be powered off until the battery dies or you can somehow manage to escape from current situation.
Click to expand...
Click to collapse
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
cmfan said:
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Sounds reasonable and I hope it's true.
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
Click to expand...
Click to collapse
Can you try ADB reboot command on Linux? As it is identifying as a fastboot device?
cmfan said:
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Click to expand...
Click to collapse
If it's detecting a fastboot device, the device isn't dead. What I'm guessing is that your device is working, and on fastboot mode but since there's no display output in this state it will only show a black screen. Can you do ADB devices command? Im guessing adb reboot requires authorization though, but it's worth trying. What I will be requesting from you is to try pressing (and keep pressing on) different key combinations while device is in that state for like a minute or so, for example keep pressing on Vol- and power for a minute then switch to Power and Vol+ for a minute and then keep pressing on both volume buttons and connect device. Can you also see the results after plugging your device into charge and letting it stay for around a minute? I know these might make no sense technically, but in my opinion randomness is your best friend to get rid of situations like this..
cmfan said:
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Sounds reasonable and I hope it's true.
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
Click to expand...
Click to collapse
Hello. again. So, i have asked few people about your situation. Conclusion is, if none of these work you will need to wait until battery wears off and device turns itself off, i'm afraid. I will ask you to not use your phone for like a day and not to keep it connected to a computer for a long time. After making sure it powered off (which, i'm guessing there is actually no way to do that) make sure to prepare the brom.bat file plug in your device with VOL+ - combo and go on. Before doing this make sure to Device Manager > Action > Add Legacy Hardware > Next > Install the hardware that I manually select from a list (Advanced) > Show All Devices > Have Disk > Choose the cdc-acm.inf > Choose Mediatek USB Port and install it to not waste time. I hope your problems will be fixed. I have confirmed that BROM mode shouldn't fall into an inaccessible state because there's no efuse.ini blown. It must be there, but you're probably stuck in a mode that doesn't allow doing anything for some reason.
Hi guys !
We had unlocked the bootloader and after that, had installed twrp but it didn't start in a few attempts. The "Your software cannot be checked for corruption" screen appeared. I had read somewhere that it's just a warning about the risk of installing custom OS and I just should go factory reset, so I did (and that was a stupid idea, I know). And then the bootloop started to happen. My PC can't see my phone and I can't turn it off in any way
To turn it off just hold the power button... while its bootlooping, it will shutdown. Connect the phone to the pc and enter the bootloader. type fastboot devices, if the pc sees it with a question mark but cannot apply the driver, download the bootloader interface driver and set it manually, now retype fastboot devices and your pc will see it in fastboot, after that, reflash twrp or your recovery of choice, wipe all, format data and install your rom of choice.
marianodelfino said:
To turn it off just hold the power button... while its bootlooping, it will shutdown. Connect the phone to the pc and enter the bootloader. type fastboot devices, if the pc sees it with a question mark but cannot apply the driver, download the bootloader interface driver and set it manually, now retype fastboot devices and your pc will see it in fastboot, after that, reflash twrp or your recovery of choice, wipe all, format data and install your rom of choice.
Click to expand...
Click to collapse
i cant turn off, is stuck on fastboot... how i can unbrick???
hold the vol- button and connect usb cable to a computer. it will connect in fastboot mode. From there you can flash twrp again.
Verity. said:
hold the vol- button and connect usb cable to a computer. it will connect in fastboot mode. From there you can flash twrp again.
Click to expand...
Click to collapse
I am having a similar issue after flashing the TWRP image - phone when into boot loop - resetting did not help. Now, it continues to reboot at the LG logo.
I was able to get it into the fastboot menu (once in like 50 times) - but am unsure of how to repeat the steps (to get it into fast boot)
Can you list the steps, and at what time do you press the vol- button, and when to connect USB cable?
Many thanks in advance
MrJoker8989 said:
I am having a similar issue after flashing the TWRP image - phone when into boot loop - resetting did not help. Now, it continues to reboot at the LG logo.
I was able to get it into the fastboot menu (once in like 50 times) - but am unsure of how to repeat the steps (to get it into fast boot)
Can you list the steps, and at what time do you press the vol- button, and when to connect USB cable?
Many thanks in advance
Click to expand...
Click to collapse
i have the same issue, cannot enter fast boot mode
Any news?
@Vargrimst @MrJoker8989
xVeenix said:
Any news?
@Vargrimst @MrJoker8989
Click to expand...
Click to collapse
unfortunately not, i believe i'll have to trash the phone
Vargrimst said:
unfortunately not, i believe i'll have to trash the phone
Click to expand...
Click to collapse
Hey! Don't lose your hope yet. I managed to fix my phone!
So first of all just to be clear - my problem was that after trying to flash ROM using Custom Recovery (in my case it was OrangeFox Recovery) my phone was stuck in bootloop and it did turn on by itself after forcing shut down.
What I did to fix it:
1. I've waited for battery to discharge
2. I've downloaded and installed on my PC:
- LG UPPERCUT - Download here - XDA
- LG Mobile Drivers - Download here - LG.COM
- Android Fastboot Drivers (not necessary needed but i wanted them just to be sure) - Download here - drive.google.com
3. After that I went to search for stock KDZ for my model and my region here (lg-firmwares.com)
4. When everything was downloaded and installed I took my phone and while holding Vol+ I've connected USB cable to my phone (make sure the second part is connected to PC before pluging in to phone) and after few seconds my phone booted into Download Mode
5. Now you need to run LG UPPERCUT - if your phone is listed in upper list then you good to go and if not, check your drivers and errors in Device Manager - select your KDZ in "BIN File", change checkbox from "REFUBRISH" to "UPGRADE", click "Start" and wait.
Your phone will reboot few times but after hitting 100% in Uppercut it will take 2-5 min and boot to stock OS!
xVeenix said:
Hey! Don't lose your hope yet. I managed to fix my phone!
So first of all just to be clear - my problem was that after trying to flash ROM using Custom Recovery (in my case it was OrangeFox Recovery) my phone was stuck in bootloop and it did turn on by itself after forcing shut down.
What I did to fix it:
1. I've waited for battery to discharge
2. I've downloaded and installed on my PC:
- LG UPPERCUT - Download here - XDA
- LG Mobile Drivers - Download here - LG.COM
- Android Fastboot Drivers (not necessary needed but i wanted them just to be sure) - Download here - drive.google.com
3. After that I went to search for stock KDZ for my model and my region here (lg-firmwares.com)
4. When everything was downloaded and installed I took my phone and while holding Vol+ I've connected USB cable to my phone (make sure the second part is connected to PC before pluging in to phone) and after few seconds my phone booted into Download Mode
5. Now you need to run LG UPPERCUT - if your phone is listed in upper list then you good to go and if not, check your drivers and errors in Device Manager - select your KDZ in "BIN File", change checkbox from "REFUBRISH" to "UPGRADE", click "Start" and wait.
Your phone will reboot few times but after hitting 100% in Uppercut it will take 2-5 min and boot to stock OS!
Click to expand...
Click to collapse
thanks, i'll try, i'm not sure about booting into download mode, as i've tried everything let's hope this time goes better... but what about the old flashing, like.. i went in a bootloop because i tryied to install Twrp, will lg uppercut overwrite everything to stock?
Yes. It will flash full Stock LG Firmware with Recovery
Vargrimst said:
thanks, i'll try, i'm not sure about booting into download mode, as i've tried everything let's hope this time goes better... but what about the old flashing, like.. i went in a bootloop because i tryied to install Twrp, will lg uppercut overwrite everything to stock?
Click to expand...
Click to collapse