yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] gostela:
Hi,

I have the problem that my S4 Mini is not booting to LineageOS anymore. It just shows the booting screen for hours.

So I tried to do a wipe and data format befor installing lineageOS again.

When I try to do the wipe o data format I recieve the following error:

"Failed to mount /efs (invalid arguement)

Failed to mount /cache (invalid arguement)

Error opening /data [and then many errors on files with /data] (I/O error)"

Any idea whats wrong and what I can do to get my phone running again?
[Galaxy S 4 Mini Android Development] mielletseed:
Seems you partition table is corrupted or you emmc (internal memory) died ....

You could try to repair the partitions from twrp but I think it's no good sign that /efs has problems. Do you have an backup of /efs partition?

Maybe you could try to flash a repair firmware with repartition option in ODIN. Therefor you would need a PIT file ...
[Galaxy S 4 Mini Android Development] gostela:
Thanks for your answer. Doesn't sound good.

Unfortunately I don't have a backup of /efs partition.

What would I need to do to flash a repair firmware with repartition option?
[Galaxy S 4 Mini Android Development] bierma32:
Go back and flash Stock Firmware.

Download a 4 part FW, under CSC image you find the PIT.file.

If after flashing all OK, install TWRP and create a Backup of efs partion.
[Galaxy S 4 Mini Android Development] gerhart.steiner:
[QUOTE

QUICK ODIN HOWTO : assuming that your Odin installation for S4 mini is OK (thanks [MENTION=3044346]arco68[/MENTION] for this) !

Turn your device OFF.

Press AND hold 'PWR' + 'VOL. DOWN' + 'HOME' buttons.

Connect your USB cable and press 'VOL. UP' button to confirm that you want to enter into DL mode.

Start Odin, uncheck "F. Reset Time", and then click 'AP' button.

Select my 'recovery.tar.md5' file that you previously extracted from my 7zip archive and press 'Start' button. The phone will reboot when finished.

When the phone begins to vibrate just before rebooting : IMMEDIATELY press and hold 'VOL. UP' + 'HOME' buttons to boot straightly into your new recovery. <= THIS LAST STEP IS NEEDED ONLY ON SOME S4 MINI DEVICES TO ACHIEVE THE FLASHING PROCESS SUCCESSFULLY.

[/QUOTE]

My S4 Mini (serranoltexx) won't work that way :(

Any idea?
[Galaxy S 4 Mini Android Development] MikeT.:
-deleted, wrong way-
[Galaxy S 4 Mini Android Development] sunshineweb:
gt-i9195i always download modus

hi,

a problem I had

after installing TWRP with odin I could not reach the recovery. it always startet in download modus. I could recover the original recovery, and it worked fine.

but to get twrp, I had to download the 64 bit version for my gt-i9195i.

https://twrp.me/samsung/samsunggalaxys4mini64bit.html

I couldn't find the link in this thread, so here it is ;)

hope it's helpful to someone ;)
[Galaxy S 4 Mini Android Development] capsuleboy:
fail

s4 mini i9190 , I tried this recovery using Odin. didnt work, GET PIT FOR MAPPING

probably my phone is broken, it only starts in download mode.
[Galaxy S 4 Mini Android Development] kayseri_inces:
woww

thank yu nce metod
[Galaxy S 4 Mini Android Development] mrrocketdog:
:good:
[Galaxy S 4 Mini Android Development] parthabhatta:
Flashed. Zip through existing philz touch recovery successfully. But recovery did not boot. The screen showed "RECOVERY BOOTING" in blue but never booted. It never booted and ultimately I had to take out batteries and wait for few minutes for normal booting. I then ODIN flashed PHILZ TOUCH again to bring back RECOVERY.
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay !

Please flash my TWRP .tar.md5 file through Odin (try first the I9190 version, then the I9195 one if the previous one fails by ny manner...)

FYI and as stated in the OP, if you get a failure after having flashed my TWRP .zip files with another recovery, then a good habit is to try again with Odin... ;)

It would be interesting to have feedback about my current TWRP builds and I9192...

Let me know if this helps...,

Regards

Tapatalked from my TF701T
[Galaxy S 4 Mini Android Development] parthabhatta:
OK I'll try at my home. Presently I am at office.
[Galaxy S 4 Mini Android Development] smartxdev:
Hi!

Are the Stable branches in the first post are updated (since it's dated before your post or the DEV branches...) and are indeed supposed to be stable?

Going too try them soon.

In the next few days I believe new CM Snapshot release will be out. So I'll do all the flashing (your recovery, f4k kernel, CM itself).
[Galaxy S 4 Mini Android Development] parthabhatta:
It worked. :laugh::good:

The I9190 version worked. It failed first time on flashing by ODIN. On reflashing by ODIN for second time it worked.

I didnt try the I9195 version as there was no need.

Now can you please advise why CWM flashing didn't or does not work?
[Galaxy S 4 Mini Android Development] ne0zone75:
Happy news that it worked ! :cool: :D It is far beyond my knowledge to explain exactly to you why Odin is 'more' reliable than flashing a recovery from another recovery BUT it is a fact ! My guess is that it has certainly to deal with the 'lower flashing level' which is used by Odin vs. the one used by recoveries...

My best regards !

Tapatalked from my TF701T
[Galaxy S 4 Mini Android Development] ne0zone75:
Good evening,

When i released the most up to date builds for DEV branches, i've also built the STABLE ones BUT i've not released them because of a lack of freetime. Besides, current STABLE branches will be replaced in a few moments by the STABLE builds mentionned just above... in around one hour !

BTW these STABLE builds should really be stable as it is always what i try to achieve with those AND both .zip files will be signed too ! (two 7zipped .tar.md5 files in addition...) :good:

Stay tuned !

Tapatalked from my TF701T

EDIT : Post #1 is now updated ! ALL AVAILABLE BUILDS are those i've built on 2014-08-31 :cowboy: :cool: :good:
[Galaxy S 4 Mini Android Development] smartxdev:
Thanks!

No pressure anyway, "when it's ready it's ready" is always the way :)

Just wanted to clear the things out.

And I'll stay tuned indeed, as always ;)
[Galaxy S 4 Mini Android Development] ne0zone75:
No worries..., i was about to forget to do it : it is done ! :good:

Nice evening to you !
[Galaxy S 4 Mini Android Development] ne0zone75:
Good morning,

I have to post this BIG RED WARNING :

-> for every current build of each branch AND for each device (ALL CURRENT FILES) : crypto is not working for stock SAMSUNG ROM... :confused: (of course only the STABLE branch is usable with it)

-> they should work with custom ROMs because i've double checked my build flags, and these ones were previously working with those... :fingers-crossed: (STABLE branch at least)

Anyway, please report back if you are having any issue with crypto (stock or AOSP based) without forgetting to mention the ROM you are using... thank you !

Very sorry for the inconvenience !

Tapatalked from my TF701T

EDIT : I think that crypto issue is now history for both stock / AOSP based ROMs... :good: :fingers-crossed: I am currently rebuilding ALL builds of each branch for each devices (8 files : .zip will be signed) AND IT IS 2.8.0.0 !!! :highfive: :cool: :good:
[Galaxy S 4 Mini Android Development] smartxdev:
Thanks for the warning!

Crypto is indeed important for some of us here...

I hope the issue will be sorted out, and of course looking forward for 2.8.0.0 :good: (and please link a changelog once its out :) )
[Galaxy S 4 Mini Android Development] ne0zone75:
Hi,

I asked for assistance to [MENTION=912474]Dees_Troy[/MENTION] (TWRP DEV thread and PM) because there is something i really do not understand : i used my usual TWRP build flags to compile 2.8.0.0 and this test build is able to decrypt /data of AOSP based ROMs BUT is not able to do the same for stock ROMs... :confused:

Anyway, i will take my time to try to make it work for both cases...

Of course, i will post the 2.8.0.0 changelog as soon as it is available from TeamWin website ;)

Kind regards
[Galaxy S 4 Mini Android Development] silentscreamz:
SCH-I435

Hi and thx for all the hard work you put into your recoveries but I do have one request. I do not see any recoveries for the SCH-I435 (serranoltevzw) model, I'd like to know if you do have one and I am just missing it or if you could build one for the model?
[Galaxy S 4 Mini Android Development] ne0zone75:
Well if your device do have the same SoC than GT-I9195 or GT-I9190, then you may try to flash one of my TWRP build which is the most close to your device AND of course it will be at your own risk !

Anyway, i am really sorry but i have absolutely no time to build TWRP for one S4 mini variant more... AND AFAIK only serranoltexx and serrano3gxx are fully supported by CyanogenMod...

Thank you for your understanding !
[Galaxy S 4 Mini Android Development] ne0zone75:
TWRP 2.8.0.0 for S4 mini will be released early next week !

Hi all,

I did not manage to get encryption working for both stock & AOSP based ROMs : it is not working for stock (i am currently awaiting [MENTION=912474]Dees_Troy[/MENTION] answer about it) BUT it should work for AOSP... to be confirmed... :confused:

Honestly, i do have no idea of what is going wrong with it !

Volunteers are wanted for testing out the new releases that will come early this week : just post a '+1' in this thread, thank you ! (i will send you then a Google Drive download link over PM)

Now, a few questions :

-> is any of you interested in ALL F2FS ?

-> is any of you is interested in encryption support from recovery for use with stock ROM ?

Nice sunday !
[Galaxy S 4 Mini Android Development] hansare:
Before I flashed TWRP I used PhilzTouch on my I9195.

No problems.

Switching off or rebooting took about 1 second and reboot in recovery worked always good and flashing zips was never a problem.

For a try I flashed TWRP from recovery.

After that my phone couldn't reboot in recovery (showing that the phone was looking for recovery, didn't find and then restarted).

Normal reboot worked good and the rest of the phone worked fine.

Except ...

... from now on switch off or rebooting takes about 9(!) seconds.

It seems the phone is searching for something it can't find.

Because of these failures I flashed again with Odin.

After that my phone was sometimes able to restart in recovery (but most of the times not).

Switch off / reboot still took about 9 seconds.

I went back to PhilzTouch (flashed with Odin).

Reboot into recovery works now most of the times but not always.

Switch off / reboot still takes about 9 seconds.

It seems the phone is searching for something it can't find.

What went wrong?

And more important for me: how can this be repaired?

Do I have to delete some files/folders from system or somewhere else?

Please help!
[Galaxy S 4 Mini Android Development] DeusEx80:
Similar problem on my I9195 flashing the .zip of stable version of 20140831.

Sometimes the recovery boot correctly (but the splash screen isn't showed) , sometimes it doesn't boot and reboot the system.

Then i flashed the stable version of 20140606 (always the zip), and the Twrp works perfectly all the time.

I tried also to reflashing the 20140831 version a second time: same behaviour
[Galaxy S 4 Mini Android Development] ne0zone75:
My TWRP builds (all devices : S4 mini and Transformer series) do consist in flashing an imaged /recovery partition that i build along with CyanogenMod's sources tree... that's it !

Now, it is far beyond my knowledge to explain to you why flashing any of my TWRP build by using Philz recovery can cause issues but it is a fact !

In my opinion only Odin is suitable for switching from a recovery like regular CWM / Philz one to any TWRP build, that is why i am offering 7zipped .tar.md5 among other things...

Flashable .zip files are handy BUT from my point of view they should be used ONLY for updating... not for switching...

Anyway, what ROM are you using please... (cannot see your signature right now) ? Stock or AOSP based ? (in order to wipe your device extensively after having NANDROID backed up what needs to; when done you will be able to start from scratch and restore what you just backed up from recovery... that is just what i would do in your case...)

Finally, i would really like to know what is [MENTION=3261191]F4k[/MENTION] opinion about all of this...

Kind regards
[Galaxy S 4 Mini Android Development] ne0zone75:
v2.8 will be released in a few moments... you will tell me if it is better... ;)

Do you have the same 'slow booting / rebooting' issue than [MENTION=3195878]hansare[/MENTION] please ? (in addition to the 'recovery not always booting' issue)

Thanks to you two for your feedback and very sorry to everyone for the inconvenience... :confused:

Regards
[Galaxy S 4 Mini Android Development] DeusEx80:
I will try it when it is available :)

No

Thanks for your work :)
[Verizon HTC One (M7)] PsyberEMT:
So here is my conundrum. I'm a crack flasher. I use CyanDelta to update CM11 every 3 - 5 days. When it runs I also have it install the EliteLunar kernel flashable zip and the exchangenopin zip. I'd like to create a flashable zip that would edit the build.prop file to change my DPI back to the 420 that I use instead of the mister magoo 480 stock. Is there a way to do this? I don't want to entirely reflash an old copy of the build.prop in case anything gets updated in the nightlies, I just want it to edit the single line with DPI.

Thanks!
[Verizon HTC One (M7)] jpradley:
Use texdroider_dpi to modify DPI on your screen. Free in Google Play.
[Verizon HTC One (M7)] disconnecktie:
Use a root file explorer such as es file explorer. Set the system as read/write. Navigate to the build prop, make the change, reboot and bam you have your changed DPI.
[Verizon HTC One (M7)] PsyberEMT:
I'm currently using ES File explorer. My goal was to make a flashable zip that I could include in CyanDelta to automatically change the DPI each time CyanDelta updates the OS.
[Verizon HTC One (M7)] disconnecktie:
See the problem you have is that what you want to edit is in a file and I don't think you can edit that file in the way you would like. You could make a flash able build prop but what if you overwrite the build prop cm provided in the update and break something as a result? Your best bet would be to manually edit the build prop or use the suggested app.
[Verizon HTC One (M7)] cmlusco:
This is the command to edit the line in build.prop

sed -i '/ro.sf.lcd_density=480/c ro.sf.lcd_density=420' /system/build.prop

If you need me to i can make the whole flashable zip when i get some time, if you dont know how.

Basicly you just need to mount system and then give the above command.

Any text based files contents can be edited this way.
[Verizon HTC One (M7)] disconnecktie:
That's cool I didn't think you could issue a command to edit one line. Learn something new all the time. He should be able to add that to any of the updater scripts after the system partition is mounted and before it is unmounted.
[Verizon HTC One (M7)] cmlusco:
Thats a little trick i picked up from tiny over on the droid incredible forums.
[Verizon HTC One (M7)] PsyberEMT:
If you get the time to make a flashable zip of this that'd be simply amazing! I'm afraid that is a bit over my Android head :(
[Verizon HTC One (M7)] cmlusco:
Here you go http://vzw1files.dyndns.org/MODs/LCD_Density_420.zip
[Verizon HTC One (M7)] PsyberEMT:
Many thanks! :highfive: Sent a beer your way...well...not an actual beer...but the paypal equivalent lol.
[Verizon HTC One (M7)] cmlusco:
Thank you.
[Verizon HTC One (M7)] speedyg0nz:
I happen to be looking for the exact same thing! However the link seems to be down at the moment, could [MENTION=3211855]cmlusco[/MENTION] or someone who has downloaded it put it up for download again? Thanks!
[Verizon HTC One (M7)] cmlusco:
It is working now. Mabey it went down for a minute.
[Verizon HTC One (M7)] asdfasdfvful:
[MENTION=3211855]cmlusco[/MENTION], do you mind uploading the zip again, but for a dpi of 400? The old link isn't working. I tried making it for my nexus 5, but it seems as though my binaries are messed. I`ve made other zips that work on android 5.0.2 though....
[Verizon HTC One (M7)] kramttocs:
Could we get this put back up?

Also, 400 would be great :D
[Verizon HTC One (M7)] superkev:
For those who still want to do this, this awesome zip file by [MENTION=5431257]klenamenis[/MENTION] will make any changes to build.prop that you specify. Just edit the tweak.prop file in the zip and flash the zip. I have Cyandelta automatically flash this zip each time I update. This saves me from having to set up all my widgets again after each nightly update because the resolution has changed! :mad:

http://xdaforums.com/showthread.php?t=2664332
[HTC Vivid, Raider, Velocity] Sleetback:
I'm scared of even touching the hardware, is there any new methods to S-off that doesn't require any wire tricks?

Sent from my HTC Velocity 4G Holics ROM @ TWRP 2.6.3.0 & Stock Kernel
[HTC Vivid, Raider, Velocity] cmerlyn:
Nope. I was worried about it, but it is pretty easy if you read all the instructions very carefully, and it is unlikely to cause any problem. The instructions are long, but they do work.
[HTC Vivid, Raider, Velocity] Sleetback:
I can't do it man. Nope nope nope. I'm better off flashing S-On. :banghead:
[HTC Vivid, Raider, Velocity] projectisaac:
In all honesty, unless you were thinking of messing around with the radio (potential for some hardcore bricking) or the other protected partitions (I think you can change the HTC boot logo?), putting your phone to S-OFF would only:

-allow for you to set your phone back to "locked" as opposed to "re-locked"

-unlock your SIM without paying some $10-$15 to a site

-be convenient in that you would no longer need to separately flash boot.img
[HTC Vivid, Raider, Velocity] Jackson_81:
Yeah I am also scared to S-OFF, just doesn't seem worth it to me when it just adds one step (flashing the kernel manually) to loading a new rom
[HTC Vivid, Raider, Velocity] projectisaac:
Yeah; for me personally I am more concerned if I go to flash ,say, recovery while in s-off and accidentally flash the recovery image to hboot (or another normally protected partition) and seriously screw myself. The actual shorting of the wires is pretty damn safe, and s-off can be reversed, but hey, to each his own comfort zone.
[HTC Vivid, Raider, Velocity] Sleetback:
Nope, i wasn't thinking of anything hardcore as to meddling with the raidio.

But yea, i was thinking of going S-OFF for me being able to flash with ease AND change my splash screen. That's about it.

So, i think it ain't worth it. For me atleast.
[XPERIA X10 Q&A, Help & Troubleshooting] fugazi1978:
I run my x10i on Feralab v37 (the latest one) but still have an old issue... I think I deleted my user dictionary soon after rooting my phone (and it hasn't returned even with fresh installs of ROMs). When going to settings then user dictionary, settings crashes. When using a user dictionary modification app they say things like "ahh crap, null exception error".

Where is it supposed to be and where can I get a fresh copy?

Thanks in advance.
[XPERIA X10 Q&A, Help & Troubleshooting] fugazi1978:
Still no dictionary...

Anyone?
[General Questions and Answers] 6u3n:
i am actually reading the forum about making note 2 like a note 3 but because of too much replies I could not find the latest steps on how to do it. I am actually new to rooting and I have no idea to do it that's why I am asking for help on that. the easiest instruction that you can share with me would be very appreciated. I really like to have that air command using stylus and some other nice features of note 2. thank you so much in advance for you the help...

I am actually using NOTE2 updated already to 4.3.... :)
[Sprint Samsung Galaxy S III] snafle:
Hi all,

Background - I'm doing a research project using phones as enhanced cameras, processing images in board. The phones we were using don't work due to low light (different environment) so we're going to buy a bunch of Galaxy S3s. The ones I can get in best buy are android 4.3, which OpenCV native camera doesn't work on.

I've flashed one to MetalFan's 4.1.2 since it is said to be close to stock. I've tried to get the stock file off stockroms.net but is doesn't want to download. I'm happy to stay with MetalFan's however I do want to be as close to stock as possible. I also want the smallest chance of something going wrong - we're going to be buying 10 more on top of the one I have here and flashing them all tonight so I want the fewest chances to wreck it as possible, hence the smallest number of steps.

So does anyone know 1) where I can dl a stock 4.1.2 image and 2) how I would best flash it. I am on a mac so would use Heimdal rather than Odin.

Tom
[Sprint Samsung Galaxy S III] thenexusgeneration:
If you purchase S3s on 4.3, or they have 4.3 as an official update (I. E. The build number goes to the one that is 4.3 (varies by carrier)) then you cannot use Odin or equivalents to revert to anything <4.3 because it will hard-brick itself. If you need a stock 4.1.2 file to flash, you can find a stock, rooted, odexed or deodexed ROM for the model of phone (carrier specific, obviously) and flash it through recovery. Or, if you want, I can try to set up a fully set up CWM backup of my SPH-L710 MD4 4.1.2 Sprint S3 in my Mega account and post a link to download. Hope I helped/can help
[Sprint Samsung Galaxy S III] Eagles1181:
TOTAL NOOB HERE. So forgive me if I don't know the correct terminology and such.

I was in the process of updating my ROM from 4.1.2 to 4.3

The ROM stated that I needed to be running TWRP version 2.6.3.0 or 2.6.3.1. I checked on my phone and I have 2.5.0.0 installed. So I followed the link the ROM post and downloaded TWPR 2.6.3.1, and moved it to my SD card. I then did a nandroid backup and then flashed the VIP file for the recovery. Now when I try to boot into recovery I end up in a boot loop. I can boot the phone into the ROM just fine. Any suggestions as to what might have happened, or how I reinstall a recovery without having access to a recovery?

Thanks

Eagle
[Sprint Samsung Galaxy S III] metalfan78:
Download goo manager from the play store, open it, hit settings, then install open recovery script.
[Sprint Samsung Galaxy S III] Eagles1181:
That did it. Thanks so much for your help.

Eagle
[G2 Accessories] brobro1312:
Hi. I bought G2 5 days ago and I liked it. But I cant use Quadbeat 2 because its not standing in ears like other earpods and it fells down with small move. How can use it. Thanks.(and sorry for my bad english)
[G2 Accessories] fizzy177:
Try to use a different size of ear-buds that suites you. Look in the box there are standard sizes of ear-buds packed with the quadbeat headset.
[G2 Accessories] Katze Pavilion:
Yes, ear-buds come with quadbeat2 is so small or so big, non of them fit with my ears. Sound quality is big decent while compare to quadbeat1 of the Optimus G. So disappointed.
[G2 Accessories] leomd333:
It aint the size that is bad, it is the type of rubber they use, it is really slippery and doesn't grip into your ears.
[G2 Accessories] fizzy177:
Ok u may be right but i don't have such kind of issues . :p
[G2 Accessories] ali_ign:
for me it's best earphone i ever had !
[G2 Accessories] lostangelintx:
I didn't get any headphones with mine. Not even any room in AT&T box for them. This was shipped from AT&T because local store didn't have any G2's in stock.
[G2 Accessories] la3ar:
You are so right! Im gettin pissed off every morning when im going to work. They are always falling of mine ears. Its iritating
[HTC Vivid, Raider, Velocity] Sleetback:
I've been looking for Apps like LeeDroid that could customize Sense 3 even further.
[8125, K-JAM, P4300, MDA Vario General] Rushey_Platt:
On my device on the Today screen the date is shown over 2 lines. This seems a waste of screen space. How can I get it to show over one line?

Current, e.g.

Monday........................2154

05 June 2006

Wanted, e.g.

Monday 05 June 2006....2154

Thanks

Rob F