Related
Q&A for [RECOVERY][nozomi] TWRP 2.8.5.0 touch recovery [2015-02-12]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][nozomi] TWRP 2.8.5.0 touch recovery [2015-02-12]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
locked bootloader
m1st3r1 said:
for cwm, there is cwm (and twrp also) for locked bootloader, but it cant flash any kernel (due to locked bootloader). in summary you stuck with stock kernel (that can only be flashed with flashtool or similar tools (if any ) with locked bootloader.
Click to expand...
Click to collapse
Sorry, I'm a bit beginner...
Does this mean that
1. if I use the procedure on page http://teamw.in/project/twrp2/144 in section Download - Stock Kernel:
2. then I can install any ROMs? For example this one? http://forum.xda-developers.com/xperia-s/s-development/rom-naosprom-xperia-s-t2958516
?
Mickey8881 said:
Sorry, I'm a bit beginner...
Does this mean that
1. if I use the procedure on page http://teamw.in/project/twrp2/144 in section Download - Stock Kernel:
2. then I can install any ROMs? For example this one? http://forum.xda-developers.com/xperia-s/s-development/rom-naosprom-xperia-s-t2958516
?
Click to expand...
Click to collapse
Flashing TWRP would require unlocked bootloader. First unlock Your bootloader, then follow the procedure from here.
From Your other post, it turns out You cannot unlock bootloader, so You can flash only sock based ROM's which work on Stock kernel.
Why is there no version 2.8.6.0 for Xperia S?
Hello guys,
I'm just download and install TWRP manager from google play and i'm trying to install the recovery. I'm choosing device name as LT26i but no recovery file is detected.
If i choose device name as "nozomi" i can find everything but my original device name is LT26i.
What to do? Are you suggest to try with nozomi and install the recovery?
Captainlag said:
Hello guys,
I'm just download and install TWRP manager from google play and i'm trying to install the recovery. I'm choosing device name as LT26i but no recovery file is detected.
If i choose device name as "nozomi" i can find everything but my original device name is LT26i.
What to do? Are you suggest to try with nozomi and install the recovery?
Click to expand...
Click to collapse
Nozomi is the code name for LT26i/LT26ii, so You can use it with no problems.
Unable to recovery
I can't flash any recovery file !!!
While I'm trying to install it returns this:
Something is wrong
------------------------
Flashing recovery was
unsuccessful.Either you already
have this recovery installed or
another error has occured.Would
you like to attempt rebooting to
recovery now?
NO YES
Captainlag said:
I can't flash any recovery file !!!
While I'm trying to install it returns this:
Something is wrong
------------------------
Flashing recovery was
unsuccessful.Either you already
have this recovery installed or
another error has occured.Would
you like to attempt rebooting to
recovery now?
NO YES
Click to expand...
Click to collapse
Which method are You following? Try the method from here.
Thank you for your help Mirhawk, but it doesn't work
Captainlag said:
Thank you for your help Mirhawk, but it doesn't work
Click to expand...
Click to collapse
What error are You getting?
Mirhawk said:
What error are You getting?
Click to expand...
Click to collapse
There is no error but I'm trying to reboot in recovery mode and it's immpossible
Captainlag said:
There is no error but I'm trying to reboot in recovery mode and it's immpossible
Click to expand...
Click to collapse
Hope You are pressing volume up button 2-3 times when Sony appears while booting the phone. Also, what ROM are You on?
Mirhawk said:
Hope You are pressing volume up button 2-3 times when Sony appears while booting the phone. Also, what ROM are You on?
Click to expand...
Click to collapse
Of course I'm pressing volume up button 2-3 times ....
My phone is on 6.2.B.1.96 stock with unlocked bootloader
Captainlag said:
Of course I'm pressing volume up button 2-3 times ....
My phone is on 6.2.B.1.96 stock with unlocked bootloader
Click to expand...
Click to collapse
I just wanted to clarify the first point since I have come across some people who didn't follow correct procedure. Glad You are doing it properly.
Ah yes, that is the problem. This method doesn't work on stock firmwares. Use the method from here to get recovery.
Mirhawk said:
I just wanted to clarify the first point since I have come across some people who didn't follow correct procedure. Glad You are doing it properly.
Ah yes, that is the problem. This method doesn't work on stock firmwares. Use the method from here to get recovery.
Click to expand...
Click to collapse
I suppose that i have to follow "method 2", right?
And what to do with the .zip file?
Captainlag said:
I suppose that i have to follow "method 2", right?
And what to do with the .zip file?
Click to expand...
Click to collapse
Method 1. You need recovery for method 2. If You have unlocked bootloader, You can simply flash the DoomKernel too. You can find it here. Use the blue "Download Now" button, and the file has .elf extension. You can flash it via flashtool, it consists of CWM and TWRP and works with stock ROM.
@Mirhawk: Many many thanks !!! :victory:
Finally , I have recovery with Doomkernel.
Thanks a lot and keep moding
I think I messed up my S
Hi
Trying to root my S and install nAOSProm I followed the instructions in the main thread. I successfully unlocked the bootloader and got the device rooted (SuperSU installed and updated in play store), but when attempting to use the TWRP manager to install TWRP I just got an error message that it wasn't successful. I then did this as I read earlier in this thread: fastboot flash boot 2.8.4.1.img. When I started the phone, it immediately boots into the TWRP but I can't get anywhere from there. Impossible to continue to the OS. When I connect it to the computer I just get an exclamation point in the device manager and I can't seem to find the correct drivers (I've installed the FlashTool Xperia Driver Pack). The phone worked perfectly in windows in both normal mode and fastboot previously. Since the phone doesn't have an external memory card, and since I can't transfer any files to it from Windows, I'm stuck in TWRP.
Is it bricked or can I get out of here?
nielsen81 said:
Hi
Trying to root my S and install nAOSProm I followed the instructions in the main thread. I successfully unlocked the bootloader and got the device rooted (SuperSU installed and updated in play store), but when attempting to use the TWRP manager to install TWRP I just got an error message that it wasn't successful. I then did this as I read earlier in this thread: fastboot flash boot 2.8.4.1.img. When I started the phone, it immediately boots into the TWRP but I can't get anywhere from there. Impossible to continue to the OS. When I connect it to the computer I just get an exclamation point in the device manager and I can't seem to find the correct drivers (I've installed the FlashTool Xperia Driver Pack). The phone worked perfectly in windows in both normal mode and fastboot previously. Since the phone doesn't have an external memory card, and since I can't transfer any files to it from Windows, I'm stuck in TWRP.
Is it bricked or can I get out of here?
Click to expand...
Click to collapse
Flash stock firmware ftf using flash mode in flashtool and then follow the instructions from here.
Or else:
Boot Your phone into recovery. Connect it to PC. Right click on the device in Device Manager, select update drivers, "browse my computer", then "let me pick from list" then select the driver similar to "Sony a0109 ADB drivers" (number may vary). Then You will be able connect to phone via adb. Then use following command to push the ROM and gapps to the phone internal memory:
Code:
adb push ROM.zip /sdcard/
adb push gapps.zip /sdcard/
This will copy the the ROM and gapps to phone which You can flash via recovery easily then.
worked perfectly! thanks for your time and help, much appreciated!
I just bought this device a week and I haven't even rooted I wanted to install Cyanogenmode and follow through the instructions and flashed TWRP through fastboot commands from Windows7 using Minimal ADB and Fastboot [8-28-15].
I got the TWRP recovery but I am not sure what have I done wrong, when I am in the TWRP recovery, it does not show any partitions so I am unable to install any ROM on it.
I have also tried to use this thread: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562 when I flash the given recovery from fastboot commands from this thread, the recovery get stuck with bootloop. So then I restored it back to the original TWRP 2.8.7.0.
So at this point now I can only access bootloader and the recovery which does not show partitions.
At this point Is it possible for me to go back to the stock ROM somehow? Please advice. Otherwise I might be able to return it because I have only bought it few days ago.
SOLVED: To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/androi...s/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/dev...o_20150630.img
This allowed TWRP to work.
Thanks to Batfink33 and lynnux
You can follow this guide to flash the newest factory image: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/. You should just download the latest factory image from: https://developers.google.com/android/nexus/images?hl=en the one in the guide is outdated.
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
lynnux said:
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
Click to expand...
Click to collapse
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Batfink33 said:
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Click to expand...
Click to collapse
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
lynnux said:
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
Click to expand...
Click to collapse
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Batfink33 said:
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Click to expand...
Click to collapse
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
a4abbas said:
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
Click to expand...
Click to collapse
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Batfink33 said:
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Click to expand...
Click to collapse
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
a4abbas said:
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
Click to expand...
Click to collapse
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
theminikiller said:
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
Click to expand...
Click to collapse
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
a4abbas said:
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
Click to expand...
Click to collapse
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
theminikiller said:
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
Click to expand...
Click to collapse
You must be right, it make sense.
Hi. Im stucked at fastboot... I have no OS and no TWRP.... on oneplus 2 it happen to me and I used a tool called FIRST AID, but for op3 it does not exist. I tried flash twrp by fastboot, it says success but when I boot to fastboot, I get a black screen.... Please help me
Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
please help me!
infamouzwt said:
Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
thats not true.....
Which TWRP are you flashing and what rom were you on before the speed bump
NZnewbie said:
Which TWRP are you flashing and what rom were you on before the speed bump
Click to expand...
Click to collapse
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....
tuga49 said:
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....
Click to expand...
Click to collapse
Try the modified 3.0.2-19 twrp. Search XDA for it. It's all over.
Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.
Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...
Nilshalok said:
Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...
Click to expand...
Click to collapse
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!
abuddlah said:
Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.
Click to expand...
Click to collapse
Hi. I don't find any twrp with version 3.0.2.19... please help me.
Unbrick tool
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Hi! thank you all! I solved the problem flashing twrp with version 3.0.2.19! thank you all!
tuga49 said:
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!
Click to expand...
Click to collapse
are you Trying 3.5.2???
Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP
Mansquatch312 said:
Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP
Click to expand...
Click to collapse
Here is the issue. 3.5.2 has a different firmware than previous OOS versions. You will need a specific 3.5.2 modified TWRP. The link is here:
http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
You can see that this is discussed on the oneplus forums here: https://forums.oneplus.net/threads/...ity-update-with-working-twrp-recovery.465353/
I ran into this same problem myself, and realized that this was the issue. You should be very careful because it could cause you some grief. Whatever you do don't lock your bootloader if you end up with a nonfunctional and non functional recovery.
I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..
Saqrez said:
I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..
Click to expand...
Click to collapse
I suggest you to refer to the post of @gmarondel :
gmarondel said:
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
Follow this guide and everything will be ok.
I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!
Vexo_ said:
I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!
Click to expand...
Click to collapse
I really appreciate your help but i think i fixed it. Today suddenly my phone went into recovery without doing anything except for 1000 methods. I am so happy that people like you are willing to help people.
I bought my 5X in October and came here to root my phone and be able to use the ElementalX and the Advanced Interactive Governor tweaks.
Everything was working fine and my phone really performed outstandingly.
Then I saw the OTA 7.1.1. popping up. I didn't allow it until I installed it by mistake yesterday...
Now I'm stuck with google asking me to lock the bootloader.
I can access the bootloader. I get a lot of options.
I can access the recovery mode and it gets me to RecoveryProject 3.0.2-2 by Teamwin.
I already have the Android platform tools on my desktop and it's working.
From there I have 2 questions :
1. Is there a way to not wipe all the contents on my phone? I didn't get the chance to backup all the data on it.
2. After that how can I get my phone working with the latest android version as I was before, unrooted and running with EX Kernel Manager.
Thanks for your help.
1. try installing the supersu zip from the recovery
2.EX Kernel Manager cannot work without root. so you need to root your device
Thanks a lot for you answer!
1. So by installing SuperSu zip from the recovery I would be able to backup my phone data?
2. I meant rooted sorry. So my phone is already rooted and I'm fine with staying that way.
Enzoli said:
Thanks a lot for you answer!
1. So by installing SuperSu zip from the recovery I would be able to backup my phone data?
Click to expand...
Click to collapse
yes
you can actually backup you device from TWRP recovery.
flash the supersu zip and you will boot normally without any data lose
Insane! thanks a lot.
One more noob question. I got the latest superSu zip.
How can I flash it from the recovery?
How can i transfer it to the phone?
Ok I almost got it.
My only question left is how can I transfer the SuperSu zip file onto my phone since I don't have access to anything else than Bootloader and TWRP
Enzoli said:
Ok I almost got it.
My only question left is how can I transfer the SuperSu zip file onto my phone since I don't have access to anything else than Bootloader and TWRP
Click to expand...
Click to collapse
adb sideload from twrp
OK guys thanks. When I use adb sideload in twrp advanced menu it gets stuck on "Starting ADB sideload feature... "
And when I type ADB devices on the command prompt it does not show my device but if I'm just in the menu before sideload it does find my device and says the serial number + recovery.
What am I doing wrong?
Thanks for helping.
You should be able to transfer files while being in recovery using MTP mode.
How do I use MTP mode? Sorry what does that mean. Can't find an explanation on the internet.
I've looked at all the options in the menu but can't find such a option.
I really feel stupid.
Ok guys I transfered SuperSu to my phone using adb push.
I flashed my phone with SuperSu but when i reboot my phone, it still tells me I need to lock my bootloader.
What shall I do now?
I keep going to the Googl screen with the little locker and then I reach the No Command screen.
The phone won't boot into Android no more. Guys please help I'm desperate. Is my phone dead?
Ok so I guess my phone is now in bootloop.
Still anyone willing to help?
OK I tried many things in despair and now I cannot enter the recovery mode anymore. It just gets stuck on the teamwin screen.
Guess it's time to buy a new phone.
So miracle I could enter the recovery.
Now I don't know where to go. I would like to be able to enter normal android but my phone will keep on showing android screen with little lock and the end on the No command screen. Endlessly.
Ok. THread can be closed. I managed to flash a factory image. Lost all my data but I got a working phone so I guess it's not to bad.
...
Enzoli said:
Ok. THread can be closed. I managed to flash a factory image. Lost all my data but I got a working phone so I guess it's not to bad.
Click to expand...
Click to collapse
If you ever need help on updating your software to the latest Android version, follow my guide as a reference:
https://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk
so i tried rooting my g4 h815. i followed multiple guides and got bootloader unlocked and twrp installed it however bootlooped after flashing supersu. i restarted the phone and went into recovery mode and hit yes to enter twrp it however did not go into twrp and now no longer boots... anybody got an idea how to fix this?
Anna
just_anna said:
so i tried rooting my g4 h815. i followed multiple guides and got bootloader unlocked and twrp installed it however bootlooped after flashing supersu. i restarted the phone and went into recovery mode and hit yes to enter twrp it however did not go into twrp and now no longer boots... anybody got an idea how to fix this?
Anna
Click to expand...
Click to collapse
Without knowing exactly what you have done, it is pretty well impossible to give any helpful suggestions. You will have to be more specific.
- what model of LG G4 do you have? H815, H811, H810, H812 ..... ?
- what guides did you follow?
- exactly how did you unlock your bootloader?
- what TWRP version did you install? Did you follow the installation process in the LG G4 TWRP thread?
- did you flash a custom rom, if so what one? What SUperSU version did you install?
- etc., etc.
sdembiske said:
Without knowing exactly what you have done, it is pretty well impossible to give any helpful suggestions. You will have to be more specific.
- what model of LG G4 do you have? H815, H811, H810, H812 ..... ?
- what guides did you follow?
- exactly how did you unlock your bootloader?
- what TWRP version did you install? Did you follow the installation process in the LG G4 TWRP thread?
- did you flash a custom rom, if so what one? What SUperSU version did you install?
- etc., etc.
Click to expand...
Click to collapse
i used the following quides and used the official lg method of unlocking the bootloader
https://www.youtube.com/watch?v=skmGRgfx2V8
https://www.**************/install-twrp-recovery-on-lg-g4-international-variant/
https://www.**************/how-to-root-lg-g4-h815-using-supersu/
https://forum.xda-developers.com/g4/general/discussion-unlock-root-situations-please-t3122752
and downloaded twrp and supersu from the following sites
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
https://dl.twrp.me/g4/twrp-2.8.6.0-h815.img.html
just_anna said:
i used the following quides and used the official lg method of unlocking the bootloader
https://www.youtube.com/watch?v=skmGRgfx2V8
https://www.**************/install-twrp-recovery-on-lg-g4-international-variant/
https://www.**************/how-to-root-lg-g4-h815-using-supersu/
https://forum.xda-developers.com/g4/general/discussion-unlock-root-situations-please-t3122752
and downloaded twrp and supersu from the following sites
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
https://dl.twrp.me/g4/twrp-2.8.6.0-h815.img.html
Click to expand...
Click to collapse
OK, so as you were able to unlock your H815 Officially(H815 Europe version?), there shouldn't be a problem there if you did everything correctly.
That leaves TWRP version and SuperSU where the problem is most likely arising from.
Wipe your Cache & Dalvik cache in TWRP if it's functioning
Then, go to the TWRP site I linked in my previous post that is specific for the LG G4 and find and download the latest preview version you require for the firmware you currently have installed (I'm presuming Marshmallow [M]?). Follow the fastboot flashing method as exactly outlined there.
Next, if you really require SuperSu* (no longer currently supported or updated and free version removed from Play Store) you want to use SuperSU v2.82.
* I would however, recommend Magisk for your root program - it is currently supported and updated frequently. Download the latest ZIP and apk versions abd install them.
** You will have to uninstall SuperSU first before installing Magisk. Download and use the program linked in this post to uninstall SuperSU before installing Magisk.
Note: Please learn to use the Thanks button (bottom right of post) when members answer your question or provide useful/helpful information - it's an XDA Courtesy and it only takes a quick click.
sdembiske said:
OK, so as you were able to unlock your H815 Officially(H815 Europe version?), there shouldn't be a problem there if you did everything correctly.
That leaves TWRP version and SuperSU where the problem is most likely arising from.
Wipe your Cache & Dalvik cache in TWRP if it's functioning
Then, go to the TWRP site I linked in my previous post that is specific for the LG G4 and find and download the latest preview version you require for the firmware you currently have installed (I'm presuming Marshmallow [M]?). Follow the fastboot flashing method as exactly outlined there.
Next, if you really require SuperSu* (no longer currently supported or updated and free version removed from Play Store) you want to use SuperSU v2.82.
* I would however, recommend Magisk for your root program - it is currently supported and updated frequently. Download the latest ZIP and apk versions abd install them.
** You will have to uninstall SuperSU first before installing Magisk. Download and use the program linked in this post to uninstall SuperSU before installing Magisk.
Note: Please learn to use the Thanks button (bottom right of post) when members answer your question or provide useful/helpful information - it's an XDA Courtesy and it only takes a quick click.
Click to expand...
Click to collapse
i indeed have the eu version of the h815 unfortunately twrp doesnt start from recovery mode and when not in recovery the phone bootloops (twrp did work before as i used it to flash supersu)
just_anna said:
i indeed have the eu version of the h815 unfortunately twrp doesnt start from recovery mode and when not in recovery the phone bootloops (twrp did work before as i used it to flash supersu)
Click to expand...
Click to collapse
Using adb, try booting into recovery mode directly using this command adb reboot recovery.
Failing that see if you can get into fastboot mode - try this command fastboot reboot recovery If that works, uninstall SuperSU with the zip in the post I referenced above and install the SuperSU version I referenced or Magisk and then try rebooting the system.
Failing that try re-installing TWRP in fastboot mode with this fastboot flash recovery (twrp.image name exactly) and then fastboot reboot recovery if successful. Then uninstall SuperSu etc.
[/IMG]
sdembiske said:
Using adb, try booting into recovery mode directly using this command adb reboot recovery.
Failing that see if you can get into fastboot mode - try this command adb reboot bootloader and then try booting into recovery mode directly using this command fastboot reboot recovery. If that works, uninstall SuperSU with the zip in the post I referenced above and install the SuperSU version I referenced or Magisk and then try rebooting the system.
Failing that try re-installing TWRP in fastboot mode with this fastboot flash recovery (twrp.image name exactly) and then fastboot reboot recovery if successful. The uninstall SuperSu etc.
Click to expand...
Click to collapse
i tried all the commands using dos/command prompt from my fastboot folder it however cant find my device[IMG="dos results"]https://flic.kr/p/2gpcL5k
just_anna said:
i tried all the commands using dos/command prompt from my fastboot folder it however cant find my device
Click to expand...
Click to collapse
Try rebooting your PC with your phone connected and then try in your adb/fastboot folder again to see if your device is recognized.
sdembiske said:
Try rebooting your PC with your phone connected and then try in your adb/fastboot folder again to see if your device is recognized.
Click to expand...
Click to collapse
unfortunately it did not recognize the device and gave me the same results
just_anna said:
unfortunately it did not recognize the device and gave me the same results
Click to expand...
Click to collapse
Try reinstalling your LG G4 USB driver (LGMobileDriver_WHQL_Ver_4.2.0) on your PC and test again.
Failing that, try using FWUL to see if you can connect to your device - refer to the LG G4 TWRP link again and see FAQ # 3 where it's suggested.
If successful, go through the above commands again in FWUL - it has adb/fastboot built-in.
If you're still having no luck, see FAQ # 2 in the LG G4 TWRP thread and see if you can connect with @steadfasterX (the TWRP thread author & recognized developer) to help you - if anybody can, he can. I'm out of suggestions as of now.