Related
Hi everyone,
thanks for taking a look at this. I bought a Nexus used and I have spent hours trying to root it. I was able to successfully unlock it a few months ago but I cannot root it.
I boot into flashboot mode using the adb command:
adb reboot bootloader
then flash the recovery:
C:\nexus> fastboot flash recovery cwm.img
sending 'recovery' <6272 KB>...
OKAY [ 0.828s]
writing 'recovery'...
OKAY [ 0.953s]
finished. total time: 1.781s
I have SU in the root directory of the SD card. After flashing the recovery i volume down to recovery and select it. The black Google screen comes up with an unlocked padlock and that is as far as I can get. It will sit on that screen for days if I let it. I've tried other, similar methods as well and get the same result. What should I try now? I've re-installed the drivers several times but that does not seem to help. I have tried this process on my XP laptop and win 7 laptop.
Also, when i try to do a factory data reset on the phone in the system settings it does the same thing.
Also another strange note... when I follow the instructions and hold the vol up and down buttons to get into fastboot mode it does not work. I have to hold only the vol up botton and power button. I do not know if that is relevant but i'm putting it out there just in case.
Any help would be very much appreciated and rewarded!
Are u able to get beyond the screen of Google the if not theb download the nexus factory images Google it out and download and extract and put it in SDK folder where all the adb and fastboot are present the go into fastboot mode and unlock ur boot loader by fastboot oem unlock by opening up a cmd by shift and right click and open cmd here then fastboot reboot boot loader and search for nexus 4 tool by mskip on Google or xda and follow the thread and follow the toolkit to root ur phone
Sent from my XT910 using xda premium
Mohhamad,
I can get past the black Google screen if I just boot up normally.
I have the Toolkit from skip and have tried that process as well. It worked for unlocking but not rooting. I will attempt it again now and see how it goes. Thanks for you suggestion i will update this shortly.
So i tried to boot to my cwm.img file using the toolkit. It put my phone into fastboot mode, installed the image and now my phone is on the black Google screen with 'fastboot status - okay' at the bottom of the screen. I heard the phone disconnect from my PC but it does not reconnect and stays stuck on this screen until i pull the battery.
Relock and then unlock
fastboot oem lock
fastboot oem unlock
make sure you have the right recovery for your phone. You might also have a corrupted recovery partition.
I would try to flash a stock rom so it can put everything back to stock (including stock recovery) then try again.
I've noticed I can not get into Fastboot mode either with UP+DOWN+Power. I can do UP+Power for recovery, thats it. Might be a 4.3 thing.
I locked and then unlocked it, rebooted, and the phone is back to stock. Not sure how that happened... or maybe that was supposed to happen. I tried to to a factory wipe just to see what it would do, sits on the black google screen with the padlock. I think you are right about my recovery partition being corrupted. I am going to see if I can flash a stock ROM like you suggested. Thank you for your help so far!
http://www.wugfresh.com/nrt/ try this and tell me if it helps
Sent from my XT910 using xda premium
Tried it Mohhamad... it's not making any difference. I tried to flash a stock ROM using wugfresh but i get failure to write errors.
I have also tried to go into download mode and see if I could get ODIN to work. Hold the volume down and power button does not work. I'm at a loss I have no idea what to do now. Any other suggestions? What method can I use to flash a stock ROM?
My kindle seems to have stopped booting past the bootloader. I rooted and installed the otterx bootloader & recovery last week along with one of the slimkat roms. Everything was working fine until today when I went to bring the tablet back from standby and it was off.
If I power on the device, the bootloader logo shows for a moment and then the device powers off.
If I press power to open the bootmenu, it works and I can see the kindle in the fastboot devices on my computer.
If I select 'Recovery Boot', the device powers off.
Obviously I'm not screwed here, fastboot access means I can get back to good(assuming it's not a hardware fault of some kind). I'm just trying to diagnose what caused the problem. I've power cycled the kindle before, and the battery was not dead when I found it like this. I have no idea what happened.
Anyone have an idea of what might have gone wrong?
I would charge it. Be sure it is off after plugging it in. Your battery status might be out of sync.
Sent from my Amazon OtterX using XDA Free mobile app
I let it charge all day and still no joy.
I also re-flashed the OtterX recovery and it still won't boot into recovery. Not sure where to go from here.
Kyjibo said:
I let it charge all day and still no joy.
I also re-flashed the OtterX recovery and it still won't boot into recovery. Not sure where to go from here.
Click to expand...
Click to collapse
Ok. Get a fresh download of twrp 2.7.1.0 and flash it again (use ADB)
If that does not work, flash the boot loader again, fresh download.
Ixthusdan said:
Ok. Get a fresh download of twrp 2.7.1.0 and flash it again (use ADB)
If that does not work, flash the boot loader again, fresh download.
Click to expand...
Click to collapse
I re-downloaded TWRP for both the Amazon and OtterX partition schemes. The md5 checked out on both of them.
I flashed the otterx TWRP recovery through fastboot, which claimed it was successful, but was unable to boot to it after selecting it in the bootloader menu
I then used the bootloader to toggle to the Amazon partition scheme and flashed the standard TWRP recovery with fastboot. This also indicated it was successful, but it would not boot when I selected it from the bootloader either.
I am hesitant to flash a the bootloader as it's currently all I have access to at the moment. I guess I don't have any other prospects though, so I'll give it a shot when I get home from work.
Kyjibo said:
I re-downloaded TWRP for both the Amazon and OtterX partition schemes. The md5 checked out on both of them.
I flashed the otterx TWRP recovery through fastboot, which claimed it was successful, but was unable to boot to it after selecting it in the bootloader menu
I then used the bootloader to toggle to the Amazon partition scheme and flashed the standard TWRP recovery with fastboot. This also indicated it was successful, but it would not boot when I selected it from the bootloader either.
I am hesitant to flash a the bootloader as it's currently all I have access to at the moment. I guess I don't have any other prospects though, so I'll give it a shot when I get home from work.
Click to expand...
Click to collapse
Your flashing
Code:
fastboot flash recovery otterx-twrp-2.7.1.0-recovery.img
bootloader is changing to fastboot mode?
could also try an older twrp like openrecovery-twrp-2.6.3.0-blaze.img
sd_shadow said:
Your flashing
Code:
fastboot flash recovery otterx-twrp-2.7.1.0-recovery.img
bootloader is changing to fastboot mode?
could also try an older twrp like openrecovery-twrp-2.6.3.0-blaze.img
Click to expand...
Click to collapse
Yes, when I issue the fastboot commands the tablet changes into fastboot mode and all commands work normally. I will check with an older recovery before attempting the change bootloaders, but I am unsure what difference it will make.
Just to be clear, the device is not boot-looping. It powers off after each boot failure instead of restarting. I'm not sure if the distinction matters, but I wanted to make sure there was no confusion.
I re-flashed the OtterX bootloader and recovery from fastboot with no success, here's what I did.
Code:
> fastboot flash bootloader otterx-u-boot_v2.05.bin
target reported max download size of 402653184 bytes
sending 'bootloader' (233 KB)...
OKAY [ 0.070s]
writing 'bootloader'...
OKAY [ 0.978s]
finished. total time: 1.048s
> fastboot reboot
rebooting...
finished. total time: 0.002s
Recovery - ADVANCED -->
Recovery - PARTITION MODE: AMAZON
Recovery - [CONFIRM] SET MODE: OTTERX
> fastboot flash recovery otterx-twrp-2.7.1.0-recovery.img
target reported max download size of 402653184 bytes
sending 'recovery' (7352 KB)...
OKAY [ 1.901s]
writing 'recovery'...
OKAY [ 1.558s]
finished. total time: 3.461s
> fastboot reboot
rebooting...
finished. total time: 0.001s
Recovery - RECOVERY BOOT
At this point the device powered off. Any thoughts?
I personally never really liked the OtterX Project , i remember giving me only but trouble.
my personal idea, if nothing goes through, is this: change the partition to stock amazon and then, on linux (ubuntu) try installing the recovery with a tool called Soupkit
REPEAT: this is a plan B, if nothing else works you could always do this, hope this helps.. good luck
aaronkatrini said:
I personally never really liked the OtterX Project , i remember giving me only but trouble.
my personal idea, if nothing goes through, is this: change the partition to stock amazon and then, on linux (ubuntu) try installing the recovery with a tool called Soupkit
REPEAT: this is a plan B, if nothing else works you could always do this, hope this helps.. good luck
Click to expand...
Click to collapse
Well, it took me a couple weeks to get to it, but I swapped partition modes and installed the normal FFF bootloader successfully.
I flashed the most recent TWRP through fastboot, but it still shuts off when I select recovery from the bootloader menu.
Any other reccomendations? It just seems to be incapable of leaving the bootloader. Is there anything that we know of that could cause this type of failure?
Kyjibo said:
Well, it took me a couple weeks to get to it, but I swapped partition modes and installed the normal FFF bootloader successfully.
I flashed the most recent TWRP through fastboot, but it still shuts off when I select recovery from the bootloader menu.
Any other reccomendations?
Click to expand...
Click to collapse
flash a different bootloader
It just seems to be incapable of leaving the bootloader. Is there anything that we know of that could cause this type of failure?
Click to expand...
Click to collapse
bad bootloader
I had the same problem today. I Use the EMMC fix and I could start the kindle
and people have reported using the EMMC fix , and getting this problem
How did you managed to do it? Windows or SOUPKIT in Linux?
I highly recomend SoupKit.
Depending on the bootloader and the rom you want to flash you might want to flash either twrp version 2.6.3.1 or 2.7.0.1
Bootloader FireFireFire 1.4a should work just fine.
I remember when i had these kind of problems i did also the emmc fix,
tell me where do you get stuck...
Hey guys,
I'm trying to root my G4 loaded with MM 6.0. I cannot get into Recovery Mode no matter what I do.
I have tried the key combo (power+down, etc) - it does nothing. If I use adb reboot recovery, I just get the dead Android guy with the exclamation in red triangle. (which is perhaps a hint as to why the key combo doesn't work.)
I followed steps to unlock the phone's bootloader via LG's dev site (success) and I've installed TWRP 3.0.2-0-H815.img but I can't get into Recovery mode. **The phone continues to work fine** and I can get it into Download Mode.
After having no success with TWRP, I thought, f*ck it, since I've gone this far, let's go with CyanogenMod instead of stock, so I installed cm-13.0-20160415-NIGHTLY-h815-recovery.img
I was also able to use adb to push CM 13 (nightly build 20160415) and Gapps (arm64 6.0 20160416) successfully to phone, but it's obviously no use since I can't get to Recovery Mode.
I'm wondering if someone can please suggest a solution or at least a next step.
When I use fastboot flash recovery twrp-3.0.2-0-h815.img it takes 0.718s 'send recovery' and 0.282s 'writing recovery'.
[solved - probably Win10's no-ask driver update policy] New problem: After going back to TWRP, fastboot devices shows nothing and my device is showing up in Device Manager as LGE Mobile USB Composite Device, whereas I specifically changed it from the LG drivers I installed to Android ADB drivers. The device doesn't even list the Android ADB driver as an available option now. WTAF?!? Maybe this is more Win10 driver-auto-update malarkey?
OS = Win10x64
Kernal = 3.10.84
Build number = MRA58K
Software version = V20d-EUR-XX
Developer options are available
USB debug is enabled
OEM unlock is enabled
I'm using the stock USB cable
Additional question - tutorials say to back up NVRAM and IMEI before doing anything risky, but I can't get those without root. How does this make sense?
EDIT: NOTE: You should be using the arm64 version of Gapps on LG G4 H815.
Thank you very much to everyone who stops in to take a look at my questions.
All the best,
Dax.
Hi
I had the same problem with Win 10 not seeing my H815 properly (same device name in Device Mgr as yours) I reverted to the older Lge drivers, 4.0.3 if I remember correctly and the phone showed up properly and I was able to use LG UP to update/downgrade etc.
Like you I have since tried to install TWRP but I cannot new get root with Kingroot 480 although it worked previously on V81520D it does not now.
Sent from my iPad using Tapatalk
try fastboot boot recovery twrp-3.0.2-0-h815.img
then tap IMG instead of ZIP (bottom) -> install img and flash the twrp img
Hi Stransky, I reinstalled the adb-setup-1.4.2.exe package which also contains drivers and now ADB will see the phone (which is good), but Fastboot still says waiting for devices (bad). Thanks!
I also changed the default driver from 'LGE Mobile ADB Interface' to 'Android ADB Interface' (as per tutorial instructions).
Hi Bender_007, thanks so much for the tip, I'll try it as soon as I can get Fastboot working again. Cheers!
Okay, so I learned ADB is for Android or Recovery mode, Fastboot is for 'HBOOT' (bootloader) mode.
As expected:
adb devices returns "List of attached devices: LGH81579d3bc56 device".
If I use the command adb reboot-bootloader, phone restarts in bootloader mode.
Then adb devices does nothing, but fastboot devices returns "79d3bc56 fastboot".
When device is in bootloader mode, it shows up in Windows Device Manager as 'Marshall London Bootloader Device'.
Bender_007, the command "fastboot boot recovery twrp-3.0.2-0-h815.img" doesn't work. It's invalid syntax. "fastboot flash recovery twrp-3.0.2-0-h815.img" works as per original post.
Any other suggestions?
Hm, put the twrp inside the same folder where your fastboot and adb are. Then start command prompt in the very same folder and type fastboot boot twrp... And that should be it. That means if everything is normal and the system is bootable.
Pardon, fastboot boot twrp(whatever the name is)
Not: fastboot boot recovery twrp..
Sent from my LG-H815 using Tapatalk
Hi Bender_007, that's exactly where the .IMG files are already. No dice. :/
May I see this via teamviewer please ? (teamviewerQS via private message)
I´ll gladly help you (if it´s in my possibilities ofc)
@daxliniere
EDIT: 21.04.2016 - we have fixed this, had a nice talk, almost a beer. It´s nice to meet new cool people , keep it up my friend
I am stuck probably on the same issue with win10. It seams like I was able to flash twrp recovery but I can't enter it. Already factory reseted it 3 times while trying to enter into custom recovery.
Any advices what to do?
madik_ said:
I am stuck probably on the same issue with win10. It seams like I was able to flash twrp recovery but I can't enter it. Already factory reseted it 3 times while trying to enter into custom recovery.
Any advices what to do?
Click to expand...
Click to collapse
The best solution there is:
1. put adb, fastboot into a directory (let´s say c:\adb), put the twrp-3......img into the same folder
2. adb reboot bootloader
3. open command prompt, cd c:\adb
4. fastboot boot twrp-3.....img (where twrp-3....img is the actual name of the twrp img)
it will boot to twrp, now you can either copy the twrp img to the phone and flash it(it will ask where to flash - tap on recovery--don´t tap on boot)
You might have to tap on zip/img toggle to enable img flashing first
should you need more help just post in here
Yep that did the trick. thank you! I was able to load recovery with the fastboot boot twrp.. but didnt realize that i can install it by the loaded twrp lol. Now I can finally confirm 2x YES and it gets me into TWRP. thanks again!
Can I make one little tip for everyone else? Follow this guide to the end: http://www.technobuzz.net/unlock-lg-g4-bootloader/
Step 1 is the easiest way to install adb, fastboot and drivers in one go.
Same problem here:
Software version = V20d-EUR-XX, Developer options are available, USB debug is enabled, OEM unlock is enabled
I can boot into recovery via bootloader: fastboot boot twrp-3.0.2-0-h815.img but:
1. had I to allow to modify system partition modifications?
2. how can I boot in recovery from system? with adb I always get the red-triangle Android on its back und with hardwarekeys after shut down the devise, I#m coming to stock recovery: factory restet no/yes
1. Yes
2. While you are in twrp just flash the twrp IMG again via twrp itself. It has the option to flash img instead of zip.
Poslano sa mog SM-G930F koristeći Tapatalk
thx, a lot...
Now im running a full system update to exsdcard and afterwards I try to "re-"install the twrp in twrp-applikation.
When i boot into recovery at the moment, the "modify-dialog" is away...
But I will see after "re-"install the twrp how it works...
---------- Post added at 03:48 PM ---------- Previous post was at 03:00 PM ----------
UPDATE:
Did it, worked!!!
on system: "adb reboot recovery" leads to twrp!
there are no hardware-key-solutions to get to recovery...
with the hardware-keys (after shutdown -> power + vol down -> release power for a second when LG-logo pops up) I get to the factory reset no/yes dialog...
On the factory reset choose yes twice. Normal for lg
Poslano sa mog SM-G930F koristeći Tapatalk
I got nervous to choose yes the second time....
sejmand said:
I got nervous to choose yes the second time....
Click to expand...
Click to collapse
Install Quick Boot from the Play Store,you can boot straight to Twrp with it
fastboot erase recovery
fastboot flash recovery xxx.img (xxx=twrp.img)
Hello,
I am still struggling with my h815 on 7.0:
I am getting the error sign with "no commands".
I cannot force it to boot to the twrp but I can flash it (unknown command):
HTML:
student:~/Downloads$ sudo fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (32992 KB)...
OKAY [ 1.106s]
writing 'recovery'...
OKAY [ 0.931s]
finished. total time: 2.037s
student:~/Downloads$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.104s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.121s
using ubuntu 16.04.
Thanks for your feedback in advance.
long story short, incase any of these are the reason why my phone can't get twrp recovery.
History:
Around 3-4 months ago I updated my phone to Color os 2.0.8i(if not mistaken). Not sure if I did root my phone or not. My phone screen broke, and touch screen spoiled, not using it until I repaired it few days ago. After repair decided to use CM13 and took me awhile to figure out how to flash TWRP and took me quite sometime to root my phone. After successfully rooting my phone, I started to install CM13 snapshot bcos i tot the nightly is not stable. But it failed. My phone can't turn on and can't go to recovery. Keeps boot to fastboot. Figured out i need to use some code like fastboot oem unlock(can't really rmb if this was the code I used) then flash my recovery again and my recovery works. But my phone still can't turn on. I use TWRP recovery to flash the same rom again to see if it works this time, but no it doesn't. i think i did try the CM13 nightly rom but it doesn't work too so i searched a lot about how to install CM13 on Find7. This link(http://forum.xda-developers.com/fin...0-marshmallow-unofficial-cm13-oppo-7-t3227311) said that Color OS 2 &2.1 needs to flash Color OS 1.2.8 and i did it. I did not flash the stock recovery. I use fastboot boot stockrecovery.img. Then, I install the stock rom using the stock recovery. The link says let it boot, and after that reboot back to TWRP recovery. After successfully booting into Color OS 1.2.8i, I switch off my phone and press down button + power button but the stock recovery came out. From that onwards i keep trying to flash TWRP recovery to my phone but it failed. I used fastboot flash recovery twrp.img and press volume down button + power button, fastboot boot twrp.img, fastboot erase recovery and fasboot flash recovery twrp.img and fastboot boot twrp.img all that doesn't work even the cmd said okay twice. All it does just either boot up the oppo logo and turn back off and turn on again with the logo and turn on the phone normally. OR it just boot up the stock recovery. I have read it some where that some stock rom will overwrite the custom recovery with its stock recovery so needs to delete some recovery file and edit the updater script. I did it and try to install the rom again after editing, but it failed. I tried installing another 1.2 color os(without editing the inside hoping this rom doesn't have the ability to overwrite the custom recovery) it did tried to install but up to about 40% of the loading bar, it says fail. I tried many times, I even factory reset my phone and try installing again but TWRP just can't be booted.
Problem:
- I can't get to TWRP recovery.
- Without TWRP I can't install custom rom or root my phone
Please help me. I have wasted about 4 days time just to install the CM13...
ron8899 said:
long story short, incase any of these are the reason why my phone can't get twrp recovery.
History:
Around 3-4 months ago I updated my phone to Color os 2.0.8i(if not mistaken). Not sure if I did root my phone or not. My phone screen broke, and touch screen spoiled, not using it until I repaired it few days ago. After repair decided to use CM13 and took me awhile to figure out how to flash TWRP and took me quite sometime to root my phone. After successfully rooting my phone, I started to install CM13 snapshot bcos i tot the nightly is not stable. But it failed. My phone can't turn on and can't go to recovery. Keeps boot to fastboot. Figured out i need to use some code like fastboot oem unlock(can't really rmb if this was the code I used) then flash my recovery again and my recovery works. But my phone still can't turn on. I use TWRP recovery to flash the same rom again to see if it works this time, but no it doesn't. i think i did try the CM13 nightly rom but it doesn't work too so i searched a lot about how to install CM13 on Find7. This link(http://forum.xda-developers.com/fin...0-marshmallow-unofficial-cm13-oppo-7-t3227311) said that Color OS 2 &2.1 needs to flash Color OS 1.2.8 and i did it. I did not flash the stock recovery. I use fastboot boot stockrecovery.img. Then, I install the stock rom using the stock recovery. The link says let it boot, and after that reboot back to TWRP recovery. After successfully booting into Color OS 1.2.8i, I switch off my phone and press down button + power button but the stock recovery came out. From that onwards i keep trying to flash TWRP recovery to my phone but it failed. I used fastboot flash recovery twrp.img and press volume down button + power button, fastboot boot twrp.img, fastboot erase recovery and fasboot flash recovery twrp.img and fastboot boot twrp.img all that doesn't work even the cmd said okay twice. All it does just either boot up the oppo logo and turn back off and turn on again with the logo and turn on the phone normally. OR it just boot up the stock recovery. I have read it some where that some stock rom will overwrite the custom recovery with its stock recovery so needs to delete some recovery file and edit the updater script. I did it and try to install the rom again after editing, but it failed. I tried installing another 1.2 color os(without editing the inside hoping this rom doesn't have the ability to overwrite the custom recovery) it did tried to install but up to about 40% of the loading bar, it says fail. I tried many times, I even factory reset my phone and try installing again but TWRP just can't be booted.
Problem:
- I can't get to TWRP recovery.
- Without TWRP I can't install custom rom or root my phone
Please help me. I have wasted about 4 days time just to install the CM13...
Click to expand...
Click to collapse
You forgot fastboot oem unlock. Also not all twrp versions work. Try and see. Recap: fastboot erase cache, fastboot oem unlock and fastboot flash recovery followed by twrp. img. After that press and hold power and volume down simultaneously and you should be in twrp.
My steps with fastboot oem unlock
tropical cactus said:
You forgot fastboot oem unlock. Also not all twrp versions work. Try and see. Recap: fastboot erase cache, fastboot oem unlock and fastboot flash recovery followed by twrp. img. After that press and hold power and volume down simultaneously and you should be in twrp.
Click to expand...
Click to collapse
Hi, thanks for your reply. It didn't work again. Here is what I did maybe you can see what mistake i made:
1) volume up + power button get to fastboot.
2) plug my phone in to computer
3) right click in platform-tools folder + shift and choose open command window here
4) fastboot erase cache
result
5)******* Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.029s]
finished. total time: 0.029s
i continued
6) fastboot oem unlock
result
7)...
OKAY [ 0.003s]
finished. total time: 0.003s
i continued
8) fastboot flash recovery twrp-3.0.2-0-find7.img
result
9) target reported max download size of 536870912 bytes
sending 'recovery' <10894 KB>...
OKAY [ 0.344s]
writing 'recovery'
OKAY [ 0.163s]
finished. total time: 0.507s
10) i unplug the phone from computer
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
ron8899 said:
Hi, thanks for your reply. It didn't work again. Here is what I did maybe you can see what mistake i made:
1) volume up + power button get to fastboot.
2) plug my phone in to computer
3) right click in platform-tools folder + shift and choose open command window here
4) fastboot erase cache
result
5)******* Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.029s]
finished. total time: 0.029s
i continued
6) fastboot oem unlock
result
7)...
OKAY [ 0.003s]
finished. total time: 0.003s
i continued
8) fastboot flash recovery twrp-3.0.2-0-find7.img
result
9) target reported max download size of 536870912 bytes
sending 'recovery' <10894 KB>...
OKAY [ 0.344s]
writing 'recovery'
OKAY [ 0.163s]
finished. total time: 0.507s
10) i unplug the phone from computer
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
Click to expand...
Click to collapse
All steps correct. Try earlier twrp versions. I remember 2.8.6.0 works.
tropical cactus said:
You forgot fastboot oem unlock. Also not all twrp versions work. Try and see. Recap: fastboot erase cache, fastboot oem unlock and fastboot flash recovery followed by twrp. img. After that press and hold power and volume down simultaneously and you should be in twrp.
Click to expand...
Click to collapse
i realise something different this time. i switch off my phone and hold volume down + power button to go to the recovery. Usually it goes to the stock recovery but this time it doesn't it just turn on the phone like just now. it repeat these steps.
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
tropical cactus said:
All steps correct. Try earlier twrp versions. I remember 2.8.6.0 works.
Click to expand...
Click to collapse
alright thanks i'll go and try
tropical cactus said:
All steps correct. Try earlier twrp versions. I remember 2.8.6.0 works.
Click to expand...
Click to collapse
I tried the 2.8.6.0 twrp. i repeated all the steps. erase cache, oem unlock, flash twrp and hold the volume down + power. this time it shows oppo logo. after awhile at the oppo logo screen, it glitch a little. Then it shows a black screen with light. but there is nothing. I tried to touch the screen nothing seems to happen...
i also tried 2.8.5.0 and it repeat this
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
ron8899 said:
I tried the 2.8.6.0 twrp. i repeated all the steps. erase cache, oem unlock, flash twrp and hold the volume down + power. this time it shows oppo logo. after awhile at the oppo logo screen, it glitch a little. Then it shows a black screen with light. but there is nothing. I tried to touch the screen nothing seems to happen...
i also tried 2.8.5.0 and it repeat this
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
Click to expand...
Click to collapse
Well, sorry to hear that. I'm out of ideas.
tropical cactus said:
Well, sorry to hear that. I'm out of ideas.
Click to expand...
Click to collapse
Alright thanks anyway. Hopefully someone out there can help?
ron8899 said:
Alright thanks anyway. Hopefully someone out there can help
Click to expand...
Click to collapse
Have you tried CWM recovery?
tropical cactus said:
Have you tried CWM recovery?
Click to expand...
Click to collapse
I haven't tried cwm yet. Cos i have used twrp on this phone before... wondering why i can't use twrp now...
ron8899 said:
I haven't tried cwm yet. Cos i have used twrp on this phone before... wondering why i can't use twrp now...
Click to expand...
Click to collapse
Try it. It might work. Does the same thing anyway.
tropical cactus said:
Try it. It might work. Does the same thing anyway.
Click to expand...
Click to collapse
i tried. using the X9007_CWM_recovery.img.
OKAY twice.
used volume down + power button.
logo showed up and stuck at the logo for a long time
the 3 buttons(back, home & menu buttons) light up
if i used fastboot boot method, the fastboot screen lightup brightly, and stuck there. and the three buttons light up too...
ron8899 said:
i tried. using the X9007_CWM_recovery.img.
OKAY twice.
used volume down + power button.
logo showed up and stuck at the logo for a long time
the 3 buttons(back, home & menu buttons) light up
if i used fastboot boot method, the fastboot screen lightup brightly, and stuck there. and the three buttons light up too...
Click to expand...
Click to collapse
Okay. Last one. Since you have unlocked bootloader i. e. Fastboot oem unlock, try using flashify from play to install twrp and see if that works. Try a few versions of twrp.
Edit. Go back to stock recovery first and start again. Good luck.
tropical cactus said:
Okay. Last one. Since you have unlocked bootloader i. e. Fastboot oem unlock, try using flashify from play to install twrp and see if that works. Try a few versions of twrp.
Edit. Go back to stock recovery first and start again. Good luck.
Click to expand...
Click to collapse
U mean I should try flashing stock recovery using cmd, after that then I use flashify flash twrp?
ron8899 said:
U mean I should try flashing stock recovery using cmd, after that then I use flashify flash twrp?
Click to expand...
Click to collapse
Yes, so you have a working recovery. Check that it is installed first. Then fastboot erase cache and fastboot oem unlock. Reboot, download flashify and flash twrp. img and then try to enter recovery.
tropical cactus said:
Yes, so you have a working recovery. Check that it is installed first. Then fastboot erase cache and fastboot oem unlock. Reboot, download flashify and flash twrp. img and then try to enter recovery.
Click to expand...
Click to collapse
Alright, I saw two flashify in play. Which one is it? The one with the requires root?
ron8899 said:
Alright, I saw two flashify in play. Which one is it? The one with the requires root?
Click to expand...
Click to collapse
Yes, the one from rashr. Skip all warnings and proceed. Put your twrp.img on sd card first.
tropical cactus said:
Yes, the one from rashr. Skip all warnings and proceed. Put your twrp.img on sd card first.
Click to expand...
Click to collapse
oh.... i can't get my stock recovery work... it always shows half of the reocvery screen only.... and the recovery screen keeps glitch. what should i do?
this is where i download the stock recovery
http://community.oppo.com/en/forum.php?mod=viewthread&tid=17397
ron8899 said:
oh.... i can't get my stock recovery work... it always shows half of the reocvery screen only.... and the recovery screen keeps glitch. what should i do?
this is where i download the stock recovery
http://community.oppo.com/en/forum.php?mod=viewthread&tid=17397
Click to expand...
Click to collapse
Now we know where the problem is. I re-read your post. New LCD screen. Flash this stock recovery. Once you see it can work, then proceed with the erase cache, oem unlock and twrp 3.0.0.0.
The links here: https://drive.google.com/file/d/0B_5WCvt_2elTU0pKR0V1Mm1jWk0/view?usp=sharing
https://drive.google.com/open?id=0B_5WCvt_2elTbmZ5MERKTzVPQTQ
---------- Post added at 06:36 AM ---------- Previous post was at 06:26 AM ----------
Oh, and by the way, CM 13 not compatible with our LCD screen. Omni supports new screen. Read before flashing rom. If not you'll have more problems.
There's a snapshot CM 13 for new LCD in oppo forum. The links are dead but if you ask someone there, they might upload. I've erased mine. Again, there's some requirements there, so read up.
---------- Post added at 06:46 AM ---------- Previous post was at 06:36 AM ----------
community.oppo.com/en/forum.php?mod=viewthread&tid=46578&extra=
Crap, link incomplete. Nevertheless, go to find 7 third party development section. It's all there.
LG G3 D852
Hey everyone, here's the summary of my whole situation: I've been trying to toy around with some roms for an old phone I had sitting around. Long story short, good phone busted so now back to this one.
Anyways, while trying to install literally every rom (except the one installed already, which I keep flashing to be able to text and all), no matter what ROM it was, it gave me an error saying, "Error executing updater binary in zip". I did some searching and read that it was because TWRP was outdated. Havent used this phone since 2016, so everything on it is outdated, made sense to me.
THIS IS WHERE MY REAL TROUBLE BEGINS!
So, while trying to update TWRP, I tried using different methods such as the Official TWRP App, as well as Flafishy, but all failed.
>>Booted into TWRP recovery, tried to update that way using the image file, followed instructions on the TWRP site, and it said it succeeded! But, when I went to power off and back on into recovery to make sure it went well, it started up in Fastboot Mode instead, and the only way to get that screen off was to take battery out. So now, every time I boot to recovery, it enters Fastboot Mode. However it CAN start up normally without issue.
>>>>The next issue I'm having is with updating TWRP through ABD.
After noticing it was only going to let me use Fastboot, I started the phone, made sure root access was given to Apps & ADB as well as made sure that Android Debugging was enabled.
Then, booted back to Fastboot screen and tried to flash the recovery file using the commands in cmd.
Made sure cmd was opened in the correct directory with the TWRP file, and after typing the flash command, command prompt sits at "Waiting for device" and the device doesnt respond, sits at the firmware screen completely frozen.
Here is what I typed for cmd;
C:\Users\Daqo\Desktop>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.199s]
finished. total time: 0.202s
C:\Users\Daqo\Desktop>fastboot flash twrp-3.0.0-0-d852
< waiting for device >
^^^Gets stuck here^^^
****Please note that after typing the bootloader command, the phone reboots normally and I have to manually press "Reboot to Bootloader" from the popup reboot screen (holding power button) in order to get to the firmware screen. I have tried rebooting to bootloader before and after typing the command to flash the file****
Any help is greatly appreciated