Related
The HTC Stocks app has the best widget of all other currency apps, so I was using it on my 1.5 Hero for displaying the EURO/GBP (EURGBP=X) rate.
After the 2.1 rom update I have a strange problem. When I try to add a new ticker for "eurgbp=x", I get the error message: "Unable to recognize the company name or stock symbol you typed. Please try again." However, this worked in the past like a charm. I have to note that adding "gbp=x" or "usd=x" works fine, with no problem at all.
Maybe this problem is related to an updated version of the Stocks app in the new rom. Is anyone experiencing the same problem? I haven't found a similar thread for a Sense Android phone. The same problem exists in the latest rom of HD2, but people have figured a work-around, by changing a file under "Application Data\HTC\", but this file doesn't exist on Android.
Any help would be more than welcome!
I experience the same problem (although I'm on VillainRom12). Previously adding currencies (EURUSD=X etc) was working, but right now I am unable to find it. This could be HTC problem as it was working fine on 1.5, but this could be also some Yahoo search glitch (I am unable to search for that quotes on mobile version of the Yahoo Finance page, while the desktop version works fine). The only workaround to that was to edit manually SQLite database of Stocks application (but this may require root - I can provide details if necessary). Once I added appropriate entries to the list of stocks, it seems to be working fine (it is displaying my currencies, but the search still does not work).
One other deficiency I found was the fact that graphs are not cached anymore - If I open the application and check for example a daily graph, I need to update it in order to see any chart - each time, even if I switch from 1D to 5D and back. It is also automatically updated each time I visit given tab, if I enable the automatic updates. Previously this app displayed previously cached graph. I'm not sure whether this happens also on stock 2.1 ROM.
Now that you mention it, I have the same problem with the graphs in the 2.1, too. It worked (showed the cashed graph) in the 1.5, but not any more. Blank graph until it updates.
Can you provide me some guidance about how to edit the Stocks' database? At least a link to something similar would be much appreciated. Can I access the phone's system folder without rooting it, through my PC (Win, Linux, whatever)?
eeVoskos said:
Can you provide me some guidance about how to edit the Stocks' database? At least a link to something similar would be much appreciated. Can I access the phone's system folder without rooting it, through my PC (Win, Linux, whatever)?
Click to expand...
Click to collapse
I'm new in the business, so I'm not sure if the root is necessary. You can try it, anyway to see if you will be able to push and pull files from the directory where Stocks stores its database.
Here's what I did:
Enable USB Debugging in Settings -> Applications -> Development -> USB Debugging
Download Android SDK from http://developer.android.com/sdk/index.html
In command line go to subdirectory tools of Android SDK
Close Stocks app and remove Stocks widget from the screen
Connect Phone via USB
... (Beginning of the optional part) ...
Go to Android shell
Code:
adb shell
List any processes to see if there's a com.htc.android.Stock process (like in this case)...
Code:
ps | grep Stock
7605 10007 130m S com.htc.android.Stock
7619 0 2156 S grep Stock
Kill any Stock processes (using the value in the first column):
Code:
kill 7605
Exit to command line
Code:
exit
... (End of the optional part) ...
Pull the Stock database:
Code:
adb pull /data/data/com.htc.dcs.service.stock/databases/stock.db stock.db
Sample output:
Code:
d:\Projects\Android\tools>adb pull /data/data/com.htc.dcs.service.stock/databases/stock.db stock.db
568 KB/s (5120 bytes in 0.008s)
Backup, just in case:
Code:
copy stock.db stock_backup.db
Run sqlite3
Code:
sqlite3 stock.db
Enable headers in sqlite:
Code:
.headers on
List contents of quotes table:
Code:
select * from quotes;
Sample output:
Code:
sqlite> select * from quotes;
_id|_name|_symbol|_price|_change|_percent|_open|_high|_low|_volume|_link|_type|_sequence|_updatetime
2|CHF/PLN|CHFPLN=X|3.08299994468689|0.0116999996826053|0.381900012493134|3.07209992408752|3.08550000190735|3.07010006904602|0|http://m.yahoo.com/htcwf/search?p=CHFPLN=X||0.0|1278490511305
3|USD/PLN|USDPLN=X|3.27649998664856|0.0200999993830919|0.617200016975403|3.25550007820129|3.27959990501404|3.24499988555908|0|http://m.yahoo.com/htcwf/search?p=USDPLN=X||100.0|1278490511305
4|EUR/PLN|EURPLN=X|4.1217999458313|0.0151000004261732|0.367700010538101|4.11250019073486|4.12349987030029|4.10799980163574|0|http://m.yahoo.com/htcwf/search?p=EURPLN=X||200.0|1278490511305
5|EUR/USD|EURUSD=X|1.25789999961853|-0.00469999993219972|-0.376199990510941|1.26170003414154|1.26259994506836|1.25689995288849|0|http://m.yahoo.com/htcwf/search?p=EURUSD=X||300.0|1278490511305
6|EUR/CHF|EURCHF=X|1.33689999580383|-0.000899999984540045|-0.0710000023245811|1.33879995346069|1.33910000324249|1.33609998226166|0|http://m.yahoo.com/htcwf/search?p=EURCHF=X||400.0|1278490511305
sqlite>
Note the last _id (here 6) and add new currency with _id higher by 1 (so here, 7):
Code:
insert into quotes (_id, _name, _symbol) values (7, "EUR/GBP", "EURGBP=X");
Check if it has been added:
Code:
select * from quotes;
Sample output:
Code:
sqlite> select * from quotes;
_id|_name|_symbol|_price|_change|_percent|_open|_high|_low|_volume|_link|_type|_sequence|_updatetime
2|CHF/PLN|CHFPLN=X|3.08299994468689|0.0116999996826053|0.381900012493134|3.07209992408752|3.08550000190735|3.07010006904602|0|http://m.yahoo.com/htcwf/search?p=CHFPLN=X||0.0|1278490511305
3|USD/PLN|USDPLN=X|3.27649998664856|0.0200999993830919|0.617200016975403|3.25550007820129|3.27959990501404|3.24499988555908|0|http://m.yahoo.com/htcwf/search?p=USDPLN=X||100.0|1278490511305
4|EUR/PLN|EURPLN=X|4.1217999458313|0.0151000004261732|0.367700010538101|4.11250019073486|4.12349987030029|4.10799980163574|0|http://m.yahoo.com/htcwf/search?p=EURPLN=X||200.0|1278490511305
5|EUR/USD|EURUSD=X|1.25789999961853|-0.00469999993219972|-0.376199990510941|1.26170003414154|1.26259994506836|1.25689995288849|0|http://m.yahoo.com/htcwf/search?p=EURUSD=X||300.0|1278490511305
6|EUR/CHF|EURCHF=X|1.33689999580383|-0.000899999984540045|-0.0710000023245811|1.33879995346069|1.33910000324249|1.33609998226166|0|http://m.yahoo.com/htcwf/search?p=EURCHF=X||400.0|1278490511305
7|EUR/GBP|EURGBP=X|||||||||||
sqlite>
Quit sqlite:
Code:
.quit
Push the file back to the phone:
Code:
adb push stock.db /data/data/com.htc.dcs.service.stock/databases/stock.db
Sample output:
Code:
d:\Projects\Android\tools>adb push stock.db /data/data/com.htc.dcs.service.stock/databases/stock.db
341 KB/s (5120 bytes in 0.014s)
Restart phone.
See if that worked
I hope HTC (or Yahoo) will be able to fix that, because the above is really a long process...
Anyway, I can't make it work. Entering "ps | grep Stock" gives me a "grep: permission denied" error message. I did some searching and I believe this is what people mean by saying "you need root access", right? I'll come back when I'm rooted (i.e. when I find a decent guide for rooting 2.1).
Thanks for your time & effort man. I really appreciate it.
eeVoskos said:
Anyway, I can't make it work. Entering "ps | grep Stock" gives me a "grep: permission denied" error message.
Click to expand...
Click to collapse
You can try to omit the "optional" part (steps 6-9) - the ps thing was just to make sure that Stock isn't running. But I noticed anyway that it never ran in the background when I closed it on the phone. Try to adb pull and adb push and see if you'll get any permission issues. If you do, then you indeed need a root (sorry I can't check that as I'm rooted)
A couple of days ago I updated the ROM of my HTC TD2, with the most recent one of HTC (WM6.5, Sense 2.5.20113030.0). Afterwards I noticed that I also could not get the stock app to accept the code EURUSD=X.
You mention the following
The same problem exists in the latest rom of HD2, but people have figured a work-around, by changing a file under "Application Data\HTC\", but this file doesn't exist on Android.
Click to expand...
Click to collapse
Can you tell me what that work-around is or point me to it? Hopefully this can help me.
Thank you in advance.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=706732
eeVoskos said:
Check this thread:
Click to expand...
Click to collapse
Thank you for the link (which I am not allowed to repost ).
Last Monday I wrote an e-mail to HTC about this problem and a couple of days later I got a reply. They told me they tried to search for the currency rate (eurusd) and that they got a result. So I tried again and lo and behold I got a result as well. Searching for eurusd=x gave me a result while last weekend it was not working.
So I tried several other currency rates and they all rendered a result, also eurgbp=x. Perhaps it is also fixed for the Android app.
[Extra information added below]
Tried again and nothing
I was connected with a data connection to my carrier, so I switched to my wifi connection. Tried again and... result.
So it seems to be a difference in communication between an ordinary data connection and a wifi connection. Maybe this will help someone
Wird problem. I tried it too on both UK and Greek carriers and on WiFi, but nothing. No result for either of them: "eurgbp=x", "eurgbp", "eurusd=x", "eurusd". I have been trying occasioanly more than one month now.
I think I should drop them an email too...
Why don't you do a soft (temporary) root and make the database entries as described in here? I did it and now I got all the stuff I need, and no trace of root on the device.
Just another party by Keen Team
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm getting increased queries and replies in this post/PM recently, so I'll try to make this clear (hopefully) for 99% of people. Short version of OP which you must read:
1. Don't install 5.1.1 for now if you ever want to root without tripping Knox warranty.
2. No new ROM can be supported as bug has been fixed.
3. If you don't know how to check a kernel's build date, DO NOT submit FPTAG.
Full story:
New bootloader blocks downgrading, be careful installing 5.1.1 OTA! More details: http://forum.xda-developers.com/tmobile-galaxy-s6-edge/general/psa-odin-5-1-1-t3136151
Kernel built after May 15th (including some 5.0.2 and all 5.1.1) have this bug fixed. Be cautious when installing OTA these days and FlashFire might be your best shot of upgrading systems. Use Odin to unroot and receive OTA if you want.
Current version: Beta 6 (HTC One (M9) SUPERSU VERSION! Check updated Usage section!)
Since Beta 5.2: Should be more "stable" on devices with more application installed, but I'm not 100% sure. If it doesn't work, roll back to beta 5.1
I'm getting too many queries about Note 4. Two things to clarify: 1) No device data needed to root Note 4, try KingRoot 4.0. 2) Unless you have KNOX warranty bit tripped already, there is no perm-root for Note 4 yet.
If you have decent bandwidth and experience with ROM files, please see this: http://forum.xda-developers.com/galaxy-s6/general/root-pingpong-root-rom-workshop-thread-t3104639. Volunteers needed to speed up adding new ROMs.
Big THANK YOU to all helped collecting ROMs. Now we have 91+2 ROM versions supported!
Everyone please do me a favor. If you want a ROM (S6 or S6E) get supported, please confirm it is not yet supported and post a reply in this thread like:
FPTAG fingerprint here
So I can quickly filter FP out of the replys by using search. Thanks.Only submit if you know what a kernel build date is.
Supported devices
Samsung Galaxy S6 with following ROM versions:
G9200ZCU1AOD5
G9200ZHU1AOD3
G9200ZHU1AOD9
G920R4TYU1AOD3
G920IDVU1AOD1
G920FXXU1AOCV
G920PVPU1AOCF
G920TUVU1AOCG
G920VVRU1AOC3
G920FXXU1AOBN
G920FXXU1AODG
G9209KEU1AOCI
G9209KEU1AODA
G9208ZMU1AOD5
G9208ZMU1AOCI
G920FXXU1AOD9
G920AUCU1AOCE
G920FXXU1AODE
G9200ZCU1AOD9
G920W8VLU1AOCG
G920FXXU1AOD4
G920R4TYU1AOCB
***new*** Use Download Data!
G920FXXU1AOCY
G920IDVU1AOC4
G920FXXU1AODI
G9209KEU1AOD5
G920IDVU1AOBQ
G9208ZTU1AOD9
G920FXXU1AOE3
G920IDVU1AOE3
G920FXXU1AOD8
G920FXXU1AOE4
G920AUCU1AOE2
G920T1UVU1AOCH
G9208ZTU1AOCI
G920IDVU1AOC6
G920IDVU1AOD3
G920FXXU1AOCZ
G920AZTUU1AOD1
G9200ZHU1AOE4
G9200ZCU1AOE4
G920KKKU1AODC
G920IDVU1AOE4
G920LKLU1AODC
G920SKSU1AODC
G920IDVU1BOE2
G9208ZTU1AOE4
G920PVPU1AOE2
G920W8VLU1AOE1
G920VVRU1AOE2
SC04GOMU1AOE1
Samsung Galaxy S6 Edge with following ROM versions:
G9250ZCU1AODC
G925VVRU1AOC3
G925FXXU1AOD9
G925PVPU1AOCF
G925FXXU1AOCV
G925AUCU1AOCE
G925TUVU1AOCG
G925W8VLU1AOCG
G925IDVU1AOD1
G925SKSU1AOD5
***new*** Use Download Data!
G925FXXU1AOD4
G925R4TYU1AOD3
G925FXXU1AODG
G925FXXU1AOCZ
G925IDVU1AOD3
G925LKLU1AOD8
G925SKSU1AOD8
G925FXXU1AOE3
G925PVPU1AOE2
G925FXXU1AOD8
G9250ZTU1AODC
G925FXXU1AOE4
G925AUCU1AOE2
G925TUVU1COE6
G925FXXU1AOCY
G9250ZTU1AOE4 (5/11 kernel, seems not fixed yet, please test)
G925R4TYU1AOE2
SCV31KDU1AOCP (Japan version of S6E?)
G9250ZCU1AOCH
G9250ZCU1AOE4
G925IDVU1AOE4
G925IDVU1BOE1
G925LKLU1AODC
G925IDVU1AOE3
G925IDVU1AOE2
G925KKKU1AODC
G925SKSU1AODC
G925W8VLU1AOE1
G925VVRU1AOE2
G925R7WWU1AOE3
HTC One (M9) -- EXPERIMENTAL, UNLOCKED BL REQUIRED
htc/himauhl_htccn_chs_2/htc_himauhl:5.0.2/LRX22G/516731.9:user/release-keys
Verizon 1.33.605 (?)
New ROM and device support are coming~~
If your ROM version is not listed here, please check if any ROM with the same variant is already supported. If the supported one is newer, I suggest go and grab it instead of waiting.
Known Issues:
None
Todo:
Coming next release: (will come after SuperSU version)
TBD
In queue:
Check the workshop thread: http://forum.xda-developers.com/galaxy-s6/general/root-pingpong-root-rom-workshop-thread-t3104639 but DO NOT REPLY UNLESS YOU ARE WORKING ON ROMS. Thank you for keeping that post clean!
Usage
OK, since manual switch is too complex and there are some compatibility issue of Kinguser, I'm making a SuperSU version now.
Note that due to the natural that SuperSU su doesn't ask for permission when SuperSU apk is missing, root will only happen when SuperSU apk has been installed. Read instrucitons below CAREFULLY!
0. Read Q&A section and BACKUP your data.
1. If you already have Kinguser installed please:
a. Open Kinguser, go to Settings -> Root authorization setting -> Remove Root permission. Click to remove root permission
b. Uninstall Kinguser2. Download pingpongroot_<ver>.apk. Install & open it.
3. It will automatically install SuperSU 2.46 for you. Follow the instructions on screen. You may need to enable unknown source for this step.
a. Once install is finished, click “Open" and run it once to "activate" it. It will prompt an error message (unless you already rooted) and exit automatically, bring you back to PingPong root.4. Click "Download Data" button to update device data if you have Internet connection.
5. Open it and click "Get Root!" button
6. If prompted for app permissions, allow them and continue. If it reboots, just retry.
7. Once finished, please make sure to reboot.
8. You can uninstall PingPong root app once finished.
Credits
Vulnerability: memeda, wushi
Original idea of exploit: memeda
Exploit: idl3r, Qoobee
Special thanks to:
Kingroot team (@Kingxteam) for help testing and great root manager
Q&A
Q: How to root 5.1.1 then since PingPong root will never work?
WARNING: User report that fingerprint sensor and incoming call stop working after using the engineering sboot.
A: The classic recovery root method. You shall find details in many other posts. If you are T-Mobile user, lucky for you that there is a leaked engineering bootloader which make root a piece of cake without tripping Knox warranty bit:
http://forum.xda-developers.com/gal...-root-tool-t3103016/post61684664#post61684664
Q: It just keeps rebooting, what can I do?
A: The exploit may panic the kernel and reboot your device. If the data is off, same could happen as well. When issue happens, try these:
a. Clean up background process before running root.
b. Turn on airplane mode after clicking "Download Data".
c. Backup your data and run factory reset.
d. Definitely avoid doing anything else when "wait!!!" appears.If these doesn't help after 5 retries, there could be some issue, please collect the information in /proc/last_kmsg and send it to me.
Note: User reporting installing My Knox or enable other Knox feature (like enterprise provision or KNOX active protection) may cause reboot loop. Be cautious!
Q: My ROM is not yet supported?
A: Since I have limited bandwidth to download ROMs, I have to prioritize ROM requests and focusing on new variants/models first. And currently recruiting volunteers to help download/shrink ROMs.
If you see your ROM FP is not listed, but a very similar one (may be just the last digit or character is different) exists, please see if you can flash that version of ROM. I'm sure you can find someone helping you in corresponding forum.
Q: Will Samsung Pay/My Knox work?
A: To be honest I can't tell for sure. Indeed this root does not trip warranty bit. But it still leaves SU files, which is inevitable, on system partitions. And a lot of root features actually make change to system partition, so let's say it can be detected. If Samsung makes the decision that there will be no certain feature for presence of a su file, then there will be no fun. IMHO this is very bad idea since even Apple doesn't disable anything on jailbreak devices. Let's see what will be the outcome. This makes sense to enterprise uses but for consumers at least a choice should be given.
Q: Note4/Z3/Old Samsung/etc?
A: We also wrote the rooting engine in KingRoot 4.0 for generic 32-bit devices. Give it a try. Note that for some devices like Note4, only temp root is achievable.
Q: Why "PingPong" root?
A: Because the vulnerability affects ping socket and we are Chinese
Q: What's the current status of this tool?
A: Beta. We've thoroughly tested it on ROMs for G9200, but not other variants. You are the 1st batch of beta testers!
Q: Is my device supported?
A: You can check the version of your ROM in "About this phone" page. It shall read LRXxxx following by the ROM version.
This tool checks your ROM version as well. If you read "Your device data is still not supported." after clicking "Get Root!", your device data has not been collected yet. Please reply with your ROM version plus keyword "FPTAG" in this thread.
Q: Will this root trip KNOX warranty bit or disable OTA?
A: No, it won't trip KNOX warranty bit and YES, it will disable OTA. It doesn't require odin to flash in a custom recovery, so the warranty bit will remain intact.
Q: I'd like switching to SuperSU, what shall I do?
A: Kinguser does not have a "swtich" function. Follow these steps to do so manually: (if you are not familiar with adb, see this version: http://forum.xda-developers.com/showpost.php?p=60632150&postcount=269)
1. Download supersu.7z and extract it. You will get the files needed to install Supersu.
2. Using adb to push su and busybox (if not installed) to /data/local/tmp.
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
3. Start a su session and run the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/bin/busybox && chmod 0755 /system/bin/busybox
daemonsu -d &
Then keep the session running.
4. Open Kinguser, go to Settings -> Root authorization setting -> Remove Root permission. Click to remove root permission. Your su session should be still running.
5. Uninstall Kinguser app.
6. Go back to the su session and run following commands to replace su and cleanup:
Code:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/bin/ddexe
busybox chattr -ia /system/bin/ddexe_real
cat /system/bin/ddexe_real >/system/bin/ddexe
busybox chattr -ia /system/xbin/ku.sud
rm /system/xbin/ku.sud
rm /system/xbin/pidof
rm /system/xbin/supolicy
7. Install Supersu apk
8. Open Supersu apk to update files.
9. Reboot.
Q: S6 Edge/G Flex 2/M9/other arm64 devices?
A: We will look into them soon
S6 Edge: Done
M9: WIP
G Flex 2/others: pending
Q: I need a video to guide me through
A: Check out this one: https://youtu.be/_Ezh7Oi-jyM
(Note: these are for earlier version)
https://www.youtube.com/watch?v=gNdWX31Sqd8
and this one: http://youtu.be/eAQ4WBg9xj0
To all sent me PM: I'm sorry that the reply could be delayed. Currently we are busy working on supporting of new ROMs and fixing bugs. To all those providing useful info/suggestion, thanks a ton!
nice work
great！
Holy crap man!!! GREAT WORK!!!!
great work! knox 0x0
You guys are awesome! Patiently waiting for G920FXXU1AODG to be incorporated
Any chance of the ATT variant being rooted?
Japultra said:
You guys are awesome! Patiently waiting for G920FXXU1AODG to be incorporated
Click to expand...
Click to collapse
Downloading the ROM now, mate Will be included in the next Beta which will happen soon enough
Kokorone said:
Any chance of the ATT variant being rooted?
Click to expand...
Click to collapse
Yes, they are waiting for an ATT rom to appear first though.
Wow...can't believe! [emoji33]
Nice work! [emoji106]
Now switched from beta1 to beta5 and SuperSU...worked like a charm!
Titanium Backup is now running how it should.
Yeah...root access until next Update to 5.1.1 [emoji7]
and Knox says 0x0?
Hoping for g920fxxu1a0cw to be included great job mate!
is it possible with G920FXXU1AOD9 french region
G920FXXU1AODG here, will it work for that firmware? (Vodafone Germany)
Joern85 said:
G920FXXU1AODG here, will it work for that firmware? (Vodafone Germany)
Click to expand...
Click to collapse
It's coming in the next update!
---------- Post added at 10:44 AM ---------- Previous post was at 10:43 AM ----------
tutti9372 said:
and Knox says 0x0?
Click to expand...
Click to collapse
You should really read the OP
Q: Will this root trip KNOX warranty bit?
A: No. It doesn't require odin to flash in a custom recovery, so the warranty bit will remain intact.
Click to expand...
Click to collapse
I'm wondering if the vulnerability used here exists on the S6 Edge. Because I don't see anyone posting a SM-925xx Rom and to my understanding SM-920 is normal S6, where as SM-925 is the edge version.
Fantastic work, Idler! Will you publish the source code for this?
cpfeifer said:
I'm wondering if the vulnerability used here exists on the S6 Edge. Because I don't see anyone posting a SM-925xx Rom and to my understanding SM-920 is normal S6, where as SM-925 is the edge version.
Click to expand...
Click to collapse
Oh, I shall update the Q&A section. S6E (and may be other arm64 devices) will be investigated. And vulnerability should still be there for any kernel before 5/3.
idler1984 said:
Oh, I shall update the Q&A section. S6E (and may be other arm64 devices) will be investigated. And vulnerability should still be there for any kernel before 5/3.
Click to expand...
Click to collapse
That's good to hear. My current kernel is from April 10th and I've got the latest ota. Hopefully I can get root before a forced ota is pushed out with a kernel update.
That is truly great work....
and my FAVOURITE
After switching to SuperSU, aps like TitanumBackup, RootExplorer and many probably more works great.
I just edit my "others.xml" and just the begin of having true FUN with my phone
BIG THANKS for ROOT
idler1984 said:
Oh, I shall update the Q&A section. S6E (and may be other arm64 devices) will be investigated. And vulnerability should still be there for any kernel before 5/3.
Click to expand...
Click to collapse
Thanks for your great tool. For us who have tripped knox will it untrip or not.:
Hi
I've made the update Android Wear 2.0 on my LG G Watch R (through the Play Store).
However, i really do not like the new interface and how notifications are now displayed.
Is it possible de downgrade Android Wear to old version 1.5? How should I do that?
Thanks for your help, have a nice day.
nicodvt said:
Hi
I've made the update Android Wear 2.0 on my LG G Watch R (through the Play Store).
However, i really do not like the new interface and how notifications are now displayed.
Is it possible de downgrade Android Wear to old version 1.5? How should I do that?
Thanks for your help, have a nice day.
Click to expand...
Click to collapse
you can flash stock image via fastboot https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
Thanks @ingbrzy for the advise, I have not found any other easiest solution to downgrade Android Wear 2.0 to Android Wear 1.5.
If it can help others, thi is how I flashed a stock image with Android Wear 1.5 on my LG G Watch R:
Enabled "Developer tools" on my watch
Connected my watch to my computer
Unlocked my bootloader with WinDroid Toolkit
After selected my device, on first screen: "Unlock Bootloader"
Downloaded and installed ADB Installer (v1.4.2)
Downloaded stock images of build "M1D65H" from this topic
Inspirated by this guide, opened a command line prompt and entered the following commands
Code:
fastboot -w
Code:
fastboot flash boot M1D65H_boot.img
Code:
fastboot flash recovery M1D65H_recovery.img
Code:
fastboot flash system M1D65H_system.img
Rebooted my watch with command
Code:
fastboot reboot
That's finished, my watch was again on Android Wear 1.5 <3
After having downgraded, has anyone managed to get rid of the update message?
midafaya said:
After having downgraded, has anyone managed to get rid of the update message?
Click to expand...
Click to collapse
Yeap, I rebooted my watch and had no more the update message.
nicodvt said:
[*] That's finished, my watch was again on Android Wear 1.5 <3
[/LIST]
Click to expand...
Click to collapse
Hi Nicodvt. Thank you for this good summary.
Unfortunatly, our friends from Google have perhaps not performed a lot for the Android Wear 2.0 new features implementation but they are really good in the development of their OTA procedure!
After the downgrade to AW1.5, even after the installation of the Android Wear 1.5 apk smartphone application and settings in Playstore not to automatically update the applications, the "always on" notification on the watch to install the new version of Android Wear 2.0 appeared one day after the downgrade....
See post below to remove the notification.
I have done tried this, not really sure what I am disabling though, but those services look like thay could bring trouble ... We'll see :silly:
Code:
laptop$ adb shell
[email protected]:/ $ su
[email protected]:/ # pm disable com.google.android.gms/.update.SystemUpdateService
Component {com.google.android.gms/com.google.android.gms.update.SystemUpdateService} new state: disabled
[email protected]:/ # pm disable com.google.android.gsf/.update.SystemUpdateService
Component {com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService} new state: disabled
adlx.xda said:
I have done tried this, not really sure what I am disabling though, but those services look like thay could bring trouble ... We'll see :silly:
Code:
laptop$ adb shell
[email protected]:/ $ su
[email protected]:/ # pm disable com.google.android.gms/.update.SystemUpdateService
Component {com.google.android.gms/com.google.android.gms.update.SystemUpdateService} new state: disabled
[email protected]:/ # pm disable com.google.android.gsf/.update.SystemUpdateService
Component {com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService} new state: disabled
Click to expand...
Click to collapse
Ah, that seems to work (for now)!
It removed the notification (after applying and rebooting) and has not reappeared for 45 minutes even after a few reboots.
I confirm these 2 commands seem to remove the upgrade notification.
For information, the creation of an empty update.zip file in the /cache/ folder was not enough and the upgrade notification appeared spontaneously one day later.
Thanks
It's great, I also want to come back the ver 1.5, but i dont have an experience in this field. I have problem in step 2 and try to install the ADT,... but it doesnt work very well. Can I contact to you via facebook or skype? Thank you.
nicodvt said:
Thanks @ingbrzy for the advise, I have not found any other easiest solution to downgrade Android Wear 2.0 to Android Wear 1.5.
If it can help others, thi is how I flashed a stock image with Android Wear 1.5 on my LG G Watch R:
Enabled "Developer tools" on my watch
Connected my watch to my computer
Unlocked my bootloader with WinDroid Toolkit
After selected my device, on first screen: "Unlock Bootloader"
Downloaded and installed ADB Installer (v1.4.2)
Downloaded stock images of build "M1D65H" from this topic
Inspirated by this guide, opened a command line prompt and entered the following commands
Code:
fastboot -w
Code:
fastboot flash boot M1D65H_boot.img
Code:
fastboot flash recovery M1D65H_recovery.img
Code:
fastboot flash system M1D65H_system.img
Rebooted my watch with command
Code:
fastboot reboot
That's finished, my watch was again on Android Wear 1.5 <3
Click to expand...
Click to collapse
dungkr89 said:
It's great, I also want to come back the ver 1.5, but i dont have an experience in this field. I have problem in step 2 and try to install the ADT,... but it doesnt work very well. Can I contact to you via facebook or skype? Thank you.
Click to expand...
Click to collapse
Check your private message @dungkr89 if you want to reach me.
Hi,
If you have some difficulties, I made this memo for me.
Downgrade LG G Watch R and block OTA upgrades
---------------------------------------------
Prepare the PC
--------------
Install adb-setup-1.4.3.exe on the PC
Place in folder (C:/wear for example) all the necessary files :
- M1D65H_boot.img
- M1D65H_recovery.img
- M1D65H_boot_system.img
- SuperSU-v2.78_Lg-G-Watch-R.zip
- twrp-3.0.0-0-Lg-G-Watch-R.img
Prepare the watch and smartphone
--------------------------------
On the smartphone, dissociate and restore factory settings on the watch.
Remove ALL applications on the smartphone in relation with the wear watch (excepted Android wear). This is usefull to avoid a long installation with risk of applications not compatible with the Android Wear version which will be installed on the watch.
Reassociate the watch with the smartphone
On the watch :
Activate developper mode (click 7 times on the build number in version menu)
Then in the developper menu, activate adb degug
Connect the watch to the pc via usb
On the PC :
DOS commands invite
Change directory (cd) to point he folfer where are located the .img files.
Type:
adb devices
// The watch device is present and ready
// Switch the watch in fastboot mode
adb reboot bootloader
adb devices
// If the watch is seen oem locked you have to type:
fastboot oem unlock
// If the watch has not been restored (I recommend to do it before via the smartphone)
//fastboot format userdata
//fastboot format cache
//fastboot format system
Send the firmware to the watch
------------------------------------
fastboot flash boot M1D65H_boot.img
fastboot flash recovery M1D65H_recovery.img
fastboot flash system M1D65H_system.img
Restart the watch via the screen menu
ROOT the watch
--------------
adb reboot bootloader
fastboot flash recovery twrp_xxx.img
//fastboot boot twrp_xxx.img (if command below is rejected)
adb push SuperSU_xxx.zip /sdcard/
// From the watch screen, by typing on the screen and following instructions, move to sdcard folder and install from zip the SuperSU_xxx.zip application
Then, when the patch has been installed (quite long), the watch has restarted. Reconnect to the watch via the PC and adb commands
Deactivate OTA
--------------
adb reboot bootloader
adb devices //to make sure your watch is connected
adb shell
> su
> pm disable com.google.android.gms/.update.SystemUpdateService
> pm disable com.google.android.gsf/.update.SystemUpdateService
> exit
Before to reassociate the watch with the smartphone, eventually, remove the Android Wear application on the smartphone and reinstall the Android Wear V1.5.apk on the smartphone.
Reassociate the watch with the smartphone.
Thanks for this thread! I am having issue getting SU in cmd. I have installed 3 different TWRP and 3 different SuperSU.zip trying to get it to work. I can't seem to get any of them to execute su commands. When trying I get a FC on SuperSU on watch, and adb does nothing after
- adb shell
- su
- then nothing happens, and I eventually get SuperSU FC on watch.
Thanks in advance for the help.
Thanks both for the re-flash guide and the commands for disabling the update service. Had a problem not finding appropriate SU and TWRP images, but after finding them I'm finally free of the damn 2.0 and the update notification too.
SU: SuperSU-2.78-wear.zip
TWRP: twrp-3.0.0-0-lenok+squashfs.img
I did not check any other root-needing apps, and as far as I'm concerned, I'm done with updates for the lifetime of this watch...
nagi603 said:
Thanks both for the re-flash guide and the commands for disabling the update service. Had a problem not finding appropriate SU and TWRP images, but after finding them I'm finally free of the damn 2.0 and the update notification too.
SU: SuperSU-2.78-wear.zip
TWRP: twrp-3.0.0-0-lenok+squashfs.img
I did not check any other root-needing apps, and as far as I'm concerned, I'm done with updates for the lifetime of this watch...
Click to expand...
Click to collapse
That's the su and twrp I have installed on my watch at this time, I am not able to get su commands to execute. Is there something else that needs to be done after installing these? Thanks.
I want to get rid of the automatic upgrade to AW 2.0, so I want to apply the recipe you have kindly shared, but I don´t know how to do it because it is my first time with ADB commands.
I have already ADB installed and USB debugging enabled. I can type "adb devices" and my watch is listed.
The question is how to apply the (two?) commands you suggest.
- Should I type "laptop$ adb shell" ??
- At the $ prompt I have tryed to type "su" but get an error.
- Also: the two commands are "one single line" each, like "...systemUpdateService Component ....", or they are two lines each command?
- Should the watch be rooted to do this ?
Thank you very much.
PD: I have flashed my watch back to AW 1.5 with no problems, using the instructions given in this link:
https://forum.xda-developers.com/g-watch-r/general/andorid-wear-2-0-t3382032/page23
adlx.xda said:
I have done tried this, not really sure what I am disabling though, but those services look like thay could bring trouble ... We'll see :silly:
Code:
laptop$ adb shell
[email protected]:/ $ su
[email protected]:/ # pm disable com.google.android.gms/.update.SystemUpdateService
Component {com.google.android.gms/com.google.android.gms.update.SystemUpdateService} new state: disabled
[email protected]:/ # pm disable com.google.android.gsf/.update.SystemUpdateService
Component {com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService} new state: disabled
Click to expand...
Click to collapse
[/COLOR]
paggps said:
I want to get rid of the automatic upgrade to AW 2.0, so I want to apply the recipe you have kindly shared, but I don´t know how to do it because it is my first time with ADB commands.
I have already ADB installed and USB debugging enabled. I can type "adb devices" and my watch is listed.
The question is how to apply the (two?) commands you suggest.
- Should I type "laptop$ adb shell" ??
- At the $ prompt I have tryed to type "su" but get an error.
- Also: the two commands are "one single line" each, like "...systemUpdateService Component ....", or they are two lines each command?
- Should the watch be rooted to do this ?
Thank you very much.
PD: I have flashed my watch back to AW 1.5 with no problems, using the instructions given in this link:
https://forum.xda-developers.com/g-watch-r/general/andorid-wear-2-0-t3382032/page23
I have done tried this, not really sure what I am disabling though, but those services look like thay could bring trouble ... We'll see :silly:
Click to expand...
Click to collapse
The commands are single lines, and it will require root. Make sure you use twrp listed above, and super su 2.78 for wear, also listed above.
It's clear that the downgrade to AW1.5 is quite easy. However, it's less obvious to block the OTA!
For that, it's mandatory to root the Watch and I didn't find a clear notice to do it. After many atempts, I did it without clearly understand how I made it!!!! But it's done, and the upgrade notification has disappeared.
I wrote my onwn notice (in case I want to try again in few months a new attempt to test for instance the next AW2.1...) here.
Somebody in this forum could write a full clean procedure for newbie with all the links to do the downgrade and OTA disabling in one shot with a 100% success.
nicodvt said:
Thanks @ingbrzy for the advise, I have not found any other easiest solution to downgrade Android Wear 2.0 to Android Wear 1.5.
If it can help others, thi is how I flashed a stock image with Android Wear 1.5 on my LG G Watch R:
Enabled "Developer tools" on my watch
Connected my watch to my computer
Unlocked my bootloader with WinDroid Toolkit
After selected my device, on first screen: "Unlock Bootloader"
Downloaded and installed ADB Installer (v1.4.2)
Downloaded stock images of build "M1D65H" from this topic
Inspirated by this guide, opened a command line prompt and entered the following commands
Code:
fastboot -w
Code:
fastboot flash boot M1D65H_boot.img
Code:
fastboot flash recovery M1D65H_recovery.img
Code:
fastboot flash system M1D65H_system.img
Rebooted my watch with command
Code:
fastboot reboot
That's finished, my watch was again on Android Wear 1.5 <3
Click to expand...
Click to collapse
Hi,
Using you guide to go back to 1.5 on g watch r but im stuck on step 6......
Only thing i can do in adb i type Y and nothing else?
Hi,
I try follow your steps, everything seems to be fine. But after last command 'fastboot reboot' I am still booting to fastboot. Please do you know what can be wrong here?
Thanks
A Noobs guide to Galaxy Note 4 Verizon Motherboard Hardware repair and replacement
and Other Samsung Galaxy Note 4 repair ( Att, Tmobile etc ) starting in thread 2 ( user input welcome )
My Overheat Heat and flash problem issues leading to
OEM Motherboard replacement and acquiring ROOT again
OP Note : read the whole guide or for that matter any OP
Thanks to many XDA-Developers forums, if you are not quoted or mentioned here I will add you !!
Device : Samsung Galaxy Note 4 Verizon SM-910V this OP ONLY !!!
Code:
[COLOR=Red][B]Your warranty is now void.[/B][/COLOR]
*most likely you don't have a warranty because you broke it, ROM'd it, its old and past warranty anyway !**
So, There is no warranty anyway, not even if you did anything in this thread to it
We are not responsible for bricked devices, dead SD cards,
thermonuclear war, or your getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this guide
before flashing it! (thanks @hsbadr)
YOU are choosing to make these modifications, and if
you point the finger at anyone for messing up your device, we will laugh at you
Symptoms : ROMs not flashing/installing , crashing, High heat, low battery life on new battery hardware note working specifically fingerprint.
Problems : digging through many forums 2 years later to root and unlock the bootloader, it took DAYS
Solution: keep track of my progress and make a useful step by step NOOB guide for Everything !
Section 1: Repairs
Then the rest of the sections are for Rooting, Installing TWRP custom recovery, fixing bootloader , and installing ROMS
Section 2: Flashing via ODIN and the correct rootable OEM rom 5.1.1 on a windows PC
section 2a: Flashing via Heimdall on a Linux device --need comments
Section 3: Achieve temporary root to install bootloader fix
Section 4: Use of ADB to (windows and linux ) to copy over bootloader fix
Section 5: install TWRP custom recovery and your first rom
Section 1: Repairs
If you have to replace the motherboard, and you have any other futzy component, might as well order it at this point, your going through pretty much the same process. I am only doing the motherboard, but the cameras and USB board are right there as well on this repair
I have been running a rooted Verizon Galaxy note 4 since Cynogenmod crashed and switched to Lineageos 14 and then 15.
Here is the forum
https://forum.xda-developers.com/no...eo-8-1-0-unofficial-lineage-15-1-rom-t3760969
After several suggestions and searches, many users hinted I may be getting a Bad internal memory,
which refuses to write anymore.
So I had to go to Walmart and buy a LG Straight talk phone to use as my daily driver,
Then I ordered a new motherboard from China, 29.00 on Aliexpress.
See OP thread #2 below!! It was not fun searching for it, but I saved $20 to $40 from buying on ebay
What I bought may not be available from this seller, but here is the link. Use a desktop browser, it will show "suggested" other devices...
Code:
[URL]https://www.aliexpress.com/item/with-Android-System-Original-unlocked-for-Samsung-Galaxy-Note-4-N910V-Motherboard-Good-Working-Free-Shipping/32802513232.html?spm=a2g0s.9042311.0.0.66e04c4dpohrQm[/URL]
When I received it , it was time to look for a repair procedure on YouTube.
Hardware needed: thin shim and 00 size phillips, AND a blank cheap SD card you don't mind losing. It may be unusable after we are done
Cell Phone repair tool kit really helps save your fingernails !
Complete note 4 teardown video:
Code:
[media=youtube]ZND9Q73wjr8[/media]
Just the Motherboard video
Code:
[media=youtube]5KpT755hNpM[/media]
In the second video, you can see the phone booting up as a test to see if you have all the connections correct.
Because it came from china, its a good idea to setup your user and
download the app CPUz before you put all the screws back in,
and check to see if you have a real or fake chipset.
Yaayyyy mine was real . Thanks Aliexpress.
Button it up and do a factory reset (it booted up set up as a no user) so I wanted a fresh install oem with my user.
Section 2: Installing the Correct rootable OEM rom so we can install Anything else.
FIRST check to see if you have the emmc brickbug or you will BRICK it !!
1. Google play store install eMMC Brickbug
If your long number starts with 15xxxxxxxxxxxxxxxxx, YOU are Golden ! if not STOP, get another board ! or you are going to waste time , and get another board !
The Galaxy Note 4 Verizon had a special custom locked bootloader installed after the 4.4.4 release to 5.0.1 and made it very difficult to get
root access to your device.
I saw the notice
DON'T UPDATE YOUR BOOTLOADER TO ANYTHING AFTER THE LATEST BUILD AS OF 4/19/16
warning about a week to late. So I finished out my 2 year contract and watched the forums.
Seriously noobs, don't update your new motherboard ...
The rom pre-installed on my replacement motherboard was already setup booted to a running 5.0.1 oem rom, I could not root it.. with any method I remember downgrading my 6.x.x to 5.1.1 in one of the many forums listed here at XDA
This one was the one I used back then, and It turned out that is where I started..
Only a Verizon Samsung Galaxy note 4 Developer Edition has the ability to install custom roms, and most likely the motherboard you bought or have is NOT a developer edition
IF you have a eMMC that starts with 15 we can reprogram it a developer edition
Thanks to @hsbadr
Here are most of the downloads we need:
Code:
[URL]https://forum.xda-developers.com/devdb/project/?id=15720#downloads[/URL]
2. Download Odin, Download TWRP, and Samsung_unlock_n4-fix
3. On your windows PC, create a folder c:/Odin and extract the Odin zip file there, and copy the TWRP image there
4. Download the following OEM root able ROM to your c:/Odin folder
Code:
[URL]https://forum.xda-developers.com/devdb/project/dl/?id=18880[/URL]
5. Plug your phone into a USB port on your Windows PC
6. Install the necessary drivers if they don't automatically install from Samsung
Code:
[URL]https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows[/URL]
7. Set up your phone for flashing ROM and communicating
Settings - Security - Unknown sources- : check allow
settings - system -about phone - build number : click several times until you activate developer options
settings - system -about phone - developer options : Android Debugging : enable android debug bridge
settings - security - reactivation lock : Turn OFF or you will brick your device ( may vary where this is at . Important to turn off )
Power Off phone
Enter Download Mode - press and hold in this order <down arrow> <home> <power> until screen comes on. release buttons.
press up arrow to enter download mode
8. Open windows explorer and go to your c:/Odin folder. You should have an odin exe file, and the twrp file, and the large rom file.
a. right click odin exe and open as administrator
b. check to see if your connected to your phone. you should see a blue box in upper left with a com under it.
If you unplug your phone, you should hear the disconnect notice and the com and blue bar will go off, and when you connect, the com and blue bar and reconnect noise should appear.
9. click the AP button box, select the ROM file that you downloaded above.
NOTE : this ROM will disable WIFI so you wont be able to use the play store unless you have cellular connection.
you will have to transfer other files via usb cable !
Click start, do not unplug! until it stops.
10. Device will reboot. Remove cable, and battery before boot completes
11. Enter recovery mode . Press in order ,<volume up><home><power>
wait for the little android dude to do his thing, then there will be a menu. select factory reset, and reset and let it reboot
Set up minimal user or as a new phone with no user and check the settings in step 7
Set up your phone for flashing roms and communicating
Settings - Security - Unknown sources- : check allow
settings - system -about phone - build number : click several times until you activate developer options
settings - system -about phone - developer options : Android Debugging : enable android debug bridge
settings - security - reactivation lock : Turn OFF or you will brick your device ( may vary where this is at . Important to turn off )
Yayy, you now have a rootable device
Section 3 Achieve temporary root to install bootloader fix
In my try to obtain temporary root, I tried every method in all the forums ( go ahead and look and try )
The only 2 programs that reported to work is Kingroot, and Kingoroot. These are APK's that are NOT in the play store
you will have to download them and install them as unknown sources. I was only able to install kingroot . Kingoroot apk would not install
in both my 5.0.1 original on my motherboard, as well as what we just installed 5.1.1 I was unsucessful at obtaining root with these programs
Then I remembered Kingoroot has a windows version that installs on the PC <dangerous dont install yet>
On your PC you will need AVG antivirus to catch the malware ( other antivirus may work but this is what I had ) my PC is windows 7 ultimate
Advanced Users only :Recommend running a virtual machine with windows so as to keep your PC completely malware free. just delete the VM after this process !
This section you will need on your Note 4 from the Play Store : root checker
You will need a throw away SD card
You will need read through section 4 and 5 and get all files and programs there ready to install use and or transfer
0.5 update your AVG
1. With AVG installed on my PC, and my phone connected as a mtp with usb I downloaded and installed Kingoroot for windows.
https://www.kingoapp.com/
NOTE after not being able to install forum recommended kingoroot apk's i dint want wast time install the newest kingoroot apk from the website. Maybe it will work for you. If you do get kingoroot apk to work on your Note 4 let me know.
2. In the install process for kingoroot windows version AVG will quarantine a file.
there will be a couple popups .. close them
when its installed it will open and start talking to your phone.
3. press the root button.
It will take 30 sec to a minute to install some files on your phone and achieve root, there will be a new floating toolbar on the phone. root will disappear after a reboot, but not the resident programs this root is pretty stable, but i was not able to install SuperSUME (paid version ) as recommended in a XDA guide to obtain permanent root for this 5.1.1 rom. If your successful with super SUme with this let me know.
4. Open root checker to verify ! yayy.
5. Cleanup instructions when finished with this guide below
Section 4: Use of ADB to (windows and Linux ) to copy over bootloader fix
1. Your Note4 phone should be running with root, make sure phone is connected
Explanation : ADB is a Google provided tool for the android platform. It communicates with your phones operating system , transfers files , and actuates programs remotely in the background. totally necessary for development of ROM's, TWRP, and programs for every android device
You may or may not know that your android device is running a Linux kernel, with some Linux programs, with custom folders and custom files and settings, and the touch screen is the GUI graphical user interface touch input.
ADB is a command line user interface, when you turned this on in Developer settings, the kernel is listening constantly on the USB com port and some times on the WiFi com port for commands. if you don't need it turn it off, it could be a security hole, but we need it on.
It works great on windows, mac, or Linux varieties
2. Install on your computer
Code:
[URL]https://developer.android.com/studio/releases/platform-tools[/URL]
If you have linux, your distribution may have a package you can install from your distribution. Then it will be in your path as a command
3. Windows users , extract or install into c:/ADB and add that to your PATH variable if you want to use it all the time as a command
4. Open a command prompt window (search command or cmd , right click open as administrator)
5. If you have ADB folder in your path or are running Linux change directories to the folder where you downloaded the Samsung n4 fix file
6. You should still have root
type
Code:
adb devices
The ADB daemon ( little server program ) will start and return some information.
your phone will have a popup screen and should ask for permission, click allow
again type
Code:
adb devices
7. You should see something like this
Code:
List of devices attached
123a12ab device
The 123a12ab is made up. Yours will be specific to your device.
If you see something listed like the above adb is working. Now on to the next command to move the Samsung_unlock_n4-fix to the phone.
type dir ( or ls -al for Linux users ) to verify Samsung_unlock_n4-fix is in your directory
8. Send Unlocker to Phone with adb
Type or copy and paste the following command:
Code:
adb push samsung_unlock_n4-fix /data/local/tmp/
You should see successful output .
If you don't, check your PATH, check if your in the right folder, or make sure samsung_unlock_n4-fix is in your adb folder
9. Activate the unlocker. This requires root and a reboot. After the reboot you have to go and reactivate root in Section 3.3 above
type the following
Code:
adb shell
Congratulations you are now looking at the linux command line interface on your phone . the $ prompt means you are in the shell
10. activate superuser mode ( kind of like administrator in windows but more powerful )
type
Code:
su
then press enter key
YOU SHOUD NOW SEE a # prompt
This means you succeed in root. If you dont see a # you missed a step above somewhere , or your root was unstable and took too long to get to this point,that is why I said read thru this section and get ready..
Ok at this point we have the file we needed transfered, we have root, now we need to upgrade the permissions on the file so #root level of the operating system can use it !
The next command does all that then executes the command to upgrade your phone to developer edition !
Copy and paste the following command series and press enter.the && joins each command
Code:
cd /data/local/tmp/ && chmod 777 samsung_unlock_n4-fix && chown root.root samsung_unlock_n4-fix && ./samsung_unlock_n4-fix
The device will reboot and flash the developer code.
You should see some sort of progress in the window.
When done ,unplug the cable and pull the battery to shut down phone.
11. Make sure you have a cheap throwaway SD card installed !
One More Time to unlock the boot loader !! section 3 and 4 short version
Put the battery and cable back in and turn the phone back on and make sure its plugged in your PC.
Now repeat the kingoroot PC to gain temp root
open a command prompt or shell
type or copy paste the following to verify its connected
Code:
adb devices
transfer the fix
Code:
adb push samsung_unlock_n4-fix /data/local/tmp/ && a
open the shell on your phone
Code:
adb shell
gain super user rights
Code:
su
unlock the boot loader
same command series
Code:
cd /data/local/tmp/ && chmod 777 samsung_unlock_n4-fix && chown root.root samsung_unlock_n4-fix && ./samsung_unlock_n4-fix
You will see your phone do a series of outputs then reboot. when it reboots, disconnect the cable.
If this step is sucessful your phone will keep rebooting. This is NORMAL . after the first or second reboot, pull the battery and pull the sd card, and set the sdcard aside. It will need to be thrown out or repartititioned to be usable. or you can keep it as a memento on your charm bracelet.
Your bootloader is NOW UNLOCKED . keep phone off until you read the next section
Section 5a: install TWRP custom recovery
Currently right now you have 5.1.1 installed with some Chinese malware on your phone and PC,
A custom developer edition and an unlocked boot loader. Lets fix them all.
Turn on phone download mode . <down volume><home><power> then volume up to enter download mode
Open Odin again ( see above )
Connect phone ( look for com and blue bar )
Select AP button, and browse to TWRP file
Press start. when finished phone will restart.
Don't let it boot all the way back up! , pull battery, and install good SD card, and if you read this section you downloaded what you needed for a new ROM onto your sdcard
Turn off the automatic rebooting in the custom tab, DO NOT select the PIT tab
Press start
Once it finishes it will say Success or FAILED
IF it says FAILED start the whole process over! you didn't unlock the bootloader !
If success, Power off the phone with the pull battery method and disconnect your cable
Press and hold these buttons immediately to enter TWRP ,
<volume up> <home> <power>.
Swipe to allow changes in TWRP.
Select backup , change to SD card, You can also plug in a memory device into the USB port. If it sees it you will be able to use that for backup space
BACKUP everything . You now have a custom recovery installed, a unlocked bootloader, and a rootable ROM Backed UP !
If you feel you want to do this all over again if you flash the OEM Samsung ROM via Odin by accident like I did, ha ha skip the next steps
Select the backup button, select all the partitions, select the source, where you want to store it.
Name the backup rooted-backup-everything-5.1.1
Select start and go make some coffee or a sandwich. its about 4 gigabytes compression, so it may take about 5 to 10 minutes
Clean up -
uninstall windows kingoroot PC and do a virus check
check for hidden folders and registry entries
Section 5b. Install your first ROM
Cleanup : After your backup WIPE your phone twice
THIS IS TO guarantee, no Kingoroot or kingroot stuff is in the phone !!!
WIPE IT TWICE !!!
Some guides (listed below ) say to adb sideload over a root file , then install an older rom. I haven tried this. Let me know if you did and are successful.
Whatever ROM you use, please post a success story in the reply's. I am interested in how you all do.
I have tried every note 4 ROM and this is the most succesful for me and most stable
I have been using this ROM for a while, and the lineageos 14 version too
Code:
[URL]https://forum.xda-developers.com/note-4/snapdragon-dev/oreo-8-1-0-unofficial-lineage-15-1-rom-t3760969[/URL]
In most all ROMS, you can update the bootloader (TWRP) by TWRP app if rooted
you can update the modem ( a partition that contains original Samsung code to run the cell and wireless ) via ODIN
Roms and patches and other goodies can be installed via TWRP by downloading to your device or transfering them to your sd card
Oem ROMS must be installed via ODIN, and will WIPE all you just accomplished. so unless your selling your device, or giving it to grandma DONT.
If you copied the rom ( usually a zip file ) and the necessary files, and have upgraded your bootloader and modem to the newest,
Now install your ROM, and after your initial setup, come back to TWRP and do a full backup !
every time you try a new rom, and get it set up, do a backup. that way you can switch and test to your hearts desire till you run out of SD memory.
The cool thing is you can backup to an external memory device ! more room !
Follow the directions in the OP of your ROM to install. Enjoy
All the above info was gleaned from the following pages
Thanks to @beaups for discovering exploit !!!
Thanks to @hsbadr [HOWTO] Bootloader Unlock and Upgrade to Marshmallow [N910VVRU2CQL1]
Code:
[URL]https://forum.xda-developers.com/note-4-verizon/development/howto-bootloader-unlock-upgrade-to-t3398144[/URL]
and his files
Code:
[URL]https://forum.xda-developers.com/devdb/project/?id=15720#downloads[/URL]
Thanks to @ryanbg [Official] Note 4 Verizon Bootloader Unlock
Code:
[URL]https://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913[/URL]
and @urgodfather
Code:
[URL]https://forum.xda-developers.com/showpost.php?p=66381707&postcount=342[/URL]
Thanks to @chriskader [HOWTO] Converting your Retail Note 4 to a Developer Edition Note 4
and @Mickey387 for discovering how to compile the note 4 32bit hardware drivers into Oreo !!
and @_mone @ripee
for maintaining and working hard on
[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [trlte][trlteduos]
Code:
[URL]https://forum.xda-developers.com/note-4/snapdragon-dev/oreo-8-1-0-unofficial-lineage-15-1-rom-t3760969[/URL]
Information Sources: felixtaf, ryanbg, kingroot, twrp, emotion, ibowtoandroid, shimp208, & urgodfather
some of this was also posted on reddit. https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked
Update:
Looking for a motherboard for a 910 that's not a v?
Thanks to user @maralexbar I need to update some info
Method 1 use eBay. Find your correct motherboard easily.
Method 2. Save some money use Ali Express ( China )
If you use Ali, and don't find your motherboard on a direct search, keep digging.
I forgot to mention this.
Looking for my Verizon motherboard, I found lots of parts like the USB internal connector etc. But no mobo. I had to go thru the store listing of the seller of the USB connector to find a vendor that had a mobo. Then I tried comparing different vendors. So do some digging. There is a billion people on Ali express selling stuff. Don't give up.
Plus Ali wants happy international buyers. So if you get a bogus item, you get your money back.
reserved #2
reserved #2
reserved #3
Reserved #3
reserved #4
Reserved #4
Thank you very much for this!!! The phone is running beautifully, smooth and fast. I ended up installing this ROM:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-resurrection-remix-6-0-0-t3768963
BJ
b1ggjoe said:
Thank you very much for this!!! The phone is running beautifully, smooth and fast. I ended up installing this ROM:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-resurrection-remix-6-0-0-t3768963
BJ
Click to expand...
Click to collapse
Your more than welcome
Announcement:
Thanks to @ripee
The lineage-17.1 thread is up!
[ROM][UNOFFICIAL][10] LineageOS 17.1 [tblte][trlte][trlteduos]
If you don't mind not having a working fingerprint sensor, or audio through the headphone jack, then Q is stable enough for daily use. As always when coming from an older rom version, it is highly recommended not to waste your time dirty flashing and just clean flash.
Q is still a work in progress, so I will still be releasing Pie builds, though maybe not as often. As in years past, once the Q bugs have been fixed up to the current Pie level, I will post about when my last Pie build will be. I will upload it to the Downloads tab located at the top of each page of this thread, and link it in the OP.
I'm starting a N8000 RADIO collection because we're having discrepancies where WiFi works on N8000 for certain ROMs for some people, but not others.
N8000 Baseband Google Drive folder
Here is a current list of Basebands in the Google Drive folder
VERSION Original Stock ROM Comment
N8000XXUDNH1 (South Africa Vodafone Android 4.4 ROM) WiFi works on @TheMorpheus Android 5.0.2 but no @lirokoa ROM's (or derivatives)
Share your baseband and help us all develop better N8000 ROMs
You will find your baseband version in Settings > About > Baseband.
If you have a N8000 with a baseband not listed above, please upload it to https://uploadfiles.io/ or a similar free filesharing site and I'll try add it to the Google Drive (so it'll be available permanently) in a timely manner.
How to dump your N8000's Baseband
You need to run a command as root on your device. I find the quickest, most convenient way is with `adb shell` and `adb pull ...`. But you could do it in a root terminal on the device and upload it from the device also.
Here are detailed instructions for doing it with ADB shell and pull (replace XXXXXXXXX with your baseband version)
1. Enable Dev Options: Go to settings > About > Software info > Tap build number 9x until Developer options is enabled.
2. Enable ADB as Root: In Settings > Developer options: Enable ADB and root over ADB
3. cd /tmp/
4. adb shell
su
dd if=/dev/block/platform/dw_mmc/by-name/RADIO of=/data/XXXXXXXXX.radio
exit
5. adb pull /data/XXXXXXXXX.radio
6. Upload XXXXXXXXX.radio for free at https://uploadfiles.io/
7. Post here
Share the link here with the basic info as per this example mentioning the latest/best ROM (in your opinion) that your device works with:
XXXXXXXXX (?Country? ?Network? Android ? ROM) WiFi works on Android ?version? ?romname? ##.# by @foo
Thank you for contributing to the N8000 community and facilitating new ROM development.
Details of WiFi issues on @lirokoa ROM's (and derivatives)
https://forum.xda-developers.com/ga...ent/rom-lineageos-14-1-nougat-t3884079/page40
In a nutshell: Not working on WPA2-PSK(AES) networks.
Although some N8000's work fine. So I'm hoping it's just a matter of swapping the Baseband.
Reserved 2
Google Drive folder is empty (?)