yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] majdykhrais:
I installed twrp and superuser (I guess).

According to the thread here http://xdaforums.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727

I have to install the sunshine.apk which I can not because my phone doesn't boot except to the bootloader !

What to do here?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
That isn't an RUU, its kernel source, and not going to be of any help to you.

---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------

Unlocking the bootloader will not allow you to run another version's RUU. I don't know why you think that, but its not correct information.

---------- Post added at 09:45 AM ---------- Previous post was at 09:41 AM ----------

S-off is not the correct path, to do what you want (nor should it be necessary - save yourself $25). As you've figured out, you need a working OS to s-off; but working OS is the reason you want to s-off. So you have a Catch-22 dead end.

If there is no RUU, unlocked bootloader and TWRP are good things to have done. Now restore the 6.13.771.4 stock nandroid backup, using the file and instruction here: http://xdaforums.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
[One (M8) Q&A, Help & Troubleshooting] majdykhrais:
Thanks

Thanks for the info.

I know TWRP and S-OFF won't help me here, but I just wanted to show what I've done.

One question, why to restore 6.13.771.4?

How will I know it's the correct one for my phone, and not a part of the pre-installed corruption?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
This is the main version given in your screenshot in your top post. And you'll see from the stock nandroid collection, that its the correct version number for your CID (carrier version).

Simply put, this is the stock Marshmallow ROM for your M8 version.

Somebody likely made the backup with a working OS. Yours has become damaged or corrupt (most likely) just on your phone. Not every phone with this software number is going to be broken!
[One (M8) Q&A, Help & Troubleshooting] majdykhrais:
a strange thing I noticed,,

on command prompt on my pc, I can't see the new folder containing the unzipped file, while I can see it through the windows-explorer!
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Any particular reason why you are looking in command prompt? Since the steps don't use command prompt (unless you adb push the files).

What version TWRP?

Can you post a screenshot of what the TWRP backup folder structure (on the phone) looks like in Windows Explorer? Not sure what we can be missing here. But its worth a look.

Also, you might try the a Lollipop backup. It should work fine with the MM firmware. Although it may cause an issue with OTA updates (mixing LP ROM with MM firmware), at least it (should) get the phone up and running.
[One (M8) Q&A, Help & Troubleshooting] majdykhrais:
twrp backup

no reason for command prompt, but I just was there and noticed this.

TWRP 2.8.7.0-m8 according to the turorial.

I want to try Lollipop since it was the o.s. when my phone was working properly before I upgrade to 6 and get the wifi problem.

any specific Lollipop version?

I just want a stable version.

thanks
[One (M8) Q&A, Help & Troubleshooting] majdykhrais:
twrp

here's a screen shot

the path on my laptop was the same.
[One (M8) Q&A, Help & Troubleshooting] majdykhrais:
sorry,

I used twrp-2.8.7.0-m8
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
I'm confused about what you are talking about anymore. Did you sell the phone or not?

http://xdaforums.com/showpost.php?p=66116673&postcount=1498

If this is a different phone, you need to give details.

Fastboot getvar all
[Xperia Z4/Z3+ Original Android Development] Olivier:
PREAMBLE

Team Win Recovery Project, or twrp 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.

#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery image
* [B]before[/B] flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

I'll keep this thread short and simple. Want a changelog or a list of features? See teamw.in.

DOWNLOAD

recovery.img

INSTRUCTIONs

fastboot flash recovery < recovery image >

or, if you only want to use it temporarily:

fastboot boot < recovery image >

XDA:DevDB Information

TWRP for Sony Xperia Z3+, Tool/Utility for the Sony Xperia Z4

Contributors

Olivier

Source Code: https://github.com/omnirom/android_kernel_sony_msm

Version Information

Status: Stable

Created 2016-03-28

Last Updated 2016-09-13
[Xperia Z4/Z3+ Original Android Development] MotexT:
Have tested this build - works perfectly, fully stable.
[Xperia Z4/Z3+ Original Android Development] Quarx:
Thanks! but this twrp not work for my dualsim version :( Reboot after few seconds of booting recovery.

I'll check whats wrong soon. But probably need use dsds defconfig.
[Xperia Z4/Z3+ Original Android Development] MotexT:
In this case check out my recovery in Dev sector - works on both single and dual.

MotexT
[Xperia Z4/Z3+ Original Android Development] Olivier:
The ivy defconfig is now unified and can hence be used for both variants as per commit ec71e11 upstream. Can you please test if it works now? twrp-ivy-20160401.img
[Xperia Z4/Z3+ Original Android Development] Quarx:
[MENTION=6004616]MotexT[/MENTION], yep, your version works.

[MENTION=4329876]Olivier[/MENTION], works now :)
[Xperia Z4/Z3+ Original Android Development] LMcR92:
Can you flash this in twrp? Or has it got to be done through fastboot?
[Xperia Z4/Z3+ Original Android Development] Quarx:
[MENTION=4329876]Olivier[/MENTION], there another problem. USB not work at all in twrp. PC not detect any usb device...
[Xperia Z4/Z3+ Original Android Development] yawo76:
USB (0) AND SD CARD (0)

Hi,

Have also detected in TWRP 3.0.1 both the USB and SD Card Storage show 0. Thus only the Internal Storage contents are visible whereas SD Card contents are not. To flash items, I have to copy them from the SD Card onto the Internal storage before booting into recovery. Worth looking into this.

Thanks!
[Xperia Z4/Z3+ Original Android Development] BustedFly:
new version from 08.04.2016 not work for extern sd....
[Xperia Z4/Z3+ Original Android Development] diemadedrei:
Doesn't work for me with 185 build. Just blinks red three times when trying to start, then rebooting.
[Xperia Z4/Z3+ Original Android Development] Olivier:
I don't know what causes this (yet), but this issue seems to be pretty random: Sometimes MTP/ADB work for me, sometimes they don't.

External SD cards should be working now; twrp-ivy-20160408.img - USB OTG is still broken though.

Works for me, have you tried using "fastboot boot"?
[Xperia Z4/Z3+ Original Android Development] diemadedrei:
Tried around a bit now. None of your builds work, neither through boot nor through flash recovery. When using boot the sony screen appears and the LED stays blue and then nothing. I then tried [MENTION=6004616]MotexT[/MENTION]'s build, which works both when booting and flashing for me.
[Xperia Z4/Z3+ Original Android Development] Olivier:
Try this build. It uses the kernel from .185, not the AOSP one like my other builds.
[Xperia Z4/Z3+ Original Android Development] alphaprosper12:
I got soft brick after flashing this recovery , E6533 . 185 firmware
[Xperia Z4/Z3+ Original Android Development] Olivier:
Use the builds from the OP, that one was just a test build for the single SIM variant.
[Xperia Z4/Z3+ Original Android Development] njaya95:
MOD EDIT

There is never a need to quote the whole OP

Can you please tell me how to boot to recovery? I installed the recovery but don't know how to boot into it. I've tried the power+volume up, power+volume down and the power on and then volume up and down. Nothing worked I'm on 6.0
[Xperia Z4/Z3+ Original Android Development] njaya95:
Can you tell me how to boot into recovery?
[Xperia Z4/Z3+ Original Android Development] SprindFinorilar:
How to add it to Z3+?(newly BL unlocked)
[Xperia Z4/Z3+ Original Android Development] Quarx:
Not work after flashing 32.2.A.0.224 :(

White screen with SONY logo and Unknown USB Device (Configuration Descriptor Request Failed) detected.
[Xperia Z4/Z3+ Original Android Development] Olivier:
Alright, I've updated the OP, can you try the new build please? It works for me now.
[Xperia Z4/Z3+ Original Android Development] Quarx:
[MENTION=4329876]Olivier[/MENTION], Sorry for delay. Thanks, it works now :)

Also usb now works too.
[Xperia Z4/Z3+ Original Android Development] krusir:
twrp-3.0.2-0-ivy-20160606.img works. However, it can not get system clock/date. This make the backup has 1970 with some random time. I tried previous 3.0.0-0 (twrp1.img), it can get clock correctly.
[Xperia Z4/Z3+ Original Android Development] jirik152:
Sorry for dumb Q there is no possibility to flash it without unlocked BL right?
[Xperia Z4/Z3+ Original Android Development] Olivier:
I don't see why it shouldn't be compatible with AOSP ROMs - I've flashed several AOSP builds without facing any issues.

Yes, the bootloader needs to be unlocked.
[Xperia Z4/Z3+ Original Android Development] bobboviking:
Mirror?

Anyone having the possibility to upload a temporary mirror for the twrp-files to use until BasketBuild is online again?

BR

Andreas
[Xperia Z4/Z3+ Original Android Development] card0384:
I Need also a mirror for downloading this File - Please Help
[Xperia Z4/Z3+ Original Android Development] Olivier:
I was waiting for BasketBuild to come back, but it seems like that won't happen anytime soon - I've updated the link in the OP, you can download it now.
[Xperia Z4/Z3+ Original Android Development] serrin:
Working with 32.2.A.0.305
[Xperia Z4/Z3+ Original Android Development] batmobile_bang:
I'm unable to flash any AOSP or Lineage ROMs using TWRP recovery, getting error 7. I haven't tried stock based ROMs.

Can someone please share the TWRP recovery which works for flashing AOSP/Lineage ROMs.

Thanks!
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
As far as I know I think it is because some lines are missing default.prop

I've been trying to compile my own TWRP build but was getting strange errors and gave up.
[Xperia Z4/Z3+ Original Android Development] batmobile_bang:
So what is the solution? We have to change the "updater-script" inside the ROM?

No other way?

I even tried that with the AOSP zip but it failed at a further step.
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
Yeah, I think the only way now is to change updater-script and remove the first lines that check the build product name props. Never tried flashing AOSP.
[Xperia Z4/Z3+ Original Android Development] batmobile_bang:
Thank you. I managed to flash Lineage ROM but now I'm unable to boot into TWRP. I even tried re-installing TWRP through fastboot. Any ideas?!! :(
[Xperia Z4/Z3+ Original Android Development] Olivier:
I doubt that - what lines are missing?
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
I haven't exactly checked whether they are physically missing from the file or not, but some environment values are missing. I checked using twrp adb and terminal using getprop. The product name props checked by the first line in updater script are not set. This is the cause of the status 7 errors for people flashing roms using the twrp in this thread.

Maybe it differs depending on how you enter the recovery. For me I flashed this twrp using fastboot to recovery and with twrp enabled kernel which allows volume up key, I press it on orange led to enter twrp.

Also would be nice if it can be built with stock encryption support. I posted a log earlier. It asks for pin but never accepts it.

Thanks so much for building this for us in the first place. I tried to build twrp from cm13 and sonyxperiadev sources before but it failed due to missing targets and I gave up.
[Xperia Z4/Z3+ Original Android Development] pou_gh2:
plz tell me how to flash twrp because when i flash it my phone automatically goes in TWRP and i cant access the rom!
[Xperia Z4/Z3+ Original Android Development] ramonet666:
Any solution for my locked bootloader :( realy need twrp to install:crying:
[Xperia Z4/Z3+ Original Android Development] nosiobadx:
Unlock it using flash tool, there are guides to unlock bootloader.
[Xperia Z4/Z3+ Original Android Development] ramonet666:
I've got bootloader unlock say no is that possible using flashtools?!

---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------

I've got bootloader unlock say no :crying: is that possible using flashtools to install twrp?!?
[Xperia Z4/Z3+ Original Android Development] nosiobadx:
Download recovery.IMG

Connect your phone via USB

In the file you downloaded the recovery open a command window

Reboot your phone to boot loader

Tipe this in the command window

fastboot flash recovery recovery.img
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
It took me a while to understand, but there are no variables missing from this TWRP! I was booting by mistake the TWRP embedded in kernel created by the kernel repack script posted on Z5 forums (the one you enter by normal power on, then waiting for the orange led and then pressing volume up). That one is the one missing setprop variables!

This recovery should be flashed to recovery using fastboot and booted using the normal power on held down with volume down and LED turns purple and enters the recovery and it doesn't give status 7 when flashing.

The issue I did find with this recovery is that it failed to mount my micro SD card (shows as 0 byte size). I am using a 128 GB Samsung EVO+ microsd. The one posted here: https://xdaforums.com/xperia-z4/development/twrp-xperia-z3-fota-recovery-t3346298 (of which the latest version to download is actually here: https://drive.google.com/drive/u/0/folders/0B2_3u92UouM7bE1NcEJWcS1MblE) and which is confusingly named FOTA_twrp.img (but should actually by flashed to recovery in fastboot!) is able to mount the micro sd card when booted with the right method.

As for encryption, I switched it off since at the time I wasn't able to decrypt from TWRP, but I will test again soon when I start playing with LineageOS builds. I am using the other one at the moment.

The custom kernel embedding TWRP (and orange LED behavior) caused a lot of confusion among all users (me included), maybe the phone didn't support volume down + power method before so it was needed, but now not anymore.
[Xperia Z4/Z3+ Original Android Development] DomusX10:
Little info:

I'm on stock MM on my z3plus, with locked bootloader, never unlocked, never rooted (for now).

With my previous Z1C, I've flash recovery without unlock bootloader or flash other kernel, keeping the stock kernel I can use recovery and a custom ROM, I can do this starting from Kit Kat, root with a tool in KK and install recovery from KK. After this, flash KK custom ROM.

Now, with z3plus and MM seems more difficult to do this.

With a locked bootloader, how can I install recovery and root my phone? It's possible? :confused:
[Xperia Z4/Z3+ Original Android Development] alpine101:
Sadly this TWRP appears to have bricked my new e6533. Backed up TA OK, unlocked the bootloader OK, and then installed this with Fastboot using the temporary mode. TWRP started OK, but I noted that while it identified size for partitions, when it came to choosing the back up locations, all the volumes had zero space. When I rebooted into the system, the device got as far as lighting the screen and putting up the Sony logo, but no further. Now a connected PC sees no device on the relevant USB port. The screen can be turned off again with long press on all 3 keys, but I can't get into fast boot or recovery from the keys. The screen doesn't time out.
[Xperia Z4/Z3+ Original Android Development] DiscMan55:
Open the flap that has the sim card tray. There's a tiny button that can be pushed with a thin ballpoint pen. That will kill it.

Then vol up + plug in usb and you'll go back into fastboot. flash a different one.
[Xperia Z4/Z3+ Original Android Development] alpine101:
Thanks. Found the little button. It has the same effect as the long hold on the three switches simultaneously. Three short vibrations and the screen goes off.

However, the PC still no longer sees the device. None of the usual bleeps indicating the PC has noticed it occur, Xperia Companion doesn't see it, and if I run the fastboot flash command says it's waiting for a device, including when I connect the phone while pressing vol up. The led lights up blue for a second or two, then changes to red, then, continuing to hold power up, it repeats that cycle.

The annoying thing is that when I got into TWRP (and I made no changes while in it), I'd done so using the 'fastboot boot recovery.img' command. I intentionally did not include 'flash' since I've always understood this ensures no flash takes place and the image will just exist in ram and vanish back to the original state when the phone is rebooted.

The phone came with the current HK customisation, 1295-0389_R10C.

I fear the next, and last resort step, is to unglue the back and see if disconnecting the battery will have any effect.

EDIT: Well....The problem was in fact the windows 10 machine which, even though it had worked and run adb and fastboot for me in the same session, had decided it didn't want to know the phone any more.

I've now run the fastboot on another machine using an old adb installation I've used for other phones, and successfully installed the FOTA_twrp image from the other thread. TWRP is running now, sees the memory and is currently running a backup for me. I've yet to find out if I can boot the OS proper...
[Xperia Z4/Z3+ Original Android Development] ramonet666:
Unlock bootloader says NO :(
[Xperia Z4/Z3+ Original Android Development] peshmarga:
hello please can you tell me whats wrong i cant flash recovery img via fastboot whats the problem ??

and says

(

target reported max download size of 536870912 bytes

sending 'recovery' (15384 KB)...

FAILED (data transfer failure (Too many links))

finished. total time: 0.020s )
[Xperia Z4/Z3+ Original Android Development] Sylus27:
Use CMD instead
[Xperia Z4/Z3+ Original Android Development] lkjsoiuew:
Does it work now? Which is the other thread?

... Solution: install lineageOS with the temporary booted twrp ... after that I could flash this recovery.img and boot to it, then flash SuperSU.2.82....zip
[Xperia Z4/Z3+ Original Android Development] ridwanxperia:
twrp for lineage os

support lineageos ?
[Xperia Z4/Z3+ Original Android Development] lkjsoiuew:
twrp doesn't find anything with external sdcard installed. is there a newer version?
[Xperia Z4/Z3+ Original Android Development] othox:
can not download
[Xperia Z4/Z3+ Original Android Development] ridwanxperia:
help i need root xeperia Z3+ dsds Os Lolipop

please answer :(
[Xperia Z4/Z3+ Original Android Development] vuvankhangk48:
: tốt:: tốt:: tốt:
[LG G Stylo Questions & Answers] superstimpy:
1. Rooted phone 2 months ago

2. Factory reset because it kept restarting.

3. After factory reset the phone wouldn't go past the lgsetup.

4. Used the wrong img file and bricked phone.

5. Fixed with the right img file. (Always check md5!)

6. After I got everything working I updated to MM.

7. Since MM update I get the following error "Unfortunately, Google Play Store has stopped." and Mobile ID is stuck on download.

Pretty sure I broke it by updating. Any help is greatly appreciated! :)
[LG G Stylo Questions & Answers] raffle2005:
The same thing happened to me

All u have to do is a factory reset on the device itself, along with erasing SD. For some reason when we updated to MM6.0 our phones already had the Google play Services updated so there was NO update available when u tried. I couldnt even get a text out because of that frikken message popping up. Basically it realigns its updates when u reset it thru the handset. Let me know if it helps.
[Sprint Samsung Galaxy Note 3] MSIgs60GhostPro:
Hello.

I have searched the forums and I do not see this question. I have googled and see this answered all over the place. Some people say you can and some people say that you can't. Something about flash locked bootloader when 5.0 is installed.

I absolutely love my white note 3. I have had it for years and just replaced the charger port. I wanted another one for my business line. I can't find one that hasn't been updated because that is exactly what I want. Before I flash this one and mess it up I want to check with you guys officially.

This is what I have now and want on my second phone:

N900PVPUBMJ4

N900P.12

SM-N900P

4.3

N900PVPUBMJ4

JSS15J.N900PVPUBMJ4

I know how to flash this with odin and have done so many times. But I have always been on 4.3 and never upgraded. I just disable KNOX and rename all the update files so it leaves me alone.

This is the note 3 that I bought:

N900PVPUEOH1

N900P.12

SM-900P

N900PVPUEOH1

LRX21V.N900PVPUEOH1

SEPF_SM-N900P_5.0_0009

MDF V1.0 RELEASE 4

VPN V1.4 RELEASE 4.1

KNOX 2.3

... [ETC all the way down]

My question is this possible at all? What is the risk? What are my options? I really want to have a nicely rooted note 3 just like my old one.

If it is not possible can I root this Lolipop?

What I was going to do was just flash the note 3 I just got in ODIN like I always do with my old one, but I am afraid that I am going to brick it or its going to get stuck on the sprint logo because the bootloader can't be downgrading.

Well please let me know.

Thank you.
[Sprint Samsung Galaxy Note 3] MSIgs60GhostPro:
Okay. I tried something different. I searched downgrade within Q/A and did find some things stating that it is impossible. This really frustrates me. What are the odds of me finding a note 3 that is not already upgraded.

So now what are my options?

I really enjoy my rooted other note 3 for exposed installer, wifi-tether, and a possible ad block.

Can I do all this with Lolipop? Is it easy to root? Or should I just return this phone?

Let me know.
[Sprint Samsung Galaxy Note 3] MSIgs60GhostPro:
This is what gave me hope.

http://xdaforums.com/galaxy-note-3/development/root-guide-note-3-lte-sm-n9005-lollipop-t3093183

Is this not true? Special phone or something? I see it is for the International Version but it says Lollipop 5.0 and its downgraded. If its impossible how did he do it?

If all is impossible. If I root Sprint Note 3 on Lollipop will I trip Knox?
[Sprint Samsung Galaxy Note 3] MSIgs60GhostPro:
Question here.

If I can't downgrade. Can I just flash a rooted "one click" on this phone and run that version of Lollipop on this phone or will that create problems as well? This will probably trip Knox as well right?

I think someone said that no matter what you do to root or re-flash ROMS now you will trip Know. That correct?
[Sprint Samsung Galaxy Note 3] MSIgs60GhostPro:
I am thinking about trying KingRoot.

I used Kingo Root a lot before and never tripped Knox. This one however seems to be support by XDA and should be better.

Do you think I could use this without tripping Knox?

http://xdaforums.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461

Its not on its supported device list through. So does that mean it will probably trip Knox?
[Sprint Samsung Galaxy Note 3] MSIgs60GhostPro:
Why isn't anyone helping me?
[Sprint Samsung Galaxy Note 3] rbeavers:
All your questions Have been answered search the forums.
[Sprint Samsung Galaxy Note 3] halfcalf1:
sounds like s\he has been trying but not having luck. Your comment isnt helpful, why reply? Personally I have trouble finding answers in the forums especially when I am not using just the right search words. Its not always lack of trying.

Just food for thought.

Joe