yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Lanchon:
TWRP FAILS TO BOOT in the most mysterious way

i have two OPOs here with me.

on the old one everything works ok: i can "fastboot flash" TWRP and later boot it, or straight "fastboot boot" into it. in both cases TWRP boots up fine.

on the brand new OPO that im just trying out, TWRP doesn't boot at all. the exact same software on the phone, including bootloader, modem etc (44S). the exact same TWRP files and fastboot commands! tried 2.8.1.0 and 2.8.3.0.

whether i flash it or fastboot boot it, the result is the same: video corruption, vertical lines, some screen noise. most of the time the screens turns fully off after a few seconds. the phone needs the 10-second power button press to reboot.

adb can't connect because the my linux box can't even enumerate the device:

----------

[1389699.593916] usb 1-1.2.1: new high-speed USB device number 116 using ehci-pci

[1389699.708836] usb 1-1.2.1: New USB device found, idVendor=18d1, idProduct=d00d

[1389699.708839] usb 1-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[1389699.708841] usb 1-1.2.1: Product: Android

[1389699.708842] usb 1-1.2.1: Manufacturer: Google

[1389699.708843] usb 1-1.2.1: SerialNumber: e615fff

[1389833.654114] usb 1-1.2.1: USB disconnect, device number 116

[1389865.110969] usb 1-1.2.1: new high-speed USB device number 117 using ehci-pci

[1389865.204269] usb 1-1.2.1: no configurations

[1389865.204282] usb 1-1.2.1: can't read configurations, error -22

[1389865.278920] usb 1-1.2.1: new high-speed USB device number 118 using ehci-pci

[1389865.372169] usb 1-1.2.1: no configurations

[1389865.372181] usb 1-1.2.1: can't read configurations, error -22

[1389865.447251] usb 1-1.2.1: new high-speed USB device number 119 using ehci-pci

[1389865.468965] usb 1-1.2.1: no configurations

[1389865.468981] usb 1-1.2.1: can't read configurations, error -22

[1389865.543334] usb 1-1.2.1: new high-speed USB device number 120 using ehci-pci

[1389865.564836] usb 1-1.2.1: no configurations

[1389865.564848] usb 1-1.2.1: can't read configurations, error -22

[1389865.567126] hub 1-1.2:1.0: unable to enumerate USB device on port 1

----------

i think there might be a problem with the hardware. can anybody shed some light?

more info:

-cm11 seems to work

-cm12 seems to work

-TWRP using cm12's bootloader fails in the same way

-Philz Touch recovery works fine

WORKAROUND: use Philz Touch recovery.
[ONE Original Android Development] bombadier:
Has anyone tried the new recovery ? I just flashed it but in recovery the touchscreen does not work and then it reboots
[ONE Original Android Development] Nburnes:
Same thing happens here. Actually came just to post that.
[ONE Original Android Development] Jax Teller:
Same here.

Probably the build needs some fixing.

I guess they will update it soon.[emoji4]

For now back to 2.8.3.0.
[ONE Original Android Development] gulp79:
same for me
[ONE Original Android Development] Mr_President:
Ahhh was gonna post the same thing :D. Thought it was me being an idiot... not this time though hue hue :p
[ONE Original Android Development] störte:
Was interested in New Version but reboot so back

Send by Hyperdrive on one+One
[ONE Original Android Development] BarnOwl:
Same here........back to 2830
[ONE Original Android Development] Criton30:
in the official 2.8.3.0 there is a reboot issue too for me..... [MENTION=3814731]katinatez[/MENTION] has resolved this.
[ONE Original Android Development] Emilius:
For me too. 2.8.3.0 reboots from time to time, not every time. I am back to 2.8.1.0.
[ONE Original Android Development] Underslung:
Experiencing same issue mentioned above on 2.8.4.0 (touchscreen is not responsive then device reboots).

Back to 2.8.3.0 ...
[ONE Original Android Development] Doo Doo:
What is everybody talking about I have no problems with the latest recovery 2.8.4.0 everything is working just fine for me ;)
[ONE Original Android Development] störte:
Thats strange.
[ONE Original Android Development] :
Same for me [emoji20]

Back to 2.8.3.0
[ONE Original Android Development] xanthrax:
Have you by any chance flashed cm 12 12/1 nightly before?

Sent from my Darkside of 1+1
[ONE Original Android Development] Heisenberg:
Yeah I agree. Version 2.8.4.0 is working perfectly for me. How is everyone flashing it? Are you all checking the md5?
[ONE Original Android Development] jackmacbunton:
Yeah same too
[ONE Original Android Development] Spannaa:
It's working fine for me too with cm12 14/1 nightly
[ONE Original Android Development] CBpbxEcmecmBeH:
Seems to be working for me too (via flashify)
[ONE Original Android Development] xanthrax:
So, apparently we need the latest firmware /touch update

Sent from my Darkside of 1+1
[ONE Original Android Development] bombadier:
Tried with flashable zip then downloaded the image again and fastbooted it no dice touchscreen does not respond and after a second or two it reboots :confused: Why should being on the the latest CM12 nightly be anything to do with it ?
[ONE Original Android Development] scanno:
Because CM12 flashes another radio image and bootloader
[ONE Original Android Development] Heisenberg:
I'm not even on Lollipop, I'm running the last Nameless KitKat build. Try flashing it with fastboot, followed by the fastboot format cache command.

Transmitted via Bacon
[ONE Original Android Development] bombadier:
So the bootloader may be the issue ?

I had a really weird problem last week with ak's kernel, he released a version that had some commits that meant it would not work on a kitkat rom (084) resulted in a bootloop,however the other weird thing was that when I rebooted to recovery I had the same problem that the touchscreen would not respond,that was on 2.8.3.0 I asked ak about it and he said it was a coincidence, none of this makes sense,I jumped onto freenode to try and troubleshoot this with someone but I cannot even workout how to post a message lol do I need a plugin or something ? I just clicked the link in the op

Will try again with the format cache command and see what happens
[ONE Original Android Development] scanno:
I am not saying that the bootloader is the issue... what i do know is that CM12 nightly builds flash another radio image and bootloader images. This can result in strange behouvior (or in worst case a bootloop)
[ONE Original Android Development] bombadier:
Still not working

I have opened an issue

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/330

Managed to get the last log if anyone can make sense of it

last_log
[ONE Original Android Development] Doo Doo:
Nope
[ONE Original Android Development] geowolf1000:
Newest support ems partition backup/restore?
[ONE Original Android Development] masterchiefb117:
Also having the no touch then restart... so went back to 2.8.3.0 and had issues again. went down to 2.8.1.0 and now im stuck on the oneplus start up :(
[ONE Original Android Development] bombadier:
Not the official 2.8.4.0 but this unofficial one does although that is still on 2.8.3.0
[ONE Original Android Development] masterchiefb117:
Hmmm ok so i tried using flashify as i suspected that the trwp app wasnt working right. So tried the 2.8.4.0 and still no luck. but at least i was able to go back on 2.8.1.0 with working touch.
[ONE Original Android Development] :
Update

System environments:

* cm12 nightly 20150114

* Flashify

* Flash Image GUI

* TWRP 2.8.4.0

-> Touchpanel non responsive and restart after short time (~1sec)

TWRP2.8.3.0 is working fine
[ONE Original Android Development] Lanchon:
my phone:

TWRP 2.8.4.0: Touchpanel non responsive and restart after short time (~1sec)

TWRP 2.8.3.0: working fine
[ONE Original Android Development] soralz:
Same to me.

But the strange thing is, my Chinese version OPO 16G is working perfectly fine with 2.8.4.0. But not on my 64G Int OPO. What might cause the issue? I roll back to 2.8.1.0 which is the pretty stable TWRP for me.

2.8.1.0 should be fine because from this version onwards my OPO is facing some issue, on 2.8.3.0 I will face the zip installation halfway and rebooted itself :(
[ONE Original Android Development] Uqbar:
Where did you get the ZIP for 2.8.4.0?

Where did you get the ZIP for 2.8.4.0? TIA
[ONE Original Android Development] Tajnymag:
2.8.4 non-touch restart

I found there's a new TWRP available. This time I was lazy, so I tried to use the app. I installed the SD-patch, rebooted and tried to install the TWRP through the install option. I tapped yes to the dialog message. Suddenly, the app is unusable. Whenever I try to open it, it crashes after a few seconds. Also when I try to boot to recovery, I see the TWRP home screen but it's not resoponsing and crashes afterwards. I reverted via fastboot to 2.8.3 and no problem. Am I the only one? I really want the "flash recovery image" feature.
[ONE Original Android Development] LeroViten:
No, you're not alone. Last few pages include discussion on that issue. So revert back to 2.8.3.0 and keep waiting for the update. ;)
[ONE Original Android Development] bombadier:
I just updated an old zip but I would wait as a lot of people are having problems with the new version so sit tight
[ONE Original Android Development] Bambou64:
[RECOVERY][bacon] TWRP 2.8.4.0 touch recover

2.8.4.0 working fine on my OPO, with CM12 nightlies.

No touch issue, no reboot.

Sent from my OnePlus One using Forum Fiend
[ONE Original Android Development] bombadier:
Still not working
[ONE Original Android Development] soralz:
I think this probably is related to the MTP, on my 16G OPO, it's working fine until I enable MTP (without turning off) I rebooted to the recovery again, and it gets stucked and reboot to OS.
[ONE Original Android Development] bombadier:
Spoke too soon although that method allowed me to install, connect the cable and touchscreen freezes then it reboots so stay on an earlier version
[ONE Original Android Development] vasilis1:
Zip link guys?
[ONE Original Android Development] bombadier:
I would wait read back a few pages as 2.8.4.0 is causing a lot of people problems
[ONE Original Android Development] :
Which nightly version of cm12? Are you using one of the pulled nightly versions (13th / 14th Jan)? Or an earlier version?
[ONE Original Android Development] AncientLord:
With newly released 2.8.4.0, touch screen is not working anymore and phone reboots. Moreover the reported CPU temperature is not right. It's somewhat 10 degrees higher than reported by 2.8.3.0. Any fix will be appreciated. I am on stock CM11s with Build Number XNPH44S.
[ONE Original Android Development] gmi78:
touch issue also for me with latest version
[ONE Original Android Development] bombadier:
For all those with issues please add a comment on the issue I opened on github

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/330

tapatyping fae the bacon
[ONE Original Android Development] Lanchon:
i think that github and tracker might have been abandoned.
[ONE Original Android Development] bombadier:
That's where I was told to open an issue

tapatyping fae the bacon
[ONE Original Android Development] Lanchon:
and if somebody says jump out the window?? :-p have you seen the last commit date there?
[ONE Original Android Development] bombadier:
That's the one in the op and I asked on g+ thread and that was where I was told to open it ?

tapatyping fae the bacon
[ONE Original Android Development] DesignGrits:
Sorry, late to the game, but yes lots of issues on the latest. Flashed back to previous.
[ONE Original Android Development] NB2A:
I just loaded TWRP and was running Beans build 26 on a Verizon Note 2. I have always used CWM for recovery and updating the phone. I tried to update Alliance Rom build 30 and it failed while loading in TWRP. No matter what I do now I cannot get past simply loading TWRP. Do I have start from stock again using Odin? Please help. Sorry to bother with post here.
[ONE Original Android Development] soralz:
You can just boot into OS, by using Flashify or similar app then flash a working recovery, or you can use ODIN to flash the custom recovery only.

Back to 2.8.1.0, which is the stable recovery for me, have not encountered any problems.
[ONE Original Android Development] Heisenberg:
Isn't ODIN Samsung only?

Transmitted via Bacon
[ONE Original Android Development] Lanchon:
why are u posting on the oneplus one thread???!!!
[ONE Original Android Development] NB2A:
I cannot get into anything except TWRP. I thought Odin was only used once as I did years back to root this phone. What file do I load into Odin and what path please if TWRP cannot help at this point? Thank you again.

---------- Post added at 11:05 PM ---------- Previous post was at 11:03 PM ----------

Because I am stuck in TWRP now sorry
[ONE Original Android Development] kenkiller:
Wrong device. Ask somewhere else. :D
[ONE Original Android Development] iamelton:
2.8.4.1 was released..

im not able to test now.. could anyone test to see if that fixes the reboot issue? thx..
[ONE Original Android Development] Heisenberg:
You're asking in the wrong place. We don't have your device, you need to go to the correct device section and ask there so that people who are familiar with your device can help you. You can't just randomly ask in an entirely different device section. Surely you've been an XDA member for long enough to know that.
[ONE Original Android Development] NB2A:
I am sorry with the new format here and the site working slow I messaged in the wrong forum. My apologies.
[ONE Original Android Development] tobitege:
At the bottom of the page, left corner, you can switch the XDA layout to e.g. "XDA 2013 Beta - 1024" to get rid of the right sidebar (matter of taste). /OT
[ONE Original Android Development] :
The latest update 2.8.4.1 worked on my device, so that is good.
[ONE Original Android Development] Nburnes:
Yep, working fine here as well.
[ONE Original Android Development] Uqbar:
Zip?

Flashable zip?
[ONE Original Android Development] LeroViten:
Use Flashify app from the play store. It is simple and fast. ;)
[ONE Original Android Development] Uqbar:
Nope!

I already have my flashing tool, it's called TWRP. ;)
[ONE Original Android Development] Heisenberg:
Why don't you just flash it

the way it's meant to be flashed

? That's with fastboot. Or Flashify as a secondary option. Flashable zips are not the norm, especially for recoveries. Either learn how to make the zip yourself or use the normal method instead of getting someone else to go out of their way to create something that isn't even worth the hassle because much better methods already exist.
[ONE Original Android Development] etoy:
for those who wanted a flashable zip for TWRP 2.8.4.1

hopefully the last one too as now it natively supports .img files
[ONE Original Android Development] Bambou64:
You don't need a flashable zip with TWRP...

You can flash recovery images directly in recovery, with embedded flashify tool...

(Flashify app not needed)

I flashed 2.8.3.0, 2.8.4.0, and last 2.8.4.1 images with this method, without issue.

I think [MENTION=1966251]Uqbar[/MENTION] was talking about that method, and not about zips :)

Sent from my OnePlus One using Forum Fiend
[ONE Original Android Development] Heisenberg:
He's talking about flashable zips. That's why he said flashable zip.

Transmitted via Bacon
[ONE Original Android Development] Bambou64:
Indeed, sorry ;) , I missed his previous post, requiring a zip...
[ONE Original Android Development] Spannaa:
:confused: How did you flash 2.8.3.0 & 2.8.4.0 using this method - it was only added in 2.8.4.0
[ONE Original Android Development] Bambou64:
I don't know :D

I installed TWRP 2.8.1.0 version from PhilZ recovery with a flashable zip.

And all the next TWRP images from TWRP, with flashify tool.

This flashify tool was maybe already present in the Materialised theme...

If anyone has the answer...

EDIT : yes, after checking, it was included in the theme :
[ONE Original Android Development] Heisenberg:
Yep. I was thinking exactly the same thing.

Transmitted via Bacon
[ONE Original Android Development] Bambou64:
See my previous post ;)
[ONE Original Android Development] Heisenberg:
Very interesting to see a feature added but without the ability to use it natively until quite a few versions later.

Transmitted via Bacon
[ONE Original Android Development] jackmacbunton:
2.8.4.1 working perfectly thanks!
[ONE Original Android Development] bombadier:
It was a script that osm0sis developed for the material theme that allowed this
[ONE Original Android Development] Bambou64:
[MENTION=2714876]bombadier[/MENTION] : Exactly, I added the precision in my post

Sent from my OnePlus One using Forum Fiend
[ONE Original Android Development] Heisenberg:
Right, I was thinking it would be a bit odd to implement something that major without the GUI component added in. Stranger things have happened though so it was relatively believable.

Transmitted via Bacon
[ONE Original Android Development] bombadier:
Just saw that buddy thanks:good:
[ONE Original Android Development] Uqbar:
That feature is only available with ... 2.8.4.1 which is the version I need to install!!!

In my limited view, a recovery needs to be flashed either with fastboot from a PC or from the recovery itself. Also because I use that recovery session also to make a backup.

Flashify, AFAIR, needs to reboot to the recovery in order to finalize the flashing. This is why I still prefer to user TWRP itself.

Anyway, the zip is on its way now.

---------- Post added at 12:38 PM ---------- Previous post was at 12:34 PM ----------

T H A N K S !!!

I still think this is the right way to flash a recovery.

With the new "flash from image" the ZIPs will be needed only from those who come from another recovery, or an older TWRP.
[ONE Original Android Development] bombadier:
Check this recovery theme out

http://xdaforums.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584

a script by osm0sis allowed you to flash from within previous recovery versions, it does not matter now as it 2.8.4.1 has the functionality you seek
[ONE Original Android Development] Bambou64:
+1 :D

Sent from my OnePlus One using Forum Fiend
[ONE Original Android Development] Natakranta:
It's such old news. I'm using Materialised theme in TWRP to flash recovery images or even radio images for few months now, at least from 2.8.1.0 times if not earlier, I don't remember precisely.

Is funny it took TWRP so long to introduce it natively. And gosh, naked not themed TWRP screen on previous page, I forgot how ugly it looks. Well, in don't care since the themes are updated almost instantly.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] bombadier:
The news is that old that it seems that a few folks still don't know about it,which is why I posted the link :eek:

Cant understand why it is not default, as I like you cannot stand a naked TWRP :silly:
[ONE Original Android Development] etoy:
the screenshot was mine, i also use materialized theme from the beginning (and holofied before that).

just renamed ui.zip for the screenshot :)

p.s.

stock curtain is even uglier than naked interface, i edit it too on every new version
[ONE Original Android Development] Natakranta:
The same. I change the curtain now from within the theme in recovery. So simple, just get the right size picture.

Anyway, I'm using multiROM, so I'm waiting for multiROM dev to come up with TWRP update.

Anybody using new 2.8.4.0 or 2.8.4.1 does USB OTG works for you when in recovery?

I want to check if TWRP lost it or only multiROM TWRP lost it. Thanks!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] bombadier:
Cant speak for multirom but OTG is working in 2.8.4.1 at least I mounted a sdcard and could see the contents
[ONE Original Android Development] Natakranta:
Perfect, that's what I wanted to hear!

So let's hope multiROM TWRP regain it with update from 2.8.3.0 to 2.8.4.1

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] bombadier:
Cool,the way I worded it, sounds a bit rude :laugh::laugh:
[ONE Original Android Development] Uqbar:
If I need to install a theme in order to gain a feature, then the default one is trivially buggy. I would have posted a huge warning fo everyone to read in case I had found that out!
[ONE Original Android Development] z31s1g:
There was no "trivially buggy default support" for flashing images in TWRP by the time the theme gained this feature (by executing a shell script).

The theme didn't "unhide" something that wasn't meant to be used. The feature was part of the theme. The whole point of the Materialised theme is not only to make TWRP look different, but to improve usability in general and, if possible, add features that aren't included in TWRP by default.

The native image flashing that comes with the latest TWRP has nothing to do with the script we've been using for while now. But both methods have been / are working brilliantly.
[ONE Original Android Development] napacastro:
No issues here I'm on latest cm12 nightly 20150112
[ONE Original Android Development] Lanchon:
x.4.1 has solved the issue!!!!!!! x.1.0, x.3.0 and x.4.0 all continue to fail to boot.

changes are not pushed to github yet:

https://github.com/omnirom/android_bootable_recovery/commits/android-5.0

could the developer share some light on the changes? thank you!
[ONE Original Android Development] Prodromodinverno:
X.4.1 is not flashable yet from twrp app
[ONE Original Android Development] RickyWars1:
Alright TWRP 2.8.4.1 is confirmed working good for me. Although I had to flash with ABD, it's not available through the TWRP app.
[ONE Original Android Development] ptr_hamilton:
But from 2.8.4.0 itself
[ONE Original Android Development] Heisenberg:
So just flash with fastboot.
[ONE Original Android Development] DerRomtester:
Or use flashify.
[ONE Original Android Development] inzaghi75:
Where can I find the link for the latest update 2.8.4.1?
[ONE Original Android Development] Heisenberg:
In the OP, as usual.

Transmitted via Bacon
[ONE Original Android Development] wrinkletit:
u guys got MTP working in 2.8.4.1?

mine didnt

2.8.3.0 is flawlessly working
[ONE Original Android Development] Heisenberg:
Working fine for me, tested a few hours ago.
[ONE Original Android Development] PresidentMcCain:
2.8.4.1 works for me as well
[ONE Original Android Development] Underslung:
Successfully flashed 2.8.4.1 over 2.8.3.0 via fastboot.

All working :good:
[ONE Original Android Development] knuspertante:
Is it enabled?!
[ONE Original Android Development] wrinkletit:
what u meant by enabled?

its in mount>enable mtp

yup i did

still not recognize unless im on 2.3.8.0
[ONE Original Android Development] Heisenberg:
How long are you waiting when you connect your phone? It took a little while for my PC to install it as a "new" device.

Transmitted via Bacon
[ONE Original Android Development] tobitege:
Hi Timmaaa... just to clarify... does a new recovery on the same device come with a new usb/device ID (or something) for windows to search/load new drivers? Is that what you are saying or did I misread the "new device"?
[ONE Original Android Development] jenaplisken:
2.8.4.1. zip version

https://mega.co.nz/#!lwQTxLpS!v5iyqDb5a8-5DaRMjeB7swG8uOag0k3lVOLtMKmF9fE
[ONE Original Android Development] nolsen311:
cryptfs corruption?

Can anyone [MENTION=4154904]PresidentMcCain[/MENTION] speak to whether 2.8.4.1 fixes the issue with corrupted data partitions when using encryption? I'd really like to get my phone encrypted, but if there's going to be an issue with corruption that obviously holds things up...just a bit.
[ONE Original Android Development] Heisenberg:
Not every new recovery version has come with a new device ID, but 2.8.4.0 seems to have done so.

Transmitted via Bacon
[ONE Original Android Development] tobitege:
Good to know, thanks! And congrats on 16K+ posts... :)
[ONE Original Android Development] Heisenberg:
Wow. Had no idea I was that high, haven't been paying attention lol, I think the last time I actually looked I was up around the 9k mark.

Transmitted via Bacon