Guide to follow once I get to my home computer.
This guide will cover how to backup, restore, and reformat your AW/TS/AX/IBC smart watch nvram and baseband information.
It will also cover tuning the radio to maximize tower connection efficiency and data throughput.
REQUIREMENTS
PC running Windows XP/7/8 or Virtual Machine capable of running Windows.
An X201 Umeox Unit (Includes Simvalley, Iconbit, Umeox, or Omate).
The charging cradle.
A USB cable and free USB port.
Maui META Tools, which can be found below.
The proper MOLY[region].ini for your region/device.
Android CDC drivers (most Windows 7/8 systems already have these installed, if not the download link is below).
READ THIS FIRST
Running these tools may void your device warranty, but the chances of a hard-brick are practically zero. In the event you somehow brick your device, try removing the battery first. If that does not work, you must use SP Flash Tools or MTK Droid Tools to restore your software! This guide assumes you have at least a basic understanding of PRELOADER mode and MediaTek devices in general.
What does this do?
Great question! Essentially the correct radio throughput and tuning will give you a stronger connection to your towers, allowing for proper communication between the tower and the antenna. You may see increases in data speeds (though it really depends on your area) and a decrease in dropped connections.
I am not responsible for what happens to your device as a result of this guide, but I am always happy to answer questions.
Step 1
First, you must make sure Quick Boot is disabled. Enter the accessibility settings menu and scroll to the bottom. Unmark Quick Boot and then power down your device.
Open up MAUI META tools using Compatibility Settings for Windows XP. You should see this screen:
{
"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"
}
Go to the options menu and make sure USB mode and connection are set to "META".
Click on "Reconnect" and then plug the device into the USB port. You should see the Splash Screen appear on the watch after a few seconds. If you are doing this for the first time it may take a little longer. If you don't see the red circle turn green and no connection shows, try a different USB port. If you can see the Splash Screen (it won't disappear) you are already in META mode and should have a connection to the PC.
Step 2
Once connected, you will see the fields populate with baseband information and it should say "Connected with target". Click on "Update Parameter" and the window to the right should come up. You can upload from flash if you want to back up your moly.ini file (it contains your stock baseband tuning information). When you are ready to re-tune, go ahead and click on "Load From File" and select the MOLY[region].ini file.
You may have to repeat this step a couple of times as MAUI is fickle on operating systems that aren't natively Windows XP until MediaTek updates.
Step 3
Click Download to Flash to continue. This may also need repetition but should work the first time.
Step 4 - IMPORTANT!
DO NOT DISCONNECT YOUR WATCH PHYSICALLY FROM THE USB PORT UNLESS YOU WANT IT STUCK IN META MODE AND LIKE PULLING THE BATTERY OUT. CLICK ON DISCONNECT FIRST SO THAT THE SOFTWARE TELLS THE WATCH TO POWER DOWN.
Once that's done, you're set.
Congratulations! You've tuned your radio to the proper frequency. To restore just repeat the process but select your stock baseband backup or reflash the stock firmware in SP Flash Tools.
OP Updated. Second post to include downloads once everything is upped to its proper place.
All Tools - [HERE]: Includes tools necessary for flashing firmware, backing up of your device, different modems for your device, and drivers for the preloader.
MAUI META 3G - [HERE] The main tuning program for your MTK device.
EU Moly Configuration File - [HERE]
Optimized NA Moly Configuration File [HERE]
Stock Moly Configuration File [HERE]
Hi are you uploading the files or should I start looking for them on the interwebs? Does this help?
Yes, I will be. Sorry, I've had a busy week.
Sent from my Galaxy Nexus using Tapatalk 2
No worries figured you had slow internet like me. LOL kept refreashing the page for a week now. J/k
2nd Post Updated with download links.
I cannot get past through "Download to Flash". Whenever I click "Download to Flash", it opens up a windows-open dialog box and once the moly file is selected it gives two error message boxes related to NVRAM.
Also, one thing I noticed that if you are stuck in META mode, you can do a reboot by issuing adb reboot instead of pulling the battery out.
Which file are you picking? The program is pretty fickle.
Sent from my Galaxy Nexus using Tapatalk 2
kuronosan said:
Which file are you picking? The program is pretty fickle.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
File is moly[na-optimized].ini
I am following your steps mentioned above. I think I am good till step #2 and get error on step #3. I am actually confused with step#2 and step#3. Since I already selected the file during step#2, it asks again for a file on step#3. On step#2, I chose moly[na-optimized].ini. Do I choose same file or different one for step#3 ?
Hi, I have the same issue
pkshr said:
File is moly[na-optimized].ini
I am following your steps mentioned above. I think I am good till step #2 and get error on step #3. I am actually confused with step#2 and step#3. Since I already selected the file during step#2, it asks again for a file on step#3. On step#2, I chose moly[na-optimized].ini. Do I choose same file or different one for step#3 ?
Click to expand...
Click to collapse
trifora said:
Hi, I have the same issue
Click to expand...
Click to collapse
I will test in a PC with win-xp later and report back.
Sent from my Nexus 5 using Tapatalk
Let me check it out, it should work.
Sent from my Galaxy Nexus using Tapatalk 2
kuronosan said:
OP Updated. Second post to include downloads once everything is upped to its proper place.
All Tools - [HERE]: Includes tools necessary for flashing firmware, backing up of your device, different modems for your device, and drivers for the preloader.
MAUI META 3G - [HERE] The main tuning program for your MTK device.
EU Moly Configuration File - [HERE]
Optimized NA Moly Configuration File [HERE]
Stock Moly Configuration File [HERE]
Click to expand...
Click to collapse
ALL TOOLS link "File not found"
mghtymse007 said:
ALL TOOLS link "File not found"
Click to expand...
Click to collapse
All Tools was updated so direct links no longer work
http://d-h.st/users/Lokifish Marz/?fld_id=28889#files
kuronosan said:
Let me check it out, it should work.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So I found a pc with windows xp and re-did the whole thing but the error is still the same at the step #3. Any help would be appreciated.
pkshr said:
So I found a pc with windows xp and re-did the whole thing but the error is still the same at the step #3. Any help would be appreciated.
Click to expand...
Click to collapse
When I get my hands on an NA unit I'll try again. It might be because of the Maui version I'm using.
Sent from my Galaxy Nexus using Tapatalk 2
pkshr said:
So I found a pc with windows xp and re-did the whole thing but the error is still the same at the step #3. Any help would be appreciated.
Click to expand...
Click to collapse
Also trying on XP. Drivers failing to install... I disabled driver signing.
Something else i'm missing?
mghtymse007 said:
Also trying on XP. Drivers failing to install... I disabled driver signing.
Something else i'm missing?
Click to expand...
Click to collapse
Drivers installation were fine on XP however gave warning in win7 which I bypassed and went smooth. It's just that damn step #3
kuronosan said:
When I get my hands on an NA unit I'll try again. It might be because of the Maui version I'm using.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Sounds good. One question though - what file do you pick for Step #2 and Step #3. Is it the same moly..ini?
For loading the nvram you need to pick the AP DB file. The ini file isn't loaded until after, during step 2. I just got shipping info on the U.S. unit, so I'll be able to test soon.
Sent from my GT-P5110 using Tapatalk 2
Related
BHP090808 PRESENTS
I545 ALL-IN-ONE TOOL ROOT + RECOVERY INSTALLER
**READ READ READ AND READ AGAIN**
DO NOT RUN IF YOU ARE ON NEW ME7 OTA UPDATE!
This tool was created to simplify the rooting and recovery installation on this device. The rooting method used is the same method already posted in this development section. I just put all the resources into a tool and provided easy to follow instructions. The root process is not a one click. You must read instructions in tool window for each step of the rooting process. It is very straightforward and easy to follow, but you must follow the instructions exactly. Once rooting is complete all other steps are one click features including recovery installation.
Make sure you have latest samsung drivers installed. I recommend downloading Samsung Kies, It will automatically download latest drivers for you. Make sure unknown sources is checked and USB Debugging is enabled or the tool will not see your phone. Also make sure you do not have any pw or pattern lock screen enabled. As soon as you start step 1 check your phone screen. You will see a prompt to authorize your computer. Select ALWAYS ALLOW. This is the cause of the majority of errors. Also the usb cable that came with your s4 is recommended. If you are having issues with odin recognizing your phone check drivers and try using a different usb port. If using a desktop I recommend using the rear usb ports. Prep step (#2) removes install-recovery.sh and KNOXAgent.apk from your phone. These have been known to cause unwanted errors.
If when rebooting from recovery you are prompted with a message advising root may have been lost would you like recovery to fix it? I have always chosen NO and had no issues.
I do not offer support on either recovery or any rom you flash after this process. Check their respective threads for any and all information. Links to both recovery threads are included as options in tool.
I've included latest CWM (credit OUDHS & Shabbypenguin) and TWRP (credit Team Win). The rooting method and kernels used were provided by sextape. The step by step root process from open1your1eyes0. The motochopper exploit was created by the legendary djrbliss. Also a big thanks to djrbliss for Loki, without which none of this would be possible. Make sure to find these fine folks and give thanks, money, beer, your first born..... whatever you see fit.
I'd also like to thank niv3d, an21281, CraziiChief and all of my other testers. I'd also like to thank my wife and kids for leaving me alone while I worked on this. Mirrors are ok, just pm me the link to list in the OP.
Hope this makes someones life easier.... Have a nice day!!!!
Instructions:
Download zip file
Unzip on desktop
Connect phone with USB debugging enabled
Click RUN_ME (inside unzipped folder)
Pick option and go!!
Have patience it takes a few for cpu to see phone after reboots and in Odin
dont disconnect phone until process is complete
If stock start with option 1
If already rooted start with option 2 then choose recovery
Download-
I545 All-In-One Tool
https://mega.co.nz/#!I1c1jTBY!GCtdvXRoeXiCRNgjXge3CA9UZ3FIBtHf-m2_kQCr3BI
Mirror-
http://db.tt/1wpdewwY
Dont forget to hit the thanks button and rate thread 5 stars:thumbup:
And if youd like to buy me a beer I wont complain :beer:
Thanks for the beer list::beer:
(Donations Received)
yamaharider
Michael Oconnell
SolemnSinner
Mills23
Eric Lee
Artiepea
JNava420
Footbaggin
Charles Uniman
Updated 5/30
oudhs cwm is now 1.0.3.5
Updated 5/31
Fixed script typos
(Thanks scrosler)
Updated 6/1
Added to prep script
Added additional instruction script
Updated 6/3
Fixed script typos
(Thanks opethfan89)
Updated 7/8
TWRP updated to 2.6.0.0
Great job! This tool simplifies the root process and makes it a breeze for those who are tempted to root and flash! Give it a shot you won't be disappointed!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tested this utility a few hours ago and it works great! Just make sure to follow the directions and give it time to do every step, very easy!
Complete newb question here, and searching didn't turn up much.. Seeing as there is no Bootloader unlock yet, theoretically you should be able to just revert to stock and unroot and no one would know you were ever rooted/ROMd, right?
If I completely missed a post that explained this, sorry.. I searched and didn't see it.
Yep. Just Odin back to stock and you're done.
Sent from my SCH-I605 using Tapatalk 4 Beta
Just used this method to root and install recovery on my new S4 and it worked great! thanks for the tool
You sir, are awesome. So easy. Always nerve racking rooting a new phone but this is cake. Took 5 minutes. A caveman could do it! Thank you!
great tool! worked very well! thanks!
Worked like a dream, thanks a lot!
Tool Updated...
CWM is now 1.0.3.5
Thanks. Success! Ive never seen odin in action, that was cool. Thanks for the easy instructions throughout the process. Very easy.
Sent from my SCH-I545 using Tapatalk 2
Thanks,m just had to trade my phone in due to manf. defect. This'll make re-rooting a lot easier!
Download link broken. Says file is corrupt.
Sent from my Galaxy Nexus using xda premium
USB Debug
New to Galaxy S4 where can I find USB Debug in setting? thx!
kevinniven said:
New to Galaxy S4 where can I find USB Debug in setting? thx!
Click to expand...
Click to collapse
To unlock the Dev Options menu, go to Settings -> About Device and scroll down to the "Build Number." Now, tap on your "Build Number" five times, and you should see a toast notification pop up saying "Developer mode has been enabled." Back out of the About Device menu and you'll see Dev Options back where it belongs, so you can turn on USB Debugging and whatever else you want to.
(taken from http://gs4.wonderhowto.com/how-to/enable-hidden-developer-options-your-samsung-galaxy-s4-0146687/)
Elvis_Marmaduke said:
Thanks,m just had to trade my phone in due to manf. defect. This'll make re-rooting a lot easier!
Click to expand...
Click to collapse
Just curious....what was the defect?
Tar file
All seems to be going ok but not seeing TAR file in Oden?
viceversa said:
Just curious....what was the defect?
Click to expand...
Click to collapse
It was a small thing in the top left corner of the screen, I could only see with the screen off. It looked like glue or a tiny hair under the glass. I was mostly just worried it was going to get worse over time. I didn't even notice it until I was putting a screen protector on (you know how impossible it is to get rid of all that dust). Free replacement through Verizon though because it's a defect.
Hi guys, I wanted to try this database system, so I'm expanding upon this thread: http://forum.xda-developers.com/showthread.php?t=2272066
Introduction
CASUAL will guide you through the process. Put your device into “Developer Mode>USB Debugging”. Click the do it button. If you experience a problem, PLEASE USE THE PASTEBIN button to post a log. Just press Ctrl+L then Pastebin and fill out the information.
Overview
You are expected to be STOCK.... Stock anything, but stock. If you are not stock and have a custom recovery, this will cause you to only be able to flash back to stock using Odin or Heimdall. Be stock. You will need to download and execute the CASUAL application below. Then click the Do It! button. You need Java. Do you have Java?. The exploit was developed by Elite Recognized Developer Ralekdev and packaged by AdamOutler.
note: if it fails, try turning everything off and back on, then run it again before posting for help.
Windows 32/64 Users: CASUAL will put your device into Download Mode. It will automatically flash everything. If drivers are required, jrloper's CADI (CASUAL Automated Driver installer) will handle it. Make sure you're connected to the internet.
Linux 32/64/raspberry pi Users There may be a permission escalation in order to install heimdall, either way sit back and relax. CASUAL automates the entire process.
Please run the following in a terminal first:
Code:
sudo apt-get install openjdk-7-jdk dpkg
Mac Users: Mac works easier than any other system at the time of this systems. Please report problems.
Download
CASUALnightly No You Verizon! Always use the highest revision with the latest date. To run CASUAL you need Java. Do you have Java?
For nightly builds click here: http://goo.im/devs/AdamOutler/VZWGalaxyNote2
Help and Troubleshooting
Are you having a problem? First check this post out for remedial troubleshooting. . If that doesn't fix it, then press CTRL+L, press the Pastebin button, come back here and press CTRL+V to paste your log. Don't hit the donate button, that doesn't fix it. Donate only if you feel it's worth donating to. Use CTRL+L and then hit Pastebin and paste the log here if you need help.
Jailbreak video for Windows users only!
This video desmonstrates CASUAL used with Odin to flash the Galaxy Note 2 firmware. Thanks to DroidModderX. While the video uses an old version the procedure is mostly the same.
Jailbreak video for LINUX only!
This video demonstrates the one-click CASUAL Linux Unlock method... at 2AM.. so don't expect me to be cheerful. While the video uses an old version, the procedure is mostly the same.
image
{
"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"
}
About CASUAL
CASUAL stands for Cross-platform ADB Scripting, Univeral Android Loader. CASUAL jar files are a wrapper for the CASUAL scripting language. CASUAL allows rapid and accurate deployment of hacks and exploits. At any time, if a serious problem is detected with any script, the kill-switch will be flipped and you will be brought to a support page (most likely here) so you can download the latest version. Otherwise for minor corrections, new CASUAL scripts can be deployed remotely.
Updates
CASUAL provides updates WAAAAY quicker than Verizon. As soon as I push an update to the Subversion repo it appears automatically in EVERY casual. See below for the change log.
31July13: initial release
XDA:DevDB Information
CASUAL- NO You Verizon, a Tool/Utility for the Verizon Samsung Galaxy Note II
Contributors
AdamOutler, jrloper, loglud
Version Information
Status: Testing
Current Beta Version: No You Veriz
Beta Release Date: 2013-07-31
Created 2013-07-31
Last Updated 2013-08-02
Very nice work
MY DIRTY LIL NOTE 2
couldnt get the latest nightly to fully load. recog device connection but the do it wouldnt work because the top of the app stayed on loading... please wait.
edit: diff build shows the top, but says disconnected on the bottom. fml
all the videos say to use windows 7. can it work with vista?
master0fursinz said:
all the videos say to use windows 7. can it work with vista?
Click to expand...
Click to collapse
yeah, it should work with Vista. @jrloper could tell you more if there are driver issues.
idkwhothatis123 said:
couldnt get the latest nightly to fully load. recog device connection but the do it wouldnt work because the top of the app stayed on loading... please wait.
edit: diff build shows the top, but says disconnected on the bottom. fml
Click to expand...
Click to collapse
I'm also having this problem. Any help Adam?
Edit: This is what you're looking for http://forum.xda-developers.com/showthread.php?t=2272066
Hi,
I'm currently running Windows 8.1 64 bit and my phone is the Samsung Galaxy Note II android version 4.1.2 stock, model SCH-i605, and baseband version i605vramc3. After downloaded the latest nightly build, the .jar file opened and gave the following error in the application:
There was a problem while excuting the command.
C:\Users\Zack\AppData\Local\Temp\CASUALZack-2013-12-26-17.09.35\adbexe devices
Then it repeated this same error every second or so infinitely until the application was closed. It did this whether the phone was connected, disconnected, in USB debugging mode, in download mode, etc. I have tried everything and I continually get this same error with the "Do It' button greyed out and disabled.
Next I downloaded the previous two builds, and I found that the December 13 build did not get this error and actually found my phone. However, after I clicked "Do It" and confirmed the warning, It rebooted my phone into download mode like it is supposed to. My phone then went into download mode like usual. However, the CASUAL program then said:
looking for download mode devices..........................................................
And kept on looking without ever finding my phone, and every minute or so it came up with a prompt asking why it can't find my device. I also found that my phone would not exit this download mode without doing a battery pull.
Next I retried the entire process with both builds using (a) 3 different USB cords, (b) 3 different computers running windows 8.0 and 7, and (c)every possible USB port on each computer. These options all gave the same exact results.
I have tried everything I can think of but it is not working! Has anyone encountered this problem before or do you have any proposed solutions?
Thanks so much!
Zack
Still can't figure it out.
http://pastebin.com/W3W1HwJi
I keep getting a libusb error -12 at the start and then it ends up failing.
Really need help here. Verizon was trying to force update me and I had to turn it off and go back to my old phone till I can get this done.
Thank you Adam!!
BrickeD?
Hi guys.
I am certain I followed all instructions to the letter, but I have ended up rendering my Note 2 pretty much useless. CAUSAL informed that the device would be started in android but then the next thing my phone displayed was:
"System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
Can I restore my device to the previous state?
thanks
Tried the second time around with CASUAL R570 and got error.
http://pastebin.com/Gpss6vtZ
UPDATE: Gave up hopes (for now) of rooting SCH-i605 running KitKat. Flashed stock rom and revived the device.
Spy26 said:
Tried the second time around with CASUAL R570 and got error.
http://pastebin.com/Gpss6vtZ
UPDATE: Gave up hopes (for now) of rooting SCH-i605 running KitKat. Flashed stock rom and revived the device.
Click to expand...
Click to collapse
There isn't a root method for ND7 4.4.2. for the i605. Also, the bootloader hasn't been able to be unlocked since MJ9 4.3.
mirror
Hosed my phone... infinite bootloop at sammy logo, couldn't get into recovery had to odin a stock image and start over... Had one hell of a time tracking down the casual jar file.
As of this moment the download link in this thread is bad.
the download link in THIS thread, now points to DevHost but the files are not the ~29MB jar file you expect. It is now a 3.5MB exe file that appears to be "shady as hell". All the other download decoy buttons at Dev-host take you to fake java update downloads and other seriously shady looking corners of the interweb.
Additionally goo.im is on holiday...
As such I have posted this temporary Mirror of the .jar file I had in my archives:
http://tweakedrom.com/Other_Files/Note_2.php
(The jar file MD5 appears to be the same as one the developer posted to Dev-Host.)
Outler, if you want me to take this mirror down just let me know.
Cannot find the download to casual sch-i605. All download links I can find lead to nowhere.
mjmplus said:
Cannot find the download to casual sch-i605. All download links I can find lead to nowhere.
Click to expand...
Click to collapse
Well you could go to his very own YouTube video and use the links there
I tested on LG G2 Korea Version F320S, F320L, F320K
- Why bootloop?: Some people Update OTA after flash CWM or TWRP so it will be bootloop. Or some strange reasons
- What should we do when we can not flash Stock firmware by FlashTool.1.0.54?
Let do follow this guide:
- Download file:
Flashtool V1.5 --> http://www.fshare.vn/file/TNVQZ9N74T ( tks to GSM Hosting forum )
Crack Flashtool : http://www.fshare.vn/file/TS1SGGVYWT ( tks to GSM hosting Forum )
File .TOT firmware :
F320S ->>> http://www.fshare.vn/file/T3SZR52W6T
F320K ->>> http://www.fshare.vn/file/TZRVMVMPFT
F320L V11c -->>> http://www.fshare.vn/file/TVR9DPAC7T
.dll file F320S/L/K >----- http://www.fshare.vn/file/TKW8J7QPQT
Driver: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
- Let do:
Step1: Install Flashtool V1.5. Default install folder C:\LG\LGFlashtool
Copy crack file Megalock.dll to C:\LG\LgFlashtool
Step2: Enter download mode: Turnoff, push vol+ and plug USB cable in
Open Device Manager on your computer and choose COM41 for phone connection:
{
"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"
}
Step3: Open Flashtool, choose .dll and .tot file, then fresh yellow icon like this:
Step4: When Flashtool show Realdy, push USB out for 5secs and plug in again. Flash tool will automatic run
Step5: Wait for finishing:
Read more: http://choimobile.vn/threads/huong-dan-cuu-soft-brick-lg-g2-f320s-l-k.12932/#ixzz2h8Fy9fJB
Suggest you read the rules for XDA no warez allowed, CRACKED SOFTWARE = WAREZ!
fma965 said:
Suggest you read the rules for XDA no warez allowed, CRACKED SOFTWARE = WAREZ!
Click to expand...
Click to collapse
This is extremely useful, please blackout offending list and leave the post alone.
JoeTF said:
This is extremely useful, please blackout offending list and leave the post alone.
Click to expand...
Click to collapse
As a RC i can't do that.
Even though it is cracked, we don't see it as "warez". Almost every device has it cracked, so noone would be able to use it if we wouldn't allow it.
I mean, we also "crack" the bootloader of devices, which would be considered as warez, too, in that case
Cheers
laufersteppenwolf said:
Even though it is cracked, we don't see it as "warez". Almost every device has it cracked, so noone would be able to use it if we wouldn't allow it.
I mean, we also "crack" the bootloader of devices, which would be considered as warez, too, in that case
Cheers
Click to expand...
Click to collapse
hmm i guess, the way it was worded seems like you were cracking software tbh. my bad
fma965 said:
hmm i guess, the way it was worded seems like you were cracking software tbh. my bad
Click to expand...
Click to collapse
oops, may be a bit unluckily worded... the first "we" was meant as the mod staff, and the 2nd "we" as xda in general
laufersteppenwolf said:
oops, may be a bit unluckily worded... the first "we" was meant as the mod staff, and the 2nd "we" as xda in general
Click to expand...
Click to collapse
sorry, yeah i meant the OP not your reply
fma965 said:
sorry, yeah i meant the OP not your reply
Click to expand...
Click to collapse
Good post. Please leave this post coz I am also the lucky guy can get repair my bricked G2 using this usefuly TOT recovery method.
If possible, remind to set back correct version number (F320 L / K / S) in build info. which match with your IMEI#.
dokyson said:
I tested on LG G2 Korea Version F320S, F320L, F320K
- Why bootloop?: Some people Update OTA after flash CWM or TWRP so it will be bootloop. Or some strange reasons
- What should we do when we can not flash Stock firmware by FlashTool.1.0.54?
Let do follow this guide:
- Download file:
Flashtool V1.5 --> http://www.fshare.vn/file/TNVQZ9N74T ( tks to GSM Hosting forum )
Crack Flashtool : http://www.fshare.vn/file/TS1SGGVYWT ( tks to GSM hosting Forum )
File .TOT firmware :
F320S ->>> http://www.fshare.vn/file/T3SZR52W6T
F320K ->>> http://www.fshare.vn/file/TZRVMVMPFT
F320L V11c -->>> http://www.fshare.vn/file/TVR9DPAC7T
.dll file F320S/L/K >----- http://www.fshare.vn/file/TKW8J7QPQT
Driver: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
- Let do:
Step1: Install Flashtool V1.5. Default install folder C:\LG\LGFlashtool
Copy crack file Megalock.dll to C:\LG\LgFlashtool
Step2: Enter download mode: Turnoff, push vol+ and plug USB cable in
Open Device Manager on your computer and choose COM41 for phone connection:
Read more: http://choimobile.vn/threads/huong-dan-cuu-soft-brick-lg-g2-f320s-l-k.12932/#ixzz2h8Fy9fJB
Click to expand...
Click to collapse
can't eneter in download mode i am stuck!!! help!!!
can someone give me the files for my D80210a
Stuck
Every time I try to press vol.up and plug in I still load right into twrp
ocarlty said:
Every time I try to press vol.up and plug in I still load right into twrp
Click to expand...
Click to collapse
I have the same problem with the CWM.
when i press the yellow arrow it gives me this error
i press ok and it continues to the step i have to reconnect the phone.
i reconnect it and i get this
i have changed the com number
i don't know what is the problem...
taxexpert said:
I have the same problem with the CWM.
Click to expand...
Click to collapse
Me too. Ever get this figured out?
I think what this boils down to is USB debugging was disabled by the factory reset. I had reset my device to prepare to sell it. When it booted back up I got an OTA offer and, not thinking, I accepted it. However, I still had CWR and root. I think OTA'S require stock recovery to work properly. So, no USB debugging and CWR as the recovery = soft brick. And, since CWR does not have a terminal option, there's no way to enter commands. I'm thinking this is going to be a warranty claim for me.
Will it work to restore a D805?
dokyson said:
I tested on LG G2 Korea Version F320S, F320L, F320K
- Why bootloop?: Some people Update OTA after flash CWM or TWRP so it will be bootloop. Or some strange reasons
- What should we do when we can not flash Stock firmware by FlashTool.1.0.54?
...
Click to expand...
Click to collapse
Hi!
Thank you for this n.n
Will it work to restore a D805? If not, then I better be careful with OTAs, or I better don't use any recovery as I'm not going to
flash any custom ROM till the G2 is done with official updates (2015?).
Thanks again n.n
- L.
I get this problem any help would be appreciated. thanks.
Could someone give another link on file for F320S > LGF320SAT-00-V10e-SKT-KR-JUL-29-20130
Becuse I have tried to download it by link in the topic. It takes me more than 8 hour, but file was corrupted (2.3 GB not 2.5 GB).
Please - I need TOT for F320
Sorry, if I interrupt here. I'm very new to forum.
My LG G2 F320S having Boot Loop after i updated on 4th Jan 2014.
I try to get TOT file for - 320S ->>> Given location But it seems not working. (I meant not downloading. I tried several days).
If anybody having it please please share with me.
Thanks Lot.
LK
Weird issue
Hi All,
tried using flashtool but I get the error that I need to check my phone model or the DLL.
I bought this phone from the Philippines with model number LG D802. I had flashed other roms for this with D802.
But when I was trying a while ago since I got a bootloop issue, the phone's downlaod mode is in korean and says in the phone and flashtool that my phone is running F320K? but it's so weird since I had D802 before even in the IMEI sticker in the back and to think I installed rayglobe ROM, before having the boot loop.
Any help would be appreciated.
THanks!
Nexus 5 Multi-Tool
{
"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"
}
me and kwongger are putting together a new tool, its one of the first that supports windows/linux/mac AND ANDROID! thats right, the tool can be used on your device!
FEATURES
Unlock bootloader
Install CWM
Install TWRP
Add root permissions
Add build.prop tweaks
Backup device
Flash a custom recovery
Flash a custom kernel
Revert device to stock out-of-box state
Pull device information
Install drivers
Find custom kernels, recoveries and roms
Click to expand...
Click to collapse
Due to my cousin having this device(not me) i would appreciate someone to help me with testing new features?
DOWNLOAD LINK
INSTRUCTIONS ARE SIMPLE
All activities take place with the device on and you will endup back with the device on.
Download
Extract
Run Tool.exe as administrator
Install device drivers(included)
Click to expand...
Click to collapse
FAQ
Q. After trying to revert to stock state(out of the box) my device is stuck in a bootloop?
A. Boot into recovery, wipe data/factory reset. Your prayers have beey answered
Q. After the tool flashes recovery, it doesnt seem to stick. why?
A. This is not an error with the tool or recovery, its just.. a nexus thing...
Flash it a few more times and eventually it will stick!
Q. Why is the file only 1.5 MB?
A. All files are stored on server and pulled only when needed with a utility
Q. Will the tool download all the files everytime i wanna perform an option?
A. No. it downloads the file once and detects that its already there the second time.
Q. Is this tool worth my time?
A. Who would think a 10 minute toolkit could hit the portal?
Q. Are the drivers included?
A. Yes but no. the application downloads the drivers only if you want to install them via my tool
Q. Who's yo daddy?
A. Idk, son.
Click to expand...
Click to collapse
CHANGELOG
3.0
Added CWM
Updated TWRP
Added "Where to find custom..." in flash options
2.4
Fixed menu error
Changed file type to executable
Added logo
Added root options menu
Changed root method
All processes are now verbal
No wait-for-device command
2.0
All files stored on server
Cut the tool size down to 1.5 MB
Added restore to stock state
Added install drivers+guide
Added get device info
Fixed minor error
1.0
Initial release
Click to expand...
Click to collapse
Credits
Chainfire
PlayfulGod
Cwm
Twrp
Click to expand...
Click to collapse
NOTE: what you do with this tool is your responsibility, use it at you own risk.
Hello,
Good work!
Published on HTCMania :good:
http://www.htcmania.com/showthread.php?t=711894
David_Vaz said:
Hello,
Good work!
Published on HTCMania :good:
http://www.htcmania.com/showthread.php?t=711894
Click to expand...
Click to collapse
Thanks
You show it as note 3 multi tool, need to change that
jd1639 said:
You show it as note 3 multi tool, need to change that
Click to expand...
Click to collapse
whopps will fix that now
Used the tool - now phone will not restart. It is stuck on the four colours that move about. Has been stuck on this now for about 5 minutes.
Any suggestions? I am able to get into twrp recovery no problems.
Ian
irhut said:
Used the tool - now phone will not restart. It is stuck on the four colours that move about. Has been stuck on this now for about 5 minutes.
Any suggestions? I am able to get into twrp recovery no problems.
Ian
Click to expand...
Click to collapse
You will have to Restore your phone.
My kit will have recovery functions monday.
http://forum.xda-developers.com/showthread.php?t=2508817
irhut said:
Used the tool - now phone will not restart. It is stuck on the four colours that move about. Has been stuck on this now for about 5 minutes.
Any suggestions? I am able to get into twrp recovery no problems.
Ild.pro
Ian
Click to expand...
Click to collapse
what function did you use?
Kwongger said:
You will have to Restore your phone.
My kit will have recovery functions monday.
http://forum.xda-developers.com/showthread.php?t=2508817
Click to expand...
Click to collapse
Also no he doesnt, the only thing that could cause this is the build.prop tweaks, whitch can be reverted by pushing the backup back to /system/ Aldo mine will Also include restore options soon
What tweaks are in this?
Sent from my Nexus 4 using Tapatalk
crackmulah said:
What tweaks are in this?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Battery saving deepsleep quickbook scrolling enhancement better touch responde better jpeg quality better picture quality better internet and connection speed, googles sms Server and overall smootheness
Does this tool install the official TWRP release for the N5?
ricky310711 said:
Battery saving deepsleep quickbook scrolling enhancement better touch responde better jpeg quality better picture quality better internet and connection speed, googles sms Server and overall smootheness
Click to expand...
Click to collapse
That's quite something to say, better all these things for a new device and software.
Sent from my Nexus 4 using xda app-developers app
Synyster06Gates said:
Does this tool install the official TWRP release for the N5?
Click to expand...
Click to collapse
Yes!
also people reading the article on the portal, the tool does not use fast flash commands, it uses the dd method for those flashes, when i add kernel flashing and backing up your device as .img files then i will be adding fastboot flash commands, so yes, the flashes occur when your device is booted!
Can I ask what version of TWRP is installed, is it the latest?
ItzMar said:
Can I ask what version of TWRP is installed, is it the latest?
Click to expand...
Click to collapse
there is only one version of TWRP compiled for the N5 and yes its the latest! update coming soon!
Ok thanks man. Can I also ask where to find the device drivers?
ItzMar said:
Ok thanks man. Can I also ask where to find the device drivers?
Click to expand...
Click to collapse
i am almost finished updating the tool i will include it in the next update!! but you could more then likely find them in the general section!
ok cheers, no problem. Will wait for the new version to be up, no rush. Thanks for your commitment to provide a tool for us noobs/lazy people!
Would you recommend running your tool before first boot?
Just a few questions: when there is <waiting for device> for 5 minutes, that seems like my drivers are wrong? It was possible to unlock, but not to install a recovery, so i am trying to update my drivers...
And can i run the tool and select unlock, install recovery and root even when my device is already unlocked?
This is the stock Rom of N & M for Yoga Book LTE & WIFI for the needers
if any dev want to help me developing a dual boot for Yoga Book, just PM me or join Telegram Group for Yoga Book devs and users:
MOD EDIT: LINK REMOVED
Prees the Thanks button if that helps you
How to install it:
Be careful, these steps will erase all your data on tablet and will downgrade rom (stock marshmallow)
First of all: read and understand all of the instructions.
1. Download the stock ROM
https://cloud.kolyandex.su/index.php/s/4WDt6ghOzHAyP4s (Nougat WiFi version)
https://easy-firmware.com/home/browse/category/id/19521/ (Marshmallo LTE version)
https://androidfilehost.com/?fid=817550096634799507 (Marshmallo WiFi version)
2. Extract it to some folder
3. Download Intel Platform Tool Lite from here: https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
4. Install Intel Platform Tool Lite
4. Boot into fastboot mode
5. Run Intel Platform Tool Lite
6. Make sure your tablet is recognized by the tool (otherwise you need to enable USB-debug in Developer settings)
7. Select "flash_update_from_eng.json" from folder in (2)
8. Push "start to flash"
9. Wait... (You should check tablet's screen in order to lock/unlock bootloader (it should be locked after flash in order to install OTA updates))
10. Reboot tablet
11. Your keyboard might not work: that is normal (just use on-screen keyboard for now)
12. After initial setup: open Contacts app, create new one (if there are no contacts yet), tap search and enter ####6020#
13. Choose your region
14. Reboot
15. Setup again (now halo should work)
16. Go into settings -> about -> updates and update till the last version (may take several hours)
17. Say thanks for alexjustes for his Amazing Steps
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
beltani said:
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
Click to expand...
Click to collapse
Unfort. no, because i dont have a YB Android Version, i have win ver.
THE MAXIMUM POWER said:
Unfort. no, because i dont have a YB Android Version, i have win ver.
Click to expand...
Click to collapse
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
beltani said:
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
Click to expand...
Click to collapse
Same, it can only flashed through fastboot mode
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
{
"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"
}
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
@MarkAllen, thank you for your valuable information. This will help people unbrick their devices.
MarkAllen said:
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
Click to expand...
Click to collapse
Thank You for the INFOS
The tool does not recognized my device
Please help to flash my yoga book.
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
jeitana said:
Please help to flash my yoga book.
Click to expand...
Click to collapse
Try installing Android SDK drivers in you PC
Guys, if anyone faced a Probleme during his way to flash the ROM, PLZ tell me the problems with More Details
_Deeb0_ said:
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
Click to expand...
Click to collapse
Is this compatible with the Yoga Book A12?
I have been away for a while. Why should I want to install this rom?
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Shawnki91 said:
Is this compatible with the Yoga Book A12?
Click to expand...
Click to collapse
Sorry but no
hajkan said:
I have been away for a while. Why should I want to install this rom?
Click to expand...
Click to collapse
No Need to reinstall this Rom if you have already your System, both are 100 % same
hajkan said:
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Click to expand...
Click to collapse
Reinstall the Rom will fix this, but doing factory reset will fix this too
In case anyone wants the wifi only M firmware here it is https://androidfilehost.com/?fid=817550096634799507