As always, you are responsible for your phone, and its warranty
I built this recovery because adb was not working in the official. I have submitted all my changes and I am sure this will be fixed shortly but until then I will put this here. Bassically I compiled the stock ND2 kernel with some small modifications and rebuilt the recovery.img with that. everything else should be exactly the same but honestly I did not test everything so please feel free to let me know.
***UPDATE 10/4/14***
Created version thats branded as kltespr, did this so CM11 is now able to auto update without modifying the CM package. Also, ADB still works. If anybody knows how to reduce the size of this image, please let me know since it is a little larger than the stock TWRP. Also built an image from the 2.8.0.1 base, which seems to have the same kernel from my original build to enable ADB, all I added here was the mod to kltespr so CM can update.
Use dd to install these images:
Newest Link 10/4/2014, working ADB and branded as kltespr so CM11 auto updates work:
Working ADB and tagged kltespr so CM11 auto updates work
Same as above but built from version 2.8.0.1 of TWRP
---Below here are all klte with working ADB, but CM11 fails to auto update complaining of wrong device---
Here is the link:
miked63017-openrecovery-twrp.img
Or try to grab it from my drive:
miked63017-openrecovery-twrp.img
Use odin to install this:
miked63017-openrecovery-twrp.tar.md5
Kernel Source Used:
https://github.com/miked63017/SM-G900P_ND2_KERNEL
This file won't download.
ChadH42 said:
This file won't download.
Click to expand...
Click to collapse
Added my google drive URL back to OP
Just got a test image from twrp, download should be up as official soon...
Sent from my SM-G900P using xda app-developers app
Excellent. Ty
Sent from my SM-G900P using Tapatalk
miked63017 said:
Just got a test image from twrp, download should be up as official soon...
Sent from my SM-G900P using xda app-developers app
Click to expand...
Click to collapse
whats the status on this is it offical yet.
Sent from my SM-G900P using Tapatalk
vinman12 said:
whats the status on this is it offical yet.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
I haven't heard anything back yet, but their test images worked as does the one in OP
Sent from my SM-G900P using xda app-developers app
Sweet thanks
Sent from my SM-G900P using Tapatalk
Hello, used to be HTC so I'm new to the Samsung thing. TWRP was the recommended recovery for the HTC devices. Is this recommended over the CWM recovery?
Thanks
talroot said:
Hello, used to be HTC so I'm new to the Samsung thing. TWRP was the recommended recovery for the HTC devices. Is this recommended over the CWM recovery?
Thanks
Click to expand...
Click to collapse
I like TWRP, but this is another option http://forum.xda-developers.com/showthread.php?t=2706253 . Honestly the only reason I prefer TWRP is probably because I've never used Philz, but I do hear good things about it.
miked63017 said:
I like TWRP, but this is another option http://forum.xda-developers.com/showthread.php?t=2706253 . Honestly the only reason I prefer TWRP is probably because I've never used Philz, but I do hear good things about it.
Click to expand...
Click to collapse
I have used all 3 available customer recoveries (TWRP, CWM, Philz) & I prefer TWRP. So me is easier and fool-proof.
Just saw this now, hope it can help with my mount/odex issues. Didnt have adb via recovery as an option before, looking forward to trying this. Thx mike
sleshepic said:
Just saw this now, hope it can help with my mount/odex issues. Didnt have adb via recovery as an option before, looking forward to trying this. Thx mike
Click to expand...
Click to collapse
Yeah its been handy. The kernel is huge though, do you mind if I pull in some of your commits to bring the size down?
Sent from my SM-G900P using XDA Free mobile app
miked63017 said:
Yeah its been handy. The kernel is huge though, do you mind if I pull in some of your commits to bring the size down?
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
My commits up there now wont help with that, I didnt push my defconfig.
You can easily change the compression and logging (less of a size diff) in either the defconfig in .../configs or through
$ menuconfig
prior to build
miked63017 said:
I like TWRP, but this is another option http://forum.xda-developers.com/showthread.php?t=2706253 . Honestly the only reason I prefer TWRP is probably because I've never used Philz, but I do hear good things about it.
Click to expand...
Click to collapse
Thanks, I went with TWRP since that's what I'm familiar with.
Just DL'd, says it's a Winzip file but my WinZip won't extract it.
Is it meant to be a .tar or Zip file?
thx
sleshepic said:
Just DL'd, says it's a Winzip file but my WinZip won't extract it.
Is it meant to be a .tar or Zip file?
thx
Click to expand...
Click to collapse
Its a flashable zip. I never use winzip so I'm not sure if it should be able to be extracted with it. I think its technically a 7zip zip file in windows, linux I just run 'unzip $FILENAME'. The google drive link is probably the most reliable, maybe try that one if you haven't already. If there are still problems I can re-upload, just let me know.
Sent from my SM-G900P using XDA Free mobile app
**UPDATE**
I take that back I only uploaded the recovery.img, I flash it with dd after putting it in /sdcard/
Code:
dd if=/sdcard/miked63017-openrecovery-twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Or if you just want to see whats in it, you can extract it like a normal boot.img.
Will try to put up a zip and/or tar tomorrow, honestly I thought they would have had an official one with adb working by now.
Flashify
Just use Flashify to push .img to your phone.
Ok with patched twrp I get this after flashing rom
Goes to boot into android, and keeps throwing up "unfortunately, SAE has stopped"
I belive that to be binary problem, is this correct and how to solve
Sent from my SM-G900P using Tapatalk
vinman12 said:
Ok with patched twrp I get this after flashing rom
Goes to boot into android, and keeps throwing up "unfortunately, SAE has stopped"
I belive that to be binary problem, is this correct and how to solve
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Haven't seen this before, what rom are you flashing?
Sent from my SM-G900P using XDA Free mobile app
Related
Hey guys we are working on our updater and initially only plan to support TWRP for auto install, so here ya go.
Install:
Code:
fastboot flash recovery recovery-passion-twrp-2.6.0.0-2013.07.10.img
MD5:
Code:
334f7c1298e34001500adf48f8d2e029 recovery-passion-twrp-2.6.0.0-2013.07.11.img
Download:
http://evervolv.com/get/recovery-passion-twrp-2.6.0.0-2013.07.11.img
Build from Evervolv ICS sources and kernel with unmodified TWRP
Evervolv/Kernel source links in signature
TWRP info: http://www.teamw.in/project/twrp2
Amazing! Million thanks making N1 still alive..
Sent from my Nexus One using xda app-developers app
How to install it using terminal emulator?
Sent from my Nexus One using xda app-developers app
~semsem~ said:
How to install it using terminal emulator?
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
If your rom has flash_image program (like evervolv) just:
Code:
$ su
# flash_image recovery /sdcard/recovery-passion-twrp-2.6.0.0-2013.07.10.img
texasice said:
If your rom has flash_image program (like evervolv) just:
Code:
$ su
# flash_image recovery /sdcard/recovery-passion-twrp-2.6.0.0-2013.07.10.img
Click to expand...
Click to collapse
Any chance of getting a flashable zip for this recovery?
Thanks for your hard work.
Sent from my GT-S5570 using xda app-developers app
Is it the same file provided by teamwin's website?
Enviado do meu Nexus One
I accidently disabled USB mass storage in the 7/10 build its fixed here http://evervolv.com/get/recovery-passion-twrp-2.6.0.0-2013.07.11.img
ponces said:
Is it the same file provided by teamwin's website?
Click to expand...
Click to collapse
Thank you, Texasice, for all you've done to keep our N1s alive! I'm planning on replacing my long-standing 4ext recovery with twrp (on a cm7 and cm10 phone). Like the quoted post, its not clear to me how your recovery differs, if it does, from teamwin's version.
CAL7 said:
Thank you, Texasice, for all you've done to keep our N1s alive! I'm planning on replacing my long-standing 4ext recovery with twrp (on a cm7 and cm10 phone). Like the quoted post, its not clear to me how your recovery differs, if it does, from teamwin's version.
Click to expand...
Click to collapse
Well i guess there isnt any. When i first searched i was unable to find a current version of TWRP so i build one.
For anyone wanting official it is here http://techerrata.com/browse/twrp2/passion
@texasice
TWRP 2.6.1.0 released. Do you think update?
respawn05 said:
@texasice
TWRP 2.6.1.0 released. Do you think update?
Click to expand...
Click to collapse
Give them a couple more days, if they don't release an official one i'll build one.
Can still be updated via goo manager !!
texasice said:
Give them a couple more days, if they don't release an official one i'll build one.
Click to expand...
Click to collapse
Same question for 2.7, Do you think update? :angel:
texasice said:
Give them a couple more days, if they don't release an official one i'll build one.
Click to expand...
Click to collapse
Will you update man?
Hey texasice, can you update ?
---------- Post added at 03:59 AM ---------- Previous post was at 03:54 AM ----------
texasice said:
Give them a couple more days, if they don't release an official one i'll build one.
Click to expand...
Click to collapse
can you update please?
I doubt it dude. Use 4ext recovery.
Sent from my One X
rabies876 said:
I doubt it dude. Use 4ext recovery.
Sent from my One X
Click to expand...
Click to collapse
I'm not a dude.
doubt what?
4ext is crap.
Alright, so I ported tripndroid to the DNA. Used cm's device tree, m7 kernel, and external/clang, and the muppets' vendor tree. Builds with no errors, flashes fine, runs great, but I got no root access. Superuser is installed, shows up under settings. Tried flashing busybox su package, koush's supersu 1.51 binary, and superuser. Nothing. Any ideas?
Sent from my HTC6435LVW using xda app-developers app
Isn't the latest supersu like 1.65? That's what I flashed on omnirom on my nexus 7 and I believe that's also the only one people were having success with.
Sent from my Droid DNA using Tapatalk Pro
jamiethemorris said:
Isn't the latest supersu like 1.65? That's what I flashed on omnirom on my nexus 7 and I believe that's also the only one people were having success with.
Sent from my Droid DNA using Tapatalk Pro
Click to expand...
Click to collapse
Yeah, you're right. I just searched for the update and that's the first that came up. I'll try it out.
Sent from my HTC6435LVW using xda app-developers app
Nope. Still no root. Tried flashing supersu and superuser.
danjull said:
Alright, so I ported tripndroid to the DNA. Used cm's device tree, m7 kernel, and external/clang, and the muppets' vendor tree. Builds with no errors, flashes fine, runs great, but I got no root access. Superuser is installed, shows up under settings. Tried flashing busybox su package, koush's supersu 1.51 binary, and superuser. Nothing. Any ideas?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I just took a look at their android_device_htc_m7. Wow, they are really not making any attempt to keep their changes in line with what CM is doing. I wouldn't be surprised if you get more surprises down the road...
In the 4.3 builds, superuser support requires that a daemon be running as root. This service is configured in init.superuser.rc which must get included by one of the etc/init*.rc scripts in the ramdisk.
The CM builds do this in vendor/cm which conveniently makes it apply to all devices. Tripndroid seems instead to have added the include directly to ramdisk/init.rc in their device tree. I suspect making the coresponding change to the init.rc on the DLX tree will fix the problem.
crpalmer said:
I just took a look at their android_device_htc_m7. Wow, they are really not making any attempt to keep their changes in line with what CM is doing. I wouldn't be surprised if you get more surprises down the road...
In the 4.3 builds, superuser support requires that a daemon be running as root. This service is configured in init.superuser.rc which must get included by one of the etc/init*.rc scripts in the ramdisk.
The CM builds do this in vendor/cm which conveniently makes it apply to all devices. Tripndroid seems instead to have added the include directly to ramdisk/init.rc in their device tree. I suspect making the coresponding change to the init.rc on the DLX tree will fix the problem.
Click to expand...
Click to collapse
Yup. You hit the nail right on the head. I finally found it. Thanks for looking into it!
If anyone wants to try it out I uploaded it here. If there's enough interest I might keep up with it.
Here's the M7 thread for the original build, if anyone wants to see the features. http://forum.xda-developers.com/showthread.php?t=2374404
danjull said:
Yup. You hit the nail right on the head. I finally found it. Thanks for looking into it!
If anyone wants to try it out I uploaded it here. If there's enough interest I might keep up with it.
Here's the M7 thread for the original build, if anyone wants to see the features. http://forum.xda-developers.com/showthread.php?t=2374404
Click to expand...
Click to collapse
Hey danjull I flashed it today and I love the themeing and it is very lite and clean, I could not send messages, kept sating message not sent. I am on Verizon and did not install any apps. Oh crap I did not install any gapps, did to? I will try again after u let me know what I did wrong. had to go back to nandroid for work. thanks for the port.
mopartonyg said:
Hey danjull I flashed it today and I love the themeing and it is very lite and clean, I could not send messages, kept sating message not sent. I am on Verizon and did not install any apps. Oh crap I did not install any gapps, did to? I will try again after u let me know what I did wrong. had to go back to nandroid for work. thanks for the port.
Click to expand...
Click to collapse
No gapps necessary. Mine is sending fine. I'm not using the stock messenger though.
Sent from my HTC6435LVW using xda app-developers app
danjull said:
No gapps necessary. Mine is sending fine. I'm not using the stock messenger though.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
ok I will try a few other apps and get back. other than that the rom is great
mopartonyg said:
ok I will try a few other apps and get back. other than that the rom is great
Click to expand...
Click to collapse
Yeah, I like it. It's pretty light on features. I mainly miss transparency settings for the status bar. I might try to work that in.
I'm using go SMS and I've been getting texts fine.
Sent from my HTC6435LVW using xda app-developers app
Hey Danjull are u going to start a thread for this rom? I think people will like it also. Are u going to update it when the other devices update? Thanks for this port
Okay people, we now have a fully functional CWMR
The Goods
Official builds from clockworkmod.com
And koush had been busy and hopefully has a few things fixed.
recovery-clockwork-6.0.4.4-hammerhead.img
Code:
sha256: 0a1f654df4dc5687762c679ea9da5d2a5706448fe8e99052e53a1c3f6940e38d
recovery-clockwork-touch-6.0.4.4-hammerhead.img
Code:
sha256: 04d3214635fc078644bb60fb2fff6481098fd5f1292638ed9292fd11a307836f
Able to be installed via ROM Manager now too.
My Builds w/ swipe/touch controls enabled
recovery-clockworkmod-6.0.5.0-hammerhead.img
To Install:
Code:
adb reboot bootloader
Code:
fastboot flash recovery recovery.img
NOTE: To access the backup via a root explorer, look in /mnt/clockworkmod.
Thanks to
Exel - for testing
ricky310711 - for making me use my noggin.
Anyone else that tested!!! I thank you!
DISCLAIMER: As always, I am not responsible for what you do with your device. USE AT OWN RISK!!!
XDA:DevDB Information
[RECOVERY] [CWMR] [Unofficial] Clockworkmod Recovery for the Nexus 5, Tool/Utility for the Google Nexus 5
Contributors
PlayfulGod
Version Information
Status: Stable
Current Stable Version: 6.0.4.6
Stable Release Date: 2014-01-08
Created 2013-11-04
Last Updated 2014-07-02
Reserved
screenshots provided by Exel.
Reserved
TESTED!!!
Hey Bro i just tested your CWM .....I LIKE THE RAINBOW MODE BTW
the only thing that didnt work was the ENTER
up/down work fine i just couldnt Select anything
good job though
Froz3nsolid said:
Hey Bro i just tested your CWM .....I LIKE THE RAINBOW MODE BTW
the only thing that didnt work was the ENTER
up/down work fine i just could Select anything
good job though
Click to expand...
Click to collapse
does swipe/gesture control work???
I/we prolly will have to do a custom recovery_keys.c to get the power button to select working.
And thanks, gweedo767 is the one to thank for rainbow mode and swipe control.
PlayfulGod said:
does swipe/gesture control work???
I/we prolly will have to do a custom recovery_keys.c to get the power button to select working.
And thanks, gweedo767 is the one to thank for rainbow mode and swipe control.
Click to expand...
Click to collapse
i was able to do UP/DOWN
but the enter doesnt work though i tried swiping to the right anywhere on the screen and .....................nothing
question if i use an app like flashify it should work right
im trying to flash a kernel cause the battery life is a bit disappointing
Froz3nsolid said:
i was able to do UP/DOWN
but the enter doesnt work though i tried swiping to the right anywhere on the screen and .....................nothing
question if i use an app like flashify it should work right
im trying to flash a kernel cause the battery life is a bit disappointing
Click to expand...
Click to collapse
should be able to flash a boot.img just like you did recovery. Just sub in
Code:
fastboot flash boot yourboot.img
instead.
Oh, you are on here!
Hey, bud. Still waiting for my nexus.. well, waiting to get off work. xD
PlayfulGod said:
should be able to flash a boot.img just like you did recovery. Just sub in
Code:
fastboot flash boot yourboot.img
instead.
Click to expand...
Click to collapse
i know but i cant seem to find the .IMG in the devs OP all i find are .ZIPS
im trying to unzip it to see if i can find the .img in there
Froz3nsolid said:
i know but i cant seem to find the .IMG in the devs OP all i find are .ZIPS
im trying to unzip it to see if i can find the .img in there
Click to expand...
Click to collapse
Yea the img is prolly in the zip. He prolly has users using TWRP to flash it.
Ah......but i hate twrp imma ask if he can provide link to .img
Sent from my Nexus 5 using XDA Premium 4 mobile app
Froz3nsolid said:
Ah......but i hate twrp imma ask if he can provide link to .img
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
pull it from the zip
Zip filed is corrupted ?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Good effort, but unfortunately select option not workin therefore CWM unusable..
Thank you and keep up the good work..
PlayfulGod said:
pull it from the zip
Click to expand...
Click to collapse
Question, does TWRP have an option to select using the buttons or is it all touch?
Maybe you can see on there, don't really know.. never used TWRP.
Exel said:
Question, does TWRP have an option to select using the buttons or is it all touch?
Maybe you can see on there, don't really know.. never used TWRP.
Click to expand...
Click to collapse
Look on the TWRP OP is its on the same page that you found this
This is for.CWM
Sent from my Nexus 5 using XDA Premium 4 mobile app
fazzieng said:
Good effort, but unfortunately select option not workin therefore CWM unusable..
Thank you and keep up the good work..
Click to expand...
Click to collapse
yes I realize that and thanks, still working on it.
Exel said:
Question, does TWRP have an option to select using the buttons or is it all touch?
Maybe you can see on there, don't really know.. never used TWRP.
Click to expand...
Click to collapse
Troy_Dees just added what he needed for TWRP and doesnt appear to have touch much of the stock code itself. Will have a closer look tho. And afaik TWRP is touch only.
Froz3nsolid said:
Look on the TWRP OP is its on the same page that you found this
This is for.CWM
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, was actually wondering about the enter button not working, not really about TWRP.
PlayfulGod said:
Troy_Dees just added what he needed for TWRP and doesnt appear to have touch much of the stock code itself. Will have a closer look tho. And afaik TWRP is touch only.
Click to expand...
Click to collapse
Hm, then would an alternative be trying to build ClockworkMod Recovery Touch until the button issues are solved?
Just throwing ideas out.
As mentioned before the select key does not work, also the resolution is huge and this makes the writing in recovery super small, the few lines available are like 3mm in height and almost impossible to read
Exel said:
Thanks, was actually wondering about the enter button not working, not really about TWRP.
Hm, then would an alternative be trying to build ClockworkMod Recovery Touch until the button issues are solved?
Just throwing ideas out.
Click to expand...
Click to collapse
I cant build touch until its forked into CM repos. I dont have access to koush's touch src.
hutzdani said:
As mentioned before the select key does not work, also the resolution is huge and this makes the writing in recovery super small, the few lines available are like 3mm in height and almost impossible to read
Click to expand...
Click to collapse
K that can be addressed.
Also new img uploaded, same link.
[ROM][v500][awifi] Omni 4.4 build w/ multiwindow
Code:
*** Disclamer
This is only for the v500 WIFI-only model (product name awifi)
NOTE: I have not tested this build myself because I don't own an LG G Pad tablet (yet).
If you are afraid, then wait for someone else to test it
Introduction
I'm basically just curious and willing to learn, and fill in the gap when there is a gap (eg no one compiling a custom ROM/kernel for a device, and sources/device-tree/kernel are available, I'll try to do it)
I try to post steps/sources so that other people can learn/follow as well.
If someone wants to take over compiling this ROM, go ahead.
If I don't update the build for a long time, PM me to remind me.
Click to expand...
Click to collapse
Installation instructions
Need custom recovery (TWRP, ...?)
Do nandroid backup in recovery
Wipe dalvik/cache/system
This ROM is only for v500 wifi-version only.
Flash this OMNI 4.4.2 ROM. boot.img will be LOKI-patched during flash.
(optional) Flash gapps-4.4 (find it yourself), flash SuperSU (find it yourself)
reboot to ROM
Click to expand...
Click to collapse
Download
Current ROMs:
[20140514] pure Omni | DL: http://d-h.st/pwn
[20140514] Omni w/ multi window patch #18 | DL: http://d-h.st/vXX
Flashable zips:
[20140514] multiwindow flashable zip - someone teach me how to do this?
(flash this zip on top of a pure Omni ROM)
Click to expand...
Click to collapse
Bugs?
What doesn't work?
- Anything that's broken on CM11 is broken here too
- You tell me
Click to expand...
Click to collapse
Thanks To/Credits
Code:
cyanogenmod dev team for source/kernel build-up
omni team for omni source
drgravy for TWRP
anyone else who contributed to the development of v500/v510/vk810
Sources:
https://github.com/ngvincent/vendor_lge.git (branch=kk4.4), forked from cmbroms
https://github.com/CyanogenMod/android_kernel_lge_v500.git (branch=cm11.0), default CM11.0 kernel
https://github.com/ngvincent/android_device_lge_v500.git (branch=omni-4.4), default CM11.0 devicetree with some omni changes​
Click to expand...
Click to collapse
​
Thank you for this!! Been using this on my phone for months and dying to have it on my tablet :victory: :laugh:
Edit: Installation went perfectly and no issues so far!
uploaded omni 4.4 w/ multiwindow patch
let me know if it works / something is broken
[20140514] Omni w/ multiwindow patch #18 | DL: http://d-h.st/vXX
Is rooted?
AdThiago said:
Is rooted?
Click to expand...
Click to collapse
I don't believe OmniROM is pre-rooted
flash SuperSU after rom if you want root....
// still trying to find a decently priced lg g pad, don't own one yet
Work Great Btw. The multi-window also seems to work fine from the little testing I did.
I just got this tablet myself.
HiddenSanctum said:
Work Great Btw. The multi-window also seems to work fine from the little testing I did.
I just got this tablet myself.
Click to expand...
Click to collapse
last I tried multi-window (on another device), i believe each "side" of the split-screen is "standalone"
(i.e. you have google maps on the left side of the screen, gmail on right. If you try to click on a hyperlink on google maps, chrome (or whatever your default browser is) will open up on the left replacing google maps)
wonder if it's possible to open chrome up on the right, so you get "better" multi-window/multi-tasking because your original app and "newly launched" apps are running side by side
paperWastage said:
last I tried multi-window (on another device), i believe each "side" of the split-screen is "standalone"
(i.e. you have google maps on the left side of the screen, gmail on right. If you try to click on a hyperlink on google maps, chrome (or whatever your default browser is) will open up on the left replacing google maps)
wonder if it's possible to open chrome up on the right, so you get "better" multi-window/multi-tasking
Click to expand...
Click to collapse
I have been rooting and installing various roms on all of my android phones but for some unknown reason I am wanting to be over protective with my tablet so I am sorry for asking but,
What were you running before updating?
I know it lists what you must have before installing but how did you do it?
Utakos said:
I have been rooting and installing various roms on all of my android phones but for some unknown reason I am wanting to be over protective with my tablet so I am sorry for asking but,
What were you running before updating?
I know it lists what you must have before installing but how did you do it?
Click to expand...
Click to collapse
i don't own a LG G Pad
as long as you already have a custom recovery installed (which requires initial root), and have a nandroid backup on the device itself AND on your computer, you should be fine
ask the other people who've already flashed it
I'm using almost the same device tree from CM11 (only need to convert the CM file structure-> omni file structure, no other changes), so there shouldn't be any unexpected surprises when you flash the ROM
I flashed this Last night and did flash the super user zip but I still diff not have root doff I miss a step?
Sent from my LG-V500 using XDA Premium 4 mobile app
xyojimbox said:
I flashed this Last night and did flash the super user zip but I still diff not have root doff I miss a step?
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
which package did you use?
http://docs.omnirom.org/Installing_Omni_on_your_device
Omni devs recommend Chainfire SuperSU
I stupidly did not flash St along with the multi window version and gapps. Now I can't get SU to work from the playstore. It says it needs to update binary but fails when it tries. I assume I need to flash the SU zip from my twrp recovery?
Anyone know how to get into recovery without root access? I was using a app that only works with root.
Sent from my Nexus 7 using Tapatalk
eagles5 said:
I stupidly did not flash St along with the multi window version and gapps. Now I can't get SU to work from the playstore. It says it needs to update binary but fails when it tries. I assume I need to flash the SU zip from my twrp recovery?
Anyone know how to get into recovery without root access? I was using a app that only works with root.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Boot into recovery via buttons LG G pad: http://youtu.be/uo3YfszOPsQ
Sent from my Nexus 5 using Tapatalk
Yep I can get into recovery. For some reason trip wasn't able to install the latest supersu zip. Said it couldn't open it. So I'll try an older zip tonight.
I guess I still have root but I don't have root access due to lack of super user installed?
Sent from my Nexus 5 using Tapatalk
---------- Post added at 02:59 PM ---------- Previous post was at 02:06 PM ----------
One thing I'm wondering. Is really flashing supersu through twrp sufficient to gain root? I've only hooked up my devices to run batch scripts in order to gain root so the idea of gaining root merely through flashing a zip is new to me.
Sent from my Nexus 5 using Tapatalk
eagles5 said:
Yep I can get into recovery. For some reason trip wasn't able to install the latest supersu zip. Said it couldn't open it. So I'll try an older zip tonight.
I guess I still have root but I don't have root access due to lack of super user installed?
Sent from my Nexus 5 using Tapatalk
---------- Post added at 02:59 PM ---------- Previous post was at 02:06 PM ----------
One thing I'm wondering. Is really flashing supersu through twrp sufficient to gain root? I've only hooked up my devices to run batch scripts in order to gain root so the idea of gaining root merely through flashing a zip is new to me.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
TWRP should also warn you when you reboot TWRP after flashing a ROM without SuperSU...
Flashing the root update.zip will gain root.... TWRP/adb/fastboot is a lot easier than running batch scripts that use exploits (unless you are stock without TWRP, and you need exploit like Towelroot to intially root)
paperWastage said:
TWRP should also warn you when you reboot TWRP after flashing a ROM without SuperSU...
Flashing the root update.zip will gain root.... TWRP/adb/fastboot is a lot easier than running batch scripts that use exploits (unless you are stock without TWRP, and you need exploit like Towelroot to intially root)
Click to expand...
Click to collapse
Yep I got it straightened out. Used a slightly older Supersu zip and it worked great.
Sent from my Nexus 5 using Tapatalk
All work
Only mobile data doesnt work
This isnt flashble zip
Use with multirom
Install
Extract folder to TWRP\BACKUPS\0a6300bf
Reboot in recovery
Add second rom from backup and use this backup
CLEAN ROM!!!!
https://docs.google.com/file/d/0B3g-BYIH1skIWmJNWlNEdmxPRlk/edit?usp=docslist_api
Kernel
Works fine with elementalx 3.0
https://www.androidfilehost.com/?fid=95784891001602494
Sent from my Nexus 7 LTE using XDA Free mobile app
Downloading now.
You probably want to pull this down and do a factory wipe on it then reupload it. It was signed into your google account and was in Russian or some other language.
Take it down, NOW!
And change your Google password.
Yeah man, take it down and restore data before reuploading it... It's signed in with your Google account!
Link is removed, user notified.
Thanks folks for looking out for fellow users! Much appreciated!
Kudos!
MD
I believe someone could open up his Drive app and turn off sharing, though
good news for deb, waiting for reupload without personal data
Woah I guess OP got a little too excited at the thought of being able to share this. Thanks though, patiently waiting for re upload. [emoji4]
New link
https://docs.google.com/file/d/0B3g-BYIH1skIWmJNWlNEdmxPRlk/edit?usp=docslist_api
Sent from my Nexus 7 using XDA Free mobile app
The stock kernel works fine with this?
Aashrey99 said:
The stock kernel works fine with this?
Click to expand...
Click to collapse
I tried elementalx and I had random reboots
Since the kernel is in the archive works fine
I used translator sorry
Oh ok. I'm still downloading the file. I don't intend to use a custom kernel with this build.
Just installed. Seems solid so far. Still downloading so many apps.
d11dog11 said:
Just installed. Seems solid so far. Still downloading so many apps.
Click to expand...
Click to collapse
How is the performance compared to previous one?
htb2050 said:
How is the performance compared to previous one?
Click to expand...
Click to collapse
Yes thery good
With elementalx very smooth and faster
Sent from my Nexus 7 using XDA Free mobile app
htb2050 said:
How is the performance compared to previous one?
Click to expand...
Click to collapse
Seems great to me. Never flashed anything on this tab before today so nothing to compare it too.
Doesn't appear in the TWRP multirom backup install for me after copying to the storage.
What am I doing wrong?
Ambious said:
Doesn't appear in the TWRP multirom backup install for me after copying to the storage.
What am I doing wrong?
Click to expand...
Click to collapse
in which folder you unzipped files
Sent from my Nexus 7 using XDA Free mobile app
Ansanen said:
in which folder you unzipped files
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I figured it out eventually (changed it to the folder with my other backups rather than the one states in op), but then after flashing/restoring it wouldn't boot.
I'll just wait a couple of days for an official flashable zip