I would like to thank this wonderful community for all the help I have gotten over the years, I think this should be my first post.
For technical details of all I have done and learned on recovering the damn phone, skip to below the line, the rest is more of an introduction + some history.
In the past I have had a Canadian (BELL) Samsung Galaxy S2.5 as I like to call it. Specs similar to the S3 but not quite.
That was fairly easy to root thanks to odin.
Anyways, I have an LG G2 that I inherited from my brother, so I have some emotional attachment given he passed away 2 years ago (Age 36)... Reason why it is critical that I fix it.
I feel it's a great phone with excellent specs, with some flaws.
Hardware wise, this phone's digitizer seems to fail after a few years and stops registering touches.
Failed on my brother after 8 months, he got it replaced by videotron.
8 months after my ownership, same issue. I replaced the screen, which is a pain.
I dropped it a year later and broke the screen, replaced again.
Replaced the battery twice (First replacement battery was DOA) and... The internals of this phone are a pain to work with... to my limited experience at least.
The get to the point line as stated above.
___________________________________________________________________________________________
I wanted to flash my 4 year old never reinstalled phone, give it new life.
Researched a bit everywhere, verified in the phone what version it is, even most google results tell me this and the replacement screen is all the same.
it's a D801
After some work and research being clueless about working with this model, I finally installed
Started with getting Dev powers by spamming a specific key, setting usb debugging...
Using some application manager.
Installed
D801_AutoRec.apk
Towelroot.apk
From autorec, I installed the twrp and... fastboot... had no idea what that was.
Here I learned how to recover my phone.
This guy... super helpful.
Youtube link removed to post
So in short Download all the necessary drivers to get the android device detected.
Download those
codefi re link removed
I erased and flashed so often now that I scripted it in a batch file
Notepad, save as (not as text) flash****.bat or whatever you want to call it.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot erase dbi
fastboot erase modem
fastboot erase persist
fastboot erase PrimaryGPT
fastboot erase rpm
fastboot erase stl1
fastboot erase tz
fastboot flash boot boot.img
fastboot flash aboot aboot.img
fastboot flash recovery recovery.img
fastboot flash laf laf.img
fastboot flash dbi dbi.img
fastboot flash modem modem.img
fastboot flash persist persist.img
fastboot flash PrimaryGPT PrimaryGPT.img
fastboot flash rpm rpm.img
fastboot flash stl1 stl1.img
fastboot flash tz tz.img
Originally, I only did boot aboot recovery and iaf
After that, my phone rebooted to the LG logo and stuck, but the Download mode is working again.
At that point I did flash a twrp recovery and was able to run it using the command abd reboot recovery
I pushed different roms, but no matter what I do, always back to fastboot.
Found this video later on, originally found a thread here but for the life of me I can't find it anymore (too much history) (How to recover with LG Tools the original kdz
youtube link removed
Now... I could not find the correct firmware
I used this
T-Mobile KitKat D80120A_00
IT worked, my phone restarted as it was before my adventures, but under a tmobile d801
Here I am happy, I get the proper D803_AutoRec.apk
Install the recovery again...
Now I really broke my phone.
Retried the steps above of flashing aboot and so on...
Refuses to work.
So I figured, hey, I recovered it under D801 tmobile... I probably broke it with the D803 recovery.
Back to the download site, made another folder and downloaded all the D801 img's
Ran my script (well that's when I created it from being sick of typing it)
Now I boot Tmobile but it's stuck to All Auto Test - FTM Mode
SUrprisingly on wifi,, shows missed calls and picking up exchange emails...
When I try to Flash as I have before under download, it fails.
SO hey, it found a 300MB tmobile update... why the hell not at this point.
Can anyone link me the proper software I can try to recover the LG Tools ?
csmgdl link removed
and
csmgdl link removed
Don't seem to work
Did I mess it up beyond repair ?
Any recommendations ?
I am hoping for one of the following
If I get tmobile OS working
Retry the D801_AutoRec.apk given it matches the tmobile recovery that somewhat works and then attempt the original goal of setting up CloudyFlex_2.8, CloudyStock_2.7 or cm-12-20150325-UNOFFICIAL-d803
Pretty sure up there, most of those wont work, I just want a working twrp
All I want is this phone wiped with a clean efficient rom to use as a reliable daily.
All I do is phone, text, exchange, camera, some apps... nothing too fancy.
I am off to sleep
Whatever I do, I can't get out of All Auto Test = FTM Mode
Reboot, hold volume up
Down
Up and down
Power up
Power down
Power vol up and down...
Always to all auto test.
Swipe down, get to options, general, do a full factory rest...
Same thing. Grr
Okay dude, take it slow. There's only one way to correctly root/install recovery on this device - that seems to work for everyone.
Tell me if this works. Plug a usb cable from the phone into your PC. Shutdown the phone holding power, release power, hold up. Keep shutting it down and doing this again until you get into "Download Mode". Tell me if you manage this.
Turbine1991 said:
Okay dude, take it slow. There's only one way to correctly root/install recovery on this device - that seems to work for everyone.
Tell me if this works. Plug a usb cable from the phone into your PC. Shutdown the phone holding power, release power, hold up. Keep shutting it down and doing this again until you get into "Download Mode". Tell me if you manage this.
Click to expand...
Click to collapse
I have gone to download mode before to recover an oem image.
Now, I can't get to download mode after trying a number of times.
Ill give it another go tonight. Yesterday I got tired from the research, trial and error.
Thanks for your reply
With a calm mind, I fixed my issue.
https://forum.xda-developers.com/showthread.php?t=2613404
Press and hold power + Vol up and tap normal boot.
Didn't understand that at first.
Now let's see if I will break it again.
Still unsure if I should root it using D801_AutoRec.apk or D803_AutoRec.apk
Reason why I hate this phone.
Videotron LG G2 writes that it's a D801 but I read in other sources that it's a D803.
Now however, it's been restored to a Tmobile Firmware...
Okay, take it really slow. I've just completely rooted, put a custom recovery on and am now on Android N. There's many things which can go wrong - requiring you to restart the process.
Treat it as a D801, as the T-Mobile firmware booted. AutoRec does not root the device. Are you on KitKat or Jellybean? If you're on KitKat, do the following.
You must use IORoot to root the device - it does it in such a way it'll accept custom recoveries.
(You already have the phone's USB drivers obviously)
1) Download IORoot V25 from here.
2) Extract the file.
3) We need to unlock USB debugging, so make sure the phone is not connected to the pc. Settings -> About -> Software -> Tap on "Build" like 8 times fast. Go back into settings and you'll see "Developer Options", tick USB debugging. Now if your device freezes up like mine did when tapping build, then download an app which lets you go directly to developer options.
4) Hook the phone up to the PC, make sure it's not in lock screen.
5) Double click "root.bat" normally (not as admin). Keep going through this process until it brings you to the stock recovery area where you can flash over ADB.
6) It'll walk you through the process where it boots back into Android.
7) Open SuperSU, which it installed.
8) In the settings somewhere, make the grant always accept rather than prompt. My device was bugged not allowing root unless it was forcefully granted like this.
AutoRec - Recovery Install
1) Copy the contents "bumpboot-v1.0-blastagator-signed.zip" and "busybox.apk" and "flashify.apk" onto your device. Download here.
2) Download TWRP for T-Mobile 2.8.6.0 from here, extract recovery.img and copy that onto your device.
3) Copy AutoRec KitKat for T-Mobile here.
4) So you should now have "D801_AutoRec.apk", "recovery.img", "busybox.apk", "flashify.apk", "bumpboot-v1.0-blastagator-signed.zip" on your phone.
5) Proceed to install "AutoRec.apk", ticking unknown sources. Let it boot into recovery. Now reboot.
6) As my recovery didn't stick, install and open "busybox.apk", click install in the program itself. Install and open "flashify.apk", flash recovery, browse using flashify to the location of "recovery.img", let it reboot into recovery. This is where I had to flash "bumpboot-v1.0-blastagator-signed.zip", otherwise I couldn't boot into the OS. So flash that file.
7) Reboot back into the OS. Until we flash lollipop, there wasn't any other way for me to reliably get into TWRP recovery without repeating step 6.
8) Copy over the Bootstack and Stock Rom from here. Don't worry about SuperSU or anything else.
9) Repeat step 6 to boot back into recovery.
10) Wipe everything except internal memory in TWRP.
11) Flash the lollipop bootloader.
12) Flash the lollipop stock rom.
13) Reboot.
14) Now you're able to get back into recovery any time by holding the power + volume down combo, releasing when the screen goes on - and holding it down again.
15) Feel free to flash LineageOS 14.1 or anything afterwards. Make sure to backup your EFS partition at some stage before this - just incase you can't connect to cell towers in the near future.
As you can see, I had to improvise a bit. No guide was good enough to just work in 2017 for my D800. These should work fine for your D801.
Thank you so much for such an amazing and detailed response !!!
After quite a bit more research and work, I got it rooted and got TWRP working.
Once done I uploaded cloudyflex 2.8
Installed it and of course, me being me, chose the wrong install when prompted. It asked Tmobile, other and Canadian 803.
I chose Canadian and after that got back to fast boot.
After that I simply erased boot, aboot and laf, getting ready to restart from scratch but it rebooted on a clean cloudyflex 2.8.
At this point, the phone is running better then stock and I am very happy with it
Your walkthrough is great and I will certainly redo my phone soon again.
For one, practice makes perfect and I certainly like that with your instructions, I will be able to call on the recovery when I want it instead of asking my way into it by adb command.
Thank you again for your time
This community rocks !
Feel free to thumb me. I also have a request for you, I'll PM.
This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.
BackCheck said:
This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.
Click to expand...
Click to collapse
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.
EpicLPer said:
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.
Click to expand...
Click to collapse
Flash Tool is a mighty powerful tool, alright. I couldn't find a good scatter file so in a caffeine deprived state I tried to cobble one together. I may have damaged the preloader. It does show up in device manager but it is different that the VCOM preloader device that was showing. Now it totally crashes Flash Tool too. I'm still working on it but since I have a second watch now, I might just RMA this one and start over.
Again, if anyone has a good scatter file please post it. I found one after the fact but I get errors and it's for another MT2601 device, not the Ticwatch.
The good news is I found if you power down the watch and hold the power button on boot you'll get a long vibrate. If you release the button and hit it 3 or 4 times during the vibrate you'll be in the bootloader.
Anyone have stock or even custom working system.img and boot.img?
great
thank you very much man, i was blocked in twrp recovery after a factory reset, and now i should have installed stock recovery, thanks to your post .
I post this because none of the guides on the internet worked for my phone, and I had to cut my own way through the jungle. Maybe, this helps someone out there. I have found it extremely difficult to flash LineageOS on my LG G5 (H850). It seems that LG changes that device every now and then, and the installation guides on the internet do not fit any more. Flashing Cyanogen on my Samsung S2 was a cakewalk compared to this.
Here is how I - finally - managed to flash LineageOS: I will explain it as a modification to LineageOs.org‘s installation-wiki for the LG-H850 (wiki.lineageos.org/devices/h850/install) and for Linux.
Firstly, I had difficulties with fastboot. It does not work just to download adb and fastboot. You have to properly install them so that you can run them from any directory. Installation guides are all over the net. Fastboot can only be used when you are in the bootloader. That means you have to run „adb reboot bootloader“ first. Other than adb, you have to run fastboot as administrator (i.e. sudo fastboot devices). You will probably forget adding „sudo“ every now and then.
Trying to tackle my fastboot problems I installed the entire Android SDK; I do not know if that is a requirements. People discuss driver problems; fastboot seems to use other drivers than adb. However, from what I can tell the core-issue is to run fastboot as administrator.
Secondly, rebooting into recovery is also extremely tricky. Entering recovery worked for me by pressing volume down + power and releasing only power for a blink of an eye once the LG logo appears. Most instructions tell you that you will enter a fully-fledged recovery menu. My phone presented me a menu which only offered factory data reset. That you have to do although one hesitates to reset the phone.
However, this will only bring you into the TWRP recovery when you earlier have taken the correct exit after flashing TWRP. You should not have left the bootloader by entering „sudo fastboot reboot“, which will simply restart your phone and you have to shut it down again after it has rebooted. If you enter recovery and do the factory data reset then, the phone will not go into TWRP recovery but simply do a factory reset, and you can start from the scratch.
Instead of rebooting, I had to end the bootloader by disconnecting the battery. When I went into recovery by using the above button-combination and did the factory reset, that lead me into the TWRP recovery menu.
Another lesson I have learned is not to use the system update but to run updates manually through TWRP recovery. The system update does not work properly, and the phone will keep booting into recovery. Another flaw well documented all over the net. And don‘t forget that you have to become a developer and to enable debugging again before you can use adb to manually access recovery...
Hi there,
after a normal shutdown, my xiaomi redmi 4 prime is not booting anymore.
it is stuck on MI Logo. I can enter fastboot and download mode. Phone is NOT rooted and Bootloader seems to be locked, but fastboot flash recovery seems to work. But all my hope to get a twrp started failed until now. I REALLY need the files from that phone. If somebody can help me, i will pay you money if you SUCCESSFULLY help me recover the files.
Beside, adb mode does not more work, after trying to fastboot flash a twrp image. But in ADB Mode i was in sideload mode, where no commands like pull did work. Oh and i never turned od developer mode i think. I will not stop believing there must be some person on this planet who can rescue my data.
thanks for any help.
I believe adb and developer mode are irrelevant since they work from within the system. One option is to make twrp recovery boot and copy files from it, but since you tried and failed you could try something else, but as last resort since I don't remember if it saved my data.
Since your bootloader is locked you cannot flash boot partition, but you can flash every other which cold fix your system. You should find EXACT same rom you had and extract partitions you want to flash (you have tutorials online, I don't remember, think you just extract them). If you try to flash complete rom with locked partition, process will fail.
fastboot flash system
fastboot flash recovery
fastboot flash data?!or whatever (or not data if your files are there)
Hope I gave you another perspective..
Hi all,
I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.
Any help please?
Hi, any help please?
Hi all, would anyone like to chime in?
It would seem an update (I think from 2020)has been floating around the net for a while.
I recently decided to revisit my 1050f after I found a replacement screen to change my original one as it was cracked.
At first everything worked Okay but then the tablet decided to do this update,which has totally messed my pad up.
As I have all the old files on my computer from years back,I thought go the the re-install of everything,no matter what I do from Command lines to using "bios restore tool " and intel lite tool with both the original "kitkat" roms and modified roms,nothing will make my pad work again.
I think Lenovo have deliberately released software to break our pads.
I know all my files are good as I have reloaded them before when I was not happy with some things I did.