Related
I have to exchange my EVO to Radio Shack and I just can't find a way to leave the phone back at stock settings!
I am currently rooted with Toast's method and running the Baked Snack 9.6 ROM. I have tried running the RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe file but it keeps saying that it cannot connect to the phone, even though I have tried it both as USB Charging only and Hard Drive only.
PLEASE, anyone can help me? I have SEARCHED the forums but haven't been able to find a way to do it properly.
You might have a better chance asking this in Q&A section, or else you are going to get lit up by the cops here.
Honda hit me up on Twitter
Sent from my PC36100 using Tapatalk
vboyz103 said:
You might have a better chance asking this in Q&A section, or else you are going to get lit up by the cops here.
Click to expand...
Click to collapse
LOL Ok
jiqqaman said:
Honda hit me up on Twitter
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Done!
I had the same issue and this is how I did it:
I turned off the phone. Turned it back on holding the volume down key and power key. Selected FASTBOOT, then I opened RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe and it worked perfect.
Just remember that your phone will no longer be rooted (you won't be able to can't access the recovery).
krosemm said:
I had the same issue and this is how I did it:
I turned off the phone. Turned it back on holding the volume down key and power key. Selected FASTBOOT, then I opened RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe and it worked perfect.
Just remember that your phone will no longer be rooted (you won't be able to can't access the recovery).
Click to expand...
Click to collapse
Ok, I got to the FASTBOOT link and selected it. Then it switched to FASTBOOT USB. I ran that exe file on my PC but it still says that it can't connect to the phone. It keeps saying ERROR [170]: USB CONNECTION ERROR
Get the update.zip from the RUU
I believe you can also open your temporary directory.
Start, run, %tmp%
Do a search for update.zip and copy it to your sd card and boot into recovery.
If you can't find the update.zip it MIGHT be named something else, so try searching for *.zip, or delete all your temporary files, open the RUU, and then search for *.zip.
HondaCop said:
Ok, I got to the FASTBOOT link and selected it. Then it switched to FASTBOOT USB. I ran that exe file on my PC but it still says that it can't connect to the phone. It keeps saying ERROR [170]: USB CONNECTION ERROR
Click to expand...
Click to collapse
Do you have HTC Sync running? I had it running and my phone was synced when I ran the .exe file.
HondaCop said:
Ok, I got to the FASTBOOT link and selected it. Then it switched to FASTBOOT USB. I ran that exe file on my PC but it still says that it can't connect to the phone. It keeps saying ERROR [170]: USB CONNECTION ERROR
Click to expand...
Click to collapse
I did it without the fast boot, just conect the usb cable, run the RUU and that's it, anyways, i,m uploading the update.zip so you will be able to go to stock flashing from SD
http://depositfiles.com/files/2dp2m33kp
devin.slick said:
I believe you can also open your temporary directory.
Start, run, %tmp%
Do a search for update.zip and copy it to your sd card and boot into recovery.
If you can't find the update.zip it MIGHT be named something else, so try searching for *.zip, or delete all your temporary files, open the RUU, and then search for *.zip.
Click to expand...
Click to collapse
THIS WORKED! The file was actually named rom.zip, so I renamed it to PC36ENG.zip and placed it on my sdcard. THANKS!
mikevillarroel said:
I did it without the fast boot, just conect the usb cable, run the RUU and that's it, anyways, i,m uploading the update.zip so you will be able to go to stock flashing from SD
http://depositfiles.com/files/2dp2m33kp
Click to expand...
Click to collapse
I got it done by kevin.slick's tip. Thanks for your tip aswell, my friend.
HondaCop said:
I got it done by kevin.slick's tip. Thanks for your tip aswell, my friend.
Click to expand...
Click to collapse
Trankilo mi pana!
mikevillarroel said:
Trankilo mi pana!
Click to expand...
Click to collapse
is the zip you uploaded the same thing that they used to do it?
cant get mine to work either
Video: http://www.youtube.com/watch?v=gvUE7lP5WME&sns=em
Okay everyone! Here is a tutorial on how to get Aircrack tools working with your Android TF300T! This gets your Alpha Card working with all the drivers in android so you can use it in Backtrack!
CREDITS: I do not take credit for the drivers I simply put all the information together.
Requirements :
Rooted Device
4 GB Free Space
USB Port or for a Phone an Adapter that can provide power like a HUB
An Alpha awus036h wifi adapter
Android 4.0 or higher that supports USB Host Mode
A brain!! :yeye:
Required Downloads:
Backtrack 5 installer APP - IN Files.zip
RootFileExplorer - IN Files.zip
Required Drivers
Terminal App - IN Files.zip
Android VNC - IN Fiiles.zip
Modules App - IN Files.zip
Required Files.zip - https://www.asuswebstorage.com/navigate/share/GY4I6766V4
First install all apps.
Follow the guide in Backtrack 5 installer APP to set up your BT5 install.
Next boot up backtrack and compile and install Aircrack!
In a backtrack terminal issue the following commands to install Aircrack:
http://pastebin.com/tPM8Qshp
Once complete stay in the terminal and get wicd manager
apt-get install wicd
Now that is done download the Alpha drivers and extract them to your system
/lib/modules folder.
Drivers: https://www.asuswebstorage.com/navigate/share/GY4JP966V4
Next TURN OFF YOUR WIFI
The drivers conflict with the internal wifi. You need to reboot to gain your normal wifi again!
Open the Modules app and open the system tab and select the 3 drives your extracted and save them!
eeprom_93cx6.ko, mac80211.ko, rtl8187.ko
Make sure to go to the settings in the Modules App and un-check load at boot!
Now connect your Alpha Wifi card and open up your backtrack terminal and type:
/etc/init.d/dbus start; /etc/init.d/wicd start
Then Type
ifconfig wlan0 up
Put your card in monitor mode: airmon-ng start wlan0
Thats it! :thumbsup:
Just start using aircrack or download reaver and your set!
If you want to use reaver just download it in your bt5: http://code.google.com/p/reaver-wps/downloads/list
Here is a good reaver tut: http://www.hackforums.net/showthread.php?tid=2079678
I know this is a fairly basic tutorial but I am a very busy guy these days!! I hope you get this working!
This is absolutely fantastic, will try this later on during the day. Thank You!
Great share!Thanks for your work!
jsantiago.antonio said:
This is absolutely fantastic, will try this later on during the day. Thank You!
Click to expand...
Click to collapse
Thanks! Enjoy, this is a great reason to own a tabet.
Hey i got an error while entering sh backtrack.sh command. It says,
backtrack.sh[6]: cut: not found
this script requires root! Type:su.
I followed the instructions perfectly. any help?
xplained said:
Hey i got an error while entering sh backtrack.sh command. It says,
backtrack.sh[6]: cut: not found
this script requires root! Type:su.
I followed the instructions perfectly. any help?
Click to expand...
Click to collapse
Its really straight forward. Just follow the onscreen instructions as best as possible. Make sure you downloaded the script during the instructions. Also make sure the files are all extracted to a folder on your sdcard named backtrack
xplained said:
Hey i got an error while entering sh backtrack.sh command. It says,
backtrack.sh[6]: cut: not found
this script requires root! Type:su.
I followed the instructions perfectly. any help?
Click to expand...
Click to collapse
I apologize if this is obvious and you have already done this, but, Try Typing: su (Enter) at the start of your terminal session to enter superuser mode.
Okay, gonna try asap.
Thanks. I'm wait more positive results for insert it on the index
Good work.
Guys ive got a question. What does aircrack do anyway?
BryanSo said:
Guys ive got a question. What does aircrack do anyway?
Click to expand...
Click to collapse
It is a command line tool which lets you *cough* *cough* test the security of your own or other people's networks. Basically if aircrack is able to discover the password on your network in a relatively short amount of time (a couple of hours) you or whoever's network it is needs to boost their security.
xplained said:
Hey i got an error while entering sh backtrack.sh command. It says,
backtrack.sh[6]: cut: not found
this script requires root! Type:su.
I followed the instructions perfectly. any help?
Click to expand...
Click to collapse
first make sure you have supersu not the normal su.apk. also usb debugging must be on.
afzalarsalan said:
It is a command line tool which lets you *cough* *cough* test the security of your own or other people's networks. Basically if aircrack is able to discover the password on your network in a relatively short amount of time (a couple of hours) you or whoever's network it is needs to boost their security.
Click to expand...
Click to collapse
Cool Imma try this
Spark1223 said:
first make sure you have supersu not the normal su.apk. also usb debugging must be on.
Click to expand...
Click to collapse
sorry. supersu? what's that? anyway to the others, yes my first terminal command is su.
You need busy box and it won't work without an external wireless card.
Spark1223 said:
You need busy box and it won't work without an external wireless card.
Click to expand...
Click to collapse
That is correct. I will add busybox to the list of requirements. I forgot to add that one.
can you do this with a different wireless card?
Spark1223 said:
can you do this with a different wireless card?
Click to expand...
Click to collapse
2nd this post specifically Verizon us 4g aircard
Sent from my Transformer Prime TF300T using xda premium
im running AKOP ROM and this dont work.
I followed all instructions and I get I/O errors in terminal when its mounting before it using the backtrack install apk.
dfoote626 said:
2nd this post specifically Verizon us 4g aircard
Sent from my Transformer Prime TF300T using xda premium
Click to expand...
Click to collapse
You should be able to use this method to install drivers from other wireless cards... HOWEVER, you need to go to backtrack's website (google it), and check the wiki to make sure your wireless card is capable of "injection"
http://www.backtrack-linux.org/wiki/index.php/Wireless_Drivers
shrumhead said:
You should be able to use this method to install drivers from other wireless cards... HOWEVER, you need to go to backtrack's website (google it), and check the wiki to make sure your wireless card is capable of "injection"
http://www.backtrack-linux.org/wiki/index.php/Wireless_Drivers
Click to expand...
Click to collapse
I'm pretty sure mine is. Has the following chipset, discovered when I use a pc with backtrack: ASUSTek Computer, Inc. RT2573 - using the mac80211 rt2500usb/rt73usb drivers
Its one of the ones listed. Don't I need to compile the .ko modules for ARM? If so, how do I do this and where do I find them?
So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
EDIT: The guide that was followed to root: http://forum.xda-developers.com/showthread.php?t=1531646&highlight=root
phracture said:
So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
Click to expand...
Click to collapse
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
justjackyl said:
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
Click to expand...
Click to collapse
I don't believe either was installed. Is there anyway to fix this problem without those?
phracture said:
I don't believe either was installed. Is there anyway to fix this problem without those?
Click to expand...
Click to collapse
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Ahhh okay I think that makes sense to me, and yes I believe I had debugging turned on so I should be able to fix this I guess fairly simply.
Thanks so much will post to say if I've solved or ran into trouble once i get home.
pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop
phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)
Excuse me for butting in but wouldnt it be easer for him to just do the SD card. A lot less confusing at least fo me..
pio_masaki said:
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)
Click to expand...
Click to collapse
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
Romman0 said:
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop
Click to expand...
Click to collapse
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.
phracture said:
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.
Click to expand...
Click to collapse
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?
phracture said:
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?
Click to expand...
Click to collapse
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.
Romman0 said:
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.
Click to expand...
Click to collapse
Thanks for confirming and giving me that link. Problem is solved. Thanks everyone for helping a noob out.
Hello guys, I need your help with the Gnex.
My friend gave me the phone hoping that I can do something. It stucks on nexus logo while booting. USB debugging is turned off, cwm or twrp is not installed. All I can is to enter Android system recovery with the following options: apply update from adb; apply update from usb drive; wipe data factory reset; wipe cache partition.
I've tried wiping cache partition but is doesn't help. Please advice whether wiping data/factory reset will delete the data from internal SD card - I am afraid to lose the photos.
Please advice what should I do to extract data (photos) in my situation?
Thanks in advance to everyone.
Sync???
were photos synced to google????
tosradde for
Wajeeh4616 said:
were photos synced to google????
Click to expand...
Click to collapse
No, they weren't.
fastboot? try it first..
change ur boot.img /kernel
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
memaro_maro said:
fastboot? try it first..
change ur boot.img /kernel
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you please explain - I'm new in this. I can enter fasrboot mode, the status is FAILBootloader locked. What should I do next?
3n3r said:
Can you please explain - I'm new in this. I can enter fasrboot mode, the status is FAILBootloader locked. What should I do next?
Click to expand...
Click to collapse
?? learn about adb & fastboot..
or use this toolkit
http://forum.xda-developers.com/showthread.php?t=2389107
try use modified boot.img
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
wiping
I don't think that anything can help you except that tool because as you are saying that USB debugging is not enabled
Wajeeh4616 said:
I don't think that anything can help you except that tool because as you are saying that USB debugging is not enabled
Click to expand...
Click to collapse
Made wipe data - android loaded but photos are gone.. sad
3n3r said:
Made wipe data - android loaded but photos are gone.. sad
Click to expand...
Click to collapse
before using device too much, quick go to galaxy nexus general section here, and find thread "internal data recovery, yes we can"
you might be able to recover deleted photos.
the way it works when you delete things, is it just tells os that the space isnt being used, so the actual data might still be there and some may still be recoverable.
it is quite a process though. good luck
3n3r said:
Made wipe data - android loaded but photos are gone.. sad
Click to expand...
Click to collapse
You should install a recovery fast as it will help you in future
ashclepdia said:
find thread "internal data recovery, yes we can"
you might be able to recover deleted photos.
Click to expand...
Click to collapse
Thanks a lot for your suggestion. I'm trying to recover. By the way, do you know what does the phrase from the recover guide "ADB (make sure adb.exe is in your path)" mean? Which path?
3n3r said:
Thanks a lot for your suggestion. I'm trying to recover. By the way, do you know what does the phrase from the recover guide "ADB (make sure adb.exe is in your path)" mean? Which path?
Click to expand...
Click to collapse
The directory from which you are using adb command
As an example if I am using cmd and typing this command then it should be like
E:/>adb fastboot *********
Then my adb file must be in E drive
Wajeeh4616 said:
The directory from which you are using adb command
As an example if I am using cmd and typing this command then it should be like
E:/>adb fastboot *********
Then my adb file must be in E drive
Click to expand...
Click to collapse
Thank you for your help. I've followed to step 6, but unfortunalely, RAW file is 0 b after creation. I've tried different numbers in this name mmcblk0p12.raw - but with no effect.. Tried to reinstall cygwin, used NetCat file insted of NC - all the same.
Maybe anyone faced this problem with 0 b size of the RAW file? Maybe it's because I have less than 15 Gb of free space on my disk C?
Would be grateful for your advices.
3n3r said:
Thank you for your help. I've followed to step 6, but unfortunalely, RAW file is 0 b after creation. I've tried different numbers in this name mmcblk0p12.raw - but with no effect.. Tried to reinstall cygwin, used NetCat file insted of NC - all the same.
Maybe anyone faced this problem with 0 b size of the RAW file? Maybe it's because I have less than 15 Gb of free space on my disk C?
Would be grateful for your advices.
Click to expand...
Click to collapse
Cant answer your question but can give you an advice....
Leave all this and dont play with your mobile they were only pictures so forget them or else after sometime you will be following a guide to unbrick your phone.
3n3r said:
Thanks a lot for your suggestion. I'm trying to recover. By the way, do you know what does the phrase from the recover guide "ADB (make sure adb.exe is in your path)" mean? Which path?
Click to expand...
Click to collapse
I'd like to try explaining this a little better. Basically when using a program from the command prompt in any OS the OS needs to know where the program is (this is not just for command prompt, but I digress). There are a few ways of telling the OS where the program you want to use is located.
For example, lets say you have ADB in the folder "android_stuff" on your E drive.
Option 1: Change Directory to the folder, IE: "cd android_stuff"
Option 2: Provide the "full path name" of the program, "e:\android_stuff\adb"
Option 3: Add the folder location to the system "path"
Options 1 and 2 are fairly easy and straightforward, whereas Option 3 can be done in a few ways.
My suggestion is to go with Option 1, its the easiest and all you would have to do is put all of the files you will be using into a single folder.
This is a discussion lifted from [Kernel] TRIM: Speeding up the Galaxy S2 Epic 4G Touch d710, as it is not really relevant in that thread.
Dudebowski said:
heimdall shell scripts for backup and repartition worked as expected. Thank you once again, Lanchon, very straightforward.
CWM backup to removable SD, backup internal storage contents to removable sd, remove the removable SD, adb reboot recovery, run backup script, run repartition script, reboot recovery, format every partition, power down, insert sdcard again, restore CWM backup, run lanchon's recovery trim zip.
[attached lanchon's trim/FPbug kernel, and recovery trimmer. note you'll have to mount all the partitions you wish to trim before executing the zip]
However great that was... I went of the beaten trail and tried reformatting my internal storage space (sdcard0) as ext4. Didn't know CWM had added that option... anyhow, it seems I have some permissions issue with the internal storage space now, can't write to it at all. What did I do wrong?
/storage/sdcard0 rwx rwx --x root:sdcard_r
Click to expand...
Click to collapse
I've been trying all morning, but I can't get Heimdall to see my phone. It never shows up in zadig.exe as "Samsung ..." instead my phone shows up as "Gadget Serial Control" and "Gadget Serial". I can not replace the driver for "Gadget Serial Control". I replaced it for "Gadget Serial", but Heimdall still could not talk to my phone. I tried all 3 different driver options. none of them worked. So far I've tried it on my 2 workstation both with windows 8.1. I am going to try to find a Windows 7 PC later and give it another go.
Kjricker said:
This is a discussion lifted from [Kernel] TRIM: Speeding up the Galaxy S2 Epic 4G Touch d710, as it is not really relevant in that thread.
I've been trying all morning, but I can't get Heimdall to see my phone. It never shows up in zadig.exe as "Samsung ..." instead my phone shows up as "Gadget Serial Control" and "Gadget Serial". I can not replace the driver for "Gadget Serial Control". I replaced it for "Gadget Serial", but Heimdall still could not talk to my phone. I tried all 3 different driver options. none of them worked. So far I've tried it on my 2 workstation both with windows 8.1. I am going to try to find a Windows 7 PC later and give it another go.
Click to expand...
Click to collapse
just use linux! a live pendrive would be enough
linux mint cinnamon 64
or simply ubuntu
to install heimdall type this:
sudo apt-get install heimdall-flash
Lanchon said:
just use linux! a live pendrive would be enough
linux mint cinnamon 64
or simply ubuntu
to install heimdall type this:
sudo apt-get install heimdall-flash
Click to expand...
Click to collapse
I thought about that as well. Easier to do that then find a Windows 7 PC for me
It'll have to wait until tonight though. I put off work too long today. I'll report back once I give that a go tonight.
A few suggestions for Windoze compatibility:
Latest Samsung ADB drivers + installer (works in W8.1, and without keeze or whatever that sammy bloatware is)
http://www.modaco.com/topic/361286-...ver-for-mobile-phones-15490-drivers-win-87xp/
Google's official Android USB driver (says it's only for nexus devices, but I've found it has worked for sammy gear too.)
https://developer.android.com/sdk/win-usb.html
Before installing those, you might want to remove the drivers for whatever devices listed as: adb interface, serial modem, gadget, samsung mobile devices. Anything that suddenly shows up when you plug the phone into the PC.
Do this from device manager (winkey+r, devmgmt.msc) and click 'View -> Show Hidden Devices' to see hardware that's not currently active / plugged in. Right click on treelist entry, 'uninstall'
when installing the new drivers, make sure the phone is NOT plugged into the PC. Once installed, reboot, then plug your phone back in. Whatever drivers necessary for connectivity should be activated now.
Neither of those drivers worked for me either. My phone always comes up in the device manager as modem or gadget. With either gadget serial driver or modem driver. The Google driver installed, but never got used.
Time to switch to a Linux live and give it a try.
Kjricker said:
Neither of those drivers worked for me either. My phone always comes up in the device manager as modem or gadget. With either gadget serial driver or modem driver. The Google driver installed, but never got used.
Time to switch to a Linux live and give it a try.
Click to expand...
Click to collapse
I don't think it is in the cards for me. In Linux Mint I also did not get it to work properly. I got initialization errors. I got it to download the current pit once. Then I tried to repartition with the new pit and I kept getting initialization errors. It would not work any more, not even download the current pit again. I tried different cables and usb ports. SIGH.
Kjricker said:
I don't think it is in the cards for me. In Linux Mint I also did not get it to work properly. I got initialization errors. I got it to download the current pit once. Then I tried to repartition with the new pit and I kept getting initialization errors. It would not work any more, not even download the current pit again. I tried different cables and usb ports. SIGH.
Click to expand...
Click to collapse
its ok. every time u use heimdall you need to restart the phone in download mode again. --no-reboot does not mean the phone keeps listening to commands. this is samsung after all
Lanchon said:
its ok. every time u use heimdall you need to restart the phone in download mode again. --no-reboot does not mean the phone keeps listening to commands. this is samsung after all
Click to expand...
Click to collapse
You gotta be kidding....Each time a Heimdall command is run, the phone needs to be restarted back into download mode. How crazy. I'll try again tomorrow then. I made an Ubuntu live flash drive now. I thought maybe I'd have better luck with it. Once again, thanks for the help.
Kjricker said:
You gotta be kidding....Each time a Heimdall command is run, the phone needs to be restarted back into download mode. How crazy. I'll try again tomorrow then. I made an Ubuntu live flash drive now. I thought maybe I'd have better luck with it. Once again, thanks for the help.
Click to expand...
Click to collapse
lol
Lanchon said:
lol
Click to expand...
Click to collapse
Success!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I ended up using Mint Linux 32bit installed and ran from a USB flash drive. Ubuntu was awful. I haven't used an Ubuntu live distro of it in a while, and I did not care for it. Neither version of Linux I used had proper drivers for my Nvidia 750TI, but at least with Mint I had a full desktop. With Ubuntu it was like working on and old win95 PC with a resolution of 640x480. YUCK!
Before starting this journey, you should already have your phone running CM11 with a current recovery.
Here are my complete steps.
Get files for install after partitioning
Download CM11 nightly, GAPPS, Lanchon's kernel with TRIM (optional), Lanchon's sensor fix v2 and FL24 modem.
Place the above files on the phone's external SD card. Unmount and eject the card.
Get files for partitioning
Download partition files and scripts provided by Lanchon:
http://forum.xda-developers.com/showpost.php?p=58317191&postcount=83
Unzip the file.
Prep live Linux usb drive
Download Linux Mint Cinnamon 32bit no codecs:
http://www.linuxmint.com/edition.php?id=175
Install Mint Linux onto flash drive using rufus-1.4.12:
https://rufus.akeo.ie/downloads/rufus-1.4.12.exe
Prep repartition files and scripts
Boot PC from usb flash drive into Linux Mint.
Place phone into download mode by turning the phone off. Then press power and volume down. When the warning screen comes on, press volume up to continue into download mode.
Plug phone into PC.
In Linux Mint navigate to the folder where you unzipped the partition files and scripts you downloaded earlier. Copy all the files to the Mint "Download" folder. Select the .sh files and right click them and choose properties. Check the box labeled "Allow executing file as a program." I also set both Group and Others access to "Read and Write". Then select the rest of the files and change their permissions as well. I just changed them all to "Read and Write". I do not know if this step is necessary or not, but it is what I did. Why copy the files to the Mint "Download" folder you ask. Well because I could not change their properties where I had originally saved them. That's why.
Next right click on the above "Download" folder and choose open in terminal. Now you should have a terminal window open at the locations of those files. You can verify it by typing in "ls". You should see a list of the files.
Install Heimdall
In the terminal window install Heimdall, the command is:
Code:
sudo apt-get install heimdall-flash
If you are not sure whether your device is connected, the command:
Code:
heimdall detect
should return Device detected.
Download you current pit
At the terminal prompt type:
Code:
sudo ./download-current-pit.sh
If all goes well you should get 2 new files in the Downloads folder:
downloaded.pit
downloaded.pit.txtIf the downloaded.pit file is 0kb, then something has gone wrong. Don't move forward. Time to figure out what went wrong. If the file is around 4kb, then compare "downloaded.pit.txt" to "d710-stock.pit.txt". If they match, move forward. Otherwise proceed at your own risk.
Repartition Phone
Due to weirdness I don't understand, each time a Heimdall command is done you need to restart the phone in download mode. Since you just downloaded your current pit, you executed a Heimdall command. So turn off the phone. Then restart it in download mode again. No need to unplug the phone from the PC while you do this.
Now , with the phone in download mode again execute the following command in the terminal window:
Code:
sudo ./repartition-now.sh
* This script uses the d710-1GBsys-6GBdata-7.3GBsdcard-8MBpreload.pit file. If you want to use one of the others that were provided, you either do the command manually or edit the .sh file accordingly.
You should see a few lines go by in terminal showing the result and then instructions on what to do next. Following is what I did.
Reinstall CM11
Unplug phone from PC and reboot into recovery. I had a little panic here as it seemed my phone did not want to boot into recovery. I had not unplugged my phone from the PC. Once I unplugged it from the PC I could restart into recovery just fine. I believe the sequence is, turn off the phone, then press power and volume up at the same time.
Once in recovery, follow the instructions from the .sh file listed in the terminal window. Go to "mounts and storage", then format the /system, /cache, /data (as vfat) and /storage/sdcard0. You can try to format /preload, but I always get an error when trying to format that.
Now, insert SD card with the CM11 files you downloaded at the start. Flash the .zips
FL24.zip
cm-11-20150118-NIGHTLY-d710.zip
gapps-kk-20140105-signed.zip
sensor-fix-v2-d710.zip
kernel-Lanchon-TRIM-FPBug-20150113-cm-11-20150111-NIGHTLY-d710.zip (optional)
Reboot the phone and complete the CM11 setup process. If you installed the TRIM kernel listed above, then you may want to run the trim commands. Open the terminal app on your phone and enter the following:
Code:
su -c "fstrim -v /system; fstrim -v /data; fstrim -v /cache; fstrim -v /preload"
Congratulate yourself and then move on with your life.
gald u made it!!!
couple of comments...
you can use bash xxx.sh to run a script that doesnt have execute permissions.
before partitioning, you should compare the downloaded.pit.txt with the stock pit.txt (bundled in zip) and if there's any difference, abort the process!! IMHO anyway.
Lanchon said:
gald u made it!!!
couple of comments...
you can use bash xxx.sh to run a script that doesnt have execute permissions.
before partitioning, you should compare the downloaded.pit.txt with the stock pit.txt (bundled in zip) and if there's any difference, abort the process!! IMHO anyway.
Click to expand...
Click to collapse
Ah okay. I didn't know about bash. So the command then would be "bash xxxx.sh"? So I can remove all the steps about changing the permissions?
I agree about comparing the pit files. I guess I didn't make that clear enough. I'll fix that.
Kjricker said:
Ah okay. I didn't know about bash. So the command then would be "bash xxxx.sh"? So I can remove all the steps about changing the permissions?
I agree about comparing the pit files. I guess I didn't make that clear enough. I'll fix that.
Click to expand...
Click to collapse
sudo bash xxx in this case, but leave it as it is! same thing
Lanchon said:
sudo bash xxx in this case, but leave it as it is! same thing
Click to expand...
Click to collapse
Okay awesome. I added the bit about comparing the 2 files.
Thank you so much for all your help. I laughed, I cried, I learned.
Kjricker said:
Okay awesome. I added the bit about comparing the 2 files.
Thank you so much for all your help. I laughed, I cried, I learned.
Click to expand...
Click to collapse
Thank you thank you, Lanchon and Kjricker! Worked for me! You have my eternal gratitude!
Here are a few observations for any one who is hesitant to try this, especially those who are unfamiliar with Linux:
Linux is the way to go. Follow the instructions. But not every Linux distro works. I have a netbook running a two year-old version of Lubuntu. That didn't work. I flashed the LInux Mint distro in Kjricker's post to a 2gb USB drive and booted into it from the netbook.
From Linux Mint home screen, connect to your network (Ethernet or wireless).
From the Toolbar on the bottom of the screen, select File Manager. Locate on your PC where you copied Lanchon's files, select them in File Manager; and from the right-click menu copy those files to the Downloads folder.
From the Menu, open the Terminal application and install Heimdall (the command is: sudo apt-get install heimdall-flash). (I wasn't sure if Heimdall was already included in Linux Mint so I did it anyway.)
Change to the Downloads directory (the command is cd /home/mint/Downloads).
Now put your phone in Download mode and plug it into the PC.
If you are not sure whether your device is connected, the command heimdall detect should return Device detected.
Ahh yes you must install Heimdall. I'll add that.
Sent from my SM-T700 using Tapatalk
Recently I restored a nandroid backup of Mokee 8-Nov-2014 release. I had made this backup prior to repartitioning. Then I updated the apps and data etc.. After verifying that my phone was running fine, I booted into recovery to do a new nandroid backup.
The backup failed, with a message "couldn't mount /preload". It's been reported in this thread, after partitioning, format of /preload failed.
Still in recovery, I formatted and mounted /preload. Rebooted the system (Mokee, that is) to make sure everything was working. (It was.)
Then I booted into recovery and made a successful nandroid backup.