Jump to content
PaulOBrien

How to root your Hudl 2

Recommended Posts

Hi there,

Could anyone make a noob friendly post for rooting with the latest update. Trued to follow the other post but had the same issue with fastboot.

Thanks in advance.

Edited by edster353

Share this post


Link to post
Share on other sites

Hi there,

Could anyone make a noob friendly post for rooting with the latest update. Trued to follow the other post but had the same issue with fastboot.

Thanks in advance.

Share this post


Link to post
Share on other sites

Hi

I just thought i would try and tell you what ive done in case you wanted to know. I havent succeeded yet :(

 

I followed this guide: http://www.modaco.com/topic/373642-how-to-root-your-hudl-2/?p=2258831

 

however im not sure why but it doesnt root. Once I started T3 option the cmd run through various checks however on the very bottom for some reason in the cmd window it says:

 

Bootloader partitioning

Failed status read failed (too many links )

 

When I follow EavanC guide the cmd doesnt list my device?

Share this post


Link to post
Share on other sites

Hi again

Following EavanC guide I get here:

"Fastboot-windows -i 0x1d4d flash system system.img" without quotes and hit ENTER

However it says no image found in the cmd window.

Edited by pryddie

Share this post


Link to post
Share on other sites

Now seems to be stuck on creating space on the Hudl2 screen. Don't know how long it should take as this has been like this for well over half hour?

Edited by pryddie

Share this post


Link to post
Share on other sites

?

That's the wrong recovery check your path for the recovery zip

 

Here's my launcher bat file if it helps

 

echo off
::setup the window size 
mode con:cols=80 lines=60
::setup background and foreground color
cls
color 0B
 
::check our shell
:CHECKSHELL
    if %COMSPEC%==%SYSTEMROOT%\system32\cmd.exe goto SHELLOK
    echo.
    echo ERROR: You must run this script from the standard Windows Command Shell
    echo (%SYSTEMROOT%\system32\cmd.exe). Please start this shell first before
    echo running this script.
    pause
GOTO:EOF
 
:SHELLOK
set VERSION=01-12-2015
set PROGRAM_NAME=FASTBOOT TETHERED RECOVERY LAUNCHER %VERSION%
 
set WORKINGDIR=""
set WORKINGDIR=%~dp0 
for %%f in ("%WORKINGDIR%") do set WORKINGDIR=%%~sf
 
call "%WORKINGDIR%resources\functions.bat"
 
GOTO:TETHERED_ACCEPT
 
 
:TETHERED_ACCEPT
    set TRIGGER="%WORKINGDIR%\FB_RecoveryLauncher\recovery.trigger"
    set LAUNCHER="%WORKINGDIR%\FB_RecoveryLauncher\recovery.launcher"
    set RECOVERY="%WORKINGDIR%\FB_RecoveryLauncher\recovery.zip"
    cls
    :: set window title specific to this section
    title %PROGRAM_NAME% disclaimer
    ::print our default header
    echo. READ ME:
::  echo *                                  *                                  * ::this line is used as a centering reference nothing prints here
    echo =======================================================================
    echo. standard disclaimer:
    echo.
    echo.              WITH GREAT POWER COMES GREAT RESPONSIBILITY.
    echo.
    echo.                     by proceeding you accept that
    echo.                  it is carried out at your own risk
    echo.             and you will not hold anyone else responsible
    echo.
    echo.              WITH GREAT POWER COMES GREAT RESPONSIBILITY.
    echo.
    echo.
    echo. . type " ACCEPT " without quotes to continue . . .
    echo.
    echo. . type quit or exit to cancell and close this window
    echo.
    echo =======================================================================
    set choice=
    echo.&set /p choice=: ||goto :TETHERED_ACCEPT
 
    :: the only accepted answer to continue
    if %choice% == ACCEPT goto :TRIGGER_SELECTION
 
    :: we always want to use our close tool to exit the toolKIT
    :: so we remap commonly used commands for exiting
    if %choice% == e GOTO:CLOSE_TOOL
    if %choice% == q GOTO:CLOSE_TOOL
    if %choice% == exit GOTO:CLOSE_TOOL
    if %choice% == quit GOTO:CLOSE_TOOL
GOTO:TETHERED_ACCEPT
 
:TRIGGER_SELECTION
    call "%CHECK_DEVICE%"
    cls
    :: set window title specific to this section
    title %PROGRAM_NAME%
    set nxt=0
    set ric=0
    ::print our default header
    cls
    echo.
    echo ***********************************************************************
    echo. %PROGRAM_NAME%
    echo ***********************************************************************
    echo.
    echo =======================================================================
    echo. Select fastboot oem trigger used to launch recovery :
    echo.
    echo. T1 . launch using oem startftm trigger
    echo.
    echo.
    echo. T2 . launch using oem backup_factory trigger 
    echo.
    echo.
    echo. T3 . launch using oem stop_partitioning trigger
    echo.
    echo.
    echo.  D . donate open default web browser paypal donate
    echo.
    echo. type shell to launch an adb shell
    echo =======================================================================
    call "%PRINT_DEVICE%"
    set choice=
    echo.&set /p choice=please make a selection or type quit or exit to close the tool kit: ||GOTO:TRIGGER_SELECTION
    set OEMTRIGGER=""
    set OEMCMD=""
    :: the only accepted answer to continue
    if %choice% == T1 set OEMTRIGGER="/sbin/adbd" &set OEMCMD="startftm" &goto :REBOOT4TETHERED
    if %choice% == T2 set OEMTRIGGER="/system/bin/cp" &set OEMCMD="backup_factory" &goto :REBOOT4TETHERED
    if %choice% == T3 set OEMTRIGGER="/sbin/partlink" &set OEMCMD="stop_partitioning" &goto :REBOOT4TETHERED
    if %choice% == D start http://forum.xda-developers.com/donatetome.php?u=4821597 &GOTO:TRIGGER_SELECTION
    
    if %choice% == shell GOTO:adbSHELL
 
    :: command to change the fastboot oem command possibly work on other intel devices
    if %choice% == SETOEMCMD echo.&set /p OEMCMD=fastboot -i 0x1d4d oem command: &GOTO:TRIGGER_SELECTION
 
    :: for debugging
    if %choice% == cmd GOTO:CMD_LINE
 
    :: we always want to use our close tool to exit the toolKIT
    :: so we remap commonly used commands for exiting
    if %choice% == e GOTO:CLOSE_TOOL
    if %choice% == q GOTO:CLOSE_TOOL
    if %choice% == exit GOTO:CLOSE_TOOL
    if %choice% == quit GOTO:CLOSE_TOOL
    echo.
    echo. invalid input please try again.
    echo.
    pause
GOTO:TRIGGER_SELECTION
 
:REBOOT4TETHERED
    call "%CHECK_DEVICE%"
    cls
    :: set window title specific to this section
    title %PROGRAM_NAME% REBOOT
    ::print our default header
    echo.
    echo ***********************************************************************
    echo. %PROGRAM_NAME%
    echo ***********************************************************************
    echo. REBOOT
    echo =======================================================================
    echo.
    echo. DEVICE STATUS: %status%
    echo.
    echo. DEVICE INFORMATION: %deviceinfo%
    echo.
    echo =======================================================================
    echo.
    if /i %status% == UNKNOWN ( GOTO:CONNECTION_FAILED)
    if /i %status% == ADB-ONLINE ( GOTO:REBOOT2FASTBOOT)
    if /i %status% == FASTBOOT-ONLINE ( GOTO:TETHERED_TOOL)
GOTO:TRIGGER_SELECTION
 
:REBOOT2FASTBOOT
    "%GOOGLE_TOOL%adb" reboot-bootloader &"%GOOGLE_TOOL%fastboot" -i 0x1d4d getvar all &GOTO:TETHERED_TOOL
GOTO:TRIGGER_SELECTION
 
:TETHERED_TOOL
cls
    call "%CHECK_DEVICE%"
    :: set window title specific to this section
    title %PROGRAM_NAME%
    ::print our default header
    echo.
    echo ***********************************************************************
    echo. %PROGRAM_NAME%
    echo ***********************************************************************
    echo.
    echo =======================================================================
    echo.
    echo. DEVICE STATUS: %status%
    echo.
    echo. DEVICE INFORMATION: %deviceinfo%
    echo.
    echo =======================================================================
    echo.
    echo copy needed files to our device
    "%GOOGLE_TOOL%fastboot" -i 0x1d4d flash /tmp/recovery.zip %RECOVERY%
    "%GOOGLE_TOOL%fastboot" -i 0x1d4d flash /tmp/recovery.launcher %LAUNCHER%
 
    "%GOOGLE_TOOL%fastboot" -i 0x1d4d flash %OEMTRIGGER% %TRIGGER%
    echo.
    echo issue fastboot -i 0x1d4d oem %OEMCMD% command to start cwm recovery:
    "%GOOGLE_TOOL%fastboot" -i 0x1d4d oem %OEMCMD%
 
    echo.
    ping -n 20 127.0.0.1 >nul
    cls
    call "%CHECK_DEVICE%"
    :: set window title specific to this section
    title %PROGRAM_NAME%
    ::print our default header
    echo.
    echo ***********************************************************************
    echo. %PROGRAM_NAME%
    echo ***********************************************************************
    echo.
    echo =======================================================================
    echo.
    echo. DEVICE STATUS: %status%
    echo.
    echo. DEVICE INFORMATION: %deviceinfo%
    echo.
    echo =======================================================================
    echo.
    echo complete
    pause
GOTO:TRIGGER_SELECTION
 
:CMD_LINE:
    SET PATH=%PATH%;%GOOGLE_TOOL%
    cls
    echo.
    echo ***********************************************************************
    echo. %PROGRAM_NAME%
    echo ***********************************************************************
    echo.
::  echo *                                  *                                  * ::this line is used as a reference nothing prints here
    echo.     cli for debugging the toolKIT type " exit " to return to toolKIT
    echo.
    cmd
GOTO:TRIGGER_SELECTION
 
:adbSHELL
    @echo off
    call "%CHECK_DEVICE%"
    ::we need to make sure status is ADB-ONLINE
    if /i not %status% == ADB-ONLINE ( GOTO:CONNECTION_FAILED )
    cls
    title %PROGRAM_NAME% ADB SHELL
    echo ***********************************************************************
    echo. %PROGRAM_NAME%
    echo ***********************************************************************
    echo. type exit to close the adb shell
::  echo. *                                  *                                  * ::this line is used as a reference nothing prints here
    echo =======================================================================
    call "%GOOGLE_TOOL%adb" shell
GOTO:TRIGGER_SELECTION
 
:CONNECTION_FAILED
    echo.
    echo.       ERROR ! ! ! ERROR PLEASE CHECK YOUR DEVICE ERROR ! ! ! ERROR
    echo.&set /p = FAILED TO COMUNICATE WITH DEVICE [ %status% ] HIT ANY KEY TO RETURN:
GOTO:TRIGGER_SELECTION
 
:CLOSE_TOOL
    cls
    echo.
    echo ***********************************************************************
    echo. %PROGRAM_NAME%
    echo ***********************************************************************
    echo.
    call "%GOOGLE_TOOL%adb" kill-server &pause &exit
GOTO:EOK
Edited by robin0800

Share this post


Link to post
Share on other sites

That's the wrong recovery check your path for the recovery zip

Hi Robin

sorry about all this i downloaded everything in the one folder on my desktop mate

Share this post


Link to post
Share on other sites

You should have two folders

 

FB_RecoveryLauncher

 

resources

 

and a launcher.bat

 

the one posted above not the one that comes with the two folders

Edited by robin0800

Share this post


Link to post
Share on other sites

Hi Robin

I copied your launcher text into my launcher and saved. Now im back where we were with the pic i sent stuck on creating space...................looks exactly the same mate

Share this post


Link to post
Share on other sites

You should have two folders

 

FB_RecoveryLauncher

 

resources

 

and a launcher.bat

 

the one posted above not the one that comes with the two folders

Hi Robin

Yes thats correct i have the above, copied your text to my launcher and still where i was earlier? with the android pic i posted creating space

Share this post


Link to post
Share on other sites

Yes mate started the launcher as administrator and it's always the same it stops at creating space stage

post-166321-0-47827300-1432997411_thumb.

Edited by pryddie

Share this post


Link to post
Share on other sites

Perhaps you are short of space lots of apps lots of games? You may if this is the case have to reset your device

Edited by robin0800

Share this post


Link to post
Share on other sites

Perhaps you are short of space lots of apps lots of games? You may if this is the case have to reset your device

Hi Mate

no games or videos on it and 4.5gb space on my device

Share this post


Link to post
Share on other sites

Hi Robin

I'm unsure what you mean really. Thanks for your support I think I've done here I've exhausted my capabilities now I've been on it 2 days now mate

Share this post


Link to post
Share on other sites

Hi Robin

Oddly enough I've come to put my sky app on and it says when I try to watch sky sports that it is not compatible with a rooted device.

I dunno if it's rooted or not lol. It looks the same and the annoying start up music and tesco widgets are still there

Share this post


Link to post
Share on other sites

Hi Robin

Oddly enough I've come to put my sky app on and it says when I try to watch sky sports that it is not compatible with a rooted device.

I dunno if it's rooted or not lol. It looks the same and the annoying start up music and tesco widgets are still there

It will look the same as stock unrooted android even if its rooted.

 

Go to the play store and download SuperSU and root checker. Run SuperSU and then run root checker. See if a root grant window pops up and if your rooted.

Share this post


Link to post
Share on other sites

Hi EananC

I have installed SuperSu and Root Checker and root checker congratulated me on a rooted device

Not sure what I do now lol

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

By using this site, you agree to our Terms of Use.