• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Sense 5 Port - Android 4.1.2 - working Bluetooth, Face Unlock

rootlinux said:
I tried flashing Y4 to see what he had going on and for some reason it killed my recovery and sent me in bootloops.
Any attempt to get into recovery just jumped back to bootloops.
I flashed recovery via bootloader and got back in.
Then it said unable to mount internal or external storage.
No rom would flash.
I managed to get stock to flash even though it said failed.
Booted up and it fixed my storage but my internal storage was wiped.
Craziness. LOL
Not related to the topic I know, just a heads up if it happens to anyone else.

Gonna flash r22 when it goes up.
Click to expand...

I posted over in that thread also. The same thing happen to me only I could not even flash recovery from the bootloader and have it work. I tried everything for 3 hours then ended up using viperRUU, unlocking again, loading TWRP and restoring my r17 nandroid. My internal storage was wiped also.

There have been more than 2 reports of the same problem.

Lets hope someone figures it out. There will be a few people who won't have the fortitude to recover from it!
 
Comstar said:
I posted over in that thread also. The same thing happen to me only I could not even flash recovery from the bootloader and have it work. I tried everything for 3 hours then ended up using viperRUU, unlocking again, loading TWRP and restoring my r17 nandroid. My internal storage was wiped also.

There have been more than 2 reports of the same problem.

Lets hope someone figures it out. There will be a few people who won't have the fortitude to recover from it!
Click to expand...

That is true.
I actually backup my internal and external storage regularly so my loses are always at a minimum.
Not sure if it was rom related or recovery.
In any case we flash at our own risk but people should be aware what can happen.
Only one other time has that happened and I am sure it was recovery that time.
This time I was running 2.6.3.0 kitkat recovery.
I flashed regular 2.6.3.0 and got back in.
 
rootlinux said:
That is true.
I actually backup my internal and external storage regularly so my loses are always at a minimum.
Not sure if was rom related or recovery.
In any case we flash at our own risk but people should be aware what can happen.
One one other time has that happened and I am sure it was recovery that time.
This time I was running 2.6.3.0 kitkat recovery.
I flashed regular 2.6.3.0 and got back in.
Click to expand...

I was running 2.6.3.0 kitkat recovery too. I also had just updated my hboot to 2.09 the day before.

I did mention in the other thread that I was not sure what the cause/combination was. I think I will hang with this ROM until we get 4.3.
 
rootlinux said:
I am thinking 2.6.3.0 kitkat maybe the problem.
Click to expand...
I'm using a 2.6.3.0 TWRP recovery with the selinux kernel, and I've been able to flash both mine and yankees2450's ROMs. However, there seems to be a specific procedure to follow.

It seems that KitKat/SELinux makes the recovery misread the update binary if you try to flash a non-KitKat ROM in recovery after having one installed. My solution to this has been to full wipe using the Advanced Wipe settings (Cache/Data/System/SD-Ext/Android Secure), and then choose the option to reboot recovery (it'll tell you no OS is installed and ask you about installing SuperSU - you can ignore the first, decline the second). This seems to normalize the partitions of the device. Then, you should be able to go about flashing whatever you want.

On a ROM-related note, r24 should be the last for a while (unless I can figure out how to fix that Dialer issue, native Tethering or Locations). I'm open to assistance on those issues :).
 
That makes since.
Still I think more will come up on the same issue.
Maybe the recovery can be tweaked to handle it better.
 
I'll just hang tight with r16 until everything is back to working [excluding zoe, of course] order. ;)
 
I'm exporting R24 from SVN now. I'll flash this tonight if I don't fall asleep. I worked my arse off today, running on fumes right now.

I can flash and test for you Cap'n, my Java skills are still at the intro level so I won't be much help with code. :o
 
rootlinux said:
That makes since.
Still I think more will come up on the same issue.
Maybe the recovery can be tweaked to handle it better.
Click to expand...

Another person boot looping in the other thread. I asked if they had flashed cm11 recovery but no response yet. Is there something I/we can do to help prevent this? I feel like we know what it is,

EDIT: that person said they never flashed the cm recovery. So maybe that's not all of it. I guess I will just enjoy r24.
 
Just flashed r24.

Gallery works just fine for me. Without a hitch actually, and it seems to be loading faster now.

I can also confirm that the duplicate media file fix works. Had probably half a dozen duplicates of my photos, after the r24 flash they're all gone! :D

Kick ass Cap'n!

Anything else you need me to test out?
 
I just now got this far on another rom if it helps any (meaning, I don't think it's down) -

1385013845651.jpg
 
bayp4amd said:
Anyone know how to disable volume button wake?
As i got s2w enabled
Click to expand...
I didn't realize that was enabled. It shouldn't be, but I guess one of the files I'm using must have it built in.

Not sure which file it is. I think there was talk of this in yankees2450's thread on XDA, so maybe check over there?
 
CapThrowback said:
I didn't realize that was enabled. It shouldn't be, but I guess one of the files I'm using must have it built in.

Not sure which file it is. I think there was talk of this in yankees2450's thread on XDA, so maybe check over there?
Click to expand...

I got it in yankees thread,
The file should be android.policy.jar and someone shared that file in order to disable volume wake and enable long press volume to next/prev song.
 
You must log in or register to reply here.
Back
Top Bottom