Related
Hey,
I have been trying to root since the minute the process was let out publicly with no luck, until this morning. I have been through each thread over and over and finally found several things that made it work. After completing the task and going back over everything I tried. I found out the following and I would bet good money it will work for any one.
1. I left my phone plugged in the whole time. No usb cord inserting
2. I had it set to disk mode under pc connection in settings.
3. I used the 2gb card from verizon. Did not erase it. Don't know how it was formatted and don't believe it matters.
4. Made sure the HTC driver was working. This was done by having phone plugged in while in normal operating mode. To verify this once you hear the usb sounds in the command window at the C:/whatever/tools prompt type adb devices. It should come up with a serial number or such.
5. This will sound odd, but several of the methods talk about the screen flicker and not many talk about a sound the phone makes when it loads the sd card. That sound is real and audible if you put the phone to your ear. try it when you turn your phone on. You can hear it. That sound is the key. Try it by starting your phone normally and put it up to your ear. You will hear it.
6. Ok, if your phone is recognized by adb and you can hear the sound you have all you need. Make sure you have the necessay files downloaded to your tools folder.
7. With your phone in normal operating mode, shut it down. You need access to your battery and your sd card so the back needs to be off.
8. Pull the battery and unclick your sd card, hold Vol- and power. The phone will start and try to load the bootloader and leave you at the screen where you can select recovery.
9. Start Loop.bat
10. Press Vol - to select recovery and press power. move the phone close to your ear with your thumbnail on the sd card. When you hear that sound, immediately click in your sd card. The phone will goto the black triangle screen. The phone will then go through it's usb detection and when you hear the connected sound, you will get the error message. This may take 15-30 seconds. It took me 2 tries the first time, but now I have gotten it everytime I have tried since.
11. type in adb devices to verify that your in recovery.
12. Use your favorite method from here. The xda method is the one I used. Everything works fine. Wireless directly to my IPAD.
I think if I made a spread sheet of all the methods, sd cards and timings, we would find out that this is usually the thing that works. You can use the clock method, but I guarantee the right time collates with the cricket sound which collates with the screen flicker.
Anyone else smart that cares to look at this may be able to figure a way to streamline it even more.
Rod
sorry buddy but this old news we all knew about the audible sound, most people tried clicking in the sd card at that point, others tried plugging in usb at that point, buts we all knew about the sound and tried different methods to get it to work. personally i tried your method and it didnt work before i actually rooted. the method i used, envolved a linux live usb flash drive, linux live sd card formatted, and the tail messages, worked everytime the first time, if i missed the first time i had to restart the entire process. atleast now you are rooted
Jesus, everyone has a method that works for "everyone".
Apparently "Search" is broken?
aaronjb said:
Jesus, everyone has a method that works for "everyone".
Click to expand...
Click to collapse
I hear what you're saying, but we shouldn't stifle discussion that could lead to a more reproducible method, either. Maybe this doesn't warrant a new thread, but whatever.
Anyway, I had tried several of the other methods before, maybe 20-30 times, but nothing worked. I tried to time it with the click sound a couple times before, and it didn't work, but I thought I'd give it another try, since OP mentioned he got it to work with the stock 2GB SanDisk card, and that's all I have.
This time, I got it on the second attempt. My reflexes were a little slow, so it was probably more like a half-second after the click sound that I managed to click in the SD card. I haven't attempted to get back yet, so I don't know how repeatable it is.
One thing that may or may not be worth trying for others is that right before I got it, I uninstalled HTC sync, installed the bootloader drivers from the unrevoked site (can't post URL since I'm a noob).
Then uninstalled them (check "delete drivers" when doing so they won't auto-reinstall), reinstalled HTC sync, and finally reinstalled the bootloader drivers. I did the last reinstall because the device wasn't showing up when the phone was in the bootloader menu w/just HTC sync. It's unclear if any of this made a difference, or if I just got lucky with my timing this time.
When I was booting into recovery and pushed in the SD card, very shortly afterwards, I got a balloon in the bottom right that said it was installing the drivers (again? is that expected?). After that, rewt!
Oh lord, if I never saw another one if these threads, I could die a happy man. They're about as useful as alchemy, phrenology, perpetual motion machines, astrology, cold fusion, x-ray specs, etc etc ...
Sent from my Hal90000 using XDA App
The question begs:
If it bothers you so much, why the heck did you read it? Nobody makes you read these particular threads.
adrynalyne said:
The question begs:
If it bothers you so much, why the heck did you read it? Nobody makes you read these particular threads.
Click to expand...
Click to collapse
Because the title is so vague that you don't know it's YARMTISWWFE (Yet Another Root Method That I'm Sure Will Work For Everybody) thread until you read it?
If you couldn't figure out the post content by this time:
I have been trying to root since
Click to expand...
Click to collapse
Then some folks here might want to get tested for some learning disabilities. Don't even have to finish the first sentence to figure out what this thread was about.
To become rooted, do you have wipe your phone and sd card?
No, you definitely do not need to do that.
adrynalyne said:
The question begs:
If it bothers you so much, why the heck did you read it? Nobody makes you read these particular threads.
Click to expand...
Click to collapse
I wanted to see who was pretentious enough to think that their hare-brained scheme for rooting needed a new post, why they thought their experience could possible impact developing for the Inc, or what could possibly justify tacking "for devs" on the title of their post--as if they succeeded in making a secret club of a thread by doing so.
If he/she really wanted to help devs, they might have PM'd the guys involved with Unrevoked first, or joined their IRC channel, rather than clogging up the forum with another rooting thread. Honestly, there's enough going on now to think of others' purposes here before your "eureka" moment. Too bad I had to bump this thread just to respond.
Why be so mean? The more discussion on obtaining root the better I would think. Maybe this topic was not helpful but another one someday might and if people like the rude folks bashing the OP in this thread make others afraid to post then we might never get a reproducible method.
The sooner we get a reproducible method the better, because that means more folks to test and a wider user base for ROMs. I dont think a developer would spend too much time on a ROM for a device that they do not own and feel only a handful of people would have access to.
Oozura said:
Why be so mean? The more discussion on obtaining root the better I would think. Maybe this topic was not helpful but another one someday might and if people like the rude folks bashing the OP in this thread make others afraid to post then we might never get a reproducible method.
Click to expand...
Click to collapse
You call it mean, I call it strongly discouraging more speculation on a topic that already has a dozen or more threads going. As you can see by the proliferation of more advanced thread recently, most have moved on from trying to root, which common sense would tell one is caused by most having figured it out.
Maybe everyone has figured it out, maybe not. I imagine if you started a thread and asked who was still trying you would get several folks respond that they were. Nothing indicative of the entire population but just saying.
Edit: I just saw your avatar and then your use of such excellent gramar and vocabulary above. Did you make your own lingwo(sp) robot?
This thread has turned into a flame fest against the OP (since pretty much the beginning of it). Thread closed.
ok, i am hopelessly stuck. I ran the unlocker and after I click the last button to start the process, it says it cannot read a file. Anyways, I check to see if it worked by chance, and it does say security unlocked. But every time I try to flash a rom from the computer it starts and gets to the point where my phone goes to the color bar screen and says usb at the bottom, then it tells me that it cannot communicate with my phone???HELP
Edit: Really Guys??? I have posted twice here, I have been in the android forums for a long time and I can get a response to anything there in 5 min., I thought this was part of our community but I guess I was wrong.
matthewjulian said:
ok, i am hopelessly stuck. I ran the unlocker and after I click the last button to start the process, it says it cannot read a file. Anyways, I check to see if it worked by chance, and it does say security unlocked. But every time I try to flash a rom from the computer it starts and gets to the point where my phone goes to the color bar screen and says usb at the bottom, then it tells me that it cannot communicate with my phone???HELP
Edit: Really Guys??? I have posted twice here, I have been in the android forums for a long time and I can get a response to anything there in 5 min., I thought this was part of our community but I guess I was wrong.
Click to expand...
Click to collapse
I haven't had this problem, but is the driver installed for when it is in the bootloader screen?
Another way you could try is flashing it from bootloader mode. Just go into bootloader mode then plug it into your comp and run the romupdate utility.
Odd
Never personally ran into it but check your USB cable. Try a different cable. Try a different USB port. I had some issues with them being a little touchy.
I dont know if anyone cares, but I figured it out. I am using a Early 2010 Model MacBook Dual Core running Parallels instead of dual-booting Win XP.
When I am in Windows XP, OSX is running in the background, when the rom update utility turns the phone off then on into the bootloader, the phone is off for that split second and parallels cant keep up with it, and the Mac trys to grab the USB connection in that split second before Win XP says "No, thats my connection", so in that split second exchange the connection with Windows and the RUU gets droped! Kind of simple once you know whats happening. No matter, I used my brother in-laws Vista Toshiba( infected with viruses to the max), it worked fine and I am now running Moonscapes 1.6 with android as well! Thank You to the people who took the time to help!! Remember guys this is a community, it doesnt work unless people respond, without participation we may as well be talking to our dogs!
You never mentioned you were doing something crazy like trying to flash your phone from a virtual machine. That never works, because the usb passthrough driver doesn't detect the windows low-level bootloader mode. How are we supposed to help you when you don't provide details?
Lol, my bad, I got sloppy!! My son dumped a Sonic drink on my dell so all I could work with was my trusty Mac, I am going to dual boot it later today. I have to say after a day with Moonscapezx's 1.6, I like WM, dont know if I like it enough to swap it out for good, I still love my Hero(at least for another 3 months when I get an upgrade, EVO!!!). Ok, well Thank You again guys, I love XDA, you guys are great
I have 64bit drivers installed, and my phone is in download mode after a disasterous attempt at flashing for the first time. The phone, when not in Download mode, flashes the AT&T logo unplugged, and an empty battery logo with a spinner in the middle.
I've read endlessly on how to proceed with the reflashing steps, but it requires that I move files to the root folder, and it requires that I enable USB Debugging. I can't enable debugging and I can't seem to get my computer to recognize the phone as a disc drive.
I don't know what to do here, but I'm desperate to get my phone back up and running. I know I screwed up, and I don't need to be reminded of things I should have done. I only want constructive advice that will allow me to use my phone again.
Thank you so much in advance for anything that might get me operational.
STOP POSTING SO MANY THREADS ABOUT THE SAME THING!!!!!
wtf
cant you keep your **** organized into one thread!?
Or just shout out things like that.
I'm resolving the topical issue in each thread and announcing it. I thought these were topical threads and that how I worked it out. But hey, thanks. I'll be sure to keep my **** together in the future.
topical..
but when you have a ton of problems that all relate to your DRIVER situation....then, um dont you think it would be best to solve your DRIVER situation? you know, that thing that would solve most of your issues??
everything you have posted about has been about your computer seeing your phone....that would be driver related. once you fix that, your computer will see your phone. its not complicated and doesnt require a different thread started for every step of your driver problem/resolution
Great, so let's keep it on this thread from now on, and stop arguing, shall we? I'm just trying to be progressive. There. I fixed the damned thing anyhow.
Hi guys, been a bit out of the loop (hospital) but bought an Alpha around sep last year...within 2 months i used a official Maze update (OTA) and it then no longer charges...got onto them via facebook (as there were no official threads for this phone back then) and they sent me this to reflash it...
http://www.mazemobile.com/download-center
The ROM used to be there, but they have the ****ing cheek to say "people tried to flash and blamed MAZE" now it was MAZE's update in the first place that buggered my phone.:silly:..i still have the original ROM...
https://drive.google.com/drive/folders/0B8XLZxEJR8albndMcXJhWGtlVDQ
^not sure if that works for you, but basically it was..
:A really crap tutorial
:Maze Alpha flash tool.zip
:Maze_Alpha_V05_20170816
I've followed everything by the letter to no avail???
Now MAZE are bloody useless, can i count on one of you clever chaps to help me out?
P.s it's the 4 gig model.
Many thanks lads...
Any joy?
Is there anybody on here that had the same problem? You guys are usually really helpful, as i'm getting no rsponse from MAZE i thought i'd try where the true tech heads reside (i've received help before on my Xioami phones and smartwatches before) or is it that not many people have bothered with this phone? please help a guy out...much appreciated.
seedaripper said:
Is there anybody on here that had the same problem? You guys are usually really helpful, as i'm getting no rsponse from MAZE i thought i'd try where the true tech heads reside (i've received help before on my Xioami phones and smartwatches before) or is it that not many people have bothered with this phone? please help a guy out...much appreciated.
Click to expand...
Click to collapse
Well the thing is that you need to provide a bit more info. 'I've followed everything by the letter to no avail???' But you are not telling what works or not or what step you are stuck in the manual.
A lot of things come to my mind.
- is it still booting
- did you try another cable - charger
- ...
If it still boots and works a bit can you connect it to a pc and access for example the internal memory etc?
Some more info would be of help to get response... although I find the Maze Alpha part of the forum a lot of read and very little help (a bit of ranting may wake up people)
Cheers...someone lives!
Thanks for responding lukesan (much appreciated)
I'm using the original charger, it was working fine until i got the OTA so i doubt that's the problem.
No it doesn't boot (there is just enough charge to get to recovery mode,fastboot mode,normal boot)
I followed the manual/flash/tool etc (does the google drive doc show up for you as posted above?) everything seemed to go fine...but the problem still persists, it just wont charge?
Maybe i need a new ROM (or it could be the tool MAZE sent me) they are ****ing useless and i've started a bit of a social media campaign against them
(at first they were keeping in touch, but now they just ignore me completely on facebook) it pisses me off no end:crying:
P.s it does connect to my PC (sometimes), where should i dig around?
lukesan said:
Well the thing is that you need to provide a bit more info. 'I've followed everything by the letter to no avail???' But you are not telling what works or not or what step you are stuck in the manual.
A lot of things come to my mind.
- is it still booting
- did you try another cable - charger
- ...
If it still boots and works a bit can you connect it to a pc and access for example the internal memory etc?
Some more info would be of help to get response... although I find the Maze Alpha part of the forum a lot of read and very little help (a bit of ranting may wake up people)
Click to expand...
Click to collapse
seedaripper said:
Thanks for responding lukesan (much appreciated)
I'm using the original charger, it was working fine until i got the OTA so i doubt that's the problem.
No it doesn't boot (there is just enough charge to get to recovery mode,fastboot mode,normal boot)
I followed the manual/flash/tool etc (does the google drive doc show up for you as posted above?) everything seemed to go fine...but the problem still persists, it just wont charge?
Maybe i need a new ROM (or it could be the tool MAZE sent me) they are ****ing useless and i've started a bit of a social media campaign against them
(at first they were keeping in touch, but now they just ignore me completely on facebook) it pisses me off no end:crying:
P.s it does connect to my PC (sometimes), where should i dig around?
Click to expand...
Click to collapse
Just checked, and yes it is the correct manual. But lets say that even me, a veteran (with no patience), had issues with it. It is 100% correct but ... well see later on where you get.
Ok, first couple of things come up in my mind. Could still be the cable, the charger or even the the charging port that is broken. Been in the electronics business since the late 80's and these things can go wrong or broken any minute even thinking that a firmware update caused it.
Charger you can easily check if you just connect it to another charger or a pc usb port. A PC usb port will only deliver (mostly) max 400mA to 500mA .. meaning it will charge, if it still does, extremely slow. So I would keep it connected to a pc all day long or night before trying to switch it on. Trying to switch it on during charging and batt at low level will probably not work. You could try to power on after 2 or 3 hours or so and if it powers on then I would power it off again to get at least some juice in it to play around.
Cable, I would go fetch another one, they will come in handy in the future too. If it doesn't fit properly because the port is to deep in the Alpha then just take a knife and carefully cut a very small piece of the plastic, just 1mm is enough. I've done this on the 2 extra cables I have here and it works perfectly and I don't even see it aesthetically so no harm done on mine.
Now if that still doesn't work we can try the next step. But be very careful to know that that will delete all data, pictures, etc off of the phone. Because of all my toying with this phone I stuck an sd-card in it and doing a backup before I play with it again.
The manual states that you have to press the volume up button.. Well you can already test that without hurting anything as long you don't press anything on the flashtool. So only volume up and then insert the usb cable to a pc. Now the mistake I made in the beginning was to also push the power button.
So on the pc open up your device manager. If you do volume up (not in any of the other modes like fastboot etc, so from a standpoint that the phone is completely off) hold it for 2 or 3 sec and plug it into the PC. Now you should hear the typical usb connection sound and see something happening like an extra device in the manager. Probably you do not have the correct drivers installed for starters. Look for mtk drivers for your OS. Be careful, a lot of crap and virus links out there.
Now another issue that I fell for the first time is that you have to connect it twice like that to the pc to actually flash. First time ... press the 'scan' and let it do it (think the top field will become green) and then disconnect the phone and do the same volume up and connect and then it will allow you to flash.
But first check what is happening before we have to flash it.
Btw I know about their attitude. Well, as a Chinese company they must understand that by this attitude they will not going to sell any products anymore. I only bought mine because it was a special deal and I wanted to test an MTK chipset. They never replied to me why there is no real fast charge on it etc.
I also very very highly recommend you to invest, well for the price of a sandwich, to buy a usb charging doctor which will allow you to see the voltage and current. You don't need to be a doctor to us it and at least you see something instead of having to guess. Also while you are at it buy good quality chargers and a couple of cables. They will always come in handy and take some of the guesswork away if needed.
Top lad.
Again many thanks luksan (hefty bit of typing you did there mate )
I very much doubt it's the charger (i was extremely careful everytime with insertion) or port for that matter...this is the only USB-C i have (everything else is old school micro USB) and i resent forking out more money (the original trader Cafago said to send it back tracked at my own cost...£60!!!)
i'd like to try and fix the bastard and then sell it, never to return
Again, all these probs literally appeared after i did the OTA (i doubt it was coincidence)
i do like your advice on the re-doing the flash twice, so i may give that a go...bloody nora, what a pain in the arse!
Thanks for being a voice in the void pal...
See
lukesan said:
Just checked, and yes it is the correct manual. But lets say that even me, a veteran (with no patience), had issues with it. It is 100% correct but ... well see later on where you get.
Ok, first couple of things come up in my mind. Could still be the cable, the charger or even the the charging port that is broken. Been in the electronics business since the late 80's and these things can go wrong or broken any minute even thinking that a firmware update caused it.
So on the pc open up your device manager. If you do volume up (not in any of the other modes like fastboot etc, so from a standpoint that the phone is completely off) hold it for 2 or 3 sec and plug it into the PC. Now you should hear the typical usb connection sound and see something happening like an extra device in the manager. Probably you do not have the correct drivers installed for starters. Look for mtk drivers for your OS. Be careful, a lot of crap and virus links out there.
Now another issue that I fell for the first time is that you have to connect it twice like that to the pc to actually flash. First time ... press the 'scan' and let it do it (think the top field will become green) and then disconnect the phone and do the same volume up and connect and then it will allow you to flash.
But first check what is happening before we have to flash it.
.
Click to expand...
Click to collapse
seedaripper said:
Again many thanks luksan (hefty bit of typing you did there mate )
I very much doubt it's the charger (i was extremely careful everytime with insertion) or port for that matter...this is the only USB-C i have (everything else is old school micro USB) and i resent forking out more money (the original trader Cafago said to send it back tracked at my own cost...£60!!!)
i'd like to try and fix the bastard and then sell it, never to return
Again, all these probs literally appeared after i did the OTA (i doubt it was coincidence)
i do like your advice on the re-doing the flash twice, so i may give that a go...bloody nora, what a pain in the arse!
Thanks for being a voice in the void pal...
See
Click to expand...
Click to collapse
Well don't flash it twice. You have to put it in that mode twice to start it to complete the procedure. I do not believe in the wipe it 3 times to be sure, turn around and jump to make it better or faster. Loads of voodoo that is not scientifically proven around. It's all about a 0 and a 1, there is nothing in between that.
But .£60 to send that charger, LOL.
A month ago I bought an Aukey charger that included a USB-C cable for like .£12 including shipping to Belgium. (well just followed the rain and snow and landed here)
Let us know what happens next.
Any update on what you did?
GAH!
Yes, i've just tried everything again...nothing seems to work? when i actually start the tool i get a number of errors (including scatter?) then the tool boots, i then go through the broken english bollocks of the 'guide' again, do everything and it still doesn't work?? listen man, could you do me a massive favour...just outline the steps (bullet point wise) on what to do? no chatting about the chinese or voodoo
just nice clear as day steps, because as it stands i'm going to have to pay £70 just to send this piece of **** back (and probably wont get a full refund)
If you could do that (and i mean laymans terms here) i'd be forever grateful...
Cheers bud.:good::good:
lukesan said:
Any update on what you did?
Click to expand...
Click to collapse
seedaripper said:
Yes, i've just tried everything again...nothing seems to work? when i actually start the tool i get a number of errors (including scatter?) then the tool boots, i then go through the broken english bollocks of the 'guide' again, do everything and it still doesn't work?? listen man, could you do me a massive favour...just outline the steps (bullet point wise) on what to do? no chatting about the chinese or voodoo
just nice clear as day steps, because as it stands i'm going to have to pay £70 just to send this piece of **** back (and probably wont get a full refund)
If you could do that (and i mean laymans terms here) i'd be forever grateful...
Cheers bud.:good::good:
Click to expand...
Click to collapse
But what about the drivers etc.... What shows up?
ROM?
lukesan said:
Any update on what you did?
Click to expand...
Click to collapse
Perhaps it's the ROM? any chance you could give me the latest version? (or a link) i keep getting error in the light green field (FAIL) on the Tool?
I'm not sure if it's the tool or the bloody ROM?
As usual not a sodding dicky bird from MAZE (emails,twitter facebook etc) what a sh!tty company...
Nothing shows up...i think the first time i tried to plug it into the PC it ran a scan,(i don't think it found the drivers, as it doesnt show up on my computer :running win 7) from there on in, nothing? it also makes the mandatory PC sound bleep when plugged in, then about a second later i get the discharge bleep? (not sure if this is lack of charge) if i had a frigging phone i'd post screenshots! damned if i do, damned if i don't!
lukesan said:
But what about the drivers etc.... What shows up?
Click to expand...
Click to collapse
seedaripper said:
Nothing shows up...i think the first time i tried to plug it into the PC it ran a scan,(i don't think it found the drivers, as it doesnt show up on my computer :running win 7) from there on in, nothing? it also makes the mandatory PC sound bleep when plugged in, then about a second later i get the discharge bleep? (not sure if this is lack of charge) if i had a frigging phone i'd post screenshots! damned if i do, damned if i don't!
Click to expand...
Click to collapse
Well if it hasn't gotten the correct drivers it will never ever be able to flash. It's like trying to use your house keys to start your car.
I see all kinds of stuff happening if you keep the device manager open. Open up the 'ports' (com & lpt) section. Now press the 'volume up' key for a second or 2 and then connect it to a usb port while holding the key.. release it like a second later when it is connected to the port. Now you should see some stuff happening. Just did it on my win10 machine but should be pretty similar on a win7. One of them says first 'mtk usb' and then 'preloader usb vcom' . If these don't show up then look no further for now.
seedaripper said:
Perhaps it's the ROM? any chance you could give me the latest version? (or a link) i keep getting error in the light green field (FAIL) on the Tool?
I'm not sure if it's the tool or the bloody ROM?
As usual not a sodding dicky bird from MAZE (emails,twitter facebook etc) what a sh!tty company...
Click to expand...
Click to collapse
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
dreambo said:
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
Click to expand...
Click to collapse
His device doesn't charge and his battery is flat so I guess his by the time he can flash the device dies anyway.
er?
lukesan said:
Well if it hasn't gotten the correct drivers it will never ever be able to flash. It's like trying to use your house keys to start your car.
I see all kinds of stuff happening if you keep the device manager open. Open up the 'ports' (com & lpt) section. Now press the 'volume up' key for a second or 2 and then connect it to a usb port while holding the key.. release it like a second later when it is connected to the port. Now you should see some stuff happening. Just did it on my win10 machine but should be pretty similar on a win7. One of them says first 'mtk usb' and then 'preloader usb vcom' . If these don't show up then look no further for now.
Click to expand...
Click to collapse
Ok, did that for a split second 'media TEK preloader USB VCOM (android) (COM4)' flashes up, i managed to click on it quickly and got to mediatek properties...then went to update driver (it searched the net and found it) all this time after the original insertion, literally a second after it just disconnects? (and it doesn't show up in my computer) i get this as device status.....
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
I plug it back in, it says normal, then a second later the above message? any ideas?
lukesan said:
His device doesn't charge and his battery is flat so I guess his by the time he can flash the device dies anyway.
Click to expand...
Click to collapse
Yep, when i try to power on i have a split second of the MAZE logo, then back to death...i Can leave it charging and i get the wobble liquid battery graphic, but it never goes above 0%, as explained this only happened after a firmware update (#dreambo)
Can't get my head round multi quote?
dreambo said:
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
Click to expand...
Click to collapse
Yep, when i try to power on i have a split second of the MAZE logo, then back to death...i Can leave it charging and i get the wobble liquid battery graphic, but it never goes above 0%, as explained this only happened after a firmware update (#dreambo)
seedaripper said:
Ok, did that for a split second 'media TEK preloader USB VCOM (android) (COM4)' flashes up, i managed to click on it quickly and got to mediatek properties...then went to update driver (it searched the net and found it) all this time after the original insertion, literally a second after it just disconnects? (and it doesn't show up in my computer) i get this as device status.....
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
I plug it back in, it says normal, then a second later the above message? any ideas?
Click to expand...
Click to collapse
Mmm, if you see the preloader thing then I guess that is ok. ... it is no longer an 'unknown device' which sounds fine to me. Let me quickly test on my Maze for a sec. (will edit this post).
It is normal that it disconnects. My guess is that it tries to setup comms between device and something on the pc where it can talk to. If there is no communication then it just powers down again. The display etc will all stay off since it directly does the comms to the cpu and the ram. Sort of write only state. So it is a very low level form of programming. Can be scary for people because you see nothing happening on the phone during that process.
Ok just tested again.. Can you do step 1 to 5 in the manual without an error? (to be sure I would right-click on the exe and run it as administrator to start that program)
Till that step 5 no connection to the Alpha is needed. In step 5 if you have pressed 'scan' it should say something like resetting comm ports and only the 'stop all' should be clickable.
If we are that far then I guess we are a step further.
Give that a try and then we'll see for the next step.
lukesan said:
Mmm, if you see the preloader thing then I guess that is ok. ... it is no longer an 'unknown device' which sounds fine to me. Let me quickly test on my Maze for a sec. (will edit this post).
It is normal that it disconnects. My guess is that it tries to setup comms between device and something on the pc where it can talk to. If there is no communication then it just powers down again. The display etc will all stay off since it directly does the comms to the cpu and the ram. Sort of write only state. So it is a very low level form of programming. Can be scary for people because you see nothing happening on the phone during that process.
Ok just tested again.. Can you do step 1 to 5 in the manual without an error? (to be sure I would right-click on the exe and run it as administrator to start that program)
Till that step 5 no connection to the Alpha is needed. In step 5 if you have pressed 'scan' it should say something like resetting comm ports and only the 'stop all' should be clickable.
If we are that far then I guess we are a step further.
Give that a try and then we'll see for the next step.
Click to expand...
Click to collapse
Pics ...hopefully...
I've been following the guide here on how to get Android on my HP TouchPad. A while ago I followed these guides and had no problem, but a little while ago I thought I would try and update my Android version and I did something wrong (what, I don't know).
Right now I have KitKat running on my TouchPad, but my PC cannot see my TouchPad when I plug it in via USB. My computer makes the sound when I plug it in as if it IS connected, but it doesn't see it in my list of drives. It DOES, however, see it when I boot into webOS.
I'm sure there are other problems I'll run into, but I feel like this is the first major one. Is there anything I can do to make my computer recognize my TouchPad when plugged in via USB? I'll answer followup questions to the best of my ability, but like the title says, I'm in a bit over my head here I think.
SquaredCircle said:
I've been following the guide here on how to get Android on my HP TouchPad. A while ago I followed these guides and had no problem, but a little while ago I thought I would try and update my Android version and I did something wrong (what, I don't know).
Right now I have KitKat running on my TouchPad, but my PC cannot see my TouchPad when I plug it in via USB. My computer makes the sound when I plug it in as if it IS connected, but it doesn't see it in my list of drives. It DOES, however, see it when I boot into webOS.
I'm sure there are other problems I'll run into, but I feel like this is the first major one. Is there anything I can do to make my computer recognize my TouchPad when plugged in via USB? I'll answer followup questions to the best of my ability, but like the title says, I'm in a bit over my head here I think.
Click to expand...
Click to collapse
https://www.random-host.com/blogs/enable-media-device-mtp-usb-mode-android-44-kitkat-and-50-lollipop?
shumash said:
https://www.random-host.com/blogs/enable-media-device-mtp-usb-mode-android-44-kitkat-and-50-lollipop?
Click to expand...
Click to collapse
Hey, thank you very much for this. Apologies for the late reply, but something personal came up that kept me away from my computer for a few days.
I looked at the guide you linked, but I actually already have MTP checked. I hear the connected sound playing on my PC, but nothing shows up as a connected device. Could there be something wrong with the drivers on my PC's end? Oddly enough, it does show up when I have the camera option checked on the tablet.
SquaredCircle said:
Hey, thank you very much for this. Apologies for the late reply, but something personal came up that kept me away from my computer for a few days.
I looked at the guide you linked, but I actually already have MTP checked. I hear the connected sound playing on my PC, but nothing shows up as a connected device. Could there be something wrong with the drivers on my PC's end? Oddly enough, it does show up when I have the camera option checked on the tablet.
Click to expand...
Click to collapse
It's something inherent in KitKat. I had the same issue, and it was never resolved, but it goes away in later Android versions. You can still download and upload using the camera option. It just ends up in Pictures, I think.
shumash said:
It's something inherent in KitKat. I had the same issue, and it was never resolved, but it goes away in later Android versions. You can still download and upload using the camera option. It just ends up in Pictures, I think.
Click to expand...
Click to collapse
I hadn't thought about uploading to an inappropriate folder like Pictures, but as long as the files I need are on the tablet I don't see why that should end up being a problem. I can just move them internally with the Files app. Thank you for the idea!
SquaredCircle said:
I hadn't thought about uploading to an inappropriate folder like Pictures, but as long as the files I need are on the tablet I don't see why that should end up being a problem. I can just move them internally with the Files app. Thank you for the idea!
Click to expand...
Click to collapse
Copy it into the picture folder then move/rename it.