Related
I've seen one or two threads that were in the same vein as this, but no clear resolution. Every time I open SuperSU, I get the message, "The SU binary needs to be updated. Continue?" I select "Continue," and am given the message to install it normally or through TWRP/CWM. If I try through TWRP, the phone restarts into TWRP, but does nothing. If I select "Normal," I get the "Installation failed!" message. I tried uninstalling/reinstalling SuperSU, but that didn't do anything.
In a related problem, I only have root access pretty much immediately after I reboot. Only immediately after I restart the phone can I use apps like WiFi Tether or Titanium.
I'm on stock, rooted 4.1.2. Any help would be great, thanks!
http://d-h.st/0du
Go into twrp and reflash supersu.
Sent from my HTC One using xda premium
eyeisdasteve said:
http://d-h.st/0du
Go into twrp and reflash supersu.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks for responding! Just to clarify, should I follow that readme file’s instructions, even though I’m already rooted and have TWRP? If simply choose “install” in TWRP and select this zip, will I have the option to just install SuperSU, or should I extract one of the following 3 zips in that file first?
SuperSU-v1.41.zip
superuser.zip
Superuser-3.2-RC3-arm-signed.zip
I assume this won’t wipe my phone, but of course, I’ll do a nandroid backup first.
Well, I went into TWRP, went to "install," and selected the whole .zip, but it didn't look like it was going to give me the option to flash just SuperSU.
Agh... I should do this stuff more often so I'm not so clueless each time I need to do stuff in recovery...
SOLVED!
I figured I just needed one of those SuperSU zips found in the file linked above, but first, I decided to first see if there was a more up-to-date version. I wound up downloading the updated version from here: http://forum.xda-developers.com/showthread.php?t=1538053
After flashing "UPDATE-SuperSU-v1.41.zip" in TWRP, my root access is much more robust (i.e., not losing root after one app successfully requests access) and I am no longer being prompted to update my binaries!
Thanks again!
SuperSU
subhumanderelict said:
SOLVED!
I figured I just needed one of those SuperSU zips found in the file linked above, but first, I decided to first see if there was a more up-to-date version. I wound up downloading the updated version from here: http://forum.xda-developers.com/showthread.php?t=1538053
After flashing "UPDATE-SuperSU-v1.41.zip" in TWRP, my root access is much more robust (i.e., not losing root after one app successfully requests access) and I am no longer being prompted to update my binaries!
Thanks again!
Click to expand...
Click to collapse
Glad U got it working. I on the other hand am hosed. I wish the thing worked like everything else. I consider this to be a near
fatal weakness with the product. I at this point won't update until I get a clear understanding of what the heck is up with it.
Also Kyocera does not seem to be well supported. I got a Kyocera Hydro from a family member who was going to throw it
away. Guess I should have let him
rwilcher said:
Glad U got it working. I on the other hand am hosed. I wish the thing worked like everything else. I consider this to be a near
fatal weakness with the product. I at this point won't update until I get a clear understanding of what the heck is up with it.
Also Kyocera does not seem to be well supported. I got a Kyocera Hydro from a family member who was going to throw it
away. Guess I should have let him
Click to expand...
Click to collapse
So er.. what's your problem exactly? I could try to help you out.
not updating
Hi, I'm here about SuperSU not updating, but I have a normal rom, not TWRP or thecother one. Every time I go on SuperSU, it tells me there's an update. I click continue, then Normal, because that's the rom I have, but then it says the update failed. What do I do? Please help!
limehedd21 said:
Hi, I'm here about SuperSU not updating, but I have a normal rom, not TWRP or thecother one. Every time I go on SuperSU, it tells me there's an update. I click continue, then Normal, because that's the rom I have, but then it says the update failed. What do I do? Please help!
Click to expand...
Click to collapse
TWRP is a recovery not a ROM. If Normal doesn't work, select the other one. Assuming you have a custom recovery (I recommend TWRP for this phone), it should restart into recovery and flash the update there.
Hello, im new here and if you can please answer me on German
My problem is when i start to update SuperSU Binary it is failing on Normal mode and TWRP is happening nothing.
When i rooted first everything was glad, but there was no button to update the Binary and when i used apps like Xmodgames it says, my root is maybe no succesfull, so i rooted again without deinstalling the SuperSU blabla. And now is nothing working, if i go in Root Checker it cant find my root. Pls Help, sry for bad Grammar etc.
still have the problem
I did the flashing of the latest su update zip on my recovery reboit and ny supersu still prompts me to update binary just like before...HELP!!
my samsung galaxy s duos 2 is not updating binary in any modes
what should i do please help me
Is there any other way to update the binary other than through TWRP or CWM. I can't for the life of me find a CWM or TWRP recovery for my Hannspree Titan.
Hey guys, I have a problem here...
I had rooted my tablet and installed SuperSU, I choose the normal mode for binary update but it said it failed. Then I tried in TWRP/CWM but it just restarted my tablet and there it stayed.
When I power it on, it just keeps restarting every 5-7 seconds and it doesn't do anything else.
What should I do?
Hi guys,
New user here. I am not sure if this is the right way to reach the developers for Omni ROM but I hope it is.
I've recently started using Omni ROM and I absolutely love it. On January 18, 2014 you fixed a major problem I was having; having to re-root my phone manually after each update. However, my other issue is that system updates do not automatically flash itself on my phone.
I originally didn't know why, but I found out after installing Philz recovery and seeing the error log that the ROM was searching for OpenDelta\ROM.zip when it should be searching for sdcard\OpenDelta\ROM.zip in order to flash the update automatically.
I am using a Samsung S3 (i9300), if that makes a difference. I would love to see this issue resolved and I hope I can be of further help in the future.
NotSoNewbie said:
Hi guys,
New user here. I am not sure if this is the right way to reach the developers for Omni ROM but I hope it is.
I've recently started using Omni ROM and I absolutely love it. On January 18, 2014 you fixed a major problem I was having; having to re-root my phone manually after each update. However, my other issue is that system updates do not automatically flash itself on my phone.
I originally didn't know why, but I found out after installing Philz recovery and seeing the error log that the ROM was searching for OpenDelta\ROM.zip when it should be searching for sdcard\OpenDelta\ROM.zip in order to flash the update automatically.
I am using a Samsung S3 (i9300), if that makes a difference. I would love to see this issue resolved and I hope I can be of further help in the future.
Click to expand...
Click to collapse
Use TWRP and everything will be fine....It updates OTA
Nope, no such luck.
TKokab said:
Use TWRP and everything will be fine....It updates OTA
Click to expand...
Click to collapse
I use to love TWRP, I guess I still do, but there hasn't been an update to it in a while and version 2.6.3.0 has never been able to load an Android 4.4.2 based ROM. Whenever I tried it with CM11, it would boot once and then go into a boot loop after rebooting (all the time, and I tried for weeks). I just tried using TWRP to load an Omni ROM nightly (omni-4.4.2-20140121-i9300-NIGHTLY.zip) and got that error you get if you use an earlier version of CWM before 6.0.4.4 (set_metadata_recursive: some changes failed).
Then after trying the above I went back into a boot loop, so I had to use Odin to flash a CWM recovery I had and re-flash Omni to get it to boot again. TWRP needs a new version before I try it again.
TWRP has a 4.4.2 compatible version, I'm using it with OMNI ROM and it's 4.4.2 version. See their site:
http://teamw.in/project/twrp2
Sent from my Nexus 10 using XDA Premium HD app
NotSoNewbie said:
I use to love TWRP, I guess I still do, but there hasn't been an update to it in a while and version 2.6.3.0 has never been able to load an Android 4.4.2 based ROM. Whenever I tried it with CM11, it would boot once and then go into a boot loop after rebooting (all the time, and I tried for weeks). I just tried using TWRP to load an Omni ROM nightly (omni-4.4.2-20140121-i9300-NIGHTLY.zip) and got that error you get if you use an earlier version of CWM before 6.0.4.4 (set_metadata_recursive: some changes failed).
Then after trying the above I went back into a boot loop, so I had to use Odin to flash a CWM recovery I had and re-flash Omni to get it to boot again. TWRP needs a new version before I try it again.
Click to expand...
Click to collapse
that does not seem typical at all.
I'd guess you're having some other problem than the twrp version number.
bleggy said:
that does not seem typical at all.
I'd guess you're having some other problem than the twrp version number.
Click to expand...
Click to collapse
Not so sure that is true. Thanks to +3DSammy, I went searching for an update and found 2.6.3.1 through the Goo manager app. Now I am installing Omni ROM without a hitch:good: So I guess I'm gonna stick with TWRP once more. But my initial problem still remains: System updates are looking in the wrong place for the ROM download and needs to be completed manually.
I'm sure the developers will sort that out soon, unless I'm the only one with this problem.
"Bug report"
Woke up this morning and both of my omni devices (Note N7000 and Tab2 10.1 P5100) urged me to flash the update, which was ready to be installed. Already downloaded, patched and verified,everything done - I simply had to tap "flash now".
Excellent stuff! Amazing. ?
Why is my phone locking itself randomly? O.O hope this gets to the devs.
P.S. is there a site to report bugs? I'll love to bookmark that site and report a bug every other day.
Smack that Thanks button if I helped!
KitKat came in on my OmniROM, running on my Note 2.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA
Irwenzhao said:
P.S. is there a site to report bugs? I'll love to bookmark that site and report a bug every other day.
Click to expand...
Click to collapse
http://jira.omnirom.org/
Truely
AA1973 said:
"Bug report"
Woke up this morning and both of my omni devices (Note N7000 and Tab2 10.1 P5100) urged me to flash the update, which was ready to be installed. Already downloaded, patched and verified,everything done - I simply had to tap "flash now".
Excellent stuff! Amazing. ?
Click to expand...
Click to collapse
The issue is truley resolved for me too. Who do I thank??? Awesome work guys. Updating is a breeze now. Just click flash now and wait.
Update would not flash
I have recently started facing the update problem which was till earlier a breeze - go to system update and click flash now and it was a cake walk. But since the update of 21st Jan for N7000, i click flash now and I go into reboot but nothing happens.
TWRP opens and i reboot but still updates would not install!!!
Any suggestions!!!?
twrp needs to be set at the internal sd or opendelta folder. you have yours set to open the external.
bleggy said:
twrp needs to be set at the internal sd or opendelta folder. you have yours set to open the external.
Click to expand...
Click to collapse
Can you guide me how to reset the same in TWRP - new to all this.
many thanks,
Z
I9505 update
I:command is: 'set' and I:value is: 'tw_signed_zip_verify 1'
Setting function disabled in CWMR: 'tw_signed_zip_verify' to '1'
I:script line: 'install OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip
'
I:command is: 'install' and I:value is: 'OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip'
Installing zip file 'OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip'
E:unknown volume for path [OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip]
-- Installing: OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip
Finding update package...
I:Update location: OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip
E:unknown volume for path [OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip]
E:Can't mount OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip
Installation aborted.
E:Error installing zip file 'OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip'
Done processing script file
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
Camera Bug
Love the ROM. Most stable I have had on the i337M. I have noticed at least since the Jan 27 nightly the following bug. If the phone goes to sleep or if you hit the power button when in the camera app you will lose connection to the camera. You have to force close the camera and reboot to get it back. I reloaded my nandroid from jan 7 and still the same.
Zeusrocks said:
Can you guide me how to reset the same in TWRP - new to all this.
many thanks,
Z
Click to expand...
Click to collapse
its easy.
just reboot into twrp
browse to opendelta folder
or just internal.
reboot system.
if the last folder you were in
was your external or whatever
the update script wont run.
Sometimes on my GT-N7000 (which has the latest Omnirom 4.4.2 2014-01-31), when I'm listening to music (either on the buildt in app or the PowerAmp) my phone randomly crashes and reboots. This can occur once a day if I'm listening to music. But the music app themselves can also crash, and to fix it I must stop the processes in the settings menu to be able to play again. Does the occur for anyone else?
Thanks
ProShifu said:
Sometimes on my GT-N7000 (which has the latest Omnirom 4.4.2 2014-01-31), when I'm listening to music (either on the buildt in app or the PowerAmp) my phone randomly crashes and reboots. This can occur once a day if I'm listening to music. But the music app themselves can also crash, and to fix it I must stop the processes in the settings menu to be able to play again. Does the occur for anyone else?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2612329
@bleggy
Sorrry for being a noob, but do you use install to browse to the omnirom folder? Auto flash is still not working for me.
twrp>install>select storage:internal>opendelta>reboot
SU Binary needs to be updated on my phone - it's causing my phone to boot up, run for about 30 seconds, and then reboot over and over again.
How can I update the binary? I go to Superuser and it gives me the option to, but the phone reboots before I get the chance to update it.
I found the file I need to flash, but how can I get it onto my phone? The phone doesn't stay on long enough for me to transfer the file onto the phone...
PLEASE HELP!!
Sounds like you flashed a GSm rom that is not compatible with Sprint.
BD619 said:
Sounds like you flashed a GSm rom that is not compatible with Sprint.
Click to expand...
Click to collapse
Forgot to mention that I haven't flashed any ROM's - I rooted just so I could access mobile hotspot for free and what not.
Anyway, I actually ended up fixing it. Was able to get into SU and it posted the update file to my phone and I accessed it via recovery. Flashed it and the problem is fixed.
saj1jr said:
Forgot to mention that I haven't flashed any ROM's - I rooted just so I could access mobile hotspot for free and what not.
Anyway, I actually ended up fixing it. Was able to get into SU and it posted the update file to my phone and I accessed it via recovery. Flashed it and the problem is fixed.
Click to expand...
Click to collapse
thanks for the tip, i'm going to give this a try. something is throwing my phone into boot loops today too, I just unfroze all the stuff I froze with TB this week thinking that was the trouble.... I am on stock/rooted 4.4.2 with SU as well.
Update:
Booted to recovery, used adb to push the new Su binary (v2.00) over to phone, used custom recovery to install new su binary zip, all seems right with the world. will post again if I have troubles, but this appears to be working *crosses fingers*
I've got no idea what started this boot loop off today, maybe some OTA tweak I didn't approve? Not really sure...
bobsbobbers said:
thanks for the tip, i'm going to give this a try. something is throwing my phone into boot loops today too, I just unfroze all the stuff I froze with TB this week thinking that was the trouble.... I am on stock/rooted 4.4.2 with SU as well.
Update:
Booted to recovery, used adb to push the new Su binary (v2.00) over to phone, used custom recovery to install new su binary zip, all seems right with the world. will post again if I have troubles, but this appears to be working *crosses fingers*
I've got no idea what started this boot loop off today, maybe some OTA tweak I didn't approve? Not really sure...
Click to expand...
Click to collapse
hey man. same issue. i just tried the latest update. seems to work for now, but did the problem ever come back for you?
Hey guys,
strange thing happened to me yesterday.
After I got fed up with Paranoid, I decided to pick one of the other AOKP derivatives.
Although I had initial problems with mounting sdcard1, I somehow managed to flash from there
and do have SOKP with android 4.4.4 running on my honami
the thing is, when I want to access recovery through vol+ or vol-, my phone freezes on boot,
otherwise everything is working fine.
Unfortunately I need to flash GAPPS and I need to find some kind of workaround...
What I have tried is flashing TWRP and Z1DualRecovery via fastboot with no success.
Any ideas?
Thanks in advance
What is SOKP? Any link you can give us?
Did the kernel for that ROM include a recovery?
TWRP cannot be installed via fastboot on xperia devices. Z1dualrecovery kernel is for stock based roms only.
Maybe you should flash a FTF and start again.
you have unlocked bootloader, let flash pimp kernel to have working recovery, so you can reflash the rom to check it.
Sent from my C6903
gregbradley said:
What is SOKP? Any link you can give us?
Did the kernel for that ROM include a recovery?
TWRP cannot be installed via fastboot on xperia devices. Z1dualrecovery kernel is for stock based roms only.
Maybe you should flash a FTF and start again.
Click to expand...
Click to collapse
SOKP is Sonic Open Kang, a newer AOKP derivate.
It is one of the top posts in Android Development Forum.
Thought you heard of it.
Ok thanks will try it with pimped kernel. Hope it works with AOKP.
lauchrecords said:
SOKP is Sonic Open Kang, a newer AOKP derivate.
It is one of the top posts in Android Development Forum.
Thought you heard of it.
Ok thanks will try it with pimped kernel. Hope it works with AOKP.
Click to expand...
Click to collapse
I have seen it now, try flashing and wiping again
Hey, thanks for the fast response guys.
So I've just flashed Pimped Kernel to this ROM
http://forum.xda-developers.com/xperia-z1/development/xperia-z1-t2834169
I am still getting stuck on boot when I'm trying to get into recovery.
Neither vol+ not vol- works, I hit it when the purple light flashes and the orange one comes up and stays like forever.
So unfortunately I cannot flash nor wipe.
And Android without GAPPS kinda sucks... especially when they have the new material design...
EDIT: And I don't want to stay on pimped kernel cuz it somehow causes battery drain for me...
Only possibility would be to somehow install the zip via ADB/Fastboot... does that work somehow?
Just keep pressing it throughout the boot sequence, don't forget you have to press, let go, press, let go etc..... Its not just one long press
gregbradley said:
Just keep pressing it throughout the boot sequence, don't forget you have to press, let go, press, let go etc..... Its not just one long press
Click to expand...
Click to collapse
Just tried that out, in both directions.
Same result - no success.
Really unusual since it was always a long press and I should also be getting into the recovery
by rebooting into recovery from inside the ROM.
What other possibilities are there to get gapps on your phone?
lauchrecords said:
Just tried that out, in both directions.
Same result - no success.
Really unusual since it was always a long press and I should also be getting into the recovery
by rebooting into recovery from inside the ROM.
What other possibilities are there to get gapps on your phone?
Click to expand...
Click to collapse
push them with adb
but that's not the point
have you booted into system and check to see if quick boot is enabled in developer options - root
gregbradley said:
push them with adb
but that's not the point
have you booted into system and check to see if quick boot is enabled in developer options - root
Click to expand...
Click to collapse
I dont seem to have that option,
all I have is the point "Update CM Recovery when installing system updates"
@gregbradley how do I push and flash those via ADB?
Check in the gapps zip where each file should be installed (Proabably all to system/app) and the associated permissions (Should be 0755 or 0644, I don't have time to check just now)
Then put all the files in the same folder where you have adb installed.
then
Code:
adb push "[I]name of file here[/I]" system/app/"[I]name of file here[/I]"
adb chmod 0755 system/app/"[I]name of file here[/I]"
Replace the name of the file with the extension where I have said, change the "0755" to "0644" if that's what it says in the updater script, and if the apks should be installed somewhere else (for example syste/priv-app) change the commands to that.
This method would take you a long time, proabably best to just push the play store and then download the google apps you want, or better still, fix your recovery
Ok guys, many many thanks for your help.
I solved the problem and got my recovery back.
I flashed PhilZ and I like it. Way better than regular CWM.
You can close the thread now.
OK people i won't talk much, i by mistake in twrp went to wipe then advance wipe and selected everything in there (including system)( i got a 158 mb update to v10d software i did that but it kinda failed cuz it rebooted once and got to twrp and stayed on it forever all other reboots take me to twrp and nothing else and then i wiped everything after trying many times cuz i was mad ).
SO yeah now there's no os installed in it.
BTW i have l90 D410 the dual sim version v10c software rooted and unlocked bootloader with guides from XDA only.
To fix myself i tried downloading CM 11 and tried flashing the zip from twrp at first i got w7ds error telling my device is not w7, so i searched a bit and got something which said change updater script and edit "w7" to "w7ds" in the first few lines. So i did that and tried to flash again but then i got MD5 does not match
WHAT should i do?
ATM im just stuck on twrp with no os installed in my l90 or say i have a completely wiped l90 with twrp recovery and a sd card (8 gb) and when trying to reboot twrp says your device doesnt look rooted install supersu to root it (obviously swiping to install dont work), other twrp functions are working good.
HELP PLSsssss most appreciated.
regards,
[IND]sattu
sattu_96 said:
OK people i won't talk much, i by mistake in twrp went to wipe then advance wipe and selected everything in there (including system)( i got a 158 mb update to v10d software i did that but it kinda failed cuz it rebooted once and got to twrp and stayed on it forever all other reboots take me to twrp and nothing else and then i wiped everything after trying many times cuz i was mad ).
SO yeah now there's no os installed in it.
BTW i have l90 D410 the dual sim version v10c software rooted and unlocked bootloader with guides from XDA only.
To fix myself i tried downloading CM 11 and tried flashing the zip from twrp at first i got w7ds error telling my device is not w7, so i searched a bit and got something which said change updater script and edit "w7" to "w7ds" in the first few lines. So i did that and tried to flash again but then i got MD5 does not match
WHAT should i do?
ATM im just stuck on twrp with no os installed in my l90 or say i have a completely wiped l90 with twrp recovery and a sd card (8 gb) and when trying to reboot twrp says your device doesnt look rooted install supersu to root it (obviously swiping to install dont work), other twrp functions are working good.
HELP PLSsssss most appreciated.
regards,
[IND]sattu
Click to expand...
Click to collapse
Did you try installing stock rom with kdz files using guides to be found on L90 general (I think) section?
sattu_96 said:
To fix myself i tried downloading CM 11 and tried flashing the zip from twrp at first i got w7ds error telling my device is not w7, so i searched a bit and got something which said change updater script and edit "w7" to "w7ds" in the first few lines. So i did that and tried to flash again but then i got MD5 does not match
Click to expand...
Click to collapse
What thread did you get your recovery from, @Quarx CM11? There is an option in TWRP on the page that's displayed right after selecting files to install, "Zip file signature verification". Make sure it's unchecked. Unchecking that option should bypass the MD5 verification and allow the installation. Unfortunately, you may have to continue with editing the updater-script on new installs.
I'll speak with @shoxxy and @Quarx about creating recoveries for the dual sim devices so that we can prevent this error from happening anymore. This will mean that there will eventually be 2 different sets of recoveries available for the L90. One set for dual-sim devices, and one set for single sim devices. By recovery set, I mean all available recoveries, CWM, TWRP, and Philz-Touch.
The reason for TWRP not installing SuperSU to root the OS is because there is no OS to root.
wojtek267 said:
Did you try installing stock rom with kdz files using guides to be found on L90 general (I think) section?
Click to expand...
Click to collapse
umm bro how could i do that since it requires my l90 to be in different modes while doing that, but i can only boot uptill twrp and there's no os in there.(btw i have stock kdz downloaded on my pc)
shinobisoft said:
What thread did you get your recovery from, @Quarx CM11? There is an option in TWRP on the page that's displayed right after selecting files to install, "Zip file signature verification". Make sure it's unchecked. Unchecking that option should bypass the MD5 verification and allow the installation. Unfortunately, you may have to continue with editing the updater-script on new installs.
I'll speak with @shoxxy and @Quarx about creating recoveries for the dual sim devices so that we can prevent this error from happening anymore. This will mean that there will eventually be 2 different sets of recoveries available for the L90. One set for dual-sim devices, and one set for single sim devices. By recovery set, I mean all available recoveries, CWM, TWRP, and Philz-Touch.
The reason for TWRP not installing SuperSU to root the OS is because there is no OS to root.
Click to expand...
Click to collapse
i believe i got twrp from google (damn) , by md5 verification you mean that zip file verification should have a cross infront of it or not? well w/e it is i tried in both ways (having cross and not having one) but it checks for md5 both times, maybe because i dont have twrp from quarx thread.
Can i update my twrp to quarx's one? if so how pls tell, would be much helpfull.
EDIT : atm i have downloaded few files that might be needed to unbrick(stock kdz file, cm11 28/10 build, twrp image from quarx) on my pc
UPDATE
OK i got to install cm11 on my device and when i try to fix permissions is says a SELinux is present (good) but phone is still just booting in twrp only.....
HELPPPP
nooooooo some1 pls help im desperate.......
p.s. why doesnt twrp remember my settings, i set screen timeout to 15 sec, after every reboot i have to w8 full 60 sec to get its screen timeout to be able to use the touch screen.
EDIT: OK guys dont bother yourself now i got myself running cm11 on my phone and its unbricked now. Cheers and thanks for your time.
if any1 wants me to tell what happened to my device how it happened and how i fixed w/e i tried etc then pls tell i might write it down for some other people who might be stuck.
sattu_96 said:
OK i got to install cm11 on my device and when i try to fix permissions is says a SELinux is present (good) but phone is still just booting in twrp only.....
HELPPPP
nooooooo some1 pls help im desperate.......
p.s. why doesnt twrp remember my settings, i set screen timeout to 15 sec, after every reboot i have to w8 full 60 sec to get its screen timeout to be able to use the touch screen.
EDIT: OK guys dont bother yourself now i got myself running cm11 on my phone and its unbricked now. Cheers and thanks for your time.
if any1 wants me to tell what happened to my device how it happened and how i fixed w/e i tried etc then pls tell i might write it down for some other people who might be stuck.
Click to expand...
Click to collapse
you said that u updated ur device to 10d..
Thats d problem.....
If u updated ur phone without stock recovery..
It will struck at twrp..
If u try to flash roms..
but still u'll struck at twrp (It happens to me tooo)
After rebooting the phone is directly enter into recovery mode to flash new update ..
I don't know where the update file and script stored but until its updated its still struck at the same twrp..
if u remove cache/delvik cache/data/system..
But still its trying to update phone by entering into recovery mode.......
So,
Only one solution to this.
Flash kdz file using offline method.
Here's link to thread
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
but after flashing kdz 10C.
It'll automatically update to 10d (Don't panic at this)..
kprsnt said:
Only one solution to this.
Flash kdz file using offline method.
Here's link to thread
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
but after flashing kdz 10C.
It'll automatically update to 10d (Don't panic at this)..
Click to expand...
Click to collapse
the problem here is that my phone was not in usb debugging mode before brick and i spent 6-7 hrs figuring out how to get my device detected, but it never got detected in my pc.
BTW my prob for now is solved since my phone is running cm11 very well, its true that i lost some good functionality like knock on, qslide apps, quick window software, etc. but at least it has an os to boot into now.
help
sattu_96 said:
OK i got to install cm11 on my device and when i try to fix permissions is says a SELinux is present (good) but phone is still just booting in twrp only.....
HELPPPP
nooooooo some1 pls help im desperate.......
p.s. why doesnt twrp remember my settings, i set screen timeout to 15 sec, after every reboot i have to w8 full 60 sec to get its screen timeout to be able to use the touch screen.
EDIT: OK guys dont bother yourself now i got myself running cm11 on my phone and its unbricked now. Cheers and thanks for your time.
if any1 wants me to tell what happened to my device how it happened and how i fixed w/e i tried etc then pls tell i might write it down for some other people who might be stuck.
Click to expand...
Click to collapse
hey brother same problem here. after flashinf L-touch rom on my galaxy S duos (gt-s7562) i got stuck in boot screen, nothing is going after it.
then i tried installing flashable twrp recovery from cwm recovery, and then followed the procedure to install L-touch rom. but when i reboot my device it says " no os installed" and asks me to install superuser. ( i think my os and my root access are gone now).
please hepl me out brother.
thanks and regards,
dhaval
You need to download the firmware (around 900mb) not cm ROM (300mb)
Sent from my GT-I9192 using XDA Free mobile app
i have found out how to fix this what you need to do is first flash a rom zip file get your stock recovery image for your device and flash it via twrp select install than install image find your stock recovery image then flash it then it will boot to the previous rom you tried to install then you can reflash twrp and all good