Search results

just to check, noone here can mount the system partition from TWRP, once thesystem has booted from the first time, true?

After flashing this kernel and using the ROM would I be able to mount data and system partition from TWRP? Nowadays it´s impossible using https://forum.xda-developers.com/galaxy-tab-s3/development/rom-lineage-17-0-android-10-q-20191010-t3981535 :( Not sure if TWRP, kernel o ROM problem.... By...

Yes

3= 20200211: latest sources, February security patch 2= 20200113: latest sources, January security patch 1= 20191224: latest sources, update kernel to 3.18.140 Hi, I´m on #1 can I just flash #3 directly (dirty flash) to update or should I do a clean flash (after a complete wipe)? Is it right...

Well, finally solved. The key was that in the wellcome wizard of android I told it to use the backup of my actual phone. Then android used exactly the same configuration (as the phone) to setup the wifi, including the fixed IP. So my phone and my tablet both had the same IP in the LAN. No one of...

Well, finally solved. The key was that in the wellcome wizard of android I told it to use the backup of my actual phone. Then android used exactly the same configuration (as the phone) to setup the wifi, including the fixed IP. So my phone and my tablet both had the same IP in the LAN. No one of...

Well the problem is that after booting system the ROM makes some changes in data partition. After that my TWRP can't access to it. It says that "unable to find crypto footer". It seems a problem of TWRP not being able to mount (read) a data partition despite the fact that it's not encrypted.

Of course, not. My signature is out-dated. I will update it. Thanks in advance.

Well, after reflashing the device behaved different and now it´s working ok. I don´t know what really happened in the first flash. What I see is (vía Google Truts) that this compiled LOS ROM has no enabled SELinux...... ¿? Not sure exactly why. Damn, damn, damn, damn..... :( After flashing...

Incredible, after falshing I can´t complete the Android Installation Welcome Wizard. It asks for a wifi (mandatory) after that the dialog says it´s searching for updates. After a minute or so says it cant connect. So I can´t even finish the wizard. Very frustrating :((

Specifically the message that shows is: "cannot mount /data and unable to find crypto footer" I don´t know why in the hell this recovery can´t find the footer inside a data partition that indeed is unnecripted.... @ jd1639 I will try to compile the new one.

Sometimes wifi transfer (donwload and upload) stops for a a long time (minutes). Then, suddenly it recovers. Very strange. 1.- I can confirm ther´s no problem with my wifi (as other devices can connect without problems, included my Tab S3 until flash). 2.- I also have used my phone as wifi point...

It would be great to have an updated TWRP for Galaxy Tab S3. I have installed that and can´t mount /data partition AFTER the first boot of Lineage OS ROM. This TWRP can only mount /data partition after formatting it. I have seen Lineage fstab (fstab.qcom) for my device and clearly says...

Exact samen problem as me. It seems that booting for first time the ROM "encrypts" de data partition and it becomes inaccesible for TWRP :(

This DID NOT workerd for me. Formatting data (or change to ext2 and ext4) only gives you TEMPORAL data access. After booting in the System then the data partition gets, again, inaccesible.

Hi there. Same problem here, but every few minutes/seconds. WiFi transfer drops to zero, then some seconds happens, and finally speed is recovered again. Very uncomfortable. Last version of the first post flashed (over clean and wiped device) :( ---------- Post added at 05:26 PM ----------...

Damn, damn, damn. First crash after almost 4 months without one. The return of the problem? Playing video with updated YouTube and while charging...

It seems the problem is solved!!!! No crashes in more than one month. Finally it seems software update (probably YouTube app) has solved the problem, despite that YouTube by itself wasn't the culprit. At last great news!! ---------- Post added at 07:42 PM ---------- Previous post was at 07:41...

Same here. No crashes sice last update (I mean, that from first of April). Problem solved? Let's see. But for the moment good feelings.

Thanks for the reports, spinik.

Also report if you don't have any reboot in a long time ;) as it will be the solution....

I just had a freeze. Confirmed, android system webview it's not the culprit. Restoring it.

Done. Let's see if it works!. I would like to know what are the disadvantages / functionality that is lost because of disabling this component. Edit: I mean this component makes possible for apps the use of the internal Android web browser. So, a bunch of apps will begin stop working properly...

Today I have had my first freeze with an app different from YouTube. The curious thing has been coming here to inform about it (it's something new for me) and seeing that you were taking just about it. So, I can confirm that with other app I have had a freeze and reboot. The app is this...

1.- Change volume= As DecypherT says, for me it also doesn´t seem to be the problem. 2.- Problem of cache (try to delete cache often)= I will give it a try. 3.- I don´t have XPrivacy installed, and it freezes, so I won´t say it´s the culprit.

I'm sorry to inform you that despite of changing to awesome player, yesterday I had a freeze again :(. So this is not a final solution. But at least it seems to be a good workaround because for me it reduced a lot the occurrence of a reeboot. We will keep investigating...

For the moment it´s working for me, too. PS: Not affected in game graphics because I don´t play.

OK. So it´s: a) a youtube related flaw (app and web version -becouse videos crashes on both versions-) or b) an optimizations in the ROMs. About this last, momulah says tha with AICP Nightly 20160105 build Youtube works with no freezing.... insteresting.

Someone said it could be a kind of bug in YouTube app. After two frezzes & reboots today, I can't state that it isn't an app problem because in both cases the crash was while playing videos with the web version of YouTube. Note: I'm running stock ROM updated with latest security update fr...

Millenium3, Where o how did you get this .zip file?

So, I supose there´s time based information inside de .img. Other way, if the source is the same, the .img generated, should be the same, shouldn´t it?

The MD5-hash of the .img provided is DIFFERENT from the MD5-hash from the original file in http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.6-i9300.img Who can explain it?

1.- recovery.img from touch version .zip in this thread. MD5= 5872D646336D5F7095372A38C292BD0A 2.- recovery-clockwork-touch-6.0.3.2-i9300.img from www.clockworkmod.com. MD5= 3C9B7B0ABDE6427F8042BAED65F9F988 Both are v6.0.3.2 and touch, ¿How can this be possible? :eek:

Thanks for the help, but I don´t have any manufacturer ROM or stock ROM installed. I have a Cyanogen ROM (which is one of the stablest and more tested ROMs in the market).

Yes, it´s HSDPA. But I need it on, because I want to be online. The rest of the consumers are allways turned off: GPS, WiFi & Bluetooth. I don´t think it´s the battery, because it happens since the battery was almost new. The key here is to know what the phone is doing when executing this 2...

Screenshot from my phone. Translated to english would be: A.- Cell standby, and B.- Phone idle Quertions: 1.- ¿What are the differences between A and B? 2.- The battery has drained but.... DOING WHAT (49+49= 98%)? Technicall explanations will be appreciated. Thanks in advance.

Simply format your SD card. You can do it with any PC whit card-reader.

hopscotchjunkie said: Why?. Could you give details? Actrually Cyanogen´s ROMs use HTC RILs. 43-gsm-android said: Are you sure that this *great* performances cames from the new radio? Won´t it be motivated by the fact of reflashing a CM ROM again (thus cleaning your system)?

After partitioning it´s logic to loose data. But partitioning is a reversible process. I mean, from the recovery console you should be able to repartition again your interna memory to it´s original state. But, as I said, from the console and typing commands by yourself.

Yes, after some days of use, I can see all my apps. And the Market is working normally.

Well, I finally solved it. Here is the complet explanation as far as I understand de problem. PROBLEM: + Some apps were missing in the "My apps" Market tab. + Despite that there were updates available for the installed apss, the Market didn´t notify about them. + Thus, the only way to update...

I´ve seen that there is an option called "Market Doctor" in Titanium Backup Pro (so far I don´t have this app). Some people says it can fix the issue. But the problem is that I don´t know how it works (so I´m not likely to pay and install it). It seems that there is a lot of people with "market...

Hello. Same problem here. I´ve tried almost everything: rebooting, deleting data & cache, unninstalling market self-update, fixing permissions, restoring old complete nandroid backups, etc. Nothing seems to work! Market v3.1.5 doesn´t fix anything, and everyday that passes I´m more sure...

I have the same problem, and I haven´t find any solution so far. If you see, the lost apps aren´t in present in the market web version.

What? I don´t understand a word! What are you trying to say?

And which version of CWMod and ROM Manager did you use?

Siru5 I totally agree with you. It would be great to know the relation (=interfaces) between ROM Manager & CWM. In the other hand I´d like @koush to give some kind of indication or information to the community in that way. We can discuss the usefull of formatting the SD card in the DHD, but...

Summarizing from the last 2 pages: + duarab said that used an up-to-date ROM Manager downloaded from Market and bricked his phone + Siru5 said that used ROM Manager v3.x & CWM V3.0.2.6 and bricked his phone As duarab doesn´t know/remeber his CWM version, we only have ONE testimony stating that...

What version of ROM Manager and Revery caused the brick? Do you remeber? I mean, a recently downloaded ROM Manager musn have this bug fixed.

OK. Thanks for the details. I didn´t know there was a method involving resistors to this issue. No problem, then. I hope you could find a good solution.