How to unlock bootloader on Note 2 - Galaxy Note II Q&A, Help & Troubleshooting

How to unlock bootloader on Note 2 - Galaxy Note II Q&A, Help & Troubleshooting

Hi there,
This may seem like a daft question but i have just rooted my Note 2 using Odin and i went ahead and installed CWM from the play store.
However, i don't seem to have the option of making a backup of my current ROM.
All it gives me is (in blue)
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache.
This worked on my HTC One X, am i doing something wrong? My Note 2 was purchased as SIM free from phones4u.
I'm on android version 4.1.2, baseband version N7100XXDLK7, BUILD NO. JZO54K.N7100XXDMB2., MODEL NO. GT-N7100.
Could my bootloader still be locked? Is this causing the issue?
Any help would be much appreciated!

Just flash CWM/TWRP recovery.
Here is one of it
http://forum.xda-developers.com/showthread.php?t=2028103

Loading default android recovery even though TWRP successfully installed
Hi,
I am not sure if I should've started a separate thread for this, please move this if this has to be a separate thread but I've mentioned below why I am posting here.
My phone Galaxy note 2 International version GSM is rooted and I installed TWRP through Goomanager and I got a message stating that "Recovery was successfully installed". After this I shut down the phone and pressed Volume up + Home + Power to go into recovery mode and it still goes into the Android default recovery mode. I tried installing it again and still faced the same issue.
Since I was having a problem, I thought I will install TWRP through Odim 3.7. So, I connect PC to my phone and downloaded the openrecovery-twrp-2.3.1.1-n7100.img.tar.md5 and opened Odim in administrator mode and clicked on PDA >> Start. Within a second I got an error stating "odin downloader has stopped working". I went to task manager and shut down Samsung KIES and tried again but still got the same error.
Next, I tried using the Samsung Note 2 Toolkit. Before I installed TWRP through option 5 in the toolkit, I wanted to Rename Recovery Restore files (if present) as suggested by the toolkit. When I chose this option, I get an error stating adbd cannot run as root in production builds. When I googled this error, it went to a post which said that the bootloader needs to be unlocked.
But then the previous post says that I need TWRP for unlocking the bootloader and I'm doing all this to first of all install TWRP.
Apart from this, as additional Info, when I open ROM Manager - Under Recovery Setup - Current Recovery is Team Win Recovery Project. When I choose to reboot in Recovery mode from the application, it goes to the Android System Recovery. No matter what I do, TWRP recovery just does not seem to open up.
I'm pretty clueless now as to what other options I have or if I have messed up somewhere
Any suggestions would be appreciated.
Thank you

its already unlocked :good:
all u need costume recovery ( TWRP or CWM )
TWRP is far better IMO
http://forum.xda-developers.com/showthread.php?t=1938733

yahyoh said:
its already unlocked :good:
all u need costume recovery ( TWRP or CWM )
TWRP is far better IMO
http://forum.xda-developers.com/showthread.php?t=1938733
Click to expand...
Click to collapse
Hi yahyoh -
The problem as I've described in my post is that I am unable to go into TWRP Recovery mode, I've installed the scripts using goomanager several times but when I shut down the phone and press volume up + Home + Power, it goes to Android Recovery mode and not the TWRP Recovery mode.

gr8one said:
Hi yahyoh -
The problem as I've described in my post is that I am unable to go into TWRP Recovery mode, I've installed the scripts using goomanager several times but when I shut down the phone and press volume up + Home + Power, it goes to Android Recovery mode and not the TWRP Recovery mode.
Click to expand...
Click to collapse
ok forgot goomanager it never worked for me
just download the tar version open odin put it in PDA put ur note 2 in download mode and connect it to ur pc wait for the blue color to show on ID:COM and press start
{
"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"
}
( and make sure kies is fully closed )

Tried that
yahyoh said:
ok forgot goomanager it never worked for me
just download the tar version open odin put it in PDA put ur note 2 in download mode and connect it to ur pc wait for the blue color to show on ID:COM and press start
( and make sure kies is fully closed )
Click to expand...
Click to collapse
Yahyoh,
Thank you for your response but if you see my original post, I have mentioned that I had already tried Odin 3.7 and put my phone in download mode and got the blue color showing ID: COM but when I pressed start, Odin gave an error stating odin downloader has stopped working and the only dialog box was to close. So, once I press START, I get a error message in a second and have to shut down. I did make sure that I have the correct tar version as I downloaded from TWRP's website directly for N7100. I did make sure that Kies was also closed.
After this I tried using Toolkit and that didn't help as well. Kinda going crazy why such a simple thing is getting to become a irritating problem, been sitting on this for the past 4 hours.

try to run odin as administrator

ran odin as administrator
yahyoh said:
try to run odin as administrator
Click to expand...
Click to collapse
Yes. I did run odin as administrator all the time.

try on another PC ? try to download odin again ? try another cable ?

yahyoh said:
try on another PC ? try to download odin again ? try another cable ?
Click to expand...
Click to collapse
I have tried downloading odin 4 or 5 times. The cable I have is brand new samsung cable. Right now, I dont have another pc but might have to go to a friends and try if that helps. I do have a mac but not sure if there is mac version of odin. I'm attaching a picture of what I see when I press volume up + home+power.

abhijitdroid said:
Hi,
1. Check that USB drivers are properly installed.
2. Your USB cable is proper and allows you to charge your phone as well as copy data from your PC.
3. Change USB port and try again. (This has worked in my case)
Click to expand...
Click to collapse
Usb drivers are installed properly. PC reads the phone as soon as itd connected. Tried three different usb ports that is available in my laptop. The phone does get charged when it's connected and I'm able to transfer data. Only thing left to try is a different pc.

Since ur already rooted, y not flash via mobile odin app? Untar to internal storage and rename the twrp image to recovery.img (btw theres a newer v2.5.0.2) and let mobile odin look for it.
Or u can dump the image directly to ur recovery partition using terminal apps:
Code:
su;
dd if=/storage/sdcard0/recovery.img of=/dev/block/mmcblk0p9 bs=4096;
sleep 5;
reboot;

Nazar78 said:
Since ur already rooted, y not flash via mobile odin app? Untar to internal storage and rename the twrp image to recovery.img (btw theres a newer v2.5.0.2) and let mobile odin look for it.
Or u can dump the image directly to ur recovery partition using terminal apps:
Code:
su;
dd if=/storage/sdcard0/recovery.img of=/dev/block/mmcblk0p9 bs=4096;
sleep 5;
reboot;
Click to expand...
Click to collapse
Hi Nazar78,
Mobile odin app is not free, it needs to be purchased. I already have the twrp image in the internal storage and was looking around if there was a free version of mobile odin app somewhere but couldn't find it.
I do not know how to use terminal apps and not familiar with the commands etc. So didn't wanna try that and mess it up. As a temporary solution I have installed CWM latest version using Rom manager but TWRP would be much better as it seems to be more user friendly.
If you could tell me how to enter this terminal apps page, I will probably follow the codes you have given and see if that helps.
Thanks

just install Android Terminal : https://play.google.com/store/apps/...251bGwsMSwxLDEsImphY2twYWwuYW5kcm9pZHRlcm0iXQ..
then type via keyboard what @Nazar78 wrote in the terminal

Just download any free terminal emulator app from play store and enter those commands per line each.
Btw u mentioned previously about adbd can't run on prod builds, its because the adbd binary in ur rom is stock, u need a patched one. Look for app called adbd insecure by CF. Or any custom builds should do the trick...

To flash recovery, tou need not to have paid version of mobile odin
Wait updating this post with link
Edit : here is mobile odin lite
http://forum.xda-developers.com/showthread.php?t=1347899
Download attached mobile odin lite from post 1
Then download flasher kernel from post 7
(download 5.0 versiin) and install
Then open mobile odin Select recovery tab, point to recovery file (tar/img) and flash
Sent from my GT-N7100 using xda premium

Thank you
Thanks Nazar78, Yahoyoh and Ketan, It's about 1:30am now, so I'm gonna shut down now and try these tomorrow. WIll get back with updates. Appreciate.

Also if you have installed EMET, a Microsoft software to stop security exploits, disable it.
It's cause me issues in the past.

I've also seen reports of people not having odin running properly when the kies process runs in the background. This was always the case when flashing with the Galaxy s, and might be a rare occurance with the note 2 too.
Sent from my GT-N7100 using Tapatalk 2

Related

[HOWTO] ROOT, Install ClockworkMod Touch Recovery & get into Download Mode for newbie

[HOWTO] ROOT, Install ClockworkMod Touch Recovery & get into Download Mode for newbie
this is so easy, you wont believe it...
ROOTing the phone the easy way!
if you want to remain absolutely stock with ROOT power you can use this [REF] ROOT via Superoneclick
Installing ClockworkMod Recovery
Prerequisites:
get CWRecovery.tar from here
get Odin 1.85 from here
launch Odin from your PC
flash recovery.tar as PDA in Odin
when completed Odin will reboot your phone
turn the phone off again
remove the USB cable
use left hand thumb to hold on down vol+ & vol- and hit the power button
you've got ClockworkMod Recovery working!
Prerequisites:
T989 must be rooted already
Download ClockworkMod ROM Manager https://market.android.com/details?id=com.koushikdutta.rommanager
Download Touch Recovery for Samsung T-Mobile GalaxyS2 from ClockworkMod ROM Manager
recovery-clockwork-touch-5.8.1.3-hercules.zip
md5 checksum = 7b7d034bccefd9d0f08e7f282619c183
run ROM Manager from the Apps Drawer
grant super user permission to ROM Manager
select Flash ClockworkMod Recovery
you'll be prompted to select the phone model, choose Samsung T-Mobile GalaxyS2
it take a few seconds or minutes to download and install Recovery to your phone
you might get prompted to grant super user permission to ROM Manager again
click OK on the successful message
(optional) Upgrade to Touch Recovery
reboot into Recovery
select mounts and storage
select mount USB storage
then drag and drop the file recovery-clockwork-touch-5.8.1.3-hercules.zip from your PC to your phone
when the file is done copying, back on the phone side select Unmount from the Recovery menu
select Go Back
select install zip from sdcard
select choose zip from sdcard
select recovery-clockwork-touch-5.8.1.3-hercules.zip
select yes to install recovery touch
done!, enjoy the new touch recovery
Download Mode
You wont be needing unless you want to return the phone completely back to stock, or if you screw-up so badly that CWR no longer works for you this is a good safety net to go back to stock.
Prerequisites:
Get and Install the USB drivers directly from Samsung website http://www.samsung.com/us/support/downloads/SGH-T989ZKBTMB
click on "Software" tab
select the one listed as "Device(Install),Tethering (Software)"
turn off the phone
wait for the green battery to show up
use left hand thumb to hold on down vol+ & vol-
NOTE: Telus SGH-T989D only requires vol-
plug in USB cable
wait until it shows the Warning!! 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"
}
then hit vol up to confirm, then it'll let you continue into the Download Mode
NOTE: you can exit the Download mode screen by holding power button for 10 sec
To Odin the phone back to stock
Download Odin (if you don't already have a copy already)
Download a stock ROM matching your phone model listed in the INDEX page http://forum.xda-developers.com/showthread.php?t=1324517
boot into Download Mode as shown above
then flash the stock ROM using Odin

or just hold vol up n vol down and plug usb cable, thats much easier than your method and faster

joselarajan87 said:
or just hold vol up n vol down and plug usb cable, thats much easier than your method and faster
Click to expand...
Click to collapse
confirmed, it's easier to get download mode

For us Telus guys its VOL DOWN and USB cable inserted.

firebane said:
For us Telus guys its VOL DOWN and USB cable inserted.
Click to expand...
Click to collapse
thanks for the reminder

is the rom above the good one for telus users im from montreal
the rom is the one for t-mobile thats why i am asking
and to boot in download mode from phone turned off
I press the vol down + power + usb ????
i dont get the wait for the green battery
thanks guys

how can i get to recovery mode without the USB cable? thanks

use left hand thumb to hold on down vol+ & vol- and hit the power button

hey allGamer, do you have a copy of the original Telus backup that you can upload somewhere. I did not back mine up i totally forgot i was too excited

it's already listed in the DEV section, you can't miss it
it's one of the top 10~15 topics

if you are talking about this http://forum.xda-developers.com/showthread.php?t=1312736 thats the T-mobile version. I cant find the Telus version

So from a powered off state, we hold vol - and then plug in the USB cable and it will boot up? :O
I'm confused with all of the T-Mobile root discussions and Telus root discussions.. How do you root the phone? Do you root through Odin, or do you just use Odin to flash the recovery (same for Telus and T-Mobile?) and then use the recovery to flash SU?

skadude66 said:
So from a powered off state, we hold vol - and then plug in the USB cable and it will boot up? :O
I'm confused with all of the T-Mobile root discussions and Telus root discussions.. How do you root the phone? Do you root through Odin, or do you just use Odin to flash the recovery (same for Telus and T-Mobile?) and then use the recovery to flash SU?
Click to expand...
Click to collapse
Yes. The Telus version is slightly different than the T-Mobile version in the sense that in order to get into download mode VOL DOWN is to be held only when inserting the USB cable otherwise you get a battery screen or windows complaining USB Device Not Recognized.

they explaine the process in this discussion the rom again is t-mobile
http://forum.xda-developers.com/showthread.php?t=1312736

firebane said:
Yes. The Telus version is slightly different than the T-Mobile version in the sense that in order to get into download mode VOL DOWN is to be held only when inserting the USB cable otherwise you get a battery screen or windows complaining USB Device Not Recognized.
Click to expand...
Click to collapse
Probably going to try this tonight. Do you know if the T-Mobile drivers that |Melvin| posted in the How-To Root T-Mobile GS2 are the same as the Telus ones? Or do I even need them? Because I know when I first plugged in my phone into Kies, it installed drivers.

skadude66 said:
Probably going to try this tonight. Do you know if the T-Mobile drivers that |Melvin| posted in the How-To Root T-Mobile GS2 are the same as the Telus ones? Or do I even need them? Because I know when I first plugged in my phone into Kies, it installed drivers.
Click to expand...
Click to collapse
I "think" the ones Melvin provides are the same ones you get with Kies. When you install Kies there is a directory it creates which has the USB drivers .exe file in it. If you have installed Kies your drivers are installed.

firebane said:
I "think" the ones Melvin provides are the same ones you get with Kies. When you install Kies there is a directory it creates which has the USB drivers .exe file in it. If you have installed Kies your drivers are installed.
Click to expand...
Click to collapse
Okay, thanks! I'm going to try this tonight and see how it goes

there is a topic linked in the index with the drivers download http://forum.xda-developers.com/showthread.php?t=1307478

just rooted my phone
and how to get back 4g network with telus ????
thanks

Following the instructions to a "T", when I I install the ROM and get to the "Setting Permissions" part of the install, the screen goes dark and reboots.
1- The ODIN flashing of Recovery.tar was successful
2 - Formatted the SD Card before copying the ROM onto it
3 - I ran the Fix Permissions
4 - Flashed ROM
5 - Phone reboots at "Setting Permissions"
6 - I repeated the procedure again and I get setting permissions error at the same point
When I access through ADB I am unable to set write permissions to /system among others but I can read. When I run #mount I get RO's for the following:
rootfs / rootfs ro,relatime 0 0
/dev/block/mmcblk0p24 /system ext4 ro,relatime,barrier=0,data=ordered 0 0 (& all directories under /system)
/mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000
Any ideas on what to do next?

[Q] Bootloop issue - need help.

This is my first thread as a user, I have been a lurker for very long time. I have decent understanding of flashing roms on HTC one X and HP touchpad, everything learned from XDA. But I have been facing this weird issue on Unlocked Rogers Galaxy note 2.
My galaxy note 2 was all stock and few days ago when I picked it up while it was charging, phone was hanging on main screen. I simply turned off and since then its stuck in bootloop. I am only getting samsung logo screen. So far everything I have tried, it hasnt resolved the issue.
I have flashed rogers stock 4.1.2 rom from samsung-updates using ODIN, but still its stuck in bootloop. I have tried multiple recoveries Stock, Clockwork and TWRP, phone mostly reboots when I try to do a factory reset. even when I am able to complete factory reset, nothing changes. All recoveries give me errors in line of unable to mount /cache and unable to mount /data.
Right now I have flashed TWRP and it shows unable to mount /cache, and it reboots when I try to do a factory reset.
These are the exact errors
E: unable to mount "cache"
E: can't mount '/cache/recovery/command'
E: can't open '/cache/recovery/command'
E: can't mount '/cache/recovery/log'
E: can't open '/cache/recovery/log'
E: can't mount '/cache/recovery/last_log'
E: can't open '/cache/recovery/last_log'
E: can't mount '/cache/recover/last_install'
E: can't open '/cache/recover/last_install'
Please help.
If nothing else works, can anyone show me a way to hard brick? So I can send in for warranty, coz download mode shows the binary counter?
Thanks

Hi, sounds like you either have a corrupted partition on your phone or a hardware issue. I have had lots of bootloops in the past and was always been able to fix it with flashing stock software with odin. You probily going to send it in for warranrt repair.
Sent from my SGH-I317M using XDA Premium HD app

pterry30 said:
Hi, sounds like you either have a corrupted partition on your phone or a hardware issue. I have had lots of bootloops in the past and was always been able to fix it with flashing stock software with odin. You probily going to send it in for warranrt repair.
Sent from my SGH-I317M using XDA Premium HD app
Click to expand...
Click to collapse
Is there any fix for corrupted partition on note 2? I have seen threads regarding s3 but not note2.
Also if I flash Mr robinsons rom from here
http://forum.xda-developers.com/showthread.php?t=2004650
it should reset the flash counter to 0, So I can send it in for repair.

I believe to fix a bad partition you need the pit file. I think it is in the stock firmware. I have never had a issue where I could not do a factory wipe/reset. You need triangle away app from the play to reset counter. You need to be on stock software, stock recovery, stock kernel but be rooted to use triangle away
Sent from my SGH-I747 using XDA Premium HD app
---------- Post added at 08:20 AM ---------- Previous post was at 08:16 AM ----------
Your issue is most likely hardware related because you were on stock software when you started having problems and you had not flashed any others software and you flashed stock software through odin and did not fix your problems
Sent from my SGH-I747 using XDA Premium HD app

I'd say try flashing a new kernel, and doing a factory reset
Edit...I re read op, and I think pit file also...
Sent from my SGH-I317M using xda premium

If that doesn't work I would definitely try flashing the pit file with the stock firmware in Odin.
Sent from my GT-N7105 using Tapatalk 2

cdshepherd said:
If that doesn't work I would definitely try flashing the pit file with the stock firmware in Odin.
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
sorry for the late reply, had to leave country for few weeks. So I tried to flash stock rom (redownloaded 4.1.1 from samfirmware) again through ODIN, and its still stuck in bootloop. when I boot into stock recovery after flashing stock rom, I get "E:failed to verify whole file signature, E:signature verification failed."

Format sd card then install latest stock rom with pit file ..it wil help u

nabilsweet007 said:
Format sd card then install latest stock rom with pit file ..it wil help u
Click to expand...
Click to collapse
I havent been able to find the pit file for note 2 i317m at all. If you have links, please share.

Anyone?
prince_f_swords said:
I havent been able to find the pit file for note 2 i317m at all. If you have links, please share.
Click to expand...
Click to collapse
Bump, anyone with pit file or a way to repartition?

Pm for pit

Thanks for the pit file, but Odin gets stuck at "Get pit file for mapping". Any ideas?

Are you putting it in the pit slot in odin?

twanskys204 said:
Are you putting it in the pit slot in odin?
Click to expand...
Click to collapse
yes, here's a screenshot.
{
"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 know you are having bootloop issues and im not an expert by any means. However, should repartition be checked? I know typically under odin you never want that box checked but maybe in this instance you do.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app

cloudraker said:
I know you are having bootloop issues and im not an expert by any means. However, should repartition be checked? I know typically under odin you never want that box checked but maybe in this instance you do.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Click to expand...
Click to collapse
well I am trying to repartition it by using pit file, as I think the errors in CWM are indicating that partition is messed up.

Ok so you have boot loops check it out,
here is list of what to grab odin version here
http://forum.xda-developers.com/showpost.php?p=33854395&postcount=2
follow those direction just insert your stock instead of cf auto root tar md5
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached Odin3-vX.X.zip file
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done
go to next post and grab cf auto root for i317m, IF your going to attempt to reboot
grab zip fro stock build http://www.hotfile.com/dl/180165074/47da708/I317MVLALJ2_I317MOYAALJ2_RWC.zip.html
and un zip with 7zip
place in odin pda slot as the directions from chainfire's post, remove sd if installed and continue.
when finished let reboot and it will hang on boot ani. pull battery, go into stock recovery and format cache and factory reset, then reboot.
you should be good to go at that point. if not pm me.

riassan said:
Ok so you have boot loops check it out,
here is list of what to grab odin version here
http://forum.xda-developers.com/showpost.php?p=33854395&postcount=2
follow those direction just insert your stock instead of cf auto root tar md5
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached Odin3-vX.X.zip file
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done
go to next post and grab cf auto root for i317m, IF your going to attempt to reboot
grab zip fro stock build http://www.hotfile.com/dl/180165074/47da708/I317MVLALJ2_I317MOYAALJ2_RWC.zip.html
and un zip with 7zip
place in odin pda slot as the directions from chainfire's post, remove sd if installed and continue.
when finished let reboot and it will hang on boot ani. pull battery, go into stock recovery and format cache and factory reset, then reboot.
you should be good to go at that point. if not pm me.
Click to expand...
Click to collapse
Here's what I did, downloaded stock rom I317MVLALJ2_I317MOYAALJ2_RWC
downloaded ODIN 1.85 from chainfire's post
put stock rom into PDA tab, reset time and auto reboot checked
- start flash, it Passed.
then downloaded CF auto root for I317M
- put the phone in download mode again
- put CF auto root to PDA tab, reset time and auto reboot checked
- it passed too
now I cannot get to recovery
- battery out Volume UP+power +Home
- "samsung galxy note II" logo keeps coming back
one thing I remember from before when device was on complete stock, it use to show "Samsung" logo in Bold not "Samsung Galaxy Note II"
any ideas?

prince_f_swords said:
Here's what I did, downloaded stock rom I317MVLALJ2_I317MOYAALJ2_RWC
downloaded ODIN 1.85 from chainfire's post
put stock rom into PDA tab, reset time and auto reboot checked
- start flash, it Passed.
then downloaded CF auto root for I317M
- put the phone in download mode again
- put CF auto root to PDA tab, reset time and auto reboot checked
- it passed too
now I cannot get to recovery
- battery out Volume UP+power +Home
- "samsung galxy note II" logo keeps coming back
one thing I remember from before when device was on complete stock, it use to show "Samsung" logo in Bold not "Samsung Galaxy Note II"
any ideas?
Click to expand...
Click to collapse
Anyone............

Make sure its volume up home then power

[RECOVERY][N8000/N8013]CWM 6.0.4.4{Fully Working}

{
"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"
}
Disclaimer:
By flashing this recovery you take full responsibility to whatever happens on your device. The developer will NOT be held responsible to whatever happens on your device. Ofcourse, the recovery has been tested but whatever happens on your device will not be held against the developer.
What Is CWM Recovery ?
CWM recovery is a way that enables you to falsh a custom rom , customize your rom and can save you from bad situations. To Be fully in controll of your android device you need a recovery and this is one of them.How To Install CWM Recovery ?
There are 2 methods for installing CWM
1.Method (dd method)
You need root before you continue.
now copy recovery.img from second post to your sd card and :
1.On PC :
Make shure that device is on usb debugging mode.
Plug device and open Terminal/command prompt.
Copy Pasta the Following Commands :
PHP:
adb shell
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6
make shure that partion is mmcblk0p6 or you will brick device !
now you can reboot to recovery (volume up + home +power) and enjoy CWM 6.0.4.4
2.On Phone :
First Download Terminal Emulator From Play Store.
Plug device and open Terminal apk
Right the Following Commands :
PHP:
su (you need root acess for it )
Then
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6
make shure that partion is mmcblk0p6 or you will brick device !(guys with fat fingers stay away !)
now you can reboot to recovery (volume up + home +power) and enjoy CWM 6.0.3.3
Second Method Is Via ODIN.
First Download ODIN
Now Download the N8000/N8013-CWM-6.0.4.4.tar From Second Post and put it in same directory as odin.
Go To Download Mod (Volume Down +Home+Power) and plug device.
Now in Odin You Will see {added} and a light blue figure on top that means that device has been recognized if you dont get them uninstall devices drivers and retry.
Now click PDA and select N8000/N8013-CWM-6.0.4.4.tar And Then Click Start .
After Device reboots Your Done and CWM Is Flashed.Thanks To :
CM Team For CWM recovery .
@Dees_Troy @bigbiff @anders3408 @cybojenix @invisiblek {These Guys Are The Best And I Thank Them for helping me every step in the way and not thinking that i am a nut job }
Please Hit The Thanks Button If You Like My Work
Follow Me On Twitter SamerDKingCobra
If You Have Any Kind Of Trouble Feel Free To PM Me As I Am Here Almost 19 Hours A Day.

Downloads And Q&A
Downloads :
1.IMAGES
N8000-CWM-6.0.4.4.img {For dd Method , Please rename to recovery.img }
N8013-CWM-6.0.4.4.img {For dd Method , Please rename to recovery.img }
2.TAR FILES
N8000-CWM-6.0.4.4.tar Build #1 {For Odin}
N8013-CWM-6.0.4.4.tar Build #1 {For Odin}
Change Log :
Build #1 Fully Working.Whats To Do In Future Build ?
Enable Touch .
Add OTG Support.FAQ:{Please Read Before Posting}
Q: OMG ! Recovey Not Booting What To Do ?
Alease Dont try entering recovery first time from advanced power menu just do it the hard way
Q:My Device is not getting read by windows ?
A:Uninstall all drivers that you installed for the device .Please Hit The Thanks Button If You Like My Work
Follow Me On Twitter SamerDKingCobra
If You Have Any Kind Of Trouble Feel Free To PM Me As I Am Here Almost 19 Hours A Day.

For Later Use

it can't mount the external sd

iRoNX said:
it can't mount the external sd
Click to expand...
Click to collapse
seriously i did not notice such error, i will see what i can do tomrrow Thanks

First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.

Shmong said:
First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.
Click to expand...
Click to collapse
Well thats odd :/ are you sure you have n8000 build not n8013 as i am recovery fine

Yes, i'm pretty sure. I've tried to do this few times via both terminal and odin. Now will try one more time...
UPD: I've repacked the img file with the tar archiver+ put md5 checksum (tar.md5) and flashed it with odin successfully.
And like iRoNX said it can't mount extSD: "error mounting /storage/sdcard1"
UPD2: The recovery from similar thread have another issue: cannot format "/data" and cannot explore internal flash )))

Shmong said:
First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.
Click to expand...
Click to collapse
+1.
The Odin tar file is not OK. Although I did not get a bootloop, the indicator on phone in download mode goes to the end and then stays there at "NAND write". I has to disconnect the phone and reboot manually, and my old version of CWM was still there (phew!). The .img files and dd worked fine.
Thanks anyways for this update !!!! It worked to get me on JB 4.4 !
Update: When phone is powered off and charger connected, upon starting there is a garbled green image that comes on for several seconds - most likely the battery charging icon - and then the phone will start up. It was not there before flashing 6.0.4.4. Anyways my phone does start up........

Tar file not working.. gets stuck at "Nandwrite"

Thanks for the recovery, I made it into CWM zip files so you can flash in CWM or TWRP here:
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8000-CWM-Recovery-v6.0.4.4.zip
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8013-CWM-Recovery-v6.0.4.4.zip

zedomax said:
Thanks for the recovery, I made it into CWM zip files so you can flash in CWM or TWRP here:
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8000-CWM-Recovery-v6.0.4.4.zip
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8013-CWM-Recovery-v6.0.4.4.zip
Click to expand...
Click to collapse
Way to go, champion !!

Flashed but the external SD card doesn't work
Sent from my GT_N8000

ODIN Image file attached.
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L

SD cards problem
Hello again,
Within this version of CWM, the SD card problem seems to be only for the 64g cards as tested on my N8013. However, after you flash the Rom you'll using, there is no problem with 64g cards outside of CWM recovery mode.
Smaller sized cards 32g and less will mount fine while you are in CWM recovery mode.
Cheers,
L

lobo25 said:
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L
Click to expand...
Click to collapse
Not working for me... says img. file is invalid. then ends.

Love it. Thanks.

lobo25 said:
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L
Click to expand...
Click to collapse
Anyone confirm this as working?
Edit: Not working. Odin says invalid.

missing file
I seem to have lost my \efs folder, and in searching for a solution one of the steps I'm told to take is to flash "N8000-CWM-6.0.4.4.tar". However, it doesn't seem to exist anywhere (now that goo is gone), other than in this thread and the version here seems to be broken. Does anyone have the N8000 version of the .tar file?

Boot-loop, can't wipe device.
Hey everyone. I'm not exactly sure what happened, but it seems that my GT-N8000 is on the fritz again. The device was screen-off this morning (I left home) and when I came home it was in a reboot loop.
I jumped into recovery (CWM v6.0.4.4) to try to wipe both cache and dalvik (both successful) and rebooted. Same bootloop.
So then I decided to wipe the storage and reinstall the ROM (Gnabo v8 is what I had been running). When I attempt to "wipe data/factory reset", it says "formatting data . . ." and then reboots into the bootloop again.
Then I thought that maybe it was wiped, so I attempted to flash Gnabo. It installs successfully (Installing update, blue bar goes across, "Enjoy!" and "Install from sdcard complete."), however, when the installation starts, I get the first box and then it sits for almost 2 minutes before the blue bar appears, fills in just a few quick seconds, and then displays the completed message. It seems to me that the installation and the blue bar should be taking longer, but what do I know. Anyway, I rebooted (No, don't fix ROM flasing stock recovery on reboot), then back into the bootloop. So I'm still losing.
I don't know if it's related, but some months ago I had something similar happen in that the device was in a bootloop and it turned out that it had somehow lost the /efs folder. I had restored that (thanks XDA forums!) and it had been working fine since about June 2015.
I'm starting to think that my memory has gone bad, and that I basically have a 10.1 inch paperweight. Suggestions? Thanks for any help you can provide.

[TUT] Root & install any custom recovery on your XS/XSL

Hey guys! So I just had my first Xperia phone-rooting experience, after ditching my old Galaxy Ace for an Xperia SL,
and I thought I'd share my experience on how to root your Xperia S or SL, and install CWM on it.
I bricked it TWICE since I didn't find good tutorials, so I thought I'd help out newcomers.
The following steps were followed on a Windows Machine, on a "virgin" Xperia SL whilst on the latest stock 4.1.2 build (6.2.B.1.96).
__________________________________________________
__________________________________________________
INGREDIENTS (what you need):
Flashtool. They say it is recommended to use one version before the latest (i.e. right now the latest is 0.9.13.0, so you should use 0.9.12.0).
However, the one that worked for me was 0.9.11.0. You can get the very latest here (official Flashtool website), 0.9.12.0 here (uploaded.net), or you can get the one I used here (mediafire). NOTE: The latest version (0.9.16.0) might fix the Windows 8+ recognition issue stated below. Try that version first.
The stock 6.2.B.0.211 kernel.
DooMLoRD's Easy Rooting Toolkit v18.
The stock 6.2.B.1.96 kernel.
DooMLoRD's CWM6 Installer or LEDelete's RecoverX.
An Xperia S/SL with stock JB 6.2.B.1.96 and USB Debugging Mode enabled.
Android SDK.(optional, in case you want to install TWRP recovery)
A computer.
Patience.
__________________________________________________
__________________________________________________
DISCLAIMER:
I am not responsible for whatever happens to your phone. Whatever does happen to your phone is your fault, since you decided to be a daredevil and try this out.
Therefore I am not to be accused of any damage (temporary or permanent) done to your phone. I will try to be as helpful as possible, should you get lost or break your XS/SL.
I bricked my phone in my first try, and fixed it, so I think I can help you.
STEPS
Ok, now that the warning is over, let's go ahead and root the hell out of that Xperia.
I am assuming you have already installed Flashtool, and that you know what it does. If you have any doubts about it, you can Google that information or ask me on this thread.
Also, this tutorial tells you how to do this on unlocked bootloader. Sony has a nice page on how to unlock it, in case it is.
The instructions are here, including how to check if your phone has or not an unlocked bootloader.
Basically, a locked bootloader means you can't flash custom kernels on your phone (hence not allowing you to flash CWM, for example).
First of all, you need to make sure whether you're on Windows 7, Windows 8, or Windows 8.1. This is very important, because it can save you hours of useless efforts to get your PC to recognize your device.
Apparently, both Windows 8 and Windows 8.1 struggle at identifying the right drivers for your phone in order for you to flash anything using Flashtool. If you're on Windows 7, head on to step 3.
If you're on a Windows 8/8.1, and you have no trouble with Flashtool (it recognizes your phone right away), then you can go to step 3 as well.
IF YOU'RE ON W8/W8.1, and your phone isn't recognized, check if you're using USB 3.0 ports, this might be the reason.
If you're on Windows 8/8.1 and Flashtool doesn't recognize your phone, then you might be in trouble; go to step 2.
FOR XSL USERS: it is very likely your phone is not recognized right away, but Flashtool might also show you a list with all the Xperia devices for you to choose your model from. Choose Xperia S, you'll be fine.
Windows 8/8.1 introduced an issue with drivers and that's why your Xperia phone might not get recognized in Flashtool as soon as you plug it in. If this is the case, try this:
Go to C:\Flashtool (or wherever you have installed it), and run the .exe inside the drivers folder. This should start an installer that will extract the desired drivers onto your system.
You must check your phone's drivers along with the Flashboot and Fastboot drivers(the last two in the list).
If the installation of the drivers finished successfully, then go to step 3. Otherwise, you must "Disable Driver Signature Enforcement" on your Windows 8/8.1 PC.
This will let you install unsigned drivers on your computer. Once you're done with Step 9 in that tutorial, try to install the drivers on C:\Flashtool\drivers once again.
This time, you should be greeted with this message:
{
"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"
}
Click on "Install this driver software anyway" as many times as prompted (three times, in my case).
When this driver installation is done, a window will tell you the installation is finished and a list with the drivers that were successfully installed will be shown.
All of the selected drivers should have a green check on their left.
Should this window still show you red crosses and fail to install the drivers, I'm afraid you might be screwed, unless you can find a Windows 7 PC.
So you have no problems with your drivers? Great! This means you can root your phone right away.
The method I use is the same explained here, but I'll explain it with more detail, as the one there assumes you know a lot about flashing.
The method DooMLoRD uses is flashing an older kernel first (6.2.B.0.211), because his toolkit doesn't support the latest 6.2.B.1.96 kernel. This is called downgrading you kernel. This will wipe all your applications and settings, just like a factory reset. Your SD data will remain intact.
So, what you need to do is download the files on the "Ingredients" SECTION (and install the Android SDK), and then:
Open Flashtool. Verify your phone has been detected by Flashtool. If it hasn't, install a different version of Flashtool while your phone is connected. Then click on the lightning icon on the top left.
Select Flashmode, because we're going to select the kernel files to flash (to turn on your cell phone on flash mode, turn it off, and once it's off plug it in to your computer while holding down the VOLUME DOWN key, a green LED will flash. If it's blue, you're in fastboot mode and you held down the VOLUME UP key instead).
Change the source folder to wherever you downloaded the stock 6.2.B.0.211 and 6.2.B.1.96 kernels.
Make sure the highlighted on is the .211 kernel, and click on flash. This should start the kernel downgrade and restart your phone once it's done.
When your phone has booted, disconnect your phone and close Flashtool (this is very important).
Great! Now your phone has the old .211 kernel and can be rooted. Extract DooMLoRD's Easy Toolkit to your C drive.
Run the "runme_file" that corresponds to your OS. MAKE SURE YOU RUN THE RIGHT ONE. Since this tutorial is for Windows PCs, the file you should run is the .bat.
This will open a console window with a set of instructions. Once you've read them and your device is plugged in (it must be on), press enter. The toolkit will go on from then. You must not worry when it says something about daemons and outdated servers.
Your device will restart as soon as it's done. You can check if it really is rooted by opening the apps drawer and verifying the SuperSU app is there.
Remember, you just downgraded your phone's kernel, so some of the old stock apps will come back up. You can uninstall them, but I recommend you do this later on (I'll tell you when).
Now your phone is rooted.
NOTE: The app drawer takes a while to fully load the first time after the root, so give it some time and you should see the SuperSU app. Don't rush things and assume it isn't there.
I did that and rooted it twice, thinking it had failed. That was such a waste of time :silly:.
Now that your phone is rooted, you can go and flash the newest stock kernel. Follow steps 3.1. to 3.5., but flash kernel 6.2.B.1.96.
Now your phone is rooted and on the latest stock kernel! Feel free to uninstall those useless stock apps that appeared back on your app drawer.
__________________________________________________
CWM INSTALLATION STEPS
This should be relatively easy now. Your phone is now rooted, and you will now flash CWM Recovery on your phone. For this, I found a quick installer by DooMLoRD.
Just extract it anywhere, run it (cwm-install-en.bat, press Enter 3 times and it will start) while your phone is connected via USB, and you should be just fine.
I had to use this method, since I used RecoverX and it did not work.
You know CWM was flashed correctly when you shut down your phone, turn it on and your see the LED turns on BLUE when the Sony logo comes up.
When it does, press the Volume Up button and the LED should turn GREEN for a couple of seconds, then boot into Recovery.
__________________________________________________
TWRP INSTALLATION STEPS
You might also want to install TWRP instead of CWM, because RaymanFX's ROMs recommend this, or because you come from a different phone and you had TWRP on it.
If you want to install one of RaymanFX's ROMs, I recommend you get the img.boot file from the ROM (extract the install .zip file and look for it) and flash it as a new Recovery. This will get you TWRP.
If you just want to flash it, you can try out the TWRP Manager app from the Play Store. This is pretty straightforward.
Also, you can try flashing the boot image on TWRP's website using fastboot (this is why you need the Android SDK). The instructions are there, just make sure you have the .elf image file in the same folder as the Android adb.exe and the fastboot.exe files, and run the command they tell you to use while your phone is connected.
Just make sure you have Busybox installed.
I strongly recommend you do a NAND Backup with your newly installed CWM Recovery.
In order to flash any custom ROM, the instructions are different, but they all follow a pattern. If you're in rooted stock, Factory reset your phone and Wipe the Dalvik cache.
If you're in a custom ROM and you're flashing an update to that ROM (say, from Beta 2 to Beta 3), you can do a dirty install on top of it (no wipes), or Wipe Dalvik and normal cache before doing so.
These instructions may vary between ROMs, however.
If you have any questions, please don't hesitate to post here. I hope this was helpful enough for everyone!
This is all DooMLoRD's work and I'm only saying how you could use it. I do not own any of the downloadable files I have posted here.
DooMLoRD's Dev-Host

Thanx dude.

Dr. NAC said:
Thanx dude.
Click to expand...
Click to collapse
Did it help? Any feedback that might help me improve this tutorial?

Good job bro
Sent from my Xperia S using xda premium

I have tried RecoverX to install recovery. The installation is finished but cannot boot into the CWM.

hm9408 said:
For this, I found a quick installer by DooMLoRD. Just extract it anywhere, run it (cwm-install-en.bat, press Enter 3 times and it will start) while your phone is connected via USB, and you should be just fine. I had to use this method, since I used RecoverX and it did not work. You know CWM was flashed correctly when you shut down your phone, turn it on and your see the LED turns on BLUE when the Sony logo comes up. When it does, press the Volume Up button and the LED should turn GREEN for a couple of seconds, then boot into Recovery.
Click to expand...
Click to collapse
timespace7 said:
I have tried RecoverX to install recovery. The installation is finished but cannot boot into the CWM.
Click to expand...
Click to collapse
Might as well try DooMLoRD's installer.

I have windows 8.1 and i have successfully installed the drivers but my PC still doesn't recognize my phone. Every time i try to enter the fast boot, the led turn blue, my windows sais that the device is not recognized and the led turns off and my phone starts charging...any ideas how to fix this? I try to make the fastboot work to unlock the bootloader.
PS: I have windwos 8.1
PPS: Never mind i figured it out...i just used the fix for USB3.

catalin1122 said:
I have windows 8.1 and i have successfully installed the drivers but my PC still doesn't recognize my phone. Every time i try to enter the fast boot, the led turn blue, my windows sais that the device is not recognized and the led turns off and my phone starts charging...any ideas how to fix this? I try to make the fastboot work to unlock the bootloader.
PS: I have windwos 8.1
PPS: Never mind i figured it out...i just used the fix for USB3.
Click to expand...
Click to collapse
I will note this on the tutorial. I had forgotten how picky W8 is with USB 3.0 ports, too.
Anything else I should add to this tutorial, by the way?
Don't forget to click on that thanks button

Can't install custom recovery

Hello guys.
So i decided to try to root my g pad. I tried to root throw windows but I kept getting errors so I ended up using towelroot which gave me root access.
Then I wanted to install TWRP but when I did it throw windows I got errors and I kept having the stock recovery. So I tried with an app from play store but then I just got stuck with secure boot error... Now I am back with stock which I got with the LGmobile support software.
I have attached my software specifications. Can someone please tell me what I need to do to be able to install a custom ROM on my G Pad?
Thanks
{
"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"
}
Sent from my LG-V500 using XDA Free mobile app

Had the same question. Go here:
http://forum.xda-developers.com/lg-g-pad-83/help/current-installing-recovery-running-t2790834

@velein
I have exactly the same software specifications (V50020a) and Build-Number (KOT49I.V50020a) and this is what I did.
Tablet: Security- activate unknown sources, Developer options - USB-debugging enabled
Computer: download and install USB-drivers for LG G Pad 8.3 http://www.lg.com/de/service-mobil-telefon/lg-G-Pad-8.3
1. Root with Tovelroot V2 http://towelroot.com/
2. Install SuperSu v2.00 http://forum.xda-developers.com/showthread.php?t=1538053
3. Start SuperSu and Update Binaries ( normal)
SuperSu says failed to update Binaries please reboot, rebooted
after reboot Supersu works fine.
4. Install SdFix http://forum.xda-developers.com/showthread.php?t=2684188
should work without problem, if not you have a problem with root.
5. Install Flashify http://forum.xda-developers.com/showthread.php?t=2349847
Backup kernel & recovery , just in case.
I did NOT use this to flash the new recovery, but later on to enter in the new recovery
6. Download the newest version of TWRP for v500 from here http://forum.xda-developers.com/showthread.php?t=2551499
Attention !!! you have to take the one where it says:" These builds are for the 4.4.2 bootloader"
download new version 2.7.1.0 !! 4.4.2-v500-TWRP_2.7.1.0-recovery.zip !!
copy the recovery.zip to your tablet
7. Download the tool to flash recovery from here http://forum.xda-developers.com/showthread.php?t=2698267
look at step 3 , download: V50020_aboot_twrp_v2.zip, to your computer and unzip it.
8. Connect the tablet (MTP) to the computer and run file:runme.bat, ! on tablet you have to allow acess from the computer and SuperSu acess for adb !
when finished disconnect usb and let the tablet reboot
9. On the tablet start Flashify , in the menu press: reboot to recovery
10.Tablet starts to the TWRP-recovery. Now go to:install and flash the new version of twrp(2.7.1.0) that you have copied to the tablet.
reboot system.
this worked for me.
Edit: For all who have the new V50020d firmware
you have to modify the runme.bat file before you run it!
Have a look over here, post 72
http://forum.xda-developers.com/showthread.php?t=2782422&page=8
change the V50020b to V50020d, dont forget to save the file.

Thanks guys. After hours og research and several tries I ended up using step 3 in i10terror's Korea thread. Worked without any problems. Thanks for the answers though.
Sent from my LG-V500 using XDA Free mobile app

whatever47 said:
@velein
I have exactly the same software specifications (V50020a) and Build-Number (KOT49I.V50020a) and this is what I did.
Tablet: Security- activate unknown sources, Developer options - USB-debugging enabled
Computer: download and install USB-drivers for LG G Pad 8.3 http://www.lg.com/de/service-mobil-telefon/lg-G-Pad-8.3
1. Root with Tovelroot V2 http://towelroot.com/
2. Install SuperSu v2.00 http://forum.xda-developers.com/showthread.php?t=1538053
3. Start SuperSu and Update Binaries ( normal)
SuperSu says failed to update Binaries please reboot, rebooted
after reboot Supersu works fine.
4. Install SdFix http://forum.xda-developers.com/showthread.php?t=2684188
should work without problem, if not you have a problem with root.
5. Install Flashify http://forum.xda-developers.com/showthread.php?t=2349847
Backup kernel & recovery , just in case.
I did NOT use this to flash the new recovery, but later on to enter in the new recovery
6. Download the newest version of TWRP for v500 from here http://forum.xda-developers.com/showthread.php?t=2551499
Attention !!! you have to take the one where it says:" These builds are for the 4.4.2 bootloader"
download new version 2.7.1.0 !! 4.4.2-v500-TWRP_2.7.1.0-recovery.zip !!
copy the recovery.zip to your tablet
7. Download the tool to flash recovery from here http://forum.xda-developers.com/showthread.php?t=2698267
look at step 3 , download: V50020_aboot_twrp_v2.zip
8. Connect the tablet (MTP) to the computer and run file:runme.bat, ! on tablet you have to allow acess from the computer and SuperSu acess for adb !
when finished disconnect usb and let the tablet reboot
9. On the tablet start Flashify , in the menu press: reboot to recovery
10.Tablet starts to the TWRP-recovery. Now go to:install and flash the new version of twrp(2.7.1.0) that you have copied to the tablet.
reboot system.
this worked for me.
Click to expand...
Click to collapse
A very useful topic. :thumbup:
Thanks for sharing your experience and for your time.
Sent from my LG-V500 using XDA Premium 4 mobile app

Hey Guys,
i've got a problem: i tried to flash twrp like it was said in the Korea Thread, but my G Pad won't start into recovery.
Not when i type "adb reboot recovery" in CMD nor when i try to get into twrp with flashify.
Any suggestions?

Which software specification do you have? If it is the V50020a than have a look at #3.
Do you have root access? Did you flash the right recovery file for your tablet?
Would be easier to help if you could provide us with some more detailed information.
Gesendet von meinem SGP511 mit Tapatalk

whatever47 said:
Which software specification do you have? If it is the V50020a than have a look at #3.
Do you have root access? Did you flash the right recovery file for your tablet?
Would be easier to help if you could provide us with some more detailed information.
Gesendet von meinem SGP511 mit Tapatalk
Click to expand...
Click to collapse
Of course, sorry.
Android 4.4.2
Kernel 3.4.0
Build-Nr. KOT49I.V50020a
Root Accesss: Yes
I already did step #3 several times (from this Thread: http://forum.xda-developers.com/showthread.php?t=2698267)
After i did this and tried to reboot into recovery, it just rebooted normally and not into recovery.
It was the second time this happenend. After the first time i used the LG mobile tool and could reboot into stock recovery, then i tried again #3 from above and couldn't reboot into any recovery..

Ok, just to clarify. With. #3 I mean the third post in this thread.
Please try to install Sdfix so we can be absolutely sure that root is working. Have you installed the drivers from lg on your computer? Is usb- debugging enabled on the tablet?

whatever47 said:
Ok, just to clarify. With. #3 I mean the third post in this thread.
Please try to install Sdfix so we can be absolutely sure that root is working. Have you installed the drivers from lg on your computer? Is usb- debugging enabled on the tablet?
Click to expand...
Click to collapse
Oops, sorry. It's early..
i also did your steps there, but they include the korean thread..
i did SDFix, it said and also says now:
"No Action Required, This device appears to already have write access to MicroSD Cards. No action has been taken....."
Yep and yep.
EDIT: Maybe it is important, if i try to reboot into recovery with flashify, in the top left corner is written:
Secure booting Error!
Cause: Device UnLock!, so Boot Success!!
Then it reboots into system.

On your computer you can see ADB Interface: Android Sooner ADB Interface in the device manager.
When connecting the tablet with usb you have set it to MTP or to charging only?

whatever47 said:
On your computer you can see ADB Interface: Android Sooner ADB Interface in the device manager.
When connecting the tablet with usb you have set it to MTP or to charging only?
Click to expand...
Click to collapse
ADB Interface -> Android Sooner Single ADB Interface
I set it to MTP.
I'm really desperate... i tried anything i found googling

can't install twrp or cwm recovery
I can't install even with this method, because my software specs are: android version - 4.4.2, kernel version - 3.4.0, compilation number - KOT49I.V50020a, software version - V50020a

Ops, didn't see your edit in post 10. The message is ok it is the same I have on my tablet before showing TWRP recovery.
Looks like you did everything OK but something messed up.
Did you get the tablet with this software version installed or did you get it per OTA.

whatever47 said:
Ops, didn't see your edit in post 10. The message is ok it is the same I have on my tablet before showing TWRP recovery.
Looks like you did everything OK but something messed up.
Did you get the tablet with this software version installed or did you get it per OTA.
Click to expand...
Click to collapse
I got it OTA, i once had twrp on it, but i tried to backup with LGs Tool and got stuck on bootloop and had to use LGs Mobile Tool.
Was the first of 2 times.
It's weird that i can't even boot into stock recovery, but in Flashify it says i got stock recovery installed...

Maybe the backup with the Lg tool wasn't a good idea.
When in Flashify you press Backup/Restore you can press the:!
In the small circle. It says that it reads the recovery from the latest cache file......so that maybe the reason why it shows you still the stock recovery.
I think the best would be to go back to stock with the Lg mobile support software and afterwards start again from the beginning like I posted in #3. Sorry
@Claudio Santos. Your tablet came with this software version or did you receive a OTA update?

whatever47 said:
Maybe the backup with the Lg tool wasn't a good idea.
When in Flashify you press Backup/Restore you can press the:!
In the small circle. It says that it reads the recovery from the latest cache file......so that maybe the reason why it shows you still the stock recovery.
I think the best would be to go back to stock with the Lg mobile support software and afterwards start again from the beginning like I posted in #3. Sorry
@Claudio Santos. Your tablet came with this software version or did you receive a OTA update?
Click to expand...
Click to collapse
I did go back to stock 2 times now and both times it did not work... used that method both times...

What else can I say, the discription in#3 is what worked for me on a new v50020a. Like you know it uses the method discribed in the Korea Thread, which worked for others also. The fact that you can see the message: Secure booting error......shows that the flashing tool worked ,but something went wrong at the end.
Maybe you should download it again ( just in case there was a problem with the download)and give it another try.

THANK YOU!
whatever47 said:
@velein
I have exactly the same software specifications (V50020a) and Build-Number (KOT49I.V50020a) and this is what I did.
Tablet: Security- activate unknown sources, Developer options - USB-debugging enabled
Computer: download and install USB-drivers for LG G Pad 8.3 http://www.lg.com/de/service-mobil-telefon/lg-G-Pad-8.3
1. Root with Tovelroot V2 http://towelroot.com/
2. Install SuperSu v2.00 http://forum.xda-developers.com/showthread.php?t=1538053
3. Start SuperSu and Update Binaries ( normal)
SuperSu says failed to update Binaries please reboot, rebooted
after reboot Supersu works fine.
4. Install SdFix http://forum.xda-developers.com/showthread.php?t=2684188
should work without problem, if not you have a problem with root.
5. Install Flashify http://forum.xda-developers.com/showthread.php?t=2349847
Backup kernel & recovery , just in case.
I did NOT use this to flash the new recovery, but later on to enter in the new recovery
6. Download the newest version of TWRP for v500 from here http://forum.xda-developers.com/showthread.php?t=2551499
Attention !!! you have to take the one where it says:" These builds are for the 4.4.2 bootloader"
download new version 2.7.1.0 !! 4.4.2-v500-TWRP_2.7.1.0-recovery.zip !!
copy the recovery.zip to your tablet
7. Download the tool to flash recovery from here http://forum.xda-developers.com/showthread.php?t=2698267
look at step 3 , download: V50020_aboot_twrp_v2.zip
8. Connect the tablet (MTP) to the computer and run file:runme.bat, ! on tablet you have to allow acess from the computer and SuperSu acess for adb !
when finished disconnect usb and let the tablet reboot
9. On the tablet start Flashify , in the menu press: reboot to recovery
10.Tablet starts to the TWRP-recovery. Now go to:install and flash the new version of twrp(2.7.1.0) that you have copied to the tablet.
reboot system.
this worked for me.
Click to expand...
Click to collapse
After trying 3 different complete HOW-TO ROOT and RECOVERY guides here on XDA and a few others on the internets, this gentleman finally helped me root and TWRPify my gpad. I was stuck on the last software struggling to find a way to root. I think all new GPad owners should start with these steps, as most guides, I feel like, are made for older software. Thank you Sir, you're a gentleman and a scholar!

I managed it!!!!!!!
I used the LG Mobile Tool and set the upgrade fail back (however it is called in english - sorry)
Then i did EXACTLY what you said in post #3
BUT! After you flashed the recovery for the first time you have to unplug your USB cable before rebooting and it will work!
Thanks guy, you're the best!

Develop Bugs

welcome