Related
Update: I upgraded my phone with XXKI3 2.3.5 firmware, from XXKH3.
The lag is gone, definitely a big improvement compared to XXKH3 version. The phone is very responsive and fast. Quadrant shows 4200+, pretty impressive:
{
"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"
}
The bootloader was updated, you cannot reset anymore your phone with a download jig. However, Intratech uploaded the old bootloader:
Intratech said:
If you've already flashed a full package from elsewhere and cannot reset your binary counter using the Jig just flash this package in the PDA or Bootloader (Yes both will work) section of Odin to replace the bootloaders and then you can reset the counter: http://www.multiupload.com/LQQBRQVJUD
Click to expand...
Click to collapse
Personally, I flashed the file with Odin (PDA).
The phone ring is set to silent, instead of default "Over the horizon" ringtone. Make sure you change it, your phone is not broken. See the complete list of changes, related to previous ROM.
Guide
I'm posting this procedure in a separate thread, as is easier to be linked into different forum posts. My Bell Canada phone came originally with the UGKG2 firmware, so everything listed below is based on my own experience with this version, I do not know or confirm it will work with other firmware. I currently run the official (?) XXKI3 Gingerbread 2.3.5 firmware, downloaded from samfirmware.com site (see details below). This is a wipe device release.
Personally, I read that other people flashed their phones with a different firmware... but I did not wanted to do it on my phone. I sticked with the same family XXKGx, just to be safe. Please read Electroz's explanation below.
There are 3 types of release builds: leaked, Frankenstein (compiled and tested by devs, based on demand) and official (Kies updates).
The procedure is simple (I presume you are familiar with Odin, Download Mode &Co.):
1) Get yourself the stock firmware and kernel (thank you Intratech)
2) Setup your drivers properly, avoid the Kies insanity (see below)
3) Flash the new firmware (my flash procedure, you can/should skip Re-Partition/PIT as Intratech explained)
4) Flash phone with CF-Root (I used the CF-Root-SGS2_XX_OXA_KI3-v4.1-CWM4.zip file)
5) Wipe (cache + factory reset)
6) Uninstall all Samsung crap and install additional system apps (i.e. Car Home)
7) Flash back the stock KI3 kernel (thank you Intratech, password: [email protected])
8) Wipe (cache + factory reset)
9) Connect your device to a download jig, to reset the flash counter (old bootloader needed)
Phone & Modem Drivers Setup
Note: This procedure was tested with Windows 7 Ultimate 64bits. If you already installed Kies, uninstall all related software/drivers and clean your registry. Or do a clean Windows install just to be safe.
1) With your anti-virus off, put your phone in Download mode and connect the USB cable. Windows Update will start to download right away the modem and USB drivers. Make sure you select the Windows Update option, when asked into driver install window.
2) Once the modem drivers installed, disconnect the cable, reboot the phone in normal mode and reconnect the cable again. A new set of drivers will be installed for the rest of USB interface.
Important: You need do it in the SPECIFIC order mentioned above, or else the modem drivers will not be installed and you will not be able to use properly Odin. I know this because I tried the other way around.
Initial Phone Setup
Once the phone rebooted, you will be welcomed to the Android Setup.
1) First, set the language from English UK to whatever you like.
A Network warning related to Date and Time will pop, tap on Cancel.
2) Tap the Android robot and setup your phone.
There is NO need to change any other settings, the phone will automatically detect the Bell network.
If for some reason it does not, once you completed your basic setup go to:
Settings > Wireless and Network > Mobile networks > Network operators
It will start the scanning and pop 3 Bell networks, pick the first one. Again, this is in case your phone does not work with calls, voicemail or SMS.
Notes
You should uninstall the CWM app once you flashed back the stock kernel, is half useless. I tested the new Superuser app from Android Market, it will properly upgrade to latest version and also upgrade the su binary on XXKI3 firmware. If you plan to poke around your phone with the Terminal, you will lose all the fancy Linux commands. (grep etc.)
Personally, I purchased ChainsDD's Superuser Elite key. It will allow you to pin protect your rooted device, among other useful things that are planned to be added (built-in terminal). I upgraded Superuser to version 3 and everything works properly.
Battery Power Savings
I always leave my phone with all default options, including screen auto-adjust. The only options I turn off are:
Settings > About phone > Software update > Auto update Disabled
Settings > Applications > Samsung Apps > Off
Personally, I have no idea who started the battery calibration myth in S2. It is useless to "overcharge" the battery, as the software has a check to stop automatically the charge once the battery is 100% while the battery itself has a build-in controller that can't be wiped.
Example of battery stats with the phone in idle mode for approx. 18hrs (86%) and 109hrs (2%):
Running Services
I use Wifi N with a Cisco E4200 DD-WRT (phone at 20"), these are my running services:
Code:
PID USER VSZ STAT COMMAND
1 root 508 S /init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [migration/0]
5 root 0 SW [watchdog/0]
9 root 0 SW [events/0]
11 root 0 SW [khelper]
15 root 0 SW [async/mgr]
16 root 0 SW [pm]
19 root 0 SW [suspend]
20 root 0 SW [sync_system_wor]
151 root 0 SW [s5p-tmu]
337 root 0 SW [sync_supers]
339 root 0 SW [bdi-default]
341 root 0 SW [kblockd/0]
356 root 0 SW [khubd]
359 root 0 SW [kseriod]
394 root 0 SW [irq/331-max8997]
434 root 0 SW [kmmcd]
527 root 0 SW [kondemand/0]
540 root 0 SW [pet_watchdog/0]
549 root 0 SW [khungtaskd]
550 root 0 SW [kswapd0]
599 root 0 SW [aio/0]
612 root 0 SW [crypto/0]
1237 root 0 SW [sec_jack_wq]
1240 root 0 SW [irq/350-sec_hea]
1245 root 0 SW [spi_gpio.3]
1262 root 0 SW [svnet_txq]
1274 root 0 SW [file-storage]
1300 root 0 SW [irq/328-mxt224_]
1306 root 0 SW [irq/325-k3g]
1312 root 0 SW [irq/326-proximi]
1315 root 0 SW [cm3663_light_wq]
1316 root 0 SW [cm3663_prox_wq]
1366 root 0 SW [mali_dvfs]
1369 root 0 SW [mali-pmm-wq]
1378 root 0 SW [sii9234_wq]
1379 root 0 SW [irq/481-mhl_int]
1380 root 0 SW [irq/496-mhl_wak]
1383 root 0 SW [irq/343-max1704]
1394 root 0 SW [kstriped]
1396 root 0 SW [kmpathd/0]
1398 root 0 SW [kmpath_handlerd]
1399 root 0 SW [ksnapd]
1400 root 0 SW [kconservative/0]
1414 root 0 SW [ktflash_requlat]
1429 root 0 SW [usbhid_resumer]
1432 root 0 SW [binder]
1441 root 0 SW [irq/333-IPC_HOS]
1452 root 0 SW [mmcqd]
1481 root 0 SW [l2cap]
1482 root 0 SW< [krfcommd]
1488 root 0 SW [dynamic hotplug]
1501 root 0 SW [melfas_touchkey]
1506 root 0 SW [fimc0_iqr_wq_na]
1509 root 0 SW [fimc1_iqr_wq_na]
1512 root 0 SW [fimc2_iqr_wq_na]
1515 root 0 SW [fimc3_iqr_wq_na]
1518 root 0 SW [hdcp work]
1529 root 0 SW [tvout resume wo]
1535 root 0 SW [sec-battery]
1538 root 384 S /sbin/ueventd
1761 root 0 SW [Si4709_wq]
1782 root 0 SW [jbd2/mmcblk0p9-]
1784 root 0 SW [ext4-dio-unwrit]
2563 root 0 SW [jbd2/mmcblk0p7-]
2564 root 0 SW [ext4-dio-unwrit]
2566 root 0 SW [jbd2/mmcblk0p1-]
2567 root 0 SW [ext4-dio-unwrit]
2570 root 0 SW [jbd2/mmcblk0p10]
2571 root 0 SW [ext4-dio-unwrit]
2579 system 868 S /system/bin/servicemanager
2580 root 6616 S /system/bin/vold
2581 system 1972 S /system/bin/notified_event
2583 root 732 S /system/bin/debuggerd
2584 radio 9512 S /system/bin/rild
2585 system 4624 S /system/bin/npsmobex
2586 system 8476 S /system/bin/drexe
2590 bluetoot 1372 S /system/bin/dbus-daemon --system --nofork
2591 root 932 S /system/bin/installd
2592 keystore 1804 S /system/bin/keystore /data/misc/keystore
2594 system 14192 S /system/bin/tvoutserver
2595 shell 800 S /system/bin/sh /system/bin/rtc_log.sh
2612 shell 780 S /system/bin/immvibed
2907 wifi 2644 S /system/bin/wpa_supplicant -Dwext -ieth0 -c/data/wifi/bcm_su
3374 media 56536 S < /system/bin/mediaserver
3375 root 15472 S /system/bin/netd
3376 root 126m S zygote /bin/app_process -Xzygote /system/bin --zygote --star
3391 system 276m S system_server
3496 root 0 SW [iscan_sysioc]
3497 root 0 SW [dhd_watchdog]
3498 root 0 SW [dhd_dpc]
3499 root 0 SW [dhd_sysioc]
3502 system 152m S com.android.systemui
3511 app_99 168m S com.sec.android.inputmethod.axt9
3521 radio 155m S com.android.phone
3522 app_66 148m S android.process.media
3528 app_53 134m S com.sec.pcw.device
3532 system 134m S com.samsung.bt.avrcp
3536 bluetoot 134m S com.broadcom.bt.app.system
3544 app_12 176m S com.sec.android.app.twlauncher
3604 app_54 173m S com.google.process.gapps
3631 app_12 148m S android.process.acore
3688 app_84 135m S com.sec.android.app.FileTransferManager
3777 app_36 137m S com.sec.android.widgetapp.weatherclock
3927 app_38 136m S com.sec.android.widgetapp.apnews
4193 app_91 137m S com.sec.android.app.clockpackage
4220 app_16 137m S com.android.providers.calendar
4234 app_100 134m S com.sec.android.daemonapp.accuweather
4255 app_78 159m S com.google.android.gm
4333 app_81 174m S com.cooliris.media
4366 app_119 144m S com.google.android.apps.reader
4376 app_103 170m S com.levelup.beautifulwidgets
4435 app_37 138m S com.sec.android.widgetapp.stockclock
4453 app_16 138m S com.android.calendar
4476 system 156m S com.android.settings
4486 app_112 177m S com.google.android.music
4633 app_82 137m S com.sec.android.app.fm
4752 app_40 135m S com.sec.android.app.samsungapps.una
6623 app_68 185m S < com.google.android.apps.maps
9014 dhcp 916 S /system/bin/dhcpcd -ABK eth0
10732 graphics 139m S com.sec.android.app.screencapture
11958 system 138m S com.wssyncmldm
11989 system 135m S com.sec.android.providers.drm
11997 app_1 139m S com.smlds
12037 app_102 139m S com.skype.raider
13094 app_5 141m S jackpal.androidterm
13136 app_115 135m S com.noshufou.android.su
13170 app_68 149m S com.google.android.apps.maps:NetworkLocationService
13180 app_68 144m S com.google.android.apps.maps:FriendService
13503 app_83 141m S com.sec.android.app.FileTransferServer
13579 root 0 SW [flush-179:0]
13646 shell 1684 S /sbin/ext/busybox sh /sbin/sleep 3600
13651 shell 1676 S /sbin/ext/busybox /sbin/sleep 3600
13707 app_68 154m S com.google.android.apps.maps:HotpotService
13788 system 135m S com.android.MtpApplication
13825 app_5 796 S /system/bin/sh -
13858 root 796 S sh -
13966 root 1684 S /sbin/ext/busybox sh /sbin/ps
13971 root 1716 R /sbin/ext/busybox /sbin/ps
CSC (Cell Site Controller)
The default CSC setting in XXKI3 is KOR. You can check it with: *#272*{IMEI}#
where the {IMEI} value represents the 15 digits of your IMEI (International Mobile Equipment Identity).
I personally used the default option (KOR) and the phone works perfect, with great reception:
There are some people who wonder if they should change the CSC. I will quote Intratech on this matter as he answered perfectly to my question:
Intratech said:
Some people do and some just use the CSC packaged with whichever firmware they flash. As long as your APN and SMS/MMS settings are ok there is no need to flash another CSC package.
Click to expand...
Click to collapse
Fast Dormancy
Some people noticed that their network idle on 3G, instead of HSPA+. That is absolutely normal, because of the "fast dormancy" feature. If enabled, HSPA+ will rapidly disconnect from the network once the information is sent or received. That will penalize the actual network you are on, unless the carrier network and your phone talk to each other in a way that takes battery life as well as network congestion into consideration. For this to work, both networks and smartphones have to implement a standardized version of the fast dormancy feature. Bell Canada supports this feature and by default Fast Dormancy is enabled into XXKI3 firmware.
You can check it with: *#9900#
You should call your carrier to see if they have it implemented. Probably your tech support will look like you are speaking Chinese and escalate it to a more knowledgeable guy. This is the average download speed I get on XXKI3 (network is switching automatically on HSPA+):
There are some reports where people confirmed that the UGKG2 build allowed you to reach faster download speeds (up to 9MB). Personally I think 6MB over a cell network is already more than perfect for tethering, not to mention that there are many factors to be taken into consideration when you deal with a wireless transmission. (location, tower antenna, weather, etc.)
Random Restart
The screen needs minimum 500Mhz to get out of Sleep Mode. Some custom ROM's use a low voltage or "underclock" feature that reduces the power consumption but also the number of CPU steps. That is what makes your phone crash and reboot randomly. If you use an external sdcard, do a sd wipe just to be safe. It should take several hours, so do it over the night. Personally, I did not experienced any random reboots using neither the XXKH3 or XXKI3 firmware.
Some people might have bad battery contacts on their S2. Basically, the phone shuts down while in your pocket. Clean the battery terminals with some audio head tape cleaner and cotton swabs, than make sure the contacts are proper.
You could also have a RAM (hardware) issue. Bad memory degrades fast so you will see your random reboots pop at a faster frequency. If you did all the above and still experience random reboots, run adb logcat to see what is going on at that specific moment. If you get error codes like:
Code:
code 1 (SEGV_MAPERR), fault addr 00000000
you are dealing with bad memory unfortunately and need to service your phone.
Manage system apps with Terminal
Personally, I decided to stick with a terminal for now, I feel more comfortable to see what is going on with my own eyes in my phone. A good alternative to Terminal would be the SystemApp Remover, is faster and more robust compared to Titanium Backup as it does only one task (backup/remove system apps).
I did an output list of all the packages:
Code:
$ pm list packages -f >> /sdcard/packages 2>&1
so I know now where each package is located and what is the associated name.
All I have to do is run:
Code:
$ su
# rm -f /system/app/package.{apk,odex}
# pm clear PACKAGE
# pm uninstall PACKAGE
Running "mount | grep system" tells me right away where and how /system is mounted:
Code:
/dev/block/mmcblk0p9 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
so all I have to do is change the mount perms to write, instead of read:
Code:
# mount -o remount,rw /dev/block/mmcblk0p9 /system
Package Manager commands:
Code:
# pm
usage: pm [list|path|install|uninstall]
pm list packages [-f] [-d] [-e] [-u] [FILTER]
pm list permission-groups
pm list permissions [-g] [-f] [-d] [-u] [GROUP]
pm list instrumentation [-f] [TARGET-PACKAGE]
pm list features
pm list libraries
pm path PACKAGE
pm install [-l] [-r] [-t] [-i INSTALLER_PACKAGE_NAME] [-s] [-f] PATH
pm uninstall [-k] PACKAGE
pm clear PACKAGE
pm enable PACKAGE_OR_COMPONENT
pm disable PACKAGE_OR_COMPONENT
pm setInstallLocation [0/auto] [1/internal] [2/external]
The list packages command prints all packages, optionally only
those whose package name contains the text in FILTER. Options:
-f: see their associated file.
-d: filter to include disbled packages.
-e: filter to include enabled packages.
-u: also include uninstalled packages.
The list permission-groups command prints all known
permission groups.
The list permissions command prints all known
permissions, optionally only those in GROUP. Options:
-g: organize by group.
-f: print all information.
-s: short summary.
-d: only list dangerous permissions.
-u: list only the permissions users will see.
The list instrumentation command prints all instrumentations,
or only those that target a specified package. Options:
-f: see their associated file.
The list features command prints all features of the system.
The path command prints the path to the .apk of a package.
The install command installs a package to the system. Options:
-l: install the package with FORWARD_LOCK.
-r: reinstall an exisiting app, keeping its data.
-t: allow test .apks to be installed.
-i: specify the installer package name.
-s: install package on sdcard.
-f: install package on internal flash.
The uninstall command removes a package from the system. Options:
-k: keep the data and cache directories around.
after the package removal.
The clear command deletes all data associated with a package.
The enable and disable commands change the enabled state of
a given package or component (written as "package/class").
The getInstallLocation command gets the current install location
0 [auto]: Let system decide the best location
1 [internal]: Install on internal device storage
2 [external]: Install on external media
The setInstallLocation command changes the default install location
0 [auto]: Let system decide the best location
1 [internal]: Install on internal device storage
2 [external]: Install on external media
Removed System Apps
This is the list of /system apps I removed from XXKI3 firmware:
BuddiesNow.apk
Days.apk
DigitalClock.apk (I use Beautiful Widgets instead)
Email.apk (I use Gmail only)
EmailWidget.apk
GameHub.apk
GenieWidget.apk
install_flash_player.apk
Kies.apk
KiesAir.apk
kieswifi.apk
Kobo.apk
MiniDiary.apk
MusicHub_U1.apk
MusicPlayer.apk (I use Google Music instead)
PolarisOffice.apk
PressReader.apk
ReadersHub.apk
SamsungApps.apk
SamsungAppsUNA3.apk
SamsungIM.apk
SecretWallpaper1.apk
SecretWallpaper2.apk
SevenEngine.apk
ShareApp.apk
SnsAccountFb.apk
SnsAccountLi.apk
SnsAccountMy.apk
SnsAccountTw.apk
SnsDisclaimer.apk
SnsImageCache.apk
SnsProvider.apk
SocialHub.apk
VoiceToGo.apk (I use Car Home instead)
Zinio.apk
Apps ported to Galaxy S2
Some of my favorite apps, not available into Market and ported to Galaxy S2:
Google Car Home
Market Access
Google+ 2.0 (works with a Google Apps account)
Terms
ROM - software stored into read-only memory. ROM retains its contents even when the phone is turned off. ROM is referred to as being nonvolatile, whereas RAM is volatile.
Kernel - portion of the OS that handles drivers, hardware control and access for the rest of the OS.
Modem - handles the communication with your carrier.
Root - superuser privileges in any Linux OS.
yqed said:
I'm posting this procedure in a separate thread, as is easier to be linked into different forum posts. My Bell Canada phone came originally with the UGKG2 firmware, so everything listed below is based on my own experience with this version, I do not know or confirm it will work with other firmware. I currently run the official (?) XXKG3 Gingerbread 2.3.4 firmware, downloaded from samfirmware.com site (see details below).
Personally, I read that other people flashed their phones with a different firmware... but I did not wanted to do it on my phone. I sticked with the same family XXKGx, just to be safe.
Click to expand...
Click to collapse
This is wrong. I'm not sure where you got that XXKG3 is remotely the same as UGKG2, but here's an explanation of the firmware version numbers:
This is standard across most Samsung Phones.
I9000 = Model #
UG = Carrier/Area code. For example, XX = Europe, UG = Bell Mobility Canada.
K = Year = 2011
G = Month = July (H = August, I = September)
2 = Revisions that month for the specific region (aka. UG, XX, XW).
A lot of people on here think the last 3 digits are important and that if you have 2 KG3 firmware that they are the same. However, this is not the case.
You need to go by all 5 letters due to the fact that each firmware is customized by different groups at Samsung. And to prove this, just look at KG2. There are 2.3.3 KG2's and there are 2.3.4 KG2's.
It's actually possible that one area's KG2 could have been newer than another area's KG4. The best way to check, is to look at the build date in the Build.prop for each firmware.
But your assuming that KGx means they're the same is wrong. All that those numbers mean is what month/revision the firmware is. Samsung has several different teams producing firmware independently of each other for different regions. The only letters that mean the firmwares are similar are the country/carrier code (ie. UG, XX, XW).
Also, your idea of what Official firmware is, is flawed. Just because it's on samfirmware, DOES NOT make it official. Most of their firmwares are leaked test builds. If it's not released on Kies, it's not official.
Thanks for the great explanation, much appreciated. It should help many people understand better how the versioning works. About the "official" part, that's the reason why I mark it with a (?). As you said very well, it is official once is released by Samsung through updates.
The thread is related to my own experiences with the Europe MULTI firmware, based on the fact that a Bell phone specs are identical to the Europe model.
Edit: I upgraded to XXKH3 firmware successfully just now, everything works great.
I currently have a Bell branded SGSII with baseband version UGKG2.
I originally flashed it with CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.zip and then I re-flashed it with the original UGKG2 Stock Kernel from Bell.
Now my phone is rooted and stock.
Any positive/negative feedback from users running XXKH3 firmware (2.3.4) would be very much appreciated.
thvpham said:
I currently have a Bell branded SGSII with baseband version UGKG2.
I originally flashed it with CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.zip and then I re-flashed it with the original UGKG2 Stock Kernel from Bell.
Now my phone is rooted and stock.
Any positive/negative feedback from users running XXKH3 firmware (2.3.4) would be very much appreciated.
Click to expand...
Click to collapse
I ran the KH3 firmware briefly with no issues. The only annoying this was when using the program monitor widget I would experience some lag or choppiness when switching homescreens(same on KG6/KH4). On the positive side the gps accuracy and lock time was greatly improved.
Aha, I had no idea as I don't use that widget... thanks for the tip.
I usually hold the Home button until the Task Manager pops, to see the running apps. But I got used already to press the Back key every time I deal with an app... that automatically closes it.
About the GPS, the accuracy is greatly improved indeed. It takes me 1-3secs max to get a lock (with wireless networks disabled) and the accuracy is always 5meters.
Edit: There is a new Digital Clock service running now... I have no idea what makes it start, please let me know. I use Beautiful Widgets on my home screen.
The digital clock service should be part of the digital clock widget. You can try to end the process under running services and see if it stops it.
I downloaded the XXKH3 firmware but I'm not sure which files I should be using with Odin (Bootloader, PDA, Phone & CSC).
KayvinM said:
The digital clock service should be part of the digital clock widget. You can try to end the process under running services and see if it stops it.
Click to expand...
Click to collapse
I use Beautiful Widgets, so DigitalClock.apk should not be starting... Weird.
I just uninstalled the system app, no more running services. It was wasting my battery for nothing.
thvpham said:
I downloaded the XXKH3 firmware but I'm not sure which files I should be using with Odin (Bootloader, PDA, Phone & CSC).
Click to expand...
Click to collapse
See step 3 and skip the PIT file (re-partition unchecked). Also see the Update note into OP.
thvpham said:
I downloaded the XXKH3 firmware but I'm not sure which files I should be using with Odin (Bootloader, PDA, Phone & CSC).
Click to expand...
Click to collapse
I ended up re-downloading the XXKH3 from Intratech's thread and it was much easier flashing the one PDA file.
Now do I need to flash the XXKH3 stock kernel or my default stock Bell kernel?
You need the XXKH3 stock kernel, Intratech has it linked below the actual firmware link.
does it matter if CSC changes?
right now, (before root + update firmware), I still have BMC....
but once it's changed, would that create problems? If yes, what kind of problems. If no, then why do we care about CSC?
Personally, I used the samfirmware files and the phone works great. The pda.bell.ca info is present into ASN also.
Thanks for the responses everyone.
I ended flashing the stock XXKH3 kernel with the firmware. So far the upgrade has been good to me, I noticed improved battery life for the first 18 hours of usage. I will continue to use this build until I find something that is more stable and efficient then this.
A BIG THANK YOU!!!! I finally rooted and unlocked.
Originally: UGKF6
Now: XXKG5
Thanks for the guide!!!
Just 1 question though, do I HAVE TO do a factory after root? Any problem if I don't?
One thing is sure, the battery life degraded compared to XXKG3 firmware.
XXKG3 | XXKH3 (about 4hrs lost)
When I took the screenshot on KG3, I was using the phone for about 2 hours to read a book (notice the sudden drops because of the white screen), while the KH3 was always in sleep mode. So ya, there is a significant change in battery life with a tradeoff for the GPS gains.
I updated the OP.
clb09 said:
A BIG THANK YOU!!!! I finally rooted and unlocked.
Originally: UGKF6
Now: XXKG5
Thanks for the guide!!!
Just 1 question though, do I HAVE TO do a factory after root? Any problem if I don't?
Click to expand...
Click to collapse
Just curious, why you did not used the KH3 to take advantage of amazing GPS? The battery life should be a bit better also, compared to KG5. What do you mean by "do a factory"? You will lose root only if you flash back the firmware, flashing the kernel will not delete the su binary. You want to keep your phone rooted.
I strongly recommend you to spend $1 and get ChainsDD's Superuser Elite key, it will allow you to pin protect your rooted device. I upgraded to 3.0 Beta4 and everything works properly. Worth the dollar in so many ways, not just for securing the su access.
What you use to remove system app.
Thanks
Fizwiz said:
What you use to remove system app.
Thanks
Click to expand...
Click to collapse
I use Titanium Backup PRO. It allows me to backup, freeze and uninstall the unwanted apps.
One thing i have see with the XXKH3. With the KG2 im stable on H+, now im switching between 3G and H+.
Anyone else?
See Fast Dormancy info in OP. Is normal and the intended way to save you battery and bandwidth congestion.
Easiest rooting method EVER !!
No need of PC................
To gain root access, you have to perform the root method by installing POOT apk ..
Download: Poot.apk (http://www.mediafire.com/download/vyn7mv413nnm3cv/poot-debug.apk)
Click to expand...
Click to collapse
To ROOT your MICROMAX is now became simple
1) Download and Install poot.apk
2) Now open the poot app then it will require you to install Ministro II, Simply follow the link to Google play store.
3) Then you will be required to update ministro library, please update it.
4) Once you updated the Ministro Library then you will be faced with two options;
1. “Press here to Poot”
2. “Built in root check”
5) Click on the first option which is “Press here to Poot” and after a while, You are going to face with three options.
1. Get Superuser
2. Get root-checker
3. In-built rootchecker
6) Press Get superuser and download superuser app.
7) And finally do a reboot to take effect
8) Congrats you have rooted your phone now
Click to expand...
Click to collapse
1.Thanks to Aziz Sayyed for his brief step by step instructions
2.Thanks to dev of poot & Ministro app
Tested on micromax qualcomm phones worked great..Hope it will work on other Qualcomm too..
Click to expand...
Click to collapse
TESTED DEVICES:
MICROMAX A54
MICROMAX A56
MICROMAX A57
MICROMAX A87
KARBON A21
Huawei U8860 Honor;
HUAWEI ASCEND Y.
SAMSUNG GALAXY MINI 2 S6500
SAMSUNG GALAXY CENTURA - SCH-S738C
SAMSUNG GALAXY DISCOVER - S730M
Samsung Galaxy S Duos S7562
Samsung Galaxy ACE 2X;
LG Optimus Sol E730;
Alcatel OT-908;
Gygabyte GSmart G1345;
Sony Ericsson WT19i Live with Walkman;
Sony Xperia Tipo (Single/Dual)
Sony Ericsson Xperia Ray;
HTC Desire Z;
ZTE V790
Ninetology Pearl Mini i5350
Kyocera Hydro C5170
.
Click to expand...
Click to collapse
hmm Looking Interesting...I was want to try but My phone is Bricked/Dead ; So hope someone Try & Post Result here
n00BXperia said:
hmm Looking Interesting...I was want to try but My phone is Bricked/Dead ; So hope someone Try & Post Result here
Click to expand...
Click to collapse
Good luck :good:
on which phones did you test it? will it work on A56?
karan128 said:
on which phones did you test it? will it work on A56?
Click to expand...
Click to collapse
Tested on a57..Worled great...And also 100% chance for working on a56...
Our Group Member "Rohit Sharma" Tested & Got Success in rooting his A87..Working Confirmed !
n00BXperia said:
Our Group Member "Rohit Sharma" Tested & Got Success in rooting his A87..Working Confirmed !
Click to expand...
Click to collapse
Thank you so much...I updated in tested devices.....
Re: [How To][Root Qualcomm phones without pc]
Will work on a89?
Sent from my A89 using xda premium
ashish33166 said:
Will work on a89?
Sent from my A89 using xda premium
Click to expand...
Click to collapse
No It wont...Because a89 is a mediatek device
Re: [How To][Root Qualcomm phones without pc]
I tried to root my Karbonn A9 with this method. It didnt work for me although my phone is Qualcomm based
Sent from my A9 using xda app-developers app
karan128 said:
I tried to root my Karbonn A9 with this method. It didnt work for me although my phone is Qualcomm based
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
What type of error u got....Between it is better to remove sdcard and try rooting..
Re: [How To][Root Most Qualcomm phones without pc]
dhinesh77 said:
What type of error u got....Between it is better to remove sdcard and try rooting..
Click to expand...
Click to collapse
sorry for the late reply. when i update the ministro library it shows error msg. i forgot what was that error.
Sent from my A9 using Tapatalk 2
karan128 said:
sorry for the late reply. when i update the ministro library it shows error msg. i forgot what was that error.
Sent from my A9 using Tapatalk 2
Click to expand...
Click to collapse
Sry for delay ..I will update you in two days
karan128 said:
sorry for the late reply. when i update the ministro library it shows error msg. i forgot what was that error.
Sent from my A9 using Tapatalk 2
Click to expand...
Click to collapse
Sorry for very late,
If download fails uninstall ministro and reinstall then redownload libraries....
After downloading libraries click press here to poot ..U r phone will stuck with blackscreen or it will reboot..
If it with blackscreen take out battery and restart then hurrily open poot and again press "Click here to poot" (If these option available)
Then you will see 3 options like "get superuser app" but not stable ..These options wil disappear soon...So as soon as you got 3 options download superuser app and enjoy
I tried this poot on galaxy mini 2 S6500D.
First time attempt to tap "press here to poot", my phone was blank and reboot immediately.
I check su file not pushed in /system/xbin.
Reboot my phone manually, and open poot again...
This time poot show debug text, instead of suddenly reboot my phone.
It say :
2012 giantpune
[+] opened device
[+] Set logging mode
[+] Resolved symbols
[+] Mapped 0x10000000
[+] Hooked 0xc02fcf6c
[-] Error running kernel-mode code
[-] Failed to clean up our mess
[-] Current && current != last + 1: 0000ffff 0000ffff
[-] Haxx has run its coarse. Reboot the device to play again
A demon materialized while pooting. Error code: 87
su binary was not written
You need to restart your device
Second attempt without reboot, produce error 22.
Did it had any chance to root my phone?
I know It was used for Cherry W100, but aleast it nearly identical to Mini 2. Thats why I test poot.
physcodelic said:
I tried this poot on galaxy mini 2 S6500D.
First time attempt to tap "press here to poot", my phone was blank and reboot immediately.
I check su file not pushed in /system/xbin.
Reboot my phone manually, and open poot again...
This time poot show debug text, instead of suddenly reboot my phone.
It say :
2012 giantpune
[+] opened device
[+] Set logging mode
[+] Resolved symbols
[+] Mapped 0x10000000
[+] Hooked 0xc02fcf6c
[-] Error running kernel-mode code
[-] Failed to clean up our mess
[-] Current && current != last + 1: 0000ffff 0000ffff
[-] Haxx has run its coarse. Reboot the device to play again
A demon materialized while pooting. Error code: 87
su binary was not written
You need to restart your device
Second attempt without reboot, produce error 22.
Did it had any chance to root my phone?
I know It was used for Cherry W100, but aleast it nearly identical to Mini 2. Thats why I test poot.
Click to expand...
Click to collapse
In your first attempt you ave rebooted manually right...After that you have pressed "press here to poot"
then ended with error code :87
................................................................................
And did you noticed the change in options ?? you will get three options namely 1.Get suer user 2. get root checker and 3. xxxx
though ended with error code...If you got three options means yours is rooted.....:good:
Then press get superuser to complete the process........
and final thing dont concentrate on message displayed..concenteate on options available in poot app......Because same error came in a57 but it was rooted
I successfully rooted my galaxy mini 2.
Using poot for h866c or huawei ascend y.
physcodelic said:
I successfully rooted my galaxy mini 2.
Using poot for h866c or huawei ascend y.
Click to expand...
Click to collapse
Its nice to hear ....Will you pls share the link of app u used ??
Btween thanks for informing your status..It will be helpful updating devices in worked devices list
Iam sorry for the late reply.
Iam sorry too if i cant post the link, iam on mobile now.
You can google giantpune thread, say "lg optimus elite poot androidforums"
There you can download all poot version.
physcodelic said:
Iam sorry for the late reply.
Iam sorry too if i cant post the link, iam on mobile now.
You can google giantpune thread, say "lg optimus elite poot androidforums"
There you can download all poot version.
Click to expand...
Click to collapse
No problem bro...I got the link of the that app..Thanks for that...
sm-a500fu, rooted, 4.4.4
My wife got a new sm-a500fu like our daugther has. To save work (after rooting) I restored the data and systems partitions (with Flashfire) of my daughters a5.
I deleted all my duaghters accounts and logged into google with my wifes account.
Still both phones have the same GSF and Androide ID.
I know that the Androide ID can be set like this:
Code:
adb shell ettings put secure android_id nnnn
- But which should I use ? Can I use the one of here old phone ?
- And what about the GSFid ?
Hoping for help now ...
What I found out so far:
android_id: *#*#8255#*#*
/data/data/com.android.providers.settings/databases/settings.db
its name in the database is android_id, value is HEX
gsf id: *#*#GCM#*#*
/data/data/com.google.android.gsf.gservices/databases/gservices.db
its name in the database is android_id too, value is decimal
Theese questions remain:
1 Is it necessary to change both or would GSFid be enough ?
2 If I change the IDs in the databases of the cloned phone to its original, what apps do I have to reinstall ?
3 Or is it cleaner to reinstall GSF and GAPPs ?
3a But would I get another ID this way ?
I realize this is an old thread which I found by searching for more information on changing the GSF-ID, where I'll just point people who may come here to a new method I found which changes the GSF_ID using basic Windows tools on a non-rooted Android phone without having to Factory Reset the darn thing (which is kind of nice indeed).
Seems tasker just won't turn on the hotspot on these. Anyone get it to work?
The error seems to state that the user does not have android.permissions.TETHER_PRIVILIGED so I went ahead and decompiled modified the manifest and then recompiled. I then used pm grant to grant the permission only to be met with "Operation not allowed: java.lang.SecurityException: Permission android.permission.TETHER_PRIVILEGED is not a changeable permission type".
Anyone find a way to resolve this? The dev says it's a sprint thing but tmobile users report it too.
Thanks
Dave
I am T-Mobile and no dice
I have latest updates and it fails for me too.
Wifi Tether enabled failed
Action Wifi Tether failed
result stop task (error)
Error 1
Action finished exeD 1 action no 0 code 113 status Err next 0
Used this all the time on my old phone sucks that this does not work now.
Anyone else? Seems to also do it on oreo w/ the S8+
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.