Database Develop

[Q] Any changes to the sdcard files will not take

editi guess sdcard is incorrect/confusing for my situation, it's the entire system up to root folders is stuck in a read-only type state.
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected]ost #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K

plasticsoldier said:
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected] #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
Click to expand...
Click to collapse
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2

thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed

plasticsoldier said:
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
Click to expand...
Click to collapse
I would suggest trying to restore down to WebOS 3.0. In that procedure you literally wipe EVERYTHING on the internal partitions in novaterm and start from absolute scratch. Therefore, if it a software issue you could solve the problem. However, if it is a hardware issue, you'd be kinda screwed.

Yeah, none of the methods I've ended up finding about this problem or other bricked problems are working at all.
i checked at work when i bought it, which of course the 11th was the year mark... but I do have android installed so even if i can get any chance of them honouring it so close they'll probably be like "oh you have android, that'll be $$$ for us to do anything. thanks!"
So I guess I now I have a paperweight with some features.

cdzo72 said:
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?

There is a thread in the General forum about how to restore and downgrade. Have you tried that thread ? It is usually a great way to try and get that last restore before sending it back to HP.
73 de VE6AY
Sent from my HP Touchpad, running the latest CM9 nightly, from the XDA Premium App

how are you adding and deleting files when in android? which version of android do you have installed? have you tried different rom versions? have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to? it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard? are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android? have you run "fix permissions"? Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.

sstar said:
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
Click to expand...
Click to collapse
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2

cdzo72 said:
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer, this would tend to suggest that the problem is software based corrupted or otherwise. I am trying to find a program that will allow me to read/format the Android partition on my windows computer and will let you know if come up with anything.
Regards

i guess i should change the title slightly.. it's not sdcard, but basically the entire touchpad contents. go to root and delete whatever i want and it doesn't matter. connect it and format with windows and it doesn't actually matter.
haxin said:
how are you adding and deleting files when in android?
Click to expand...
Click to collapse
i've added and deleted just by using mtp. i've also deleted the files on the android side with the video player (vplayer) i've installed es file explorer (which after restart is gone) and deleted with that. i've also gone into webos and installed internalz pro and deleted files that way, which it then seems to work until i of course do anything related to restarting.
some of the files i've put on, i've had it recognize briefly. so for the video file, start it, then it gets really choppy/glitchy playing it. so stop it, go back into the vplayer and it's back to the old stuff
which version of android do you have installed? have you tried different rom versions?
Click to expand...
Click to collapse
android version 4.0.3. nothing else will install. if i add files while in android, when i boot into cwm they are gone. if i mount usb in cwm and add them they stay briefly but when i try to flash them they fail.
have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to?
Click to expand...
Click to collapse
i have not tried adb yet, just not as familiar using it properly, i will give it a try though.
i am using windows 7 on my laptop currently. i do have a pc upstairs that i barely use that has vista, but i don't know how that would make a difference to the touchpad
it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard?
Click to expand...
Click to collapse
yeah as i put above i guess saying sdcard was a bit confusing/misleading (my bad, sorry!), i didn't really know what else to call it at the time or how to explain myself properly at first.
are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android?
Click to expand...
Click to collapse
i can move/delete/modify anything which has absolutely no effect to the device. i've used es file explorer and gone up to root and deleted everything and the system runs fine. says the system is empty with lots of free space (its the 32gb model) but restart or even go into recovery and everything is once again there.
have you run "fix permissions"?
Click to expand...
Click to collapse
i've run it a few times. just acts likes it's working and then says done. i've even gone into the mounts and storage in cwm and formatted sdcard/cache/data/system. does nothing at all in the end of things
Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
Click to expand...
Click to collapse
it was just something to try to get somewhere right. it never gets past 12%. always fails to reboot.
I am currently letting the battery drain and see if it dying and then being charged will do anything. probably not. but who knows. i talked to a "tech" on the chat support (i never mentioned android) who told me that having preware installed in webos causing it to become corrupt and they "don't knowledge of preware installed devices" exact words. no idea what that means haha don't have knowledge, don't acknowledge...
anyhow. i've not quite given up. i just don't really see it turning out any differently from the previous times. i do appreciate all the feedback and help very much though

ok so heres what I would try. First try flashing a new fresh rom. download one that you want to your computer like cm9 nightly or aokp or whatever you feel like. then boot into CWM recovery connect the touchpad to the computer via usb. then connect to the touchpad with adb. I'm not sure how to do this in windows because it's been so long since I've done it on a windows box, I always use linux.
adb has alot of options, you can move files to and from the device, you can uninstall or install app packages, and more. this way you can adb push the rom .zip to the touchpad's sdcard while youre in cwm recovery. this way you dont have to reboot the touchpad and risk having the file disappear, you can just go to 'install zip from sdcard' and then 'choose zip from sdcard' in cwm recovery after you adb push the rom, you should see it in the folder you pushed it to on the sdcard.
If you arent familiar with how to use adb from the command line or the terminal this might not make alot of sense and i dont know how better to explain it than that. Also yes windows 7 vs windows vista does make a difference there are issues with novacom installing properly, that's why you would have problems running acmeuninstaller or acmeinstaller2. if you look around you should find some videos or how to's that can probably explain it better. Hope this helps.
http://www.webos-internals.org/wiki/Novacom_with_Windows_7
http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-5.html

http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.

ve6ay said:
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
Click to expand...
Click to collapse
Probably the best suggestion yet given that everything else has been tried.
Good luck.

****EDIT****
Before you attempt the step above I have just noticed a difference between between cwm and. TWRP2.2 which I have installed on my Touchpad via goo manager. If I open recovery via goo manager and then select wipe it gives me 4 options cache, davlik, factory reset AND system which i think says will remove your rom . I don't see the forth option available with the regular cwm/clockwork. Just a thought.
All the best with whatever you try next.

sstar said:
Probably the best suggestion yet given that everything else has been tried.
Good luck.
Click to expand...
Click to collapse
this would work, however you have to fix you novacom/novaterm issues on your windows machine before you'll be able to do any of this. the reason acmeuninstaller, acmeinstaller2 arent working is likely because youre on a windows7 64bit box and Palm-sdk, the novacomd.exe, noverm.exe, and javaruntime apps and drivers arent setup right. just make sure you have the proper javaupdates on your computer then you can install preware in webos, preware has some nice tools that will delete the entire android install partitions, one is called 'remove android' and the other is called 'tailor' you run them from within webos. after you do that then in webos you should do a full device reset. you'll find it in the "info" tab under settings in webos. this will delete and reformat the whole /media ,(aka sdcard) partition. so you will lose all the files you have stored on both webos and android. that format will take a long time probably like 30 min or more. after thats done. reboot the hp and run webosdoctor. now i know for sure this will work because ive done it on mine. remember to put the touchpad in developer mode in webos first to install preware. you can do that by typing webos20090606 into the webos search bar and hitting enter. I'll put links from my box.com accou t to everything you need.
https://www.box.com/s/479acdb6ef9c99fc7b92
https://www.box.com/s/1aed4722990aad251570
edit: also I'm not sure if youre on the 16gig 32gig or 64gig pad, the webosdoctor that i linked is for 32gig wifi only US version. if thats not what you have then youll need to get the doctor for for specific touchpad. or you could create a webosmetadoctor but thats a whole nother project.

i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point

plasticsoldier said:
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Click to expand...
Click to collapse
ok no one will be able to help you fix this issue unless you give complete details of the problems. when you say " novacom/novaterm stuff doesn't work" we cant really help specific error details is what i need. I dont mind helping you fix this but you have to be a little more specific on exactly what,where, and how youre installing and running and mounting apps and directories.
your problem IS fixable but you need to slow down and really do things exactly step by step.
Ok so back to ./adb. now when you boot in to CWM recovery on he touchpad DONT do anything in CWM just plug it into the computer. do not mount it as a usb storage and dont mount or unmount the sd partition LEAVE IT.
you can then use ./adb from the command line or terminal on the computer to move the files to the touchpad' or install apk's uninstall apk's you name it. This will require that you know some linux terminal commands. for example to move a new rom zip to the internal sd card or into any other folder you can use ./adb push command to run a root shell on the android device itself you can use ./adb shell and then change folder and file properties from readonly to rw. this can all be done while the touchpad is patiently waitng in CWM recovery. this way when youre done installing or uninstalling apps from the device and moving flash zips to it, you can disconnect the .adb connection with ./adb disconnect or just type exit from the terminal till it closes. unplug it then you will be able to pick up the touchpad and install zip from the sdcard, keep in mind you dont want to choose 'apply u[date from sdcard' you want to use the 'install zip from sdcard option' you can read up more on how adb works. it is probally the most important part of hacking android.
with that being said. novaterm is the palm webos version of .adb. this is why when you boot into webos recovery to do things like acmeinstaller and acmeuninstaller2 the novaterm novacom and novacomd apps have to be installed correctly on the computer or else you wont be going anywhere fast. some screenshot examples of how it should appear below.
https://www.box.com/s/432e63a83215f00eea6a
https://www.box.com/s/970bc29542a05f98f036
https://www.box.com/s/63c0f656e8354f7f2d6a
https://www.box.com/s/cbe3266467ae8e3ebabe
https://www.box.com/s/005e56a61a178dd17fa4 some better resolution images.

Plasticsoldier said
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Yes there is
Firstly tailor does exist, it is a beta and the facility to dl must be enabled.
Read this and scroll down to Enabling beta test feeds and follow the instructions , when you get as far as using the Linux command you CAN copy and paste thank God.
http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true . After that reboot into Webos and launch preware. Go into managed feeds as per the instructions in the link above and install Tailor. Reboot again and the app will work. It looks very good actually.
But before attempting to actually use Tailor please read the article I have posted below it is only 7 pages long but will explain how to use Taylor properly as it is a powerful tool.
http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html
I have done all of this , this morning so if you have any problems pm me or ask in this thread.
I sincerely hope that this helps, it should be the answer to your problems.

@haxin: sorry, wasn't trying to be unhelpful when everyone is being helpful to me. I shall be more detailed in future responses. I think i was getting frustrated and had had a busy exhausting day so it didn't help me come across clearly/properly.
OK, so I had preware installed already, so I removed it, went into developer mode, used the linux commands, reinstalled preware, added Tailor.
(i've done this a few times, because I didn't remove the cable after doing the linux commands for preware, then i accidentally hit the wrong buttons and it connected to 'usb drive' mode and wouldn't connect on the pc side and got stuck on the "ow disconnected me properly next time" screen).
So it gives me the following options
USB (media)
Android (system)
Android (cache)
Android (data)
Unused Space
the 'usb media' starts mounted and will mount again if unmounted. If I use 'check filesystem' it'll pass. So then I try 'delete partition' which pretends to delete, then it takes me to the unused partition which is still at 16mb. so i try to use "check filesystem' again and it fails. try repair and it fails as well
I've tried mounting the android parts just to see, they just sit there processing that they are trying to mount. trying to delete or anything else fails as well.
and now after trying things, any of the 'cards' will try to open and just sit there grey. and with my usb cable not plugged in it still is giving me the option to enter usb drive mode. and with this i have to restart and go through the steps again of adding Tailor which is getting tedious.
I restarted, went through the motions to get back to Tailor. trying out resizing just to see how that goes. So far 15%. not sure what will happen when done, but we will see.
This is getting long, so i'll end this part and update on anything and also try to familiarize myself with adb a tad more

ADB logcat setup, etc.

I've Google'd the topic and all the comes up are my own post in the Dev sections where I asked how to create/get a logcat. I can "adb logcat" to a text file, then it shows "waiting for device". Now what's the procedure or setup on the S7 end? I've turned On adb debugging options in the S7. Can/ls this done by USB? The "adb devices" command while plugged into the USB shows nothing. I can connect in Fastboot mode and "adb devices" shows nothing also. Or is more of the Android SDK package needed for this?

Did you install the adb drivers?
Sent from my Nexus 7 using Tapatalk 2

giveen said:
Did you install the adb drivers?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hmm, since I've never used adb commands in the past, maybe not! Are they installed from a EXE file or in a INF fashion?

I love you man
http://forum.xda-developers.com/showthread.php?t=1484406
Download and extract, boot up device, make sure ADB is turned on device, then plug it into the computer, go to My Computer > Manage > Device Management, you should see something pop up with a yellow triangle, install the driver, it will ask you for the location point it to where you extracted the download at.

giveen said:
I love you man
http://forum.xda-developers.com/showthread.php?t=1484406
Download and extract, boot up device, make sure ADB is turned on device, then plug it into the computer, go to My Computer > Manage > Device Management, you should see something pop up with a yellow triangle, install the driver, it will ask you for the location point it to where you extracted the download at.
Click to expand...
Click to collapse
I may have never really installed ADB drivers, only Fastboot months ago. I feel like a real noobie again! Thinking that I missed the ADB drivers somehow I found that post on my own but take a look at the link. See anything missing??

wptski said:
I may have never really installed ADB drivers, only Fastboot months ago. I feel like a real noobie again! Thinking that I missed the ADB drivers somehow I found that post on my own but take a look at the link. See anything missing??
Click to expand...
Click to collapse
Um....no?
http://d-h.st/592

giveen said:
Um....no?
http://d-h.st/592
Click to expand...
Click to collapse
Yep, that's a link to the page but where's a link to actual file download? I think the third comment on the page mentions this.
If I'm not missing the driver files, I wonder if it might be that I NVflashed CM10 again but didn't allow it to reboot before restoring a TWRP backup?

All the old links to files have been changed since the DNS problems but I found a link to the old files at StreakDroid and the DNS issued is fixed. Download, unzipped, nothing looks any different to what I already have. I still tried the package anyway and it still can't find it's driver. Next I'm going to NVflash CM10 again and let it boot up fully and try it then before restoring my TWRP backup.

I had the same problem the other day when i flashed mine to CM10.
In the end the procedure which worked for me was to unplug the usb cable from my laptop.
Press the small button to hard power off the device.
Boot the device to CM10 again.
Plug the device in to a different USB port.
Then i went in to device manager and found a "dell" device which i right clicked then update drivers and pointed to the folder where i had the adb drivers downloaded to. It found them and installed the devices as an adbx device.
Then i unplugged from usb again and plugged it back in. At this point i ran the logcat command and it started logging.

jamezz98 said:
I had the same problem the other day when i flashed mine to CM10.
In the end the procedure which worked for me was to unplug the usb cable from my laptop.
Press the small button to hard power off the device.
Boot the device to CM10 again.
Plug the device in to a different USB port.
Then i went in to device manager and found a "dell" device which i right clicked then update drivers and pointed to the folder where i had the adb drivers downloaded to. It found them and installed the devices as an adbx device.
Then i unplugged from usb again and plugged it back in. At this point i ran the logcat command and it started logging.
Click to expand...
Click to collapse
I tried exactly as you outlined and it still didn't find the needed drivers. Funny as it shows a "B10B" as the unknown device and in the two WIN32 INF files that is a Dell parameter ID.
I may try my TWRP backup to ICS-B4 again before I NVflash again sometime today.
EDIT:
Restored my TWRP ICS-B4 backup but it can't find its drivers either and I tried swapping ports also. One thing though, instead of "B10B" showing up in "Other Devices", I get "Android". An NVflash is next, maybe a TWRP backup breaks ADB??

wptski said:
I tried exactly as you outlined and it still didn't find the needed drivers. Funny as it shows a "B10B" as the unknown device and in the two WIN32 INF files that is a Dell parameter ID.
I may try my TWRP backup to ICS-B4 again before I NVflash again sometime today.
EDIT:
Restored my TWRP ICS-B4 backup but it can't find its drivers either and I tried swapping ports also. One thing though, instead of "B10B" showing up in "Other Devices", I get "Android". An NVflash is next, maybe a TWRP backup breaks ADB??
Click to expand...
Click to collapse
Its because I was testing some things out in init.streak7.usb.rc

giveen said:
Its because I was testing some things out in init.streak7.usb.rc
Click to expand...
Click to collapse
Ah, what do you mean? ADB isn't going to work? It didn't work after another NVflash and allowed to boot up.

wptski said:
Ah, what do you mean? ADB isn't going to work? It didn't work after another NVflash and allowed to boot up.
Click to expand...
Click to collapse
It works just fine.

I'm stumped!

Got it! I had use the pick device option route which led to Android to ADB Interface or ADB Composite Interface. I selected the non-composite option, used those same files again and it installed the proper drivers. I have no idea and don't really care. What a PITA!

wptski said:
Got it! I had use the pick device option route which led to Android to ADB Interface or ADB Composite Interface. I selected the non-composite option, used those same files again and it installed the proper drivers. I have no idea and don't really care. What a PITA!
Click to expand...
Click to collapse
Restored my ICS-B4 backup, ran into the exact same issue and used the same solution to install the ADB drivers.

I think I seriously messed up my phone, can't copy stuff over while TWRP :(

Guys I have TWRP V2.8.10...I was trying to install ViperOne Rom. I had in installed but I foolishly did a FULL ADVANCED Whipe...Idk why I did that I wasn't thinking about it...well naturally it wiped the ROM clean off the device as well as EVERYTHING else. I don't even have my backup to restore to. UGH I'm so frustrated with myself. Well anyways I try to enable MTP while in TWRP and its shows the HTC One as a portable device as well as havin 24.9 of 25.0 GB of FREE Space however it will NOT let me copy the ViperOne ROM over....it keeps saying the file size is too large. IT most certainly is NOT too large. There has to be someway around this to FORCE this file onto to the device for a reflash. Any help would be appreciated here. Idk if this is a windows thing but I was thinking I could maybe even attach a micro to full size usb plug to the htc and put the rom on a flash drive and flash it onto the device but idk if this would work. I should also note that when I open internal storage on the device it only shows the TWRP folder. I'm half wondering if the device has lost its root as well...will a reflash over the terminal maybe help?

gravatrax1 said:
Guys I have TWRP V2.8.10...I was trying to install ViperOne Rom. I had in installed but I foolishly did a FULL ADVANCED Whipe...Idk why I did that I wasn't thinking about it...well naturally it wiped the ROM clean off the device as well as EVERYTHING else. I don't even have my backup to restore to. UGH I'm so frustrated with myself. Well anyways I try to enable MTP while in TWRP and its shows the HTC One as a portable device as well as havin 24.9 of 25.0 GB of FREE Space however it will NOT let me copy the ViperOne ROM over....it keeps saying the file size is too large. IT most certainly is NOT too large. There has to be someway around this to FORCE this file onto to the device for a reflash. Any help would be appreciated here. Idk if this is a windows thing but I was thinking I could maybe even attach a micro to full size usb plug to the htc and put the rom on a flash drive and flash it onto the device but idk if this would work.
Click to expand...
Click to collapse
If you have a USB-OTG adapter it will certainly work.
your other options are adb push rom.zip /sdcard
and adb sideload rom.zip
just be sure the rom.zip is in the same folder as adb

I have a fastboot folder on my desktop the directory is
C:\Users\GRAVATRAX\Desktop\fastboot
VIPER adb and fastboot are all in the same folder, how would enter this into the command terminal? I'm following instructions that I found but it cames throwing me errors
Attached a pic, what am i doing wrong here lol

gravatrax1 said:
I have a fastboot folder on my desktop the directory is
C:\Users\GRAVATRAX\Desktop\fastboot
VIPER adb and fastboot are all in the same folder, how would enter this into the command terminal? I'm following instructions that I found but it cames throwing me errors
Attached a pic, what am i doing wrong here lol
Click to expand...
Click to collapse
What does your storage show as in recovery? 0mb?
Since you wiped it all anyway you may as well try Wipe>Format Data, from within twrp. You will be prompted to type yes to confirm. When its done reboot recovery and try MTP again.
As for using adb and fastboot. Do this, Hold Shift and Right Click on your fastboot folder. From the drop down menu that appears select "Open a command window here" this should open a cmd prompt with your fastboot folder as it's working directory.
Now use the push command
Code:
adb push viper.zip /sdcard
The command window will appear unresponsive until the push completes. When it's done install the Rom with your recovery.

Danny201281 said:
What does your storage show as in recovery? 0mb?
Since you wiped it all anyway you may as well try Wipe>Format Data, from within twrp. You will be prompted to type yes to confirm. When its done reboot recovery and try MTP again.
As for using adb and fastboot. Do this, Hold Shift and Right Click on your fastboot folder. From the drop down menu that appears select "Open a command window here" this should open a cmd prompt with your fastboot folder as it's working directory.
Now use the push command
Code:
adb push viper.zip /sdcard
The command window will appear unresponsive until the push completes. When it's done install the Rom with your recovery.
Click to expand...
Click to collapse
How long does it usually take to transfer files via this method? It shows the file onthe device but in the amount of like 128kb, will it give some sort of confirmation when its done?
Also in recovery it would show the device as having an internal storage os 26034.
If this doesn't work where I can find an otg cable? Would it be possible to use lets say a male to female usb adapter with a standard micro usb cable to achieve this effect

gravatrax1 said:
How long does it usually take to transfer files via this method? It shows the file onthe device but in the amount of like 128kb, will it give some sort of confirmation when its done?
Click to expand...
Click to collapse
While the Rom is being pushed you will see only a blinking cursor in the command window. When it's complete you should get a confirmation and the prompt will return to normal
It can take several minutes.
A basic OTG cable looks like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But they com in all sorts of shapes and sizes I use one like this
Picked up in my local tesco for a few quid

Danny201281 said:
While the Rom is being pushed you will see only a blinking cursor in the command window. When it's complete you should get a confirmation and the prompt will return to normal
It can take several minutes.
Click to expand...
Click to collapse
Alright Ill just be patient and let it do its thing....I tried to push the file via adb sideload however it kept saying device not found And yes i would enable ADB sideload via TWR
I might have to take a trip down to best buy and staples nad see if I can find one...I would call and see if they have what Im looking for...but LOL.
SO while we are waiting for this file to be pushed I am curious as to why this is happening. what exactly did I do for it cause to bring me this issue in Windows?

gravatrax1 said:
Alright Ill just be patient and let it do its thing....I tried to push the file via adb sideload however it kept saying device not found And yes i would enable ADB sideload via TWR
I might have to take a trip down to best buy and staples nad see if I can find one...I would call and see if they have what Im looking for...but LOL.
Click to expand...
Click to collapse
you need to fix your pc drivers while the phone is in recovery
look for the one in device manager with an exclamation mark and update the driver manually

clsA said:
you need to fix your pc drivers while the phone is in recovery
look for the one in device manager with an exclamation mark and update the driver manually
Click to expand...
Click to collapse
The deivce manager shows no issues with the drivers :/
Still trying to push the file...something gotta be wrong here.

gravatrax1 said:
Alright Ill just be patient and let it do its thing....I tried to push the file via adb sideload however it kept saying device not found And yes i would enable ADB sideload via TWR
I might have to take a trip down to best buy and staples nad see if I can find one...I would call and see if they have what Im looking for...but LOL.
SO while we are waiting for this file to be pushed I am curious as to why this is happening. what exactly did I do for it cause to bring me this issue in Windows?
Click to expand...
Click to collapse
Check your SDK is upto date by typing this into the fastboot command window
Code:
adb version
The latest is 1.0.32.
Also you may try TWRP 2.6.3.3 some other versions of TWRP have issues with adb. :good:
EDIT:- Infact reading back to your first post i see your using TWRP 2.8.1.0. It's been a while since i first tested that version but i'm sure I ditched it because of problems with adb

Can't get TouchPad to mount as UMS; also TP Toolbox won't run though it did before

Hi everyone,
So, I've got a windows 7 64 bit machine, and a 32 GB HP touchpad. A couple of years back, I installed JCSullins' Kitkat CM ROM... I think that's what it's called, anyway, it's been a while..
From what I remember, the install went off without a hitch - I got the novacom drivers, and then I ran the TP Toolbox which made the process quite easy.
Now I'm interested in tinkering with the touchpad more... possibly trying out a new ROM, or something like that.. but the problem is that I can't get the TP Toolbox to even start. When I run the batch file, I don't receive any error messages. The USB cable I'm using (which came with my old Samsung Galaxy S3) seems to be fine - I can use the TouchPad in windows explorer as an MTP device without any issues. Also, I don't think it's an issue with the novacom drivers, they seem to be working fine.
In addition to that, I can't get the storage to mount as a USB mass storage device... when I try to do this, I get an 'Unknown Device' showing up in Device Manager... I tried installing the generic USB Mass Storage driver to no avail. I also tried booting the device into TWRP and using the mount option in there but that didn't do anything that I could discern (mind you I wasn't looking too hard, I tried this before the other stuff I've already talked about, so it might be worth another shot I suppose).
And I do have developer options enabled, does this matter..? I can't remember whether I turned this on myself after installing CM Kitkat or if it somehow came already enabled (not sure if this is even a thing).
Thanks so much!
-Tim

HP TOUCHPAD Novacom Repair Android
[email protected] said:
Hi everyone,
So, I've got a windows 7 64 bit machine, and a 32 GB HP touchpad. A couple of years back, I installed JCSullins' Kitkat CM ROM... I think that's what it's called, anyway, it's been a while..
From what I remember, the install went off without a hitch - I got the novacom drivers, and then I ran the TP Toolbox which made the process quite easy.
Now I'm interested in tinkering with the touchpad more... possibly trying out a new ROM, or something like that.. but the problem is that I can't get the TP Toolbox to even start. When I run the batch file, I don't receive any error messages. The USB cable I'm using (which came with my old Samsung Galaxy S3) seems to be fine - I can use the TouchPad in windows explorer as an MTP device without any issues. Also, I don't think it's an issue with the novacom drivers, they seem to be working fine.
In addition to that, I can't get the storage to mount as a USB mass storage device... when I try to do this, I get an 'Unknown Device' showing up in Device Manager... I tried installing the generic USB Mass Storage driver to no avail. I also tried booting the device into TWRP and using the mount option in there but that didn't do anything that I could discern (mind you I wasn't looking too hard, I tried this before the other stuff I've already talked about, so it might be worth another shot I suppose).
And I do have developer options enabled, does this matter..? I can't remember whether I turned this on myself after installing CM Kitkat or if it somehow came already enabled (not sure if this is even a thing).
Thanks so much!
-Tim
Click to expand...
Click to collapse
Read this guide and download the ISO, it will fix or get the Tablet all clean and ready to go:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
When ready then follow this guide to flash any ROM:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773

HP_TOUCHPAD said:
Read this guide and download the ISO, it will fix or get the Tablet all clean and ready to go:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
When ready then follow this guide to flash any ROM:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
Click to expand...
Click to collapse
Thanks very much for the helpful reply!
So, if I'm understanding this correctly.. Windows 7 has been updated since I last used the TP Toolbox, and the novacom drivers no longer function properly?
Does this mean that I won't be able to mount the Touchpad as a USB Mass Storage device? From looking at the top posts in that thread you linked me to, I see only an MTP option available for file transfer...
Also, the thing you posted seems to be a workaround for novacom drivers that don't function properly?
I tried what I was talking about in my initial post, mounting the device in TWRP, and this did work, though I was only able to see the recovery partition (which I guess is all that TWRP will load, makes sense in retrospect..). I was able to do this by installing the novacom driver when windows asked me to provide a driver after seeing the device booted into TWRP.
But that says to me that it isn't a driver problem, I think..? Thus that workaround seems unnecessary (sorry, not trying to be rude, I do appreciate the help regardless). Also the novacom driver does load up properly when I boot the device into the WebOS recovery mode.
I really would like to be able to have the device mount as UMS in Windows 7, if possible..
Edit: Also, forgot to mention that when I do try to load the TP toolbox, it does seem at some point to show the HP logo for some reason, which I think it's supposed to as it loads the toolbox..at least this happens when I try to run the batch file a second time after it fails to do anything the first time (not sure if this means anything at all..).
Thank you again!

[email protected] said:
Thanks very much for the helpful reply!
So, if I'm understanding this correctly.. Windows 7 has been updated since I last used the TP Toolbox, and the novacom drivers no longer function properly?
The novacom driver works even in Windows 10, if the user know how to install it and use it properly.
Does this mean that I won't be able to mount the Touchpad as a USB Mass Storage device? From looking at the top posts in that thread you linked me to, I see only an MTP option available for file transfer...
The Tablet USB mass storage device can only be mounted ( and use) by booting into TWRP recovery or Android, not the USB symbol.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you see the instructions and Images? Even the Toolbox can be loaded.
Also, the thing you posted seems to be a workaround for novacom drivers that don't function properly?
Is a Linux boot disk with built in Novacom drivers, that will boot on any PC and allows to repair, load the Toolbox and do everything need it.
I tried what I was talking about in my initial post, mounting the device in TWRP, and this did work, though I was only able to see the recovery partition (which I guess is all that TWRP will load, makes sense in retrospect..). I was able to do this by installing the novacom driver when windows asked me to provide a driver after seeing the device booted into TWRP.
The novacom driver is only use to load uImages into memory, troubleshoot, it does not offer USB transfer.
But that says to me that it isn't a driver problem, I think..? Thus that workaround seems unnecessary (sorry, not trying to be rude, I do appreciate the help regardless). Also the novacom driver does load up properly when I boot the device into the WebOS recovery mode.
If the user does not know how to load uImages into the Tablet, it does not matter if the novacom are working properly or not.
That is the reason of the Linux bootable CD, make it easier for those that have issues and are not technically incline.
I really would like to be able to have the device mount as UMS in Windows 7, if possible..
Edit: Also, forgot to mention that when I do try to load the TP toolbox, it does seem at some point to show the HP logo for some reason, which I think it's supposed to as it loads the toolbox..at least this happens when I try to run the batch file a second time after it fails to do anything the first time (not sure if this means anything at all..).
Thank you again!
Click to expand...
Click to collapse
The HP Logo will show before the Toolbox gets loaded into memory, then the print screen of all commands will show and finally the Toolbox loads.
Is impossible to provide technical support for issues relating to the novacom drivers on any PC with all the operating systems options available and the different configuration.
The bootable CD is available, just click and load anything to the touchpad, follow all the directions, read it all.
If the user try to take shortcuts, it will be a long way to accomplish nothing.

Device not detected in Fastbootmode.

SOLVED:
The reason Device was not detected in Fastbootmode was due to my new ryzen 3000 system, I tried it on my much older quad core 46XXk(?) Intel system and it gave me no problems whatsoever finding the device in fastboot mode in my first try! wtf amd!
The second Set of problems came with flashing 16.0631.1910.64. It gave me a ton of errors and it was on an infinite boot loop, nothing I tried fixed it, my device was a worthless brick in that state, but fastboot Power+Volume up > 16.0631.1910.64 worked perfectly.
I decided to instead try 16.0631.1910.35, but once I flashed it everything worked perfectly! I am in the latest version of android 10 atm and can acess banks, play nintendo games, etc with the rooted device.
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?

TeknoViking- said:
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?
Click to expand...
Click to collapse
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?

reg66 said:
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?
Click to expand...
Click to collapse
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw

TeknoViking- said:
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw
Click to expand...
Click to collapse
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done

reg66 said:
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done
Click to expand...
Click to collapse
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

TeknoViking- said:
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
View attachment 5173971
Click to expand...
Click to collapse
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.

reg66 said:
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.
Click to expand...
Click to collapse
Done, nothing happens, did it multiple times here's what I get:

TeknoViking- said:
Done, nothing happens, did it multiple times here's what I get:
Click to expand...
Click to collapse
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....

reg66 said:
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....
Click to expand...
Click to collapse
Will do! ty

TeknoViking- said:
Will do! ty
Click to expand...
Click to collapse
try this version, after installing the drivers you could also try that folder with the cmd-here file in combination. Also, try booting into android os and enable developer options (click on 'build' 7 or so times in settings/system/about phone/software information/build number), then go to developer options and enable USB debugging - might make a difference...

Also, check your pm, I sent you modified instructions for using the other guide that'll take you straight to last Android 9 version before you can update to Android 10 (1910.64). You could always be downloading that newer RAW + root img while tinkering with getting the damn thing recognised by your pc!!

Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "

TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...

TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Oh sorry, you meant try flashing the root img, NO, definitely not. The root img MUST only flashed after successful flashing of RAW - both rom and boot/root boot img's must match. (But either way, if your device isn't recognised by fastboot it just won't flash, just an FYI)

See this thread for info on Ryzen issues, if that is what you're running. The OP says he used an external USB hub as a solution

reg66 said:
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...
Click to expand...
Click to collapse
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.

Also I got this from continually trying to boot:

TeknoViking- said:
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.
Click to expand...
Click to collapse
Hmm, this phone is troublesome. Sorry dude, I've not seen that before. The bootloader unlock tool definitely worked, right? What about if you try using the original 1910.35 RAW - same error?

TeknoViking- said:
Also I got this from continually trying to boot:
Click to expand...
Click to collapse
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc

reg66 said:
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc
Click to expand...
Click to collapse
Yeah the charge is over 90 percent, anything I can do for that error? when I connect to the intel pc it doesn't even beep any more. I still can access the boot screen though.
EDIT: OOPS, noticed I had it plugged on the bottom, nvm intel system still detects the device. I did perform everything on the side port usb but I took it out to try and check back on the ryzen system.