Bricked my Nexus 9 wont turn on - Nexus 9 Q&A, Help & Troubleshooting

Hello everyone ,
I think I have just bricked my nexus 9 , it started when I installed the dirty unicorn rom, but without thinking I did not perform a factory reset before in recovery and now my nexus 9 will not boot at all. When I hold the power button the google logo appears for a couple of seconds and turns off quickly. I also tried fasboot , and I eventually got it to appear but it turned off after 1-2 seconds. I then tried to use nexus root toolkit to flash the factory image, but since I cant acces fastboot it wont find my device. Am I out of options, or is there something else I can do , or should I send it in for repair. Any help would be appreciated, thanks.

Update:
anyone please help , edit:: I tried everything I could to turn on the nexus 9 and when I plugged in the nexus 9 to the wall and held power + up button , it turns on and says Fastboot AC, however whenever I select fastboot it shows it for a second and turns off. I tried plugging it into the wall and Fastboot AC but when I unplug it to my computer it just turns off and from there I cant do anything and it does not turn on at all.
Is there perhaps someway I can flash the bootloader without the screen on or anything like the nexus root utility that fixes bricked bootloaders?

Did you flash the custom rom via twrp? Do you still have the twrp recovery?
If yes try to boot into twrp recovery and connect to your pc.

Yes, I did flash the custom rom in twrp , however I cannot boot into twrp recovery or even into fastboot or the bootloader. My nexus 9 will not even turn on unless is connected to the wall outlet and then when I press the power + volume button it shows Fastboot ac however when I select the bootloader or anything else it just turns off. When I connected it to my pc, my nexus 9 does not turn on at all and is not even recongnized

Can you find a pc with a USB charging port or a hub with a charging port? A USB charging port will be able to deliver 2A along with the USB connection. You may also find a USB3 port may also deliver sufficient power - the official spec says 900mA but I think that is the minimum requirement.

I tried using 3 different pc's , one with a usb charging port , and the nexus 9 was still not able to turn on, even when holding power + volume up or any other configuration. I tried different usb cables and still no luck. Is there someway that I can access it without fastboot or adb? I know on the nexus 7 forum, there is one click factory restore dead or alive , but I dont think there is anything like that for the nexus 9.

spartacus279 said:
Update:
anyone please help , edit:: I tried everything I could to turn on the nexus 9 and when I plugged in the nexus 9 to the wall and held power + up button , it turns on and says Fastboot AC, however whenever I select fastboot it shows it for a second and turns off. I tried plugging it into the wall and Fastboot AC but when I unplug it to my computer it just turns off and from there I cant do anything and it does not turn on at all.
Is there perhaps someway I can flash the bootloader without the screen on or anything like the nexus root utility that fixes bricked bootloaders?
Click to expand...
Click to collapse
Can you take a picture of this?
I dont think you are bricked....

scrosler said:
Can you take a picture of this?
I dont think you are bricked....
Click to expand...
Click to collapse
I will try to take of a picture of it connected to the wall charger , it says fastboot ac , thank you for all your help everyone, I dont know what to do as I cant access fastboot or the bootloader

spartacus279 said:
I will try to take of a picture of it connected to the wall charger , it says fastboot ac , thank you for all your help everyone, I dont know what to do as I cant access fastboot or the bootloader
Click to expand...
Click to collapse
SO after it says fastboot, what happens? It just reboots?

scrosler said:
SO after it says fastboot, what happens? It just reboots?
Click to expand...
Click to collapse
No, I can access fastboot ac , however when I select hboot or anything else it just turns off.

spartacus279 said:
No, I can access fastboot ac , however when I select hboot or anything else it just turns off.
Click to expand...
Click to collapse
All you need is fastboot. From there you should be able to flash boot.img and system.img
commands are....
fastboot flash boot boot.img
fastboot flash system system.img
Then I would run fastboot format userdata
Of course you need to get these image files from the factory image site here: https://developers.google.com/android/nexus/images
LMK

scrosler said:
All you need is fastboot. From there you should be able to flash boot.img and system.img
commands are....
fastboot flash boot boot.img
fastboot flash system system.img
Then I would run fastboot format userdata
Of course you need to get these image files from the factory image site here: https://developers.google.com/android/nexus/images
LMK
Click to expand...
Click to collapse
I really want to do this , however my nexus 9 does not turn on when connected to any pc's , It will only turn on when connected to the wall charger. I have tried different usb cables and different computers and still no luck. I also tried nexus root toolkit however it doesnt recognize the nexus 9 as it needs fastboot which I cannot access.

spartacus279 said:
I really want to do this , however my nexus 9 does not turn on when connected to any pc's , It will only turn on when connected to the wall charger. I have tried different usb cables and different computers and still no luck. I also tried nexus root toolkit however it doesnt recognize the nexus 9 as it needs fastboot which I cannot access.
Click to expand...
Click to collapse
Hmmm
How long have you left it plugged into wall charger?

scrosler said:
Hmmm
How long have you left it plugged into wall charger?
Click to expand...
Click to collapse
I tried leaving it in overnight becuase I thought that the battery might of been low, but still nothing and I dont know what else to do right now?

spartacus279 said:
I tried leaving it in overnight becuase I thought that the battery might of been low, but still nothing and I dont know what else to do right now?
Click to expand...
Click to collapse
Ahhh, Ok. Thats what I was getting at.
You may have to RMA the device. Tell them nothing of root and ROM and just give the function failures you discussed here.

scrosler said:
Ahhh, Ok. Thats what I was getting at.
You may have to RMA the device. Tell them nothing of root and ROM and just give the function failures you discussed here.
Click to expand...
Click to collapse
I dont think I can RMA the device becuase I purchased the nexus 9 from an ebay seller and I contacted him and he said returns are only valid for two weeks and I have already had the device for other two months now. Should I just sell it or can I somehow return the device to google even though I did not buy it through the play store?

Just for reference , here is a picture of the nexus 9 in fastboot ac connected to the wall charger
http://imgur.com/coUY7qS
If I select hboot it turns off ,and if I try to plug it into a PC it just quickly shuts down and will not turn back on

I would still try to RMA back to HTC.
The most they can say is No.

Ok thanks for you help , I will try to contact HTC for a RMA
Edit: I just called HTC and described my situation and they said they would not be able to return it or RMA the device because it was bought from an ebay seller and they are not responsible. Is there anything else I can do?

spartacus279 said:
Ok thanks for you help , I will try to contact HTC for a RMA
Click to expand...
Click to collapse
Good luck to you!

Related

[Q] Is this prime bricked or not?

Well a friend of mine has flashed the Jellybean ROM onto his prime and now it wont boot into the OS. It can boot into CWM and bootloader. However when connecting to a computer it shows up as unknown (I've tried intstalling both ASUS and Universal naked drivers with the same result) no matter what mode it is in (fastboot, APX or recovery). So I can't use adb and it's an old CWM version that doesn't support an external SD. I have tried different computers and a different cable without success, also for it to be recognized by a computer the cable connecting to the primes port needs to be bent to a certain position, though I am not sure if this matters. So is this prime bricked or is there still hope?
JJ2197 said:
Well a friend of mine has flashed the Jellybean ROM onto his prime and now it wont boot into the OS. It can boot into CWM and bootloader. However when connecting to a computer it shows up as unknown (I've tried intstalling both ASUS and Universal naked drivers with the same result) no matter what mode it is in (fastboot, APX or recovery). So I can't use adb and it's an old CWM version that doesn't support an external SD. I have tried different computers and a different cable without success, also for it to be recognized by a computer the cable connecting to the primes port needs to be bent to a certain position, though I am not sure if this matters. So is this prime bricked or is there still hope?
Click to expand...
Click to collapse
It is not bricked. I'm still not convinced you are on jellybean bootloader as there is not a version of Cwm that works with it and you still have cwm.
First thing you need to do is confirm what bootloader you are on before you really brick it.
Switch the machine on and look where the tegra logo is. If it is bottom center you are still on ICS bootloader and if it is bottom right it is jellybean bootloader.
We need to know this to point you to the correct version of twrp to flash to start.
Yeah, the logo is still bottom center. But can I flash TWRP on with it saying Unknown Device when connecting to a computer as I know I can't use such things as adb and fastboot commands until it is recognized?
JJ2197 said:
Yeah, the logo is still bottom center. But can I flash TWRP on with it saying Unknown Device when connecting to a computer as I know I can't use such things as adb and fastboot commands until it is recognized?
Click to expand...
Click to collapse
Really you are going to need to get into fastboot and get the drivers installed.
I'm guessing you know how to get into fastboot but if you don't then hold down volume down and power button for 10 seconds when off. When the icons appear press volume down to go over to the USB icon and then press volume up. It will freeze on the prime screen at this point and that is fastboot mode.
Now go into device manager and try to install naked drivers. If this does not work then try in on another pc. If this still does not work then you have a faulty cable. A faulty cable can still charge the tablet but will not work in pc.
At this moment my money is on your cable being faulty over something you said earlier about having to play with it. You can buy a replacement cheaply on eBay.
Well at first I couldn't get the prime to be recognized by any PC so I got a replacement and that cable didn't work either. However the cable was stuck, so I had tried pulling it in different directions and then all of a sudden the PC had recognized it. This also worked for the other cable, figuring me to believe there is something wrong with the pins on the primes port. Anyways I've tried installing drivers, ASUS did nothing and the naked drivers would tell me the drivers were either not for the device or not 64 bit compatible. I've tried in fastboot, recovery and APX with the same result.
JJ2197 said:
Well at first I couldn't get the prime to be recognized by any PC so I got a replacement and that cable didn't work either. However the cable was stuck, so I had tried pulling it in different directions and then all of a sudden the PC had recognized it. This also worked for the other cable, figuring me to believe there is something wrong with the pins on the primes port. Anyways I've tried installing drivers, ASUS did nothing and the naked drivers would tell me the drivers were either not for the device or not 64 bit compatible. I've tried in fastboot, recovery and APX with the same result.
Click to expand...
Click to collapse
Without getting any drivers installed at all there is not much we can do.
Cwm doesn't support external cards and even tho I could make you a flashable zip to install twrp you couldn't get it on there.
If you can get back into the machine at all then we could use wireless adb and send the files over that way or use es file explorer to access network shares and take them over.
So it is pretty much as I had feared even though I can turn it on and boot into Recovery, fastboot and APX without being able to use adb commands it is as good as bricked. I'm still wondering as to why I can't seem to install the drivers, does the device think it is something else?
JJ2197 said:
So it is pretty much as I had feared even though I can turn it on and boot into Recovery, fastboot and APX without being able to use adb commands it is as good as bricked. I'm still wondering as to why I can't seem to install the drivers, does the device think it is something else?
Click to expand...
Click to collapse
This normally happens with a faulty cable and as you said you think the pins are faulty so it could be that instead.
You could try going to the wipe icon where the fastboot icon is and try running that. If there is a rom still on there it will try to factory reset but I can't guarantee that will work but at this point you have nothing to lose.
I've done a factory reset clear delvic and regular cache, wipe user data etc in CWM already.
JJ2197 said:
I've done a factory reset clear delvic and regular cache, wipe user data etc in CWM already.
Click to expand...
Click to collapse
I'm not talking about in CWM. I'm talking about the wipe icon where the fastboot icon is also.
Isn't the factory reset the same in both CWM and bootloader?
JJ2197 said:
Isn't the factory reset the same in both CWM and bootloader?
Click to expand...
Click to collapse
No
Hmm, really. What does bootloader change the CWM doesn't or do you just know it's not the same?
JJ2197 said:
Hmm, really. What does bootloader change the CWM doesn't or do you just know it's not the same?
Click to expand...
Click to collapse
It reformats the partitions back to stock except the system partition.
I'm not saying this is going to work for you. Just as you are your only other option if the pins are broke is to get it sent back to asus and they will swap out the whole mobo so you might as well have a go.

Cant connect xperia p

Hello,
I isntalled that rom with kernel. http://forum.xda-developers.com/showthread.php?t=2391858. and the problem is now that my pc, cant see my phone, i tried every method i found on the site. i instaled all drivers and reinstaled from flashtool like 10 times, and my pc still doesnt see device. while i try to connenct via fasboot. i have the violet light for like 2 sekonds and after it the device starts to boot normally, same is with flashboot. flash tool does not give any msg of connecting a device. can any tell a way to get it working? i want to flash to stock soft. but i cant cause nothing sees the device with installed drivers.
FOrogot to ad that i flashed the aospa rom, cause i thought i will get usb working atlast. but im stuck now on com.android.phone stopped working, and i cant even download any other rom using phone:
EDIT
Just read in nemesis kernel topic "* Computer/PC Companion and even Flash Tool cannot detect.". so Any ideas how can i flash it. without have any other rom on sd card? I will be rlly happy if someone can help me, i know i made a big mistake but not doin recovery, first time i not did and all went wrong.
do u have SUS? (Sony Update Service)
try connecting with SUS if SUS don't detect your phone then flashtool will not detect your phone also.
Well it doesnt not see to, In my opinion no porgram will see it if device manager cant see it, but now after some slleep i got and idea. Could it be maybe the problem of to old micro usb cable. because my got broken. and i have to use from my sister that has samsung wave.
Good Luck.
LED should be blue not violet for fastboot.
Make sure the phone is shut down first, press volume up + power for 10-15 seconds untill you feel 3 vibrations.
Well whatever coulour it is violet or blue. I press the volume up connect the phone to usb. And i got this coulur for 2-3 second and then it goes to charging mode. it happens every time. Same happens to flashboot. Green for 2-3 sec and the it goes to charging mode.
maebara said:
Well whatever coulour it is violet or blue. I press the volume up connect the phone to usb. And i got this coulur for 2-3 second and then it goes to charging mode. it happens every time. Same happens to flashboot. Green for 2-3 sec and the it goes to charging mode.
Click to expand...
Click to collapse
It's not "whatever" if it's violet it means it's waiting for vol- to enter CWM and not entering fastboot.
Make sure the phone is turned off as I explained.
Phone is turned of, I allways wait for those 3 vibrations before i begin the process. And here to enter the cwm is blue, and for fastboot i have violet. If i had a camera i would record it to prove it.
maebara said:
Phone is turned of, I allways wait for those 3 vibrations before i begin the process. And here to enter the cwm is blue, and for fastboot i have violet. If i had a camera i would record it to prove it.
Click to expand...
Click to collapse
Flashtool and PCC worked before on the same PC?
What do you see in flashtool log when you connect in fastboot and flash mode?
ChikeD said:
Flashtool and PCC worked before on the same PC?
What do you see in flashtool log when you connect in fastboot and flash mode?
Click to expand...
Click to collapse
THey say nothing, As i say in the first post. PC does not see the device, Flastool handles as nothing has been conected. same device manager on wondows. no poop outs that drivers are missing, or anything.. Fastboot has allways waiting for device, doesnt matter how much i try to onnect. It worked before. I tried on other laptop but its same. Thats why later i wrot that maybe this cable is to old for that phone. But it works for other phones.
maebara said:
THey say nothing, As i say in the first post. PC does not see the device, Flastool handles as nothing has been conected. same device manager on wondows. no poop outs that drivers are missing, or anything.. Fastboot has allways waiting for device, doesnt matter how much i try to onnect. It worked before. I tried on other laptop but its same. Thats why later i wrot that maybe this cable is to old for that phone. But it works for other phones.
Click to expand...
Click to collapse
Your USB did not work before?
ChikeD said:
Your USB did not work before?
Click to expand...
Click to collapse
I got my orginal mircro usb from xperia but it went boroken last time, on monday i go buy me new. but i wanted to use my sis micro usb from samsung wave, well mirco usb is micro usb imo, but i can be wrong. before i was able to do things on that cable too. but now idk if its the cable fault. or its phone, cause seems i can only charge my phone throught it. even on pc. it only charges nothing more. I just want to know if there is any way to make phone visible to pc, installing drivers, reseting. wiping data on phone, nothing works
maebara said:
I got my orginal mircro usb from xperia but it went boroken last time, on monday i go buy me new. but i wanted to use my sis micro usb from samsung wave, well mirco usb is micro usb imo, but i can be wrong. before i was able to do things on that cable too. but now idk if its the cable fault. or its phone, cause seems i can only charge my phone throught it. even on pc. it only charges nothing more. I just want to know if there is any way to make phone visible to pc, installing drivers, reseting. wiping data on phone, nothing works
Click to expand...
Click to collapse
It could be the connector on the phone.
I use samsung cable no problem, the Sony that came with XP is still sealed

[Q] fastboot, adb, rsd doesnt work on xt910

Hi, i bought a phone from a guy that said the battery is dead.
i bought new battery, installed, phone works (i was happy), and started to charge it, as new battery had 20%.
after a while it showed 30%, but then i noticed it went back to 20%, untill it died with "white light of death".
i hotwired the battery, let it charge to 80%
tried to switch back to wall charger, but again, although it says its charging battary drains, same with usb cable to pc.
i also noticed that battery drains very quick without any charge, so i thought maybe its firmware issue.
i installed every possible driver and rsdlite, but it just wont connect in adb or fastboot mod
i thought usb port in the phone is damaged, but it shows charge when connected, and also in some option in the bootloader it does recognize the phone as mz 600 something, but that doesnt help.
the phone currently have what seems to be stock GB + stock recovery
i tried to get Safe Strap recovery, but it didnt work.
from what i read the only firmware updates (not rom) are via fastboot.
i probably can flash custom rom via the stock recovery, but im not sure if it would help.
did anyone experience something similar?
Hi all,
I have Motorola XT621 Primus, after some playings with it and trying to root and add RTL patching i got a brick.
Now the status is that i have fastboot mode working but bootloader is locked, no recovery working and no ADB working, no boot too.
I tryed many ways to flash or unlock bootloader but nothing works. Any commands like fstboot oem got output like (...)
Is there any way to unlock bootloader via fastboot and flash new rom or it completely bricked?
Thanks!
if you have fastboot you can flash recovery
http://www.youtube.com/watch?v=9vaHPVV_-b0
Just make sure you have a good battery or you will have to get a factory cable if the battery say battery low.
SimonK9 said:
if you have fastboot you can flash recovery
http://www.youtube.com/watch?v=9vaHPVV_-b0
Click to expand...
Click to collapse
Problem is that bootloader locked and every thing that i try to flash fails...
alfa156v said:
Problem is that bootloader locked and every thing that i try to flash fails...
Click to expand...
Click to collapse
Get the gb firm, unzip it, and flash one by one the archives, if you don't know how, open the .xml and there are the commands, you can do it in linux/windows, i had a similar problem, cannot flash anything, my razr only turns into fastboot by using factory cable, and wired the battery, flashing couple of files,then i did flashed one by one and get error in webtop, but it work, the razr turn on (i did this in linux), then i where able to charge the battery and connect to windows, run the rsd, put another jb firm (had to download 5-6 'till i get the right) and works like a charm.
You need the android sdk tools, the latest fastboot, your drivers and some good luck. :good:
(Sorry my bad english)
By the way, if you get the "battery low" line, it doesn't matter, you need to use the factory cable + the battery wire to charger metod, do it and you'll get the O.K.
I have exactly the same problem.. Can we do something vía stock recovery?
Sent from my Nexus 5

[Q] Nexus wont boot

Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
aaronthew said:
Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
Click to expand...
Click to collapse
You can't go into your recovery?
Install ADB and try to connect your Nexus to your PC and enter "adb devices". See if your tablet is recognized like that.
How to setup ADB
Do not use toolkits with Nexus devices.
cheers for the advice but nope no luck still wont connect
aaronthew said:
cheers for the advice but nope no luck still wont connect
Click to expand...
Click to collapse
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
es0tericcha0s said:
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
Click to expand...
Click to collapse
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
aaronthew said:
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
Click to expand...
Click to collapse
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
es0tericcha0s said:
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
Click to expand...
Click to collapse
if i choose recover, to gets stuck on the google screen
Tried different cables, Pc and PC ports no luck
I could try get linux on vm when i get home? never used it thou
Sucks man. Such a random thing and not typical of most Nexus issues. This is the only other option I can think of then: http://mobiletechvideos.mybigcommerce.com/asus-nexus-7-2012/ - Brick service. These guys are legit. They have a great reputation and I've personally used their services twice (different devices) and one was fixed while the other was a lost cause, but Josh was nice enough to refund some of the money since it didn't work. I'm guessing they would need to do what's called a JTAG service where they hook up (usually solder) a special cable to a specific port on the board and it kind of circumvents the other issues and reloads the OS back on.
Thanks for all you hep mate will prob give them a try
No problem. Good luck!

Fastboot problem

I have a mtk6580 the phone only stays in fastboot for 10 seconds and doesnt respond to any fastboot comands.I don't think its a driver problem because it works fine on another phone which is also a 65xx. I also tried a linux vm. With the same results. Mostly i just want to root the phone. Even set my bios so the usb are recognized as usb 2. As well i tried a lot of one click solutions to get root. Also miracle box and mtk-tools. The phone has no reset button and the battery cant be removed. Please help.
smackpotato said:
I have a mtk6580 the phone only stays in fastboot for 10 seconds and doesnt respond to any fastboot comands.I don't think its a driver problem because it works fine on another phone which is also a 65xx. I also tried a linux vm. With the same results. Mostly i just want to root the phone. Even set my bios so the usb are recognized as usb 2. As well i tried a lot of one click solutions to get root. Also miracle box and mtk-tools. The phone has no reset button and the battery cant be removed. Please help.
Click to expand...
Click to collapse
I take it you're on Windows?
Ya i tried a linux usb stick but my bios won't let me boot from usb. Im getting shut down at every step
Ok i tried a linux usb stick still no results
Get fastboot and adb package?? Maybe that's the problem

Categories

Resources