So noob question, I've been searching for hours and can't get a straight answer. I updated my phone last night from v10G ics to v20D jb is it possible to root after the update or?
Sent from my LG-P769 using xda app-developers app
djak3 said:
So noob question, I've been searching for hours and can't get a straight answer. I updated my phone last night from v10G ics to v20D jb is it possible to root after the update or?
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
I think we need a single thread titled, "JB, V20, Root". It seems that people are not taking the time to search and read. Maybe it is because things are getting messy around here.
djak3: Here you go: http://forum.xda-developers.com/showthread.php?t=2173465
I agree with you kevev
Yeah I definitely agree like I said I've been reading all day and its all over the place
Sent from my LG-P769 using xda app-developers app
djak3 said:
Yeah I definitely agree like I said I've been reading all day and its all over the place
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
I just posted semi-simple instructions here: http://forum.xda-developers.com/showthread.php?p=40898425#post40898425
It may help.
Would u know if theirs anyway to downgrade from 20d back to 10g?
Sent from my LG-P769 using xda app-developers app
djak3 said:
Would u know if theirs anyway to downgrade from 20d back to 10g?
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
I am not 100% sure. But I think you can just flash the 10g KDZ.
Yes you can downgrade from v20D to v10g via offline kdz method.
Sent from my LG-P769 using xda app-developers app
Why downgrade to 10g?
I got the JB upgrade, didn't notice much difference. but I don't like Qslide. Looks like only to get ride of it is to root first.
djak3 said:
Would u know if theirs anyway to downgrade from 20d back to 10g?
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
value99 said:
Why downgrade to 10g?
I got the JB upgrade, didn't notice much difference. but I don't like Qslide. Looks like only to get ride of it is to root first.
Click to expand...
Click to collapse
since v20d isnt rootable at this time it makes since to downgrade back to v10g root, use voodoo ota root keeper and upgrade back to v20d JB
Makes sense
Thanks
djak3 said:
since v20d isnt rootable at this time it makes since to downgrade back to v10g root, use voodoo ota root keeper and upgrade back to v20d JB
Click to expand...
Click to collapse
I tired Lelus method.
I tried the Lelus method and I always get stuck. I hit the web upgrade test to flash V10G_00.KDZ to my phone in S/W upgrade mode via the Marwin mod. followed the steps, downloaded drivers, enabled the server and every single time it just says my phone is up to date and then if I click start upgrade it actually seems like it's doing something, then it freezes and crashes. I have reread it enough times to say **** reading it. I'm guessing that for some odd reason I have missed something EVEN though I have EVERYTHING and did EVERYTHING those post have told me to do... can't flash there for I can't root. kinda butt hurt tbh. this is most liekly the last place for this but I don't wanna be attatched at the end of a 15 page thread where my questions won't be answered
hollow2318 said:
I tried the Lelus method and I always get stuck. I hit the web upgrade test to flash V10G_00.KDZ to my phone in S/W upgrade mode via the Marwin mod. followed the steps, downloaded drivers, enabled the server and every single time it just says my phone is up to date and then if I click start upgrade it actually seems like it's doing something, then it freezes and crashes. I have reread it enough times to say **** reading it. I'm guessing that for some odd reason I have missed something EVEN though I have EVERYTHING and did EVERYTHING those post have told me to do... can't flash there for I can't root. kinda butt hurt tbh. this is most liekly the last place for this but I don't wanna be attatched at the end of a 15 page thread where my questions won't be answered
Click to expand...
Click to collapse
Hey buddy. Try to flash with the phone booted into android. In the top right corner of the flash tool there is a box with 3 options like Emergency and Diag and 1 other. Try Diag instead of emergency with your phone booted up.
Tablechair said:
Hey buddy. Try to flash with the phone booted into android. In the top right corner of the flash tool there is a box with 3 options like Emergency and Diag and 1 other. Try Diag instead of emergency with your phone booted up.
Click to expand...
Click to collapse
Do I still follow the instruction and do Web upgrade test instead of start upgrade? I would love to root this phone, currently on 20D since I prematurly OTA updated to V10G, so I want to flash backwards and root using Lelus's method. thank you for the response!!
---------- Post added at 08:00 PM ---------- Previous post was at 07:37 PM ----------
Tablechair said:
Hey buddy. Try to flash with the phone booted into android. In the top right corner of the flash tool there is a box with 3 options like Emergency and Diag and 1 other. Try Diag instead of emergency with your phone booted up.
Click to expand...
Click to collapse
Okay so I put it in LG software mode, left it on (or booted into android) then I switched it to DIAG and clicked my V10G_00.kdz file. hit web upgrade test, then upgrade start, it loaded up LGMobile support tool and still says completely up to date. should I click start upgrade (skipping the upgrade web test) because that gets me no where. My device manager shows all 3 entries in it. So I am a little stumped..
hollow2318 said:
Do I still follow the instruction and do Web upgrade test instead of start upgrade? I would love to root this phone, currently on 20D since I prematurly OTA updated to V10G, so I want to flash backwards and root using Lelus's method. thank you for the response!!
---------- Post added at 08:00 PM ---------- Previous post was at 07:37 PM ----------
Okay so I put it in LG software mode, left it on (or booted into android) then I switched it to DIAG and clicked my V10G_00.kdz file. hit web upgrade test, then upgrade start, it loaded up LGMobile support tool and still says completely up to date. should I click start upgrade (skipping the upgrade web test) because that gets me no where. My device manager shows all 3 entries in it. So I am a little stumped..
Click to expand...
Click to collapse
did you add
Code:
127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com
to hosts file and run shttps ?
Lelus said:
did you add
Code:
127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com
to hosts file and run shttps ?
Click to expand...
Click to collapse
I did, here.
"# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
# 127.0.0.1 csmg.lgmobile.com
# 127.0.0.1 csmgdl.lgmobile.com
##""
that is what my host file looks like, and I had the small server running and windows enbler. ALL in windows service pack 3 compat mode. also everything was run as Admin. this is why I am confused. I did all that got all the fiels, installed all the drivers for every mode including the S/W upgrade mode I am at a loss mate I just wish I could go back to V10E and use Bin4ry's way but I was noob, and OTA updated.. like a fool XD
hollow2318 said:
I did, here.
"# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
# 127.0.0.1 csmg.lgmobile.com
# 127.0.0.1 csmgdl.lgmobile.com
##""
that is what my host file looks like, and I had the small server running and windows enbler. ALL in windows service pack 3 compat mode. also everything was run as Admin. this is why I am confused. I did all that got all the fiels, installed all the drivers for every mode including the S/W upgrade mode I am at a loss mate I just wish I could go back to V10E and use Bin4ry's way but I was noob, and OTA updated.. like a fool XD
Click to expand...
Click to collapse
remove # in from of all 127.0.0.1
hollow2318 said:
I did, here.
"# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
# 127.0.0.1 csmg.lgmobile.com
# 127.0.0.1 csmgdl.lgmobile.com
##""
that is what my host file looks like, and I had the small server running and windows enbler. ALL in windows service pack 3 compat mode. also everything was run as Admin. this is why I am confused. I did all that got all the fiels, installed all the drivers for every mode including the S/W upgrade mode I am at a loss mate I just wish I could go back to V10E and use Bin4ry's way but I was noob, and OTA updated.. like a fool XD
Click to expand...
Click to collapse
It took me a few tries to do the lelus method.. but im sure u will get it.. if u can maybe u can back up ur phone.. factory reset it and do the lelus method on a different computer step by step.. ur not actually online updating when using lelus method.. if u get that server is offline connection error make sure ur hosts files are correct and u have restarted ur pc
aarongotgame said:
It took me a few tries to do the lelus method.. but im sure u will get it.. if u can maybe u can back up ur phone.. factory reset it and do the lelus method on a different computer step by step.. ur not actually online updating when using lelus method.. if u get that server is offline connection error make sure ur hosts files are correct and u have restarted ur pc
Click to expand...
Click to collapse
I am not even trying to root yet, I need to flash backwards to V10G cause I am currently running V20D. I am just trying to reflash my rom and I will remove the # from infront of the 127.... I hope that makes a difference. it says I am online too. I might need to use a differnent comp but I don't see how that will help haha.. I am not really all that new to flashing and rooting, I had a 4G blaze and rooted and flashed the b'jesus out of it. plus my Kyocera. but the LG optimus is a pain in the ass... forgive my language but yeah it is.
SO I will try removing the # from host. should I try this in Emergency mode(phone in upgrade mode) or Diag (booted into android) also, does the web upgrade test actually flash the phone, or should I juct click start upgrade; cause it's always telling me it's up to date when it pulls up the LG mobile support tool via web upgrade test. Sorry for the spoon feeding.
hollow2318 said:
I am not even trying to root yet, I need to flash backwards to V10G cause I am currently running V20D. I am just trying to reflash my rom and I will remove the # from infront of the 127.... I hope that makes a difference. it says I am online too. I might need to use a differnent comp but I don't see how that will help haha.. I am not really all that new to flashing and rooting, I had a 4G blaze and rooted and flashed the b'jesus out of it. plus my Kyocera. but the LG optimus is a pain in the ass... forgive my language but yeah it is.
SO I will try removing the # from host. should I try this in Emergency mode(phone in upgrade mode) or Diag (booted into android) also, does the web upgrade test actually flash the phone, or should I juct click start upgrade; cause it's always telling me it's up to date when it pulls up the LG mobile support tool via web upgrade test. Sorry for the spoon feeding.
Click to expand...
Click to collapse
I never added a # to my hosts files btw.. follow this hosts text word for word.. copy and paste if needed because the two extra #'s at the bottom of your text are not in mine and the #'s next to the added text BE SURE TO RESTART UR PC AFTER FIXING HOSTS FILES
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com
I was going to factory reset my phone before upgrading to v20d instead of after and now my wifi isnt connecting so it wont OTA update so right now im actually flashing 10g on my phone with lelus method as we speak.. ill let u know what happens.. and some people tried on a pc and it didnt work and when they tried on a different pc it worked. only reason i suggested it
UPDATE: IVE JUST FINISHED FLASHING 10G ON MY PHONE.. I REMEMBER THERE BEING A FILE YOU HAD TO ADD WHEN YOUR PHONE UPDATED TO A CERTAIN PERCENT WHEN I FLASHED TO ROOT THE FIRST TIME. MAYBE THAT WAS ONLY FOR ROOT AND THATS WHY IT SEEMED TO BE REMOVED FROM THE GUIDE.. IM NOT SURE
Related
All you need to do is extract this and run the "runme.bat"
Code:
echo off
cls
echo *********************************
echo * Please plug the USB into Nook *
echo *********************************
pause
adb kill-server
adb devices
echo *******************
echo * Blocking Update *
echo *******************
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push block-1.1.sh /system/media
adb shell sh /system/media/block-1.1.sh
ping -n 5 127.0.0.1 >NUL
echo Success
adb reboot
adb kill-server
echo *****************************
echo * You nook is rebooting *
echo * Disconnect the USB cable! *
echo * Wait until rebooted... *
echo * *
echo * BN 1.1 Update Blocked *
echo * *
echo *****************************
pause
exit
Download
Can you release an "Undo" script as well that undoes what this does?
I was under the impression that the otacert rename was a dud and the build.prop was very questionable???
found this and replied to the discussion on the subject.
IMO, Until the OTA is squashed we are going to have a repetitive debockle of blowing up everyones rooted work and would think addressing this would be of significant value:
-cut-n-paste-
I was wondering what you folks thought of this 'prevent' 1.1 hack??
http://forum.xda-developers.com/showthread.php?t=930477
seems reasonable to me, adding:
127.0.0.1 csqaint.barnesandnoble.com
(looks to be the primary check for updates?)
and
127.0.0.1 bncs.barnesandnoble.com
(just for good measure but might have unwanted consequences?)
to /etc/hosts file
I would personally like to be able to put an end to this 'forced' OTA update behind us and be able to sideload any updates from bn manually at our convienence in the future.
how bout u??????
In reviewing the script it appears to apply the build.prop spoof update?
I thought this was questionalble in overall effectiveness?? and even if it worked would have to be reapplied after every update from bn???
I noticed an interesting reply from ixampl as follows:
What I did when the first scare of an update arose was:
a) Checked in /data/data/com.bn.nook.devicemanager/databases/ for an sql file
b) Pulled the sql file.
c) Dump its contents with sqlite3.
d) In it there's an entry for OTAs... with value "auto"
e) Changed that value to "manual"
f) Pushed the modified database file to the device.
I never got any OTA updates. Still on first OS version.
This is exactly what I'm lookin for, a permenant block unless of course the database update got reversed back to auto?????
is this normal? i go into settings/device info/about your nook color. it still shows 1.0.1? where do i have to go to verify this is blocked?
C:\NC - Auto Config Script 1.0.1>adb push block-1.1.sh /system/media
32 KB/s (506 bytes in 0.015s)
C:\NC - Auto Config Script 1.0.1>adb shell sh /system/media/block-1.1.sh
cp: not found
sed: not found
sed: not found
sed: not found
sed: not found
john10101 said:
is this normal? i go into settings/device info/about your nook color. it still shows 1.0.1? where do i have to go to verify this is blocked?
C:\NC - Auto Config Script 1.0.1>adb push block-1.1.sh /system/media
32 KB/s (506 bytes in 0.015s)
C:\NC - Auto Config Script 1.0.1>adb shell sh /system/media/block-1.1.sh
cp: not found
sed: not found
sed: not found
sed: not found
sed: not found
Click to expand...
Click to collapse
You dont have busybox installed on the NC?
bonzer2u said:
In reviewing the script it appears to apply the build.prop spoof update?
I thought this was questionalble in overall effectiveness?? and even if it worked would have to be reapplied after every update from bn???
I noticed an interesting reply from ixampl as follows:
What I did when the first scare of an update arose was:
a) Checked in /data/data/com.bn.nook.devicemanager/databases/ for an sql file
b) Pulled the sql file.
c) Dump its contents with sqlite3.
d) In it there's an entry for OTAs... with value "auto"
e) Changed that value to "manual"
f) Pushed the modified database file to the device.
I never got any OTA updates. Still on first OS version.
This is exactly what I'm lookin for, a permenant block unless of course the database update got reversed back to auto?????
Click to expand...
Click to collapse
Can you elaborate a little further on what commands you used so I might be able to add it into a script.
i dont think so... what installs busybox?
No offense, but this isn't a worry any more anyway. We already have a CWM flashable update.zip that updates you to 1.1, but does not harm your root or installed aps. Why are people bothering with all this "blocking" nonsense?
From this thread:
http://forum.xda-developers.com/showthread.php?t=874871
Attached is a working sqlite3 binary. Copy it to /system/bin and you will be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
-----------------------------------------------------------------------------
And I found a sqlite3 sample that will need to be edited like somthing as follows:
In your terminal,
$ adb pull /data/data/com.bn.nook.devicemanager/databases/settings.db settings.db
$ sqlite3 settings.db
sqlite> update secure set value='manual' where name='an entry for OTAs???-Dont know the parameter here'
;
sqlite> .q
$ adb push /data/data/com.bn.nook.devicemanager/databases/settings.db settings.db
$ adb reboot
Hope this helps, I dont know the input name for placeholder.
xboxexpert said:
You dont have busybox installed on the NC?
Click to expand...
Click to collapse
Ok i installed busy box off the market, and ran the script!!! success. when i rebooted it told me that 1.1.0 has been installed. and it now shows 1.1.0 in the about.
i suggest noting busy box in the original post.
Divine_Madcat said:
No offense, but this isn't a worry any more anyway. We already have a CWM flashable update.zip that updates you to 1.1, but does not harm your root or installed aps. Why are people bothering with all this "blocking" nonsense?
Click to expand...
Click to collapse
not everyone wants to upgrade to 1.1, or has cwm installed.
john10101 said:
Ok i installed busy box off the market, and ran the script!!! success. when i rebooted it told me that 1.1.0 has been installed. and it now shows 1.1.0 in the about.
i suggest noting busy box in the original post.
Click to expand...
Click to collapse
It says 1.1 is installed but its really not. (Spoofed it)
john10101 said:
not everyone wants to upgrade to 1.1, or has cwm installed.
Click to expand...
Click to collapse
Uh... why? What is there about 1.1 not to want? And if you are ok with doing all of this to block an update, there is no reason not to have CWM (which is quite stable). Sorry, but this really is all just wasted effort..
Divine_Madcat said:
Uh... why? What is there about 1.1 not to want? And if you are ok with doing all of this to block an update, there is no reason not to have CWM (which is quite stable). Sorry, but this really is all just wasted effort..
Click to expand...
Click to collapse
Took me 2 seconds to throw together...took longer to upload then anything. Its just for people who want it. If you dont want it I dont want you to have it :/
xboxexpert said:
Took me 2 seconds to throw together...took longer to upload then anything. Its just for people who want it. If you dont want it I dont want you to have it :/
Click to expand...
Click to collapse
Don't get me wrong, im not knocking your work, just people's reasoning for wanting it done in the first place. I understand before the update.zip was developed, since it would break root and mess up your apps. But now, there is no reason not to take the update; thus the continued demand for this is puzzling.
If you really want the OTA update to stop, take a look at the updater-script inside the sideload_update.zip file from B&N. The first two lines read:
Code:
assert(getprop("ro.product.device") == "zoom2" ||
getprop("ro.build.product") == "zoom2");
I think those are set in the build.prop file. Change either ro.build.product or ro.product.device to something other than zoom2 (say zoom2a), and the rest of the script won't continue. This is what people are seeing when the file gets downloaded OTA and then disappears without being applied. If for some reason you must avoid it, make that change and you will stop the update cold. Not sure what the side effects of making the change are, but there would be an easy way to revert by undoing the edits, if you need to.
Wasn't this already available from another forum member?
http://forum.xda-developers.com/showthread.php?t=930382
Seems a lot easier to just copy and replace build.prop with a filemanager.
Divine_Madcat said:
Uh... why? What is there about 1.1 not to want? And if you are ok with doing all of this to block an update, there is no reason not to have CWM (which is quite stable). Sorry, but this really is all just wasted effort..
Click to expand...
Click to collapse
Yah go ahead and read thru the cwm thread and try to convince anyone in this forum that it is 100% stable. Not to suggest that anyones efforts are not welcome and appreciated but if you asked the actual devs involved I would bet they would not suggest so as well.
I for one have rooted twice (1.0 and 1.0.1) with autoroot and am 100% stable, never had a crash or the pleasure to have to restore/rebuild, not interested in the stock browser or anything else bn has to offer, quite happy and perhaps lucky with the way its workin now. I also dont appreciate being strong armed an update without a confirmation, hell even microbuddies doesnt have that kinda gawl.
I guess it will take one of the next of many 'future forced' updates from bn that bothches all the work that you have put into your NC and for whatever reason your recovery doesnt work and you are forced to rebuild from scratch before you realize that if you had a permenant block in place, you could have the time for outstanding efforts of the local devs to stabilize an upgrade path before you pulled the trigger?
The database hack appears to be best way to permanently kill OTA, no need for future updated spoof build.prop scripts (before you get hit) and no worries about being updated and possibly blown up while your sleepin and bn pushes an update out before you get the news.
or maybe its just me..........
Exactly! If you are not diligently checking the forum everyday, you wouldn't know BN is pushing out 1.1 update and you wouldn't know there is a pre-nootered 1.1 version available. BN will update you OTA before you know any better and screw up your rooted setup. Hence the need for a permanent update block.
I had recently found an update zip on Motorola's servers that updates .206 > .209, thing is I was on .181 My understanding of how the servers work are that all these updates are dumped on them and then devices can pick through them with the system version number. So, by changing the system version number on your phone, and then accessing the servers you could pull whatever updates are available for that system version. Still following me?
After the update has been downloaded it can be accessed through the cache folder on root of your system. With these updates is there a chance we could unlock the bootloader? It's possible. Especially since cheesecake and ics aren't the best of friends. So right to it.
What you need:
Rooted Motorola phone
Rom toolbox (optional)
Cheesecake app
File explorer with root access
What to do: Set-up your servers on cheesecake (first option) Reboot (These steps have been done already if you have used cheesecake before)
Go into Rom Toolbox from the market On the second screen you can edit the build.prop Scroll down a 1/3 of the way and you'll see ro.build.version.full This is the device's system version, changing this makes the magic happen The numbers that you want to change are the # marks Blur_Version.#.##.###.XT912.Verizon.en.US
As of now your options are
6.11.748
6.12.181
6.14.75
6.14.79
6.14.84
6.14.85
6.16.203
6.16.204
6.16.206
6.16.208
After altering the version number you'll want to save it and reboot Now give it a minute after you reboot so it can realize what is going on, don't know why but sometimes I couldn't check for updates if I jumped right on cheesecake after it rebooted, know it is going to be hard to wait a minute but.. just do it. Open cheese cake and click your heart away!
Lather, rinse, and repeat!
If you find something you can post your finds here and I'm sure someone that is stuck can check it out and see what the good word is. In case you don't know, after the file is completed you can access it with es file manager or root explorer under /cache folder on the root of your system, zip and crc file.
Now if you are interested in searching for bionic files there are builds 5.9.902 and 5.9.905 currently in use. You will also have to change the XT912 to XT875 in the ro.build.version.full Example: Blur_Version.5.9.905.XT875.Verizon.en.US I'm sure this method could be used with any motorola versions (atrix droid 3 4 and so on), possibly on a non-motorola phones even? Have fun with this and be careful not to brick! And don't blame me if you do!
Also, play around with it, this write up is for cdma but I'm sure you can look for anything else by editing the ro.build number.
I usually change these lines in build.prop to spoof Moto server
Code:
ro.build.id
ro.build.display.id
ro.build.version.incremental
ro.build.date
ro.build.date.utc
ro.build.host
ro.build.description
ro.build.fingerprint
ro.build.version.full
Because of the fear of getting my Device ID block by Moto server, I only do it once in a while.
Most of the time I don't need to to this. Somebody will eventually upload the OTA.zip anyway.
Where can I find the cheesecake app? Any chance this will work with GSM to?
Whirleys: if you check for updates often with chessecake there is a chance that Motorola will block me from future ota updates?
Edit: I tried it but the only thing I get is "should be good " :facepalm:
Sent from my XT910 using xda premium
Contact zombizam ...cheesecake app in atrix forum
Sent from my Galaxy Nexus using xda app-developers app
This surfs the servers, but when I attempt to download a file for another device (Like the Sprint XPRT) I get an error saying the package couldn't be validated and the update disappears from the cache.
Sent from my Galaxy Nexus using xda app-developers app
Long story short, tether doesn't work.
I was running rooted 6.11.181 and had edited the entitlement check and was using the Wireless Tether app.
Was impatient for OTA so tried to manually push the file. It failed miserably several times. I downloaded the Droid Razr 1.6 utility, and pushed my phone back to factory.
I then factory reset my phone, ran the Droid Razr 1.7 utility. The upgrade worked fine. Rerooted my phone.
Now, when I go into SQL Lite editor I can't find the entitlement check anywhere and my Wireless Tether app isn't work. Anyone know how to fix?
Try FoxFi app. I like our better than the built in tether app. I've never had problems with it.
Sent from my DROID RAZR using xda premium
trypadelik said:
Long story short, tether doesn't work.
I was running rooted 6.11.181 and had edited the entitlement check and was using the Wireless Tether app.
Was impatient for OTA so tried to manually push the file. It failed miserably several times. I downloaded the Droid Razr 1.6 utility, and pushed my phone back to factory.
I then factory reset my phone, ran the Droid Razr 1.7 utility. The upgrade worked fine. Rerooted my phone.
Now, when I go into SQL Lite editor I can't find the entitlement check anywhere and my Wireless Tether app isn't work. Anyone know how to fix?
Click to expand...
Click to collapse
Go back to SQL Lite and check entitlement on number 79. Edit that like you did before and you'll be set!
I did exactly what the video showed to do on gb, and it worked. At least I'm not getting any notifications of a $30 charge.... Mine was number 150
texbuck
I tried to do what the video said but the options just don't exist.
There is no way possible to go back to .181 and try to redo this is there?
Make sure you went to the Moto settings and not the other one.
Sent from my iPad using Tapatalk HD
I have the .211 update on my Razr as of today. Rooted and with SQL_ite the entitlement check is number 79. On .181 is was number 150. So if you have updated to ICS you will find the entitlement check on #79.
Goes like this on ICS for the Razr .211
1 SQlite from Market (have to be rooted)
2 Settings Storage (hammer and crescent wrench)
3 settings.db
4 settings
5 #79 press and hold until edit comes up
6 edit record
7 change value to 0
8 Save
9 Home screen
10 Reboot
11 Profit and you will have tether
It has worked all day for me
How strange, I don't even have #79. It goes from #78 restriction lock to #84 dialup_modem_restriction. My entitlement check was still #150. And yes I'm really on 4.04 ics. Go figure....
texbuck
Astrobrewer said:
Try FoxFi app. I like our better than the built in tether app. I've never had problems with it.
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
^This
Seriously, FoxFi just plain works. No need to do ANYTHING other than setting your password.
sRDennyCrane said:
^This
Seriously, FoxFi just plain works. No need to do ANYTHING other than setting your password.
Click to expand...
Click to collapse
+1
I use FoxFi every day since I got it without issue. You don't even need to set a password if you don't want to. I just hit a button on the widget, select tether and away I go.
Well, setting a password is a good precaution against ANYONE just hopping onto your wifi hotspot.
I just updated to ICS and now my WifiTether app doesn't work. I got FoxFi and it tethered to my laptop with no problem. However, it won't connect to Xbox Live on my 360. It shows it has a network and internet, but won't connect to Xbox Live. My other tether app never had issues connecting.
abowlofsoda said:
+1
I use FoxFi every day since I got it without issue. You don't even need to set a password if you don't want to. I just hit a button on the widget, select tether and away I go.
Click to expand...
Click to collapse
Ok, I'm a beleiver. I'm using FoxFi right now and it works great. No more hotspot hacks for now. Forget my resent posts. :good:
Moved To Q&A
Please Post questions in the Q&A section
I had to do a bit of work to get the entitlement_check sorted out, so I figured I'd post here in case anyone else is having problems. I force fed the OTA to my RAZR Maxx and rooted without much problem. When I tried to update the entitlement_check field in the sqlite DB, I get errors about being unable to write. I even tried chmoding the file to 666 (-rw-rw-rw-), via adb, and it didn't work. These are the steps I used and now I'm in business.
NOTE: I'm using a Linux box. A similar process will probably work on Windows or Mac OS but I don't know.
You'll need to install the SDK and the platform-tools, if you don't already have them.
Code:
$ cd /path/to/platform-tools
$ sudo ./adb kill-server
$ sudo ./adb root
$ ./adb devices (Make sure your device is listed correctly.)
$ ./adb shell
Now you'll be in the android shell.
Code:
$ su -
# id (Make sure "uid=0(root)")
# cp /data/data/com.motorola.android.providers.settings/databases/settings.db /tmp
# chmod 666 /tmp/settings.db
# exit
$ exit
Now you're back at your Linux terminal.
Code:
$ ./adb pull /tmp/settings.db
$ sqlite3 settings.db (If you don't have sqlite3 installed, you can use the binary in the SDK tools dir.)
Now you're in the sqlite db shell.
Code:
sqlite> UPDATE settings SET value=0 WHERE name="entitlement_check";
sqlite> SELECT * FROM settings WHERE name="entitlement_check";
(This should show "79|entitlement_check|0" now.)
sqlite> .quit
Back at Linux terminal.
Code:
$ ./adb push ./settings.db /tmp/settings.db
$ ./adb shell
Back at android shell.
Code:
$ su -
# id (Check for "uid=0(root)" again.)
# cp /tmp/settings.db /data/data/com.motorola.android.providers.settings/databases/settings.db
# exit
$ exit
Now go ahead and reboot you phone and check tethering. Should be good to go.
You should probably make a backup copy of db.settings, after you adb pull it off your phone. It's a small change and easy to fix but Safety Second and all that. (Fun should always come before Safety, in my book.)
UPDATE: You can enable CP Debug by just typing *#66336# and turn the option on.
If you don't know what this is, it might be a good idea to pass on this, as it won't really provide you any benefit.
Verizon disables CP debugging in the radio/service menu. I found a unique little proof-of-concept hack that I tested and was successful. So basically there's a file called cmdline in /proc which shows you the arguments ran at boot time. This file is from the kernel/ramdisk, and cannot be modified, as it's merely a symlink to the arguments in the kernel, and not a file itself. /proc is very dangerous for the uninformed/uneducated user, so continue at your own risk. I am not responsible for anything any of you do, ever.
Before you continue, understand this is a VERY dangerous process, and messing up can permanently destroy your device. I am not responsible for anything that happens to your device. It is your choice to utilize this information. Please follow my directions VERY carefully.
Step 1: Make a copy of your /proc/cmdline
It should look similar to this (note: do not use this example, it has been heavily modified to protect my private information and applies to my kernel/device specifically):
Code:
console=ttyS0,115200 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F cont_splash=1 ********************
[email protected] [email protected] sec_debug.reset_reason=0x1a2b3c00 lcd_attached=1 lcd_id=0x404024 androidboot.debug_level=0x4948 sec_debug.enable=1 sec_debug.enable_user=1 slub_debug=o msm_rtb.enable=1
[B]androidboot.cp_debug_level=0x55FF sec_debug.enable_cp_debug=0[/B] cordon=REMOVED connie=SM-N900V_VZW_USA_REMOVED
loglevel=8 samsung.hardware=SM-N900V samsung.board_rev=8 androidboot.emmc_checksum=3 androidboot.warranty_bit=0
androidboot.bootloader=N900VVRUBMJE androidboot.nvdata_backup=0 androidboot.boot_recovery=0 androidboot.batt_check_recovery=0
sec_debug.pm8941_rev=3 sec_debug.pm8841_rev=2 vmalloc=450m level=0x47494844 sec_pvs=0 batt_id_value=0
androidboot.check_recovery_condition=0x0 androidboot.emmc=true androidboot.serialno=REMOVED androidboot.baseband=msm
Step 2: Take a look at the bolded line in the previous step. If we want to enable CP debugging, we'll need to change those values. Change androidboot.cp_debug_level=0x5500 instead of 0x55FF and obviously change sec_debug.enable_cp_debug=1 instead of 0. Save this copy to /sdcard or wherever you will remember it. Remember to save it without an extension so it's not a text document.
Step 3. Since cmdline is read at boot, how would changing this work? Well it appears that it reads some of these debugging values during runtime, instead of just at boot. We can't edit or modify /proc/cmdline, but we can bind it to another file so it reads our custom cmdline instead of the one from our kernel. Find your modified cmdline copy (i.e, /sdcard/cmdline) and take note of its location. Next, open adb shell or terminal emulator and type the following:
Code:
mount -r -o bind /sdcard/cmdline /proc/cmdline
Now check your logcat I use a nifty free app called aLogcat which can be found in the Play Store. You will need to run this command every time you boot/reboot, or you can write a script to do so at startup. You can also verify success by using the following command: cat /proc/cmdline and that should result in your modified cmdline appearing.
Keep in mind this log can contain sensitive information such as incoming text messages or google messages, which may leave you vulnerable. Surge1223 was also successful using this method on the Verizon S4 also. Again, PLEASE do not change any other values in CMDLINE as it will either not work since it takes those values at boot time, or it can render your device inoperable/bricked/unbootable.
I'm also currently exploring the possibility of enabling bands 26 and 41 (Sprint bands) on Verizon devices. Again, it won't really bring any benefit to most, but is more of a proof-of-concept type hack.
Thanks to surge1223 and bftb0 as always
This is very useful. Note this also enables you to grab the detailed logs from the sec_log location indicated in the cmdline, though this log is prob only useful to devs or enthusiasts.
Surge1223 said:
This is very useful. Note this also enables you to grab the detailed logs from the sec_log location indicated in the cmdline, though this log is prob only useful to devs or enthusiasts.
Click to expand...
Click to collapse
How would do you do that? viewmem?
Also, what's the difference between:
sec_log= and sec_dbg=
Have you tried it? Can you post an example output?
E:V:A said:
How would do you do that? viewmem?
Also, what's the difference between:
sec_log= and sec_dbg=
Have you tried it? Can you post an example output?
Click to expand...
Click to collapse
Second to last post here I posted a lot of a sec_log http://forum.xda-developers.com/showthread.php?t=2691420 (I didn't post all of it because sec_log is a minimum of 1 MB) and yep I used viewmem to extract it As for sec_dbg, it isn't human readable per se.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
S As for sec_dbg, it isn't human readable per se.
Click to expand...
Click to collapse
Perfect! Probably the sec_dbg contain raw RF data or whatever is in the SHM buffer. Probably QXDM can read this, or try loading it in Wireshark...Um, no it probably need to be "translated/extracted" first.
Figured I'd update this post too, since I found the correct way to enable CP Debug Mode. Make sure HiddenMenu is enabled in /efs then dial *#66336# and turn CP Ramdump On (or MDM Ramdump if you're on an S4.)
ryanbg said:
...I'm also currently exploring the possibility of enabling bands 26 and 41 (Sprint bands) on Verizon devices.
Click to expand...
Click to collapse
Are you using a Sprint SIM?
If not, you'd probably need to look deeper, and perhaps reprogram part of SIM, enable correct PRL's and check for phone band support etc.
... Make sure HiddenMenu is enabled in /efs
Click to expand...
Click to collapse
What menu is that and how is that done?
I obviously don't have your device, but perhaps this is not Verizon specific...
E:V:A said:
Are you using a Sprint SIM?
If not, you'd probably need to look deeper, and perhaps reprogram part of SIM, enable correct PRL's and check for phone band support etc.
What menu is that and how is that done?
I obviously don't have your device, but perhaps this is not Verizon specific...
Click to expand...
Click to collapse
I believe the bands may be controlled by Qfuses, and some other parameters within the CP.
/efs/factoryapp/HiddenMenu -> ON
ryanbg said:
I believe the bands may be controlled by Qfuses, and some other parameters within the CP.
/efs/factoryapp/HiddenMenu -> ON
Click to expand...
Click to collapse
bands are not controlled by Qfuses. I've never heard of such a thing. Bands are controlled in NV items and/or in SIM card. If Qfuses are involved there must be a proxy app doing the fuse --> NV items translation. Or did you see something in the Qfuse register dump?
Deleted.
ryanbg said:
Deleted.
Click to expand...
Click to collapse
I be damned! Nice to be wrong sometimes. That's when you learn new stuff.
We'll then I just don't know how it works. I guess Verizon is such a big customer, they can do what they want. So the questions are, where is the physical location of those fuses? Where are they read and where is that information going?
E:V:A said:
I be damned! Nice to be wrong sometimes. That's when you learn new stuff.
We'll then I just don't know how it works. I guess Verizon is such a big customer, they can do what they want. So the questions are, where is the physical location of those fuses? Where are they read and where is that information going?
Click to expand...
Click to collapse
Their SoC package with integrated Baseband/CP is REALLY interesting. I think the CP = Hexagon, and the Hexagon DSP does all sorts of low-level non-radio business. The more I discover the more I'm intrigued.
Introduction
**EDIT**: Please see 4th post on how to obtain your MSL/SPC Code for the last step in restoring stock firmware
I figured it would be good to have a dedicated Factory Restore thread here for the LS990 (Sprint) G3 seeing as how we now have root and people want to be sure they can restore their phones if they screw something up.
First off, I am not presenting any new material here, I just simply gathered guides/tips/tricks from many forum members in an attempt to make it easier for LS990 users to restore their phones. Also, if you notice something wrong with the guide please say so! I have no ego here, we're all here to help one another so if I made a mistake please let me know
Hopefully this will be helpful to those who want to restore their phones back to stock and allow a thread for troubleshooting if someone is having issues
Disclaimer
I, nor anyone on XDA, is responsible for any damage done to your device. Please use at your own risk! The LG Flash Tool has the power to save your phone from a bootloop or soft-brick, however it can also do more damage if used improperly for the specified device. Please use with CAUTION.
Thank-You's/Credits
@wolfgart for hosting the stock G3 files. Please thank him in his thread here
@dokyson for his guide on how to restore the LG G2. Please thank him in his thread here
@AlanVenu for pointing out Sprint users should select "Board DL" in the LG Flash Tool. Please thank him at his post here
Team Codefire for finding an exploit that allows us to root our phones. Please thank (and donate if you can) to them here
Now lets get started!
Prerequisites
Sprint LG G3 (LS990)
Windows 7/8
LG Drivers (Links will be below)
Sprint LG G3 stock .tot file (Links will be below)
Sprint DLL file for LG Flash Tool (Links will be below)
LG Flash Tool (Links will be below)
A good/reliable USB cable
Backup your data! This will format your internal storage, including user apps, SMS/MMS, Call Logs, Pictures etc. So please backup your data
Downloads
Sprint LG G3 Stock LS990ZV4 .tot file
Sprint LG G3 DLL File
LG Drivers
LG Flash Tool
Generic LG G3 DLL (**ATTENTION!!! ONLY USE IF YOU EDITED THE BUILD.PROP TO A DIFFERENT PRODUCT MODEL/BUILD ID AND ARE STUCK IN A BOOTLOOP. USE THIS DLL INSTEAD OF THE SPRINT)<------Big Thanks to engine95 and autoprime
Steps
Download all files/zips above
Double click on the LGUnitedMobile exe to install the drivers
Extract the Setup_LGFlashTool.zip and double click on the exe inside the extracted folder to install the LG Flash Tool (note: make sure you don't choose a custom directory and that it installs to C:\LG\LGFlashTool)
Inside the extracted LG Flash Tool folder (where the exe is) there is a file called "MegaLock.dll". Copy this file and paste it in the C:\LG\LGFlashTool directory (overriding the current MegaLock.dll file)
If your phone is still working (and not in a bootloop or perpetually off) plug it in to your computer and let the installation of the LG Drivers finish (if your phone is in a bootloop or it won't turn off it shouldn't be a big deal)
Unplug your phone from your computer then turn off your phone
While its turning off you can open up the LG Flash Tool program (if no desktop icon was created for the program just do a search for it within your installed apps or browse for it from the start menu). You can open it with the default setting (Korea Factory)
Once your phone is completely powered off press and hold the Volume Up button and reconnect the phone to your computer via the USB while still holding the Volume Up button until you enter Download Mode (it will look like this)
Once you're in download mode let go of the Volume Up button and wait for the drivers to install on your computer
Once the drivers have finished installing navigate to your desktop and right-click on your Computer (or This PC) icon and select "Manage" (or do a search for "Device Manager")
In the Computer Manager screen select "Device Manager" then select Ports
Look for the LGE AndroidNet USB Serial Port (COM#) (where # just means whichever port is was installed to. Ex: (COM3)). Double Click on this and select "Port Settings"
Next, select "Advanced" then change the COM Port Number to COM41. Once COM41 is selected click OK, then OK again to save your settings. Now your Device Manager should have refreshed and the LGE AndroidNet USB Serial Port should have changed to (COM41). Exit out of Device Manager/Computer Manager.
Navigate to wherever you downloaded the LGLS990_20140704_LGFLASHv160_Download.zip and extract the zip.
Back in the LG Flash Tool Program the Model Config screen should be open. Select "Manual Mode". Right below it select the LGLS990_20140704_LGFLASHv160.dll you extracted for the DLL selection (navigate to wherever you extracted it)
After that select "Add" (immediately after the DLL selection option) and select the LS990ZV4_04.51101.tot file (navigate to wherever you downloaded it)
Now, navigate to Action Mode section and select Board DL. Click OK, then click the yellow arrow in the top left corner
After you click the yellow arrow (start) button the LG Flash Tool begins examining the DLL and tot file you selected. IF everything went OK after a little wait you'll see a "READY!!" prompt under the COM41 Port.
Once you see "READY!!" sign unplug your phone from the USB, wait 5 seconds, then plug your phone back into the USB
After you reconnected your device you'll notice the flashing process begins as indicated by the progress bar. It could take a while so just hang tight and keep an eye on the progress
Sometimes the LG Flash Tool will not show 100% progress but will successfully flash the firmware so keep an eye on your phone
Once the flash is finished (either indicated by 100% progress or the PASS sign that pops up) your phone will begin to reboot into the AAT Mini OS Screen. Once at the screen hold onto the power button and select "OK", then select the "normal boot (+power)" option
After that selection is made your phone should reboot normally
Sign into everything and let your phone settle for a few minutes. Then, restart the phone
If you're missing certain apps like WiFi Calling and Sprint Bloat please follow the links provided by @engine95 to restore these apps (I took apart the Sprint tot file and the apps are present, however for certain people these apps are not showing up immediately after the flash)
Success or Failure?
If your phone successfully rebooted into the system congrats! If not please look down for some trouble shooting tips (coming very soon! I need to hit the hay right now lol)
Again, I did not discover anything new, I thought it would be good to have a concise and detailed guide to restoring the LS990 to stock firmware. Hopefully this helps!
General Tips & Tricks to AVOID a Bootloop/Soft Brick
Stay away from editing the build.prop! Many users have reported that they made edits to the DPI, Build ID, Product Model. Then upon rebooting their phones they are in a boot loop. For right now, I'd say stay away from making any build.prop edits BUT if you do please have ADB ready along with the stock build.prop on your computer so you can troubleshoot
Have a backup ready! As of right now we don't have a custom recovery, however if you are modifying system files/apks make sure you have stock equivalents on your computer and ADB ready to troubleshoot
Only use mods/themes for the LS990 model. While the LS990 (Sprint) model certainly does share a lot of the same components as the international versions certain framework/system apps have certain Sprint/CDMA settings in them (ex: framework-res.apk, LGUSMms.apk, etc) so just be careful.
Use common sense. As of right now we don't have a custom recovery; but we will at some point. So just hold off for a little bit on hacking up your system environment.
Troubleshooting Tips if the Flash Failed
Check your USB Cable. I know it may seem silly, but if you don't have a stable/reliable connection between your computer and phone bad things could happen. Once the phone is plugged into the USB port of your computer/laptop try not to move the phone/laptop too much (could interfere with the connection)
If you get a "Wrong Device" error when trying to flash the phone, and you are 100% sure you do in fact have the Sprint LG G3 (LS990), replace the Sprint DLL file with the Generic LG G3 DLL file in the OP. This error is most common if you have changed the Product Name, Product Model, Display ID, and/or Build ID entries in the build.prop
If you get any COM errors make sure you did indeed switch the LGE AndroidNet USB Serial Port to COM41
How to Get your MSL/SPC
**NOTE** This will only work if your phone is able to turn on
Make sure you have the LG Drivers Installed on your computer (link is in 1st post for that)
Open up your dialer and enter ##DIAG#
Enable DIAG Mode
Connect your phone to your computer
On your phone change the USB Connection type to Charge Only (pull down your statusbar and click on USB Connected)
Download CdmaDevTerm on your computer(I prefer this version)
Extract the CdmaDevTermZip
Inside the extracted folder double click on the cdmaTerm file to start the application
On the right hand side of the CdmaDevTerm screen select "Scan ports"
Next select the LGE AndroidNet USB Serial Port from the drop down menu (mine was COM6) then click Connect
In the SPC/Lock Options change NV to LG from the drop down menu
Now click Read SPC
Success!
Took me all day to figure this out. I Was hoping someone would make a thread like this in the sprint section.
Very well done. Thank you!
Wikd said:
Took me all day to figure this out. I Was hoping someone would make a thread like this in the sprint section.
Very well done. Thank you!
Click to expand...
Click to collapse
Yea I checked with a moderator to make sure it was OK because there is a universal Restore thread for the G3 but not a lot of people know about it
Do you see anything I missed in the OP? I quadruple checked it but since your memory is fresh from the experience I figured you may have some more useful tips for the community
fergie716 said:
Yea I checked with a moderator to make sure it was OK because there is a universal Restore thread for the G3 but not a lot of people know about it
Do you see anything I missed in the OP? I quadruple checked it but since your memory is fresh from the experience I figured you may have some more useful tips for the community
Click to expand...
Click to collapse
I only made it to the point where I selected the tot and dll, and changed my com port. I stopped just before I was supposed to hit the yellow arrow. I was really just trying to make sure I had it all figured out for when I need it.
However, your instructions seem to be spot on. I did see a typo that I was going to point out to you but can't find it now, haha. You must have found it.
Thanks :laugh::laugh::laugh:
HELP!!!
so i did a big no no and changed my build prop and now i am stuck in a boot loop. this method isnt working because it thinks my model is different. any ideas on how to fix it???
FYI... I edited my build.prop dpi the other day. And got bootlooped ...I used the same method as this one on my G3spr LS990 AND WORKED FINE. There are a few tweaks to GSM instructions...but seems OP has covered all of them. BTW Flashtool did error out at 93% but phone still booted after the mini Os step.
Sent from my LGLS990 using Tapatalk
---------- Post added at 11:22 AM ---------- Previous post was at 11:19 AM ----------
treezy26 said:
so i did a big no no and changed my build prop and now i am stuck in a boot loop. this method isnt working because it thinks my model is different. any ideas on how to fix it???
Click to expand...
Click to collapse
what exactly is happening...and what step ?
Sent from my LGLS990 using Tapatalk
matthew0776 said:
FYI... I edited my build.prop dpi the other day. And got bootlooped ...I used the same method as this one on my G3spr LS990 AND WORKED FINE. There are a few tweaks to GSM instructions...but seems OP has covered all of them. BTW Flashtool did error out at 93% but phone still booted after the mini Os step.
Sent from my LGLS990 using Tapatalk
---------- Post added at 11:22 AM ---------- Previous post was at 11:19 AM ----------
what exactly is happening...and what step ?
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Its failing because it tells me it's the wrong device. I changed the model name to sync with my gear 2 neo. Which is weird because it worked fine for a bit then I rebooted phone and it just boot loops now.
Sent from my SPH-L710 using XDA Premium 4 mobile app
You got everything covered,.Thank you
Where was this yesterday morn when I had to figure it all out. I found all the scattered info after I was done.
Thanks for posting this. ?
Warning
Do not modify Build.prop, you will soft brick your device. Wait until a recovery is Out. Just posting this as a clear warning. This Guide would have helped me big two days ago. Great info Thanks to OP again
treezy26 said:
Its failing because it tells me it's the wrong device. I changed the model name to sync with my gear 2 neo. Which is weird because it worked fine for a bit then I rebooted phone and it just boot loops now.
Sent from my SPH-L710 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't understand all this build.prop editing for the Gear 2 Neo. I've used my Gear 2 Neo on my G3 since phone launch...month or more before root existed. There are tutorials on XDA how to get it working and again ROOT IS NOT REQUIRED!!!
treezy26 said:
Its failing because it tells me it's the wrong device. I changed the model name to sync with my gear 2 neo. Which is weird because it worked fine for a bit then I rebooted phone and it just boot loops now.
Sent from my SPH-L710 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I would see if you can hook up to adb, either with the phone completely shut down or while it's rebooting and push the stock build.prop
Here's the stock build prop : https://www.dropbox.com/s/8b9hkqen9d19l9e/build.prop
I would try to mount the system as r/w first. So in adb shell enter this:
mount -o rw,remount /dev/block/mmcblk0p41 /system
After that try to use adb push to get the new prop into the /system. Just use a terminal/Command Prompt and CD into the folder you have the stock build.prop saved in and push it with
adb push build.prop /system/build.prop
Then back in adb shell fix permissions
chmod 644 /system/build.prop
fergie716 said:
I would see if you can hook up to adb, either with the phone completely shut down or while it's rebooting and push the stock build.prop
Here's the stock build prop : https://www.dropbox.com/s/8b9hkqen9d19l9e/build.prop
I would try to mount the system as r/w first. So in adb shell enter this:
mount -o rw,remount /dev/block/mmcblk0p41 /system
After that try to use adb push to get the new prop into the /system. Just use a terminal/Command Prompt and CD into the folder you have the stock build.prop saved in and push it with
adb push build.prop /system/build.prop
Then back in adb shell fix permissions
chmod 644 /system/build.prop
Click to expand...
Click to collapse
I tried that way before Flashtool. The problem is it's read only without root. If you root, then abd shell and grant root, then you can do that.
I may be wrong, but that's the issue I ran into.
engine95 said:
I tried that way before Flashtool. The problem is it's read only without root. If you root, then abd shell and grant root, then you can do that.
I may be wrong, but that's the issue I ran into.
Click to expand...
Click to collapse
So if you asked for su in shell it would give you an error?
I did some looking, I wonder if issuing these command manually would work. The phone needs to be plugged into the computer and then turn it on. As its turning on:
(1 @ECHO*off
(2)cd /d %~dp0
(3)echo.
(4)echo Waiting for device...adb wait-for-device
(5)echo.
(6)adb -d shell stop
(7)adb -d shell su -c "mount -o remount rw /system"
fergie716 said:
So if you asked for su in shell it would give you an error?
I did some looking, I wonder if issuing these command manually would work. The phone needs to be plugged into the computer and then turn it on. As its turning on:
(1 @ECHO*off
(2)cd /d %~dp0
(3)echo.
(4)echo Waiting for device...adb wait-for-device
(5)echo.
(6)adb -d shell stop
(7)adb -d shell su -c "mount -o remount rw /system"
Click to expand...
Click to collapse
Yeah. It would say read only.
That's following what you have in the post above this one, just adding su before all the commands.
What you have posted here may work. I'll admit, my adb skills aren't that great.
bhint15 said:
I don't understand all this build.prop editing for the Gear 2 Neo. I've used my Gear 2 Neo on my G3 since phone launch...month or more before root existed. There are tutorials on XDA how to get it working and again ROOT IS NOT REQUIRED!!!
Click to expand...
Click to collapse
I used the build prop trick because it allows me to use everything such as s voice and download apps from the samsung store that's not available with just the gear manager app. I know it was a dumb mistake to change it since there is no recovery available yet. It worked fine for about an hour. I downloaded several apps for the neo just fine. Its when I changed a setting in xposed that needed a reboot to go into effect when everything went bad. I followed the steps here in the op to a tee and kept getting the red failed message after pressing the arrow. Didn't understand why till I read the error and it says wrong device. And that's when it clicked. Being stupid and impatient now I'm stuck with a bricked device. I don't think adb will work since it won't recognize it being Lg. Oh well thanks for you guys help. Luckily I'm still under warranty and have insurance. Do you think I will have issues with sprint since having it being rooted and change the build prop?
Sent from my SPH-L710 using XDA Premium 4 mobile app
Break screen? Dont know never carried warranty on a phone or used a factory warranty so im no help.
Sent from my LGLS990 using XDA Free mobile app