Database Develop

[Q] I CAN'T root my phone (2.2 froyo, factory reset)

Here is what I've tried so far:
1- SuperOneClick. The program hangs at a step where it reads "Check if rooted : false"
2- Galaxy One Click Root. Program is responsive but it stops at "* daemon started successfully *" and does nothing from there.
3- Copying the "update.zip" file to the root of my internal SD card. I'm greeted by a "E: Signature verification failed. Installation aborted" error.
All remediable steps to fix one or all problems REQUIRES root, so i'm in limbo here. I honestly am about to cry. This seemed a hell of a lot easier when I read about it...
Well, what's left here for me to do? I'm lost. I read so many threads here I honestly can't do it anymore. This is my last resort.
This phone is all stock, AT&T Captivate.
Sorry if this is the wrong section of this forum... New here.

Flash your phone via Odin to jf6 stock then try superoneclick
Sent from my SPH-D710 using XDA App

hold up on that flash back. It oculd cause you to loop. Try using SOC v1.9 or lower. Also make sure your computer has all the required updates installed.

So this developed into a new, bigger, problem. I tried THIS guide to flash cyanogenmod (latest) but, guess what, the freaking thing hanged. So I was left with the only option, severing the link between PC and phone, and rebooting the phone.
I get this "phone - attention sign - computer" image. I think to myself "oh sh#&, I bricked the phone" so I rebooted it once again and to my surprise, the phone won't turn on. Won't react to the usb cable (can't boot to download mode), won't react to wall charger, won't turn on with the power button.
The battery was almost full...
What the heck is going on!?!? I had this phone for 3 days and I already ruined it?
I wan't to kill myself

leandroab said:
So this developed into a new, bigger, problem. I tried THIS guide to flash cyanogenmod (latest) but, guess what, the freaking thing hanged. So I was left with the only option, severing the link between PC and phone, and rebooting the phone.
I get this "phone - attention sign - computer" image. I think to myself "oh sh#&, I bricked the phone" so I rebooted it once again and to my surprise, the phone won't turn on. Won't react to the usb cable (can't boot to download mode), won't react to wall charger, won't turn on with the power button.
The battery was almost full...
What the heck is going on!?!? I had this phone for 3 days and I already ruined it?
I wan't to kill myself
Click to expand...
Click to collapse
Unfortunately, it doesn't sound promising. Even if you have a black screen, I would still try to access DL mode with Odin open (pull battery, remove sim, put battery back in, hold both volume buttons and insert the USB cord, don't touch the power button). If you get a yellow com light in Odin, even if the screen stays black, you're in download mode. If that doesn't work, you could try a jig and then see if Odin recognizes it. If neither of those work, you'll need to send your phone out to someone like Adam Outler to have it unbricked.

I get nothing with Odin. I can't believe I bricked my phone like that. I thought I would get an error screen at least. But this is outrageous. It's like the phone shorted and fried from the inside.
All I can say is wow... My happiness of a new phone turned to ashes in 30 seconds. Nice waste of money.

If you buy a USB download jig it will get you out of soft brick situations and if Odin fails try heimindal
Sent from my SPH-D710 using XDA App

leandroab said:
I get nothing with Odin. I can't believe I bricked my phone like that. I thought I would get an error screen at least. But this is outrageous. It's like the phone shorted and fried from the inside.
All I can say is wow... My happiness of a new phone turned to ashes in 30 seconds. Nice waste of money.
Click to expand...
Click to collapse
It didn't fry, it failed while flashing bootloaders. The bootloaders are what tell your phone what to do when you press power. Mismatched bootloaders = hard brick = no power up.
I would still try a jig, but if that doesn't work send a message to AdamOutler. He can give you the details of getting it unbricked.

MJHawaii said:
If you buy a USB download jig it will get you out of soft brick situations and if Odin fails try heimindal
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Considering the flashing hanged at the very beggining, I'm 90% sure it HARD-bricked my device. A jig wouldn't work and I'm left with a very fancy paperweight.
There is NO power on whatsoever.
My luck is amazing, isn't it?
Please, someone tell me there is still hope (there isn't probably)
apbthe3 said:
It didn't fry, it failed while flashing bootloaders. The bootloaders are what tell your phone what to do when you press power. Mismatched bootloaders = hard brick = no power up.
I would still try a jig, but if that doesn't work send a message to AdamOutler. He can give you the details of getting it unbricked.
Click to expand...
Click to collapse
Exactly. I figured
I have no idea of who "AdamOutler" is. But I'll find out. :/
FML

leandroab said:
Considering the flashing hanged at the very beggining, I'm 90% sure it HARD-bricked my device. A jig wouldn't work and I'm left with a very fancy paperweight.
There is NO power on whatsoever.
My luck is amazing, isn't it?
Please, someone tell me there is still hope (there isn't probably)
FML
Click to expand...
Click to collapse
I suspect you are correct about the hard brick, but I would still try a jig. I had a failure flashing bootloaders once that killed my cappy, but though a stroke of fortune a jig still worked for me. You can build one for a couple of bucks of parts from Radio Shack, you've got nothing to lose. If not, it can be repaired.

Before you start looking at all that, make sure you are hard bricked. Easiest way is to use Linux Mode Detector. Use the link below labeled Captivate sig link, then choose am i bricked?.

apbthe3 said:
I suspect you are correct about the hard brick, but I would still try a jig. I had a failure flashing bootloaders once that killed my cappy, but though a stroke of fortune a jig still worked for me. You can build one for a couple of bucks of parts from Radio Shack, you've got nothing to lose. If not, it can be repaired.
Click to expand...
Click to collapse
Yes, it's still worth a try. But unfortunately it will have to wait at least till the end of the month. That's when my college break is over and I'm back to school.
mrhaley30705 said:
Before you start looking at all that, make sure you are hard bricked. Easiest way is to use Linux Mode Detector. Use the link below labeled Captivate sig link, then choose am i bricked?.
Click to expand...
Click to collapse
Sorry but I'm not installing an OS just to use a program. I do believe the phone is hard-bricked though:
1- Doesn't power up with the on/off button
2- Doesn't go into recovery mode
3- Doesn't go into download mode
4- Doesn't light up when plugged into wall charger
If that isn't hard-bricked, then I'm really scared to find out what that really is
I sent a PM and an email to Adam Outler. I hope he replies it!

Linux is easier to use than you think, and it's a really handy tool to have when working with Android phones. You can install Linux entirely to a cheap thumb drive (I have a $4 4gb thumb drive running lubuntu) and it can get you out of a lot of Android related jams. If you're not willing to go through letting Linux up and running, might not want to do too much with phones either. I don't mean to be snarky, but I started using Linux casually a couple years before I started messing with phones and Linux is much more straightforward.
Edit: and if you have a multimeter around, check the voltage of your battery. Should be 4.2v=full, 3.5v ish is dead. If you battery pull, reinsert, hold volume up and down, and then connect to your pc with Odin open (don't hit power) what does Odin show? Last, did you get this phone used? Battery may be completely worn out, which would be why it was almost full and looks hard bricked now.

Wubi installer would be a better choice. And when your finished, it uninstalls just like an app. It's kind if a semipermanent dual boot. Check it out.

sekine12 said:
Linux is easier to use than you think, and it's a really handy tool to have when working with Android phones. You can install Linux entirely to a cheap thumb drive (I have a $4 4gb thumb drive running lubuntu) and it can get you out of a lot of Android related jams. If you're not willing to go through letting Linux up and running, might not want to do too much with phones either. I don't mean to be snarky, but I started using Linux casually a couple years before I started messing with phones and Linux is much more straightforward.
Click to expand...
Click to collapse
Well, I guess I'll look into that now. I'm running windows over a MacBook (stuck with it till I get back home). Maybe some tips running linux w/ a pendrive with bootcamp?
sekine12 said:
Edit: and if you have a multimeter around, check the voltage of your battery. Should be 4.2v=full, 3.5v ish is dead. If you battery pull, reinsert, hold volume up and down, and then connect to your pc with Odin open (don't hit power) what does Odin show? Last, did you get this phone used? Battery may be completely worn out, which would be why it was almost full and looks hard bricked now.
Click to expand...
Click to collapse
I'll look into the multimeter. The phone IS used, but I'm sure the battery isn't worn out.
Hooking up the phone, pressing both volume buttons, with odin open gives me nothing. Zip. If it was the battery wouldn't the phone give some sign of life after charging it for a while? Didn't happen.
mrhaley30705 said:
Wubi installer would be a better choice. And when your finished, it uninstalls just like an app. It's kind if a semipermanent dual boot. Check it out.
Click to expand...
Click to collapse
As stated, using windows with bootcamp over a MacBook. Maybe you can help me out? Will this work?

leandroab said:
If it was the battery wouldn't the phone give some sign of life after charging it for a while? Didn't happen.
Click to expand...
Click to collapse
My understanding is that charging is controlled by firmware to protect the battery, so it won't even charge if it's bricked.

apbthe3 said:
My understanding is that charging is controlled by firmware to protect the battery, so it won't even charge if it's bricked.
Click to expand...
Click to collapse
Right, or if the battery is so dead it can't start to turn on, it won't turn on. Or, if it was soft-bricked with no images to display, it may have killed itself without a firmware to allow it to charge properly. Not very likely, but there are a couple possibilities that end with a dead battery and no way to know.

apbthe3 said:
My understanding is that charging is controlled by firmware to protect the battery, so it won't even charge if it's bricked.
Click to expand...
Click to collapse
sekine12 said:
Right, or if the battery is so dead it can't start to turn on, it won't turn on. Or, if it was soft-bricked with no images to display, it may have killed itself without a firmware to allow it to charge properly. Not very likely, but there are a couple possibilities that end with a dead battery and no way to know.
Click to expand...
Click to collapse
Right. I'll check the V of the baterry once I get my hands on a multimeter.(somebody took all of them here at the house for some reason)

The multimeter read that the battery has 3.92V, so it's not dead. So to sum it up I only have two options now:
1- Try a USB jig
2- Attempt the UnBrickable mod/send it to Adam Outler
Both of them will take time. Unfortunate for me. Good news is that WILL have it back up and running. It will just take some time

leandroab said:
The multimeter read that the battery has 3.92V, so it's not dead. So to sum it up I only have two options now:
1- Try a USB jig
2- Attempt the UnBrickable mod/send it to Adam Outler
Both of them will take time. Unfortunate for me. Good news is that WILL have it back up and running. It will just take some time
Click to expand...
Click to collapse
So nothing whatsoever shows up in ODIN when you 1- batt pull, 2- batt reinsert, 3- plug in USB while holding either volume down, or volume up + vol down (w/o turning phone on)?

(Another) Touchpad Bricked. Please Help!

Ah I think I really screwed myself here.
I was flashing a rom last night in Clockwork Mod and didn't realize my battery was extremely low (stupid I know!). Anyway, in the middle of me flashing it, my battery died, thus interrupting the flash.
After charging it up, it booted up with the dreaded white Triangle Exclamation point screen with www.palm.com/ROM.
Ok, I went there and downloaded WebOS Doctor. Thing is, when I manually try to mount my TP, it doesn't show up on my computer. I get to the USB screen, but no luck mounting it on my computer.
I tried to "manually inject" CWM and successfully did so using my computer's terminal. (I'm using Mac, but have Windows access). Ok, I can now boot up into Clockwork Recovery. Is there anyway for me to use terminal (CMD) to recovery this?
Every option I do, it shows Loading '/boot/uImage.ClockworkMod' . . . OK
Checking uImage . . . Invalid Magic
BOOT FAILED!
Press SELECT to continue
or
Loading '/boot/uImage.webOS' . . . OK
Checking uImage . . . Invalid Magic
My computer won't recognize the USB storage for me to install WebOS Doctor on it. WebOS / CM won't load, ALL giving me the message of checking uImage . . Invalid Magic.
It's booting to moboot 0.3.5, but all options don't go.
I've tried holding power / home button for minutes, etc. All that. Nothing.
I'm pretty frantic right now as you can imagine and I'm praying I didn't completely turn this into a paperweight. Can someone help me out!?

jask0 said:
Ah I think I really screwed myself here.
I was flashing a rom last night in Clockwork Mod and didn't realize my battery was extremely low (stupid I know!). Anyway, in the middle of me flashing it, my battery died, thus interrupting the flash.
After charging it up, it booted up with the dreaded white Triangle Exclamation point screen with www.palm.com/ROM.
Ok, I went there and downloaded WebOS Doctor. Thing is, when I manually try to mount my TP, it doesn't show up on my computer. I get to the USB screen, but no luck mounting it on my computer.
I tried to "manually inject" CWM and successfully did so using my computer's terminal. (I'm using Mac, but have Windows access). Ok, I can now boot up into Clockwork Recovery. Is there anyway for me to use terminal (CMD) to recovery this?
Every option I do, it shows Loading '/boot/uImage.ClockworkMod' . . . OK
Checking uImage . . . Invalid Magic
BOOT FAILED!
Press SELECT to continue
or
Loading '/boot/uImage.webOS' . . . OK
Checking uImage . . . Invalid Magic
My computer won't recognize the USB storage for me to install WebOS Doctor on it. WebOS / CM won't load, ALL giving me the message of checking uImage . . Invalid Magic.
It's booting to moboot 0.3.5, but all options don't go.
I've tried holding power / home button for minutes, etc. All that. Nothing.
I'm pretty frantic right now as you can imagine and I'm praying I didn't completely turn this into a paperweight. Can someone help me out!?
Click to expand...
Click to collapse
I don't think your TP is bricked, after all you've got it booting to moboot.
I'm not sure, but it sounds like you need to update the drivers on your computer. I'm not familiar with mac at all, I've doctored mine, but using my xp desktop.
Plug your tp to charge for a good long while (three hours should do it). Reinstall the drivers to your pc with the latest version, it should now see your tp.
Go to the webOS nation forums, there are plenty of threads there that will give you step-by-step directions to get you running again. It's been a while since I had to doctor mine so you're better off following those instructions.
Needless to say, don't let the battery get too low anymore. I'm thinking that after this you won't let that happen anymore.....
Good luck and post your results.

chicle_11 said:
I don't think your TP is bricked, after all you've got it booting to moboot.
I'm not sure, but it sounds like you need to update the drivers on your computer. I'm not familiar with mac at all, I've doctored mine, but using my xp desktop.
Plug your tp to charge for a good long while (three hours should do it). Reinstall the drivers to your pc with the latest version, it should now see your tp.
Go to the webOS nation forums, there are plenty of threads there that will give you step-by-step directions to get you running again. It's been a while since I had to doctor mine so you're better off following those instructions.
Needless to say, don't let the battery get too low anymore. I'm thinking that after this you won't let that happen anymore.....
Good luck and post your results.
Click to expand...
Click to collapse
Well, it's a sigh of relief hearing that it may not be bricked. Just to clarify, I do have access to my 2001 HP Pavilion ze4400 clunker of a laptop with Windows XP on it. I can use that today to mess with this.
I've tried to have my computer detect the TP through the USB by holding Power+Volume up. Computer won't detect it.
Is there somewhere I can get the drivers from?

I've tried WebOS doctor. Gets to the step where it asks me to connect my device to my computer. After connecting it, it doesn't read it and I can't move forward. Next isn't highlighted.

It's pretty hard to "brick" a webOS device sine they offer the doctor that flashes a fresh new OS on your device. To me it sounds like what was already mentioned. You probably need to update novaterm drivers. And I have always had problems connecting mobile devices to a Mac. I've never had problems with a PC.
And also, every time you update drivers, restart you computer before running the doctor again.

Ok. I hate to sound like a complete noob, but how do I go about updating nova term drivers? I downloaded "Universal Novacom Installer" just now and will try that / report back. I hope this works.

jask0 said:
Ok. I hate to sound like a complete noob, but how do I go about updating nova term drivers? I downloaded "Universal Novacom Installer" just now and will try that / report back. I hope this works.
Click to expand...
Click to collapse
Yeah, try that out first then restart you computer and try again. If that doesnt work, you can download the webOS SDK which will install novaterm for you also I think. There may be another method. I will search around for you.

jsgraphicart said:
Yeah, try that out first then restart you computer and try again. If that doesnt work, you can download the webOS SDK which will install novaterm for you also I think. There may be another method. I will search around for you.
Click to expand...
Click to collapse
Well, I ran Universal Novacom Installer and it successfully installed the drivers on my computer... I rebooted, loaded WebOS Doctor 3.0.5 and even tried 3.0.0, but both of them would not detect my device on the step that asks to connect it.
On that step, I've tried powering down, rebooting while holding volume up, and plugging it in after the USB image displays. The "Next" button doesn't light up for me at all.
When I plug it into my computer, in device manager, Palm Novacom (bootie) is recognized, but I'm still unable to mount the SD card from the Touchpad to my computer. Maybe my SD card is corrupt?

jask0 said:
Well, I ran Universal Novacom Installer and it successfully installed the drivers on my computer... I rebooted, loaded WebOS Doctor 3.0.5 and even tried 3.0.0, but both of them would not detect my device on the step that asks to connect it.
On that step, I've tried powering down, rebooting while holding volume up, and plugging it in after the USB image displays. The "Next" button doesn't light up for me at all.
When I plug it into my computer, in device manager, Palm Novacom (bootie) is recognized, but I'm still unable to mount the SD card from the Touchpad to my computer. Maybe my SD card is corrupt?
Click to expand...
Click to collapse
I remember having the same problem when I used my Pre Plus. I thought it was a driver problem but if not, I cant remember what I did to get it to work. Maybe try searching the forums over at webOS nation. You are going to definitely need to get webOS working before getting Android working again so concentrate on that. You device is not bricked. Im positive you can get it up and running again. I will continue to look around as well.
---------- Post added at 12:38 PM ---------- Previous post was at 12:24 PM ----------
OK, I came across some other suggestions.
1. Try different USB ports and cables
2. Let your TouchPad fully charge before trying the doctor.
I actually think that second one was my problem when it happened to me. And if your TouchPad died while flashing, that could very well be it. I think the webOS doctor actually says something along the lines of charging the battery or waiting for battery to charge when you have it plugged in and the next button is faded out. I cant remember. But that was with the phone. The Touchpad doesnt charge through a computer. So plug it into a wall and leave it for a while and try again.

Well I definitely appreciate you attempting to help me out. I'm basically in full panic mode at this point. I'll skim through the webosnation forums to see if there's anything. If you remember what you did to your Pre Plus, pleaseeeeee let me know!
Edit: Ok, after reading your post my TP is at home now (I'm at work) and it's on the charger. Bummer thing is that there's no indication of how charged, or not charged, it is at this point. I'll definitely let it sit on there for a while and report back. Fingers crossed again.

jask0 said:
Well I definitely appreciate you attempting to help me out. I'm basically in full panic mode at this point. I'll skim through the webosnation forums to see if there's anything. If you remember what you did to your Pre Plus, pleaseeeeee let me know!
Click to expand...
Click to collapse
Check my previous post. Try recharging the battery first
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
jask0 said:
Edit: Ok, after reading your post my TP is at home now (I'm at work) and it's on the charger. Bummer thing is that there's no indication of how charged, or not charged, it is at this point. I'll definitely let it sit on there for a while and report back. Fingers crossed again.
Click to expand...
Click to collapse
Good Luck. I have a good feeling that is your problem.

jsgraphicart said:
Check my previous post. Try recharging the battery first
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
Good Luck. I have a good feeling that is your problem.
Click to expand...
Click to collapse
I really hope this is the solution, and I don't want to dismiss the thought, but I was thinking that I woke up this morning at around 730AM and it was on the charger from then until about 12:30PMish. Do you know if WebOS requires it to be FULLY charged? Or up to a certain percentage? I would think about 5 hours on the charger would put enough juice in it already...

jask0 said:
I really hope this is the solution, and I don't want to dismiss the thought, but I was thinking that I woke up this morning at around 730AM and it was on the charger from then until about 12:30PMish. Do you know if WebOS requires it to be FULLY charged? Or up to a certain percentage? I would think about 5 hours on the charger would put enough juice in it already...
Click to expand...
Click to collapse
Hmm. I dont know. I've never charged my TouchPad from being completely dead so I dont know how much 5 hours would give it. I'm not sure if the doctor requires a full percentage or not but I think it does check if your battery is full enough so it doesn't shut off during the procedure.
---------- Post added at 01:50 PM ---------- Previous post was at 01:08 PM ----------
Its all coming back to me now. This is what I did when this happened with my phone:
1) Remove the battery
2) Press and hold the volume up button
3) Plug the USB charging cable into the wall charger, and insert the USB cable into the Pre.(you will see a picture of a battery and a question mark at this point)
4) Insert the battery.
5) Release the volume up button.
At this point, you will see a full-screen "USB" symbol, instead of the normal small USB symbol over a picture of the Pre. DO NOT CONNECT THE PRE TO YOUR PC YET. Once the webOS Doctor asks you to plug in the Pre, take the USB cable out of the wall charger, and plug it into your USB port on the PC. The "Found New Hardware" wizard will run, installing "Novacom" drivers. After that completes, the "Next" button will light up in webOS Doctor, and allow you to finish repairing your device.
Click to expand...
Click to collapse
I dont know what the equivalent is to the touchpad since you cant remove the battery. But this is what I did when I had this problem.

Phew. Thank you very much for your time and patience. I came home and ran the WebOS Doctor again and it went through. I guess you were right about the battery. I figured the amount of time I had it on, the battery had to be near full. But I guess those few extra hours helped out.
I'm back on WebOS with breathing a huge sigh of relief.
Now I have to remember and look for how to reroot this thing and put CM9 on it and LEAVE it. No more messing with roms for me unless it's a huge update. lol.

jask0 said:
Phew. Thank you very much for your time and patience. I came home and ran the WebOS Doctor again and it went through. I guess you were right about the battery. I figured the amount of time I had it on, the battery had to be near full. But I guess those few extra hours helped out.
I'm back on WebOS with breathing a huge sigh of relief.
Now I have to remember and look for how to reroot this thing and put CM9 on it and LEAVE it. No more messing with roms for me unless it's a huge update. lol.
Click to expand...
Click to collapse
Nice! I'm glad it works now. And maybe you should say "no more messing with ROMs with a low battery" instead. lol. Flashing ROMs is the funnest part of Android.

Bricked Touchpad need help

I have been running CM9 nighties for some time now with no issues on my 16GB US WiFi only Touchpad. I installed TWRP and after some time decided to remove it and just use CWM. After trying several things from the posts (which would not work) I decided to remove CM9 completely then reinstall. This is where I got into trouble...
I loaded all necessary CM9 files in the cminstall folder on the Touchpad. I successfully ran ACMEUninstaller and got back to the WebOS language selection (i.e. the initial WebOS screen from factory). Instead of logging into WebOs (felt there was no-need since I never use it), I put the unit in Download mode (vol down + power). I then ran ACMEInstaller2. I received an error (text on the black touchpad screen which I assume is the bootloader) saying the needed files were not installed and something like "remove the wall". I thought I would reboot the unit and now log into WebOS and reinstall the CM9 files (thinking I made a typo when loading them). Now I cannot get the Touchpad to reboot - totally black and even when connected to the PC I dont get the USB connection sound.
Does anyone know if there is a hardware method to bring the unit back (maybe a different sequence of button presses or shorting a pin on the USB connector)? I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port.
Any thoughts would be greatly appreciated.
EDIT
Resolution: In a post I saw dated May of 2012, the user indicated HP was still honoring their warranty. I contacted HP via their Chat service, after giving them my model and serial number, I was told I had three weeks remaining on my warranty. HP sent me the return box with authorization and in a week I received (what seems to be) my exact Touchpad... only now it booted just fine. I have since reinstalled ICS and am running fine. Thanks to all who responded. I wanted to share this as I am extremely impressed with HP's warranty service (no questions were asked if I had rooted the device, where I bought the device, etc).

Make sure that your touchpad is not low on battery and see if anything happens when you plug it into the wall charger that it came with.
This has almost been the problem for me when my tp has problems.

Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is.
paul96 said:
Make sure that your touchpad is not low on battery and see if anything happens when you plug it into the wall charger that it came with.
This has almost been the problem for me when my tp has problems.
Click to expand...
Click to collapse

**Help needed with no charge and the lacklustre help not given via MAZE(Alpha 4gig)**

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...

yoga tablet 2 1050l doesn't start. Help please(

Hi everyone! I have a problem! Need help. Soooo... I have yoga tablet 2 1050l (android 5) and i wanted install windows. I rooted successful my device and i enter into bios. I changed boot from android to windows, idk why, i just thought that boot from usb. And now tablet doesn't start, when enabled, he returns errors. I can't enter into bios, recovery and fastboot, but i can enter into fastboot starting... mode. This is my fault, i know, but i really don't know what i need to do. I searchig many forums and didn't found. I hope you can help me)
P.S Sorry for my english, i'm russian

I would assume you need to flash the stock firmware back for your device

If you end up getting it back up and running do some research on how to do a complete backup. Whenever messing with things like that it should be your first thought

i tried to flash rom in fastboot starting... but no results. ADB doesn't see the tablet, fastboot see it, but it doesn't respond to commands, I've been struggling with it for 2 days

vitchay said:
i tried to flash rom in fastboot starting... but no results. ADB doesn't see the tablet, fastboot see it, but it doesn't respond to commands, I've been struggling with it for 2 days
Click to expand...
Click to collapse
Have you tried booting into safe mode?

3MrBojangles3 said:
Have you tried booting into safe mode?
Click to expand...
Click to collapse
i tried, but no results too(

idk, nothing's worked

vitchay said:
idk, nothing's worked
Click to expand...
Click to collapse
Have you tried the intel flash tool?

it tries to boot from windows, but it's no there at all
vitchay said:
idk, nothing's worked
Click to expand...
Click to collapse

3MrBojangles3 said:
Have you tried the intel flash tool?
Click to expand...
Click to collapse
yes, so many errors

I found this.....
Fixed, Instead of booting it into fastboot like all the tutorials say (power + up + down) just go into droidboot and flash it from there.
Sorry I didn't see this earlier.... Glad you got it though. I have all the files and old tutorials for the 1050f if you need in the future.

3MrBojangles3 said:
I found this.....
Fixed, Instead of booting it into fastboot like all the tutorials say (power + up + down) just go into droidboot and flash it from there.
Sorry I didn't see this earlier.... Glad you got it though. I have all the files and old tutorials for the 1050f if you need in the future.
Click to expand...
Click to collapse
i tried to flash in this mode, but some errors, i'll do screenshot

here

I wonder if you need different drivers now since it's saying it's a windows operating system now.. just a thought?

3MrBojangles3 said:
I wonder if you need different drivers now since it's saying it's a windows operating system now.. just a thought?
Click to expand...
Click to collapse
I changed drivers many times, but still not working

vitchay said:
here
Click to expand...
Click to collapse
What did you boot into when you got this wrong device state error? And what were you flashing with? I see adb there

vitchay said:
I changed drivers many times, but still not working
Click to expand...
Click to collapse
Try this ....
Lenovo Yoga 2 1050F Bricked
Hello, A friend give to me his Yoga2 1050F Tab, because it's bricked... "After a kind of upgrade he said" So, here's the situation, Tab is really bricked, stuck on Lenovo Android Screen. I've tried to factory restore, no success. I've...
forum.xda-developers.com

vitchay said:
yes, so many errors
Click to expand...
Click to collapse
I think I found what you need.....
Another way to clear CMOS is to reseat the CMOS battery.
Start by making sure your computer is unplugged. If you're using a laptop or tablet, make sure the main battery is removed, too.
Next, open up your computer's case if you're using a desktop PC, or find and open the small CMOS battery panel if you're using a tablet or laptop computer.
Every laptop is different. Some may have a small battery compartment with its own cover, but many don't. Instead, it may be in the same compartment where you will find the hard drive(s) and/or RAM memory chips and/or Wi-Fi radio(s). Sometimes you will need to remove the whole back cover.
Finally, remove the CMOS battery for a few minutes and then put it back in. Close the case or battery panel and then plug in, or reattach the computer's main battery.
By disconnecting and then reconnecting the CMOS battery, you remove the source of power that saves your computer's BIOS settings, resetting them to default.
Laptops & Tablets: The CMOS battery shown here is wrapped inside a special enclosure and connects to the motherboard via the 2-pin white connector. This is an increasingly common way that manufacturers of small computers include a CMOS battery. Clearing CMOS, in this case, involves unplugging the white connector from the motherboard and then plugging it back in

Thanks, i'll try it

3MrBojangles3 said:
I think I found what you need.....
Another way to clear CMOS is to reseat the CMOS battery.
Start by making sure your computer is unplugged. If you're using a laptop or tablet, make sure the main battery is removed, too.
Next, open up your computer's case if you're using a desktop PC, or find and open the small CMOS battery panel if you're using a tablet or laptop computer.
Every laptop is different. Some may have a small battery compartment with its own cover, but many don't. Instead, it may be in the same compartment where you will find the hard drive(s) and/or RAM memory chips and/or Wi-Fi radio(s). Sometimes you will need to remove the whole back cover.
Finally, remove the CMOS battery for a few minutes and then put it back in. Close the case or battery panel and then plug in, or reattach the computer's main battery.
By disconnecting and then reconnecting the CMOS battery, you remove the source of power that saves your computer's BIOS settings, resetting them to default.
Laptops & Tablets: The CMOS battery shown here is wrapped inside a special enclosure and connects to the motherboard via the 2-pin white connector. This is an increasingly common way that manufacturers of small computers include a CMOS battery. Clearing CMOS, in this case, involves unplugging the white connector from the motherboard and then plugging it back in
Click to expand...
Click to collapse
Thank you so much, i did, it works, thank you