Related
Hi, My DHD volume buttons no longer work and I've been reticent to send it off to get fixed as I can do with out the volume controls as opposed to being without a phone for 2-3 weeks.
However I used Rom manager to boot into CWR and was in the process of upgrading to revolution 5.2.4 from 5.1.8.
I ran the full wipe script then my fat fingers rebooted the phone rather than flashing the rom.
I now cant get back into CWR to flash the new rom. It just sits at the boot logo, obviously as all other partitions have been wiped.
Is there any other way I can force the phone to boot into CWR, perhaps using the sdk tools or similar?
I've tried adb devices, but it doesnt show up. Is there an external way to force the phone into flashing a new ROM or booting into CWRM ?
Thanks
Ron
I would like to help, first lets try using adb, command would be adb reboot recovery
Hi, thanks for the help.
As mentioned in OP. I have powered the phone on and have have already attempted this, but the device is not recognised by adb.
tools>adb reboot recovery
error: device not found
My question is how to get the device to be recognised if its simply sitting at the boot image?
R
Sorry I over looked that, it seems to me if adb (which is an sdk tool) won't recognize the device as being attached, i don't see any other sdk tool doing any different, also as far as I know there is no alternate method to scrolling through the boot loader that would allow you to choose recovery and flash a zip other then the volume keys , so it seems the solution is, to send the phone off, get the volume keys fixed, and then you will be able to get back into the boot loader, and select recovery, and reflash a rom. Other than that, I don't see any other method, if adb doesn't recognize the device as being plugged in, I am assuming you attempted to boot into boot loader as well, and see if adb recognized the device?
EDIT: stupid question you can't boot into boot loader without volume key
I just want to confirm that I need do nothing else other than configure the sdk and ENV path etc, such that if i can run adb and get the deafult output, eg switches fr command line options etc...
then all I should need to do is turn phone on and connect via usb to computer. I dont need to edit any config files for specific phone versions or whatnot?
If not then Ill try and bring it to a vodaphone shop and see if they can fix the volume button...
R
if you get the volume buttons fixed, we don't even need adb, I was simply thinking adb since your volume buttons are broken. Once the volume buttons are fixed, you simply need to boot into boot loader, then to recovery, mount USB mass storage, put a new rom on there, wipe the phone, flash the rom and your good
Good luck mate, do some mediation meanwhile and learn to keep patience, so when your phone is back, you can treat it gently while in the recovery.
You will be alright once your vol keys are fixed.
I'm in need of some expert help for my wifes Droid Incredible. It is rooted, s-off running Cyanogen 7.xxx
She woke me in a pannic this morning saying her phone wasn't working. When I took a look, it keeps booting to the white screen with the "htc Incredible" words. I can press volume down and power to get into hboot, but when I select recovery or factory reset, it just boots back to the white screen with "htc Incredible"
I can't seem to get anywhere from here and the search I did seems to bring up other issues with people at least able to get into the recovery.
Any help or advice on where to go from here would be greatly appreciated.
Thank you.
Droinc said:
I'm in need of some expert help for my wifes Droid Incredible. It is rooted, s-off running Cyanogen 7.xxx
She woke me in a pannic this morning saying her phone wasn't working. When I took a look, it keeps booting to the white screen with the "htc Incredible" words. I can press volume down and power to get into hboot, but when I select recovery or factory reset, it just boots back to the white screen with "htc Incredible"
I can't seem to get anywhere from here and the search I did seems to bring up other issues with people at least able to get into the recovery.
Any help or advice on where to go from here would be greatly appreciated.
Thank you.
Click to expand...
Click to collapse
You need to try to reflash recovery thru hboot. Download CWM 5.0.2.0 http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip, and place the file on your sdcard in no folders. Boot into hboot (vol down and power) and it should find the file after a couple secs and prompt you to press vol up to update. Do so and then when prompted to reboot do so. Now remove or rename the PB31IMG.zip on your sdcard and then pull the battery and boot to hboot and see if you can access recovery.
cmlusco said:
You need to try to reflash recovery thru hboot. Download CWM 5.0.2.0, and place the file on your sdcard in no folders. Boot into hboot (vol down and power) and it should find the file after a couple secs and prompt you to press vol up to update. Do so and then when prompted to reboot do so. Now remove or rename the PB31IMG.zip on your sdcard and then pull the battery and boot to hboot and see if you can access recovery.
Click to expand...
Click to collapse
I got the message to hit volume up to update and then after that it asked if I wanted to reboot the device. I selected yes (volume up) and it still loops the white screen with the "htc Incredible" words. I never got to the point where it rebooted fully.
SHOOT!!! Was hoping this would have done it. Thank you for the help though. I appreciate it.
Anything else I might be able to do?
As a side not, the phone does not get recognized when I connect it to my computer. I had to use another phone to place the PB31IMG file on the SD card.
Droinc said:
I got the message to hit volume up to update and then after that it asked if I wanted to reboot the device. I selected yes (volume up) and it still loops the white screen with the "htc Incredible" words. I never got to the point where it rebooted fully.
SHOOT!!! Was hoping this would have done it. Thank you for the help though. I appreciate it.
Anything else I might be able to do?
As a side not, the phone does not get recognized when I connect it to my computer. I had to use another phone to place the PB31IMG file on the SD card.
Click to expand...
Click to collapse
No you misunderstood, it will still boot loop at this point, that was just the first step. Boot to hboot and see if you can access recovery now.
If you can access recovery, either restore a backup or flash a new rom.
cmlusco said:
No you misunderstood, it will still boot loop at this point, that was just the first step. Boot to hboot and see if you can access recovery now.
If you can access recovery, either restore a backup or flash a new rom.
Click to expand...
Click to collapse
Oh, gottcha. Sorry about that, my fault.
After hitting volume up to reboot, I took out the SD card and placed it in the other phone to remove the file. After that I put it back in the Incredible and booted it into hboot, but when I selected recovery, it did the same thing and just loops the "htc Incredible" screen.
Ok the next step to try would be to do an ruu. It will restore the phone to stock, but you will still have s-off.
Download this file http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip and place it on the sdcard in no folders, boot to hboot, vol up to install. This time though when prompted to reboot select no, and then select factory reset. Hopefully when its done it will boot normaly.
cmlusco said:
Ok the next step to try would be to do an ruu. It will restore the phone to stock, but you will still have s-off.
Download this file and place it on the sdcard in no folders, boot to hboot, vol up to install. This time though when prompted to reboot select no, and then select factory reset. Hopefully when its done it will boot normaly.
Click to expand...
Click to collapse
OK, going to give it a shot. Will be back soon with good news hopefully
Question...... After selecting "no" to the reboot option after it's been updated with the file, do I delete or rename the file and THEN try to get into recovery?
Droinc said:
Question...... After selecting "no" to the reboot option after it's been updated with the file, do I delete or rename the file and THEN try to get into recovery?
Click to expand...
Click to collapse
After selecting no to reboot, select factory reset from the hboot menu. When the factory reset is done it should automaticly reboot and boot up like normal.
Then you can delete the file and reflash cwm recovery as the ruu left you with the stock recovery.
OK, I must be doing something wrong. Here are the steps I have done:
* I put the SD card into a phone recognized by my computer
* I then place the RUU file onto that SD card
* I then take the SD card out and place it in the DInc
* I then hold the volume down button and power button to get into hboot
* The phone recognizes the file and starts the update (takes a bit)
* Once the update is done it asks if I want to reboot and I select no
* It then goes to a screen with a few options (bootloader, reboot bootloader etc...) I don't select anything and then pull the battery
* I then take the SD card out of the DInc and place it in the other phone so I can remove the file
* Once the file is deleted I take the SD card out of that phone and place it back into the DInc
* I go into hboot and select recovery and it just boot loops again with the "htc Incredible" screen
Am I missing something?? I know it can be recovered. Even it's back to stock, it would be great. My wife just wants her phone back.
cmlusco said:
After selecting no to reboot, select factory reset from the hboot menu. When the factory reset is done it should automaticly reboot and boot up like normal.
Then you can delete the file and reflash cwm recovery as the ruu left you with the stock recovery.
Click to expand...
Click to collapse
Damn, you're fast cmlusco.
When I select no to the reboot, it does not present me with the screen that has the recovery option. It's a different screen with, I think, 4 options: bootloader, reboot bootloader, and 2 others I can't recall
Just notice this thread is on page 2 now. Check the last post on page one for steps on what I did.
When you boot to hboot there should be an option to do a factory reset, do that, you may have to select bootloader first. Then see if it boots normaly.
cmlusco said:
When you boot to hboot there should be an option to do a factory reset, do that, you may have to select bootloader first. Then see if it boots normaly.
Click to expand...
Click to collapse
no go.
I assume once I apply the RUU I don't need to do it every time?
I went back into hboot and selected factory reset and it just did the same boot loop. Should I try wiping the SD card 100% clean and then try the RUU file?
Droinc said:
no go.
I assume once I apply the RUU I don't need to do it every time?
I went back into hboot and selected factory reset and it just did the same boot loop. Should I try wiping the SD card 100% clean and then try the RUU file?
Click to expand...
Click to collapse
You could try it, but it sounds like the recovery partition may be messed up. The stock recovery dosent work, cwm recovery dosent work, but ruus and recoverys flash fine without error. Sounds like a messed up partition table. Do you have ADB setup on your pc?
I don't have ADB on this PC. Been a while since I've even done anything with ADB. Could you point me in the right direction on what to do to get set up?
Once set up, what steps need to be taken?
Thanks for all your help with this. It's very much appreciated.
Droinc said:
I don't have ADB on this PC. Been a while since I've even done anything with ADB. Could you point me in the right direction on what to do to get set up?
Once set up, what steps need to be taken?
Thanks for all your help with this. It's very much appreciated.
Click to expand...
Click to collapse
gotta download android sdk
http://developer.android.com/sdk/index.html
this should help http://androidforums.com/faqs/443072-adb-guide-updated-12-05-2011-a.html
Droinc said:
I don't have ADB on this PC. Been a while since I've even done anything with ADB. Could you point me in the right direction on what to do to get set up?
Once set up, what steps need to be taken?
Thanks for all your help with this. It's very much appreciated.
Click to expand...
Click to collapse
Download this http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip, and extract the contents to C:\ADB.
Connect the phone to the pc and on the pc go to device manager and look for an entry called unknown or android 1.0. Right click on it and select update driver. Select browse for driver and navigate to C:\ADB\drivers and select the adb folder. It should find the driver and update it.
Then open a cmd prompt on your pc and navigate to the C:\ADB folder. At tje prompt type adb devices , it should return a string of numbers and letters.
From there if it finds the phone you need to fastboo flash your misc partition.
Its gonna get a little complicated and require a bunch of steps. It sucks but it may fix it. I know there are already threads out there on how to fix this issue but i cant seem to find one.
When I plug the phone into the computer and power the phone on it just boot loops and the computer doesn't acknowledge it at all. In device manager there is not entry under any of the categories that says "Android..." or "unknown"
Droinc said:
When I plug the phone into the computer and power the phone on it just boot loops and the computer doesn't acknowledge it at all. In device manager there is not entry under any of the categories that says "Android..." or "unknown"
Click to expand...
Click to collapse
Crap i forgot you need to be able to boot the phone to enable usb debuging for the pc to see it. Um now im not sure what to do. Mabey format the sdcard fat32 and try the ruu again. I need to think about it, it will come to me.
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
krazzyjman said:
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
Click to expand...
Click to collapse
Return it.
You have a defective unit.
[email protected] said:
Return it.
You have a defective unit.
Click to expand...
Click to collapse
Another one of many. ASUS quality control FTW.
anjelika said:
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
This thread doesn't work for me since my nexus is in a bricked like state
hard reset ?
hard reset always works for me. 20 seconds
krazzyjman said:
This thread doesn't work for me since my nexus is in a bricked like state
Click to expand...
Click to collapse
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
sfhub said:
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
Click to expand...
Click to collapse
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Is your device rooted? If not that is just rediculous on asus's part
slamdunksaliby said:
Is your device rooted? If not that is just rediculous on asus's part
Click to expand...
Click to collapse
My device is not rooted at all.
I've had it for 2 days.
I have to say, I am very disappointed in all of these issues.
I would return it..I'm sorry to hear that I have had troubles myself with two devices so far
krazzyjman said:
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Click to expand...
Click to collapse
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
It was not working, but my tablet just died and I was able to charge and get into the bootloader.
Now to see if it will work.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
krazzyjman said:
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
Click to expand...
Click to collapse
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
Where am I typing in those lines?
And all the files I need are in the download link?
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
I figured out where to type, but I have to unlock my bootloader?
I have no way to enable usb debugging since I cant tun on the device, right?
krazzyjman said:
I have no way to enable usb debugging since I cant tun on the device, right?
Click to expand...
Click to collapse
You don't need to enable USB debugging for fastboot mode.
You just need to press Power+VolDown until you get into the bootloader. That is fastboot mode. It will install Android Bootloader Interface (usb debugging does android debug bridge interface)
I actually didn't realize you weren't unlocked. If that is the case, the unlock process will erase your userdata, so you might as well just do the full factory restore.
First goto bootloader mode using Power+VolDown and connect USB, type
fastboot oem unlock
You'll see a question on the tablet screen, Press VolUp to go to yes and Power to select.
On the command prompt in windows, you should see it erase userdata and cache.
On the bootloader screen it should have "Start" highlighted (if not, use VolDown to cycle until you see "Start"). Press Power to accept. You should see Google, then it'll go into recovery and format userdata and cache. It'll then try to boot and since /system is having issues, you'll be stuck in Google again.
Go back into bootloader mode, hold Power+VolDown for a while until you see the bootloader screen.
Now grab the factory image as above, gunzip, untar, and you should have a folder razor-jss15j
Copy these files from your adb directory to the razor-jss15j directory
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
In command prompt in the razor-jss15j directory, type
flash-all
It should output a bunch of stuff, essentially writing a factory image to your tablet.
When it is done, it'll reboot and hopefully you'll get the initial setup window.
I wrote this up from memory, so hopefully I didn't forget stuff. If something doesn't seem right just ask.
Thanks for all of your help.
It really means a lot you took the time to help me.
I'm going to Best Buy today and I am going to see if I can do an exchange.
If not, I will try this later.
Again, thank you
hey guys,
i was bored and flashed a .zip on my phone and now I'm no longer bored. Long story, short... I'm booted into the os (almost) with constant errors popping up. I can't get the power button down for 10 seconds to reboot phone and i want to get back to recovery to flash by back up. How can I use terminal (mac) to force back into recovery if phone is not in mode for adb to recognize phone?
Thanks in advance.
Try hold power button + volume up to force reboot. Once the screen goes black release those buttons and hold volume down button to go to hboot
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Otherwise, I guess I wait until power drain.
andason said:
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Otherwise, I guess I wait until power drain.
Click to expand...
Click to collapse
Power + Volume Up should work. But as you asked for adb/fastboot
1) "adb devices" to check if device is recognized
2) "abd reboot bootloader" so the phone reboots into bootloader
3) go to recovery and try a reflash
andason said:
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Click to expand...
Click to collapse
This should always work as long as the screen is on. It might take 10 seconds or more, so you may not be holding the buttons long enough.
Alternately, you can use:
adb reboot bootloader
or
adb reboot recovery
There is no required more for adb commands, as long as the screen is on. Fastboot on the other hand, requires the phone to be in fastboot mode.
What did you flash? Was it a ROM, and if so did you do a full wipe (data, cache and Dalvik) before flashing?
Thanks for all the replies. It finally died and I was able to jump back into recovery. I was trying to flash a .zip (one+ one theme) to my rom and some things about it (audiofx) was not liked. I guess adb could not recognize the phone since it was basically booted into the os. I just thought there was a way to still use adb or fast boot to push it into recovery. I did not get to try adb reboot boot loader, but would adb recognize phone even with this command?
andason said:
Thanks for all the replies. It finally died and I was able to jump back into recovery. I was trying to flash a .zip (one+ one theme) to my rom and some things about it (audiofx) was not liked. I guess adb could not recognize the phone since it was basically booted into the os. I just thought there was a way to still use adb or fast boot to push it into recovery. I did not get to try adb reboot boot loader, but would adb recognize phone even with this command?
Click to expand...
Click to collapse
Glad it worked and that we could help a
adb reboot bootloader should be recognized nearly any time.
Sent from my HTC One_M8 using XDA Free mobile app
So here's the deal, I tried to format the cache partition of a stock, non-rooted and non-unlocked bootloader Zenfone 2 (Z00A) through recovery, and it somehow failed/got stuck. After about 1h, I shut down the phone via long-pressing the power button and now it won't boot.
Booting it just leads to an "error!' message and stay there. Trying to go back to recovery does the same thing, I can get to the initial fastboot screen, but selecting recovery mode and pressing power+vol up after the reboot doesn't lead to recovery at all. Instead, every 5 or 10 seconds, the screen clears to black for 1 sec and the same error message shows up.
I tried to get access to it through ADB, but it won't show up in the device list under either the fastboot screen or the Error! message screen on which it stays stuck. Also, the phone was setup so that it didn't allow USB debugging, but I doubt that matters, given that it can't even load Android at all.
Is there something I can do about it? Any tip is greatly appreciated, I looked around XDA and Reddit but didn't find anything that really helped.
When you get to the Error screen, hold power and press up volume button. It should get you to recovery...
You can also clear the cache in fastboot mode using the command "fastboot erase cache". It will ask if you want to format/erase cache, say yes and it should clear your cache in a few seconds...
ultramag69 said:
When you get to the Error screen, hold power and press up volume button. It should get you to recovery...
You can also clear the cache in fastboot mode using the command "fastboot erase cache". It will ask if you want to format/erase cache, say yes and it should clear your cache in a few seconds...
Click to expand...
Click to collapse
Thanks, I had tried various variations of that approach but the issue was a bit more complex than that. In the bootloader, the phone was detected by Windows and drivers from Asus installed properly. ADB wouldn't list the phone, but fastboot did. However, any operation by fastboot was denied access because USB debugging was not enabled prior to the phone going down. Otherwise, as you mentioned, fastboot erase cache would have worked fine.
In the end, I found another post on XDA by Theja which linked to a post in Spanish. The modified ADB and fastboot packet there contains a batch file that manages to bypass this issue and installs CWR, from which clearing the cache is possible. Upon reboot, Asus replaces CWR with the original recovery and things look back to normal.
Sweet, as long as you got it back up and running...
ultramag69 said:
Sweet, as long as you got it back up and running...
Click to expand...
Click to collapse
Hehe, thanks. I'm pretty happy indeed, was already considering the need for a new phone.
However, I must say that finding this toolset worries me a little bit. I thought the whole point of disabling USB debugging was to ensure that people can't perform low-level operations on the phone via fastboot/adb. In this case, this protection is somehow bypassed. I didn't have time to read through the entire batch file, nor am I proficient-enough in Android to make sense of it all, but I wonder how it was done...
In any case, I now have USB debugging left on. It increases convenience and the ability to recover things if problems occur, and it seems like the security benefits are not that strong anyways.