Hello XDA-Community!
After roundabout 8 Weeks of using my LG G4 (last year), it was demaged and restarted all over without a reason - so I contakted my provider for a repair - it was sended to w-support(.com) - it returned but wasn't repaired. Only thing that changed was, that I had Android v5.1 against v5.1.1 before the *repair* and the continuesly restarts were still happening. I tired to enter the Recovery-Mode by button-combination, but this wasn't possible... same for the Hardreset... so I was forced to enter the Hardreset by the running OS - this worked.
(After it was sended directly to LG-Support, it came back and worked again as it should, without 300 restarts a day... some memory-unit was demaged on the bord... however it fine now... BUT...)
Now ... I want to get back this STOCK-RECOVERY-MODE because I want to root this phone now! - last week I was able, after the contakt to LG-Support, to get the Android Update by OTA - for some reason, there are still devices which aren't able to get this update (even by PC-Software), because of something coupled with the IMEI (because the support asked for my IMEI and after only 1 day, I saw the update-info on my screen[?]!). Still strange sh**, but okay however, finally I got the update, but now I am struggled by the problem of the missing Recovery-Mode... what the Hell may I am able to do, to get things running??
I tried the "fastboot" or "LG-Method", by ADB-Connection to the PC, to unlock the Bootloader, but cmd isn't able to find my device, that's the first problem, why I am unable to unlock my bootloader directly, by the LG-Method (let's say LG-Method, because of the steps you have to make on the LG-Website, okay).
So all methods, based on the official Bootloader-UNLOCk are out for me... so what is left or do I have to recover the Recovery-Mode - and if I have to, then please tell me how!^^
By the way - after W-Support repaired my older LG G2 - there's also no Recovery-Mode anymore and also the Hardreset is bombed away, but device runs nicely! - There, I was able to get rootaccess back, by nvflash!
I hope, that I can get help here... this turns me scary as crazy!^^
SW-Update-Mode is availlable by Volume Down, without the battery - coupled to the PC... but the other method, by Volume Up and Power On-Button isn't availlable (?!)... so strange... what they had done to my phone?! - This wasn't meaned by the task to "REPAIR" the phone...
Some (mostly) needed information:
Android v6.0
Baseband-Version: MPSS.BO.2.5.c3-00101-M8992FAAAAnAZM-1.31581.1
Kernel-Version: 3.10.84
Build-Number: MRA58K
Software-Version: V20d-EUR-XX
I'm looking forward to your replies!
With friendly special thanks,
Reaper
>>>EDITED!<<<
Hello again Ladies and Gents,
As far as I am now, I was finally able to find my device below "adb devices", but now I got the thread with the PRE-Rooted System.img:
Link1: Click me!
and
Link2: Click me!
> question is now: "Is this compatible with my device?" - Because, I read "Problem may be because of latest OTA..." - this means the Android vX.X.X -> But which one they got to get the problem as same for the Method itselfs, isn't named in which ANDROID VERSION(S) - this Method is working or NOT!
{
"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"
}
Happy about any responses to me! - As you can see, but only if I do understand this method the right, it might be a method without the unlock of the bootloader, right?
With friendly greeting again,
Reaper
Related
Hi,
I used a long time CyanogenMod 12 and 13 with my LG G3 (d855). Suddenly some problems occurred. I flashed a lot of images and TWRP versions.
Last days I tried to flash wit the LG Tool 2014 original kdz images from LG.
{
"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"
}
I tried:
D85521C_00_1204 (21C).kdz
D85530C_00_0211 (30C).kdz
D85530F_00_0329 (30F).kdz and
Europe D85530B_00_1217 (30B).kdz.
Normally KingRoot and AutoRec worked fine. A short time. After using my phone a few minutes or hours i got bootloops and I had to flash again a clean official ROM. Sometimes I couldn't enter TWRP via buttons.
I think my phone has a hardware failure.
In the past few minutes I tried to flash the 30F image above. Android started regular and asked my which language I want to use. I scrolled down, selected German and the phone rebooted. Now I've a bootloop again. After a few seconds after flashing a original ROM.
Can you help me? Is the phone hardware bricked?
Best regards
Tim
Now I will try http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
Katzenstreu said:
Hi,
I used a long time CyanogenMod 12 and 13 with my LG G3 (d855). Suddenly some problems occurred. I flashed a lot of images and TWRP versions.
Last days I tried to flash wit the LG Tool 2014 original kdz images from LG.
I tried:
D85521C_00_1204 (21C).kdz
D85530C_00_0211 (30C).kdz
D85530F_00_0329 (30F).kdz and
Europe D85530B_00_1217 (30B).kdz.
Normally KingRoot and AutoRec worked fine. A short time. After using my phone a few minutes or hours i got bootloops and I had to flash again a clean official ROM. Sometimes I couldn't enter TWRP via buttons.
I think my phone has a hardware failure.
In the past few minutes I tried to flash the 30F image above. Android started regular and asked my which language I want to use. I scrolled down, selected German and the phone rebooted. Now I've a bootloop again. After a few seconds after flashing a original ROM.
Can you help me? Is the phone hardware bricked?
Best regards
Tim
Edit 1:
Now I will try http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
Click to expand...
Click to collapse
Edit 2:
Same Problem
https://youtu.be/6MlxVDFYpW0
Hi,
I am a complete newbie when it comes to this so please explain in simple terms.
So I will explain as briefly as possible:
- I have Windows 10 x64
- Bought LG G3 last week, it had Android 4.4.2 (and was already rooted)
- It had overheating issues and battery died fast so I tried to update Android via LG PC Suite -> Did NOT work
- I read that having root access blocked it, but that I could update manually
- I installed USB drivers
- I setup ADB and Fastboot
- I tried using LG Flash Tool 2014 and the Android 6.0 KDZ but it did NOT work (always said there was connection error)
- I tried using lgg3rootdotcom's method to reset the phone back to STOCK ROM without root and followed their instructions to the letter (set COM to 41 etc)
- I did everything, but then it keeps coming up with an error on LG Flash Tool (at 6%)
- It repeats "LAF : Bin_User_Mode" three (3) times whereas in the instructional video it only showed ""LAF : Bin_User_Mode" once (1)
- Then "[ERROR] : Partition Change factory Partition (Phone!=tot)"
(I want to share images but I can't because I am a new member with restrictions, I will post images later today)
- I downloaded the .tot and .dll from lgg3rootcom's website
- I tried D855 Europe, Hongkong, and Taiwan .tot but NONE worked
- Now my phone ONLY boots into Download mode :crying:
- I cannot get into Recovery mode or Normal boot...
- I REALLY just want to get it back to stock right now... Please HELP!
Any help will be much appreciated! Thanks in advance!
I used exact instructions from this thread: http://forum.xda-developers.com/showthread.php?t=2772199
But it ERROR appears at 6% with "[ERROR] : Partition Change factory Partition (Phone!=tot)"
Also, please ask any questions if you want to know more so you can help me..
{
"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"
}
Hi everyone,
This is regarding my ASUS ZenFone 2 ZE551ML (1.8 GHz CPU, 4 GB RAM, 16 GB ROM). A few days ago, after 1 year and 11 months of excellent service, suddenly I saw that some of the apps (Play Music, ASUS MiniMovie) were corrupted. But a simple uninstall and reinstall fixed them. Later that day, I was about to open settings when a message popped up "Unfortunately, settings has stopped". Rebooting the phone did not fix it and I was totally stuck as I was unable to clear the data also for the settings app which also requires "Settings" to function. I managed to do a factory reset after which, I could not even get to the home screen because that involves the Settings app as well.
{
"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"
}
I went on to proceed with factory reset from the recovery mode and to my shock, the recovery mode was also corrupted. Screen just froze with a USB logo. I tried to flash the recovery with xFSTK but got write error.
Then I took apart the device and cooled the flash memory (SK hynix manufactured) with some IPA.
The device booted up and was able to get to the home screen. Then I followed the ASUS standard downgrade procedure to downgrade the device from Marshmallow to Lollipop (which should force flashing of the recovery as well and everything). Phone was stable then. Then following ASUS standard upgrade procedure, I upgraded to Marshmallow and did a factory reset again. Set up everything and phone is rock stable now, performs good as new with no slow downs or anything.
My question is "What exactly happened?" It was never rooted and very well taken care of (even looks like new). Is the flash memory failing? Can the firmware get corrupted on its own?
Any answers would be appreciated. Thanks.
Hello I am also having the same issue? Can you please explain more about the way you have recovered. I love my Asus Zenfone2. I am trying to do Factory RESET which causes this issue. Do you mean, use IPA to clean the Memory side? Please help me. My email ID is [email protected]
Firstly, try to flash it with xFSTK using the tutorial here on XDA. If it fails, then you need to take the phone apart.
My 3 year old Moto G5 Plus running android 8 suddenly restarted two days ago and went into Start up failure. It no longer shows My product or IMEI number. It just shows potter 000000000000000 32GB P3B
Bootloader logs read " Start up failure. Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant" written in red.
I have my IMEI and product numbers saved on my pc in a notepad file, but the LMSA software does not recognise my device to even try to rescue it. I want to retrieve files from my phone before attempting a factory reset.
On using the LMSA, it says "lmsa doesn't match appropriate firmware. you can try to select a firmware manually" but then it has no option to select anything manually. I have my phone previously registered on the software on my PC.
I have not rooted my phone, nor used anything other than stock android. My bootloader is locked. I cannot remember if I had Developer options selected or not, most probably not.
On trying to go to recovery mode it says the same message " Start up failure. Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant"
When I connect the phone to the computer, it recognises it (I hear a notification sound) and under Devices it shows under Unrecognised as "Fastboot potter s"
I've never flashed my phone but would it be possible to recover the files in the internal storage of the phone by installing TWRP (in a non rooted, bootloader locked phone) without data loss?
How does it work?
Please help! I really need to recover my photos and notepad notes. Is there any way? Any software?
Please help! Please!
i have the same issue.
can someone help with that .
sharing screenshots of the same.
{
"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"
}
i have the same issue too. ( xt1683)
I'm not responsible for what you do to your device.
Have you seen this post? https://forum.xda-developers.com/t/...d-as-qhsusb_bulk.3636457/page-9#post-76035108. Also read post # 223 about trying this on a Windows 10 machine.
Good luck.
roundaway said:
I'm not responsible for what you do to your device.
Have you seen this post? https://forum.xda-developers.com/t/...d-as-qhsusb_bulk.3636457/page-9#post-76035108. Also read post # 223 about trying this on a Windows 10 machine.
Good luck.
Click to expand...
Click to collapse
I tried this method and didn't work for me. but the device loads bootloader (not on blanck mode)
Hi there,
I have an issue with my S-Pen. it suddenly have stopped working with my device.
I own a N976B Note.
I guess it is an issue with the firmware, because the stylus is recognized on my other devices and the other styluses are not recognized on my note.
To help you understand the history i want to sum up some steps.
1. my phone had a t-obile branding, witch i wanted to remove, so i flashed another csc rom to get rid of that. (back in 2020)
2. After some annoyance by advertisement and the wish to get root and a custom rom, i installed Dr.Ketan Rom and was pretty satisfied, but the hassle with manual updates was a draw back, so i decided to roll back to complete stock to get OTA.
3. After some huslte and some rookie mistakes by trying to install a n975 stock rom on my device, i figured it out and flashed the matching rom. but now the stylus or the digitizer seems to be corrupted. the firmware version is not recognized by the phone. see the screenshot below:
{
"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"
}
After some attempts to get it running again, i installed the very stock rom for my phone several times. (N976BXXS7FUI1)
I even checked "re-partition" and flashed with the matching pitfile in odin.
But there still no luck.
do you guys have some tips?
big thanks in advance!
greeting
Play with it. Spen's can be ornery as mules, once you get it going you're good.
They don't like being neglected for months.
My stock one was neglected. Took a couple days of playing with and then boom it stated charging like nothing ever happened.
Until it shows it's taking a charge it will do nothing. It will play dead.
Try clearing the system cache, reset network, pray to the pagan gods, play with it more... in and out, etc. Try enabling multiple spens, try disabling same... don't cross your spens, use the one for the 10+
Guess it just needs a good fk to get it going
I have 2 10+'s, both stock* and both run very well. Loading custom roms isn't needed, can kill desirable features and makes troubleshooting** much more difficult. That said if you're back on a stock rom the spen and associated hardware/firmware/software are likely good... it's just showing you who's boss. Play with it at least once a day, it will likely perk up in a week and stop it's wallflower act.
*with a package disabler and heavily optimized. I never update if it's running fast and stable; many apps are still running on their factory load as well. One 10+ is running on Pie, one on Q.
**Do Not enable power management. Make sure you didn't disable a needed parent/dependency apk! Do not ever, ever load Android 11 or higher, the kiss of death. Of course I could be mistaken, but probably not...