488 replies to this topic

[johnlgalt]

OK, I thought that taking the OTA was causing my 'refresh' issue, where the phone will refresh right in the middle of an activity, such as replying here via TapaTalk. So, I HoNd my device to 5.0.1, keeping data, with TWRP and root.

Refresh issue is still there, although HoN process was fully successful.

Sent from my Nexus 6 using Tapatalk

[livinginkaos]

OK, I moved all the non-HoN relevant stuff over to that "other" thread.  Gotta keep the  Samuri complacent or appeased 

[s3inks]

Tried using HoN yesterday. Had issues with it recognizing my device. Followed the noob guide that suggested deleting the device including deleting the driver file. I then deleted everything google or android related from my hdd. Downloaded new SDK then reinstalled. Plugged in device while in fastboot and manually pointed windows to the google USB driver folder within the SDK and manually selected the bootloader driver. My computer sees shamu but HoN still does not. I tried this three times with the same results. Within the sdk folder i am able to use adb and fastboot commands so i got the device unlocked and rooted. I'm sure the issue is with my system or the operator, but if anyone has suggestions I should try, other than nuking my HDD, I would be greatly appreciative.

HoN did generate the flasme.bat script and seems like its going to be amazing for flashing images once I can get it setup correctly. Sam, thanks for all your hard work creating this tool!

[SamuriHL]

You are putting it in fastboot mode, yes?  It doesn't work being booted up into the system.  It MUST be in fastboot mode.

[johnlgalt]

Tried using HoN yesterday. Had issues with it recognizing my device. Followed the noob guide that suggested deleting the device including deleting the driver file. I then deleted everything google or android related from my hdd. Downloaded new SDK then reinstalled. Plugged in device while in fastboot and manually pointed windows to the google USB driver folder within the SDK and manually selected the bootloader driver. My computer sees shamu but HoN still does not. I tried this three times with the same results. Within the sdk folder i am able to use adb and fastboot commands so i got the device unlocked and rooted. I'm sure the issue is with my system or the operator, but if anyone has suggestions I should try, other than nuking my HDD, I would be greatly appreciative.

HoN did generate the flasme.bat script and seems like its going to be amazing for flashing images once I can get it setup correctly. Sam, thanks for all your hard work creating this tool!

 

 

You are putting it in fastboot mode, yes?  It doesn't work being booted up into the system.  It MUST be in fastboot mode.

 

Yeah, he said he was already in fastboot.  It's odd, though, that adb sees it but your script doesn't.  I'm wondering if it is a JAVA issue instead....

 

S3 - try uninstalling JAVA SDK and installing the latest version - either 7.72 or 8.x.  I used HoN perfectly fine with the Build 8 Update 20 SDKs installed (I install both x86 and x64 SDKs just to be safe because I'm alternating between using either for some basic JAVA stuff I am doing, but just the x86 SDK should be sufficient).

[SamuriHL]

The java is only used during script generation.  The script uses fastboot for the factory image.  I don't use adb at all in the script.  I can check to see if the platform sdk has been updated since I released it.  My advice would be to copy the adb dll's and fastboot.exe from the platform sdk and overwrite the versions in HouseOfNexus/TOOLS.  But other than that, there should be no difference at all.

[johnlgalt]

Ahhh.  So JAVA isn't the issue, as he said the scripts are being generated.

[SamuriHL]

Yup, exactly.  Of course, what'd help me is if the generated script were posted so I could see if there was any crazy error type stuff going on.

[s3inks]

You are putting it in fastboot mode, yes? It doesn't work being booted up into the system. It MUST be in fastboot mode.

Yes. I powered off, entered fastboot, connected USB to usb2 port on my motherboard, ran flashme.bat. Was only returned with 'waiting for device' message.

[SamuriHL]

Yes. I powered off, entered fastboot, connected USB to usb2 port on my motherboard, ran flashme.bat. Was only returned with 'waiting for device' message.

 

So let me see the generated script.  I have a guess but I'd need to see it.

[s3inks]

Yup, exactly. Of course, what'd help me is if the generated script were posted so I could see if there was any crazy error type stuff going on.

I'll gladly post the script or anything else that will help diagnose the issue. Do I just attach the file to the post? Thanks for taking the time to respond/help.

[SamuriHL]

I'll gladly post the script or anything else that will help diagnose the issue. Do I just attach the file to the post? Thanks for taking the time to respond/help.

 

Just open it up with an editor, select all, copy, and then paste it into a post here.

[s3inks]

@echo off

::Generated script from the House of Nexus 1.2.

PATH=C:\HouseOfNexus\TOOLS;%PATH%

fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash cache cache.img

:ask_recovery
    set choice=
    set /p choice=Flash custom recovery? [y/n]:
    if "%choice%"=="y" goto flash_custom_recovery
    if "%choice%"=="Y" goto flash_custom_recovery
    if "%choice%"=="n" goto flash_stock_recovery
    if "%choice%"=="N" goto flash_stock_recovery
goto ask_recovery

:flash_custom_recovery
    fastboot flash recovery C:\HouseOfNexus\RECOVERY\openrecovery-twrp-2.8.4.0-shamu.img
goto end_recovery

:flash_stock_recovery
    fastboot flash recovery recovery.img
goto end_recovery

:end_recovery

fastboot flash system system.img

echo WARNING: Choosing yes to this option will WIPE YOUR DATA.
:ask_erase
    set choice=
    set /p choice=Erase user data? [y/n]:
    if "%choice%"=="y" goto flash_userdata
    if "%choice%"=="Y" goto flash_userdata
    if "%choice%"=="n" goto end_userdata
    if "%choice%"=="N" goto end_userdata
goto ask_erase

:flash_userdata
   fastboot flash userdata userdata.img

goto end_userdata

:end_userdata


::SuperSU installation

:ask_supersu
    set choice=
    set /p choice=Install SuperSU? [y/n]:
    if "%choice%"=="y" goto flash_supersu
    if "%choice%"=="Y" goto flash_supersu
    if "%choice%"=="n" goto no_supersu
    if "%choice%"=="N" goto no_supersu
goto ask_supersu

:flash_supersu
   fastboot boot C:\HouseOfNexus\RECOVERY\openrecovery-twrp-2.8.4.0-shamu.img
   ping -n 5 127.0.0.1 >nul
   echo.
   echo o) Select Reboot
   echo o) Select System
   echo o) Swipe to install SuperSU
   echo.
   echo After the system reboots, install SuperSU from the play store.
   echo.
   goto end

_supersu
    fastboot reboot
    echo Rebooting...
goto end

:end
   echo Thanks for using the House of Nexus.
   pause
 

[SamuriHL]

Fascinating.  So you followed directions on the path.  Usually people ignore the "don't have spaces in the path" warning and then end up with issues.  That all looks correct.  My guess would be that the version of fastboot I shipped may be older than the latest platform tools.  Other than that there should be no reason why it'd work manually but not in the script.

[johnlgalt]

Hmmm.  Then that may be why mine worked OOB - I have the Android SDK in my path, as well as platform tools and tools subdirs, so it may have overridden ... no, windows looks in the current dir first, as you added to the PATH statement, and then hits the path.

 

Hmmm.

 

The usual suspects - another cable, USB port in the back of the computer, disable AV software.....

[SamuriHL]

Yea, I force my version ahead of the path for many, many reasons.  Usually that's the right thing to do given all the problems the wrong version can cause.  The NX6, however, can be a finicky little jerk sometimes where drivers are concerned.

[johnlgalt]

So I learned.  I also learned that EagleGet downloads the.tgz files from the Nexus Factory Image site and untars the file, leaving only a gzip file.  It took me three tries of it (the HoN .jar file) not working for me to realize that the filename itself was not right, as the second and third times I made sure the SHA-1 hash matched.

[SamuriHL]

The code for that stuff is not finalized.  It took a LOT of work to get it to decompress the tgz files.  I'll improve it at some point.

[johnlgalt]

I still haven't looked at the actual code lol.  But it goes without saying that your code is looking for a .tgz, and giving it a gzip just ain't gonna cut it.

[SamuriHL]

That's not....entirely fully accurate.