Unbrick my Infuse! - Samsung Infuse 4G

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.

Related

100$ to whoever can help me solve this (NO JOKE)

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

[SD CARD][HOW TO] Cant Mount SD Card or SD Card Corrupted

For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Preliminary Review - Check to see if you can mount in recovery or bootloader
First, go back to your bootloader screen and click on fastboot (reset your phone and hold the power and vol down button). Once in bootloader check your computer drives to see if the sd card is recognized
Your computer may be able to recognize the drive even if it cant open it. If thats the case, you may be able to format it from your computer (use FAT32 formatting).
Second, If you cannot see your SD Card in your ROM or from the PC, and you are using Clockwork Recovery (CW), try flashing TWRP recovery first. Do this by going through the following steps:
Step #1
Download TWRP recovery from http://teamw.in/project/twrp2/100 Make sure to download the correct version for your device
Step #2
Place the recovery file into a folder with fastboot.exe
Step #3
Reboot your phone and hold down the Vol Down Button and Power Button until your bootloader screen appears, then enter fastboot. Then connect to your computer. I find this method works best by holding down the buttons right away. If your phone is off, press the power button then immediately press and hold the power and vol off buttons again until bootloader screen shows up. Dont let go until the screen shows.
Step #4
Type
Code:
fastboot flash recovery twrp.img
but replace the twrp.img wording with the exact name of your downloaded TWRP recovery
Step #5
Enter TWRP recovery by selecting it from your bootloader screen. Then ensure the device is connected to your computer and select the Mount option and then mount your sd card.
IF you still cant see your SD Card from TWRP recovery or you get an error, proceed to the next steps. Your computer may be able to recognize the drive, even if it cant open it (if your lucky).
If your computer recognizes the drive but cant open it, you can try formatting it from your computer (make sure to format as FAT32)
If you really cant see your SD Card, and your fairly sure its corrupted, and you have no way formatting it from your computer, continue on below:
Basic Solution
Reflashing Stock Recovery to your device using fasboot, then doing a full factory reset. This would be using the method in post http://forum.xda-developers.com/showthread.php?t=1630459
PLEASE NOTE THIS METHOD WILL WIPE THE DATA FROM YOUR DEVICE AS WELL AS FROM YOUR SD CARD
This method works because custom recoveries cannot re format SD Cards on the HTC One S, only wipe data from them. However, the stock recovery does have a proprietary feature that will reformat the internal sd card if it has been corrupted.
Inotherwords:
Step #1
Download the stock recovery from: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
*******Note that this file is a stock recovery for S4 devices, not S3.
Place the file into the same folder as your fastboot.exe
Step #2
On your device, go into bootloader and fastboot mode, connect your computer to the device, and type
Code:
fastboot flash recovery ville_recovery_signed.img
Step #3
Reboot into the bootloader and then choose to "clear storage" from the main screen and afterwards reset to factory defaults.
Step #4
Go back into the bootloader once step #3 is done and enter fastboot, connect your device and reflash your original custom recovery again. Your SD Card should be visible
Advanced Solution - If you do not want to wipe the data from your device
This method does not require reflashing the original recovery and factory reseting the whole phone. However, it still means that the info on your sd card will be lost. It also needs a rooted device.
This method does not require you to access your bootloader or use fastboot. You can do this while having your phone in custom recovery.
DO NOT ATTEMPT UNLESS YOU FEEL COMFORTABLE WITH THE INSTRUCTIONS. THERE ARE ALWAYS RISKS WITH FORMATTING. DO NOT HOLD ME RESPONSIBLE FOR BRICKED DEVICES. YOUR DEVICE IS LIKELY OUTSIDE OF WARRANTY ALREADY SINCE YOU WOULD HAVE UNLOCKED THE BOOTLOADER.
I have taken this solution from HTC One X forums namely from post 17 at http://forum.xda-developers.com/showthread.php?t=1647806&page=2
However, I have also confirmed (SneakyGhost's partition list for HTC One S) that the correct mmcblk0p for the HTC One S sd card is mmcblk0p36.
Step #1: Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. You only need to do this if you dont already have busybox installed on your HTC One S. Sometimes this busybox file can be found under /system/bin or /system/xbin if youve previously installed it. If so, replace the paths in the instructions below for that of your busybox. If you have busy box already installed in /system/bin , then you do not need to type in the paths since the adb shell automatically picks up programs in that folder
Step #2: Go to your command prompt in the folder with adb.exe . Connect your HTC One S to your computer and type
Code:
adb devices
and ensure your computer sees your HTC One S. This command should work even if you are in a custom recovery like TWRP or CW (but for gods sake, if your on CW, the first thing you should do is flash TWRP, but thats just an editorial opinion, lol).
Step #3: Type
Code:
adb push busybox /data/local/tmp
This pushes busybox to a temp folder on your HTC One S. Make sure you are pushing the busybox file and not the zip file. If you already have busy box installed you do not need to do this step. (you can delete it from this folder later if you like)
Step #4: Type
Code:
adb shell
to get into your linux shell. Then type
Code:
su
to get root access. Your command prompt should now be a # and not $.
Step #5: Type
Code:
chmod 755 /data/local/tmp/busybox
to fix permissions for busybox. You may not need to do this if you already have busy box installed with the correct permissions. If these instructions dont work with your version of busy box, try setting the permissions with this code but replace the path with the location of your busybox.
Step #6: Type
Code:
cat /proc/partitions
and just ensure you see mmcblk0p36. This is the sdcard partition for HTC One S
Step #7:Type
Code:
/data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p36
Make sure you type this correctly. You dont want to format the wrong partition accidentally.
That should work. Pls let me know if it doesnt. If it doesnt work with your version of busybox just try using the one in the zip file below. Also remember, dont just push the zip file. Extract the busybox file from the zip and push that to your device instead.
Also, it may help to use adb through a custom recovery instead of being in your ROM (ie if it doesnt work when your phone is booted normally, try doing the steps with recovery loaded).
There are other methods to try too They would be:
Other Solutions
Other Method #1: Relocking your bootloader and using a compatible RUU with your phone. This will fully wipe your device
Other Method #2: If your computer sees your sdcard even if it cant open it when your device is connected, you can try formatting it that way (ie the way you would format any other drive on your computer)
Only use the busybox method if you are comfortable with it and if other methods have failed. You can learn more about the formatting command (ie mkfs.vfat) by googling it.
So if I got this right if I have busybox already I only have to do is step 7.
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Step 4, a quicker way: adb shell su , get you into shell as root right away
AKToronto said:
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Darknites said:
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Click to expand...
Click to collapse
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
AKToronto said:
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
Click to expand...
Click to collapse
No idea but does sounds like a good start lol.
Darknites said:
No idea but does sounds like a good start lol.
Click to expand...
Click to collapse
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
AKToronto said:
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
Click to expand...
Click to collapse
Nice update. Ya I wish they hurry up with sorting it, the other one is a load of crap and this really should replace it.
Updated with a link to another good tutorial about pushing ROMs to the phone
Its like they don't care about stickys any more, come mods its about time this replaced the crappy one.
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
AKToronto said:
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
Click to expand...
Click to collapse
yea I got into the bootloader and then fast boot. ive managed to sort it now, for some reason my pc was the problem, I had to reboot my computer after a command window prompt otherwise I just got the waiting for device screen.
typical really, my laptop and phone both conspiring against me.
eventually managed to flash another recovery which did see my sdcard so all is good now.
thanks for your reply though!
AKToronto said:
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Click to expand...
Click to collapse
Dude, this works flawless!
Thought I had a soft-brick, but your instructions bring back my sd-card!
I choose the "advanced Option", it works fine....
Typing su-command generated an error message, but the other steps still functioned....
I will place link in section "helpfull links" in my signatur
Big THX to you good sir, ...
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
$droyd$ said:
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
Click to expand...
Click to collapse
Some people had reported not being able to see their phone from their PC no matter what they tried... Hence the advanced steps
Dude add S3 stock recovery please.
Darknites said:
Dude add S3 stock recovery please.
Click to expand...
Click to collapse
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
AKToronto said:
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
Click to expand...
Click to collapse
Nope but a RUU will have it.

Pantech Element TWRP Recovery and Stock Rooted Roms

This is TWRP recovery and Stock rooted roms for the ICS firmware on the tablet.
These will only work if you currently have ICS running on your tablet. If you still have honeycomb then do the upgrade first.
Nothing was added or removed from the stock roms besides root and busybox.
Only bug with TWRP is that you can't mount sdcard in recovery. Just use adb push.
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Thanks:
attn1 - gave me some help since I am new to pantech devices
Dees_troy - for TWRP code obviously
Tassadar - for his rotation code for twrp. Without this it wouldn't have been possible
Disclaimer: Flash this ROM at your own risk. I am not responsible for what you do on your device. I left this stock to provide a base for anybody that wants to use it. Mod this rom how you want. Just please remember to give credit where credit is due.
This is a pure stock rooted rom. It has items like busybox, init.d support and so forth. No apps were added or removed. Both Odexed and Deodexed versions below.
Downloads
just in case i need another
Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)
mavblues said:
Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)
Click to expand...
Click to collapse
On the computer. your command prompt should be at wherever you put twrprecovery.img file is. So for example you put twrprecovery.img at the root of c:, your command prompt should read c:/ .....
Sent from my M7 using xda premium
Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA
mavblues said:
Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA
Click to expand...
Click to collapse
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium
jmztaylor said:
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Got it - working great!
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium
dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Did you check "USB debugging" on the tablet?
Also, I had to set USB connection on the tablet to the last choice "PC Data Mode".
Hope it helps.
jmztaylor said:
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4
dagadu said:
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4
Click to expand...
Click to collapse
Anytime when the tablet is not plugged in. This will make the computer automatically install anything needed for the tablet and you won't have issues with fastboot or adb anymore
Sent from my M7 using xda premium
jmztaylor said:
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Click to expand...
Click to collapse
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.
1806 said:
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.
Click to expand...
Click to collapse
Actually it's similar steps; however, yours is more like 1-click root
Anyway, I tried everything all above, but it didn't solve my problem, then I found the solution from other website
I just want to share in case others are stuck in fastboot mode like me:
1. When your tablet screen is on fastboot mode (white), go to device manager on your pc
2. Right click on Android > Update driver
3. Click on Browse driver
4. Choose Let me pick manually from my pc list
5. Choose Android phone and pick the first list there. It should be "Android ADB..."
6. Install and fastboot continued
if you can't find Android ADB from your pc list, then you should unplug device then install PC Suite.
here's the old tuts: youtube com/watch?v=UHRonVzBMsI
Hopefully it helps others and thank you very much for all your help!
Delete!
Finally! and a question
Finally a recovery for the element! Rhanks to the OP. Now I am less afraid to tinker with my tablet.
Question: The most important thing right now that I'd like to do is move the folder /data/data from the internal storage, to the internal SD card. This is stopping me from using Google Magazines and Google music, since their data is being stored there, and it shares space with actual applications. 1GB is not that much space for APPS, Dalvik Cache and APPs' data when you add magazines, and when google starts caching Music and Chrome data there. I currently only have 300MB left before I install Music and magazines. And that is AFTER I've used app2sd on all apps that can be moved. How do I do this?
I have tried simply creating a Link using "ln - s /mnt/sdcard/data /data/data" once I copied/moved the contents of the directory, which sort of works initially, but it will not work after a reboot. It actually stops my tablet from booting. (again, thanks to the OP for the recovery).
right now, I am just doing an "ln" on the specific folder inside the /data/data folder, but it acts weird when I use Titanium Backup to restore data
-> Android noob <-
Installing TWRP went smooth as silk. With twrprecovery.zip on you micro sdcard and Element connected with usb cable and USB debuuging checked 1.Just copy twrprecovery.img into your sdk folder/ platform-tools and also have a copy of cmd.exe from windows in the platform-tools folder. 2. Start cmd.exe and type or copy & paste command reboot bootloader 3. Then on white screen(fastboot) type or paste command fastboot boot twrprecovery.img 4. When you boot into TWRP install twrprecovery.zip.....As you rebbot system TWRP should ask if you want Supersu installed and swipe to install. Once rebooted install supersu from the Play store and open Supersu to update SU file all should be good
Thanks for the info and files. I know I'm a little late on this Tablet but picked it up cheap and with ATT 4G it goes along with my devices. The orginial owner hadn't even installed ICS and she wasn't even aware of an update. She now owns an Apple :laugh::laugh:device LOL
I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?
marcustaz said:
I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?
Click to expand...
Click to collapse
Yes good deal, got mine last month on Craigslist for $70.00 and works really well. The owner hadn't even updated to 4.0 or even knew how. It is a good tablet and have rooted it. I think its development is pretty well dead as not many sold. Only thing bad about it is the Element reads 2nd partition instead of 1st as most android devices do, so harder to use link2sd or folder mount as they both use 2nd partition.
Sent from my PantechP4100 using XDA Premium 4 mobile app

[Q] synergyRom plan B help

Hi i am trying to do this part
Part B (SynergyROM's "Plan B" manual backup):
1. Download the attachment at the bottom of this post. This is an update ZIP you can run right from recovery.
2. Reboot into recovery. On stock this can be done by turning off the phone and then turning it back on while holding UP and HOME.
3. CWM: Use VOL UP and VOL DOWN together with HOME to select "install zip from sdcard" then "choose zip from sdcard". Navigate to the folder you downloaded it to (most likely Download/). Select the zip you just downloaded to "flash".
Click to expand...
Click to collapse
my vzw s3 is stock and this is my first time trying to root and flash roms. so i downloaded the file in step 1 and put that zip file in my micro sd and enter recovery by hold vol up and home button and press the power button once in there i proceed to install file from external device (microsD) i run that file i downloaded in step 1 and i see green texts activity and after 3-4 lines of texts i see " E: Signature verification fail" in red texts and it continue to output 3-4 green texts after that and it auto reboot. i also want to make and go to my external sd to verify if anything wrriten in it and i dont see any new folder created..
anyone can help me? is this a problem or normal?
thanks
tainle said:
Hi i am trying to do this part
my vzw s3 is stock and this is my first time trying to root and flash roms. so i downloaded the file in step 1 and put that zip file in my micro sd and enter recovery by hold vol up and home button and press the power button once in there i proceed to install file from external device (microsD) i run that file i downloaded in step 1 and i see green texts activity and after 3-4 lines of texts i see " E: Signature verification fail" in red texts and it continue to output 3-4 green texts after that and it auto reboot. i also want to make and go to my external sd to verify if anything wrriten in it and i dont see any new folder created..
anyone can help me? is this a problem or normal?
thanks
Click to expand...
Click to collapse
This entire process must be done AFTER you have rooted and unlocked. You'll need CWM or TWRP recovery in order to flash those Synergy zips.
Sent from my SCH-I535 using Tapatalk 4 Beta
SlimSnoopOS said:
This entire process must be done AFTER you have rooted and unlocked. You'll need CWM or TWRP recovery in order to flash those Synergy zips.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
okay thanks for the help i will do that after roooted and unlocked bootloader
Step 1: Download these files to your pc:
Samsung Driver- http://tinyw.in/Fdoz
RootDebugFS- http://goo.im/devs/invisiblek/i535/Root Debug FS.7z
Step 2: Install samsung drivers to the pc and unzip the RootDebugFS tool to desktop.
Step 3: Connect the device with the oem usb cable to pc.
Step 4: On your device, Make sure USB Debugging(settings/developer options/usb debugging) and Install of Unknown Sources(settings/security/unknown source) is checked.(Also, make sure there are no other android devices, emulators, or any tethering programs running!!).
Step 5: From the PC, Open the Root Tool folder you downloaded in step 1 and Double click "RootDebugFS". press 1 then hit enter.
Step 6: Agree to all of the disclaimers by pressing Y after each one pops up.
Click to expand...
Click to collapse
i need help with this part. first i cannot download the samsung drivers in that link, error 404. so i got go on with the steps without the samsung drivers and run the rootdebugfs at step 6 and agree to all dislaimer and it start to run commands on it own and in end command line it said "Failed...." for every lines so i dont know why and the phone did reboot twices and now i am stuck at this screen and not sure what it mean in the command prompt. it say " Testing superuser... /system/bin/sh: /system/xbin/su: not found uid and gid should both be 0. Are they? <y/n>
should the uid and gid be 0? and i get all the failed when running the rootdebug is because i dont have the samsung drivers? or i am doing something wrong? thanks for the assistant
tainle said:
i need help with this part. first i cannot download the samsung drivers in that link, error 404. so i got go on with the steps without the samsung drivers and run the rootdebugfs at step 6 and agree to all dislaimer and it start to run commands on it own and in end command line it said "Failed...." for every lines so i dont know why and the phone did reboot twices and now i am stuck at this screen and not sure what it mean in the command prompt. it say " Testing superuser... /system/bin/sh: /system/xbin/su: not found uid and gid should both be 0. Are they? <y/n>
should the uid and gid be 0? and i get all the failed when running the rootdebug is because i dont have the samsung drivers? or i am doing something wrong? thanks for the assistant
Click to expand...
Click to collapse
Well, you need to use Open1your1eyes0 thread to root/unlock.
As for DebugFSRoot, just read the top of its thread and you'll see where you went astray.
SlimSnoopOS said:
Well, you need to use Open1your1eyes0 thread to root/unlock.
As for DebugFSRoot, just read the top of its thread and you'll see where you went astray.
Click to expand...
Click to collapse
i installed cwm 6.0.2.3 and in the recovery i cannot mount my sd, i believe that any sd 64gb+ class 10 will not work? and i have to use TWRP recovery? if so how do i install twrp recovery? just use odin and flash it and it will override the cwm recovery?
tainle said:
i installed cwm 6.0.2.3 and in the recovery i cannot mount my sd, i believe that any sd 64gb+ class 10 will not work? and i have to use TWRP recovery? if so how do i install twrp recovery? just use odin and flash it and it will override the cwm recovery?
Click to expand...
Click to collapse
Just use Odin. Or reformat the sdcard to Fat32 and lose ability to transfer >4gb files.
Sent from my SCH-I535 using Tapatalk 4 Beta
hey thanks for the help
SlimSnoopOS said:
Just use Odin. Or reformat the sdcard to Fat32 and lose ability to transfer >4gb files.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I think you have become the noob helper. I gave up because it seemed like to many people was not reading and bricking. Never seen so many people bricking devices until the price of this phone went down.
Sent from my GT-P5113 using xda premium
bbqsfire said:
I think you have become the noob helper. I gave up because it seemed like to many people was not reading and bricking. Never seen so many people bricking devices until the price of this phone went down.
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Nah, I'm just a part of the community my friend. It helps to pace yourself. Plus I learned at work, the hard way no doubt, that I don't have to do everything because there's plenty of folks capable of helping.
Sent from my SCH-I535 using Tapatalk 4 Beta

[Q] I've really messed up my phone, can't seem to install stock ROM now

How can I flash a stock ROM considering I cannot boot the phone up normally in order to put the file onto the phone? The Moto G has no external storage so I can't use an SD card.
I get get into the bootloader, and I have managed to install Team Win Recovery Project but don't know what else to do!
Euskadi said:
How can I flash a stock ROM considering I cannot boot the phone up normally in order to put the file onto the phone? The Moto G has no external storage so I can't use an SD card.
I get get into the bootloader, and I have managed to install Team Win Recovery Project but don't know what else to do!
Click to expand...
Click to collapse
Disclaimer : I have not used TWRP recovery on Moto G. So may have errors in my post
You have 2 options.
1. On some versions of TWRP, under advanced you have an option to mount USB. You can the access the phone as a drive from a computer.
2. Use ADB to push file to the phone. Install drivers and ADB works in recovery,
Thanks I actually found out about the adb push thing just after making this thread. I was able to push Beanstalk onto the device and install it through TWRP, however it's just stuck on the Beanstalk bootscreen forever. I tried installing it again and the same thing is happening. This also happened earlier when I tried to install Cyanogenmod
Once when i wanted to flash Stock 4.3 i got also stuck in bootanimation.
To restore Stock i had to execute flashall.bat /eu. The option /eu erases userdata. Once i did this my phone booted without any issues.
So what you can try is to erase userdata via fastboot or cwm
fastboot erase userdata
Click to expand...
Click to collapse
onyinly made
I tried one final Hail Mary before going to be last night, erased all data and installed Cyanogenmod again and I'm pleased to say it worked!
Only downside is I've lost all my apps & data. Now I did back these up using Titanium, and stored them on Google Drive, however the reason I got into this mess in the first place is because I manually flashed the 4.4.2 update, which worked ok, but then when I restored my apps/data with Titanium my soft buttons (back button etc) disappeared!
I guess I'll just play it safe and not try to restore the back up this time.
M8 u couldn't give a walk through guide how u pushed ROM to phone pls
Sent from my HTC Desire C using XDA Premium 4 mobile app
the sarge said:
M8 u couldn't give a walk through guide how u pushed ROM to phone pls
Click to expand...
Click to collapse
Not exactly an expert myself but look for a download of 'Fastboot', it should have a program called adb.exe or abd-windows.exe. Turn on your phone while holding the Volume Down button and it should start into the bootloader screen, plug in the USB and it will say it's connected.
Then you go to the folder (on your PC) that has adb.exe - put your ROM .zip into this folder - then hold shift and right-click somewhere inside the folder (not on a file) and choose "Open command window here".
Then you just type "adb push ROM.zip /sdcard" where ROM.zip is the name of the zip file. note: you might have to type adb-windows instead, depends what .exe you have
Then just wait until it finishes transferring. Will take 30 secs or so for a 200mb ROM.
I'm sure if you google "adb push" you'll get some better instructions, with downloads etc
While reverting to stock it's important to use mfastboot(moto-fastboot) instead of normal fastboot. Download mfastboot.exe and place in adb folder, and replace 'fastboot' commands with 'mfastboot'
Sent from my XT1032 using XDA Premium 4 mobile app
Or try supertool on root junkies download site worked for me to get o t a kit kat
Sent from my Moto G using XDA Premium 4 mobile app

Categories

Resources