Related
hi guys just thought id let you all know that samsung has officially released jellybean 4.1.1 for the galaxy s3 in poland !!!
those of you that are patiently waiting for this update wait now more.
How to Update Galaxy S3 to Official XXDLIB Android 4.1 Firmware
[Important] If you flash this firmware over a custom ROM or a Galaxy S3 from another country than Poland, you might need to wipe the data on the phone to make the firmware boot up properly <<< (i did not wipe my data and it flashed perfectly
To be sure you do not lose any data, backup your Apps and important data — bookmarks, contacts, SMS, APNs (internet settings), etc. This Android backup guide would help you. The SD card contents are always safe, so there is no need to back up those. Only backup apps and personal data.
NOTE: Don’t forget to at least note down your network’s APN settings, which are required to make mobile data work. Go into Settings » More » Mobile Networks, click on the APN that is in use, then note down the setting for each field. While APN settings should be automatically restored from network, you can enter them manually if needed to make mobile data work. You can also find your APN details → here.
Download and install the software Kies on your computer, which will install the necessary drivers for the phone.
Download Kies
You can also download the drivers directly — download from here: 32 bit (x86) Windows | 64-bit (x64) Windows
Download the firmware.
Download XXDLIB | Alternate Link | Filename: GT-I9300_XEO_1_20120922093900_w8pdod73hi.zip
Extract the GT-I9300_XEO_1_20120922093900_w8pdod73hi.zip file on the computer to obtain a file named I9300XXDLIB_I9300OXFDLI1_I9300XXDLIB_HOME.tar.md5 (ignore the file named SS_DL.dll).
Download the Odin PC software. If you are new to this, Odin is what is used to flash stuff – firmware, kernels, etc. – on Samsung phones. We’ll use Odin to flash the firmware file obtained in step 4.
Download Odin3 v3.04 | Filename: Odin3_v3.04.zip
Extract the contents of the Odin3_v3.04.zip file to a folder on your computer.
Now, turn off your Galaxy S3 and wait for it to shut down completely.
Then, put the phone into download mode. To do so, press and hold these keys together: Volume Down + Home + Power till the screen turns on. Then press Volume Up to enter download mode.
Open Odin by double-clicking on the Odin3 v3.04.exe file obtained in step 6 after extracting Odin3_v3.04.zip.
Important! Connect your phone to PC now. You should get the message “Added !!” under Odin’s message box in the bottom left.
If you don’t get this message, make sure you installed drivers correctly (using Kies or directly) as given in step 2. If it still doesn’t work, try changing to another USB port on the computer and also use the USB ports on the back if you have a desktop PC.
Click on the PDA button in Odin, then browse to and select the I9300XXDLIB_I9300OXFDLI1_I9300XXDLIB_HOME.tar.md5 file obtained in step 4 above.
Important! Do not make any other changes in Odin !!!. Leave all other options as they are. Make sure Re-Partition check box is not selected.
Now, click the Start button to start flashing the firmware on your phone. When the flashing is complete and is successful, you’ll get a PASS message (with green background) in the left-most box at the very top of the Odin, and the phone will automatically reboot. When you see the Samsung logo, you can safely unplug the cable.
IF you have any questions or you get stuck let me know
Sigh...
Sent from my GT-I9300 using xda premium
Omg really!!!!! Wow thanks!!! What's your PayPal I want to send a donation for this amazing find...
Sent from my GT-I9300 using xda premium
Jeez wrong forum old news wrong information .
Over excited 11 poster i guess.
Reported .
RULES
Only the following topics are allowed in the DEVELOPMENT area:
[DEV] - Development for any projects or Apps.
[ROM] - Custom ROMs.
[KERNEL] - Custom Kernels.
[MOD] - Hack & Modifications for the phone. (See below for more details)
[FIX] - Fixes for known issues & bugs.
[R&D] - Research & Development for Devs only, when gathering data for a new projects.
Note: If you are unsure where your new topic should go, then please post it in General.
jje
Moved to general and closed
1) repost
2) development section is not the right place for this sort of thing.
Only fresh flashed bootloader locked XT1058 AT&T - ROM LPAS23.12-21.7-1, and XT1060 VZW - ROM LPAS23.12-39.7-1 are supported!
See archive content for instructions. Time to install ~20 min. If you experience problems after Android boot, like not working buttons or quick settings, wipe cache + data partitions. Don't update SuperSU (disable auto updates), it won't work. Later I'll post complete debloated ROMs with fresh SuperSU version, and simplify instructions. Be informed also, that this method doesn't give you read-write rights like unlocked bootloader. You may read and write having root-rights, but only till a restart or shutdown occurs, and every change will be undo by the Qualcomm protection (like HTC' s=on).
At the moment patch includes:
SuperSU 2.65 Free
Xposed Framework v86 (installer, modules)
Busybox 1.25.0.YDS, path /system/xbin/busybox
Download
P.S. Install only on indicated above ROM versions, and it's obvious that you must have enough theory knowledge and practical experience to make use of 9008 patch, so I'm not responsible for any consequences, etc. Greets go to: CrashXXL (method inventor), Sabissimo (our former OP), and serg_gangubas (ROM guru).
==============================================================================================
31.07.2017 - Full ROM Patch for Bootloader Locked Moto X ATT/VZW/etc
Based on the same principle, and not depend on system partition content, so it suits any bootloader locked Moto X Gen1 ATT/VZW (possibly any model, besides 1049 RepW / 1055 US Cell), but takes about 4 hours to be done - prepare for that, 100% battery level only!
This full ROM patch includes:
SuperSU 2.82 Free
Xposed Framework v87 (installer, modules)
Busybox 1.26.2, path /system/xbin/busybox
ViperFX 2.5.0.5 - sorry needs polishing, removed now (
Gallery and Camera not depend on Moto services
Gboard instead AOSP Keyboard. If it eats too much RAM, see Simple Keyboard
GAPPSes updated. Use command like adb shell pm uninstall --user 0 com.blahblah.blah to block any unwanted app or service
ES File Explorer Free Edition (a clone, you can disable and install yours )
"Jedy" gesture
AdBlock support (effect lasts till the 1st reboot yet, I'll think about make it constant). Please, choose /data/hosts instead of /system/etc/hosts
ROM debloated, but not deodexed.
Download
Instruction
Be careful, phone will be WIPED then flashed in 9008 "brick" mode (CrashXXL idea). Before you start install Moto drivers, latest RSD Lite, and fully charge the battery.
1) Download and unpack zip on С: (or any), open Python27, launch RUN_path.bat (needs to be launched only single time), install driver QHSUSB_driver.exe, and launch file _Moto.X.BootLocked.*.exe (where * - is desired ROM).
2) Go into fastboot mode, execute RUN_blbroke.bat. Screen gets black, Device Manager in Windows finds "QHSUSB_DLOAD", and installs it as "Qualcomm HS-USB QDLoader 9008 (COM*)". If it doesn't install, google for Windows driver digital signature disable.
3) Now launch RUN_root.bat, and see that patching process took start.
4) A small patch *SPEAKERS.BOOST.exe (if exists) boosts both speakers' volume.
P.S. Please, don't flash anything extra into the phone. In case of trouble, all you need is inside this folder. Just make it work.
To make "Battery OK" in fastboot use fastboot_cyclecharge.bat
Completely drained out battery causing "USB input device" needs disassembly of the phone to charge externally.
In case Titanium Backup shows error "Batch backup interrupted: insufficient free storage space", delete default backup folder, and make a new:
Titanium Backup > Menu > Preferences > Backup folder location > Storage Provider > DocumentProvider storage > Show Internal Storage > Internal Storage > Select Internal Storage > Create the folder > Use the current folder. Done!
Notes for myself: Viper, force wipe, readme.txt, volume patch, Adblock, advanced debloat
Debloated, rooted, lightweight ROM - soon! )
PUBLISHED. Sorry, took long time.
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
This method is working on locked BL.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
Wait wait... If you can have now possibility to unlock bootloader - go for it immediately! You will have normal FULL root-rights (SuperSU 2.49). Don't install 5.1, if you plan to unlock, because Sunshine app (25$) works only on 4.4.2 Android.
This topic is to help those AT&T users that are boot locked forever (who missed out possibility to unlock on 4.4.2 by proceed to 5.1) to give them READ-ONLY root. Yes, it's limited, but anything at least.
s5610 said:
If you can have now possibility to unlock bootloader...
Click to expand...
Click to collapse
I guess anyone on 4.4.4 today. There is no possibility to use Sunshine anymore.
Anyway spasibo za method
Ahh, if I don't have to be BL unlocked that's great lol.
I haven't read too much into the 5.1 updates or sunshine for that matter.
I've been on krypton 1.4.1 since it was released, and I haven't been able to successfully upgrade to any 5.1 roms yet.
Works great!
Works great for me on Windows 10 RTM 64-bit! Thanks a ton, I was waiting for a post like this.
I only had 3 minor hiccups:
1. RSD Lite gave me an error about "getvar", so I had to go into flashfile.xml in the ROM zip and remove the line that said getvar
2. I had to reboot to disable driver signature enforcement twice for some reason because Windows Update
3. The run-root.bat got stuck on "Executing..." because I installed the wrong driver (the correct file is qcusb.inf when installed from device manager -> browse my computer for driver software -> let me pick from a list -> all devices -> have disk)
Otherwise, everything runs just as well as KitKat, including Xposed.
Hehe got to love step 9
System Write
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
Click to expand...
Click to collapse
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Need some help, I did all steps until step 9. I installed the QHSUSB_DLOAD driver manually, and I can see 'Qualcomm HS-USB QDLoader 9008 (COM4)' showed in my Device Manager, but when I run 'RUN_Root.bat', I got this
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Sending MAGIC ...
QCOM fast download protocol targ:
Version: 7
Compatible version 2
Maximum block size 1024 (0x00000400)
Base address of Flash 0x00000000
Flash: eMMC
Window size: 30
Number of sectors: 128
First sector size: 2097152 (0x00200000)
Feature bits: 09
Sending SBL Reset...
Done
c:\Python27>pause
Press any key to continue . . .
Then I tried to run 'RUN_Root.bat' again, then I got
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device progr
amming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91,ca,fd,bb,94,2a,0d
,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960.bin' to addr 0x2a000000...
Executing...
Could not find Qualcomm device in Emergency download mode
Done, with errors!!!
c:\Python27>pause
Press any key to continue . . .
any suggestions? Thanks
jahrule said:
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Click to expand...
Click to collapse
Ill put the files here
Fantastic!!! I was looking this. All the last week I was sleeping about 3 hours per day trying to root my phone.
----
I scream "Victory" before the process finish.
Damn! My phone reboot and stay in the android doll fallen screen.
DejanPet said:
Ill put the files here
Click to expand...
Click to collapse
What to do with these files?
Those files are needed by Jahrule
Sabissimo
Hello.
I did everything as instructed, but eventually got the screen "no command".
The only thing I did not flash rom - a month ago updated by an OTA to 5.1, thought it was not necessary.
Factory reset does not help.
Advise something.
In the end, everything worked, thank you))
It works
It works great! Thank you very much! ATT xt1058.
eze_cba17 said:
Damn! My phone reboot and stay in the android doll fallen screen.
Click to expand...
Click to collapse
Follow the OP instruction EXACTLY, no exceptions!
If you got your current 5.1 through AT&T OTA, it's not enough for root patching procedure. A full RSD 5.1 official SBF flash over is required.
Could someone please do a video on this. I'm having a little trouble.
ONEPLUS 3 - SUPPORTS ALL VERSIONS UP TO THE LATEST OXYGEN OS BUILD.
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Google, Nexus, OnePlus and Samsung Toolkits and supports many devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
* Root any public build automatically
* SkipRoot boot image to AutoRoot (selected builds)
* Sideload root/unroot files via Custom Recovery
* ALLINONE to Unlock, Flash Recovery, Root, Rename the restore file + install Busybox (G,N,O)
* ALLINONE to Flash Recovery, Root, Rename the recovery restore files + install Busybox (Samsung)
* Unlock/Re-Lock your Bootloader (G,N,O)
* Download Google Stock Image files directly to the ToolKit (G,N,O)
* Check md5 of google stock image before flashing
* Flash Google Stock Image (G,N,O)
* Flash any part of a stock firmware image to device [boot, system, recovery, etc.] (G,N,O)
* Download/sideload stock OTA image (G,N,O)
* Install BusyBox binarys on device
* Rename the Recovery Restore File present on Stock Roms (if stock recovery is being restored after flashing custom recovery image)
* Flash Stock Recovery, CWM touch, Philz_touch or TWRP Touch Recovery
* Pull /data and /system folders, compress to a .tar file and save to your PC
* Auto Update Toolkit at startup (PRO ONLY)
* Auto Update superuser file and custom recovery images to latest versions (PRO ONLY)
* Disable forced encryption on Nexus5X,6,6P and 9
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps
* Install EFS/Partition Backup/Restore app by Wanam
* Create tar with 1-Click for flashing via Odin
* Fix extSdCard write permissions in Android 4.4+
* Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC (selected builds)
* Useful Mods, Fixes and Tools Section
* Extras, Tips and Tricks section (includes guides)
* Backup/Restore your /efs partition (gsm only)
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC ( on builds with insecure image available)
* Mods section to automatically perform certain tasks on your device
* Boot to any recovery without Flashing it (G,N,O)
* Boot or Flash .img Files directly from your PC
* Quick Picks Professional Feature (10 slots)
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your phone
* Pull Files from your phone to your PC
* Set Files Permissions on your device
* Pull and Trim your Radio Image (gsm models only) to your PC
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Rip cache.img to zip file in CWM format
* Reboot device to Fastboot Mode or Android in fastboot mode (G,N,O)
* Reboot device to Fastboot Mode, Recovery, Android or Download Mode in adb mode
* Turn Initial Start Screen On/Off for next use
* Sideload any zip file via Custom Recovery
* Basic Toolkit for use with ANY Android device
Key: G-Google N-Nexus O-OnePlus S-Samsung
--------------------------------------------------------------
{
"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"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: Grarak or TWRP custom recovery on OnePlus 3, ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Up' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.
**FAQ**
**VIDEOS**
I have finished all the work on the OnePlus modules for the 1, 2 and 3 devices and it is ready for testing.
You can download and test the Toolkit from the link in post#1. Please remember that this IS a test version at the moment as I do not own any OnePlus devices but I have checked all the code thoroughly and don't see any problems. I am especially pleased with the unlock/lock routines and will probably implement the code for the Nexus modules if it works well.
Everything can be checked (and please do) except downloading a stock build directly from the Toolkit as I am waiting to hear back from AndroidFileHost to see if I can get direct links to use in the Toolkit. The fastboot flash routines are working though and the Toolkit will detect the storage of the device (16GB or 64GB) and flash the relevant userdata image so you do not have to do that manually anymore.
I have used the Universal USB driver pack from CWM so if anyone has not installed OnePlus drivers yet PLEASE test if this works. I did originally include the official drivers from OnePlus but they close the Toolkit when the drivers installation starts and thats not great.
The ALLINONE routine should work fine and I have sent out some pro codes to testers to check it all works.
All builds are covered and the correct version of TWRP will be downloaded depending on the build selected. Please check everything and let me know of any bugs or textual errors (as I used a lot of the Nexus code) so I can release it publicly as soon as possible.
Thanks, Mark.
Great job, thanks a lot!!!
Dude, did a scan of your file and found this: Result: Detected: Trojan-Ransom.Win32.Cryrar.gib care to explain?
Trojan?
I hope not - seems legit.
I have 2 problems:
1)
It never asks me to authenticate the PC on the phone after installing drivers - tried both driver versions.
But the Phone serial shows up in the menu, the driver test is fine and I can backup .apks.
2)
I can not flash the OTA
Is it because it is a full stock image instead of an OTA?
gruntyoldbag said:
Trojan?
I hope not - seems legit.
I have 2 problems:
1)
It never asks me to authenticate the PC on the phone after installing drivers - tried both driver versions.
But the Phone serial shows up in the menu, the driver test is fine and I can backup .apks.
2)
I can not flash the OTA
Is it because it is a full stock image instead of an OTA?
Click to expand...
Click to collapse
Just saying, got that hit when I scanned the installer file. Might be wrong but I will not run it until dev explain why
TheErk said:
Dude, did a scan of your file and found this: Result: Detected: Trojan-Ransom.Win32.Cryrar.gib care to explain?
Click to expand...
Click to collapse
Did you read the first post of the thread?
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Click to expand...
Click to collapse
The Toolkit has been running over 4 years and there have never been any viruses in it.
Mark.
I ran this on my Nexus days, the guy is well known around, you can go with this.
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
gruntyoldbag said:
Trojan?
I hope not - seems legit.
I have 2 problems:
1)
It never asks me to authenticate the PC on the phone after installing drivers - tried both driver versions.
But the Phone serial shows up in the menu, the driver test is fine and I can backup .apks.
2)
I can not flash the OTA
Is it because it is a full stock image instead of an OTA?
Click to expand...
Click to collapse
I found the problem right away, just deleted 1 word by accident when I was renaming things.
I have made new device modules and uploaded them. Delete the ConfigOnePlus3.exe file from the Tools folder (or run ToolkitClean and select the OnePlusThree), then rerun the Toolkit and select your device to download new modules. Should work then.
Mark.
mskip said:
Did you read the first post of the thread?
The Toolkit has been running over 4 years and there have never been any viruses in it.
Mark.
Click to expand...
Click to collapse
Thought I did! Thanks for the fast reply!
---------- Post added at 11:23 AM ---------- Previous post was at 11:11 AM ----------
Impressive tool you got here! Thanks!
mskip said:
Delete the ConfigOnePlus3.exe file from the Tools folder (or run ToolkitClean and select the OnePlusThree), then rerun the Toolkit and select your device to download new modules. Should work then.
Click to expand...
Click to collapse
I cleaned the toolkit and
**************
Also I had to restart the toolkit (my own error - I didnt use the toolkit to restart, but restarted manually) and I got:
************
Tried again and Windows installed more device drivers when accepting sideload from ADB.
Didnt work the 2nd time either.
**********
BTW: drivers are installed correctly
******
Btw: I really love your tool - nice, clean, fast and a lot of HELP in the menus
gruntyoldbag said:
I cleaned the toolkit and
**************
Also I had to restart the toolkit (my own error - I didnt use the toolkit to restart, but restarted manually) and I got:
************
Tried again and Windows installed more device drivers when accepting sideload from ADB.
Didnt work the 2nd time either.
**********
BTW: drivers are installed correctly
******
Btw: I really love your tool - nice, clean, fast and a lot of HELP in the menus
Click to expand...
Click to collapse
Thanks and thank you for staying with me, I have had to change some of the procedures for the OnePlus.
Should be all fixed now. One of the procedures I had to skip set the filename for the OTA image. Have added it back in.
Clean the module files, download the new ones and retest. Hopefully it should go through.
Mark.
It is sideloading now
Reboot was successful - thx
Btw: If you want the help text to be 100% correct:
When you reboot you have to chose ENGLISH (or you can chose chinese or madarin?)
And it is called 'Install from ADB' not from USB.
Then click OK to 'Do you want to update' (not 100% sure about this text - can not remember now.
************
Just tried option 11 from the main menu:
****
Booting to stock recovery gives me the same error.
gruntyoldbag said:
It is sideloading now
Reboot was successful - thx
Btw: If you want the help text to be 100% correct:
When you reboot you have to chose ENGLISH (or chinese or whatever)
And it is called 'Install from ADB' not from USB.
Then click OK to 'Do you want to update' (not 100% sure about this text - can not remember now.
Click to expand...
Click to collapse
Thank you. I have uploaded the fixes to all the OnePlus device modules so that part at least should work for them all now.
Does the language selection come up as soon as the device boots to recovery?
I put Install from USB as thats what it said in the flashing tutorial on oneplus.net I will change it to Install from ADB/USB just to be safe for all devices.
Thanks again for the feedback. If you want to test any of the pro functions (ALLINONE) then let me know and I will send an activation code to your inbox.
Mark.
gruntyoldbag said:
It is sideloading now
Just tried option 11 from the main menu:
****
Booting to stock recovery gives me the same error.
Click to expand...
Click to collapse
Have you unlocked your bootloader? This is required before flashing/bootings images to your device.
I can capture the error when trying to boot/flash with a locked bootloader to provide more help for the user.
Mark.
The language selection come up as soon as the device boots to recovery - yes.
No I didn't unlock the bootloader - I didn't think it was necessary - help text said something about unlocking - but not that it was required.
I just wanted to backup the device - not flash anything.
Yes let me try (ALLINONE) - send me a PM thx.
gruntyoldbag said:
The language selection come up as soon as the device boots to recovery - yes.
No I didn't unlock the bootloader - I didn't think it was necessary - help text said something about unlocking - but not that it was required.
I just wanted to backup the device - not flash anything.
Yes let me try (ALLINONE) - send me a PM thx.
Click to expand...
Click to collapse
I have changed the text when booting to recovery and added extra error control when flashing or booting an image without the bootloader unlocked. New device modules uploaded.
Now sending a pm to you with a code.
Mark.
PM received - PM sent
New text and error control seems to work :good:
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.
[GUIDE/TUTORIAL/HOWTO] Huawei Honor 5X from Stock to Android 10
[GUIDE/TUTORIAL/HOWTO] Huawei Honor 5X (kiwi) from Stock to Android 10 / LineageOS 17.1 in 2023
Complete guide to install Android 10 on your Huawei Honor 5X.
This tutorial only applies to this model, to check the correct version:
in Android, go to Settings > About phone > Model number, make sure it is one of these models:
- KIW-L24
- KIW-L22
- KIW-L21 (Qualcomm Snapdragon)
Not 100% sure for following models:
- KIW-L23
- KIW-AL10
- KIW-AL20
- KIW-CL00
- KIW-UL00
- KIW-TL00
- KIW-TL00H
- KII-L05
- KII-L22
- KII-L21
I wrote tis tutorial with KIW-L21.
See all my tutorials at https://github.com/djibe/Android-tutorials
Netflix and Disney+ are working.
CHANGELOG
v1. Initial release
1) WHAT YOU NEED
- djibe Honor 5X pack: https://bit.ly/honor5xdjibepack or https://anonfiles.com/EfHbPev2z2/djibe_Honor_5X_pack_zip or
(Contains TWRP Recovery 3.4.0-0 + Magisk root + Huawei USB drivers x32/64 + fastboot + cited files for root)
+ ROM LineageOS Unofficial 17.1: https://forum.xda-developers.com/t/rom-10-0-lineageos-17-1-unofficial-for-honor-5x.4212671/
Download latest build here: https://mega.nz/file/tbUliQ7Q#7f7Byu1QuuYNkojPnu5MDevPyCx6oMxXxQsjgjciCsE
+ BitGApps ARM64 10: https://github.com/BiTGApps/BiTGApps-Release/releases
+/- extra apps: https://bitgapps.github.io/addon/ARM64.html
+ a microSD card formatted in FAT32: copy ROM, GApps (+ Magisk). Insert it in phone
+ Charge phone to 100%
2) INSTALL DRIVERS
Install Huawei USB drivers.
Then plug phone to PC and let the install go on.
3) BACKUP YOUR DATA
When your phone is connected to Windows, search for all .jpg, .mp3, .mp4 files on your phone and make copies on your PC.
Then, with your Google Account (Whatsapp and co) or an app like Backupyourmobile, backup all your SMS, MMS, contacts.
Make sure the backup is located on microSD card.
4) UNLOCK BOOTLOADER
Update your Honor 5X to the latest official Android 6 Marshmallow (MM).
In Android, go to Settings > Updater. Make sure you have latest version.
Go to Settings > About phone.
Tap 7 times on Build number to unlock Developer options.
Go to Settings > Developer options.
Switch ON "Enable OEM unlock" and "USB debugging".
You must pay to unlock bootloader as Huawei closed the official website.
List of services offering unlock codes for money:
- DC Unlocker ($4 + VAT): https://www.dc-unlocker.com/supported_models_1/huawei_phones
- MinistryOfSolutions ($4): https://ministryofsolutions.com/huawei-bootloader-unlock-paid-service-html
Follow steps to get a paid unlock code. Here are the steps for DC Unlocker.
Go to DC Unlocker website: https://www.dc-unlocker.com/supported_models_1/huawei_phones
Download latest Client for Windows and install it.
On phone, launch Dial pad and type: *#*#2846579#*#*
ProjectMenu opens.
Go to Background Settings > USB Port Settings > select Manufacture Mode and Close.
### If you restart phone before the end of the process, you have to do this again.
Connect Honor 5X to PC.
Go to Windows Device Manager.
In the Modems section, Android Adapter Modem is listed.
In the Ports section, Android Adapter PCUI (COMn) is listed.
### If not, you must check USB drivers installation again.
Launch DC Unlocker.
- Select manufacturer: Huawei phones
- Select model: Auto detect (or Huawei Qualcomm Android phone)
Click magnyfying glass button.
DC Unlocker returns:
Code:
Found Applications port COM3
Found Diagnostics port COM5
Found Phone : HUAWEIKIW-L21
Model : Huawei Qualcomm Android phone
IMEI : xxx
Serial NR. : xxx
Firmware : xxx
Hardware ver. : HL3KIWMAD
Now go to DC Unlocker shop: https://www.dc-unlocker.com/buy
You need 4 credits ($4) for operation 24: Huawei Qualcomm Read Bootloader Code (up to Android 8)
Set subscription as:
Item: New user account
User name: YOUR CHOICE
Credits: 4
I used Credit card.
Note down purchase informations, we will need these in DC Unlocker.
Back to DC Unlocker.
Go to Server panel.
Fill User name and Password with data from your receipt.
Click Check login.
Go to Unlocking section and click Read bootloader code button.
DC Unlocker returns:
Code:
Reading bootloader code...
Bootloader code : xxx
Note down Bootloader code carefuly.
On phone, launch Dial pad again and type: *#*#2846579#*#*
ProjectMenu opens.
Go to Background Settings > USB Port Settings > select Google Mode and Close.
Go to my djibe/flash folder.
In the address bar, type cmd and confirm with keyboard Enter key.
Enter command:
Code:
adb devices
Authorize USB debugging from phone.
Enter command again (use arrow up key to print last command):
Code:
adb devices
Command returns
Code:
List of devices attached
W6HDU16325009900 device
Then:
Code:
adb reboot bootloader
Phone switches to white screen in FASTBOOT&RESCUE MODE.
To check that fastboot USB drivers are OK, type:
Code:
fastboot devices
### If command doesn't print a line like: 516b3414 fastboot, you have to fix USB drivers.
Now enter THE command:
Code:
fastboot oem unlock FILL_WITH_YOUR_UNLOCK_CODE
Confirm with enter and wait a moment ... till success is confirmed :
"(bootloader) Unlock success , the device will reboot and factory reset
OKAY [ 0.046s]
Finished. Total time: 0.046s".
Keep Windows command opened and let phone reset Android.
4) FLASH RECOVERY
Configure Android rapidly.
Unplug phone and replug USB.
Go to Settings > About phone.
Tap 7 times on Build number to unlock Developer options.
Go to Settings > Developer options.
Switch ON "Enable OEM unlock" and "USB debugging".
Back to Windows command, type:
Code:
adb reboot bootloader
Twice to authorize USB debugging from phone again.
Now that you are back to bootloader, enter:
Code:
fastboot flash recovery twrp-3.4.0-0-kiwi.img
Confirm with Enter.
Terminal confirms : "Finished. Total time: 2.711s".
And now:
Code:
fastboot boot twrp-3.4.0-0-kiwi.img
### If phone goes in a bootloop, disconnect phone and force shutdown holding Power button.
Welcome to TWRP 3.4 recovery.
TWRP asks for Keep System Read Only ? Swipe to Allow Modifications.
### You don't see this warning screen? Then you'll get "TWRP unable to mount storage" while trying to wipe partitions.
### > in TWRP, go to Reboot > Recovery so Recovery will refresh and popup the partition writing privilege.
In TWRP home screen, go to Wipe > Format data.
This will remove encryption.
Type yes and confirm to format partition.
Go to Reboot > Recovery.
Back to TWRP, go straight to Backup menu.
Select Boot, Data, System, Custom, OEMinfo, EFS and Firmware partitions.
Tap on Select Storage and set Micro SD card.
Swipe to Backup and wait during backup.
### If MicroSD card is too small. Backup on data partition and after backup has ended, go to Mount and connect phone to PC to retrieve TWRP backup folder.
### Store this backup (aka nandroid backup) somewhere safe before going further.
5) WIPE PARTITIONS
Go to Wipe > Advanced Wipe and check Cache, Data, Internal Storage, System and Swipe to Wipe.
6) FLASH ROM, BITGAPPS +/- MAGISK
Back to TWRP Home menu. Then tap on Install > select Storage MicroSD > choose lineage*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active).
then Add more Zips > BiTGApps*.zip,
Optional: Add Magisk*.zip
then Swipe to confirm Flash.
Wait for operation to end.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System.
Android 10 is installed !
Wait for the phone to boot during 10 minutes.
7) ROOT WITH MAGISK (OPTIONAL)
### Only if you flashed Magisk via TWRP recovery
Do not connect to Android account.
Magisk root starts with Android.
You can manage permissions and extra modules with Magisk Manager app.
Open Files app > Install Magisk.apk.
Then in Magisk goto Settings > Hide magisk app and give it a name, switch Zygisk option ON.
Go to Modules Tab > Install from Storage: MagiskHidePropsConfig and safetynet.
Go to Developer options to disable Android debugging (ADB).
Reboot phone.
You can use yasnac app to check Safetynet passes.
Then with Files App: install netflix and disney+ if needed.
10) OTHER APPS
- You can use GPS Status & Toolbox for faster GPS fix.
- Developer options
Settings > About phone.
Tap 7 times on build number.
Back to Settings > System > Advanced > Developer options
Select USB Configuration > set MTP
Set Windows animation scale, Transition animation scale and Animator duration scale to .5x
That's it.
Enjoy ;-)
djibe
Thanks: @BadDaemon, LineageOS team, TWRP team, BitGapps team, TopJohnWu (Magisk)
Thanks for this updated tutorial. I might be like a lot of others who only recently purchased this smartphone. I think they cost a little more now then the $34.95 I paid a month ago.
Huawei Honor 5X 4G LTE Android 5.5" Dual-SIM 16GB Unlocked Smartphone 886598039147 | eBay
Find many great new & used options and get the best deals for Huawei Honor 5X 4G LTE Android 5.5" Dual-SIM 16GB Unlocked Smartphone at the best online prices at eBay! Free shipping for many products!
www.ebay.com
I originally purchased to I could try the freemobile SIM, but unfortunately it requires VOLTE. I also tried T-Mobile data only SIMS with it, but they seem to be shut down as I am still using the stock image.
I opted to use Ministry of Solutions as it was only $4 and DC seems to require the user to go through a process and Ministry of Solutions pretty much does all the work. The process just required me to do the following:
Go to their website and pay $4 via paypal for the service,
Contact them to let them know you paid for the service and schedule a time to get it done. I just used email.
Install teamviewer and provide the access information for them to access your system remotely.
Be available to configure the phone so they can do their work.
Wait for them to get done with the process and provide the unlock code for you.
The unlock code will also be included on paypal upon completion of their work.
So far I have only unlocked the bootlader and installed TWRP and will finish the process when I have time. I am just happy to have noticed that this tutorial is up to date and has links to all the resources needed to do the upgrade.
Hi @comm-ents, thanks for sharing.
I would not let anyone come on my computer but it is nice to have this alternative.
This phone is still damn cool, even though Honor closed their unlock site.
djibe89 said:
Hi @comm-ents, thanks for sharing.
I would not let anyone come on my computer but it is nice to have this alternative.
This phone is still damn cool, even though Honor closed their unlock site.
Click to expand...
Click to collapse
I wasn't too concerned as I currently use Linux Mint for work and Windows mostly for playing games so there isn't much there to compromise. I will be using them again if needed as they only did what was needed to get the code. I am pretty sure that a copy of Windows installed in Virtualbox would also work for increased security.
Just be aware that most compromised information isn't done while you're watching but behind the scenes so you're always taking a risk when connected to a remote site.
I suppose not having to pay $4 to get the unlock code would be nice, but it is just $4 to get even more benefits out of a very inexpensive dual SIM phone. Maybe if I am lucky it will be even more useful once I replace the Stock ROM with something a bit more up to date.
I am not able to install the lineage rom as I just get an error.
updater process ended with error 7 with my KIW-L24. I also tried to remove the assert lines as some instructions suggest should be done and it looks like the install went ok, but It ends up in a boot loop.
After trying the process twice just in case I made a mistake, I found that but removing the assert lines from the file, the install seems to complete, but I am no longer able to use TWRP from the phone as the touch screen doesn't work any more and Lineage doesn't boot either.
The only reason I can think of that the install doesn't work is because there is something that is different about the phone I have like it is a newer revision. It seems that the partition sizes might be different and when I remove the assert lines the install just writes to a partition that is too small to hold the data and it ends up overwriting itself so it is basically corrupted in the process. Just a theory, but I haven't had any luck with anything but the stock firmware.
comm-ents said:
I am not able to install the lineage rom as I just get an error.
updater process ended with error 7 with my KIW-L24. I also tried to remove the assert lines as some instructions suggest should be done and it looks like the install went ok, but It ends up in a boot loop.
After trying the process twice just in case I made a mistake, I found that but removing the assert lines from the file, the install seems to complete, but I am no longer able to use TWRP from the phone as the touch screen doesn't work any more and Lineage doesn't boot either.
The only reason I can think of that the install doesn't work is because there is something that is different about the phone I have like it is a newer revision. It seems that the partition sizes might be different and when I remove the assert lines the install just writes to a partition that is too small to hold the data and it ends up overwriting itself so it is basically corrupted in the process. Just a theory, but I haven't had any luck with anything but the stock firmware.
Click to expand...
Click to collapse
Sure of your model ?
Info about kiwi | LineageOS Wiki
wiki.lineageos.org
djibe89 said:
Sure of your model ?
Info about kiwi | LineageOS Wiki
wiki.lineageos.org
Click to expand...
Click to collapse
Yep. Model number KIW-L24.
comm-ents said:
Yep. Model number KIW-L24.
Click to expand...
Click to collapse
Format Data
Wipe all partitions
Reboot recovery
Flash
Leads to Error 7 ?
djibe89 said:
Format Data
Wipe all partitions
Reboot recovery
Flash
Leads to Error 7
Click to expand...
Click to collapse
Yes.
The first issue is that when I try to format Data I get: Unable to wipe '/data' -- unknown file system 'auto' Unable to format to remove encryption. I found a suggestion to format the /data partition manually from adb shell which works.
The Lineage from wasn't the only Install I the error 7 with though as ResurrectionRemix-M-v5.7.4-20161220-kiwi also gave the same error 7.
Now the touch screen isn't working again in TWRP because I accidentally installed the wrong version of Lineage. with the assert lines removed. It would be nice to know how I can do a restore from the command line, but the TWRP command line guide isn't much help. It is just too much of a PITA that once I can get stock back on it I will just sell it while I'm ahead.
Sometimes you have to manually reformat.
Go to Wipe > Advanced wipe > Cache > Change partition
Too bad you didn't succeed
I was able to unlock the boot loader and still have a rooted phone. What I had hoped to do is use it with a T-Mobile data only plan and a SIM from FreeMobile provides a few hundred minutes a month for free.
I don't know why I get the Error 7, but you can't just remove the assert lines as the install might seem to have worked, but that is only because it just proceeds to install even though there might be something wrong and the install just messes up the phone.
I am still using the phone right now to test as a hotspot. The real reason that SIM didn't work in the phone is because of something on T-Mobiles end so it actually works in the phone now and since it is rooted I can make other changes that actually allow it to work as hotspot without limitations.
I should be able to find another dual SIM phone that can be rooted, but I am not sure there is anything that also supports Volte.
Is there otherway to unlock bootloader without paying 4 dollar. My country has restriction. i cant pay.
neysariy said:
Is there otherway to unlock bootloader without paying 4 dollar. My country has restriction. i cant pay.
Click to expand...
Click to collapse
No way.
Or tell us if a miracle happened
In djibe Honor 5X pack, you said it contains Huawei USB drivers x32/64 but i didnt found it. Only driver that worked is:
Support area | files.dc-unlocker.com
files.dc-unlocker.com
Please add to your pack if you forgot that
In my phone there is not "unlock oem" option. What shoud i do. It that important?
Dc unlocker say error conection to server. I dont know why.
I'll dig into it. Thx
This guy in telegram can unlock bootloader of huawei phones very fast @fullkade_huawei_support
.
neysariy said:
In djibe Honor 5X pack, you said it contains Huawei USB drivers x32/64 but i didnt found it. Only driver that worked is:
Support area | files.dc-unlocker.com
files.dc-unlocker.com
Please add to your pack if you forgot that
Click to expand...
Click to collapse
Pack updated with USB drivers. Sorry for that