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)?

Qhsusb_dload?

Is there a novacom command to correct this?

Okay, I've got the Qualcomm QHSUSB driver loader. Anyone know how to reset with QSPT?

I'm not sure what you're asking. What are you trying to do?

I'm trying to get it out of download mode. I'm trying to awaken it.

pworcester said:
I'm trying to get it out of download mode. I'm trying to awaken it.
Click to expand...
Click to collapse
Where are you getting this message? Are you plugged into your computer? Are you trying to transfer files or what? What were you doing before this error occurred? What is download mode? Awaken what, the Touchpad?
We need a lot more detail than what you've given us to help you.

This was my son-in-laws tp. He powered it off and now it will not power on. When connect it ot my windows 7 pc it is recoqnized as QHSUSB_DLOAD. This is a special
Qaulcomm mode.

pworcester said:
This was my son-in-laws tp. He powered it off and now it will not power on. When connect it ot my windows 7 pc it is recoqnized as QHSUSB_DLOAD. This is a special
Qaulcomm mode.
Click to expand...
Click to collapse
Try holding power and home down for about 15 seconds at the same time while connected to the PC. If it doesn't work the first time, try a few more times.

tried it. nothing

pworcester said:
tried it. nothing
Click to expand...
Click to collapse
Sorry, then I have no idea. Hopefully someone else will know.

thanks

I had this problem... and fixed it
... however I cannot guarantee this will work.
Your TP is very VERY low on juice and using the A/C adapter will not work. Power management is not running and trying to charge your TP without power management will not work. You need to trickle the power into the TP, either with the wireless touchstone or using the USB cable plugged into your PC to the TP.
I had the same issue and left my TP on the touchstone for one solid week. After that, I began playing with all the various combinations of button holds (power and Home, solid hold; power and home with my pulsing the home button 10-15-20 times; power and volume up (or down), etc...) and within a few minutes I had the red low battery icon on the display. At that time I jumped to A/C power and let it charge for several hours.
I suffered no loss of data, only had to reboot into CM9 and I was golden.
I hope this helps. And as always, "past performance is not a guarantee of future returns" so while this worked for me, I cannot promise anything.
Good Luck!
---------- Post added at 04:10 PM ---------- Previous post was at 03:42 PM ----------
Check this thread for more information.
http://forum.xda-developers.com/showthread.php?t=1740408&highlight=screen+dead

Thanks. I gave it back to my son-in-law. He's going to send it to HP and hope the doctor it which will blow away moboot.

I got the same issue. I tried the power + home + down volume connected to pc, then I tried the power+home and now is charging.

Possible QHSUSB_DLOAD solutions/fixes.
For anyone who's watching this thread, I have a few possible solutions.
I'm assuming you have the WiFi-only Touchpad (HSTNH-I29C), not the 4G version, although the bootloader should be the same.
First of all, it seems your Touchpad's booted into OMAP Download mode.
You might be able to reset a boot flag and get past this, by doing the following:
Plug in a USB charger for several minutes
While holding Power, quickly click the center home button ten times.
If that fixed it, great. If it recurs, you might want to consider backing up your device and running WebOS Doctor.
If this doesn't work, then bootie might be corrupted, the boot partition is boogered up, tokens may be misset, or the NAND is damaged, and is throwing you into this mode.
If bootie's corrupted, you can fix it, but it's involved, and explained below. If the NAND is damaged, it's time to RMA.
If you have a Linux PC, and feel comfortable building the tool, you can do the following OMAP bootstrapping, paraphrased from http://www.webos-internals.org/wiki/Last_Resort_Emergency_BootLoader_Recovery#OMAP_boot_Procedure.
($> is not meant to be typed, but is the prompt.)
Install libusb. On Debian-likes (Ubuntu, Mint et. al) the package is libusb-dev and can be installed with
$> sudo apt-get install libusb-dev
Download the following:
View attachment omap3_usb.tar.bz2, the OMAP USB download client
View attachment boot-topaz.zip, containing the bootloader​ and extract them to a new directory. Put the boot-topaz.bin in the same directory as the omap3_usbload file.
Now that it's all extracted, open a terminal to the directory containing the Makefile, and just run
$> make
You should have an executable named omap3_usbload now.
Now run
$> sudo omap3_usbload boot-topaz.bin
which should show a row of dots.
While it runs, plug in the device. It should say found device! then download ok.
Your Touchpad should be booted.
If it shows a USB logo, you may need to manually back it up through recovery and/or booting the kernel through novacom, and re-doctor it. It's a bit involved, but I can step you through it if that does happen.
If it boots, great.
If, after rebooting, this happens again, I'd advise you to back up and doctor unless you don't mind booting like this every time
If anything needs explaining, feel free to ask in this thread or PM me.
If you think this is helpful, thank Rod Whitby and webos-internals. They're the real brains.

How could you use a software (omap3_usbload) built for Texas Instrument Omap CPU on a Qualcomm SnapDragon ?
Have your tried ?

dadwarf said:
How could you use a software (omap3_usbload) built for Texas Instrument Omap CPU on a Qualcomm SnapDragon ?
Have your tried ?
Click to expand...
Click to collapse
I believe, I have completely derped up. It was 3AM on no sleep. The OMAP was on the Pre, wasn't it?
I feel like a grand fool.

Just need overnight charge with correct A/C adapter, not with PC.

Friend's "Dead" Phone Problem

Hey everyone,
My friend came across an unfortunate problem with his HTC One. This is what happened according to him:
For the past few months the battery life was getting worse and became terrible, but it's been otherwise fine in terms of performance.
He was at work playing some music via aux
The song stopped playing unexpectedly
Figured that it was a problem with YouTube was like wtf, so he closed YouTube and tried reloading.
It wouldn't show anything and nothing worked, left it that way as to not mess it up more.
Then it completely froze and he shut it off
Not it wont turn back on at all.
He said he left it plugged in charging for a while, still nothing. Tried overnight, still nothing.
Says he really wants to get at least his pictures out of his phone.
So, what are some troubleshooting steps he can take, or what can he do?

suckafoola said:
Hey everyone,
My friend came across an unfortunate problem with his HTC One. This is what happened according to him:
For the past few months the battery life was getting worse and became terrible, but it's been otherwise fine in terms of performance.
He was at work playing some music via aux
The song stopped playing unexpectedly
Figured that it was a problem with YouTube was like wtf, so he closed YouTube and tried reloading.
It wouldn't show anything and nothing worked, left it that way as to not mess it up more.
Then it completely froze and he shut it off
Not it wont turn back on at all.
He said he left it plugged in charging for a while, still nothing. Tried overnight, still nothing.
Says he really wants to get at least his pictures out of his phone.
So, what are some troubleshooting steps he can take, or what can he do?
Click to expand...
Click to collapse
try to boot the phone while shinning a bright light to the light sensor. (this is protection to avoid booting the phone when its in your pocket)
Press and hold Power and Volume down for at least 30 sec
Connect the phone to a Windows computer using the original usb cable (or any other cable already known to work for data transfer) to a USB 2.0 port on your computer, then go to Windows devices manger, is the device detected as QHSUSB ? Or Qualcomm something?

Hi thanks for the reply.
He said that when he plugged into his PC, QHUSB_DLOAD shows up in device manager. So now what?

suckafoola said:
Hi thanks for the reply.
He said that when he plugged into his PC, QHUSB_DLOAD shows up in device manager. So now what?
Click to expand...
Click to collapse
Since the phone went in QHUSB_DLOAD by itself and randomly, this is an hardware failure, the phone will need a new motherboard. It would be fixable only if the phone went in this mode directly after flashing a (incompatible) firmware. Unfortunately there is no way to recover the data from it since the emmc is soldered on that defective board.
Sorry

Wow damn that's real bummer... so there really isn't anything he could do? I remember him telling me that he wanted to salvage pictures from his graduation, but this problem is not letting him

suckafoola said:
so there really isn't anything he could do?
Click to expand...
Click to collapse
Unfortunately no. Another perfect example why you must backup your important files regularly. Smartphones are unreliable for preserving data, they are not made to last very long (well like everything nowadays ).
I already heard of someone desoldering his emmc chip (not from a M7 btw) and soldering it back to other hardware to extract the data so this is not impossible but your friend would have to find someone really qualified to try this kind of thing and it will probably not be cheap if it can be done..... But no there is no conventional method (using your computer and a usb cable) to extract any data from this phone.

@alray I know it sounds silly, but would it be possibly to save the pics by booting into twrp and copying them to a USB otg?
I'm guessing no
And yeah, it's always a bad idea to keep important files and data on one device.. be it a USB flash drive, an external hdd, a laptop, a smartphone.... etc
there's always the chance of it refusing to work or getting stolen.

monrokhoury said:
@alray I know it sounds silly, but would it be possibly to save the pics by booting into twrp and copying them to a USB otg?
I'm guessing no
And yeah, it's always a bad idea to keep important files and data on one device.. be it a USB flash drive, an external hdd, a laptop, a smartphone.... etc
there's always the chance of it refusing to work or getting stolen.
Click to expand...
Click to collapse
how are you supposed to go in twrp if the phone is stuck in qhusb_dload (qhusb_dload = phone not even booting in bootloader = dead).
Sent from my HTC One using XDA Labs

alray said:
how are you supposed to go in twrp if the phone is stuck in qhusb_dload (qhusb_dload = phone not even booting in bootloader = dead).
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
What if it says qualcomm something?
Shining a light method doesnt work, i left it charging for 3 days, nothing, i tried connecting it to computer and turning on, but not working...

boleguc said:
What if it says qualcomm something?
Shining a light method doesnt work, i left it charging for 3 days, nothing, i tried connecting it to computer and turning on, but not working...
Click to expand...
Click to collapse
Doesn't matters what it's saying exactly, it's dead. It's only possible to unbrick a m7 that went in a "Qualcomm something" mode because of a bad firmware flash. If it went in that mode itself, without flashing, your phone is dead.
Sent from my HTC One using XDA Labs

alray said:
how are you supposed to go in twrp if the phone is stuck in qhusb_dload (qhusb_dload = phone not even booting in bootloader = dead).
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Yeah I expected that lol

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

Razer Phone 2 Won't Boot into Anything

Heyyo all. I was trying to reflash the stock rom, and kept having "too many links" errors. Restarted my PC, and tried again. Looked like it was working, until the phone "restarted". It didn't turn back on, and nothing is working on it now. Tried holding every button combo for 2+ minutes each. None had any effect. Tried holding volume down while plugging it in. Still nothing. Anyone have any idea how I can force it into download mode or anything?
Appreciate any input you have.
Edit: By nothing is working, I mean it won't turn on at all. Display stays black no matter how long I hold the power button.

Plugging in the charging cable also no response?

Docence said:
Plugging in the charging cable also no response?
Click to expand...
Click to collapse
Unfortunately not. Had tried leaving it charging for an hour or so in case it somehow died, and nothing. Left it unplugged all day today hoping a full battery drain may kick it back to life.

TBurn420 said:
Unfortunately not. Had tried leaving it charging for an hour or so in case it somehow died, and nothing. Left it unplugged all day today hoping a full battery drain may kick it back to life.
Click to expand...
Click to collapse
I guess you unlocked the critical bootstrap partition, the "too many links" error may be a problem with the connection of the data cable, which caused some underlying partitions to be damaged due to disconnection during the flashing process

Docence said:
I guess you unlocked the critical bootstrap partition, the "too many links" error may be a problem with the connection of the data cable, which caused some underlying partitions to be damaged due to disconnection during the flashing process
Click to expand...
Click to collapse
I had unlocked it, yeah. I was thinking it may have been the same thing. I had tried a different cable as well. Both would switch between no link, and too many links. Eventually just wouldn't boot into anything, so I think you're right about the partitions being damaged.
Do you know of any way to try to repair them? Ill do some Googling myself now as well

TBurn420 said:
I had unlocked it, yeah. I was thinking it may have been the same thing. I had tried a different cable as well. Both would switch between no link, and too many links. Eventually just wouldn't boot into anything, so I think you're right about the partitions being damaged.
Do you know of any way to try to repair them? Ill do some Googling myself now as well
Click to expand...
Click to collapse
I think your rp2 had turned a hard brick, because Razer did not provide a firehose file, can't flash any partition in 9008 mode

Docence said:
I think your rp2 had turned a hard brick, because Razer did not provide a firehose file, can't flash any partition in 9008 mode
Click to expand...
Click to collapse
riiiip. I'll try contacting them and see if its possible to get them. Thank you for your help!
Edit: Razer refuses to provide any support for the device now. It ended a year ago. Although in some other searching someone was saying they found the firehouse file within one of the .img's in the stock rom. Going to look more into it.