Related
To anyone of knowledge I have a HTC HD2 I have been trying to install Android from on here from many diiferent links etc.. and everytime I installit to mycomputer then unzip and install on my SD i run the Clcrd then Haret then my phone either shows a penguine or htc logo I let it sit for over 2 to 4 hurs everytime i try to install it on my phone and it just sits there. is it something Im not doing are there steps Im missing or things I need to installl along with the android program i choose I am super frusrtated can someone please help me get android up and running .. Thanks
mallfox said:
To anyone of knowledge I have a HTC HD2 I have been trying to install Android from on here from many diiferent links etc.. and everytime I installit to mycomputer then unzip and install on my SD i run the Clcrd then Haret then my phone either shows a penguine or htc logo I let it sit for over 2 to 4 hurs everytime i try to install it on my phone and it just sits there. is it something Im not doing are there steps Im missing or things I need to installl along with the android program i choose I am super frusrtated can someone please help me get android up and running .. Thanks
Click to expand...
Click to collapse
First of all tell me about your hd2, what rom is it currently running (stock 2.08, 3.14?) , what radio do you have? Whats your sd card?
All these questions are relevant to make droid work.
I'm not sure if this will work or not. But I had a similar problem when I first rooted my HD2. Under the Android folder, there is a text file: startup.txt
Open it up. The last line I've found typically reads "boot". Now, I don't know if this affects everyone. But after reading for 18+ hours when I first rooted my phone, I remembered reading somewhere that that particular line should read "bootlinux". And I've found that no matter what build I use, if I don't change it to bootlinux, it wouldn't get past the HTC. So try adding "linux" after the "boot". Then try starting it up again with CLRCAD.exe then haret.exe.
Hope that works for you.
RAM 576... OS version 5.2.2191 (21913.5.0.94) ... manilla version 2.5.20181424.0 ...Rom version 3.14.53.1(04666) WWE ... Radion version 2.15.50.14 ... SD card is Fat32.. i have tried alot of programs and have yet to get it to work . and i thank you both for your input I dont know what else to do...
mallfox said:
RAM 576... OS version 5.2.2191 (21913.5.0.94) ... manilla version 2.5.20181424.0 ...Rom version 3.14.53.1(04666) WWE ... Radion version 2.15.50.14 ... SD card is Fat32.. i have tried alot of programs and have yet to get it to work . and i thank you both for your input I dont know what else to do...
Click to expand...
Click to collapse
Did you erase all other content from your sd card, and was the content put in a named folder called Android?
GUIDE (yes another one) for ANDROID on HD2
mallfox said:
RAM 576... OS version 5.2.2191 (21913.5.0.94) ... manilla version 2.5.20181424.0 ...Rom version 3.14.53.1(04666) WWE ... Radion version 2.15.50.14 ... SD card is Fat32.. i have tried alot of programs and have yet to get it to work . and i thank you both for your input I dont know what else to do...
Click to expand...
Click to collapse
Here hope this helps! any questions feel free to ask...
I just posted this in another thread to clear some things up for some guys ...... hope this clears up the process for you a bit
............................excerpted from previous post........................................
********BTW i have attached a little template that i use when flashing various roms and storing them on my PC. has task29, HSPL & MAGLDR already in it. all u need to do is go to the xda hd2 master radio thread to grab your appropriate radio and put that into the empty radio file. then find the rom you want to test out and usually the developer will have both rom (obviously) and the appropriate CWM that u should use with it and just put those in their respective empty folders i have in the attached file. that way all the steps below will line up to the files i have attached
OH YEAH, FORGOT... THESE STEPS ARE TO BE DONE AFTER THE INITIAL PREREQUISITES i.e. windows mobile device center, activesync, proper spl version...blah blah blah
--------the following steps 1 - 4 are to be preformed while at the tri-color boot screen (easiest way to reach is to turn off your phone while its connected to your PC then immediately hold volume down button till you see it n wait for it to say usb in the white section).
(by the way your device will ALWAYS automatically restart itself after a couple seconds if it is shut down while plugged in via USB to either a wall/car charger or hooked up to a PC this is normal and a small hiccup either due to the use of magldr or the hspl but dont worry)...cant quite remember
1. run task 29
-double click the only icon in file if your using the one provided by doloop
-wait for it to run and do its thing. when its finished it will automatically turn off your device so be sure to hold down the volume key as soon as it does.
2. install radio
-run the "customRUU" file with the HD2 icon in the radio of your choosing
-it will operate in a similar fashion as the task 29, automatically turning off device upon completion.... down on the vol key
3. install hspl3/hspl4
-run the "HSPL3_PKG/HSPL4_PKG" file. should be the only one in there
-make sure you select 2.08.HSPL in the setup and it will execute itself just like the installers in the previous two steps n turn off your phone... down vol key
4. install magldr113
-make sure your selecting "rom update utility" in the magldr113 file. dont run the "DAF" it wont work properly if you do and youll get errors
-BUT THIS TIME AS IT TURNS ITSELF OFF HOLD DOWN THE POWER BUTTON ON YOUR DEVICE AS IT BOOTS UP UNTIL U GET TO MAGLDR AND CONTINUE TO HOLD IT DOWN UNTIL YOU SEE ABOUT 12 DIFFERENT OPTIONS...
5. install CWM recovery
-go to option 5 "USB Flasher" and hit the green call key. wait a few moments till it shows USB....USB make sure the second usb pops up and your PC recognizes the connection. then when it does sync you get to......
-while still in the usb flasher mode above, simply run you desired CWM recovery which should the one your developer recommends for the builds as the requirements tend to vary from rom to rom.
-this is achieved by selecting the "DAF" file from the clockworkmod recovery your using
-and again this installer will shut off your device upon completion and HOLD DOWN THE POWER KEY LIKE ABOVE TILL YOUR BACK AT THE MAGLDR MAIN MENU (with options 1-12).
6. install rom
-now go to option 8 "AD Recovery" and hit the green call button to enter into the CWM recovery u just installed
-after it loads up (GO!GO!GO!) go down to the "mounts and storage" option that is third from the bottom and hit the call key.
-once there go to the last option "mount USB storage" and hit the call key.
-give your PC a few moments to recognize the sd card for your device and choose to open it when your PC prompts with the regular file explorer or just find it and double click on the newly recognized drive (sdcard) if your PC doesnt auto prompt you.
-now the new drive (sdcard) should be empty (depending...) then just find the desired rom you chose to use, right click on it and copy.....then over to the new drive (sdcard) and paste. might take a min or two depending on the roms size
-once the copying is complete hit the call button to "unmount" your sdcard then the back button on your device till your back at the CWM main screen
-now go to the fifth option down and "install zip from sdcard" and hit the call button
-now select the second option "choose zip from sdcard" and select the zip file you just copied to your sdcard. then it will begin to install the rom and all rom install times vary by build. some take a minute, some seem like they take forever.
-once installation is complete hit the back button till your back at CWM main screen and choose the last option which is to "power off"
-then tap the power button(if u unplugged it from usb otherwise it wil reboot by itself) to turn on your device and give it some time for the initial boot and load as it has to set up everything u just installed. subsequent boot wont take as long but again it can all vary from rom to rom.
-after initial load and a successful bootup you should arrive at ether the lockscreen or a startup screen. give the rom a few more mins to settle and dont hit any buttons. then unlock the device or skip through the startup options and get to the home screen. maybe give it another min to settle the launcher and the last bit of data and resist the urge to mess with the features. your gonna hate this but hold down the power button and select power off device from the popup menu. i know it sucks but it is best practice when flashing roms. after device shuts off wait a few seconds and turn it back on and let it reboot. should be faster this time and when u get to your lockscreen simply give it a few seconds to settle again, unlock and go to main launcher a wait a couple more seconds for it to finish settling and.....have fun! (every time i restart my device for any reason i will always give it a few moments to finish loading up before just blazing away with the apps)
WOW! maybe its not so abridged after all, but oh well tried my best to be as clear as possible so people can utilize their HD2 to its fullest potential.
HOPE THIS HELPS AND IF INDEED I HAVE PLEASE HIT THE THANKS BUTTON
MEG4LOM4NI4C said:
Here hope this helps! any questions feel free to ask...
I just posted this in another thread to clear some things up for some guys ...... hope this clears up the process for you a bit
............................excerpted from previous post........................................
********BTW i have attached a little template that i use when flashing various roms and storing them on my PC. has task29, HSPL & MAGLDR already in it. all u need to do is go to the xda hd2 master radio thread to grab your appropriate radio and put that into the empty radio file. then find the rom you want to test out and usually the developer will have both rom (obviously) and the appropriate CWM that u should use with it and just put those in their respective empty folders i have in the attached file. that way all the steps below will line up to the files i have attached
OH YEAH, FORGOT... THESE STEPS ARE TO BE DONE AFTER THE INITIAL PREREQUISITES i.e. windows mobile device center, activesync, proper spl version...blah blah blah
--------the following steps 1 - 4 are to be preformed while at the tri-color boot screen (easiest way to reach is to turn off your phone while its connected to your PC then immediately hold volume down button till you see it n wait for it to say usb in the white section).
(by the way your device will ALWAYS automatically restart itself after a couple seconds if it is shut down while plugged in via USB to either a wall/car charger or hooked up to a PC this is normal and a small hiccup either due to the use of magldr or the hspl but dont worry)...cant quite remember
1. run task 29
-double click the only icon in file if your using the one provided by doloop
-wait for it to run and do its thing. when its finished it will automatically turn off your device so be sure to hold down the volume key as soon as it does.
2. install radio
-run the "customRUU" file with the HD2 icon in the radio of your choosing
-it will operate in a similar fashion as the task 29, automatically turning off device upon completion.... down on the vol key
3. install hspl3/hspl4
-run the "HSPL3_PKG/HSPL4_PKG" file. should be the only one in there
-make sure you select 2.08.HSPL in the setup and it will execute itself just like the installers in the previous two steps n turn off your phone... down vol key
4. install magldr113
-make sure your selecting "rom update utility" in the magldr113 file. dont run the "DAF" it wont work properly if you do and youll get errors
-BUT THIS TIME AS IT TURNS ITSELF OFF HOLD DOWN THE POWER BUTTON ON YOUR DEVICE AS IT BOOTS UP UNTIL U GET TO MAGLDR AND CONTINUE TO HOLD IT DOWN UNTIL YOU SEE ABOUT 12 DIFFERENT OPTIONS...
5. install CWM recovery
-go to option 5 "USB Flasher" and hit the green call key. wait a few moments till it shows USB....USB make sure the second usb pops up and your PC recognizes the connection. then when it does sync you get to......
-while still in the usb flasher mode above, simply run you desired CWM recovery which should the one your developer recommends for the builds as the requirements tend to vary from rom to rom.
-this is achieved by selecting the "DAF" file from the clockworkmod recovery your using
-and again this installer will shut off your device upon completion and HOLD DOWN THE POWER KEY LIKE ABOVE TILL YOUR BACK AT THE MAGLDR MAIN MENU (with options 1-12).
6. install rom
-now go to option 8 "AD Recovery" and hit the green call button to enter into the CWM recovery u just installed
-after it loads up (GO!GO!GO!) go down to the "mounts and storage" option that is third from the bottom and hit the call key.
-once there go to the last option "mount USB storage" and hit the call key.
-give your PC a few moments to recognize the sd card for your device and choose to open it when your PC prompts with the regular file explorer or just find it and double click on the newly recognized drive (sdcard) if your PC doesnt auto prompt you.
-now the new drive (sdcard) should be empty (depending...) then just find the desired rom you chose to use, right click on it and copy.....then over to the new drive (sdcard) and paste. might take a min or two depending on the roms size
-once the copying is complete hit the call button to "unmount" your sdcard then the back button on your device till your back at the CWM main screen
-now go to the fifth option down and "install zip from sdcard" and hit the call button
-now select the second option "choose zip from sdcard" and select the zip file you just copied to your sdcard. then it will begin to install the rom and all rom install times vary by build. some take a minute, some seem like they take forever.
-once installation is complete hit the back button till your back at CWM main screen and choose the last option which is to "power off"
-then tap the power button(if u unplugged it from usb otherwise it wil reboot by itself) to turn on your device and give it some time for the initial boot and load as it has to set up everything u just installed. subsequent boot wont take as long but again it can all vary from rom to rom.
-after initial load and a successful bootup you should arrive at ether the lockscreen or a startup screen. give the rom a few more mins to settle and dont hit any buttons. then unlock the device or skip through the startup options and get to the home screen. maybe give it another min to settle the launcher and the last bit of data and resist the urge to mess with the features. your gonna hate this but hold down the power button and select power off device from the popup menu. i know it sucks but it is best practice when flashing roms. after device shuts off wait a few seconds and turn it back on and let it reboot. should be faster this time and when u get to your lockscreen simply give it a few seconds to settle again, unlock and go to main launcher a wait a couple more seconds for it to finish settling and.....have fun! (every time i restart my device for any reason i will always give it a few moments to finish loading up before just blazing away with the apps)
WOW! maybe its not so abridged after all, but oh well tried my best to be as clear as possible so people can utilize their HD2 to its fullest potential.
HOPE THIS HELPS AND IF INDEED I HAVE PLEASE HIT THE THANKS BUTTON
Click to expand...
Click to collapse
Thanks
help needed complete noob
Hi all...total noob in need of expert advice...i have a htc hd2..it had windows 6.5 so upping to android hopefully. the step I am getting stuck on is installing from memory card. radio is 2.5,magdlr 113, clockwork is installed and spl 2.08.hspl.
What I am getting is the following.
Installing: /sdcard/.android/update.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(bad)
Installation aborted.
I have been trying for a week with no success.. Help.
Thanks in advance.
It could be a corrupted zip. Try downloading again, if you've not tried that.
Sent from my GT-I9100 using Tapatalk
Hi..Thanks for the reply. I have downloaded many firmwares and still no joy.Rather annoying really as its just the last step and really need to finish it off. Anyone having a android firmware I could download? Again thanks in advance.
Finally managed to put android 2.2 on, don't know how but it is on there...but no connection to the internet, it says on the setting for mobile network no connection.
If someone could list how exactly to put android on my hd2 in lamans terms (lol) I would really appreciate it..i.e. what to flash first and so on.
I dont know if you read the following guides but they are pretty awesome. Follow the first link in order to get 2.2 on. I know you said you did it but I would do it again since I dont like starting in between steps, rather do it start to finish. Follow the second link to put another ROM on.
http://forum.xda-developers.com/showthread.php?t=893948
http://forum.xda-developers.com/showthread.php?t=1044830
Today I boot RT into advance boot mode,
and then I launched the command line.
I run diskpart and then use 'clean' to cleaned the disk...
I though MS will stop me to clean the disk, but it seems that I'm wrong..
Now surface can't boot, I can't get it into recovery mode.
What can I do now? Return it to MS?
What happens if you try to turn it on?
So what does it show now when you turn it on?
Some error message from the UEFI 'bios' ?
Clean just zero's the fist sector
Since this is a GPT disk, it merely has a single protective partition table entry (type EE)
(although might nee a complete good copy of the sector if it is checksummed etc as part of the secure boot)
If you could get a copy of the required sector
and
If you could find a way to write it to the disk
then it would be fixable
But since there is no recovery OS we can boot (secure boot) via USB, your stuck
There should be some way of making a recovery USB...
TheEdge24 said:
There should be some way of making a recovery USB...
Click to expand...
Click to collapse
There is.
Desktop > Control Panel > System and Security > File History.
Tap "Recovery" at the bottom of the left pane, and you'll find an option to "Create a Recovery Drive."
It copies the Recovery Partition to a flash drive and makes the flash drive bootable for using in the Advanced Startup option.
I am having similar issue, Word froze and only way I can come out of it was to close desktop app. Metro was still working fine, but now when I start my surface it is stuck on "Surface" logo screen and nothing happens. Any ideas?
TheEdge24 said:
What happens if you try to turn it on?
Click to expand...
Click to collapse
If I turn on it, it will show 'Surface' logo, and then shutdown...
I have a message:
The operating system cuoldn't be loaded because the system registry file is missing or contains errors.
File:\windows\system32\config\system
"Error code: 0xc0000225".
Update
Mayur said:
I am having similar issue, Word froze and only way I can come out of it was to close desktop app. Metro was still working fine, but now when I start my surface it is stuck on "Surface" logo screen and nothing happens. Any ideas?
Click to expand...
Click to collapse
Spoke to Surface support (UK) today and they are sending out replacement unit.
If you can boot from a USB key some way, I could make an ISO of the recovery partition for you.
TheEdge24 said:
If you can boot from a USB key some way, I could make an ISO of the recovery partition for you.
Click to expand...
Click to collapse
Culd you make it for me too? I'll try to boot.
Thanks in advance.
TheEdge24 said:
If you can boot from a USB key some way, I could make an ISO of the recovery partition for you.
Click to expand...
Click to collapse
I would really appreciate it if you could also send it to me. My Surface is still not able to recover itself from the integrated recovery partition
Alexvsv said:
Culd you make it for me too? I'll try to boot.
Thanks in advance.
Click to expand...
Click to collapse
xray84 said:
I would really appreciate it if you could also send it to me. My Surface is still not able to recover itself from the integrated recovery partition
Click to expand...
Click to collapse
Check your Inbox
Hold VOLUME DOWN while turning on the device to boot from a USB device.
TheEdge24 said:
Check your Inbox
Hold VOLUME DOWN while turning on the device to boot from a USB device.
Click to expand...
Click to collapse
Hi.
I also have a problem with booting my Surface RT and I think this could work.
Can you send me this iso as well?
I would be very happy for your assistance.
jernej5 said:
Hi.
I also have a problem with booting my Surface RT and I think this could work.
Can you send me this iso as well?
I would be very happy for your assistance.
Click to expand...
Click to collapse
I managed to get recovery USB for Surface RT but I still can't recover anything at all.
Booting from USB does me give option of choosing language and keyboard but then it just shows advanced boot screen.
Hard reset does not work because it can't start it due an error. Same goes for refresh.
Is there a way to fix this, because I'm in Slovenia and will not travel to America anytime soon.
It seems that I'm stuck in a loop. I've tried 2 different recovery USBs from 2 different Surface RT devices. While my Surface is able to boot into the recovery screen on its own (without a USB), I still tried the USB method.
Here are the steps that I'm attempting:
1. boot Surface from USB (VOLUME DOWN + Power)
2. it starts to read data from the USB drive
3. It shows a new screen "Select language"
4. I select English
5. After that it shows another screen: "Select keyboard layout"
6. Once that is selected, I'm taken back to the basic "Choose an option" screen, where I have:
- A) Continue
- B) Use a device
- C) Troubleshoot
- D) Turn off your PC
I've tried all the options but nothing works.
6.A) Tries to repair but fails
6.B) Use a device takes you back to step 1 (loop). Btw… If I boot without a USB and select USB as a recovery method, I still get into the same loop
6.C) Selecting troubleshoot and then Reset your PC actually gives me another option: "Choose a target operating system" with only Windows RT as an option. If I select this, I get »There was a problem reseting your PC« after a few seconds.
I went into the Command Prompt (Troubleshoot -> Advanced options) and looked at the diagnostics log (c:\windows\system32\LogFiles\Srt\SrtTrail.txt). Everything seems to be OK it shows no errors and there is a weird text which says »Startup repair has tried several times but still cannot determine the cause of the problem«.
One thing that does seem odd to me is the »disklayout.txt« file in the same directory. This seems to be an output file of DiskPart. It shows all the disk and says »DISK 0« selected. Then it shows all the volumes on Disk 0 and I have:
Volume 0 | C | Windows | 24 GB
Volume 1 | | Recovery | 300 MB
Volume 2 | | SYSTEM | 200 MB
Volume 3 | | Recovery Im | 3600 MB
What's strange is that it says »VOLUME 1 is the selected volume«. Shouldn't this be Volume 0? Or even 2 or 3?
And ideas? Is there any way to flash the contents of the USB drive to the recovery disk? Or to even flash the C partition? Or… to make the C partition bootable again (because I think this may be the core problem)
As I said, I'm from Europe and bought my Surface in the US last week. There's no realistic way of me returning it any time soon.
Are there any files on "Volume 3 | | Recovery Im | 3600 MB"
diskpart
select volume 3
assign letter=R
exit
dir r:
should be an install.wim maybe under \sources ?
similar what are on Volume 1 (Recovery)
probably a boot.wim etc
which is the same as the USB contents
xsoliman3 said:
Are there any files on "Volume 3 | | Recovery Im | 3600 MB"
diskpart
select volume 3
assign letter=R
exit
dir r:
should be an install.wim maybe under \sources ?
similar what are on Volume 1 (Recovery)
probably a boot.wim etc
which is the same as the USB contents
Click to expand...
Click to collapse
Thanks for the answer…
Tried to mount both volumes and here are the results:
On Volume 3 (R ) I only have the »RecoveryImage« folder, which contains:
CreatePartitions-UEFI.cmd
install.wim
ResetConfig.xml
On Volume 1 I have:
File: Recovery.txt (empty file; 0 Bytes)
Folder: Recovery (empty folder; no files)
Is there something wrong with Volume 1?
The contents of the USB file are more similar to Volume 3…
Any further suggestions?
The good news is install.wim is the full OS and Apps
(I assume its about 3-5GB)
From the recovery cmd prompt, if you type imagex (Return) does some app run and show help?
That's the app we need to reapply/reinstall the image
However we don't want to rush it as there's only one chance !
No correction, have lots of chances if we can boot from USB and provided we don't loose this recovery image volume and contents
On Volume0 (windows, 24GB) I assume you have a 'normal' Windows like filesysytem
That is probably 99% good still
UPDATE - That volume might be encrypted and might not be able to read it from usb boot ?
Its probably the boot info on Volume 2 or a few files on Volume0 that are the trouble
---------- Post added at 05:42 PM ---------- Previous post was at 05:36 PM ----------
the commands would be something like
imagex /apply r:\recoveryimage\install.wim 1 c:\
bcdboot c:\windows
But before doing that
can you give the system volume a drive letter eg s:
and try
bcdedit /store s:\efi\microsoft\BCD
---------- Post added at 06:14 PM ---------- Previous post was at 05:42 PM ----------
Also check the contents of the system drive (s: )
especially
\efi\boot\
\efi\Microsoft\
xsoliman3 said:
The good news is install.wim is the full OS and Apps
(I assume its about 3-5GB)
From the recovery cmd prompt, if you type imagex (Return) does some app run and show help?
That's the app we need to reapply/reinstall the image
However we don't want to rush it as there's only one chance !
No correction, have lots of chances if we can boot from USB and provided we don't loose this recovery image volume and contents
On Volume0 (windows, 24GB) I assume you have a 'normal' Windows like filesysytem
That is probably 99% good still
UPDATE - That volume might be encrypted and might not be able to read it from usb boot ?
Its probably the boot info on Volume 2 or a few files on Volume0 that are the trouble
---------- Post added at 05:42 PM ---------- Previous post was at 05:36 PM ----------
the commands would be something like
imagex /apply r:\recoveryimage\install.wim 1 c:\
bcdboot c:\windows
But before doing that
can you give the system volume a drive letter eg s:
and try
bcdedit /store s:\efi\microsoft\BCD
---------- Post added at 06:14 PM ---------- Previous post was at 05:42 PM ----------
Also check the contents of the system drive (s: )
especially
\efi\boot\
\efi\Microsoft\
Click to expand...
Click to collapse
What do you mean with "However we don't want to rush it as there's only one chance !"?
1. To start off, make sure your tablet's battery is fully charged.
2. Download the 'T230NU Root Kit' & 'Samsung USB Driver' files to your PC & extract them.
3. Locate the 'Samsung USB Driver' file and install it on your PC.
4. In your Tablet go into Settings/General, scroll down and click on 'About device'. Look for where it says 'Build number', you need to TAP that continuously until it says 'Developer mode has been turned on'. You should now see 'Developer options' on top of 'About device', click it and checkmark 'USB Debugging'.
5. Connect the tablet to your PC with the USB cable.
6. In your PC locate the 'UPDATE-SuperSU-v2.46' file and copy it to your Tablet (Root directory of your tablet is fine or place it anywhere you want, remember the location and DO NOT EXTRACT IT, just copy it as it is).
7. Disconnect the tablet from your PC & power it off.
8. Put your Tablet into 'Download Mode' (push all these three buttons at the same time; Power/VolumeDOWN/Home) As soon as you see letters on the screen IMMEDIATELY hit the 'VolumeUP' button while letting go of the other three buttons). If you did it right, it should now say 'Downloading...', if not then power it off and try again.
9. Connect the tablet to your PC with the USB cable.
10. In your PC locate the 'Odin3 v3.09' file, right click it and choose 'Run as administrator'. Once the program opens it should automatically detect your tablet--it should say 'Added!!' under Message. Now click on the button that says 'BL' and locate the 'openrecovery-twrp-2.8.0.1-degas' file, select it and click open. Make sure to uncheck 'Auto-Reboot' and then click 'Start'. When it's done you should see the word RESET in blue on top & it should say 'RES OK!!' under message.
11. Disconnect the tablet from your PC & power it off by holding down the power button for at least 10 seconds.
12. Now that your tablet is off, go into 'Recovery Mode' (push all these three buttons at the same time; Power/VolumeUP/Home) As soon as the Samsung logo comes up let go of ONLY the power button, then as soon as you see the 'Teamwin' logo IMMEDIATELY let go of the other two buttons. If you did it right then you should now be inside the 'Teamwin' program, if not and your device booted up normally then you need to try again starting from step #7.
13. Click on 'Install' and locate the 'UPDATE-SuperSU-v2.46' file--depending on where you saved it in your tablet on step #6, now at the bottom where it says 'Swipe to Confirm Flash' swipe it to the right, wait until it is done flashing and then choose 'Reboot System'.
14. Before you start jumping for joy, lets first check for Root status (once your tablet boots up, go to the play store and download an app called 'Root Check',
install it, open it & it should say that your device is 'ROOTED').
15. Congratulations! You now have full control of your device.
Are you aware this is now the third how-to-root guide thread made for this exact method, for this model?
First
Second
its same device and same twrp so its for NU and no NU versions, works on both
I've been using the Acheron ROM for more than a year now and it has been a great experience.
AmelieCo said:
I've been using the Acheron ROM for more than a year now and it has been a great experience.
Click to expand...
Click to collapse
isnt acheron thread...... but ive used it too for 10 months now
How do I uninstall this root please?
blairrad said:
How do I uninstall this root please?
Click to expand...
Click to collapse
You can check the uninstall option in superSu app or Re-install your firmware(or install any rom). I also think there might be some kind of superSu-uninstaller script/app somewhere in forums.
how to root galaxy tab4, Model: SM-T230NW, T230NWBMW1ARB1
If you dont have full ROM backup from your device or official ROM, dont do anything in terms of modding but to install vcom drivers (in my case they wont work without Virtual Serial Port Drivers) for bootloader, and adb/fastboot drivers, make sure theyre working, install Miracle Box / SPFlashTool (or similar ?) to be able to backup/flash your ROM/partitions from/to your device.
Check if it works for you (ie backup your ROM and try to flash something (cache) back.
Now when people are scared enough I want to tell you that it is almost impossible to kill (brick) your MTK phone, it happens mostly when people flash something that is not suppoused to be flashed (something from another device), the worst case if you flash wrong preloader or erase preloader but even after this there is a chance for resurrection. it takes time and efforts though.
++++++++++++++++++++++++++++++++++++
This is TWRP 3.2.2.0 recovery for Chuwi hi9 Pro.
Partitions available for backup:
boot, recovery, system, vendor, data (not incl. data/media = internal sd), cache and "para" (if you have got "recovery loop" - flash "para")
.img flashable - boot, recovery
look for detailed instructions for coomon things in other treads, like
- how to install bootloader vcom drivers and adb / fastboot drivers
- How to work with adb / fastboot command from your computer cmd window.
- how to use Miracle Box / SPFlashToll
This is detailed instruction how to make SPFlash backup out of your phone though Miracle Box does it in one click (well, almost)
- how to unlock bootloader (fastboot mode)
- how to use toilet paper (manual mode)
- how to install twrp recovery
- how to root
Unlock, Install, Root in one post
++++++++++++++++++++++++++++++++++++++
So, main point of this thread is TWRP, youll need:
- roll of toilet paper
- spflashtool backup (just in case)
- backup of your data (if you care) - your data will be erased during the process.
- unlocked bootloader
- twrp image
If something went wrong (highly unlikely), but "if".
Worst case scenerio: your phone will not boot into system / recovery
Solution: reflash (fastboot or flash tool): boot / recovery / system
Worst case scenerio: flash factory ROM (SPFlashTool)
Steps to do when you have all knowledge and all files ready.
IN YOUR CURRENT SYSTEM
In settings->System->About tablet -> click several times "build number" untill you see message "now you are developer"
In settings->System->Developer options: Enable USB debugging and OEM Unlock, connect cable
REBOOT INTO FASTBOOT
Power off, Power on holding "vol+"
Youll see black screen with 3 strings of menu (very small font):
- recovery
- fastboot
- system
use "vol+" for navigation, use "vol-" to confirm your choice (fastboot)
OR from your pc cmd window (shift+right click on adb folder -> choose "open command window here") type: adb reboot bootloader
press Enter
UNLOCK BOOTLOADER
on your pc (if cmd window is not ooened yet: shift+right click on adb folder -> choose "open command window here") type: fastboot oem unlock
press Enter
watch your phone and pc screen for messages
if you have vision problems, make sure you have a magnifying glass.
INSTALL TWRP
download hi9pro_twrp.img to your /adb folder
from the same cmd window type:
fastboot flash recovery hi9pro_twrp.img
*
Reboot into twrp and flash Magisk
*
Basically this is it
There is no command from fastboot to reboot into recovery (correct me)
You can power of, power on holding "vol+", choose "recovery" from menu
command to reboot into system: fastboot reboot
+++++++++++++++
* NEW *
Infect_Ed has posted TWRP recovery that he has compiled from source. DOWNLOAD FROM HERE
We don't know how to make twrp recovery work with encrypted data partition.
Read next paragraph if you are OK to trade security (encripred userdata) for functionality.
++++++++++
==========
In case you want to have your userdata decrypted (and full functional twrp), use following steps:
*** Please, note all userdata AND internal SD will be wiped during the process***
If you care
Save Internal SD card content to your ext.SD or computer
Make a Titanium backup of user apps (check Enable external data backup in Titanium settings)
If Titanium fails to write to your ext.SD than change Titanium backup folder location to int.SD
and after backup is done copy Titanium backup folder to ext.SD or PC.
Disable any passwords/pins from Settings->Security & Locations
(I know they are stored in /data/.. and will be erased anyway but just in case)
- Reboot into TWRP
- ftom TWRP -> Wipe ->Format userdata -> Confirm with "yes"
do not reboot into system
- flash encryption_prevener_hi9pro.zip to prevent system automatically encrypt userdata (it is used to insert modified fstab.mt6797 into vendor/etc)
- reboot system
- restore your int.SD content and apps
============
Link to official ROM/Firnware
*** Read this if you have Recovery Loop - no matter how you boot (buttons, from twrp recovery or from adb/fastboot shell) your device you always end up in TWRP recovery ***
- download 2018-09-29--para.zip
- unzip it - there is a folder 2018-09-29--para with 3 files inside
- connect your phone in twrp recovery mode to your computer
(you may need to turm "enable mtp" option in TWRP->mount)
- copy that folder into your sd card, the path is : TWRP/Backups/Hi9Pro
- click "Restore" (on the next screen make sure ExtSD is chosen as backup path)
- check checkbox "para", run restore, reboot
explanation: para is a partition contains last issued kernel reboot flag(command), like "reboot to recovery, reboot to system, etc." I think there is one flag that tells to kernel something like "reboot to recovery, do something untill its done", since this "something" never done, device reboots into recovery over and over again. This happend to me when I tried "factory reset" command from android settings, so android have sent my device into recovery mode where that "factory reset" command had to be performed but never done because its now not stock recovery but twrp.
**** If you have following problems:
Unknown Baseband -> Unknown IMEI -> NO sim card -> NO cell network
Look here first
****
***** If you came here from there.*****
and you are following their instructions, please, note, step 7. Unlock bootloader : DO NOT DO command "fastboot flashing unlock", just skip it.
Also, try to avoid "fastboot boot recovery.img" command to reboot into recovery (just use physical buttons for reboot). I'm not sure but something caused "recovery loop" in one case at least.
****** back-to-encr.zip if you want to encrypt your decrypted userdata (original fstab.mt6797 will be flashed, no data loss, you will not be able to mount userdata in TWRP, first boot may take long time due to encryption process - 10-60 min- depends how much data do you have)
******* twrp_recovery_chuwi-hi9pro_infectEd-XL is same Infect_Ed recovery adopted for our screen.
Hello. I made a mistake last week. I flashed accidently twrp with a scatter File from the HI9 Air through the spflashtool on the Hi9 Pro. Now it doesnt turn on etc. Is it hardbricked or can i still get it back to life?
No, its not complitely bricked if flash tool still recognizes your phone in bootloader mode. Most likely youve made same mistake I did. Depends of how you flashed that recovery - recovery only or full sisyem WITH new recovery. most likely you flashed only recovery partition. than, first, try to reflash backed recovery & next to recovery ("para") partition. in "download only mode" therell be an error "pmt has changed" than try "format & download" and "firmvare upgrade" - use scatter file contained only those two partitions. if you didnt make a backup ill put here that "para" partition and you can use hi9pro twrp img. in case this wont work, you may want to reflash the whole rom. We need to find factory rom image (from Chuwi or someone who did a back up prior he entered his credintals - thats another mistake Ive made Ive dumped a rom with all my logins information). if I have time I'll try "factory reset" to make a backup from "clean" system.
again, its almost impossible to brick mtk completely. even if flash tool doesnt recognize you phone (dead battery) there is a jump-pins method.
upd. Just looked @ Air scatter and found that Air recovery partition size is same as Pro (~16mb). now I dont know haw was that possible to overwrite next to recovery partition(s) and I think I used same Air img as you did and I've got size warning message when I flash it. anyway here is archive with scatter for recovery and para. just add twrp hi9 pro recovery (rename recovery.img to recovery.bin) and try to flash.
I didnt made a Backup (stupid me) i flashed the recovery file with a scatter file. When i plug the device in the pc the USB sound comes and its recognized as MEDIATEK USB PORT (COM8), but its removed automatic (USB Sound for disconnecting) The Screen stays black. So i have to wait for a Rom and a scatter File then?
---------- Post added at 19:50 ---------- Previous post was at 19:39 ----------
I tried your idea. I got an error Message: "Status Preloader Invalid" The Preloader File Format is invalid.
you know how to use flash tool , first you have to press "download" THAN connect usb cable.
but this is a good sign (pc recognize something), you may want to google for something like "unbrick mtk 6797 sp flash tool" for more info
this is archive w. 4 1st partitions (incl preloader)
Ive gotta go. Dont smash your tablet its 100% repairable, well 99.999%
thats how it looks
https://photos.app.goo.gl/9EK8vTwcTS3fDf1a7
---------- Post added at 20:21 ---------- Previous post was at 19:58 ----------
Still get an error Message for the PRELOADER. I read some Tutorials and dont find a Problem in my setup or my doing. Sucks :-/ But Thank you very much for your help
is it "MEDIATEK USB PORT (COM8)" appears for a second in the devices tree or "mediatek preloader usb vcom (android) (com8)"
if second, then everything is OK with the connection.
if its exactly MEDIATEK USB PORT (COM8) then there is something wrong
try to connect cable with diff buttons combination, i.e. "vol+" + connect cable .
try different "download agent" (DA_PL.bin ?)
Though I also used AllInOne_DA and flash tool V.5.1728
also, you might find Miracle Box Tool is easier to use
try "read" option first to backup your current rom
View attachment 4598709
I shoul ask this first:
- have you ulocked bootloader ?
- when your press "power" and "vol+" after some wait is anything appears on the screen
(boot menu: fastboot, recovery, regular boot) ?
- when your press "power" and "vol-" after some wait is anything appears on the screen
(chinese written) ?
Good Morning.
Bootloader is unlocked, no matter which key combinations ill try the screen stays black. When i have the usb cable at the PC (no matter which Port or cable) it the plugin - plugout sound plays every few seconds/minutes (not the same time in between). It is recognized as "MediaTek USB Port (COM4)" (different PC i tried). When ill try to install the vcom drivers i get the message that the best drivers are already installed and that are the mediatek usb port driver.
Image of the device manager: https://ibb.co/erkW6e
zelipukin said:
is it "MEDIATEK USB PORT (COM8)" appears for a second in the devices tree or "mediatek preloader usb vcom (android) (com8)"
if second, then everything is OK with the connection.
if its exactly MEDIATEK USB PORT (COM8) then there is something wrong
try to connect cable with diff buttons combination, i.e. "vol+" + connect cable .
try different "download agent" (DA_PL.bin ?)
Though I also used AllInOne_DA and flash tool V.5.1728
also, you might find Miracle Box Tool is easier to use
try "read" option first to backup your current rom
View attachment 4598709
I shoul ask this first:
- have you ulocked bootloader ?
- when your press "power" and "vol+" after some wait is anything appears on the screen
(boot menu: fastboot, recovery, regular boot) ?
- when your press "power" and "vol-" after some wait is anything appears on the screen
(chinese written) ?
Click to expand...
Click to collapse
---------- Post added at 07:34 ---------- Previous post was at 07:07 ----------
zelipukin i made a short Video about the behavior. The Device seems to activate when i push vol+ or power, but it looses connection when i stop holding the button or sometimes even when i hold the button.
https://drive.google.com/file/d/1m3YLrH5ZaVLttcSfDxx3RvL0DaXPcxzk/view?usp=sharing
...thinking
Just tried...seems like backups I made(and posted here) from Miracle Box is incompatible with SP Flash.
SP Flash doesn't like this and doesn't like that when tries to restore those backups but Miracle Box restores individual partitions or whole ROM w/o problem.
SP Flash is so inconvenient if you try to make a backup ... its also inconvenient when you try to restore.
Where did I get that Miracle Box for free ?
Let me figure out something...
....
This is something beyond my understanding but let me to describe what I did
- in SP Flash I choose scatter file and recovery.bin (like I sent to you)
- download only - no go
- download+format - no go
- firmware update - warning message about wrong partition size or something like this - Ignored - Flashed
- Bricked again (like yours - black screen - that's it)
- OK, I have several backups. Tried all of them - none of them works... except one
- Flashed that backup with SP Flash - no questions, no warnings, no errors - device came alive
- Flashed only recovery.bin - everything went fine
- Tried to find difference btw different backups - but couldn't find any
- So I tried to flash those files (to try 3.zip) several times and everything went OK, so this is 100% working backup.
Try it and see what happens, then we can go somewhere else. I still suspicious about those MTK Usb Com(8) instead of preloader usb. Also if you used "Firmware upgrade" option once, I beleive you'll need full ROM flash. Keep looking for it @ Needrom.com.
Strange things happen. Couple years ago I lost MTP connection with my MiMax. I tried everything possible but no luck - have to use UMS Enabler so I can read/write ExtSD at least, but MTP works with Chuwi.
I spent numerous hours trying to connect Chuwi in preloader mode until found that solution about Virtual Serial Port drivers.
Thanks for your help so far. Seems like my Device is half dead after 2 Hours of use
I'll tried to change the Drivers for the mediatek, it shows the device now with the preloader, but i think it doesnt work right. when i change the usb port it comes back as MediaTek USB Port (COM4). I made you a 15 Second Clip of the behavior.
https://drive.google.com/file/d/1m7wyIlIYJLN7ikmgUTzHBJtBdbZQrYaa/view?usp=sharing
Really weird. :-/
---------- Post added at 14:55 ---------- Previous post was at 14:40 ----------
and no chuwi hi9 pro rom at needrom yet. :-/
Sorry, haven't seen there is second page of this thread.
Saw a video where one guy showed how he changed drivers to right ones.
Main idea is in that short period of time when wrong drivers appear click right mouse button and choose "uninstall drivers"
after this in his video in next attempt system found usb vcomm by itself. worth to try
or other videos where guys catch a moment when this port appears in device tree but choose "update drivers"-> "browse my computer..."-> "let me pick from a list of device drivers" -> remove flag from "show only compatible.."->
I cleaned system, removed apps,accounts, etc. and made a backup of a "clean" ROM (well, almost). will put somewhere when/if I get good wifi somewhere (its 3GB.. w/o data partition) I'm on slow & limited mobile network.
but I don't think you need anything but recovery & para if you never used "format" & "firmware upgrade"
i think i used the upgrade one, after download only didnt work.
Ill tried the same method with changing drivers.
I will sit this one out, till you have uploaded the rom
Thanks for helping me out!
zelipukin said:
Sorry, haven't seen there is second page of this thread.
Saw a video where one guy showed how he changed drivers to right ones.
Main idea is in that short period of time when wrong drivers appear click right mouse button and choose "uninstall drivers"
after this in his video in next attempt system found usb vcomm by itself. worth to try
or other videos where guys catch a moment when this port appears in device tree but choose "update drivers"-> "browse my computer..."-> "let me pick from a list of device drivers" -> remove flag from "show only compatible.."->
I cleaned system, removed apps,accounts, etc. and made a backup of a "clean" ROM (well, almost). will put somewhere when/if I get good wifi somewhere (its 3GB.. w/o data partition) I'm on slow & limited mobile network.
but I don't think you need anything but recovery & para if you never used "format" & "firmware upgrade"
Click to expand...
Click to collapse
Just a few questions after using Hi9 Pro for about a week:
1) Where is the microphone ? Is it the small hole under the volume button ? (Strange position)
2) On the back side the two metallic stripes separating the plastic of the metal body are they something like antennas ? (LTE or WiFi or both ? )
3) What is the version of Bluetooth ? (4.0 or 4.1 or 4.2 ? )
4) Is it possible to use some kind of fast charging with a suitable charger or software app (firmware update) ?
MediaTek has a technology called "Pump Express" or something like that...
5) Do you have sudden, unexpected pop-ups of full screen advertisements while you are working with your tablet ?
How do we get rid of them ?
6) How do I find the LTE band the tablet is actually using while it's in use ?
I don't mean the table of supported bands, I mean the active band while using it.
Thanks!
1) looks like and its logical bc its close to mouth than if they put it in the bottom.
2) not sure, but most likely
3) according to this https://www.manilashaker.com/mediatek-helio-x10-vs-x20-vs-x30-chip-comparison-difference-specs/ its 4.2
4) too many different opinions, cant find the truth
5) none so far
6) you can try to find some info from mtk engineering mode *#*#3646633#*#* from you dialer
but its not intuitive and complicated
zelipukin said:
1) looks like and its logical bc its close to mouth than if they put it in the bottom.
Click to expand...
Click to collapse
Yes, it is a very small hole at the bottom right as you hold it, with a size of the edge of a needle!
zelipukin said:
1)3) according to this https://www.manilashaker.com/mediatek-helio-x10-vs-x20-vs-x30-chip-comparison-difference-specs/ its 4.2
Click to expand...
Click to collapse
Thank you.
zelipukin said:
5) none so far
Click to expand...
Click to collapse
But how did you do that ?
Did you add an Ad Block after rooting the tablet ?
The kind of ads I get, is more of suggested apps to install from Google Play.
It is literally bombarding me with an exhaustive rate.
I went to settings to "advertisements" of Google and it says that I can't turn it off.
Could it be some app that I installed that is spamming me this way ?
Can you suggest something to stop it ?
zelipukin said:
6) you can try to find some info from mtk engineering mode *#*#3646633#*#* from you dialer
but its not intuitive and complicated
Click to expand...
Click to collapse
I installed LTE Discovery and although I'm not rooted it seems that it works OK and it's showing me the bands.
The signal strength is lower than a mobile phone at the same position, same time, same provider.
Do you have an equal signal strength like your mobile phone ?
One more question:
7) Is it feasible for a developer to build a custom ROM for this device if he wants to or there are certain restrictions forbidding custom firmware ?
Is there any chance for a custom ROM in the future, because I don't think Chuwi will upgrade to 8.1 or better Android.
Thank you!
Regarding ads - I didn't do anything, I looked @ settings->google->ads and I can turn it on and then off w/o problem
Also I culdnt find any junk software so far, the phone came from GearBest factory sealed. I didn't do any system modifications except installing Magisk and modules - ExCard Access Enabler, init.d injector, Magisk SELinux Manager, ViperX (slightly better sound from speaker)
I didn't try the device as a phone, though it fit in a pocket of one of my jeans. I'd like to try but my current phone (miMax) has a micro sim.
7) Depends how popular is this device and who (developers) got it. Also, depends if this chipset is used in many other similar models (popular, prefferable) than you don't need to be a real "developer" to port ROM from a similar device and if you find that divice X is updated to 8.1 there is a chance someone will make a port (or you can try to do it yourself). I'm not a big fan of immediate upgrading to a newest version, for me they usually bring more limitations (you cannot let apps to modify files on your own sdcard f.e.) than benefits. I still use >2 y.o. andr. 6.0 custom rom on my MiMax.
zelipukin said:
Regarding ads - I didn't do anything, I looked @ settings->google->ads and I can turn it on and then off w/o problem
Also I culdnt find any junk software so far, the phone came from GearBest factory sealed.
Click to expand...
Click to collapse
Me too, I got a sealed and clean tablet from GearBest but If you look closer to that setting, it says that you can turn on or off the specialized ads for you, but you can't close ads completely.
For example, during web browsing do you see ads inside various sites ?
Or when opening apps on your tablet ?
I think we need an ad-blocker for this.
zelipukin said:
I didn't try the device as a phone, though it fit in a pocket of one of my jeans. I'd like to try but my current phone (miMax) has a micro sim.
Click to expand...
Click to collapse
I meant for mobile 4G data, not as a phone.
In my country we have three bands for LTE:
B3, B7, B20.
When the tablet rotates between 3 and 7, I have poor to zero signal.
But I saw with LTE Discovery that when it switched to 20 then the signal is very good.
So, with the help of MTK Engineering I disabled 3 and 7 bands and everything seems OK now.
I hope B20 to be used everywhere near to me.
zelipukin said:
7) Depends how popular is this device and who (developers) got it. Also, depends if this chipset is used in many other similar models (popular, prefferable) than you don't need to be a real "developer" to port ROM from a similar device and if you find that divice X is updated to 8.1 there is a chance someone will make a port (or you can try to do it yourself). I'm not a big fan of immediate upgrading to a newest version, for me they usually bring more limitations (you cannot let apps to modify files on your own sdcard f.e.) than benefits. I still use >2 y.o. andr. 6.0 custom rom on my MiMax.
Click to expand...
Click to collapse
I'm not familiar with Android internals so much, I am only using a Note II with TWRP and a custom 7.1.2 ROM and I'm missing some simple customizations not available with out Oreo 8.0 stock ROM.
I haven't even tried yet your first post regarding rooting and all the others because I'm not so sure where to find these tools and how to use them.
It could help a lot when you find some time to add more descriptions and links in your first post, if possible like Hi9 Air thread.
Thank you!
I dont know how and why, but I dont have any agressive advertisements. Checked Opera I'm using for webbrowsing - even "block popups" option wasn't checked. Had to download app yesterday (AutoNotification) from gp store and when I started it in a "free mode" there was a message like "to use this app in a free mode you have to agree to see ads", clicked "ok" , then message "downloading..." appeared...and nothing, no ads. I connect my tablet to the internet through my phone but dont think that matter.
Just a few more short questions:
8) Is there any other way to wake up the device instead of pressing the red button ?
For example double tap or maybe using the volume buttons or any other way.
Because I'm afraid of pressing the same button again and again.
9) Does this device have a WiFi 2x2 MIMO ?
I haven't found any particular info on this.
10) What is the kernel of the ROM ?
Is there any GUI compatible like Kernel Aiutor to make changes or take a look at info for the device ?
Thank you!
Dragged my JXD S7800b out of drawer, stuck it on charger and charged up okay.
However, boots up but does not get past boot animation?! So I am looking into how to recover the device please?
Used RockChip Driver Assistant v5.1.1 to setup my windows 10 machine.
RockChip Batch tool v1.8 connects when device powered up but shows pink but not green indication (with no useful error reports), so I don't appear to be able to jam firmware on that route.
Not having much fun with RockChip Factory Tool v5.3 since most images I am downloading fail to load into that, other than what appears to be the official firmware from JXD. That tool otherwise appears only for editing images but not uploading.
I bumbled onto the recovery menu. What wasn't well documented on the steps to get there, so ended up with:
1) power up while holding down power and + volume.
2) display shows an android on it's side, guts opened with a ! and the text message "No command"
3) insert USB
4) the missing bit, hit - volume to scroll into menu
So I found an adb option but haven't installed any android tools as yet on my new machine.
I burnt an SD card with etcher, to use the update from external storage option, but I am guessing the etcher wants to build a boot disk and a boot disk is not wanted? Etcher reports the image will not be bootable in any event.
Reformated SD and copied image onto it in the end but neither apply update or update rkimage "found" anything on the SD card or found the image to be invalid (despite it coming from JXD site).
So, any links to how to set up the SD card for updating the firmware would be appreciated.
I guess also I would like to know the difference between an "apply update from external storage" and "update rkimage from external storage" is what please?
Also, any links to JXD_S7800B_RileyROM_1.2.1.zip seem dead, so has anyone a live link to JXD_S7800B_RileyROM_1.2.1.zip please?
Also wik, with the usb cable in and holding down power and + volume, a few seconds in and windows reports usb device unrecognised. I have installed, uninstalled and re-installed the drivers to now avail. Not sure this is a problem? The fact I can occasionally, rarely, not often enough but just enough to irritate, get a pink but not green light up on the Patch Tool hints the software can almost, but not quiet, enough to make my teeth grind, "see" the device LOL.
Cannot get adb driver going on Windows 10 despite the driver helper having supposedly Windows 10 drivers? Whether that relates to the unrecognised device is unknown but it looks like the Drive Assistant installs usb but not adb drivers, which seem to need a manual install.
UPDATE
=======
Still looking for the information above BUT managed to recover the device by doing a factory reset.