yashsingh1/xdaforums huggingface dataset:
[G2 Q&A, Help & Troubleshooting] SuperBrolySSJ:
I see on the cm page the Verizon variant's cm13 nightlies are from March. Does that mean CM has officially stopped development for the vs980?
[G2 Q&A, Help & Troubleshooting] SuperBrolySSJ:
:| is someone going to answer????????
[G2 Q&A, Help & Troubleshooting] wsw1640:
Yes they did. There were issues with the RIL I believe.

Sent from my Note5
[G2 Q&A, Help & Troubleshooting] SuperBrolySSJ:
So that means if we get CM14, it will be unofficially? COULD CM resume the development for the Verizon g2 if they wanted to?
[G2 Q&A, Help & Troubleshooting] wsw1640:
Yes they could start it back up but it's doubtful since it's such an old device.

Sent from my Note5
[Sony Xperia C4 Guides, News, & Discussion] gsser:
Please lock the thread.
[Sony Xperia C4 Guides, News, & Discussion] Anh Tuấn:
Thank your post, but i don't understand this. Please detail + img?
[Sony Xperia C4 Guides, News, & Discussion] mmuak6:
relock the bootloader

please make a video on it i have sony xperia c4 e5333 i remove the root but how to relock the bootloader i dont have backup
[Sony Xperia C4 Guides, News, & Discussion] gsser:
Sorry guys i cant make a video nor take ss. Cause i dont have a pc with me and my school started..

BUT if you be able to unroot the device and restore stock system, i can help repairing it with team viewer
[Sony Xperia C4 Guides, News, & Discussion] mmuak6:
How to take untouched backup from the Xperia c4

I have 2 devices one have unlocked bootloader and the other device have locked bootloader so how to take a untouched backup from locked bootloader device please give me your contact information to contact you via email or team viewer my email is: mmuak6@gmail.com please help me
[Sony Xperia C4 Guides, News, & Discussion] okolyigit:
I think this steps works. Am I right?[MENTION=5021225]gsser[/MENTION]

device1: locked bootloader

device2: unlocked bootloader

- unlock bootloader device1

- install TWRP

- take a backup (don't flash supersu)

- restore backup (don't open device)

- repair device1 with xperia companion

- copy backup files from device1 to device2

- restore backup with TWRP to device2 (don't open device)

- repair device2 with xperia companion

- done

You should have 2 updated devices after this steps. Good luck :victory:

And please share us your backup :o
[Sony Xperia C4 Guides, News, & Discussion] mmuak6:
Both devices model is different

Both devices model is different device1 is:e5333 and the device2 is:e5353 so what I want to do it
[Sony Xperia C4 Guides, News, & Discussion] Anh Tuấn:
What version flashtool support c4, c5? This brick devices??
[Sony Xperia C4 Guides, News, & Discussion] gsser:
I use latest one and didnt have any problem
[Sony Xperia C4 Guides, News, & Discussion] darksoul79:
versión flashtool c4 e5306

Can you explain me the process complete about flashing marshmalow on c4 single because i'm afraid for brick my Xperia...there are too many comments about the latest versión of flashtool brick those model.. Could be make this favor...thx
[Sony Xperia C4 Guides, News, & Discussion] aidy.lucas:
Use the latest version of flashtool in simple mode only and select YES if asked for a fsc script. And wipe the user data, cache ect to get the best results if in doubt wait for the update to arrive in xperia companion latest version flashtool works on the mediatek powered xa just fine
[Sony Xperia C4 Guides, News, & Discussion] darksoul79:
So no problem...flash e5306 with 0.22....versión

Enviado desde mi E5306 mediante Tapatalk
[Sony Xperia C4 Guides, News, & Discussion] aidy.lucas:
Flashed my mediatek xa using it last week just fine only use it in simple mode and select YES if asked for a fsc script and it should be ok(I accept no responsibility if it turns it into a paperweight)

It's supposed to be impossible to brick a device if the above is done
[Sony Xperia C4 Guides, News, & Discussion] mmuak6:
Finally finally i relock the bootloader without backup

Finally finally i relock the bootloader

Make sure you have 80% charged your battery

1)Go to supersu app then go to setting in super su scrool down you will see the unroot option click on it now your device is unrooted

Power off your device and then

2)go to twrp recovery then go into wipe format data and factory reset and power of your mobile dont open it

3)go into flashtool the latest version is not working so please download this version i am giving this link (https://www.google.co.in/url?sa=t&s..._tG8o6zY_RcEP0qEw&sig2=v7komLSRiQR9iWP7ChHJpg ) so please go to this link and download this version of flashtool 0.9.19.10 and just install it normally then in flashtool click on BLU and connet your phone in flash mode the relock screen is appear click on relock when relock is completed disconnect your device (don't open it)

Now finally 4) step go to Xperia companian and go to repair software and its ask for accept terms and other stuff make sureyou have fast Internet connection because its download the firmware when it ask for connect connect in flash mode and be patience after that you are running in marshmallow rom make sure you have 80% charged your battery and this method is working 100% if its work for you dont forget to hit thanks button
[Sony Xperia C4 Guides, News, & Discussion] Anh Tuấn:
It realy :D i waiting along time :D
[Sony Xperia C4 Guides, News, & Discussion] mmuak6:
Yes its really work
[Sony Xperia C4 Guides, News, & Discussion] gsser:
Its just the same as i said, version selection depends on you and system backup required if you removed any of the system apps.

I couldnt relock until i restored
[Sony Xperia C4 Guides, News, & Discussion] mmuak6:
But this method without restore the backup iys work for me
[Sony Xperia C4 Guides, News, & Discussion] gsser:
It must be cause of not modified system, most of the root users decide to remove apps to boost battery life
[Sony Xperia C4 Guides, News, & Discussion] okolyigit:
Thanks bro :good:
[Sony Xperia C4 Guides, News, & Discussion] mmuak6:
This method is work for you?

Please reply
[Sony Xperia C4 Guides, News, & Discussion] okolyigit:
Yes. I relock bootloader, repair phone with Xperia companion and flash 6.0 ftf :D
[Sony Xperia C4 Guides, News, & Discussion] darksoul79:
Could you please tell me the steps by steps for flash c4 with flashtool and wich versión do you using...

PD: sorry my poor english

Enviado desde mi E5306 mediante Tapatalk
[Sony Xperia C4 Guides, News, & Discussion] okolyigit:
I followed this steps. Flashtool version 0.9.19.10. I created ftf file via xperiafirm and flashed it.
[Sony Xperia C4 Guides, News, & Discussion] Anh Tuấn:
My devices is C4 e5333. I'm unlock bootloader and root (5.0.2)

I lost DRM key when unlock and have no backup DRM key, i will unroot, relock bootloader and up to MM via Sony Companion

... So, how to restore DRM key?

Please help, thank all.
[Sony Xperia C4 Guides, News, & Discussion] aidy.lucas:
Your drm keys are gone forever unfortunately which means no bravia engine, x-reality, or low light camera performance, mirrorlink and probably a few Sony apps compared to a stock xperia and don't try using anyone else's unless you want a nice shiny Sony permanent paperweight. One reason my xa is still stock unrooted for almost 3mths no way to back up the drm/ta keys at all on the x range.
[Sony Xperia C4 Guides, News, & Discussion] dzambranoo:
[IMG="Flashtool error while flashing E5506 locked BL and unrooted"]https://scontent.feoh2-1.fna.fbcdn.net/v/t1.0-9/14479546_917881685012416_2838082728557737226_n.jpg?oh=0d22fffdb4b750fd3419744248b3a436&oe=586A07DD[/IMG]

Can someone help me why this happens while flashing E5506 locked BL and unrooted? FLASHTOOL VERSION: 0.9.19.2
[Sony Xperia C4 Guides, News, & Discussion] ka_za:
can you found any solution? i have same problem.
[Sony Xperia C4 Guides, News, & Discussion] gsser:
Corrupt ftf file.

Dont remove anything from bundle, at the flash section just dont move in simlock cust reset. When you dl from xperifirm add all files into ftf
[Sony Xperia C4 Guides, News, & Discussion] Loloflat6:
Thank's !!!:good:

I'st the good right way !

Successefuly done and update trough Xperia compagnion to MM 6.0.0 on my 5533 and debranded too !

Good job
[Sony Xperia C4 Guides, News, & Discussion] bywarlord:
I have C4 unlocked bl with marshmallow and with no root what should I do I can't relock with flashtool blu function,it keep saying impossible to unlock this device but it already unlocked :D Any suggest for relock my device?
[Sony Xperia C4 Guides, News, & Discussion] xdaroussy:
What do you mean by simple mode?

Simple mode? How do I do that?
[Sony Xperia C4 Guides, News, & Discussion] xshinichix:
thanks for the guide. now running marshmallow :)
[Sony Xperia C4 Guides, News, & Discussion] theArkhamKnight:
Same for me too flashtool keep saying ' INFO - Your phone bootloader cannot be officially unlocked' but it's already unlocked :D i am trying to relock it,any suggestions ?
[Sony Xperia C4 Guides, News, & Discussion] lvluat:
Thanks so much! It worked for me:

* C5 Ultra Dual (E5563) with custom ROM, rooted, unlocked bootloader.

* Flashtool 0.9.19.8

* No backups or ROMs needed.

* Steps i did:

1/ Open supersu => unroot

2/ Goto TWRP => Factory reset => power off

3/ Open the flashtool, hold down the Down Volume key and connect USB cable to the phone.

4/ Click on BLU button on the Flashtool => Relock => Ok

5/ Power off the phone.

6/ Open Xperia Companion => Software Repair => Check "My device cannot be detected..." => click Next => click Xperia .. phone => Next => check "Yes, I know.." => Next, wait a moment and Xperia Companion prompt to connect the phone (in flash mode) => Hold down the Down Volume key and connect USB cable => Next. Wait for a long time (about 15 minutes) => the phone auto restart and the new ROM (29.2.B.0.129) is updated!!!
[Sony Xperia C4 Guides, News, & Discussion] Na007:
half year before I have unsuccessfully tried to update under windows 10 I think driver problem.

there is now an opportunity to correct this problem Sony С5 E5303.

It not start firmware when usb connectd led red color.

windows 7 64 bit does not recognize it. device code in device manager is USB\VID_0FCE&PID_D1A0&REV_0100.

is there any possibility now to correct this problrm and run again this phone ?
[Sony Xperia C4 Guides, News, & Discussion] strongst:
Thread closed per OP's request.

strongst

Forum Moderator
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
reserved for [MENTION=1162986]Captain_Throwback[/MENTION]
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Oops
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
files are in the download section, the posts need some editing, bug gonna be a bit busy tomorrow

so enjoy ;)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] azZA_09:
Ok,ok,you will say that im noob,but i flashed both files,flash the RR ROM,but the multirom menu doesnt show and it boots me directly to primary rom
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
That's not a "bug report" ;)

Please provide detailed information, and logs... BTW, I didnt add the advanced kernel logging feature "by mistake", it's so you can get "easier" logs... but if those exist, then you still need to pull a kmsg

adb pull /sys/fs/pstore/console-ramoops

No boot menu, normally means that trampoline (if it's in the above log), wasnt able to mount data... or it's not even there
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] azZA_09:
Sorry dude,Im at work atm and I think too slow :)). I will provide logs tomorrow,but maybe somebosy can provide them since then. Once again,great job and im sure you will fix every problem
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
open a terminal emulator on your phone, and

cat /sys/fs/pstore/console-ramoops | grep tramp

then you'll see if trampoline is even in there ;)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] azZA_09:
It shows only the # after that
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] jsaxon2:
Download links are not working. :(
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
then probably the log is way after trampoline & multirom, so you need to enable "kernel logging"... I didnt add that by mistake :p
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
http://xdaforums.com/devdb/project/?id=17079#downloads

Tab isn't showing up for me, but that link should work.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
They're supposed to be here

If you can't access them, I've uploaded them to AFH as well
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] jsaxon2:
Got it installed and booted up cm13 as secondary. Working good so far. Thanks for this. I'm back on Viper running from primary.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
hmm is that a complaint? ... sounds rather positive, so i'm unsure. i usually only hear complaints :p

Well, if it's not, thanks for reporting back :good:

I currently have an old version of Viper10 as primary / daily

and as secondaries:

ice-2.1.1_PERFUME_UHL_M60_SENSE80GP_HTC_Europe_1.90.401.3

BeanStalk-6.20-20160905-pme

cm-13.0-20160915-UNOFFICIAL-pme

and some other weird stuff :D
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] jsaxon2:
Lol, not a complaint, it's a compliment. You have done excellent work. Just wanted to report that it is working. I'm too tired to mess with it anymore, but awesome that I can test CM builds and get right back to my daily driver.

Job well done.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Thank you, I do enjoy positive feedback, Hope you enjoy it :)

as well as comments, thoughts and ideas.

@ all, If something is wrong, please be as descriptive as possible... please no "it doesn't work" posts.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] janarp:
okay.. that means I have to partition SD card... damn i dont want to make partition to my SD card... :laugh:
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] 5m4r7ph0n36uru:
I guess it does :laugh:
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
I'm still looking into it, but it may never work especially due to HTCs custom texfat implementation.

But in either case, if you do really want to use MultiROM, then an ext4 partition is highly recommended, because exfat/fat has limitations, such as having to set the size of the partitions (system, data, cache) from the start, and not easily changeable. So if you end up needing just 1 little byte more in your data partition... poof, it worn't work.

(I also find it slower)

You can always flash to internal storage, if you don't want to repartition your sdcard ;)

EDIT: the "how to repartition" is in the FAQs
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] janarp:
thanks...
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] MrRob0t:
Just getting around to flashing RC2, thank you again for the awesome job! :good:

Not a complaint, but an issue (or maybe let's say, mistake?) most certainly caused by my inexperience. (this is before flashing RC2)

I have latest Viper ROM on my internal, and had stock Verizon ROM + Leedroid ROM as secondaries (all 3 on internal, not sure if it matters?).

I did a dirty flash of Viper (in the main menu of TWRP) and when I rebooted I noticed no multirom menu, so after Viper booted up I re-flashed the multirom-20160920-v33b-UNOFFICIAL-pme.zip, which did bring back the menu, but when I tried to boot into either secondary ROM I was stuck on the HTC Splash screen with the red warning text. From here I figured I would just delete the 2 secondary ROMs (as I have nandroids of them backed up on the PC anyway) and upgrade to RC2.

Any ideas where I went wrong for future reference? [MENTION=2605798]nkk71[/MENTION]

Thank you in advanced!
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Yeah, I know the issue, it's due to the "uninjected" boot.img doing a restorecon_recursive.

Please do the following:

After

making sure your primary boot.img is now properly injected

In TWRP, go to the MultiROM section -> List ROMs -> select the ROM -> run a restorecon on it.

then it should boot up fine.

EDIT: btw, when you dirty flashed to primary, I'm guessing you let AROMA reboot the device... this will have prevented injection (unless you disabled) it, which caused the restorecon to mess up all secondaries.

So you need to "list" and "restorecon" every secondary you have
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] MrRob0t:
Thank you kindly for the fast response!

ok, sorry, I'm a bit new to all this so please forgive me being a little thick on some parts. :)

Technically the issue is because I let aroma directly reboot, and if I un-check it next time, this will let the primary boot.img inject properly in TWRP, and I won't run into this?

but.. just in-case I do forget, (this is the 1 step I'm a little bit confused on) I need to make sure the primary boot.img is properly injected (how do I do this? just do another dirty flash on my primary again and remember to un-check letting aroma reboot?) then just "MultiROM section -> List ROMs -> select the ROM -> run a restorecon"

I appreciate you putting up with my questions.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Just updated the FAQ (roughly), I'll make it clearer tomorrow.

To make a long story short (kinda late over here :o):

An uninjected boot.img will do what it's supposed to do and "fix permissions" on your data partitions (as now mentioned in the FAQs at the end).

.

A MultiROM injected boot.img adds exceptions so that the "fix permissions" excludes multirom folders from being affected.

(Also, it seems, a major cause of headaches it seems across the MultiROM community, as they continue trying to flash Android N ROMs)

Back to AROMA: By rebooting from AROMA Installer, you're basically bypassing anything else TWRP (and in this case MultiROM) wants to do after the flash is complete.

Since TWRP (or in this case MultiROM) is unable to continue its job, you end up with an uninjected boot.img, which does not have the above exclusions... on a secondary ROM flash this would be less problematic as there are certain checks in place to do that in case it wasn't done; however those checks are not possible for a primary flash.

There are other "side effects" you may encounter from a AROMA Installer reboot, such as the infamous boot.img truncation, and possibly others. As well as the restoration (if needed of the original ROM)... ROM's larger than the ones that can fit in tmp (the ones where you see "preparing Zip", get modified, and become unusable for non MultiROM secondary flashing, i won't bore you with the details)

If on the other hand TWRP is allowed to continue it's job, it will properly inject the boot.img as well as restore the rom.zip to it's original format... you'll see it in the progress, and yes it does take a while unpacking and repacking a 2GB rom.zip.

So I highly recommend

not

to allow AROMA Installer to reboot the device. IMHO, let TWRP finish it's job completely, then reboot the device.

(I'll add that to the OP as well)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Go to bed
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
I must be sleeptalking again :eek: (all that stuff "looks" so simple in my mind, but difficult to verbalize it properly)

Still need to fix lockscreen though :o :D:D
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Haldi4803:
Uhm, i have a question... or more like multiples ^^

The OTA for 709 region TW came this week. For the first time i've been unable to START the update. I've flashed the stock system_image, so that's not the issue. Does MultiROM install trigger this DM_verity thingy? Or is it because of the modified boot.img as i do get the red warning lable?

I've Downloaded OTAs with Ex Kernel installed (IIRC....) and Systemless SU.

Well... thats not really an issue :) downloaded the OTA.zip directly from HTC's server and installed it (reflashed stock recovery first.) . System verified and installed. no issue.

Flashed new (BETA) TWRP MR recovery, flashed Multirom.zip and installed the APK. Multirom works again :) made a NEW (copy first to internal) Multirom. works. Old Beanstalk also works.

But the Old copy from Stock rom does not work. It does boot, i can see the boot animation, but then reboots. My guess is: It's not related to Multirom but an incompatibility with the Base/partitioning or anything else as i can see the HTC bootanimation. Well... doesn't matter anyway, i don't need that anymore it's getting deleted :)

P.S On another note... i can create Backups of my secondary ROMs... .but how do i restore such a Backup on my secondary ROM ? -.o
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
uhm, what's the question :o

Kinda lost track there, what was what, what didn't work (since it seems at one point you "made" it work)

Can you make it a little bit more clear, what the problem(s) and error(s) were?

Also there's a logging feature in twrp->mrom->settings if you want to enable that to get some logs.

As for the "restore backup", well currently there isn't, you can "Install from backup"... not sure why you would need that option, but I guess it could it be added, if need be... maybe explain, under what circumstance you'd need it.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
On a separate point, I'd like some input from you guys.

As you know, all secondary ROMs currently "think" they're unencrypted devices... whether the device is or is not actually encrypted (only the primary ROM would know that).

What would you think about having all secondary ROMs "think" they are encrypted (whether the device is or is not)?

Any ideas, feedback, thoughts, on whether this would be a good thing or a bad thing?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Black_Eyes:
Really encrypted or just a placebo?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Secondaries, cannot be encrypted (and should not, as in the FAQs).

They do not have a separate partition to be encrypted, so yeah, kind of placebo.... but it will also not allow you to press the "encrypt this device" button, and who knows what happens then.

I never tried, so I wouldn't know either.

I also have no idea, how that would affect, the extra partition (which stores you decryption hash), etc.... which is why I'm bouncing the idea in here ;)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] codeglitch:
I've been kidding arround with multi rom and some roms, last night i installed a secondary rom with no problems, but after i went back to regular twrp and wiped internal/data/cache/dalvik but i think the secondary rom space is still missing, could that be? do I have to resize partition to get that secondary rom size back?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
I'm assuming you mean Internal Storage?

For ROMs stored on Internal Storage, they would have been deleted when you wiped "internal", but that is kinda overkill, to get rid of ROMs, you could have just TWRP -> MultiROM section -> List ROMs -> select the ROM you dont want -> Delete

and if you want to get rid of multirom completely you should just flash the uninstaller, as mentioned in the OP, it's here http://xdaforums.com/devdb/project/dl/?id=20467
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] codeglitch:
I see, i must be confused than, it says 24G total storage, i was thinking it was a little more, thanks :P
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Mine has 0.5 more :p:silly:
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] codeglitch:
ah mine has the same, i think i got it now, Settings > Storage > shows a total of 32G, my problem was i was checking the total on the MTP connection to my PC, which only shows the the Data partition which is the said 24G, I think the TWRP also shows only the data partition free space because i was getting the same number there.

Also from what i used, MultiRom looks very stable, thank you!