Hi. I just got the Moto x and I rooted the phone. I understand that with the new root method I have to load into recovery which will boot my phone and I'll be able to make changes. I want to modify my framework and change the nav bar dpi to 42. The thing I am worried about is if something goes wrong I could normally boot into recovery, Erase everything and start over. But the root method loads the OS when I try to use recovery. Is there any other way to reset the phone in case my modifications fail and I won't be able to load the OS anymore?
Sent from my XT1060 using XDA Premium 4 mobile app
ruben8448 said:
Hi. I just got the Moto x and I rooted the phone. I understand that with the new root method I have to load into recovery which will boot my phone and I'll be able to make changes. I want to modify my framework and change the nav bar dpi to 42. The thing I am worried about is if something goes wrong I could normally boot into recovery, Erase everything and start over. But the root method loads the OS when I try to use recovery. Is there any other way to reset the phone in case my modifications fail and I won't be able to load the OS anymore?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes. Either...
Code:
fastboot flash system system.img
fastboot flash boot boot.img
If that doesn't work (I got an error trying to fastboot the system) you can use RSDLite and the SBF file to reflash the entire stock image...
Tutorial
sbf files
The RSDLite method worked like a charm after I edited the XML like the tutorial says
Awesome thank you. I'll read more into and then I'll try to install that modified framework file.
Sent from my XT1060 using XDA Premium 4 mobile app
Or just use gravity box which does give you the ability to decrease the bottom navigation bar height
Sent on my Moto X injected with some sweet 4.3 JB
Really? That will definitely save me some time. Thanks. I'll try that first
Sent from my XT1060 using XDA Premium 4 mobile app
ruben8448 said:
Really? That will definitely save me some time. Thanks. I'll try that first
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No problem
Sent on my Moto X injected with some sweet 4.3 JB
flashallthetime said:
Or just use gravity box which does give you the ability to decrease the bottom navigation bar height
Sent on my Moto X injected with some sweet 4.3 JB
Click to expand...
Click to collapse
ruben8448 said:
Really? That will definitely save me some time. Thanks. I'll try that first
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, that's what I did. Works great, looks great. Made the landscape one even thinner for gaming.
_MetalHead_ said:
Yep, that's what I did. Works great, looks great. Made the landscape one even thinner for gaming.
Click to expand...
Click to collapse
same here, works and looks great
Related
There are several modes probably available to make Nexus 7 tablet mode. What am I confused with all these modes is which one is the possible the safest one?
...
What version of Android is your Nexus 7 running?
Paranoid android rom has tablet mode.
Sent from my HTC6435LVW using xda app-developers app
is there any way to add tablet mode in 4.2.2 w.o using any rom ??
I want cyanogenmode with tablet mode...
You can use this guide to set individual apps to tablet mode, very easy and painless to do as long as you have root: http://forum.xda-developers.com/showthread.php?t=2205834
Sent from XDA app
#sadegh# said:
is there any way to add tablet mode in 4.2.2 w.o using any rom ??
I want cyanogenmode with tablet mode...
Click to expand...
Click to collapse
Try this option. It is an app that you install that creates a flash able package that will give you tablet ui
Sent from my Nexus 7 using Tapatalk 2
hlxanthus said:
Try this option. It is an app that you install that creates a flash able package that will give you tablet ui
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You forgot to post the link.
eksasol said:
You forgot to post the link.
Click to expand...
Click to collapse
Um, yeah. Sorry about that!!
http://forum.xda-developers.com/showthread.php?p=38670671
Sent from my Nexus 7 using Tapatalk 2
The following mod worked very well for getting tablet UI on the stock odexed ROM:
http://forum.xda-developers.com/showthread.php?t=2176145
jbaumert said:
The following mod worked very well for getting tablet UI on the stock odexed ROM:
http://forum.xda-developers.com/showthread.php?t=2176145
Click to expand...
Click to collapse
Well, yeah for stock, my flashables will do it. But for cyanogenmod , aux's tabletizer is awesome!
Sent from my Nexus 7 using Tapatalk 2
Paranoid android rom has tablet mode.
thanks for all the response. I am quite happy with stock ROM actually, espesically newest Google update 4.2.2 has been great battery life and fixed a lot of issues. so I am kind of not into mode to flash a different ROM so just get tablet UI mode. I know you can modify build.prop, but again it does not quite works from app to app.
i was kind of asking around and see if anyone has some other solution, preferably a safe method that does not mess up system files (and OTA update fails when there's new release Google pushes!).
jazzespresso said:
thanks for all the response. I am quite happy with stock ROM actually, espesically newest Google update 4.2.2 has been great battery life and fixed a lot of issues. so I am kind of not into mode to flash a different ROM so just get tablet UI mode. I know you can modify build.prop, but again it does not quite works from app to app.
i was kind of asking around and see if anyone has some other solution, preferably a safe method that does not mess up system files (and OTA update fails when there's new release Google pushes!).
Click to expand...
Click to collapse
I answered your question, check my previous reply.
Sent from XDA app
I've tried fullscreen toggle+button savior, gmd gesture control and full!screen, finally I've managed to have a nice solution with Paranoid Android with pie control.
eksasol said:
I answered your question, check my previous reply.
Sent from XDA app
Click to expand...
Click to collapse
thanks. I am checking it out...quite interesting idea though. Did some research on that, and found this link http://forum.xda-developers.com/showthread.php?t=1574401..
I been looking to fix this annoying warning but cant find a solution for it if any.
Can someone helps me out with this?
thanks
Well there's a solution in the how to unlock your bootloader thread. Possibly in the op. Must be to hard to search today huh?
Sent from my PACMAN MATRIX HD MAXX
Try triangle away in Google market.
Sent from my Nexus 7 using xda app-developers app
That's only for Samsung devices.. :facepalm. And there's a very easy solution. Located right in the topic he used to unlock the bootloader.
Sent from my PACMAN MATRIX HD MAXX
Simple, just flash some other boot logo, I prefer the dual core technology one which comes with Mexican retail. .
Sent from my MB886 using xda app-developers app
http://d-h.st/JSx
fastboot flash logo logo.bin
If anyone wants the logo.bin, let me know...
Sent from my MB886 using xda app-developers app
EcHoFiiVe said:
If anyone wants the logo.bin, let me know...
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Why maintaining suspense? Here is the link for that logo... Download, extract and run this command in fastboot...
fastboot flash logo logo.bin
https://www.box.com/s/rvackslfpal2tukfv763
Sent from my MB886 using xda app-developers app
Aingaran said:
Why maintaining suspense? Here is the link for that logo... Download, extract and run this command in fastboot...
fastboot flash logo logo.bin
https://www.box.com/s/rvackslfpal2tukfv763
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Well damn.
Sent from my MB886 using xda app-developers app
Aingaran said:
Why maintaining suspense? Here is the link for that logo... Download, extract and run this command in fastboot...
fastboot flash logo logo.bin
https://www.box.com/s/rvackslfpal2tukfv763
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
loving that new logo
Me too. I'm excited about Motorola's future with Google if they start googleizing everything like this. Will be sweet.
Sent from my mb886 using Tapatalk 4 Beta
Yeah but this logo sucks...if the logo represents their future, then i'd say it looks bleak...
Youngunn2008 said:
Me too. I'm excited about Motorola's future with Google if they start googleizing everything like this. Will be sweet.
Sent from my mb886 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I found that flashing Mexican Retail removes the bootlader warning and never returned once flashing any ROM thereafter. Stock included
the problem is that I dont have a PC for me to do this my friend.
I think I have an image on my phone that I saved there and I think I like a lot for that boot image to be.
If someone can make me one with my image if is NOT too much to ask that will be great so I can flash it through CWM
SVLAN said:
the problem is that I dont have a PC for me to do this my friend.
I think I have an image on my phone that I saved there and I think I like a lot for that boot image to be.
If someone can make me one with my image if is NOT too much to ask that will be great so I can flash it through CWM
Click to expand...
Click to collapse
Nevermind this post...read yours wrong and thought you wanted the MR logo for CWM....did the dd instructions, but still....
download this post's attachment with your phone
rename logo.bin.zip to logo.bin
open Android Terminal Emulator and do the following commands
Code:
su
dd if=/sdcard/Download/logo.img of=/dev/block/mmcblk1p29
I think the default location for Downloads is /sdcard/Downloads, change the if=/sdcard/Download part of the command if it isn't.
This requires root, unlocked bootloader, and busybox being installed...not sure if stock has the dd command by default or not...hence the busybox recommendation. Plenty of busybox installers in the market.
skeevydude said:
Nevermind this post...read yours wrong and thought you wanted the MR logo for CWM....did the dd instructions, but still....
download this post's attachment with your phone
rename logo.bin.zip to logo.bin
open Android Terminal Emulator and do the following commands
Code:
su
dd if=/sdcard/Download/logo.img of=/dev/block/mmcblk1p29
I think the default location for Downloads is /sdcard/Downloads, change the if=/sdcard/Download part of the command if it isn't.
This requires root, unlocked bootloader, and busybox being installed...not sure if stock has the dd command by default or not...hence the busybox recommendation. Plenty of busybox installers in the market.
Click to expand...
Click to collapse
Thank you very much skeevy but it didnt worked for me even though it did find the file.
Sent from my LG-MS770 using xda premium
1) Backup your ROM
2)Clean flash MR
3)Clean and restore backup
here is the fix
This is the link http://www.droidrzr.com/index.php/t...f-the-bootloader-unlock-warning-with-1-click/
noobsaibot34 said:
This is the link http://www.droidrzr.com/index.php/t...f-the-bootloader-unlock-warning-with-1-click/
Click to expand...
Click to collapse
lol. I didn't even think about that one....My first unlocked boot I went....oh, a new boot logo .....hold up, hmm...I'll just flash a new one and a flasboot flash and we're off :victory: (that was a good day)
noobsaibot34 said:
This is the link http://www.droidrzr.com/index.php/t...f-the-bootloader-unlock-warning-with-1-click/
Click to expand...
Click to collapse
Thanks this did it for me.
One question to skeevy though about this subject.
I was wondering if anyone have tried to mess with the files. It should be a command file some where at the system that write the permissions or something to load the boot image.
Do you know what will be this file so we can try to make changes to it as resolution (Image size) ?
Reason I ask is because maybe we can change the image size like from 540x540 to 540x960 or something like that
after rootting my tmobile lg g flex today i can no longer use knock on to wake the device but i can still lock the phone by tapping the home screen has anyone else ran into this? is there a fix for it? i am still on 4.2.2 i did not want to do the upgrade yet in case it broke things even farther thanks for your help.
delurfangs said:
after rootting my tmobile lg g flex today i can no longer use knock on to wake the device but i can still lock the phone by tapping the home screen has anyone else ran into this? is there a fix for it? i am still on 4.2.2 i did not want to do the upgrade yet in case it broke things even farther thanks for your help.
Click to expand...
Click to collapse
Your problem is not from rooting. You may have inadvertently messed up something in your system partition. Try to lg flash tool back to stock.
PattyNYC said:
Your problem is not from rooting. You may have inadvertently messed up something in your system partition. Try to lg flash tool back to stock.
Click to expand...
Click to collapse
⬆⬆⬆⬆ Rooting cannot break knock on. I would try
1. Make sure it's on and toggle it either way
2. Factory reset after making a LG backup and dragging that file over to your computer. Then reset and drag the file back To the LGbackup folder on your phone. Restore from backup and the whole process shouldn't take more than 5min and you're phone will be exactly the way you had it setup still.
Sent from my LG-D950 using XDA Premium 4 mobile app
Did you by chance downgrade from 4.4 at some point?
Sent from my LG-D959 using Tapatalk
brittoking said:
⬆⬆⬆⬆ Rooting cannot break knock on. I would try
1. Make sure it's on and toggle it either way
2. Factory reset after making a LG backup and dragging that file over to your computer. Then reset and drag the file back To the LGbackup folder on your phone. Restore from backup and the whole process shouldn't take more than 5min and you're phone will be exactly the way you had it setup still.
Sent from my LG-D950 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah def try these first before restoring back to stock. Also some xposed modules can break features
You need to update your touch firmware in the hidden service menu. I could provide you with how to get there if you had mentioned what variant of the flex you have
Sent from my LG-LS980 using XDA Premium 4 mobile app
justinswidebody said:
You need to update your touch firmware in the hidden service menu. I could provide you with how to get there if you had mentioned what variant of the flex you have
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'd LOVE to know how to fix this issue on AT&T 950 variant. That's the only thing keeping me from flashing back to 4.2.2 so I can install custom recovery. If you know how to fix it when I downgrade from KK to JB I'd be forever grateful.
delurfangs said:
after rootting my tmobile lg g flex today i can no longer use knock on to wake the device but i can still lock the phone by tapping the home screen has anyone else ran into this? is there a fix for it? i am still on 4.2.2 i did not want to do the upgrade yet in case it broke things even farther thanks for your help.
Click to expand...
Click to collapse
Like justinwidebody suggested dial 3845#*959# then click "Settings" then "Update Touch Firmware"
or in Geners case I think you have to dial 3845#*950#
justinswidebody said:
You need to update your touch firmware in the hidden service menu. I could provide you with how to get there if you had mentioned what variant of the flex you have
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey Justin. I believe you have the sprint variant correct? If you do, what is the dialer code for it to fix knock on after downgrading?
Sent from my LG-LS995 using Tapatalk
Nybs31 said:
Hey Justin. I believe you have the sprint variant correct? If you do, what is the dialer code for it to fix knock on after downgrading?
Sent from my LG-LS995 using Tapatalk
Click to expand...
Click to collapse
3845#*your model number# so sprint should be 3845#*995#
Sent from my LG-D950 using XDA Premium 4 mobile app
Intub8 said:
3845#*your model number# so sprint should be 3845#*995#
Sent from my LG-D950 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry. Just tried. Doesn't work. Does it matter that I'm on kitkat?
Sent from my LG-LS995 using Tapatalk
Nybs31 said:
Sorry. Just tried. Doesn't work. Does it matter that I'm on kitkat?
Sent from my LG-LS995 using Tapatalk
Click to expand...
Click to collapse
Try this 5689#*995#
Nybs31 said:
Sorry. Just tried. Doesn't work. Does it matter that I'm on kitkat?
Sent from my LG-LS995 using Tapatalk
Click to expand...
Click to collapse
Actually the hidden menu on Sprint does not have the option to fix it. The work around is go into the general section and download my Sprint unlock Rom which is a att Rom. Then use the att dialer code and get into the hidden menu. Then go into recovery and run a back up. You will have knock on again.
Sent from my LG-LS980 using XDA Premium 4 mobile app
PattyNYC said:
Try this 5689#*995#
Click to expand...
Click to collapse
This does bring me to the hidden menu. But like Justin said, I do not have that feature in that menu.
Sent from my LG-LS995 using Tapatalk
justinswidebody said:
Actually the hidden menu on Sprint does not have the option to fix it. The work around is go into the general section and download my Sprint unlock Rom which is a att Rom. Then use the att dialer code and get into the hidden menu. Then go into recovery and run a back up. You will have knock on again.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have flashed the LS995 Rom that you provided to return to stock, and yet the knock on is not working. I dont know why.
Yes, the ATT Rom that you provided is great, it can repair the Knock by access the dialer code.
After I fix the knock on, and I use TWRP backup to restore System, Data, Cache, EFS, Boot, but the knock on is gone again on Sprint Rom.
Do you have any guide to restore back the knock?Or I perform a wrong way?
Or perhaps there's a way just to get the touch firmware from AT&T or AT&T Hidden menu LoL and install it to Sprint LS995 Rom.
I would appreciate your help.
justinswidebody said:
You need to update your touch firmware in the hidden service menu. I could provide you with how to get there if you had mentioned what variant of the flex you have
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Works really well on g flex 955 4.2.2 many thanks:good:
Request
justinswidebody said:
Actually the hidden menu on Sprint does not have the option to fix it. The work around is go into the general section and download my Sprint unlock Rom which is a att Rom. Then use the att dialer code and get into the hidden menu. Then go into recovery and run a back up. You will have knock on again.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
can you please post a link to the Sprint unlock Rom which is a att Rom" you are mentioning, i did not find it.. tried...
thanks.
Hi Everyone, I just want to share this easy steps to root Android L.
Note: Android L is a Developer preview, it is not stable as the KitKat version and it is using ART runtime only, so not all apps are compatible.
Update: The v2.01 release fixes some incompatibility issues with the Android "L" Preview. There is no binary update over v2.00.
Chainfire said:
v2.01 released - RELEASE NOTES
Click to expand...
Click to collapse
Zip file:
http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip
Google Play:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
Download the latest TWRP here:
http://techerrata.com/browse/twrp2/hammerhead
rename the "openrecovery-twrp-2.7.1.1-hammerhead.img" to "recovery.img"
Click to expand...
Click to collapse
I recommend backup all your data/files in a PC, to avoid data loss. And don't blame me if you have a bootloop or stuck at boot logo.
TRY IT AT YOUR OWN RISK.
Boot into bootloader
For TWRP format cache first
Code:
fastboot format cache
fastboot flash recovery recovery.img
Boot into recovery
Flash the SuperSU-v2.01.zip
Reboot
You now have root access.
Click to expand...
Click to collapse
Thanks to @Chainfire
Sent from my Nexus 5 using XDA Premium 4 mobile app
very nice
I have root access but cannot read/write to system. Is this a known issue at the moment?
Sent from my Nexus 5 using XDA Premium HD app
At first I had a problem with wiping the caches via TWRP, but I had to flash supersu first then wipe the caches and now everything is up and running. Great job!
Confirmed. This is working! Nice job!
Crackdroid said:
At first I had a problem with wiping the caches via TWRP, but I had to flash supersu first then wipe the caches and now everything is up and running. Great job!
Click to expand...
Click to collapse
Edit: Thanks!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Confirmed! Works like a charm. DPI changed finally!
Edit: Disregard this post.
Crackdroid said:
No problems with root explorer
Click to expand...
Click to collapse
Oh, Sorry for that wrong quote. Btw thanks!
Sent from my Nexus 5 using XDA Premium 4 mobile app
rongregoryred said:
Oh, Sorry for that wrong quote. Btw thanks!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No problem bro!
k3mik4l said:
I have root access but cannot read/write to system. Is this a known issue at the moment?
Sent from my Nexus 5 using XDA Premium HD app
Click to expand...
Click to collapse
Try using Root Explorer. I have no issues with the read/write on the system
Sent from my Nexus 5 using XDA Premium 4 mobile app
Everytime I try it says that the TWRP recovery image is too large. Any ideas?
I'm guessing this is the same as the other root method, where it roots your device, but some apps still don't work as root apps?
Titanium Backup is my main concern.
ArkAngel06 said:
I'm guessing this is the same as the other root method, where it roots your device, but some apps still don't work as root apps?
Titanium Backup is my main concern.
Click to expand...
Click to collapse
Yup. Pretty much. I'm having the same problem with TB.
Got stuck in a boot loop anyone have a idea?
Atleast put my name in there or something.
Dogie52 said:
Got stuck in a boot loop anyone have a idea?
Click to expand...
Click to collapse
Me too, stuck at Google, with the unlock symbol.
Does this wipe data
savoca said:
Atleast put my name in there or something.
Click to expand...
Click to collapse
I agree. I saw your post in the preview thread. I haven't used your process and boot.img yet, but will soon.
Give this man the recognition man, the least you could do.
Can anyone explain what this means?
Are those commands I put into cmd?
I usually flash images via my PC, which is currently down. Has anyone had experiences with image flashing in twrp? Stable? Any major problems I should be aware of?
Thanks
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
I usually flash images via my PC, which is currently down. Has anyone had experiences with image flashing in twrp? Stable? Any major problems I should be aware of?
Click to expand...
Click to collapse
The new version of TWRP 3.0.0.1 is able to flash img-files. But every IMG I have flashed was/is available as flashable zip-file.
For N6 you could look here: http://forum.xda-developers.com/showthread.php?t=3059493
NLBeev said:
The new version of TWRP 3.0.0.1 is able to flash img-files. But every IMG I have flashed was/is available as flashable zip-file.
For N6 you could look here: http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
Thanks I'll give it a read. I've been wanting to try N and being there are no flashable zips available yet through twrp I was considering flashing system and boot via twrp. Would it work?
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
Thanks I'll give it a read. I've been wanting to try N and being there are no flashable zips available yet through twrp I was considering flashing system and boot via twrp. Would it work?
Click to expand...
Click to collapse
I've not tried that myself. I would not try flashing N beta, as long there is no PC available to solve issues.
Better ask in this thread.
http://forum.xda-developers.com/showthread.php?t=3332599
Worse case I can get a laptop to fix it. Just looking for input on how well twrp image flashing works
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
Worse case I can get a laptop to fix it. Just looking for input on how well twrp image flashing works
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
works nearly perfectly, nearly because nothing is perfect
I've been using twrp for years now..
simms22 said:
works nearly perfectly, nearly because nothing is perfect
I've been using twrp for years now..
Click to expand...
Click to collapse
I've been using twrp since it was released, hate cwm n philz touch. I've always flashed zips, first image I flashed was to update twrp from twrp. Well looks like the flashathon is about to begin
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
I've been using twrp since it was released, hate cwm n philz touch. I've always flashed zips, first image I flashed was to update twrp from twrp. Well looks like the flashathon is about to begin
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I hated cwm and philz as well :angel:
anyways, I'm friends with @AmonRA, whose code twrp recovery was based on.
31ken31 said:
I usually flash images via my PC, which is currently down. Has anyone had experiences with image flashing in twrp? Stable? Any major problems I should be aware of?
Thanks
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Super stable. I've flashed many images with TWRP and never had an issue.
simms22 said:
I hated cwm and philz as well :angel:
anyways, I'm friends with @AmonRA, whose code twrp recovery was based on.
Click to expand...
Click to collapse
How well I remember that name
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
How well I remember that name
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
yea, his recovery was an all time important android thing at one point. if all android users only knew at this point. anyways, hes still an android user, but has gone on with his own life now-a-days