Related
i have already checked xda for a solution but couldnt find one i even checked google and youtube and still found nothing i am in need help bad. i will even pay someone paypal if they can help me with my phone
i downloaded the matrix rom and i liked it but i wanted to go back to ice cream sandwhich for the day so when i tried to go to recovery it froze on the google screen while trying to get to recovery i kept trying and trying but my recovery wasnt working i couldnt get to it. so i went to titanium back up and clicked un-install all system and data because i thought it was when i restored all system and data from ICS but after i did the uninstall i kept getting a force close alot of things and i got all the way down to one and it was process.android i think and everytime i clicked force close it popped right bacj up instently. so i took out the battery and put it back in and now i cant power on my phone it gets stuck on the matrix screen. can you please help me i can only acces the volume up power button menu.
*solved*
Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium
it wont let me do any of that it keeps saying waiting for device then gets stuck on that ive installed pdanet but it keeps giving me a htc sync error =1 and my bootloader and everything was already unlocked i dont know what to do i cant turn my phone on or get to recovery. thats why im paying 100 dollars to anyone who can help me restore my phone and make sure its up and running ive been trying for 2 days now and thats my work phone and everything im stressed
Serious_Beans said:
Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
when i turn on the phone and it keeps trying to load the matrix animation the phone still connects with my computer and says removable disk f but when i try and click on it. it says please insert a disk into removable disk f
Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium
Serious_Beans said:
Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
at the bottom of my phone screen it says fastboot statud - FAILInvalid command
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Make sure you are using the most up to date drivers and then use ADB to install recovery again. If I'm understanding it right I think that's what you need to try.
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
can someone help me threw team viewer and just access my computer threw that and help me that way
Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Maybe you should just try Odin.
http://forum.xda-developers.com/showthread.php?t=1022481
DL: http://droidangel.blogspot.com/2011/05/odin-multi-downloader-flasher-program.html
Greetz
OP... check your PM inbox.
Why on earth have you posted this thread 6 times? Lol
Sent from my Nexus S using XDA App
scottypeterson said:
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Click to expand...
Click to collapse
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file
Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps
mathkid95 said:
Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps
Click to expand...
Click to collapse
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
Da_Reaper said:
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file
Click to expand...
Click to collapse
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.
Yes thank you guys i love u all
check your mp , excepted if you found the solution.
$100? Lol
Sent from my Nexus S using XDA App
crump84 said:
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.
Click to expand...
Click to collapse
Yeah excuse me for not reading all 6 threads
Sent from my Nexus S using XDA App
Hi,
please help me! I hope it is not a brick.
I wanted to make full wipe. I made factory reset in recovery and then wiped sdcard.. Now I cannot boot ROM because there is no one and I have nothing on my SD. So I even cannot copy rom or backup back to phone.
Is there any way out? (
EDIT: I think I can push files (e.g. backup) through adb, right? I installed adb for dummies but when I want to execute SDKmanager.exe. it only opens black window and immediately closes it. I cannot continue
devcager said:
Hi,
please help me! I hope it is not a brick.
I wanted to make full wipe. I made factory reset in recovery and then wiped sdcard.. Now I cannot boot ROM because there is no one and I have nothing on my SD. So I even cannot copy rom or backup back to phone.
Is there any way out? (
EDIT: I think I can push files (e.g. backup) through adb, right? I installed adb for dummies but when I want to execute SDKmanager.exe. it only opens black window and immediately closes it. I cannot continue
Click to expand...
Click to collapse
Access your commands through a terminal window, like start > run > cmd to get into the prompt.
and from there work your way to your directory where you have placed it, and execute the command from that directory directly.
..
Thanks!
In the end I used adb to push backup in recovery...
All this I did because I wanted wipe my device - today I woke up and got a call and found out that my earphone stopped working I am afraid that it is due to condensation and next oxidation... I did not do anything wrong but when you come from cold winter weather into a warm flat it can happen Now I need to send it and hope the warranty will pass..
Anyway, I was looking for complete unroot process and found several advices. I am not clever from them. Is it enough to flash stock ROM? Recovery will be removed as well??
..
Election Day said:
Flash a stock ROM (this will also flash the stock recovery) and relock the bootloader with fastboot oem lock afterwards.
Click to expand...
Click to collapse
Ok. I have everything done but the relocking. Could you tell me how shall I do this? I tried to write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English) Cannot lock it
devcager said:
Ok. I have everything done but the relocking. Could you tell me how shall I do this? I tried to write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English) Cannot lock it
Click to expand...
Click to collapse
1.Switch off your phone
2.Connect your phone to your PC throught the USB cable
3.Switch on phone into fastboot
4.Provided that you have the driver for windows for the phone installed open Start/run/cmd (from your PC)
5.From the Android-SDK/platform-tools run the following "fastboot oem lock".
like :
C:\Android-sdk\platform-tools\fastboot oem lock
this will lock it immediately ...
mahanddeem said:
1.Switch off your phone
2.Connect your phone to your PC throught the USB cable
3.Switch on phone into fastboot
4.Provided that you have the driver for windows for the phone installed open Start/run/cmd (from your PC)
5.From the Android-SDK/platform-tools run the following "fastboot oem lock".
like :
C:\Android-sdk\platform-tools\fastboot oem lock
this will lock it immediately ...
Click to expand...
Click to collapse
it works only in "tools" and then it just says "waiting for device" and stucks When I tried "fastboot devices" it says nothing... I tried to reinstall drivers but maybe I have some old version? When I am in Windows copying files etc. it works well.
1. Make sure you open the command prompt IN in the folder with fastboot.exe.
2. Put the phone in fastboot mode.
3. In the command prompt type fastboot devices.
It will now show your serial number. If not its either you are such a noob that you managed to screw that up or the fastboot drivers are not installed. Or both.
albundy2010 said:
1. Make sure you open the command prompt IN in the folder with fastboot.exe.
2. Put the phone in fastboot mode.
3. In the command prompt type fastboot devices.
It will now show your serial number. If not its either you are such a noob that you managed to screw that up or the fastboot drivers are not installed. Or both.
Click to expand...
Click to collapse
OK. I really dont understand what could have been screwed up. Ok. It doesnt show anything. Just nothing. Cen you please send me the link for the drivers which should work? Maybe there is the problem. Fastboot drivers are something else than drivers for adb to be working? Because I dont know whats wrong. Thanks...
devcager said:
OK. I really dont understand what could have been screwed up. Ok. It doesnt show anything. Just nothing. Cen you please send me the link for the drivers which should work? Maybe there is the problem. Because I dont know whats wrong. Thanks...
Click to expand...
Click to collapse
If you have i9023 you need to add a line into the sdk for driver. You can search the tutorial threads for it.
Sent from my Nexus S using Tapatalk
try this
just check if you have fastboot and adb on the same folder, when I've rooted mine's got this issue, if cmd report "the command is an external one" simply means there is no such program in the folder you are in
copy both adb and fastboot in tools and platform-tools too, so you can run the command in both folder
cd>desktop > cd android>cd android-sdk> cd tools (then run adb or fastboot)
cd>desktop > cd android>cd android_sdk> cd platform-tools (thr run adb or fastboot)
1. Find out exactly what phone model you have if you don't know already.
2. Do the same for your computers os . Including 32 or 64 bit.
3. Combine that info and search the forum or just Google search. How to install fastboot drivers for phone model in step 1 with the os in step 2.
..
Thank you all. I decided to unroot it and relock it using Odin software which was great and quick. So I am done.... Adb has a lot of problems with drivers, commands, paths. This way was much easier
adb has no issues. User error.
albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
+1
Sent from my GT-I9100 using XDA App
albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
Maybe you are right. Maybe it was driver problem which I solved and then immediately used odin. Anyway, it is user friendly and I am finally done with what I wanted
albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
Agreed, but not the user friendliest.
For the OP: Good luck having it repaired!
I recently downloaded an ICS-based, Cynagen 9 ROM. It was making my Infuse very hot, so I decided to restore back to my previous ROM (Ethereal). I've tried Odin (can't get COM## to appear on it) and Heimdall (installed drivers, new version of Java, still doesn't recognize device). I don't want to pay to have it fixed again, so does anyone have any suggestions as to how I can fix myself? I have a blue CWM. Thanks.
GAPY427 said:
I recently downloaded an ICS-based, Cynagen 9 ROM. It was making my Infuse very hot, so I decided to restore back to my previous ROM (Ethereal). I've tried Odin (can't get COM## to appear on it) and Heimdall (installed drivers, new version of Java, still doesn't recognize device). I don't want to pay to have it fixed again, so does anyone have any suggestions as to how I can fix myself? I have a blue CWM. Thanks.
Click to expand...
Click to collapse
I flash a gb rom in blue cwm to get....red cwm, then flash a gb ROM again...
Have you tried diff usb port & cable....pc?
bigjoe2675 said:
I flash a gb rom in blue cwm to get....red cwm, then flash a gb ROM again...
Have you tried diff usb port & cable....pc?
Click to expand...
Click to collapse
I tried to reflash Ethereal ROM but it doesn't work. Oh, hell, I may just get GSIII on Verizon and call it a day.
GAPY427 said:
I tried to reflash Ethereal ROM but it doesn't work. Oh, hell, I may just get GSIII on Verizon and call it a day.
Click to expand...
Click to collapse
way to throw in the towel...some don't have that option...but XDA is learning experience, not for the towel tossers...
but if you require and want it we can provide it for you any and some assistance.
if you no longer require the thread you can click that triangle to the right of your op...and tell mods to close this thread..
thx
Sounds like if you would do a battery pull and get to download mode you could odin or heimdall back but if ya wanna toss money away to upgrade that's cool too
Sent from my SGH-I997 using xda premium
dawsndev said:
Sounds like if you would do a battery pull and get to download mode you could odin or heimdall back but if ya wanna toss money away to upgrade that's cool too
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
That's it -- I tried Odin and Heimdall but they didn't work. I downloaded the drivers several times, but both programs couldn't recognize my device. I couldn't see the COM## in Odin when I plugged in my Infuse.
bigjoe2675 said:
way to throw in the towel...some don't have that option...but XDA is learning experience, not for the towel tossers...
but if you require and want it we can provide it for you any and some assistance.
if you no longer require the thread you can click that triangle to the right of your op...and tell mods to close this thread..
thx
Click to expand...
Click to collapse
I want to fix my Infuse, but it becomes frustrating when you try these programs (Odin, etc.) and it isn't successful. I can't reboot my phone into anything right now (a new ROM, a restore, etc). It's stuck in the blue recovery.
to get COM## Try using a different usb plug. That has always been my fix for that issue
TheDSMjuggalo said:
to get COM## Try using a different usb plug. That has always been my fix for that issue
Click to expand...
Click to collapse
can I get in bluerecovery?
Sent from my SGH-I997 using xda premium
bradman117 said:
can I get in bluerecovery?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
using a different usb port is for odin. download and flash the modded 3e rom found here: http://forum.xda-developers.com/showthread.php?t=1092021
Then flash over the rom you wanted thru the recovery
GAPY427 said:
I want to fix my Infuse, but it becomes frustrating when you try these programs (Odin, etc.) and it isn't successful. I can't reboot my phone into anything right now (a new ROM, a restore, etc). It's stuck in the blue recovery.
Click to expand...
Click to collapse
Since you're stuck in recovery and can't get Heimdall or Odin to work, you'll need to use adb to do what I'm about to explain. So, let me know if you need a tutorial on using adb. You can use adb to push items to /sdcard/ while in CWM recovery. Using adb, put the rom that you want on the internal sdcard and put Zen Arcade's Infusion-Z kernel zip there as well. Get the kernel here:
http://forum.xda-developers.com/showthread.php?p=25724526
Then, use the install from zip feature in CWM recovery to flash Zen's kernel to the phone. After the kernel flash, unplug the USB cable and shut the phone off by holding down the power button (it won't boot into anything yet). Then hold the power button and two volume buttons. When the Samsung logo appears, release the power button and keep holding the volume buttons until you are in red recovery. Go to mounts and storage and format system, data, and cache. Then, go back to flash your rom and then reboot. If you're still wanting to throw in the towel, mail it to me and I'll do it for you.
Sent from my SGH-I997 using Tapatalk 2
TheDSMjuggalo said:
to get COM## Try using a different usb plug. That has always been my fix for that issue
Click to expand...
Click to collapse
I've tried that several times. My device is not recognized by Odin.
jscott30 said:
Since you're stuck in recovery and can't get Heimdall or Odin to work, you'll need to use adb to do what I'm about to explain. So, let me know if you need a tutorial on using adb. You can use adb to push items to /sdcard/ while in CWM recovery. Using adb, put the rom that you want on the internal sdcard and put Zen Arcade's Infusion-Z kernel zip there as well. Get the kernel here:
http://forum.xda-developers.com/showthread.php?p=25724526
Then, use the install from zip feature in CWM recovery to flash Zen's kernel to the phone. After the kernel flash, unplug the USB cable and shut the phone off by holding down the power button (it won't boot into anything yet). Then hold the power button and two volume buttons. When the Samsung logo appears, release the power button and keep holding the volume buttons until you are in red recovery. Go to mounts and storage and format system, data, and cache. Then, go back to flash your rom and then reboot. If you're still wanting to throw in the towel, mail it to me and I'll do it for you.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I'll need a tutorial on adb.
GAPY427 said:
Yes, I'll need a tutorial on adb.
Click to expand...
Click to collapse
I've put together a package with all that you'll need for adb. Use these instructions to move the files that I mentioned in my earlier post.
First, let's make sure that we are on the same page with drivers, since you have had trouble with both Heimdall and Odin.
1.) Unplug USB cable.
2.) In the Windows Control Panel, go to "Programs and Features" or "Add/Remove Programs" and uninstall any instances of Samsung Kies and SAMSUNG USB Driver for Mobile Phones.
3.) Download and install THIS version of SAMSUNG USB Driver for Mobile Phones.
4.) After installing the driver, plug in USB cable, and give Windows a moment to setup the driver. When your connection is ready, a USB cable with a check beside it should appear in the Windows system tray.
You can give Odin another try, and it should work for you now with the new driver, or you can move forward with using adb to do what you need.
1.) Download and unzip THIS adb package.
2.) Browse to the folder containing adb.exe. Hold down shift and right click with the mouse; then choose "Open command window here".
3.) Make sure that you are in CWM recovery, and in the Windows command prompt, type
Code:
adb devices
If all is working correctly, your device should appear in the list.
4.) Place any files that you want to move to the device in the same folder as adb.exe.
5.) Then do this for each file: Type the command below, but replace fullfilename with the full name of the file.
Code:
adb push [I]fullfilename[/I] /sdcard/
When the transfer finishes, you should be able to access the items on your internal sd card. From here you can follow the instructions that I gave in the earlier post.
jscott30 said:
I've put together a package with all that you'll need for adb. Use these instructions to move the files that I mentioned in my earlier post.
First, let's make sure that we are on the same page with drivers, since you have had trouble with both Heimdall and Odin.
1.) Unplug USB cable.
2.) In the Windows Control Panel, go to "Programs and Features" or "Add/Remove Programs" and uninstall any instances of Samsung Kies and SAMSUNG USB Driver for Mobile Phones.
3.) Download and install THIS version of SAMSUNG USB Driver for Mobile Phones.
4.) After installing the driver, plug in USB cable, and give Windows a moment to setup the driver. When your connection is ready, a USB cable with a check beside it should appear in the Windows system tray.
You can give Odin another try, and it should work for you now with the new driver, or you can move forward with using adb to do what you need.
1.) Download and unzip THIS adb package.
2.) Browse to the folder containing adb.exe. Hold down shift and right click with the mouse; then choose "Open command window here".
3.) Make sure that you are in CWM recovery, and in the Windows command prompt, type
Code:
adb devices
If all is working correctly, your device should appear in the list.
4.) Place any files that you want to move to the device in the same folder as adb.exe.
5.) Then do this for each file: Type the command below, but replace fullfilename with the full name of the file.
Code:
adb push [I]fullfilename[/I] /sdcard/
When the transfer finishes, you should be able to access the items on your internal sd card. From here you can follow the instructions that I gave in the earlier post.
Click to expand...
Click to collapse
Followed your instructions. Removed SAMSUNG drivers. Installed drivers in your instructions. Odin did not work. Tried the other method and I receive this message in the Cmd window: 'adb' is not recognized as an internal or external command, operable program or batch file.
GAPY427 said:
Followed your instructions. Removed SAMSUNG drivers. Installed drivers in your instructions. Odin did not work. Tried the other method and I receive this message in the Cmd window: 'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You have to be in the exact directory as adb.exe or you'll continue to get that error. Go to the exact folder, hold shift and right click the mouse in that folder window. Choose "Open command window here".
Good luck, and enjoy the holiday.
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
You have to be in the exact directory as adb.exe or you'll continue to get that error. Go to the exact folder, hold shift and right click the mouse in that folder window. Choose "Open command window here".
Good luck, and enjoy the holiday.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Not working. I'm stuck either in blue recovery or a Galaxy S cyanogen(mod) screen.
GAPY427 said:
Not working. I'm stuck either in blue recovery or a Galaxy S cyanogen(mod) screen.
Click to expand...
Click to collapse
Anyone taking time to help you is going to need more to go on than "Not working." I already know that you're in blue recovery. What's the latest on using adb to push a kernel with red recovery to your device so we can get you back to Gingerbread?
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
Anyone taking time to help you is going to need more to go on than "Not working." I already know that you're in blue recovery. What's the latest on using adb to push a kernel with red recovery to your device so we can get you back to Gingerbread?
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
I tried pushing a kernel through adb but I didn't see it on my sd card. There were also 4 different choices of kernels (Core A, Core B, etc.). I tried to push A & B but saw neither of them on recovery.
GAPY427 said:
I tried pushing a kernel through adb but I didn't see it on my sd card. There were also 4 different choices of kernels (Core A, Core B, etc.). I tried to push A & B but saw neither of them on recovery.
Click to expand...
Click to collapse
Did you see the transfer in progress in the command line? If so, and if the transfer finished, it's on there. I wonder if you're looking on your external sd card instead of the internal.
Sent from my SGH-I997 using Tapatalk 2
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
Alright, in blue recovery, go to "install zip from sdcard".
Then, go to "choose zip from sdcard". Do you see the items that you pushed with adb listed there? Don't choose "choose zip from internal sdcard". Despite what that sounds like, it's your external sdcard.
So basically I found out just today we have Cyanogenmod 10.2 >.<
I downloaded the Joilaroi version, flashed it in TWRP 2.6xx and then suddenly "E: Error in updating binary script" did a bit of googling and found out that it's a common problem with TWRP > 2.3.3.0
So I was about to downgrade it to 2.3.3.0 or temp boot into CWM. Connected my phone to my laptop and went to bootloader, then did Adb devices....the list was empty.
Reinstalled HTC drivers, used different USB port...nothing.
TL;DR : Phone doesn't get recognized in Bootloader mode, Can't flash ROM, Can't replace recovery. Help!
AIndoria said:
So basically I found out just today we have Cyanogenmod 10.2 >.<
I downloaded the Joilaroi version, flashed it in TWRP 2.6xx and then suddenly "E: Error in updating binary script" did a bit of googling and found out that it's a common problem with TWRP > 2.3.3.0
So I was about to downgrade it to 2.3.3.0 or temp boot into CWM. Connected my phone to my laptop and went to bootloader, then did Adb devices....the list was empty.
Reinstalled HTC drivers, used different USB port...nothing.
TL;DR : Phone doesn't get recognized in Bootloader mode, Can't flash ROM, Can't replace recovery. Help!
Click to expand...
Click to collapse
Why don't you flash with terminal emulator?
Just put recovery.img in the root of your sdcard
Open terminal type
su
cd sdcard
flash_image recovery recovery.img
That's it
Sent from my gt-1900 using xda premium
Taha Haq said:
Why don't you flash with terminal emulator?
Just put recovery.img in the root of your sdcard
Open terminal type
su
cd sdcard
flash_image recovery recovery.img
That's it
Sent from my gt-1900 using xda premium
Click to expand...
Click to collapse
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
AIndoria said:
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
Click to expand...
Click to collapse
install htc drivers and make dure you cleared the all registry and files from your previous installation and connect your device
open cmd and go to the folder where you placed adb and type command
adb kill-server =>it will close all adb processes running at that time
adb start-server => it will start new adb process
adb devices=> to reconize your device
if it shows your device then through fastboot command flash the recovery
but make sure you have all neccessary binary files in that folder for adb and fastboot
hit thanks if helped
AIndoria said:
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
Click to expand...
Click to collapse
You can try installing the newer Drivers.
Else your usb port may be broken. that is also a possiblity
Hi Guys, I just want to ask if there will be a possible solution on how I will be able to use my phone again. I accidentally deleted the OS and the backup of my OS. When I tried to connect my phone to a pc, the pc wont read my phone. Any possible solution on how will I connect it or any solutions for my problem. I also dont have the custom rom zip on my sdcard anymore.
dxlevel81 said:
Hi Guys, I just want to ask if there will be a possible solution on how I will be able to use my phone again. I accidentally deleted the OS and the backup of my OS. When I tried to connect my phone to a pc, the pc wont read my phone. Any possible solution on how will I connect it or any solutions for my problem. I also dont have the custom rom zip on my sdcard anymore.
Click to expand...
Click to collapse
Can you boot into fastboot or recovery?
Mr.Ak said:
Can you boot into fastboot or recovery?
Click to expand...
Click to collapse
yes I can boot into TWRP, but can't connect to pc.
dxlevel81 said:
yes I can boot into TWRP, but can't connect to pc.
Click to expand...
Click to collapse
Ahh..
Just boot into Twrp,connect your device to Pc and transfer any ROM and flash it.Gee,twrp supports mtp,which means you can transfer stuff.Alternatively,if mtp is not working for any reason,you can use usb otg as well.
Mr.Ak said:
Ahh..
Just boot into Twrp,connect your device to Pc and transfer any ROM and flash it.Gee,twrp supports mtp,which means you can transfer stuff.Alternatively,if mtp is not working for any reason,you can use usb otg as well.
Click to expand...
Click to collapse
The pc wont read my phone anymore, I installed adb drivers already. But I'll try to use an otg usb.
dxlevel81 said:
The pc wont read my phone anymore, I installed adb drivers already. But I'll try to use an otg usb.
Click to expand...
Click to collapse
I forgot to mention you can use adb sideload as well.
Since you've adb drivers installed,boot into twrp,go to advanced and enable adb sideload,connect to PC.Copy the ROM zip in your adb folder(where adb files are situated),press shift and simultaneously hit right button on your mouse,select open cmd here.Now write command "adb devices"(obviously without quotes), if all goes well,you'll see your device Id there,proceed and write command "adb sideload ROM name.zip" (where ROM name= exact name of file you're trying to flash).The flashing progress should start now.
Mr.Ak said:
I forgot to mention you can use adb sideload as well.
Since you've adb drivers installed,boot into twrp,go to advanced and enable adb sideload,connect to PC.Copy the ROM zip in your adb folder(where adb files are situated),press shift and simultaneously hit right button on your mouse,select open cmd here.Now write command "adb devices"(obviously without quotes), if all goes well,you'll see your device Id there,proceed and write command "adb sideload ROM name.zip" (where ROM name= exact name of file you're trying to flash).The flashing progress should start now.
Click to expand...
Click to collapse
Do you have links on working adb drivers? That is my problem now. My pc is unable to read my oneplus
dxlevel81 said:
Do you have links on working adb drivers? That is my problem now. My pc is unable to read my oneplus
Click to expand...
Click to collapse
Device doesn't get detected even after enabling adb sideload in Twrp? What does it shows in Device Manager?
https://forum.xda-developers.com/showthread.php?t=2588979
Mr.Ak said:
Device doesn't get detected even after enabling adb sideload in Twrp? What does it shows in Device Manager?
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
It does'nt show in the device manager.