Database Info

Samsung Infuse Soft Brick and Distorted Clockwork Mod Recovery

I am in desperate need of help .. I am not a noob to flashing roms and rooting, however I have a one-off situation w/ no precedents to my knowledge. I have read these and other forums for days to no avail.
I was flashing Infintium Rom 4.0.4 from MIUI 2.3.6. I followed the steps listed in the post (http://forum.xda-developers.com/showthread.php?t=1661690). After flashing I rebooted and waited however the phone was/is stuck on the Samsung logo and never progressed. I then pulled the battery and attempted to go back to recovery mode to reflash make sure I did flashed correctly. However, upon going back into recovery I was greeted by the below image.
Clockwork Mod is extremely distorted and flat out unusable !! As I read further down it advised to use Heimdall (http://forum.xda-developers.com/showthread.php?t=1331381). I downloaded and attempted to use, however my PC (Which by the way is Windows 7 64-Bit) recognized the phone but the Heimdall software did not. I already had the right drivers for the PC and phone. After a few tries I deleted the files and reapplied them. On the 2nd menu after selecting list devices, on the drop down the option for Samsung USB Composite Device neeever ever appears. I also tried on a different PC that ddnt have the drivers and started brand new. Still, Heimdall ddnt recognize.
I also tried to flash numerous files including but not limited to GTG Ultimate Unbrick via Odin. Again, PC recognized USB connection however program ddnt. At this point, I do not know if it is because the status of Clockwork Mod on my phone, but I know it is not because of the drivers or the USB ports on my PC.
In addition to that, I have just scrapped the idea of flashing or getting in CWM and just wanted to do a hard reset (While phone is off held Vol down and Power, once started released power and contimued to hold Vol down. This should take the phone from the Samsung logo to an alt menu that will give the option to do a factory reset. But again w/ my luck .. that screen neeever appears.
In short I have tried at least 3 different ways and many maaany variations to get the phone back into recovery or into a full boot and had NO success.. Please help and ask as many questions as needed to diagnose and resolve this issue .. Thanx in advance and apologize in advance if posted in the wrong thread.

Are you placing your phone in download mode?
Remove battery and place it back.
Hold vol+ & vol- , and plug in the usb to your phone with the other end already connected to the PC.
Now see if Odin or heimdall recognize your device.
Sent from my sweet & buttery Infuse

andros11 said:
Are you placing your phone in download mode?
Remove battery and place it back.
Hold vol+ & vol- , and plug in the usb to your phone with the other end already connected to the PC.
Now see if Odin or heimdall recognize your device.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
I have done so neither Odin or Heimdall are recognizing it or showing the phone is connected.

ohsirus said:
I have done so neither Odin or Heimdall are recognizing it or showing the phone is connected.
Click to expand...
Click to collapse
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
http://d-h.st/sKF
Then open Odin/Hemdall and plug your phone in again while in Download Mode.

Ryo Misaki said:
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
Then open Odin/Hemdall and plug your phone in again while in Download Mode.
Click to expand...
Click to collapse
I will try again .. Downloaded, rebooting then will go thru the process again .. standby

Ryo Misaki said:
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
Then open Odin/Hemdall and plug your phone in again while in Download Mode.
Click to expand...
Click to collapse
no change .. still shows disconnected

The pic u have posted it shows u need to press the up button to get the download mode (continue)
Sent from my Galaxy Nexus using Tapatalk 2

rkkaranrk said:
The pic u have posted it shows u need to press the up button to get the download mode (continue)
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I just did that to post a pic as an example .. I did go to download mode and not recognizing it

The CWM screen is shot because you don't have gingerbread bootloaders, it will always look like that until to can flash the right ones..
Have you tried different cables, different ports, etc?
Sometimes mine would recognize.. sometimes being plugged in first then running Odin works, sometimes I would have to run Odin and then plug in the phone.. kinda a crapshoot...
Its powered by Jellybeaned AOKP!

drnecropolis said:
The CWM screen is shot because you don't have gingerbread bootloaders, it will always look like that until to can flash the right ones..
Have you tried different cables, different ports, etc?
Sometimes mine would recognize.. sometimes being plugged in first then running Odin works, sometimes I would have to run Odin and then plug in the phone.. kinda a crapshoot...
Its powered by Jellybeaned AOKP!
Click to expand...
Click to collapse
I know I need to get the bootloader and a kernel on it however I cant = ( .. yet .. I have 4 different ports on my PC and have tried them all. i have tried phone on then run programs and programs on 1st then phone on and no new results.
I found this short video and it describes my exact situation .. please watch to futher understand http://www.youtube.com/watch?v=OHLUYckTlug

So u have odin and heimdal both on the same PC and drivers for them if yes then try this.
On the PC/Laptop uninstall all the drivers for samsung or any other phone and follow this.
Go to accessories> system tool> system restore and check the restore point where the drivers for heimdall were installed restore to a previous restore point after restore finishes install the drivers for Infuse and see now Odin recognizes ur phone, It should.

I had the same exact problem, do you have another phone on which you can install the same CWM recovery on? ...Because the clockwork mod recovery still works, it's just that you can't see it. So just flash a new ROM, by going back n forth between phones, clock how many clicks it takes to get to 'choose zip to install' then 'download' on the not messed up phone, then do the same on the screwy one, just keep doing that till u flash the new ROM.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] Asus tf700 JB 4.2 NOT WORKING

Hey guys, first time on here.
I've been trying to root my unlocked Asus tf700 running JB 4.2.1 for days and have been following all the xda guides with no luck.
I've tried to flash CMW on it through fastboot to no avail. Everything I see says, once you get into the bootloader or whatever, to press Vol Down until you get to the USB icon and then press volume up but there isn't any USB icon. Right when I get into the bootloader, after I hold Vol Down and Pwr, the first thing it reads on the top left corner of the screen is "Key driver missing." But I have downloaded the drivers from the asus website. Any suggestions about why this is happening? I also tried just using Motochopper (http://forum.xda-developers.com/showthread.php?t=2230763) but when it ran it said failure. I booted it up and I had SuperSU but I tried to open it and it said "no SU binary found! This is a problem!". Any suggestions on how to root this and flash a recovery on it would be greatly appreciated, because none of the other forums guides seem to work? help out a noob!

npf24 said:
Hey guys, first time on here.
I've been trying to root my unlocked Asus tf700 running JB 4.2.1 for days and have been following all the xda guides with no luck.
I've tried to flash CMW on it through fastboot to no avail. Everything I see says, once you get into the bootloader or whatever, to press Vol Down until you get to the USB icon and then press volume up but there isn't any USB icon. Right when I get into the bootloader, after I hold Vol Down and Pwr, the first thing it reads on the top left corner of the screen is "Key driver missing." But I have downloaded the drivers from the asus website. Any suggestions about why this is happening? I also tried just using Motochopper (http://forum.xda-developers.com/showthread.php?t=2230763) but when it ran it said failure. I booted it up and I had SuperSU but I tried to open it and it said "no SU binary found! This is a problem!". Any suggestions on how to root this and flash a recovery on it would be greatly appreciated, because none of the other forums guides seem to work? help out a noob!
Click to expand...
Click to collapse
If your device is unlocked you don’t need MotoChopper for rooting, just flash TWRP Recovery and it will ask you if you want to root your device (in case it detect that root is missing).
For the "Key driver missing" error, just ignore it, Fastboot will work just fine as long as you are sure that the drivers are installed just fine.

Pretoriano80 said:
If your device is unlocked you don’t need MotoChopper for rooting, just flash TWRP Recovery and it will ask you if you want to root your device (in case it detect that root is missing).
For the "Key driver missing" error, just ignore it, Fastboot will work just fine as long as you are sure that the drivers are installed just fine.
Click to expand...
Click to collapse
Thanks, but I'm still confused. I thought you needed GooManager to install TWRP, and GooManager won't work unless you have a rooted device.

npf24 said:
Thanks, but I'm still confused. I thought you needed GooManager to install TWRP, and GooManager won't work unless you have a rooted device.
Click to expand...
Click to collapse
Goo Manager is not mandatory, you can still flash the TWRP via fastboot.You can find more info on the TWRP website.

Sounds like a driver issue to me. If you can't fastboot cwm or use motochopper something is up.
Could also be your usb connection. Try another cable or port or another pc.

lafester said:
Sounds like a driver issue to me. If you can't fastboot cwm or use motochopper something is up.
Could also be your usb connection. Try another cable or port or another pc.
Click to expand...
Click to collapse
yeah ive tried two differ pcs already so I dont think its that. It definitely could be the drivers. Ive tried to install them from the asus site a bunch of times though so idk whats up.

npf24 said:
yeah ive tried two differ pcs already so I dont think its that. It definitely could be the drivers. Ive tried to install them from the asus site a bunch of times though so idk whats up.
Click to expand...
Click to collapse
If you have recently updated your firmware to xxxx.10, you will "not" be able to run motochopper (there is nothing wrong with your PC or cables), Ausus closed the Moto root opening with the latest firmware. However, you can still root following the TWRP instructions.....as indicated above.

just some more info
So i tried re installing the drivers one more time to my PC, and everything went okay, so I'm sure it can't be the drivers, although the error still comes up. And just to tell you guys, when moto chopper runs it says, "waiting for device, daemon not running, starting it now on port 5057, daemon started successfully." Don't know if that helps at all to what the problem is, but just some more info. Now I'll try flashing twrp and rooting that way.

Nothing works at all
dishinit said:
If you have recently updated your firmware to xxxx.10, you will "not" be able to run motochopper (there is nothing wrong with your PC or cables), Ausus closed the Moto root opening with the latest firmware. However, you can still root following the TWRP instructions.....as indicated above.
Click to expand...
Click to collapse
So I went to the TWRP website to try and install twrp 2.6.0. The three options on how to do this were:
1. Via GooManager - which I can't do because my device isn't rooted.
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
3. The terminal method.
I just tried the terminal method, and that didn't work either because when I typed in what it said I was supposed to type in, it said "permission denied."
So yeah.

npf24 said:
So I went to the TWRP website to try and install twrp 2.6.0. The three options on how to do this were:
1. Via GooManager - which I can't do because my device isn't rooted.
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
3. The terminal method.
I just tried the terminal method, and that didn't work either because when I typed in what it said I was supposed to type in, it said "permission denied."
So yeah.
Click to expand...
Click to collapse
I vaguely remember running Motochopper & getting the same message.....it you are on .8 or earlier firmware (in 4.2.1), Motochopper should run.
I think I turned off my tablet, left it connected to PC & then ran motochopper & tablet self booted.....lots of ABD's out of date messages, but Moto worked it's way through them and rooted my device.
I have read of problems with Win 7 (my OS) & Motochopper, but none if used with XP.
Good luck, & Let us know how t goes

npf24 said:
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
Click to expand...
Click to collapse
Recent bootloaders do not have a USB icon because they activate fastboot already while the boot menu is visible (read the tiny text in the top left corner).

dishinit said:
I vaguely remember running Motochopper & getting the same message.....it you are on .8 or earlier firmware (in 4.2.1), Motochopper should run.
I think I turned off my tablet, left it connected to PC & then ran motochopper & tablet self booted.....lots of ABD's out of date messages, but Moto worked it's way through them and rooted my device.
I have read of problems with Win 7 (my OS) & Motochopper, but none if used with XP.
Good luck, & Let us know how t goes
Click to expand...
Click to collapse
I tried what you said. The tablet didn't self-boot when I ran Motochopper again. It just stayed powered off. I turned it on, and the exact same thing happened. except there was another error in motochopper this time. it said "FAILURE ALREADY EXISTS." any other suggestions?

_that said:
Recent bootloaders do not have a USB icon because they activate fastboot already while the boot menu is visible (read the tiny text in the top left corner).
Click to expand...
Click to collapse
Okay that's what I thought. So if I do that second method on twrp, I guess I should just skip when it says to press the USB icon because fast boot is already running??

npf24 said:
Okay that's what I thought. So if I do that second method on twrp, I guess I should just skip when it says to press the USB icon because fast boot is already running??
Click to expand...
Click to collapse
Correct.

_that beat me to it - again. )

how to push file to device?

So i messed around with my n5 and now it wont boot, black screen with background light on. No back up, no .zip on the phone.
Apparantly I cant mount usb my phone with TWRP(v.2.7.1) - nothing happens when I press the buttons.
ADB doesn't recognize my phone as well.
Got ideas on how to fix?

flash factory image with fastboot.
Tapatalked from my Hammerhead.

Timoooo said:
So i messed around with my n5 and now it wont boot, black screen with background light on. No back up, no .zip on the phone.
Apparantly I cant mount usb my phone with TWRP(v.2.7.1) - nothing happens when I press the buttons.
ADB doesn't recognize my phone as well.
Got ideas on how to fix?
Click to expand...
Click to collapse
First off, never mess around with your device without making a backup first. If you had, this post would not be necessary.
Take a look here:
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396

upndwn4par said:
First off, never mess around with your device without making a backup first. If you had, this post would not be necessary.
Take a look here:
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
Click to expand...
Click to collapse
Yeah I learned that the hard way now...
I'm guessing the main problem is that I cant access my system to turn adb on. So I followed the steps and installed the drivers. When the phone is in bootloader and I install the drivers its now connected as Android Bootloader Interface and not recognized by adb. When I try to install the drivers in recovery mode(phone was recognized as AOSP on Hammerhead with a yellow warning triangle) it says that no driver was found..

Timoooo said:
Yeah I learned that the hard way now...
I'm guessing the main problem is that I cant access my system to turn adb on. So I followed the steps and installed the drivers. When the phone is in bootloader and I install the drivers its now connected as Android Bootloader Interface and not recognized by adb. When I try to install the drivers in recovery mode(phone was recognized as AOSP on Hammerhead with a yellow warning triangle) it says that no driver was found..
Click to expand...
Click to collapse
adb works in custom recovery, not bootloader. You do not need USB debugging (this is an Android setting only) or to turn "adb on", so lets bust those myths right here
for more info, click the link to the sticky in my signature and read the "adb and fastboot, What is it?" thread, which will help you out with drivers etc too.

rootSU said:
adb works in custom recovery, not bootloader. You do not need USB debugging (this is an Android setting only) or to turn "adb on", so lets bust those myths right here
for more info, click the link to the sticky in my signature and read the "adb and fastboot, What is it?" thread, which will help you out with drivers etc too.
Click to expand...
Click to collapse
thanks got everything to work that way!

Timoooo said:
thanks got everything to work that way!
Click to expand...
Click to collapse
No problem. Cool

[Q] Hard-Bricked, no boot. Failed during flash

OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?

gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
+1

gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
So will the tablet not boot into the bootloader ?
Thx Josh

lj50036 said:
So will the tablet not boot into the bootloader ?
Thx Josh
Click to expand...
Click to collapse
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.

gtgeek said:
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.
Click to expand...
Click to collapse
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh

lj50036 said:
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh
Click to expand...
Click to collapse
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?

gtgeek said:
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?
Click to expand...
Click to collapse
Nope there is just no way...
The chip is locked down ... :crying:
There is lots of info out there but its just info ...
No one to date has come back from where you are ....
Thx Josh

[Q] My One is not booting at all, and does not react when i try to charge it

If i just use my charger, there is no response from the phone. When i try with the laptop, my laptop makes a sound to show that the phone has been plugged in, but the phone does not respond at all. I had a cm12 nightly flashed, and tried to flash Francos kernel on it, which made the phone get stuck on that blue alien logo when booting. After trying various fixes with no results, i just wiped everything ( i had no backups because i am a stupid ****) and then it got stuck on the Oneplus One logo. Now i am trying this http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541[1] and while i used the flash all.bat file, i noticed that cmd just kept showing waiting for device response (or something like that) which was weird, since it had completed some of the previous actions. Then i looked at my phone, with nothing at the screen. And it is now that it does not boot at all (not into the recovery, fast boot, normally, nothing) and does not show anything while i try to charge. What can i do?
Before the cmd process, the phone was showing up as a unit under Computer, but it is not anymore.
Just before, when i plugged it in, windows showed that something had been connected, but it did not know what, so i assume that there are some driver issues or something, though i have installed the qpst driver.
I also made a reddit post about it, where i got some response, but i could not go through with those either https://www.reddit.com/r/oneplus/comments/3bzwel/my_one_is_not_booting_at_all_and_does_not_react/
Do you know what i am doing wrong? Got any other fixes? Thanks in advance.

One get a otg cable then flash any custom rom using ur pen drive or go to adb and connect ur phone and check in device manager if it shows ur phone there or install any adb driver the try that flashall.bat it will surely work!! But I would say get a otg cable
Transmitted via Bacon

alan2500 said:
If i just use my charger, there is no response from the phone. When i try with the laptop, my laptop makes a sound to show that the phone has been plugged in, but the phone does not respond at all. I had a cm12 nightly flashed, and tried to flash Francos kernel on it, which made the phone get stuck on that blue alien logo when booting. After trying various fixes with no results, i just wiped everything ( i had no backups because i am a stupid ****) and then it got stuck on the Oneplus One logo. Now i am trying this http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541[1] and while i used the flash all.bat file, i noticed that cmd just kept showing waiting for device response (or something like that) which was weird, since it had completed some of the previous actions. Then i looked at my phone, with nothing at the screen. And it is now that it does not boot at all (not into the recovery, fast boot, normally, nothing) and does not show anything while i try to charge. What can i do?
Before the cmd process, the phone was showing up as a unit under Computer, but it is not anymore.
Just before, when i plugged it in, windows showed that something had been connected, but it did not know what, so i assume that there are some driver issues or something, though i have installed the qpst driver.
I also made a reddit post about it, where i got some response, but i could not go through with those either https://www.reddit.com/r/oneplus/comments/3bzwel/my_one_is_not_booting_at_all_and_does_not_react/
Do you know what i am doing wrong? Got any other fixes? Thanks in advance.
Click to expand...
Click to collapse
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
yashshan said:
One get a otg cable then flash any custom rom using ur pen drive or go to adb and connect ur phone and check in device manager if it shows ur phone there or install any adb driver the try that flashall.bat it will surely work!! But I would say get a otg cable
Transmitted via Bacon
Click to expand...
Click to collapse
That won't work, the phone isn't turning on.

Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
Thanks a lot, i dont know how i did not come upon that link while trying various fixes, now i can boot the phone again

Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
Uh, new problem, i used the toolkit to unlock the bootloader, and i had to use the Ultimate Tool kit to get TWRP on it. When i connect the phone to the pc (windows 7) i keep getting a message saying i have to format the phone before i can use it. When i click that, it says its writing protected. When i boot up the phone, it turns on, and i can go to the home screen (some times) but after a few seconds, it just turns off it self. Sorry for asking for your help again, but do you know of this problem? Google just came up with results for people with battery problems.

Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
I am just going to message you again before i mess up my phone even more, after a lot of hassle, i messed something up and redid the guide in the link you sended to me. According to the Oneplus one toolkit, my bootloader is unlocked. I can not enter fastboot, so i can not get a custom recovery or root. I can not turn on the phone normally either. I can Volume up+power button though, which takes me to the ColorOS RECOVERY screen. I would appreciate your help.

alan2500 said:
I am just going to message you again before i mess up my phone even more, after a lot of hassle, i messed something up and redid the guide in the link you sended to me. According to the Oneplus one toolkit, my bootloader is unlocked. I can not enter fastboot, so i can not get a custom recovery or root. I can not turn on the phone normally either. I can Volume up+power button though, which takes me to the ColorOS RECOVERY screen. I would appreciate your help.
Click to expand...
Click to collapse
Get rid of the toolkit,they're nothing but trouble. Plus, you don't need it. Plus, they allow you to bypass some very crucial learning experience. Power + volume up should take you to fastboot, not recovery, the button combo for recovery is power + volume down. Are you sure you can't get into fastboot? Is adb working in ColorOS recovery?

Heisenberg said:
Get rid of the toolkit,they're nothing but trouble. Plus, you don't need it. Plus, they allow you to bypass some very crucial learning experience. Power + volume up should take you to fastboot, not recovery, the button combo for recovery is power + volume down. Are you sure you can't get into fastboot? Is adb working in ColorOS recovery?
Click to expand...
Click to collapse
Oh brainfart, yup, its volume down+power that goes to the recovery. I just tried volume up+power, and now it goes into fastboot. I did try before, and the vibration was there, but no text on the screen. Not sure what to say about adb, when i launch adb.exe the CMD window just opens up, types a bunch in so fast that i cant read it, and then it closes down. It does the same thing when my phone is not plugged in, so i assume it does not work.

alan2500 said:
Oh brainfart, yup, its volume down+power that goes to the recovery. I just tried volume up+power, and now it goes into fastboot. I did try before, and the vibration was there, but no text on the screen. Not sure what to say about adb, when i launch adb.exe the CMD window just opens up, types a bunch in so fast that i cant read it, and then it closes down. It does the same thing when my phone is not plugged in, so i assume it does not work.
Click to expand...
Click to collapse
Ok, you're not meant to launch adb.exe like that though. You go to the folder where adb.exe is located, then hold shift and right click the mouse, and select "open command prompt here" from the menu, then you can issue adb commands. The same process goes for using fastboot. Anyway, now that you have access to fastboot all you should need to do is flash the stock images, go to section 8 of my guide thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2839471

Heisenberg said:
Ok, you're not meant to launch adb.exe like that though. You go to the folder where adb.exe is located, then hold shift and right click the mouse, and select "open command prompt here" from the menu, then you can issue adb commands. The same process goes for using fastboot. Anyway, now that you have access to fastboot all you should need to do is flash the stock images, go to section 8 of my guide thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Thanks a bunch, i got through it this time lol. So just to be sure that i do not end up bricking my phone again, can i just install TWRP, root, then dirty flash the latest CM nightly? I have no idea whats best to go with, and other than long battery life and good performance, i do not really have any needs, so i am thinking the latest cm will be fine. It was a nightly i was running before i bricked the phone actually.

alan2500 said:
Thanks a bunch, i got through it this time lol. So just to be sure that i do not end up bricking my phone again, can i just install TWRP, root, then dirty flash the latest CM nightly? I have no idea whats best to go with, and other than long battery life and good performance, i do not really have any needs, so i am thinking the latest cm will be fine. It was a nightly i was running before i bricked the phone actually.
Click to expand...
Click to collapse
Don't dirty flash, clean flash. Try out the Exodus ROM, great battery life and great features too.