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.
The purpose of this thread is to have all information regarding the Weloop Tommy, gathered, fresh and to the point.
(i am not affiliated with Weloop)
Please read both post number 1, 2 and search thread before asking questions thank you.
FAQ
Q:What is the latest firmware?
[Release] black watch v3.19 firmware update notifications [Copy link]
This update to the firmware update, the client does not update the current firmware version v3.18 firmware watches friends can try to use the old client detects the firmware update.
Update:
Solve watches restart, restore factory settings watches language will change.
Download Link:
iOS client 2.079: http://fir.im/iosobt
Android client 1.29.3702b: http://fir.im/andobt
Unofficial file archive of WeLoop Tommy. APK-Files with ending "b" are BETA http://www.wtf.li/
Q: When is the next app update
A: Weloop v. 3.0 will be released as closed beta 7the of March 2015 we don't know when there will be an open english release....
the extensive update 3.0 have,
better health monitoring
profiles
sleep monitoring
more alarms weekdays/weekend
and more.
(see attached pictures for app version 3.0 UI improvements
Q: What does the settings do?
- Backlight
24H: Backligth always turns on when button is pressed
Nite: Backligth turns on when button is pressed at night time (from 17–8)
Off: Backligth Always Off
- Motion
24H: Motion detection always on (backlight turns on when motion is detected)
Nite: Motion detection on at night time (from 17-8)
Off: Motion detection Off
- Night
On: Notification vibration disabled at night (from 23–8)
Off: Notification enabled at night
- O Clock
On: every whole hour the watch will vibrate. 12'O'clock etc.
Off: Off
- Fitness
On: Fitness functionality on
Off: Off
- Language
Chinese
English
- Anti Loss
On: Alarm when Phone is out of BT range
Off: Off
Q: Is there Cyrillic support
A: Yes
Q: The GoClever Ecos Chronos is the same watch right?
A: Yes it is on the hardware side, and you can with a "hack" install the firmware from the ECOS on the Tommy. (see next post for How to.!)
Awesome Weloop Review by VECTRON
http://forum.xda-developers.com/smartwatch/other-smartwatches/weloop-tommy-smartwatch-looks-best-t2864444
Troubleshooting
Q: i can not update my watch/its stuck/acting weird
Have you tried to reset the watch? there are 3 ways to do it
Restart watch from app. under update there is a restart button (it says reset but it restarts and keeps all your settings)
Reset from watch (Last menu point, this resets everything)
Hard reset (connect charge cable and press up and down button to reset)
Force OTA update:
Connect your watch to the charger. (watch must be charging)
Press all 3 buttons on the side simultaneously
Release the 2 side buttons, and keep the middle button pressed until you get the upgrade connecting display. (this might take some seconds)
Delete connection from phone
Connect and pair from app and upgrade
If you are on an Android device and it cannot connect, try an ios device, and vice versa
Q: The watch keeps switching back to chinese
More people have experienced that if the language is non english the watch will reset to chinese. Changing the phone OS to english stops the watch from switching to Chinese.
"Hacks"
How to make your own watchfaces:
user fcsabika has created a cool tool to create your own watchfaces
WeLoop Tommy Watchface Creator
attached are also some watchfaces made by user ruicoel filename "project rui.zip"
How To install GoClever Chronos ECO firmware on Weloop tommy (android only)
Download latest ECO firmware to phone
Disconnect Watch from phone, install ECO app
Go to “Check For Upgrade”
Tap on the middle circle six times
“Select a firmware file___ [Browse]”
Watch must be in forced OTA
Update watch.
You can flash between weloop and Goclever firmware (always be careful and follow instructions when flashing, i take no responsibility for bricked or exploding watches...)
To install weloop firnware, follow same instructions but use weloop app instead.
PROJECT OPEN FIRMWARE (please make sure you understand what this is and what it does before you attemtp to flash your watch)
Make a Weloop Tommy an open source sport watch that can be used without a mobile phone. Want to see a heart rate when running, cycling speed and cadence when cycling or number of laps while swimming? Help to make it possible! LINK
This project is divided into six phases:
Phase 1: find out and document watch pinout so it will be possible to communicate with screen, accelerometer and a flash memory from a custom firmware. DONE
Phase 2: write a custom firmware that will print sample text on a screen and expose a BLE service. Firmware will be flashed using SWD connector. DONE
Phase 3: make it possible to upload a custom firmware using OTA. This will save the waterproof case from destruction. DONE
Phase 4: update softdevice to the newest version (S110 8.0.0). Add possibility to switch to other softdevice (S120/S130) DONE
Phase 5: create a "terminal" firmware that allows to control what is displayed on a watch from an android/iOS app. IN PROGRESS
Phase 6: create a "standalone" firmware using S130 softdevice that can connect to external sensors (HRS, CSCS etc) without a phone. TODO
Go support developer Krzysiek
Goclever APK & FW file is attached to this post.
Latest Chronos ECO firmware 3.18
http://www.chronos.goclever.com:8080/fileServer/firmware/CHRONOSECO_V3.18_1.bin
Chronos ECO app (android)
https://play.google.com/store/apps/details?id=com.yf.foreign.goclever
Chronos ECO IOS app
https://itunes.apple.com/th/app/goclever-chronos-eco/id955306578?mt=8
BUGS & Annoyances
Notification not always deleted from phone when deleted on watch
Watch freezes sometimes
Being able to set the night time manually would be great (This can be done with the Goclever fw)
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
skiiermike said:
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
Click to expand...
Click to collapse
Thanks was this working on ios or android?,
will add to FAQ
taleboblen said:
Thanks was this working on ios or android?,
will add to FAQ
Click to expand...
Click to collapse
Android.
Thx
Thnx for the information, all working ok on my samsung s4, get the last version v3.18.
thx again
backlight
first of all thanks for this thread :good:
the nite backlight on my tommy watch actually comes on after 5PM (17:00)
i am from Slovakia, phone language is English, time zone CET (GMT+1)
interesting to see that yours turns on after 23:00
chsustik said:
first of all thanks for this thread :good:
the nite backlight on my tommy watch actually comes on after 5PM (17:00)
i am from Slovakia, phone language is English, time zone CET (GMT+1)
interesting to see that yours turns on after 23:00
Click to expand...
Click to collapse
Thanks for the update. i decrypted some of the information from the official Weloop FAQ. and yes i can now confirm that you are right. it turns on from 17-8 thanks again. I have now updated the FAQ with the correct time for all Night settings. :good:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
k0ra said:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
Click to expand...
Click to collapse
Hi , the chronos eco app is not compatible with the Weloop Tommy.
Brand new Tommy, it was paired with my phone but the connection was unstable, so I tried and forced an OTA update, watch is "Updating... 0 pct" but now the phone cannot detect the watch any more
Resetting the watch will restart it in ota update mode again!
Any help appreciated...
l.capriotti said:
Brand new Tommy, it was paired with my phone but the connection was unstable, so I tried and forced an OTA update, watch is "Updating... 0 pct" but now the phone cannot detect the watch any more
Resetting the watch will restart it in ota update mode again!
Any help appreciated...
Click to expand...
Click to collapse
Happened to me also, try to delete connection under bluetooth settings on device. now connect to to weloop and pair from Weloop app. keep trying and then go to update. again persistence is key. keep trying to update suddenly it will connect and update.
Whas the watch on latest firmware when you tried the force OTA?
are you on android or ios see if there is an updated App for you phone. see link on OP for beta APK.
let me know if it works.
watch was not on latest firmware, cant' remember which version it had.
I'm on android, also v1.24 does not help as check for updates does not go beyond "Checking version...".
k0ra said:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
Click to expand...
Click to collapse
l.capriotti said:
watch was not on latest firmware, cant' remember which version it had.
I'm on android, also v1.24 does not help as check for updates does not go beyond "Checking version...".
Click to expand...
Click to collapse
Try to update the Weloop app, latest is 1.27.
kill weloop app
delete bt connection from phone.
Open weloop app
conmect and update. Keep trying it can take a couple of times.
If all fails if possible try with other device and or ios device
update: I used an iphone and after a few retries I got it on v3.18.
back to android, but the pairing and the sync is problematic, to say the least, on my Huawei P7...
skiiermike said:
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
Click to expand...
Click to collapse
If it's allowing you to select an update file, surely it is showing you the file system of the phone? Otherwise, you'd have no way to put a firmware update file there to select. My understanding would be this allows you to install a firmware update file stored on your phone, although I can't test this for sure as my Android phone is currently being repaired. There's some discussion about this here and that thread also contains a very small amount of analysis on the firmware file (VERY small amount, basically just analysing the name of the binary file), and another app that is apparently in some way related (link).
For what I can glean from the description of that app (seemingly made by the manufacturer of the SoC [System on a Chip] used in the WeLoop Tommy), it would appear that devices using the SoC (including the Tommy) have three firmwares: "bootloader", "soft device" and "application". The one embedded within the WeLoop app apk has the name "ble_app_ancs.bin"; ble stands for bluetooth low energy and ancs apparently stands for apple notification centre services. That leaves "app" - my guess would be this is the "application firmware". I'm not entirely sure the roles of the "bootloader" and "soft device" firmwares, but my guess is the one or other allows the device to get into "DFU mode" (or "OTA mode" as it seems to be referred to also), meaning in theory it should perhaps be possible to recover from any bricks arising from flashing dodgy application firmwares.
So potentially there is the option of reverse engineering the firmware (easily obtained from here: http://wtf.li/ - mirror of the APKs of the app [each of which contain a version of the firmware], and also one version of the firmware (the .bin file) separately), and creating a custom/modified one, while still being able to recover (because bootloader & soft device should be untouched). However, I have neither the expertise nor the time to look into that.
Without an Android phone with which to run either of the apps right now, I can't poke about too much (I only received my Tommy today), but once I get my phone back I'll maybe try and see if I can find anything else interesting. I'd like to see if I can figure out any way to get access to the watch faces, and see if they can be reverse engineered in any way, for example.
EDIT: Here is the output of strings run on the firmware binary from the latest version of the app on http://wtf.li : http://pastebin.com/X7TQXTb3 - nothing particularly interesting, a few filenames of the source files and a few other strings seen in the watch interface and stuff.
EDIT: A couple of URLs accessed by the app (seemingly related to updating):
http://au.umeng.com/api/check_app_update
http://www.yfsmart.com/weloopInterface/getFirmware.do
I can't see anything on these sites, my guess would be they need query strings parameters or something (not really sure what, some way of identifying that the app is accessing the site) to actually do anything.
EDIT: Hmm... http://www.yfsmart.com/weloopInterface/firmware_Upload.jsp - this site seems to allow you to upload a firmware. I wonder if it allows anyone to upload a firmware, which would then be downloaded by everyone when they check for updates? Certainly seems rather insecure...There's a bunch of other pages at http://www.yfsmart.com/weloopInterface/ haven't looked through them all yet.
EDIT: From what I can glean from this page ("SoftDevices" section under the "Development Tools and Software" tab), it seems like the "soft device" firmware is essentially a bit like a library, it's a precompiled binary supplied by Nordic (company that makes chip inside Tommy) which provides all the networking functions etc. which the "application" firmware uses. So:
Code:
application = front end UI (basically, the part WeLoop made)
soft device = "library" via which application can access hardware etc.
bootloader = initial part of firmware that loads SD + app firmwares
So the only really interesting part is probably the application firmware, the part that is in the WeLoop app. That's the code that actually "matters", the rest is just low level stuff. For actually changing the interface or whatever, modifying the app firmware would be all that's needed (for example, to increase the font size or the back light duration etc.).
SifJar said:
If it's allowing you to select an update file, surely it is showing you the file system of the phone? Otherwise, you'd have no way to put a firmware update file there to select. My understanding would be this allows you to install a firmware update file stored on your phone, although I can't test this for sure as my Android phone is currently being repaired. There's some discussion about this here and that thread also contains a very small amount of analysis on the firmware file (VERY small amount, basically just analysing the name of the binary file), and another app that is apparently in some way related (link).
For what I can glean from the description of that app (seemingly made by the manufacturer of the SoC [System on a Chip] used in the WeLoop Tommy), it would appear that devices using the SoC (including the Tommy) have three firmwares: "bootloader", "soft device" and "application". The one embedded within the WeLoop app apk has the name "ble_app_ancs.bin"; ble stands for bluetooth low energy and ancs apparently stands for apple notification centre services. That leaves "app" - my guess would be this is the "application firmware". I'm not entirely sure the roles of the "bootloader" and "soft device" firmwares, but my guess is the one or other allows the device to get into "DFU mode" (or "OTA mode" as it seems to be referred to also), meaning in theory it should perhaps be possible to recover from any bricks arising from flashing dodgy application firmwares.
So potentially there is the option of reverse engineering the firmware (easily obtained from here: http://wtf.li/ - mirror of the APKs of the app [each of which contain a version of the firmware], and also one version of the firmware (the .bin file) separately), and creating a custom/modified one, while still being able to recover (because bootloader & soft device should be untouched). However, I have neither the expertise nor the time to look into that.
Without an Android phone with which to run either of the apps right now, I can't poke about too much (I only received my Tommy today), but once I get my phone back I'll maybe try and see if I can find anything else interesting. I'd like to see if I can figure out any way to get access to the watch faces, and see if they can be reverse engineered in any way, for example.
EDIT: Here is the output of strings run on the firmware binary from the latest version of the app on http://wtf.li : http://pastebin.com/X7TQXTb3 - nothing particularly interesting, a few filenames of the source files and a few other strings seen in the watch interface and stuff.
EDIT: A couple of URLs accessed by the app (seemingly related to updating):
http://au.umeng.com/api/check_app_update
http://www.yfsmart.com/weloopInterface/getFirmware.do
I can't see anything on these sites, my guess would be they need query strings parameters or something (not really sure what, some way of identifying that the app is accessing the site) to actually do anything.
EDIT: Hmm... http://www.yfsmart.com/weloopInterface/firmware_Upload.jsp - this site seems to allow you to upload a firmware. I wonder if it allows anyone to upload a firmware, which would then be downloaded by everyone when they check for updates? Certainly seems rather insecure...There's a bunch of other pages at http://www.yfsmart.com/weloopInterface/ haven't looked through them all yet.
EDIT: From what I can glean from this page ("SoftDevices" section under the "Development Tools and Software" tab), it seems like the "soft device" firmware is essentially a bit like a library, it's a precompiled binary supplied by Nordic (company that makes chip inside Tommy) which provides all the networking functions etc. which the "application" firmware uses. So:
Code:
application = front end UI (basically, the part WeLoop made)
soft device = "library" via which application can access hardware etc.
bootloader = initial part of firmware that loads SD + app firmwares
So the only really interesting part is probably the application firmware, the part that is in the WeLoop app. That's the code that actually "matters", the rest is just low level stuff. For actually changing the interface or whatever, modifying the app firmware would be all that's needed (for example, to increase the font size or the back light duration etc.).
Click to expand...
Click to collapse
Thank you for the insights and findings its all very promising. :good:
On a sidenote:
I talked to one of my colleagues who is an engineer (i'm not a dev but a Designer), it seems like we in the office are playing around with the exact same SOC from NordicSemiconducter. we tried one of the apps from the google play store and it connects to the weloop(see attached pic). The app was called "nRF Master Control Panel", tried the other apps from NordicSC but no luck.
Hopefully there will be some sort of SDK with the v3.0 release on the 30th...
I got my Android phone back today, and haven't tinkered too much with Tommy just yet, but I can confirm that the file system you are browsing when you tap the percentage 5 times during an update is just the phone file system. It browses from root (i.e. /), rather than /sdcard or whatever, which is the standard, user accessible partition, hence there are some folders etc. you may not recognise, but amongst them will be "sdcard" which will take you to your regular storage (note: this is the case on phones without a micro SD card as well), where you could easily place an update file.
SifJar said:
I got my Android phone back today, and haven't tinkered too much with Tommy just yet, but I can confirm that the file system you are browsing when you tap the percentage 5 times during an update is just the phone file system. It browses from root (i.e. /), rather than /sdcard or whatever, which is the standard, user accessible partition, hence there are some folders etc. you may not recognise, but amongst them will be "sdcard" which will take you to your regular storage (note: this is the case on phones without a micro SD card as well), where you could easily place an update file.
Click to expand...
Click to collapse
Thanks for the confirmation. :good:
taleboblen said:
Troubleshooting
Force OTA update:
Connect your watch to the charger.
Press all 3 buttons on the side simultaneously
Release the 2 side buttons, and keep the middle button pressed until you get the upgrade connecting display. (this might take some seconds)
Delete connection from phone
Connect and pair from app and upgrade
If you are on an Android device try an ios device, and vice versa
Click to expand...
Click to collapse
I tried to use the OTA update to go from 3.17 to 3.18 (on Android) but Tommy stuck on screen "WeLoop ... Udating 0%", my smartphone (HTC M8) with its APP (latest version) dont find the Tommy and it remains bricked, how do I restart it? I tried all combinations, but remains on the screen, help me!
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.
in case someone is interested, i just saw an update in huawei firmware finder: L09C432B182
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1635/g104/v90811/f2/full/filelist.xml
but it was not approved
not approved firmwares drives device into NRD test keys
venugopalu007 said:
but it was not approved
not approved firmwares drives device into NRD test keys
Click to expand...
Click to collapse
i don't think so ..
OldDroid said:
i don't think so ..
Click to expand...
Click to collapse
ho thanks for this
Hi guys, I tried downloading the correct firmware (Update) unpacked and placed in the folder created on sd card dload. Then I tried to get into the Upgrade software mode. The phone reboots, seems to update the firmware but shortly afterwards it fails because incorrect firmware appears, and yet it's ok. I do not think it's updating because the firmware is not approved. Has anyone tried it?
nino64 said:
Hi guys, I tried downloading the correct firmware (Update) unpacked and placed in the folder created on sd card dload. Then I tried to get into the Upgrade software mode. The phone reboots, seems to update the firmware but shortly afterwards it fails because incorrect firmware appears, and yet it's ok. I do not think it's updating because the firmware is not approved. Has anyone tried it?
Click to expand...
Click to collapse
as i said before, it runs perfect here, but the update process is kinda complicated :/
changelog?
beltxo said:
changelog?
Click to expand...
Click to collapse
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1635/g104/v90810/f2/full/changelog.xml
That's B130 / B132 changelog. Weird. Maybe the changelog info has been not updated yet.
beltxo said:
That's B130 / B132 changelog. Weird. Maybe the changelog info has been not updated yet.
Click to expand...
Click to collapse
see this for full ota http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1635/g104/v90811/f2/full/changelog.xml
Same
beltxo said:
Same
Click to expand...
Click to collapse
i think the database have some to update
OldDroid said:
as i said before, it runs perfect here, but the update process is kinda complicated :/
Click to expand...
Click to collapse
Please, explain how to upgrade firmware
ferrarif1 said:
Please, explain how to upgrade firmware
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-8-pro/how-to/oeminfo-c432-t3625886
no need to when i already wrote a guide for it ?
OldDroid said:
https://forum.xda-developers.com/honor-8-pro/how-to/oeminfo-c432-t3625886
no need to when i already wrote a guide for it
Click to expand...
Click to collapse
Thankyou for the reply, you confirm that at the end of the process I have a factory erased locked bootloader phone ?
upgrading Honor 8 pro B310 to B 182
questions:
Do you have to have boot unlocked?
Do you need root y TWRP?
OldDroid said:
https://forum.xda-developers.com/honor-8-pro/how-to/oeminfo-c432-t3625886
no need to when i already wrote a guide for it
Click to expand...
Click to collapse
nino64 said:
Tutorial
1. download the firmware for your model
2. extract the fw_DUK-<model number>.tar.gz file
3. format your MicroSD as ExFAT (Fat32 is limited to 4gb file transfer size)
4. copy the extracted dload folder in the root directory of your MicroSD
5. shutdown the device, insert the MicroSD and disconnect the USB cable
6. boot device using VOL+, Vol- and POWER and keep this combo pressed until the recovery process starts
7. once finished your device should reboot and be back in a working state
questions:
Do you have to have boot unlocked?
How do you extract the tar.gz file from Upadate?
Do you need TWRP?
Click to expand...
Click to collapse
Part 3 of the tutorial, not part 1
Looks like there's a B183 out there, but still same changelog as B130...
Accumulative changelog from B130 to B182 for Honor V9 (chinese version of 8 Pro)
* Adds the call encryption feature for China Telecom for better security.
* Optimizes prompts to enable Wi-Fi hotspot when Data saver is enabled.
* Integrates Google security patches for improved system security
* Improves system performance and stability for smoother operations.
* Optimizes power consumption for extended use.
* Fixes an issue where your device would occasionally fail to power on.
* Fixes an issue where sliding to answer calls would occasionally not work.
* Optimizes the response speed when viewing WeChat messages using WLAN.
* Enables the feature to add Honor watermarks by default.
* Optimizes touchscreen sensitivity.
* Optimizes GPS performance for more accurate positioning.
beltxo said:
Accumulative changelog from B130 to B182 for Honor V9 (chinese version of 8 Pro)
* Adds the call encryption feature for China Telecom for better security.
* Optimizes prompts to enable Wi-Fi hotspot when Data saver is enabled.
* Integrates Google security patches for improved system security
* Improves system performance and stability for smoother operations.
* Optimizes power consumption for extended use.
* Fixes an issue where your device would occasionally fail to power on.
* Fixes an issue where sliding to answer calls would occasionally not work.
* Optimizes the response speed when viewing WeChat messages using WLAN.
* Enables the feature to add Honor watermarks by default.
* Optimizes touchscreen sensitivity.
* Optimizes GPS performance for more accurate positioning.
Click to expand...
Click to collapse
Waiting for this update in India!
********** ANNOUNCEMENT - Beta Enrollment without Banner (OPEN NOW - Nov 16,17) - Read More Here
INTRODUCTION - Hello all. Now Samsung wants us to go to Members app and keep looking for banner to sign up for Android 11, One UI 3 Beta . It went live October 27th, 10:20 PM EST, As fate would have it, i went to sleep early, i missed it and the banner refused to show up for me in the morning. Download was only showing up for people with unlocked variants on ATID firmware.
DISCLAIMER / NOTICE - Flashing is always risky. I am not responsible for anything that may happen to your device including but not limited to it turning against you, making you its slave and sucking you into the Matrix.
This post is a collection of wisdom, research and hard work of many people over many years across many forums and not just XDA. I will try to credit and link to their original posts.
TIP -Keep in Notice -This SHALL NOT Factory Reset Your Device or Format Data, it is still a good idea to Take Back Up - Just a Suggestion - Always have a latest Back Up
******** UPDATE - It seems ATT devices are getting wiped now if its CSC or the Sim remains to be tested.
i don't have ATT hence cant verify but in case you have an Unlocked device (N986U1) with ATT sim, then, removing sim and Changing the CSC to XAA/XAA/XAA before sideloading Beta is advisable.
PROBLEM STATEMENT - Missed the One UI 3.0, Android 11, Beta Sign up Banner in Members app or got the banner but didn't get the download and I really want it NOW.
Not sure if you want it now? - Find the BETA CHANGELOG HERE
GRAB YOURSELF A COFFEE / DRINK, because depending on where you at and how fast you/your internet speeds/your Machine is this may take anywhere between 7 to 45 MinsSOLUTION -
1. Pre-Requisites - Make sure Following Conditions are met before you start
You need a PC/Laptop along with your phone and USB Cable.
You need ADB installed, you can use ADB on Linux too - NOTE If your ADB Tools are not working, download my ADB Folder called platform-tools. Then extract it somewhere easy to remember/ find, like desktop
Remember the Location of the folder where you have ADB installed / Location of platform-tools- This is the location containing adb.exe file.
You may or may not need ADB/USB Drivers if any errors in ADB please Download Drivers from here and Install on your PC.
This following one step is relevant Only for flashing Beta 1
Use Odin to Flash Unlocked (SM-N986U1) ATID Firmware if you are not on that. Refer this thread to get your Firmware.
For changing Firmware from N986U to N986U1 and / or GUIDE TO FLASHING USING ODIN Refer This thread
______________________________________________________________________________________________________________________________________________________________
2. Now Download the relevant Beta File that you intend to flash - note that to Sideload Beta 2 you need to be on Beta 1 first. Mandotory Sequence = Beta 1>>Beta 2>>Beta 3 There is no skipping versions possible here.
BETA 1 (ZTGJ) Get the Beta1.zip file from here Thanks to @thatotherguy.. for the original zip.
BETA 2 (ZTK1) Get the Beta2.zip file from here
BETA 3 (ZTK9) Get the Beta3.zip file from here
______________________________________________________________________________________________________________________________________________________________
*************** Apply Update from SD card failed for me (Feel free to try that ) but here we will be using ADB Sideload Feature in Stock Recovery*************
HOW TO - Using ADB Sideload - Windows -The Process is Similar for Linux too
1. Copy the downloaded zip file to the ADB Folder (From Pre-Requisite step). ADB Folder is the folder containing ADB.exe it might be named differently for you (The one i have posted is called platform-tools)
2. Open Command Prompt Window as Admin.
3. Type in
Code:
cd Copy-paste the location of your ADB folder here
4. Connect the phone to the PC using USB Cable and Unlock it. Go to Developer Options and Switch on USB Debugging.
To turn on developer options go to Settings>>About Phone>>Software Information>> Then tap the build number 7 times - Developer options will appear at the bottom of Settings Menu
5. On your PC Type in Command Prompt
Code:
adb devices
6. Give Permission that appears on your phone and PC - I check the box Always Allow, you should do the same.
7. Now type the following and the phone will reboot to recovery.
Code:
adb reboot recovery
8. Once you see recovery on your phone Use Volume Keys to scroll down to Apply Update from ADB and press Power Button.
9. Now on your PC, Type the following in Command Prompt; this is just to be sure, it should show the device name with Sideload next to it.
Code:
adb devices
10. Type
Code:
adb sideload Beta1.zip
For Beta 2 use adb sideload beta2.zip Similarly For Beta 3 use adb sideload beta3.zip. Use whatever you have named the zip file. Most people use update.zip. The commands here are for the attached files in this post and their naming convention.
11. Wait for it to finish and Done
2nd (Second) BETA Is Out- How To Do this if you are not able to Enroll for Beta and or don't see update to download even after Enrolling
Second Beta should be flashed After Beta 1. Second Beta (ZTK1) can not be flashed unless you have Beta 1 (ZTJG).
To flash follow the same instructions as above only this time the prerequisite is you have to be on the 1st Beta. Download the 2nd Beta (ZTK1) Zip File to flash Here Thanks to @hayabusa1300cc for the FOTA Link.
3rd (Third) BETA Is Out- Nov 16, 2020 Do this if you are not able to Enroll for Beta and or don't see update to download even after Enrolling
Third Beta should be flashed After Beta 1>>Beta 2. Third Beta (ZTK9) can not be flashed unless you have Second Beta (ZTK1). Second Beta (ZTK1) can not be flashed unless you have Beta 1 (ZTJG).
To flash follow the same instructions as above only this time the prerequisite is you have to be on the 2nd Beta. Download the 3rd Beta (ZTK9) Zip File to flash Here
OPTIONAL THINGS TO DO POST UPDATE
If you want to enable RCS (In the Native SMS app) and Native Video calling (This feature is on Tmobile) have a look at this thread.
Check out this Guide Service Mode and CSC Guide/Enable LTE/5G Bands and Services/5G Low Band on U1 by @mellojosh
TROUBLESHOOTINGSome people might run into "cant read update.zip" error for that we need to make ADB Large address aware. Follow the Steps Here I use the Advanced mode as it shows the true false flags. - This wont happen if you use the ADB Tools provided by me above under the Pre-requisites section.
************** FOR FUTURE BETA OTA Questions / Bugs - Observations and some more info - Go Here ********Please dont ask questions without reading.
QUESTIONS, HELP & SUPPORT ?? - See if I am Online here on this Live Chat
If it helped HIT THAT THANKS BUTTON, what are you waiting for ? Cheers !!
Suggest you rename the title for which device it's for as it's not for every snapdragon (right?)
I get "adb: failed to read command: No error"
ekerbuddyeker said:
Suggest you rename the title for which device it's for as it's not for every snapdragon (right?)
Click to expand...
Click to collapse
I flashed on an Unlocked one so there is no way for me to tell if this can be flashed on N986U since so many people have flashed Unlocked firmware on the U devices using Odin (One confirmed guy flashed unlocked firmware on Verizon locked device and got the Beta banner) hence i think this will work for all Snapdragon devices. Give it a try and see. Just that before you try this make sure you are on ATID firmware.
d_ganggreen said:
I get "adb: failed to read command: No error"
Click to expand...
Click to collapse
Use a different USB Cable. A good quality one preferably. Also try changing USB port.
Can i install this on sm n 9860 version and does google pay and samsung pay beta work?
warriorvibhu said:
Use a different USB Cable. A good quality one preferably. Also try changing USB port.
Click to expand...
Click to collapse
Hmm, still getting same. Tried 3 cables including the one that came with the phone and both usb ports on my computer.
d_ganggreen said:
Hmm, still getting same. Tried 3 cables including the one that came with the phone and both usb ports on my computer.
Click to expand...
Click to collapse
Are you on ATID Firmware?
warriorvibhu said:
Are you on ATID Firmware?
Click to expand...
Click to collapse
I am, I odin flashed it a few weeks ago.
1gorelo said:
Can i install this on sm n 9860 version and does google pay and samsung pay beta work?
Click to expand...
Click to collapse
Too early in the morning to go out and test that. This is Beta and i have already encountered some bugs. So you have to be up for that.
Good Lock wont work, gesture navigation is buggy, you can not even apply wallpapers from the Galaxy Themes app.
Wallpaper Service on the other hand is greatly improved. Fingerprint sensor is much faster.
d_ganggreen said:
I am, I odin flashed it a few weeks ago.
Click to expand...
Click to collapse
My friend there are so many reasons why that error can happen. Sometimes you might have to change the ADB version. I am attaching the platform-tools i used. Extract this zip inside folder on desktop and try. If that doesnt work you might need to update ADb/Samsung drivers. Let us know if this works.
warriorvibhu said:
My friend there are so many reasons why that error can happen. Sometimes you might have to change the ADB version. I am attaching the platform-tools i used. Extract this zip inside folder on desktop and try. If that doesnt work you might need to update ADb/Samsung drivers. Let us know if this works.
Click to expand...
Click to collapse
Thank you! Whatever it was, that worked. I am able to get it running with your tools. I am running it now.
CHANGELOG - Android 11_OneUI 3 Beta
************ Notice: This changelog is compiled from various different resources online, verification of these features rests with the users **********
Code:
[COLOR="SeaGreen"][CENTER]BETA CHANGELOG[/CENTER][/COLOR]
[B]Home screen[/B]
– Touch and hold an app to add an associated widget
– Turn the screen off by double-tapping on an empty are of the Home screen. You can turn this on in Settings > Advanced features > Motion and gestures.
Lock screen
– Dynamic Lock screen now has more categories, and you can select more than one.
– Lock screen widgets are improved.
[B]Contacts, Phone and Call Background[/B]
– Added the ability to edit multiple linked contacts at one time.
– Added an option to help you quickly delete duplicate contacts.
– Enhanced the search experience.
– Extended the storage period of the Trash bin from 15 to 30 days.
– Added the ability to customize the call screen with your own pictures and videos.
[B]Messages[/B]
– Created a Trash bin to store recently deleted messages.
– Call & Text on other devices
– Added the ability to turn Call & text on other devices on or off with Bixby Routines.
[B]Calendar[/B]
– Events with the same start time are now shown together in month and agenda view.
– Reorganized options for adding and editing events.
– Improved layout for full screen alerts.
[B]Reminder[/B]
– Improved layout for full screen alerts
[B]Camera[/B]
– Improved auto-focus and auto exposure functionality and usability.
– Improved stabilization when taking pictures of the moon at high zoom levels.
[B]Photo editor[/B]
– Added the ability to revert edited pictures back to their original versions.
[B]Bixby Routine[/B]
– Grouped preset routines help you get started quickly and learn how to build your own routines easily.
– You can now see what actions are reversed when a routine ends.
– New conditions have been added, such as a specific start time, the disconnection of a Bluetooth device or Wi-Fi network, a call from a specific number, and more.
– New actions have been added, including talking to Bixby and accessibility actions.
– You can add a customized icon for each routine and add routines to the Lock screen for quick access.
[B]Digital wellbeing and Parental controls[/B]
– Added trends to your weekly report. You can see how your usage has changed since the previous week and check your usage time for each feature.
– Added phone usage time while driving to the weekly report.
– Added a lock screen widget so you can check your screen time without unlocking your phone.
– Added separate profiles for personal and work modes so you can track your screen time separately.
[B]Internet[/B]
– Added ability to block websites from redirecting you when you tap the Back button.
– Added warnings and blocking options for websites that shot too many pop-ups or notifications.
– Rearranged menus to make things easier to find.
– Added several new add-ons, including one that translates websites.
– Added option hide the status bar for a more immersive browsing experience.
– Increased maximum number of open tabs to 99.
– Added ability to lock and reorder tabs.
– Improved design for tab bar which is now supported on all devices.
– Ended support for Samsung Internet edge panel.
[B]Quick panel[/B]
– See your conversations and media more conveniently in their own sections when you swipe down from the top of the screen.
[B]AOD[/B]
– Always On Display widgets are improved.
[B]Accessibility[/B]
– Get quick access to the most important accessibility settings during device setup.
– Get recommended accessibility features based on what you use.
– Set the Accessibility shortcut more easily in settings.
– Sound detectors now work with your SmartThings devices such as TVs and lights to give you more visible alerts when the doorbell rings or a baby is crying.
[B]Samsung Keyboard[/B]
– You can find the keyboard in settings more easily under General management in Settings, and the settings have been reorganized to put the most important ones first.
Samsung DeX
– You can now connect to supported TVs wirelessly.
– New touchpad multi-gestures let you change screen zoom and font size more easily.
Feel free to add anything else that you observe.
warriorvibhu said:
Wohooo Fingers Crossed. Did it finish ?
Click to expand...
Click to collapse
Yes it did, running 3.0 beta now!
warriorvibhu said:
I flashed on an Unlocked one so there is no way for me to tell if this can be flashed on N986U since so many people have flashed Unlocked firmware on the U devices using Odin (One confirmed guy flashed unlocked firmware on Verizon locked device and got the Beta banner) hence i think this will work for all Snapdragon devices. Give it a try and see. Just that before you try this make sure you are on ATID firmware.
Click to expand...
Click to collapse
I'm on n9860 which is a snapdragon. I'm not sure if it's the same. Anyone want to try?
My US unlocked stuck at 16% when sideloading? Is it normal?
jianansong said:
My US unlocked stuck at 16% when sideloading? Is it normal?
Click to expand...
Click to collapse
Since how long ?
Which step are you at?
warriorvibhu said:
Since how long ?
Which step are you at? (See Pics)
Click to expand...
Click to collapse
On my phone, it shows "Verifying updte package..."
On the adb, it shows serving update.zip 16%.
It has been there for at least 20 minutes... Do I need to cancel and restart?
I used the uploaded adb and the first link for update.zip.
jianansong said:
On my phone, it shows "Verifying updte package..."
On the adb, it shows serving update.zip 16%.
It has been there for at least 20 minutes... Do I need to cancel and restart?
I used the uploaded adb and the first link for update.zip.
Click to expand...
Click to collapse
Yes thats too long Cancel and restart, It took me 97.5 seconds to verify the package.
Your ADB is fine dont change that. For firmware you can try using the second link from google drive. do you meet the criteria Unlocked and on ATID ?
warriorvibhu said:
Yes thats too long. do you meet the criteria Unlocked and on ATID ?
Click to expand...
Click to collapse
Yes, mine is us unlocked and it's on ATID. Do you know how I could cancel it?
---------- Post added at 03:45 PM ---------- Previous post was at 03:43 PM ----------
jianansong said:
Yes, mine is us unlocked and it's on ATID. Do you know how I could cancel it?
Click to expand...
Click to collapse
At the command line, I clicked "control + C" and surprisingly the progress number starts moving again, and now I am at 53% and it's still going...