Related
So I was planning to install the new cloudy g2 3.3 rom on my lg g2. To do this first, i was using a guide that first told me I would have to root with towel root. Which I did, and then I would have to install an auto recovery. My lg g2 is a Canadian d801. However I did not know that the auto recovery I would have to download was the d803 version. After installing the auto recovery my phone is stuck on fastboot mode. I cannot go into recovery or download mode. The screen says
fastboot mode started
udc_start()
when i plug it into my pc, it adds a couple more lines
reset
portcharge
I am stuck. I have found some other information which has told me
1. download autorec for your version
2. extract aboot - boot - laf
3.
fastboot flash aboot aboot.img
fastboot flash boot boot.img
fastboot flash laf laf.img
I have downloaded the d803 auto rec version, and extracted these 3 files. But my phone does not connect to adb. I am currently using the adb and fastboot minimal version, and when i type adb devices nothing shows up. It is important to note that I had installed adb after my phone became bricked like this. The only fix that I can do is to push these files onto my phone. However it does not connect to adb. I have downloaded and installed lg drivers for the lg g2 multiple times. I have gone to device manager and tried to set my up phone to use those drivers, but it does not let me. I will try to attach screen shots below. Please help me fix me phone. I think that if I can connect it to adb I can push the files onto it, but it wont connect. Any help would be much appreciated as I am very inexperienced in this area.
http://forum.xda-developers.com/showthread.php?t=2904404 try this ,see first page
******************Root Recovery Doogee X5 max pro*******************
Your waiting Time IS Now Finished Here is Complete Guide to Root Doogee X5 Max Pro install twrp And More,
Hit :good:
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
Install twrp-
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly, rename twrp to recovery.img
type fastboot flash recovery recovery.img to flash recovery
Type fastboot reboot
Rooting-
Download BETA-SuperSU.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in twrp. Go to Install zip, find SuperSU.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Other Solutions-
i have doogee x5 max-s (i geuss limited editon in algeria ) with mtk6735 . i do evrything and all steps but when i reboot to recovery mode i have ( no command ) in the screen .... how to fix that ? sorry for my ****ty english XD
I had the same Issue but i have found a solution!
After you have flashed the twrp recovery, dont reboot the phone! the "recovery.sh" will replace the twrp on every boot!
Just pull off the battery after flashing, disconnect usb and put the battery back in to the phone.
Now get in to the recovery by pressing volume up and power button together until the select bootmode menue appears.
select recovery with the volume up button and enter with the volume down button.
and now you should be in the twrp main menue.
i hope it works for you too!
greetz from the lizard
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
pitro1 said:
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
Click to expand...
Click to collapse
use sp flash tools to flash recovery, scatter also added with twrp
Flash does not pass the file in the download only option, the process does not start. I reinstalled ROM by firmware mode all ok, but the process of passing recovery on command 12 and 13 of the error message. I manually copied the recovery to the sd and internal memory but also from the error. Does not find the file speaks that it is not a command found.
pitro1 said:
It does not work from step 12, "can not load Recovery.img".
Click to expand...
Click to collapse
Don't use Capital R's
fastboot flash Recovery Recovery.img
Code:
fastboot flash recovery recovery.img
Doogee X5 Max Pro - Update 01/16/2017 + TWRP-3-0-2 & SuperSU-v2.79
Working root for Update 01/16/2017
Title: Doogee X5 Max Pro
Listed: 01/19/2017 11:21 pm
ROM Version: ROM Android 6.0
Doogee X5 Max Pro - Update 01/16/2017
TWRP-3-0-2 + SuperSU-v2.79
Use This Version Flashtool
SP_Flash_Tool_v5.1620.00.000
XN Logos said:
use sp flash tools to flash recovery, scatter also added with twrp
Click to expand...
Click to collapse
Until today I could not do root on x5 max pro. In the method below even downloading the twrp when starting with the power + volume down button start with a menu in Chinese and if you start with volume up + power goes in the default recovery mode.
Same as Pitro1 I am on 16.01 update and I cannot install twrp no matter what I try.
I tried x32 and x64. I tried rebooting directly on recovery or first load system and then adb reboot recovery. I tried to format all first (now I lost my Imei and so on lol). I downgraded and updated again. Downgrading works only with 26.12 version. All others are giving me Colorado lines on the screen and nothing else...
OEM unlock, file transfer, adb, fastboot, drivers detection, are all working good. Only I cannot install twrp...
Also I cannot write nvram nor with SN Writer 2.1504 nor with Imei & SN Writer 1.7.2, MetaAP mode fails all the time...
I'm just about to send it back...
How i rooted my Doogee X5 Max Pro
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
i returned the phone as i had no imei anymore.
i got a new one, i did not put any sim or whatsoever, i just unlocked bootloader, and updated to 16.01 version
then i tried to install twrp via fastboot and it did not work, i did it with sp flash tools as advised and removing the battery prior (don't forget to!). it worked !
Stripe_nl said:
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
Click to expand...
Click to collapse
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Hi. I have tried to root my x5 max pro with flash tools to load TWRP, but it always restarts normally and the TWRP does not come out. I found you and I started to try this method to load the TWRP. Does everything good, unload bootloader and load recovery, but loading the TWRP gives me error .:
Device unauthorized.
This adb's $ ADB_VENDOR_KEYS is nor set; Try adb kil-server if that seems wrong
what I do?
rooting X5 Max pro in Ubuntu 16.04
Hi all, this is my first china phone and I basically bought it only to experiment, I'm a linux power user but this is the first time I 'play' with an android OS.
thanks to multiple guides and posts on this and other forums I'm getting somewhere and learning a lot about how to manage an android OS, I'm sharing a bit of info I unovered about doing this under ubuntu but I'm also stuck and in need of guidance, please help me.
Linux specific issues:
I'm running ubuntu 16.04 LTS, installed fastboot and adb tools from ubuntu repos, with these tools and no other modification to my system I could follow the tutorial on how to unlock the OEM bootloader with adb and fastboot.
accordingly to this post about SP flash tool in linux you might need to blacklist a modem manager module in order for SP flash tool to connect to the phone, you also need to install usb development tools (package libusb-dev) and check through dmesg that your linux OS can actually properly read mediatek usb devices.
After following the above mentioned instructions (both the linux sp flash tool tutorial and the bootloader unlocking howto) I could get SP flash tool linux (multiple version) to see the phone after you connect it while SP flash is downloading the new recovery image and flash it with an ok message.
If you get stuck with a BROM error 1013 remember to start sp flash tool with root privileges.
Phone specific issues:
I can get SP flash tool to flash my phone recovery with an ok message confirmation but the phone keeps rebooting with doogee recovery and not twrp. I'm on the newest stock ROM update (20170116) as of current post date. I've been using 32 bit TWRP images from multiple sources and linux version 5.1620 of spflash tool from their website
so my questions are as following:
1) after reading other posts I think I might have to play with different versions of SP flash tool and TWRP until I get the right combination, I think I might be using 64bit spflash tool for linux to flash a 32bit rom or something like that, can anybody confirm precise version number of the stock rom, TWRP and SP flash tool that worked out for you?
2) should I try to install the whole stock ROM posted in this chinadevices thread before trying to flash only TWRP recovery? please also check the linked thread for multiple custom ROM being ported to this phone, please also note that the full stock rom this poster uploaded (it's in the "all firmware" link) contains another flashing tools with chinese instruction called MultiDownloadTool.
www.china-devices.com/forum/index.php?threads/doogee-x5-max-pro-mt6737-custom-roms.20527/
3) I don't have access to a windows installation right now, but I do have a Win10 VM under Vmware workstation 12 pro, so I could try windows version of sp flash tool, do you guys think that USB passthrough would work?
ibrooks said:
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Click to expand...
Click to collapse
Same here. May a work around would be finding out the oem commands in fastboot. I have seen a tutorial to get them, but you have to be root: https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
I search a simple method
Why all so complicate? I am searching for a simple way to root.
For my old Doogee X5, I discovered just
update-ROOT-DOOGEE_X5.zip
Copy the zip to the micro-SD-card
Settings -> Phone info -> Update -> menu "update local" -> choose zip from micro-SD-card.
Start update.
That's all!
Now I search for such a simple solution for my new Doogee X5 MAX pro.
I do not want any methods with "volume down power", because my X5 MAX pro has the menus after "Volume down power" start in Chinese language.
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
This version finally works ! Thank you
Neaw said:
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
Click to expand...
Click to collapse
Hi there,
I just tried the first file you posted, (twrp-x32-rom), and this one works for me after all previous attempts to boot up TWRP failed. Thanks for the link !
What I had tried before:
I have a relatively new X5 Max Pro, which I ordered a week ago. I updated the firmware to the newest version (20170116) using the OTA update function.
Then I tried to flash TWRP using the files from "needrom.com" which seem to have worked on older versions of the phone/firmware, but did not work for the newer versions.
I tried 32bit and 64bit TWRP versions and flashed them with SP flash tool, but when pressing Vol+/Power the phone would not boot into TWRP recovery. Insted, when selecting "Recovery" from the boot menu, the phone would show the Doogee logo in silver, then blink once, then boot up normally. When repeating this process, then phone boots into Stock recovery, indicating that the TWRP I flashed was replaced by stock recovery.
However, I just flashed the recovery.img from "TWRP LATEST" (the first file posted by Neaw) with SP flash tools and was finally able to boot into TWRP. I installed the superSU-zip 2.79 included in the link, and I am now rooted. Once again, thanks for posting this :good:
Greetz, Ollek74
Doogee X5 MAX! SERIUS PROBLEM......
Hello Guys i have a serious problem with my phone.....i have Malware on it and i cant uninstall it or anything alse.....the worst thing is that my phone not responding in any connection except that charging.....i can't have access on my storage cause this is not allowed or gives the choice! i tried everything but nothing nor the usb debugging or anything else please give me your help!!!!
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.
jeanclaudevandamme said:
Right, I've figured out where things have went wrong but still can't find a fix
1) So after Step 14 after running the BAT files all cmd windows closed. I then clicked step3.bat while in fastboot mode. because he did not explain clearly where you were supposed to get CMD window for commands in Step 16.
I had used CMD / ADB / Fastboot years ago, but I had forgotten how they worked exactly, as the instructions for the previous phones I have rooted were so much better written.
later i discovered how to see what was inside a BAT file (use notepad to open it) so step3.BAT contained instructions to flash "boot1.img" which came with the Dirty Santa v20 files. I don't know what model that boot image was taken from. it also contained instructions to flash a twrp file name that didn't exist (so I guess nothing would have gotten flashed).
2) later I was able to launch into fastboot mode and manually flash the correct twrp file onto the phone. then led me being able to get into twrp recovery to flash kernel + SU.
However phone still didn't boot, presumably of the mistake was previously by clicking Step3.BAT, which flashed a "boot1.img" from dirty santa files
Also when going into download mode, the phone would crash with static 1 second after connection.
3) At the time, I didn't know the difference between aboot and boot files. So I went into fastboot and flashed abootbackup.img
I still don't know fully what aboot does. But the effect it has is it locked the bootloader, so i am no longer able to flash anything with fastboot. writing the old aboot.img has caused my device to go into a corrupt bootloop, cannot launch into recovery.
I think that if I flashed bootbackup.img then things might have worked out ok. i had 2 choices and I picked the wrong one, but that's gone now.
flashing the abootbackup.img also had another effect, download mode no longer crashed with static after 1 second, however a new error code came up when download mode is launched <633A B50>, the phone acts like a firmware is currently trying to be flashed but stuck at 0% even just by launching download mode.
I'm guessing there may be some sort of variant mismatch between the boot1.img and the abootbackup.img as the boot1.img wouldn't have originally come from my phone? As well as the other stuff pushed onto device in Step2.BAT
eithe way, LG Bridge / LGUP do not recognise model even with Uppercut.. LG Flash 2014 has the error messge of "connection to server failed", I tried letting it run in the background without closing error message as suggested in that thread, but I guess because of my 633A B50 error message, flashing did not occur in the background like other people.
----------------
I don't know where to go from here exactly. because
1) boot1.img, that came with dirtysanta files, which model / variant did it come from?
2) what LGUP_common.dll will recognise my device now? I know someone patched their DLL, but how do you patch a DLL using hex editor and how to make the DLL recognise my presumably mismatched device?
3) i don't know what the <633A B50> error message means exactly
------
https://forum.xda-developers.com/v20/help/help-h990ds-t3650303
looks like someone did something similar to what I did. he didn't get answers to his questions and he hasn't been logged in since August..
Click to expand...
Click to collapse
It's more bricked than usual..
Have a go at this?
I like using the LGUP Patched DLL for H91810J. It seems to recognize all variants.
as a last resort use LG Bridge, refurbish. it will repair all sorts of half installs and messed up partitions. the only thing is : IT WILL BRING YOUR BUILD UP TO 10q=================WHICH IS NOT ROOTABLE!!======================
Just in case this issue has not been resolved. I did the same thing 10 minutes ago. I flashed the wrong abootbackup.img (10c) instead of 10d.
All you have to do is open LGUP and if the device won't be recognise, just run the Uppercut tool and the device will show up. Flash your .kdz file and the phone should be running once again.
Hello everybody. Im asking for help and im pretty desperate for my issue.
I have LG G4 h815 20p which was rooted few years back. Then the phone died and got re-balled recently and it works now. But i can not access twrp by using Volume Down and Power buttons combination. I can go to Download mode where i can updated firmware using LG UP and it will be processed to the end and after the required reboot phone stays black and recognized only as qualcom device in device manager.
I can not use ADB as it will never show any devices under adb device neither fastboot devices. Drivers are installed. Tried bunch of different versions on both win10 and win7 but no luck. I also tried installing those on ubuntu, where the phone is seen as a device under lsusb but not under fastboot or adb.
I just want to get the phone up and running. NO matter if i unroot or keep it rooted. It wont be used as daily phone but im eager to fix it.
The phone lists bootloader unlocked on the top of the screen together with LG logo and then comes the android robot animation for 3-4 seconds then loops the same 2-3 times then goes black screen (shows as qualcom device in device manager).
Tried LG UP, LG flash tool neither helped. LG Flash tool wont even end as LG UP finishes but wont boot after the reboot when process is completed.
Any help please will be extremely highly appreciated. I am also willing to arrange team viewer if necessary for easiness.
sbelcovski said:
Hello everybody. Im asking for help and im pretty desperate for my issue.
I have LG G4 h815 20p which was rooted few years back. Then the phone died and got re-balled recently and it works now. But i can not access twrp by using Volume Down and Power buttons combination. I can go to Download mode where i can updated firmware using LG UP and it will be processed to the end and after the required reboot phone stays black and recognized only as qualcom device in device manager.
I can not use ADB as it will never show any devices under adb device neither fastboot devices. Drivers are installed. Tried bunch of different versions on both win10 and win7 but no luck. I also tried installing those on ubuntu, where the phone is seen as a device under lsusb but not under fastboot or adb.
I just want to get the phone up and running. NO matter if i unroot or keep it rooted. It wont be used as daily phone but im eager to fix it.
The phone lists bootloader unlocked on the top of the screen together with LG logo and then comes the android robot animation for 3-4 seconds then loops the same 2-3 times then goes black screen (shows as qualcom device in device manager).
Tried LG UP, LG flash tool neither helped. LG Flash tool wont even end as LG UP finishes but wont boot after the reboot when process is completed.
Any help please will be extremely highly appreciated. I am also willing to arrange team viewer if necessary for easiness.
Click to expand...
Click to collapse
Boot to fastboot and exec
fastboot format userdata
(will obviously erase the whole device including photos etc)
If that does not help you can use SALT to flash TWRP to the BOOT (!) partition. For that you must start SALT from the cli with --experimental argument. If you plan to use SALT I recommend using the latest mAid njghtly which has all already installed.
For flashing with SALT you also must do a custom backup of the sbl1 partition and place the twrp image in the same dir where the sbl1 backup is.
Sent from my OnePlus 7T Pro using XDA Labs
steadfasterX said:
Boot to fastboot and exec
fastboot format userdata
(will obviously erase the whole device including photos etc)
If that does not help you can use SALT to flash TWRP to the BOOT (!) partition. For that you must start SALT from the cli with --experimental argument. If you plan to use SALT I recommend using the latest mAid njghtly which has all already installed.
For flashing with SALT you also must do a custom backup of the sbl1 partition and place the twrp image in the same dir where the sbl1 backup is.
Sent from my OnePlus 7T Pro using XDA Labs
Click to expand...
Click to collapse
Hey, Thank you.
I found your stuff uploaded, but i really cant figure it out. Whenever i press Volume UP and Power button to keep them 6-7sec then plug usb cable, the phone misses the chance to go into download mode. So i have no opportunity to go into fastboot. But i can go in download mode but neither fastboot or salt finds the device.
Could you please provide some more info?
sbelcovski said:
Hey, Thank you.
I found your stuff uploaded, but i really cant figure it out. Whenever i press Volume UP and Power button to keep them 6-7sec then plug usb cable, the phone misses the chance to go into download mode. So i have no opportunity to go into fastboot. But i can go in download mode but neither fastboot or salt finds the device.
Could you please provide some more info?
Click to expand...
Click to collapse
fastboot and download mode are complete different things. you cannot use fastboot commands in download mode.
you have to provide more info:
how do you run mAid? VirtualBox or from an USB stick (recommended)
share the debug log of SALT when your device is in download mode (Advanced menu -> debug log -> upload button -> share just the link)
boot your device in download mode and THEN start mAid first could also help
.-
steadfasterX said:
fastboot and download mode are complete different things. you cannot use fastboot commands in download mode.
you have to provide more info:
how do you run mAid? VirtualBox or from an USB stick (recommended)
share the debug log of SALT when your device is in download mode (Advanced menu -> debug log -> upload button -> share just the link)
boot your device in download mode and THEN start mAid first could also help
.-
Click to expand...
Click to collapse
Hello again.
I figured mAid out. I run from live usb, and i can connect to phone and get the device information through Salt..
What i did:
- i use experimental flag with root privileges and device is read and comes info that my Laf fw does not support direct flashing. (i cant figure it out how this works),
- i made backup of sbl1 partition, downloaded twrp image twrp-3.3.1-PREVIEW-196_g4_MM.img, placed the twrp image in same folder where the backup of sbl1 is.
- Now i dont know how to flash the the twrp to the boot partition. I tried to find some guides but no luck. Yesterday for some reason i had Flash button in salt on the bottom, today it is not there. The way i start salt is by browsing inside /home/android/Desktop/LG directory and use sudo ./SALT.desktop --experimental command. I use the latest mAid from your file server 4.19.126-1-MANJARO - mAid_v2020-07-14_23-43_x86_64_forgetful.iso.
3 attachments are uploaded bellow. The debug log from salt was unable to upload and gave bunch of package errors, so it is attached bellow in a txt file as well.
The phone keeps stable connection in download mode.
Please advice. I am very grateful.
sbelcovski said:
Hello again.
I figured mAid out. I run from live usb, and i can connect to phone and get the device information through Salt..
What i did:
- i use experimental flag with root privileges and device is read and comes info that my Laf fw does not support direct flashing. (i cant figure it out how this works),
- i made backup of sbl1 partition, downloaded twrp image twrp-3.3.1-PREVIEW-196_g4_MM.img, placed the twrp image in same folder where the backup of sbl1 is.
- Now i dont know how to flash the the twrp to the boot partition. I tried to find some guides but no luck. Yesterday for some reason i had Flash button in salt on the bottom, today it is not there. The way i start salt is by browsing inside /home/android/Desktop/LG directory and use sudo ./SALT.desktop --experimental command. I use the latest mAid from your file server 4.19.126-1-MANJARO - mAid_v2020-07-14_23-43_x86_64_forgetful.iso.
3 attachments are uploaded bellow. The debug log from salt was unable to upload and gave bunch of package errors, so it is attached bellow in a txt file as well.
The phone keeps stable connection in download mode.
Please advice. I am very grateful.
Click to expand...
Click to collapse
you start SALT in experimental mode as this in a terminal:
Code:
~/programs/SALT/salt --experimental
anyways the problem is that your LAF version is 100004 so flashing will likely not be possible.. You can try it anyways by using the above cmd which will bring up the flash buttons.
before doing that rename the twrp image to recovery.img to ease up things.
then you select flash (folder) and ensure that anything else then the recovery image is selected (e.g. do not flash sbl1 etc).
also ensure that the target partition is named "recovery" then choose flash.
as said it will likely not work though as your download mode (LAF) is too new though. you could downgrade with LGup to Lollipop which will allow flashing with SALT for sure.
but back to the initial description, you mentioned that:
[...] after the required reboot phone stays black and recognized only as qualcom device in device manager.
[...]The phone lists bootloader unlocked on the top of the screen together with LG logo and then comes the android robot animation for 3-4 seconds then loops the same 2-3 times then goes black screen (shows as qualcom device in device manager).
These indicates very very likely the beginning of the ILAPO. you can check my signature for some workarounds though there is no proper way to fix it other then by replacing the mainboard.
.-