Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download & Installation (assuming, you've unlocked the bootloader following Korelev's instructions)
1) Download and open the Official TWRP App from the Play Store
2) Select TWRP flash
3) "Select device" > "LG Spirit LTE (H440N) -- c70n" > select the latest image available
4) When the image is downloaded, return to the app and "select a file to flash". Select the downloaded image and tap "Flash to recovery"
5) Reboot to recovery
You're in TWRP!
NOTE: To boot into recovery with hardware buttons use this method. Power off the device > press and hold Power + Volume Down buttons simultaneously > keep pressing them until the LG logo shows up > when the LG logo shows up, let go of the buttons for 1 second and then press them again. A factory reset menu will show up. Select "Yes" two times to "wipe" your device. Don't worry, this will actually NOT wipe your device. It will boot into recovery normally. This is because LG phones are a bit different and they instruct the recovery (TWRP in this case) to automatically perform a factory reset of the phone by triggering the /misc wipe flag. I mapped /misc partition to a different partition (/pad) so TWRP doesn't perform a factory reset.
BUGS:
battery indicator (sometimes)
Some features were untested, but the most important ones seem to work just fine. As I'm pretty unexperienced with this, help from other devs would be greatly appreciated. If you come up with an improved version of my build, let me know and I'll edit the OP ASAP.
XDA: DevDB Information
[RECOVERY]Official TWRP for LG Spirit H440N, Device Specific App for the LG Spirit H440N
Contributors
Fobos531
Device tree: https://github.com/TeamWin/android_device_lge_c70n
Version Information
Status: Stable
Thanks to:
@midzan21
@Korelev
@pvineeth97
@cerg2010cerg2010
If I've left anyone out, please let me know. I'm new to this too
Created 2017-02-27
Last Updated 2017-03-24
CHANGELOG
#1 2017-02-27 - first build
#2 2017-02-27 - screen timeout bug fixed
#3 2017-03-02 - fixed booting into recovery with hardware buttons, you can now do that normally
#4 2017-03-11 - TWRP 3.1.0 released, check the changelog here
It's already starting!!! Actual development for our old but still good Spirit! :,-)
Is this the desire twrp? I think you should post it at kernerls recoveries and development subforum instead of the guides one. Good work!
Korelev said:
Is this the desire twrp? I think you should post it at kernerls recoveries and development subforum instead of the guides one. Good work!
Click to expand...
Click to collapse
the base is from Moto G 3rd gen.
Yeah, my bad. I'll leave it here for now.
fixed screen timeout bug, redownload the recovery from OP
I'll give it a try tonight
Make sure you flashed the c70n_recovery3.img(I forgot to update the link till today) recovery image since that's latest one with all fixes so far.
New build up, download: https://drive.google.com/open?id=0B4VJbV8vBFHadllaM2EyY3hVMk0
Check post #2 for changelog
Another build up, download from the OP.
The difference between this build and the one in post #9 is that in post #9 I used a dirty hack that told TWRP to ignore the /misc wipe flag when booting into TWRP with hardware buttons on LG phones. In the newest build I removed that hack and instead the mapped the /misc partition to a different partition (/pad) so the factory reset doesn't occur. The reason this was needed is because, with the previous build, if we had LineageOS and tried to do a factory reset in the system, it wouldn't work because of the hack I used. Now the factory reset will work when performing a factory reset on (future) custom ROMs.
@Fobos531: Hi, just wanted to tell you that the latest TWRP didn't seem do what the OP says. If I understood correctly, the intended behaviour on stock roms should have been to ignore the factory reset commands and just boot up TWRP for normal use.
When I selected yes for the second time, to confirm a factory reset, TWRP booted executing some kind of a script (forgot the exact name), and never gave me a chance to stop it. After that it rebooted. It technically performed a factory reset, only using TWRP to do it.
Did I misunderstand something in your explanation? I'm running stock MM, installed using Korelev's zip.
Alanon said:
@Fobos531: Hi, just wanted to tell you that the latest TWRP didn't seem do what the OP says. If I understood correctly, the intended behaviour on stock roms should have been to ignore the factory reset commands and just boot up TWRP for normal use.
When I selected yes for the second time, to confirm a factory reset, TWRP booted executing some kind of a script (forgot the exact name), and never gave me a chance to stop it. After that it rebooted. It technically performed a factory reset, only using TWRP to do it.
Did I misunderstand something in your explanation? I'm running stock MM, installed using Korelev's zip.
Click to expand...
Click to collapse
Can you specify the exact name of the "latest" TWRP you're referring to? I flashed the exact TWRP that is currently in the OP and booting into TWRP with hardware keys works completely fine for me. I encountered this script you're referring to as well, but that was when I was using an older version of the build. The newest image that I built shouldn't do that.
If there are more issues, feel free to send me a PM in your native language. I speak it so we should be fine.
I pretty much flashed them in order of appearance, closely following your posts. If I remember correctly, the first was called recovery.img, then there was c70n_recovery.img, and finally twrp.img, which was the last one I flashed. The only memory I have is of these names, and I have a twrp.img in a folder on my PC. The file attributes, like the time of creation, match.
If I didn't flash the latest twrp, I still must have flashed the build with the previous factory reset hack, which still doesn't explain what happened. The only explanation I can think of is that that somehow Flashify didn't really overwrite the existing twrp?
Anyways, It's not all that big a deal, since I boot to recovery from the OS in 90% of the cases, and ADB is always there as a backup solution. This was really about testing to see if it worked, for if and when this was the only option. I've already reflashed the twrp from the first post, but I'd really hate to have to go through another factory reset in search of confirmation. I just got the apps sorted again. xD
Alanon said:
I pretty much flashed them in order of appearance, closely following your posts. If I remember correctly, the first was called recovery.img, then there was c70n_recovery.img, and finally twrp.img, which was the last one I flashed. The only memory I have is of these names, and I have a twrp.img in a folder on my PC. The file attributes, like the time of creation, match.
If I didn't flash the latest twrp, I still must have flashed the build with the previous factory reset hack, which still doesn't explain what happened. The only explanation I can think of is that that somehow Flashify didn't really overwrite the existing twrp?
Anyways, It's not all that big a deal, since I boot to recovery from the OS in 90% of the cases, and ADB is always there as a backup solution. This was really about testing to see if it worked, for if and when this was the only option.
Click to expand...
Click to collapse
If you've indeed flashed the build with the previous factory reset hack, you may have left out the "cd /cache/recovery, echo '--show_text' etc." steps. I suppose they have to be done every time a build is flashed.
I've already reflashed the twrp from the first post, but I'd really hate to have to go through another factory reset in search of confirmation. I just got the apps sorted again. xD
Click to expand...
Click to collapse
Fine, no problem, the only unfortunate thing that could happen is if you were to flash a custom ROM and it would bootloop, you wouldn't have much chance of properly getting into recovery (since it would execute that wipe script AFAIK) and you wouldn't be able to flash the recovery through fastboot either so it's worth getting the recovery right, at least before flashing custom ROMs.
Remember, you can always make a Nandroid backup of your ROM in TWRP and then test if you can boot into TWRP with hardware buttons, and if factory resets the phone, you can have it set up like before by restoring the backup in TWRP.
how to boot into twrp recovey with key.?
when i go to twrp recovery my phone going to auto reset.
i install marshmellow rom with twrp.
plz help
inoxentrajaa said:
how to boot into twrp recovey with key.?
when i go to twrp recovery my phone going to auto reset.
i install marshmellow rom with twrp.
plz help
Click to expand...
Click to collapse
Make sure you flashed the latest TWRP (link is in the original post) using the procedure described in the original post.
To boot into TWRP recovery with hardware keys:
Power off the device > press and hold Power + Volume Down buttons simultaneously > keep pressing them until the LG logo shows up > when the LG logo shows up, let go of the buttons for 1 second and then press them again. A factory reset menu will show up. Select "Yes" two times to "wipe" your device. Don't worry, this will actually NOT wipe your device. It will boot into recovery normally
Click to expand...
Click to collapse
TWRP 3.1.0 is released, download from the OP, changelog in second post
inoxentrajaa said:
how to boot into twrp recovey with key.?
when i go to twrp recovery my phone going to auto reset.
i install marshmellow rom with twrp.
plz help
Click to expand...
Click to collapse
use adb its better way
adb reboot recovery
fobos531 said:
twrp 3.1.0 is released, download from the op, changelog in second post
Click to expand...
Click to collapse
thanks bro
inoxentrajaa said:
thanks bro
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B4VJbV8vBFHaUmREejFjeUpUZ1k
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have decided to post the wipe scripts here for those KernelHolics & Flashaholics that are flashing kernels and ROMs constantly. I've made small modifications to these scripts FULL credit to the originator of them Credits below.
These are compatible with TWRP, CWM.
Since there have been numerous kernels recently being posted and people wondering what to wipe or what not to wiped here is the Kernel Cleaner.
1. Place the file in the root of your /sdcard
2. Flash Kernel Cleaner
3. Flash/Fastboot Kernel
4. Reboot.
Download: http://d-h.st/ke1
This second script I'm sure everyone is familiar with SUPERWIPE script.
Tired of wiping after every ROM or not knowing what to wipe to flash a ROM and have a clean install? Just flash this script & flash ROM easy right?
1. Place Wipe-Script in root of /sdcard
2. Flash Wipe-Script
3. Flash ROM
4. Reboot.
5. Wipes System, Cache, Data.
Download: http://d-h.st/qIo
Debug
If it doesn't flash please tell me what recovery your using.
ONLY works for the DROID DNA flashing this on another device will brick your phone.
Credit goes to the following people.
Mike1986
AmazingLarry31
Jivy26
I-777
Myself
IF YOU USE/DOWNLOAD THIS SCRIPT PLEASE PRESS THE THANKS BUTTON
Reserved for more Awesome Scripts
Awesome. Thanks. Will test later today when I get home.
Sent from my ViperDNA
cool,works great Thanks!
Very cool...what does the Kernel Cleaner wipe? I will either Flash GUI or fastboot flash the boot.img file, then boot into recovery, wipe cache, wipe dalvik, mount system then flash the corresponding zip files.
Anything else I should be doing/this script does?
when using the system wipe it will wipe your SD card FYI. Just lost my backups luckly I know about the adb sideload trick to get a rom back on my device to get back up and running. May want to adjust the script to not wipe the location on data that is the SD card (not sure of the xact location )
crackeyes said:
when using the system wipe it will wipe your SD card FYI. Just lost my backups luckly I know about the adb sideload trick to get a rom back on my device to get back up and running. May want to adjust the script to not wipe the location on data that is the SD card (not sure of the xact location )
Click to expand...
Click to collapse
Will update the zip today.
Sent from my HTC One S using Tapatalk 2
...Awesome... said:
Will update the zip today.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
It is the data/media folder that holds the SD card
crackeyes said:
It is the data/media folder that holds the SD card
Click to expand...
Click to collapse
Yes its cache, system, data. I will make one with just cache, system.
Sent from my HTC One S using Tapatalk 2
...Awesome... said:
Yes its cache, system, data. I will make one with just cache, system.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
has it been updated
bakemcbride21 said:
Very cool...what does the Kernel Cleaner wipe? I will either Flash GUI or fastboot flash the boot.img file, then boot into recovery, wipe cache, wipe dalvik, mount system then flash the corresponding zip files.
Anything else I should be doing/this script does?
Click to expand...
Click to collapse
i second this.. what does the kernel cleaner wipe actually do?
No most of those programs already wipe. This is only if you fastboot/flash the kernel just like the OP states.
Sent from my HTC One S using Tapatalk 2
So i used the superwipe script in TWRP recovery and immediately after I went into mounts and attempted to mount system. I was going to install CyanogenMOD newest nightly from a clean flash.
Although when I chose mount system my phone rebooted, since there is no OS it obviously stays at the HTC white splash screen. So i hold the power and vol down button get back into bootloader so i can go back into recovery but now my entire SDcard is wiped, gone, no where to be found. At first I am like alright whatever screw it sh*t happens so i move onto to restore a backup of a ROM i have via USB-OTG and now nothing works, I cant boot into OS or recovery, i tried fastboot flash recovery again, and it succeeds both with TWRP and CWM but it never boots into recovery.
I see like the splash screens of the recovery (the teamwin icon and CWM icon but never fully boots) and then it goes into a constant bootloop that never comes out of it.
Help please!
El Ha$on said:
So i used the superwipe script in TWRP recovery and immediately after I went into mounts and attempted to mount system. I was going to install CyanogenMOD newest nightly from a clean flash.
Although when I chose mount system my phone rebooted, since there is no OS it obviously stays at the HTC white splash screen. So i hold the power and vol down button get back into bootloader so i can go back into recovery but now my entire SDcard is wiped, gone, no where to be found. At first I am like alright whatever screw it sh*t happens so i move onto to restore a backup of a ROM i have via USB-OTG and now nothing works, I cant boot into OS or recovery, i tried fastboot flash recovery again, and it succeeds both with TWRP and CWM but it never boots into recovery.
I see like the splash screens of the recovery (the teamwin icon and CWM icon but never fully boots) and then it goes into a constant bootloop that never comes out of it.
Help please!
Click to expand...
Click to collapse
Follow the unbricking thread. Specifically my posts to get you back up and running.
Skip right to the part where you flash "ROM.zip", check md5, in fastboot. This will restore your to stock and you can start over.
If you have the eng hboot or a custom splash screen you may have to flash the original parts if the flash doesn't take.
Pay any attention to errors while flashing. I don't follow the DNA much so hit me up in pm if you need help.
thanks a lot
Doesn't work on TWRP 2.5 !
Hi there ,
I have Htc DNA . installed custome recovery TWRP ... flashing Kernel cleaner works! BUT flashing superwipe.zip Doesn't work ! (gives [email protected]).
Can you please help ?!
One another question : how to format phone with twrp ? i have one option "wipe" ... as written there it will wipe everything needed by sliding ?! I do that but seems something still not wiped !? cause phone has crashes ... I would prefer CWM! (better and simple).
BY the way in TWRP i have in wiping partions ... something like "OTG USB " ?? WTF ? what's this that i can't wipe ?!
Thanks for help .
Pretty much all in the title, my Galaxy S2 SGH-i777 was charging while I was doing some school work. I look down and the boot screen saying "Samsung Galaxy SII" so I look back up, I'm used to my phone restarting here and there (probably not a good thing..) so I just ignored it and looked back down because I was checking to see if my ride was ready or not and it was just showing "Samsung Galaxy SII" and it'd go to a black screen, and restart the process all over again.
I looked for any other people having the same problem, but I think I'm the only one on AT&T that has. One guy with T-Mobile had the same issue and he said that constantly pushing the button would work, I tried that and it still didn't work, so I don't know what to do.
Anyone have any ideas?
Search for back to stock topic.
Is it rooted? If so, download another room and flash it.
Sent from my SGH-I777 using xda app-developers app
RatusNatus said:
Search for back to stock topic.
Is it rooted? If so, download another room and flash it.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
So you're saying my OS is basically dead? Haha, would it be possible to root it now? I've had stock for ever and I've looked into getting it done, but been to worried I'd completely brick my phone. What would be the best ROM?
There are a lot of them. If that's the road you choose to take, try a few and see which ones meet your needs.
The problem could be either firmware related (more likely) or hardware related (less likely.) First, boot into recovery mode and perform a wipe data/factory reset. With the phone off, hold all three of vol- vol+ and power buttons continuously until it boots into recovery.
If that does not clear the problem, then as suggested try flashing one of the stock packages using Odin. If you want root at the same time, flash one of the stock plus root packages. There is little risk of completely bricking your phone as long as you read first, understand the steps, and use the correct firmwares.
See the links in my sig, and the stickies in these forums to guide you.
creepyncrawly said:
The problem could be either firmware related (more likely) or hardware related (less likely.) First, boot into recovery mode and perform a wipe data/factory reset. With the phone off, hold all three of vol- vol+ and power buttons continuously until it boots into recovery.
If that does not clear the problem, then as suggested try flashing one of the stock packages using Odin. If you want root at the same time, flash one of the stock plus root packages. There is little risk of completely bricking your phone as long as you read first, understand the steps, and use the correct firmwares.
See the links in my sig, and the stickies in these forums to guide you.
Click to expand...
Click to collapse
Tried recovery mode today and now when I boot I still get boot loop, then if I try going back to recovery it says "Deleting System Meta Data". I'm still on 2.3 update by the way, which pack do I need, the UCKH7 or UCKH6? I'm going to do the stock +root packages, I just need to run to get a data cable tomorrow.
Do I need to do anything extra since I have the "Deleting System Meta Data" or can I still flash with stock FW +root Kernel?
Thanks guys for your help by the way!
zZSleepyZz said:
Tried recovery mode today and now when I boot I still get boot loop, then if I try going back to recovery it says "Deleting System Meta Data". I'm still on 2.3 update by the way, which pack do I need, the UCKH7 or UCKH6? I'm going to do the stock +root packages, I just need to run to get a data cable tomorrow.
Do I need to do anything extra since I have the "Deleting System Meta Data" or can I still flash with stock FW +root Kernel?
Thanks guys for your help by the way!
Click to expand...
Click to collapse
Deleting cryption meta data is a little difficult to get past, but it can be done. See this post for a way to fix it, maybe.
Were you able to do the wipe data/factory reset as suggested? Or what do you mean by "tried recovery mode today?"
creepyncrawly said:
Deleting cryption meta data is a little difficult to get past, but it can be done. See this post for a way to fix it, maybe.
Were you able to do the wipe data/factory reset as suggested? Or what do you mean by "tried recovery mode today?"
Click to expand...
Click to collapse
Like, I held down Volume Up/Down and the power button and got the menu where it asked me if I wanted to "wipe data/factory reset" or "clear cache partition" and another option, I clicked "wipe data/factory reset" and now I get "Deleting Cryption Meta Data".
I just made this harder didn't I? Aha..
The only menu I can actually do anything with now looks like this..
(This isn't my phone, just an example of the screen.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this where I'm going to have to go to when I begin to load the Binaries? I got to this screen by holding Volume Down + Power for about 3 seconds
That screen is download mode. From there you can install firmware using Odin or Heimdall. I suggest following the instructions in the link I posted.
i am having the same issue with this device - please help
hey guys,
This is rooted sgh-i777. and is going into bootloop. First I tired clean cache then dalvik cache bit no success and then i tried factory reset as well and thats when I see the problem that it wouldn't let me. Its says unable to mount data <invalid argumant>. I read some of xda threads that If I install stock rom again via Odin it would come back to my original state and i did that. After successful flash of stock rom with Odin I was hopeful that it would solve my problem but it wouldn't and it kept getting stuck on "Samsung Galaxy s2" black boot screen and is in bootloop. I thought my kernel might have meesed up and so i installed siyah kernel, it would let me come out of black boot screen but now next it would hung on Siyah logo startup screen. I can still go to CWM recovery mode and can install any rom and clean the cache or dalvik cache but the problem is with /data, it just stuck on formatting /data infinitely.
I would really appreciate any help which could lead me to fix my device.
---------- Post added at 04:57 AM ---------- Previous post was at 04:45 AM ----------
hey guys,
This is rooted sgh-i777. and is going into bootloop. First I tired clean cache then dalvik cache bit no success and then i tried factory reset as well and thats when I see the problem that it wouldn't let me. Its says unable to mount data <invalid argumant>. I read some of xda threads that If I install stock rom again via Odin it would come back to my original state and i did that. After successful flash of stock rom with Odin I was hopeful that it would solve my problem but it wouldn't and it kept getting stuck on "Samsung Galaxy s2" black boot screen and is in bootloop. I thought my kernel might have meesed up and so i installed siyah kernel, it would let me come out of black boot screen but now next it would hung on Siyah logo startup screen. I can still go to CWM recovery mode and can install any rom and clean the cache or dalvik cache but the problem is with /data, it just stuck on formatting /data infinitely.
I would really appreciate any help which could lead me to fix my device.
pushpendra.jain said:
hey guys,
This is rooted sgh-i777. and is going into bootloop. First I tired clean cache then dalvik cache bit no success and then i tried factory reset as well and thats when I see the problem that it wouldn't let me. Its says unable to mount data <invalid argumant>. I read some of xda threads that If I install stock rom again via Odin it would come back to my original state and i did that. After successful flash of stock rom with Odin I was hopeful that it would solve my problem but it wouldn't and it kept getting stuck on "Samsung Galaxy s2" black boot screen and is in bootloop. I thought my kernel might have meesed up and so i installed siyah kernel, it would let me come out of black boot screen but now next it would hung on Siyah logo startup screen. I can still go to CWM recovery mode and can install any rom and clean the cache or dalvik cache but the problem is with /data, it just stuck on formatting /data infinitely.
I would really appreciate any help which could lead me to fix my device.
Click to expand...
Click to collapse
What stock did you flash? 2.3.4, 2.3.6, 4.0.3, 4.0.4, or 4.1.2?
Since you can still boot into CWM recovery, what happens when you perform a wipe data/factory reset again? And what exactly do you mean "stuck on formatting /data infinitely?"
RatusNatus said:
Search for back to stock topic.
Is it rooted? If so, download another room and flash it.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem my sgh i777 is stuck in start up mode, then tried doing a hard reset, it gets stuck in download mode, with the android green thing, then says download do not restart, i left it on the whole day, nothing. what do i do? ive taking it to att tech support to get it flashed they couldnt, taken it to samsung experience they couldnt do anything. pleasee help.
While in download mode reflash stock firmware using Odin in administrator mode on your PC. Then use Framaroot.apk too root device and flash a kernel with cwm recovery using rom manager. Then install the rom of choice using CWM in recovery mode.
Sent from my SGH-I777 using xda app-developers app
I have a LGH850. I unlocked the bootloader and flashed TWRP, just to change a couple of things that niggled me - the emojis, for instance.
Recently, I was offered an OTA update. Obviously, I couldn't use that with TWRP so I tried flashing a stock recovery back. That work, in so far as the OTA update ran, but it stopped halfway saying that as my phone had been modified it couldn't continue.
I am now left with a phone that would only boot into recovery (whether that be stock or TWRP).
I can get into "download mode", fastboot or recovery fine. I have flashed a couple of different KDZ files using LGUP. I have used both "refurbish" and "update" modes. They have all said they were successful, but on reboot all I get is stuck at a bootloop on the LG screen.
Am I missing something? Is my partition table totally messed up or something? Shouldn't a KDZ fix all that?
Any ideas?
bigstoo said:
I have a LGH850. I unlocked the bootloader and flashed TWRP, just to change a couple of things that niggled me - the emojis, for instance.
Recently, I was offered an OTA update. Obviously, I couldn't use that with TWRP so I tried flashing a stock recovery back. That work, in so far as the OTA update ran, but it stopped halfway saying that as my phone had been modified it couldn't continue.
I am now left with a phone that would only boot into recovery (whether that be stock or TWRP).
I can get into "download mode", fastboot or recovery fine. I have flashed a couple of different KDZ files using LGUP. I have used both "refurbish" and "update" modes. They have all said they were successful, but on reboot all I get is stuck at a bootloop on the LG screen.
Am I missing something? Is my partition table totally messed up or something? Shouldn't a KDZ fix all that?
Any ideas?
Click to expand...
Click to collapse
If you can boot in twrp then you tried to flash the system zip posted by autoprime?
Also, What's the Point of the title? It seems that G5 is detective which is not in this case xD
Killua96 said:
If you can boot in twrp then you tried to flash the system zip posted by autoprime?
Click to expand...
Click to collapse
Yes. I've tried flashing with TWRP, flashing with fastboot, flashing with LGUP. All are successful, but the phone still will not boot.
Killua96 said:
Also, What's the Point of the title? It seems that G5 is detective which is not in this case xD
Click to expand...
Click to collapse
It was meant as "Another Bootloop Thread - My Fault", rather than "Another Broken G5 - LG's Fault".
Sorry for any misunderstanding.
bigstoo said:
Yes. I've tried flashing with TWRP, flashing with fastboot, flashing with LGUP. All are successful, but the phone still will not boot.
Click to expand...
Click to collapse
What haven you tried to flash through twrp exactly?
The full zip provided by autoprime? Did you try also to do a factory reset (all wipes) and also a format data?
Change the title you can make a mess with people thinking that G5 has a bootloop problem like G4.
That's what I thought and entered to see if it's true.
Install twrp, wipe everything then install stock recovery and flash full kdz from download mode.
Killua96 said:
What haven you tried to flash through twrp exactly?
The full zip provided by autoprime? Did you try also to do a factory reset (all wipes) and also a format data?
Click to expand...
Click to collapse
I flashed the
LG-H85010E-Flashable.COMPLETE.zip in this post. I also tried flashing the LG-H85010E-Flashable.Boot.zip and LG-H85010E-Flashable.Bootloader.zip separately. I did a wipe and a format of everything in TWRP (which I suspect may be the problem - could it be that internal storage is somehow messed up?). Whilst I still had TWRP on there, it would boot directly into TWRP with no buttons pressed in (instead of booting properly into the ROM). Now I have the stock recovery, it just bootloops.
I have flashed H85010c_00_OPEN_EU_OP_0415.kdz and H85010h_00_H3G_COM_OP_0816.kdz using LGUP. Both say they are successful, but both just sit on the initial LG screen during boot.
Unfortunately I have now relocked the bootloader (in preparation for returning it to LG). I thought I would be able to unlock it again if I wanted, but it says I have to enable OEM Unlock in the ROM. Which, of course, I can't boot into. So fastboot has now become useless for the moment.
bigstoo said:
I flashed the
LG-H85010E-Flashable.COMPLETE.zip in this post. I also tried flashing the LG-H85010E-Flashable.Boot.zip and LG-H85010E-Flashable.Bootloader.zip separately. I did a wipe and a format of everything in TWRP (which I suspect may be the problem - could it be that internal storage is somehow messed up?). Whilst I still had TWRP on there, it would boot directly into TWRP with no buttons pressed in (instead of booting properly into the ROM). Now I have the stock recovery, it just bootloops.
I have flashed H85010c_00_OPEN_EU_OP_0415.kdz and H85010h_00_H3G_COM_OP_0816.kdz using LGUP. Both say they are successful, but both just sit on the initial LG screen during boot.
Unfortunately I have now relocked the bootloader (in preparation for returning it to LG). I thought I would be able to unlock it again if I wanted, but it says I have to enable OEM Unlock in the ROM. Which, of course, I can't boot into. So fastboot has now become useless for the moment.
Click to expand...
Click to collapse
Then return it to LG, but i dubt it will be repaired in warranty as you have unlocked the bootloaderm, even if you locked it trough the command LG will always have your device identified as "unlocked".
In any case good luck and keep us informed!
it's odd that LGUP refurbish with the KDZ didn't work. after the KDZ flash does it boot into TWRP or just show the green android? if it shows the green android that means /data should be reset now and you should be able to boot. first boot after a data wipe can take a long time... you waited a bit longer I assume?
if resetting data with stock recovery isn't working after a KDZ flash.. I'm not sure what would make it work without having it in my hands.
good luck
autoprime said:
it's odd that LGUP refurbish with the KDZ didn't work. after the KDZ flash does it boot into TWRP or just show the green android? if it shows the green android that means /data should be reset now and you should be able to boot. first boot after a data wipe can take a long time... you waited a bit longer I assume?
if resetting data with stock recovery isn't working after a KDZ flash.. I'm not sure what would make it work without having it in my hands.
good luck
Click to expand...
Click to collapse
After the KDZ flash there was no TWRP. Booting into recovery takes me to the stock recovery, where I can just do a data wipe. So it looks like it changed whatever was causing it to boot directly to recovery.
A normal boot just stays on the LG screen for, say, 5 seconds then the screen briefly goes blank and back to the LG screen. Rinse and repeat.
I'm not sure what the stock recovery normally looks like when you do a data wipe. I get, iirc, 2 questions confirming I want to wipe then it hangs for a short while before rebooting. It's possible that the stock recovery is struggling to access data somehow. Could a format in TWRP have messed it up?
Does a KDZ repartition/format etc?
bigstoo said:
After the KDZ flash there was no TWRP. Booting into recovery takes me to the stock recovery, where I can just do a data wipe. So it looks like it changed whatever was causing it to boot directly to recovery.
A normal boot just stays on the LG screen for, say, 5 seconds then the screen briefly goes blank and back to the LG screen. Rinse and repeat.
I'm not sure what the stock recovery normally looks like when you do a data wipe. I get, iirc, 2 questions confirming I want to wipe then it hangs for a short while before rebooting. It's possible that the stock recovery is struggling to access data somehow. Could a format in TWRP have messed it up?
Does a KDZ repartition/format etc?
Click to expand...
Click to collapse
kdz flashes the main partitions over top of what was there before.. but /data (including internal sdcard) only gets touched in you select "refurbish" in LGUP.. "upgrade" leaves data alone.
stock recovery should ask you to hit "yes" twice... then after the second yes you should see a green android figure in the center of the screen for a second or so... that confirms data is being wiped.
I'm sorry in advance for bumping a 4 year old thread, but it's the only one that outlines the exact same issues I'm having. @bigstoo did you ever manage to fix this? I've tried everything and nothing has worked like you've listed above. I've run out of ideas.
I want to get this phone working to give to my nephew, but obviously can't give a bootlooping phone that doesn't work.
In the pictures attatched is how far I've managed to get, but after the "Android is starting" screen gets to 100% it reboots and goes back to bootlooping.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey there,
I'm having repeated restarts after installing Cyanogenmod 13 (Snapshot) on my honor 5x, let me put you through the steps I followed.
First I unlocked my bootloader using adb/fastboot.
then flashed custome recovery(TWRP)
rooted my phone using SuperSU from TWRP
placed CM 13 and open gApps zip files on SD card
rebooted in recovery mode(TWRP)
selected wipe and swipe
then click on install
selected CM 13 zip file from SD card
swipe to flash
after process completed
wipe Dalvik/cache
then click on install
selected gApps zip file
swipe to flash
and then reboot
then when the phone reboots my phone shows the default honor boot screen and then Cyanogenmod boot screen
and then the phone restarts with a vibration
and keeps on repeating the process untill I restore my TWRP backup
Also I tried only installing CM 13(No gApps-thought it might be interrupting the system) and reboot
and installing gApps and clearing cache/dalvik and then reboot
I tried it many times but still the same issue
Please help me
swapnilVtiwari said:
Hey there,
I'm having repeated restarts after installing Cyanogenmod 13 (Snapshot) on my honor 5x, let me put you through the steps I followed.
First I unlocked my bootloader using adb/fastboot.
then flashed custome recovery(TWRP)
rooted my phone using SuperSU from TWRP
placed CM 13 and open gApps zip files on SD card
rebooted in recovery mode(TWRP)
selected wipe and swipe
then click on install
selected CM 13 zip file from SD card
swipe to flash
after process completed
wipe Dalvik/cache
then click on install
selected gApps zip file
swipe to flash
and then reboot
then when the phone reboots my phone shows the default honor boot screen and then Cyanogenmod boot screen
and then the phone restarts with a vibration
and keeps on repeating the process untill I restore my TWRP backup
Also I tried only installing CM 13(No gApps-thought it might be interrupting the system) and reboot
and installing gApps and clearing cache/dalvik and then reboot
I tried it many times but still the same issue
Please help me
Click to expand...
Click to collapse
I Think you should only Wipe Dalvik/Cache after you install both The Rom and the Gapps... Just install at the same time (The Rom and Gapps)
And Factory reset your System before you install the cynogen and gapps
Milupi said:
I Think you should only Wipe Dalvik/Cache after you install both The Rom and the Gapps... Just install at the same time (The Rom and Gapps)
And Factory reset your System before you install the cynogen and gapps
Click to expand...
Click to collapse
Milupi said:
I Think you should only Wipe Dalvik/Cache after you install both The Rom and the Gapps... Just install at the same time (The Rom and Gapps)
And Factory reset your System before you install the cynogen and gapps
Click to expand...
Click to collapse
What do you mean by installing both at the same time, do you mean selecting both zip files at once?
Also I factory reset my phone before I install cyanogen mod from within twrp and had my phone factory reset before rooting.
Also I've tried to install cm and gapps one by one and wiping dalvik/cache after both of them.
Please help
swapnilVtiwari said:
What do you mean by installing both at the same time, do you mean selecting both zip files at once?
Also I factory reset my phone before I install cyanogen mod from within twrp and had my phone factory reset before rooting.
Also I've tried to install cm and gapps one by one and wiping dalvik/cache after both of them.
Please help
Click to expand...
Click to collapse
Yes selecting both zips at the same time
Milupi said:
Yes selecting both zips at the same time
Click to expand...
Click to collapse
Do I need to factory reset again and Will this revoke my root access.
I'm asking this because of a reason...let me tell you what I've done.
I factory reset my phone, and then made a nandroid backup using twrp, then I flashed superSU using twrp, installed root checker biscuit said root access is installed properly. Then installed cm 13 and gapps, when that didn't worked, I restored my nandroid backup that I made before rooting, and when I checked from root checker, it was saying the phone is not rooted.
swapnilVtiwari said:
I factory reset my phone, and then made a nandroid backup using twrp, then I flashed superSU
Click to expand...
Click to collapse
You made a nandroid backup before root so when you restore it is not rooted ( normal ).
What version of stock do you have before flashing cm13 ? If b360, you have bootloop, under b360 shall be no issue.
What i do to flash:
1/ wipe factory reset
2/ advance wipe cache,dalvik,system,data
3/ install ROM
4/ install gapps (arm64)
5/ wipe dalvik/cache
6/ reboot system
To have root, you need to flash supersu ( after gapps ) or alone after first setup of ROM and gapps.
But most of ROM have root built inside, just need to go to options for dev under settings and select app for root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my KIW-L21 using XDA-Developers mobile app
rodolphe06 said:
1/ wipe factory reset
2/ advance wipe cache,dalvik,system,data
3/ install ROM
4/ install gapps (arm64)
5/ wipe dalvik/cache
6/ reboot system
Click to expand...
Click to collapse
I did as you say, but still the same...it's restarting repeatedly.
swapnilVtiwari said:
I did as you say, but still the same...it's restarting repeatedly.
Click to expand...
Click to collapse
Have you thought of trying another rom ?
Zakaria.R said:
Have you thought of trying another rom ?
Click to expand...
Click to collapse
No, because I think there are no other final builds, and I just wanted to try cyanogen mod and waited for the snapshot build because I don't want to have trouble with my phone as this is my main phone.
swapnilVtiwari said:
No, because there are no other final builds, and I just wanted to try cyanogen mod and waited for the snapshot build because I don't want to have trouble with my phone as this is my main phone.
Click to expand...
Click to collapse
You do know that the other roms share the same sources as cm13 right ? And that a snapshot isn't that more stable than the other roms, it's pretty much a placebo effect,anyway your phone, your call.
R
Zakaria.R said:
You do know that the other roms share the same sources as cm13 right ? And that a snapshot isn't that more stable than the other roms, it's pretty much a placebo effect,anyway your phone, your call.
Click to expand...
Click to collapse
Can you name any other custom Rom that is as good as cyanogen mod and has final stable builds.
And why do you say placebo effect, aren't snapshots the stable builds?
swapnilVtiwari said:
Can you name any other custom Rom that is as good as cyanogen mod and has final stable builds.
And why do you say placebo effect, aren't snapshots the stable builds?
Click to expand...
Click to collapse
There's the final build of RR or crdroid or any other you really should try yourself and see because like I said they all share the same sources
as for what I said about the snapshot, yeah it is stable and is supposed to be bug-free but what I mean is at this point every other rom is as much stable as that snapshot, try by yourself and see.
Zakaria.R said:
There's the final build of RR or crdroid or any other you really should try yourself and see because like I said they all share the same sources
as for what I said about the snapshot, yeah it is stable and is supposed to be bug-free but what I mean is at this point every other rom is as much stable as that snapshot, try by yourself and see.
Click to expand...
Click to collapse
I checked both RR and cRdroid download page, they don't seem to have builds for honor 5x.
swapnilVtiwari said:
I checked both RR and cRdroid download page, they don't seem to have builds for honor 5x.
Click to expand...
Click to collapse
They are in the development section of honor 5x, what are you using to check xda ?
Zakaria.R said:
They are in the development section of honor 5x, what are you using to check xda ?
Click to expand...
Click to collapse
My phone, I restored the nandroid backup I made using twrp.
Could you please share links for cRdroid and resurrection remix download page.
swapnilVtiwari said:
My phone, I restored the nandroid backup I made using twrp.
Could you please share links for cRdroid and resurrection remix download page.
Click to expand...
Click to collapse
I meant which app, but here you go http://forum.xda-developers.com/honor-5x/development you can find any rom you like, it's the "roms and Kernels" section for honor 5x
Zakaria.R said:
I meant which app, but here you go http://forum.xda-developers.com/honor-5x/development you can find any rom you like, it's the "roms and Kernels" section for honor 5x
Click to expand...
Click to collapse
Not using any app, just my phone's browser.
And thank you so much for the links, but most of them links say they're unofficial, and as I said earlier I just can't afford to have trouble as this is the only phone I have.
I really appreciate your help, but I can't take risk as I'm not very much into android development.
Sorry if I bothered you.
I really appreciate your help...but I hope you could help me with my cm13 issue.
swapnilVtiwari said:
Not using any app, just my phone's browser.
And thank you so much for the links, but most of them links say they're unofficial, and as I said earlier I just can't afford to have trouble as this is the only phone I have.
I really appreciate your help, but I can't take risk as I'm not very much into android development.
Sorry if I bothered you.
I really appreciate your help...but I hope you could help me with my cm13 issue.
Click to expand...
Click to collapse
Brother don't be afraid, what matters is the absence of bugs not the tags "official" or "unofficial" your are not gonna break your device (unless you are doing something stupid) and if you want an example to be assured just look at all the users in XDA, they are all rocking nightly builds on their phone, some of them use "betas" and some others use even "alphas" so don't let that Stop you, and if you have a nandroid backup what would you lose ? If you don't like it you get back to your stock rom, don't let your fear prevent you from the sweetness of custom roms.
Hey buddies,
I m currently using kiw-l22,
I installed twrp, but when I flash any custom rom,
I have the same problem as discussed above,
it would be great if I get some help
Appy punia said:
Hey buddies,
I m currently using kiw-l22,
I installed twrp, but when I flash any custom rom,
I have the same problem as discussed above,
it would be great if I get some help
Click to expand...
Click to collapse
Were you on volte firmware before coming to custom rom??
Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
kishikaisei said:
Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
Click to expand...
Click to collapse
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
mecoromeo said:
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
Click to expand...
Click to collapse
I tried that, now I am a step forward I think, I flashed the stock firmware I found, and installed the latest stock ROM, rebooted (doesn't say no os anymore), but the only thing I see is a DELETE ALL DATA button and at the bottom 'Encryption was interrupted and can't be completed. As a result, the data on your phone is no longer accessible.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account.'
Darklouis said:
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
Click to expand...
Click to collapse
I have an issue with the MiFlash part, it seems that it doesn't work as I mentioned...
Aight all, formatting data partition to ext4 worked, now it is booting
kishikaisei said:
Aight all, formatting data partition to ext4 worked, now it is booting
Click to expand...
Click to collapse
Works now?
mecoromeo said:
Works now?
Click to expand...
Click to collapse
So I had an OS-less phone that don't get recognised in MiFlash, and I had orangeFox recovery.
The steps to fix were:
- Flash a full stock Firmware
- Flash the stock ROM
- Flash DFE
- Format data to ext4
- Reboot and it works
So thanks all for your help