I recently purchased the me max 2 x829. I had twrp 3.1.1.0 installed and tried out MIUI just fine. I later restored my backup and went to install small eui. After doing so the stock recovery is what my phone would boot into when trying to boot into recovery. I've tried reinstalling twrp but when booting into recovery I just get a blue led and on the next attempt I get the stock recovery again. Any help? I'm currently running the 16s Indian stock rom
Sent from my Nexus 5X using Tapatalk
GenoAndroid said:
I recently purchased the me max 2 x829. I had twrp 3.1.1.0 installed and tried out MIUI just fine. I later restored my backup and went to install small eui. After doing so the stock recovery is what my phone would boot into when trying to boot into recovery. I've tried reinstalling twrp but when booting into recovery I just get a blue led and on the next attempt I get the stock recovery again. Any help? I'm currently running the 16s Indian stock rom
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I haven't read anything about but I also had problems with this twrp version. My first attempt was just booting it and I got the same blue led with no response. Fastboot commands were not being recognized as well. So I tried the second most recent version, which worked smoothly.
The last one e quite smaller so I was afraid it could be corrupted. Not sure about it.
Sent from my Le X820 using Tapatalk
razmth said:
I haven't read anything about but I also had problems with this twrp version. My first attempt was just booting it and I got the same blue led with no response. Fastboot commands were not being recognized as well. So I tried the second most recent version, which worked smoothly.
The last one e quite smaller so I was afraid it could be corrupted. Not sure about it.
Sent from my Le X820 using Tapatalk
Click to expand...
Click to collapse
I'll test the previous recent version and report back.
Sent from my Le X821 using Tapatalk
razmth said:
I haven't read anything about but I also had problems with this twrp version. My first attempt was just booting it and I got the same blue led with no response. Fastboot commands were not being recognized as well. So I tried the second most recent version, which worked smoothly.
The last one e quite smaller so I was afraid it could be corrupted. Not sure about it.
Sent from my Le X820 using Tapatalk
Click to expand...
Click to collapse
So. I had the version numbers wrong. I was trying to install the most recent 3.1.1.1 to no avail. I pushed 3.1.1.0 to the phone via fastboot with no issues and currently running miui again. Thanks for your help [emoji2]
Sent from my Le X820 using Tapatalk
Related
Recently just received a warranty replacement Note 2 and of course first thing I did was root and unlock it. After flashing a rom a indicator would pop up saying TWRP had lost root permissions and after selecting okay, fix permissions for it. I wrote it off not thinking much of it but after flashing a different rom the same pop up appeared again, still no problems. Finally my phone started locking up and today it eventually bricked up as I flashed a rom. No biggie, I flashed back to stock and am good to go but I just want to know if anyone else has come across this same issue as well?
Sent from my SCH-I605 using Tapatalk 4 Beta
endo689 said:
Recently just received a warranty replacement Note 2 and of course first thing I did was root and unlock it. After flashing a rom a indicator would pop up saying TWRP had lost root permissions and after selecting okay, fix permissions for it. I wrote it off not thinking much of it but after flashing a different rom the same pop up would appear again, still no problems. Finally my phone started locking up and today it eventually bricked up as I flashed a rom. No biggie, I flashed back to stock and am good to go but I just want to know if anyone else has come across this same issue as well?
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Only time I've seen this it has been an issue with the rom I'm flashing.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Only time I've seen this it has been an issue with the rom I'm flashing.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
For some reason it happened with every rom I would flash. Possibly mucked something up when I rooted and unlocked in the first place.
Sent from my SCH-I605 using Tapatalk 4 Beta
I is twrp that causes the issue, if I'm mistaken they have updated to fix that bug.
M.A.D.NoTe.||
Going through the exact same thing right now, same situation and all, did you get this worked out? I flashed back to stock just a couple minutes ago and am now in the process of flashing a custom rom again. Never experienced this before and been flashing on this phone the Note 2 since October. New phone, new problem. Used the Toolkit to do everything every time I get a new phone. This is my third.
StevetotheH said:
Going through the exact same thing right now, same situation and all, did you get this worked out? I flashed back to stock just a couple minutes ago and am now in the process of flashing a custom rom again. Never experienced this before and been flashing on this phone the Note 2 since October. New phone, new problem. Used the Toolkit to do everything every time I get a new phone. This is my third.
Click to expand...
Click to collapse
Sorry for such a long delay in responding. I found a fix for this issue. I ended up just flashing all the way back to the original stock rom when the Note 2 was released then went about using the unlocking/rooting methods and have not ran into a single problem.
Sent from my SCH-I605 using Tapatalk 4 Beta
endo689 said:
Sorry for such a long delay in responding. I found a fix for this issue. I ended up just flashing all the way back to the original stock rom when the Note 2 was released then went about using the unlocking/rooting methods and have not ran into a single problem.
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I was having this issue a few days ago and formatting my internal SD with TWRP and reflashing my ROM fixed it.
Sent from my SCH-I605 using XDA Premium HD app
I wipe internal every time along with the normal wipes when I flash a rom. Gives you the best chance of everything being stable and having a great gps lock even on aosp or tablet roms
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
I wipe internal every time along with the normal wipes when I flash a rom. Gives you the best chance of everything being stable and having a great gps lock even on aosp or tablet roms
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I do this as well but for some reason twrp still lost root permissions.
Oh well having no issues anymore so I am a happy camper.
Sent from my SCH-I605 using Tapatalk 4 Beta
USB connection problems
Now I keep running into USB driver issues as of late. Don't understand why this keeps happening. Uninstalled and reinstalled all drivers and Note 2 connects for awhile and then completely stops. I can browse/edit items on the phone but cannot copy files over to it. A pop up saying it has been disconnected and cannot copy files to said device. WTF?!
endo689 said:
Now I keep running into USB driver issues as of late. Don't understand why this keeps happening. Uninstalled and reinstalled all drivers and Note 2 connects for awhile and then completely stops. I can browse/edit items on the phone but cannot copy files over to it. A pop up saying it has been disconnected and cannot copy files to said device. WTF?!
Click to expand...
Click to collapse
What OS you on? Try a different cable and different usb port. Use the drivers from mskips all in one tool from the forum. Have you tried adb devices to see if it recognizes your device? If you haven't rebooted you rig lately do that and your device as well. I had this happen for a minute on Win8 I had to manually point the driver update to the file I wanted to use.
Rock, Flag and Eagle!
Way back when I got my Note 2.... the version of casual actually flashed a wrong TWRP , it was the one for the international Note 2.
The fix was to simply install the newest TWRP for our phone (SCH-i605)
Milimbar said:
Way back when I got my Note 2.... the version of casual actually flashed a wrong TWRP , it was the one for the international Note 2.
The fix was to simply install the newest TWRP for our phone (SCH-i605)
Click to expand...
Click to collapse
What?
Rock, Flag and Eagle!
StevetotheH said:
What OS you on? Try a different cable and different usb port. Use the drivers from mskips all in one tool from the forum. Have you tried adb devices to see if it recognizes your device? If you haven't rebooted you rig lately do that and your device as well. I had this happen for a minute on Win8 I had to manually point the driver update to the file I wanted to use.
Rock, Flag and Eagle!
Click to expand...
Click to collapse
I will definitely give this a shot when I have a chance.
Sent from my SCH-I605 using Tapatalk 4 Beta
Make sure youre using the latest TWRP version.
After installing the unofficial CyanogenMod 11 build, whenever I try to boot into TWRP it hangs at the logo.
I've went back to stock and reflashed the latest TWRP via Odin but it refused to go past the "teamwin" screen.
I tried different versions of TWRP and nothing works. My SD Card is not detected either; I don't know if that's related.
I'm not sure where else to go from here.
You can try the version of TWRP before the current one, read somewhere that a few people where having problems with latest version. Might help.
Sent from my SM-N900P using XDA Premium 4 mobile app
tonyevo52 said:
You can try the version of TWRP before the current one, read somewhere that a few people where having problems with latest version. Might help.
Click to expand...
Click to collapse
I'll give it a try and update with results.
EDIT: Didn't work. Got stuck on the "RECOVERY BOOTING....." screen with nothing coming up.
Just flashed 2.6.3.0 and got stuck at the splash screen again.
Read through the TWRP feed, might something, or someone who can help.. http://forum.xda-developers.com/showthread.php?t=2471564
Sent from my SM-N900P using XDA Premium 4 mobile app
Not sure what happened but my after my Note 3 detected my SD Card, recovery started working again.
So I've tried researching this slight issue and I have seen a lot of different solutions but none of them apply to my particular problem. My phone works just fine when booted regularly and charges just fine. The only time I'm having an issue is if I boot into recovery. I just installed twrp 2.7.0.3 and tried to reboot in order to flash supersu. No dice. I've tried rebooting into fastboot and reflashing and I've tried the M8 toolkit. Reflashing works, but still won't boot to recovery and the toolkit just hangs trying to flash the file. I think that's where my issue lies. I waited 19 minutes and eventually closed the program and just rebooted. I'm thinking this caused an issue and corrupted my recovery but i figured reflashing would solve this.
I was wondering if someone could clarify this for me, in which i'll just sit tight and wait until an ruu releases and stick with stock sense. The phone works perfectly so I can deal for a little while. I was just hoping to move to the GPe rom and get xposed running on it.
Thanks yall. I'll keep searching until I have to go to work and if I find a solution before anyone responds I'll update this post so it can be locked.
I would make sure you adb files are up to date, and try flashing philz recovery instead.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
HolyAngel said:
I would make sure you adb files are up to date, and try flashing philz recovery instead.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you using philz instead? I flashed twrp and it's very buggy. Did you fastboot flash recovery etc...? How can I install philz over twrp?
Thanks
Sent from my HTC One_M8
yeah im using philz, have been since it came out as i thought the same about twrp, tons of issues.
definitely 'fastboot flash recovery philz_touch_6.25.5-m8.img'
It'll apply itself right over your current recovery no problem :good:
pokedroid said:
So I've tried researching this slight issue and I have seen a lot of different solutions but none of them apply to my particular problem. My phone works just fine when booted regularly and charges just fine. The only time I'm having an issue is if I boot into recovery. I just installed twrp 2.7.0.3 and tried to reboot in order to flash supersu. No dice. I've tried rebooting into fastboot and reflashing and I've tried the M8 toolkit. Reflashing works, but still won't boot to recovery and the toolkit just hangs trying to flash the file. I think that's where my issue lies. I waited 19 minutes and eventually closed the program and just rebooted. I'm thinking this caused an issue and corrupted my recovery but i figured reflashing would solve this.
I was wondering if someone could clarify this for me, in which i'll just sit tight and wait until an ruu releases and stick with stock sense. The phone works perfectly so I can deal for a little while. I was just hoping to move to the GPe rom and get xposed running on it.
Thanks yall. I'll keep searching until I have to go to work and if I find a solution before anyone responds I'll update this post so it can be locked.
Click to expand...
Click to collapse
Seems like every problem in here is when someone uses a toolkit. IMO it is easier just to use the commands. There is nothing wrong with twrp as most people including myself are using it flawlessly. Download fresh copy of twrp. Make sure you get .img file, not .zip. Boot your phone, plug in and type "adb reboot bootloader" it will reboot to fastboot, if not, you do not have newest adb drivers, get this fixed before moving on. once in bootloader type "fastboot reboot-bootloader" this will just reboot your boot loader and let you know fastboot is working. If not fix this. next move to your directory with twrp and type "fastboot flash recovery twrp***.img" should only take 5 seconds. next type fastboot reboot to make sure system is still booting. Then type "adb reboot recovery" and it should go to twrp. Make sure you are getting the UL_CA twrp and not the whl. whl is for sprint and will not work. let me know. UL_CA is not available on official site. search the xda forums for it.
I actually tried the commands first and couldn't get it that's why I tried the toolkit. That's actually what ended up working for me though, but at least I'm good to go! I should have updated this a few days ago but forgot lol this thread can be locked if a mod wants to. Thanks all
Sent from my HTC One_M8 using Tapatalk
HolyAngel said:
yeah im using philz, have been since it came out as i thought the same about twrp, tons of issues.
definitely 'fastboot flash recovery philz_touch_6.25.5-m8.img'
It'll apply itself right over your current recovery no problem :good:
Click to expand...
Click to collapse
Which version of the recovery did you download? I can't find an AT&T version . Just regular M8 version. Just wanna make sure
Sent from my HTC One_M8 using Tapatalk
Z51 said:
Which version of the recovery did you download? I can't find an AT&T version . Just regular M8 version. Just wanna make sure
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
The regular m8 version in original android development ^^
Sent from my HTC One_M8 using XDA Premium 4 mobile app
I'm trying to use TWRP to update to a new cm12 nightly, but every time I select the zip and try to flash it, TWRP crashes and reboots. Is there something I'm missing? It's probably just a noob mistake... For example I only today figured out how to get TWRP to cooperate with encryption and my pattern lock on boot up, hah. I thought it wasn't mounting storage because something was corrupted. Anyways, thanks for any suggestions you can give.
What version of twrp are you using?
Sent from my Nexus 5 using XDA Free mobile app
I have the same issue. It is only with 5.1 Android and I am using 2.8.5 TWRP
Sent from my VS985 4G using Tapatalk 2
I had the problem this afternoon. I just tried it again and it worked. Didn't change anything.. never had problems like this on any other Nexus device. Creepy.
jd1639 said:
What version of twrp are you using?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
2.8.5.0. But I did some more tinkering today and eventually solved my problem. Here's to help you others who saw the same thing: I tried using progressively older versions of TWRP to see if they're used work, until version 2.8.2.1 I think. At that version, instead of crashing, it gave me an error that my zip file was corrupted. I deleted the zip and downloaded it again, switched back to version 2.8.5.0, and everything worked. (except for the Rom, which had bugs that made it unusable, but at least it flashed successfully and booted lol). Hopefully my experience can help someone else now.
I'm having issues with twrp hopefully I found the right thread. It shows no storage available? I'm trying to flash CM. Thanks
Xda posted that twrp 3.0 has been released for all previously supported devices (including ours) link herehttps://twrp.me/devices/lgg3verizon.html however, haven't flashed yet. A little scared it's not pre-bumped.. Enjoy!
I dont know if it bumped either. Consider this a bump lol. If you knows if it is please Comment.
Flashed now. Bumped and awesome!!
Looks good. But it still can't decrypt
Sent from my LG-VS985 using Tapatalk
Seems to be working just fine here. Thanks
I read about multiple issues with various builds on reddit. I'm gonna stick with what I know works for now.
Actually. It said some known good zips were corrupt.
Sent from my Venue 8 7840 using Tapatalk
Thanks for the notice.
Idk if flash it = get ready for VS98546A
I'm on 46a with twrp 3.0... Lol
guys what do you mean by bumped?
Actually the zips were corrupt. 3 is working fine. Cm13
Sent from my Venue 8 7840 using Tapatalk
for some reason, I'm only getting to the twrp 3 screen and not into twrp 3 yet. CM13 still works, I can boot into the os, but I cant flashify twrp, I cant reboot into twrp and now I'm stuck trying to reflash twrp from android terminal. any ideas why this failed?
Seems like the issue was my SD card. No reason for it, but when I pulled my sd card, rebooted into recovery, twrp 3 would work fine. Just FYI if anyone else gets stuck on the recovery TWRP 3 boot screen. I found the info here