Hello,
This is a dead easy fix to get tethering working completely with android-wifi-tether (http://code.google.com/p/android-wifi-tether/):
UPDATE
New development version has support for this rolled in, instructions are no longer necessary:
http://code.google.com/p/android-wi...name=wireless_tether_2_0_2-pre14.apk&can=2&q=
Steps:
1. Open adb shell (start cmd.exe, run "adb shell")
2. Issue the following commands:
- "mkdir /sdcard/android.tether"
- "cat /etc/firmware/fw_bcm4329_ap.bin > /sdcard/android.tether/fw_bcm4329.bin"
3. Download and install the android-wifi-tether application, start tethering.
Your log from android-wifi-tether should look like the attached image.
Happy configuration free tethering!
NOTE: This works because of the two separate firmwares that HTC has included in /etc/firmware. One is specific for AP-mode and must be more open to this kind of stuff. The original bug stemmed from the usual firmware dropping ARP requests pretty consistently, possibly as a powersaving measure.
The second firmware is loaded using the firmware_path option when loading the bcm4329.ko kernel module.
anyone else confirm this working please.
I confirm this working...
You will need to have root to run the app of course but 2 or 3 people have confirmed it on bug 362 already on the google project.
Not working for me
AWESOME!!!
actually i ever use wifi tether but this is pretty cool because it actually worked. i know on the heroC we had issues with wifi tether all of a sudden not wrking after 2.1. nice to see that its been fixed. good work spreading the word
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
would be cool if someone can confirm 4g is able to be tethered.
fdot said:
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
Click to expand...
Click to collapse
same here. any ideas?
toastcfh said:
would be cool if someone can confirm 4g is able to be tethered.
Click to expand...
Click to collapse
Not confirming but based on what I read harry_m stated the wifi tether app uses the current connection, so in theory if you switch between 3g and 4g the app will switch accordingly.
i can confirm
I originally flashed with toast's rom. Used the recovery .bat to install Flipz's stock root rom.
I then flashed toast's radio rom.
wifi tether did NOT work.
I then performed the above instructions, and viola, it works fine. (i am posting via wifi tether)
I want to thank everyone who is hard at work on these projects, you guys are awesome.
fdot said:
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
Click to expand...
Click to collapse
Check that the log screen looks exactly like mine does. Did you get any errors when you issued the adb commands?
Look on your sdcard for the android.tether folder and see if fw_bcm4329.bin file exists there.
toastcfh said:
would be cool if someone can confirm 4g is able to be tethered.
Click to expand...
Click to collapse
dcmtnbkr said:
same here. any ideas?
Click to expand...
Click to collapse
It should work according to one of the comments given about the issue. http://code.google.com/p/android-wifi-tether/issues/detail?id=362#c36
Because I am weary of rooting my phone not being able to return it to stock, I am gonna try it with the unrevoked root first.
goodfellaslxa said:
I originally flashed with toast's rom. Used the recovery .bat to install Flipz's stock root rom.
I then flashed toast's radio rom.
wifi tether did NOT work.
I then performed the above instructions, and viola, it works fine. (i am posting via wifi tether)
I want to thank everyone who is hard at work on these projects, you guys are awesome.
Click to expand...
Click to collapse
i followed this same exactly.
andrew500 said:
Check that the log screen looks exactly like mine does. Did you get any errors when you issued the adb commands?
Look on your sdcard for the android.tether folder and see if fw_bcm4329.bin file exists there.
Click to expand...
Click to collapse
no errors in adb.
and the .bin file is sitting in the directory.
and the log looks like yours.
running toasts ROM
can't get this to work
followed instructions, and when i click on the tether button it instantly says: unable to start tethering, please try again!
log screen is completely blank
any ideas?
fdot said:
i followed this same exactly.
no errors in adb.
and the .bin file is sitting in the directory.
Click to expand...
Click to collapse
I meant the screen in android-wifi-tether, does it look like the screen cap I included? It should have a debug line about the loaded firmware on the first item.
- Didn't see the edit you made with that screen:
Have you done the OTA update? Could be the SD card bug possibly. The log screen shows it didn't load the external firmware.
"Unable to start teterhing try again"
I skimmed this thread, I am using toast's rom.
I have just applied the Unrevoked root. I cannot access the sdcard via adb shell. Any ideas?
When i send command
"cat /etc/firmware/fw_bcm4329_ap.bin > /sdcard/android.tether/fw_bcm4329.bin"
it gives me error msg
"cannot creat /sdcard/android.tether/fw_bcm4329.bin: directory nonexistent"
i followed this same exactly.
no errors in adb.
and the .bin file is sitting in the directory.
Click to expand...
Click to collapse
I meant the screen in android-wifi-tether, does it look like the screen cap I included? It should have a debug line about the loaded firmware on the first item.
- Didn't see the edit you made with that screen:
Have you done the OTA update? Could be the SD card bug possibly. The log screen shows it didn't load the external firmware.
Click to expand...
Click to collapse
I have not done the ota.
-------------------------------------
Sent via the XDA Tapatalk App
Related
Hello all!
I just updated now to rc33 and I knew my themes wouldn't work but I am ok with that. I do use phone as modem pretty frequently but now when I try to setup tether 1.6 it don't work. I am wondering if anyone has been able to get it working yet.
Stuck at the part where I type xf /sdcard/tether-1.6.tar
term says xf not found. Any ideas? Thanks
Oh wow, I totally forgot about tethering, Ill give it a try, I am running 1.3JF kernel running rc33 firmware (thanks to quietlurker). Ill tell you how it goes.
I just set it up and it works for me. Did it to show up a cocky iphone friend and let him connect his iphone wifi to me hehe.
Stuck at the part where I type xf /sdcard/tether-1.6.tar
Click to expand...
Click to collapse
Not sure if its a typo but you forgot the tar it should be
tar xf /sdcard/tether-1.6.tar
Hope that helps.
M9x3mos said:
Hello all!
I just updated now to rc33 and I knew my themes wouldn't work but I am ok with that. I do use phone as modem pretty frequently but now when I try to setup tether 1.6 it don't work. I am wondering if anyone has been able to get it working yet.
Stuck at the part where I type xf /sdcard/tether-1.6.tar
term says xf not found. Any ideas? Thanks
Click to expand...
Click to collapse
are you typing "xf" or "tar xf"?
You only need to tar once.
From then on, just make sure you 'su' and then 'tether start'.
But yes, worked fine for me. Once I turned my wifi back off. doh!
Anyone seen this?
http://forum.xda-developers.com/showthread.php?t=480067
Worked fine for me
Worked here without any problem.
I wiped my phone before RC33, and I did have problems getting it to work. The solution was very simple--the tar command was extracting to the SD card rather than root, so I just did:
tar -xf /sdcard/tether-1.6.tar -C /
This put it in root where it belonged. Then I removed the folder on my SD card.
wow, that tetherWifi app is great. 40 seconds after seeing the link i was tethered up and getting 350kbps speeds to my laptop. this alone makes the rooting essential.
thanks the first thing worked. I went back and tried cupcake but am going back to rc33 might take a little while to reroot and everything. will stay with engineering bootloader though.
esnapz said:
Not sure if its a typo but you forgot the tar it should be
tar xf /sdcard/tether-1.6.tar
Hope that helps.
Click to expand...
Click to collapse
I wiped my phone also for rc33 and when i type everything it works in terminal BUT my macbook isnt detecting the G1 like it used too..
You only need to issue the above command only once to get the file setup and in the phone. After that you will need to type:
su (to get super user press enter)
tether start (this command will actually start the program)
tether stop (when you are done to stop the service and not completly kill your battery)
so again to try at first just type in command as follows:
$su
#tether start
#
if done correctly and would that is what you should see. If that does not fix try typing this into your phone and download the application for it. Haven't tried it myself but have heard it works.
www.tauruspc.net/tetherWifi.apk
Well I know I'm not the only one who got a bad WiMax MAC address after trying to update my WiMax radio image. I should learn to not try and fix things if they aren't broken
If you've gotten the dreaded "00:16:08:00:24:05" MAC address like I did, this guide will help you fix it. You'll need fastboot set up, a NAND unlocked phone with Toast's part 2 method, your correct MAC address for WiMax, and the files below.
FILES:
New radio
New WiMax
You MUST download & flash these again even if you already have. I don't care if you think you already have the right ones, download these. If you don't, don't ask me for help if you use the wrong ones.
STEP 1: Fix MAC
First, get your right MAC address. It can be found under the battery by the WiMax tag, or on your box under the WiMax barcode. It should be 12 digits long, with no colons in it. If it were supposed to be "00:16:08:00:24:05" it would look like 001608002405 on the box. Write that address down with a colon between every two characters to get it in the right format.
Next, boot your phone into fastboot mode. If you don't know how to do this, hold down volume and press power to boot into the bootloader. After it brings up the menu where "FASTBOOT" is highlighted, press power. It should say "FASTBOOT USB" in red where it previously said "HBOOT" in green.
On your PC, open a shell. First off, lets see if you have a bad MAC, run
Code:
fastboot oem wimaxrmac
It should return something like
Code:
INFOcmd_wimaxrmac
INFODev MAC = *Your MAC address will be here*
OKAY
If it doesn't match the code you wrote down, then you have a bad MAC. If it does match the code you wrote, then skip to step 2.
To fix it, you need to run:
Code:
fastboot oem wimaxwmac *Address you wrote down here*
Like if you wanted it to be "00:16:08:00:24:05" then you would run:
Code:
fastboot oem wimaxwmac 00:16:08:00:24:05
It should return something like:
Code:
INFOcmd_wimaxwmac
IFNOWrite OK! MAC = *Address you entered here*
OKAY
Then just run
Code:
fastboot reboot
To reboot back into Android with your correct MAC address.
STEP 2: Flash the images again
Now push those files to your SD card & reboot into recovery.
Once you're in recovery, flash the "evo.2.05.00.06.10.zip" file. Reboot from the menu like it tells you. Once you're in Android, update your Profile & update your PRL.
Now reboot into recovery again, this time flash the "evo.wimax.25641_r01.zip" file. Reboot again from the menu, and guess what. Once again, update your Profile & PRL. Reboot one more time for good measure, and you should have working 4G. I haven't been able to confirm 4G myself, but others have reported it working with my method. My logcat no longer shows any 4G errors and neither does the kernel log, plus all the data now matches how it was before my update, so that leads me to believe it's working.
I wrecked my MAC with the update and fixed it like this, but I haven't had a chance to try out 4G yet since I won't be going into the city where I'll have coverage until Saturday.
Please post here if it works for you or if it isn't clear then just post & I'll try and clear it up.
Regards,
Jesse C.
EDIT: As a few posters had trouble, it came to my attention that you MUST have run Toast's root part 2 image to have access to fastboot oem commands.
EDIT 2: Now full 4G fix.
Thank you so much!
Sent from my PC36100 using XDA App
On it.....!!!!
It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.
Hot damn!!!! It works!!!
Neotelos_com said:
It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.
Click to expand...
Click to collapse
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure
Geniusdog254 said:
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure
Click to expand...
Click to collapse
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).
Well i changes the mac....i dont know if 4G is working on it.....
ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.
( waiting for device )
*nevermind*
Sleep..needed badly
Travyevo said:
ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.
Click to expand...
Click to collapse
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.
asrebel said:
*nevermind*
Sleep..needed badly
Click to expand...
Click to collapse
are you in fastboot?
Neotelos_com said:
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).
Click to expand...
Click to collapse
I saw the same thing. I ended up with the one i posted in the OP but it seems they all start with the 00:16:08 characters.
I don't think its safe to post the after MAC address, sicne it's unique to every device. It won't hurt anything, but I'd rather keep mine private
Neotelos_com said:
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.
Click to expand...
Click to collapse
ADB appeared to install when i connected it. I'll take a look.
Thanks
my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?
Anyone 4G back working using this method?
rocolema said:
my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?
Click to expand...
Click to collapse
Yes. It should work for everyone. Do you have the newest fastboot?
david279 said:
Anyone 4G back working using this method?
Click to expand...
Click to collapse
I thought you said you had it working? Do you not have 4G or did it not fix the 4G errors
It fixed my MAC address. I have no 4G to test to see if thats working.
This is an interesting method.
I have restored my MAC via a different route, but I believe if I were to flash an offical wimax right now, I would lose my MAC again. What I have done requires modification to the wimax.img file.
Does this persist through reboots? If it does, this would likely be the best answer to the problem of the bad mac addresses.
david279 said:
It fixed my MAC address. I have no 4G to test to see if thats working.
Click to expand...
Click to collapse
Ah okay. I'm in the same boat
The Samsung Transform has the same vulnerability as the Epic (joeykrim-root.sh works to get root).
So how would I go about rooting? Would I use the same process as the EPIC 4g?
if you're good with linux, you can follow the directions in this link forum.sdx-developers.com/epic-development/adb-root-exploit-test
(The mount command is slightly different in step 4.)
I'm running a mac. I tried several guides on the sph-m910 rooting for mac osx but it won't let me push any files to the phone with adb.
Sent from my SPH-M920 using XDA App
Have any of you successfully rooted it using this method?
I have successfully rooted my brother's Transform using the same method I used to root my Epic 4G... same files and everything.
aliendude5300 said:
I have successfully rooted my brother's Transform using the same method I used to root my Epic 4G... same files and everything.
Click to expand...
Click to collapse
Here's a link to the zip file containing the exploit that worked: http://www.filedropper.com/ocr
drivers?
What drivers are you guys using? i cant get any drivers to install...
mark920 said:
What drivers are you guys using? i cant get any drivers to install...
Click to expand...
Click to collapse
From what I am told and understand it must be mounted and run in linux. I will find out as soon as my local store gets one in, I'm first in line.
aliendude5300 said:
I have successfully rooted my brother's Transform using the same method I used to root my Epic 4G... same files and everything.
Click to expand...
Click to collapse
Any link to the method you used?
aliendude5300 said:
Here's a link to the zip file containing the exploit that worked:
I've tried 8 times, cannot get it rooted. Suppose I'll wait just like the rest of us
Click to expand...
Click to collapse
berger1980 said:
aliendude5300 said:
Here's a link to the zip file containing the exploit that worked:
I've tried 8 times, cannot get it rooted. Suppose I'll wait just like the rest of us
Click to expand...
Click to collapse
I tried it as well. I couldn't get it to work either.
Click to expand...
Click to collapse
I got it to work. I tried it under my computer with Windows 7. I had to right click the run.bat and click properties, Click compatibility, Run this program in compatibility mode for Windows XP Service Pack 3. Thanks.
cachorropedorro said:
I got it to work. I tried it under my computer with Windows 7. I had to right click the run.bat and click properties, Click compatibility, Run this program in compatibility mode for Windows XP Service Pack 3. Thanks.
Click to expand...
Click to collapse
I don't mean to be a ****, but what app have you installed that requires root access? I have a specific one, roam manager, that will not run. I believe you may have seen visually that it was rooting it, but it does not do squat.
berger1980 said:
I don't mean to be a ****, but what app have you installed that requires root access? I have a specific one, roam manager, that will not run. I believe you may have seen visually that it was rooting it, but it does not do squat.
Click to expand...
Click to collapse
apps2sd, I need a new kernel for wifi tethering which is the main thing that I want
Rooting Help
Can someone give some detailed instructions on rooting the Samsung Transform???
I agree with cachorropedorro, I'm looking to root for wifi teathering also..... Tried a few methods also.... No luck.
Guys, I've never rooted a phone before and this is my first android. I looked a the Joeyconway version of root.... I'm having a hard time following the command prompts??? Any suggestions?
Is there going to be a transform category? Are there other pages about rooting this new phone??
I was able to root my transform using the ocr joey krimm root method, the drivers for the epic finally worked after restarting the phone, one thing i noticed about the transform was that the ratc script takes longer to work and does not always work. I modified the bat file to have a longer wait after running the ratc file, however that doesnt even work all the time, if you manually run the ratc script and then run the bat it should work thats what i had to do. I also updated the su bin and the busybox version from the current version of the one click root because the files in the ocr.zip have an older su bin that doesnt use superuser.apk and the busybox is not compatible with ti backup.
Mark920,
Can you give some more detailed directions for all of us that are newbees? Like I said in a earlier post, I've never rooted a phone so some of the things you were talking about like ratc script confuses me. Any detailed steps would be awsome.
dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..
Simplest way i know.
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
is3od said:
dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..
Click to expand...
Click to collapse
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer File name: SDK ADB.zip File size: 359.93 KB put them all in a folder called rootxoom or something.
prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
His Xoom is 3G there is no OTA update to 3.2 for 3G.
I really would not relock and go back to stock. He's rooted and that's more than half the battle.
is3od, the method I posted is for non-US Xooms as long as they are rooted.
i'll try it
prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
thank you for your help... today i'll try it and will inform you about the result.
Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,
okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
first i will relock my xoon then i'll update it ..
thank you,
prowlex said:
incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer put them all in a folder called rootxoom or something.
Click to expand...
Click to collapse
ok
thanks...
k66473 said:
Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,
Click to expand...
Click to collapse
it should be, because my Q is for 3G Xoom.
is3od said:
it should be, because my Q is for 3G Xoom.
Click to expand...
Click to collapse
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.
thanks a lot
okantomi said:
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.
Click to expand...
Click to collapse
I really appreciate your help .. thanks a lot ..
adb devices returns no devices
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Make sure USB Debugging is checked under Settings/Applications/Development. If it is checked, then there is something wrong with your drivers.
big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Check the thread you started...people have answered there.
okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
I'd like to do the same as OP, update a rooted stock 3.0.1 euro 3G to 3.2 - I've already come across the thread you link to, but there's something I don't get.
pienut (user whose post you linked to) is saying that he went from 3.0.1 to 3.2, but in step 3 he writes:
Step 3 - Install 3.2 EURO rom:
Just copied the Euro 3.2 update from this post to my SD Card and flashed it from recovery.
Just to be sure, I did a full wipe after flashing.
Click to expand...
Click to collapse
Am I missing something, or is the SD card not disabled in 3.0.1? I know it is for me, afaik it only started working with 3.1 and up. I can't wrap my mind around going from 3.0.1 -> 3.2 using the SD card method, and yet it's mentioned in quite a few more threads and posts.
Ideally, I'd like to update to the Xoom ROM 2.1 Hammerhead (http://forum.xda-developers.com/showthread.php?t=1203635), but in those instructions, too, step 2 says
Download the 2.1 rom zip file and place it on your external sdcard
Click to expand...
Click to collapse
How, if I can't access it in the first place? Should I install 3.1 first before I install Hammerhead? If so, do you know about any step-by-step I can follow?
Sorry to jump in on this thread like this... it was the closest I could find related to my problem after hours of searching and reading. Thanks.
Alright, I figured it out on my own... I took a leap of faith and installed the ClockworkMod Recovery 3.2.0.0 (R4c), booted to recovery, and in there it's possible to mount the SD card under mounts and storage > mount usb storage. It will then appear in Windows as an external drive (as usual).
Yay, learned something new today. Now on to the next battle
After a lot of attempts, I found a way to force upgrade to Android 6.0 MM on AT&T LG V10 H900.
Before you start these steps:
•Make sure you have ADB installed on your computer and running. If you don’t, follow this guide to set it up. Or if you don't want the whole Android Studio, try this guide to setup Minimal ADB and Fastboot
•Make sure your phone is stock non rooted. If not here is the link to the stock tot file. And here is the link to the instructions for using tot file.
Instructions:
1. Download the Android 6.0 MM OTA zip file.
2. Unzip the file, and you get a 20N.up file
3. Copy 20N.up file to /Internal storage/SoftwareUpdate/ not external SD card (if folder doesn't exist, just create it)
4. Activate USB Debugging on phone and plug into computer
5. Open CMD window in C:\Users\YOURUSERNAME\AppData\Local\Android\sdk\platform-tools by holding shift and right clicking and selecting open command window here. (Path may be in different location based on your installation of SDK)
6. Type the following command in CMD window:
Code:
adb devices
Check and see if your device appears listed. If not, check on phone and select to trust computer if prompted. Run command again once you added computer to trusted list.
7. Run this command:
Code:
adb shell
This should appear: [email protected]:/ $
8. Run this command in ADB shell:
Code:
am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart
Phone Screen should show OFTA Easy Upgrade screen for a few seconds and then reboot to software update.
Note:
This does not give you root, it simply forces the update to marshmallow.
Edit: This method has now worked for everyone who tested it. If it doesn't work for you, just ask for help and either myself or one of the other fine members of the community can try and see what we can do to help.
Special Thanks To:
@kangi26
@syndicator
@LGMONO
@@autostrada048
@betasp
@shepcontracting
RESERVED
Reserved
Tested works
Thanks for this. After flashing back to stock my phone wouldn't show that I had an update no matter what I tried. This method worked perfectly.
For those who do not want to install the whole android studio to get ADB you can use this to get it.
http://forum.xda-developers.com/showthread.php?p=42407269#post42407269
That is what I used.
silentmage said:
Thanks for this. After flashing back to stock my phone wouldn't show that I had an update no matter what I tried. This method worked perfectly.
For those who do not want to install the whole android studio to get ADB you can use this to get it.
http://forum.xda-developers.com/showthread.php?p=42407269#post42407269
That is what I used.
Click to expand...
Click to collapse
Thanks @silentmage for Minimal ADB and Fastboot link! Added link to OP.
I can't decide if give up root and update. I use root mainly for adblock
So I don't currently have a SIM in my V10, it's in my Nexus 6P, but when I check for the MM update I've been told there is no update. This has happened since the MM update was released. My question is can I use this method to update to MM even if there is no SIM in the phone?
I wouldn't think that having a SIM would be require to update but maybe it uses the SIM to auth to the AT&T servers?
manny18pr said:
I can't decide if give up root and update. I use root mainly for adblock
Click to expand...
Click to collapse
You can technically adblock without root, if that's the only thing holding you back from an update.
http://forum.xda-developers.com/showthread.php?t=2726443
This worked perfectly! Thanks, TheBobMiller. Glad we figured out what I was doing wrong.
rcook55 said:
So I don't currently have a SIM in my V10, it's in my Nexus 6P, but when I check for the MM update I've been told there is no update. This has happened since the MM update was released. My question is can I use this method to update to MM even if there is no SIM in the phone?
I wouldn't think that having a SIM would be require to update but maybe it uses the SIM to auth to the AT&T servers?
Click to expand...
Click to collapse
I'm honestly not sure if this method would work for you or not. I am unaware if any of the testers or anyone who has used this method has done so without a sim card. In theory it should work since it's an AT&T version of the phone just missing the sim card. If you try, let me know the outcome please.
Worked great. Thanks!
takkuso said:
You can technically adblock without root, if that's the only thing holding you back from an update.
http://forum.xda-developers.com/showthread.php?t=2726443
Click to expand...
Click to collapse
Have you tried this?
manny18pr said:
Have you tried this?
Click to expand...
Click to collapse
Yep! Did it today. Working like a dream. Adblock was the main reason for rooting, but I really wanted marshmallow.
Best of both worlds!
takkuso said:
Yep! Did it today. Working like a dream. Adblock was the main reason for rooting, but I really wanted marshmallow.
Best of both worlds!
Click to expand...
Click to collapse
Can you post a screenshot of the apn settings you used?
manny18pr said:
Can you post a screenshot of the apn settings you used?
Click to expand...
Click to collapse
http://imgur.com/a/GO5KX
takkuso said:
http://imgur.com/a/GO5KX
Click to expand...
Click to collapse
When I set the apn settinga and hit save it said that the apn name was invalid
manny18pr said:
When I set the apn settinga and hit save it said that the apn name was invalid
Click to expand...
Click to collapse
Are you naming it the same as the original? I'm not sure, but I'd bet they can't have the same name. Other than that, I'm not sure what the issue would be. Maybe length of name, or invalid characters?
takkuso said:
Are you naming it the same as the original? I'm not sure, but I'd bet they can't have the same name. Other than that, I'm not sure what the issue would be. Maybe length of name, or invalid characters?
Click to expand...
Click to collapse
I'm trying again. I'll let you know
Edit: I managed to change the apn.
I now don't know what to manage in the adblock plus.
Deleted
TheBobMiller said:
I'm honestly not sure if this method would work for you or not. I am unaware if any of the testers or anyone who has used this method has done so without a sim card. In theory it should work since it's an AT&T version of the phone just missing the sim card. If you try, let me know the outcome please.
Click to expand...
Click to collapse
I hate to say this but it was all of 5 seconds to put the SIM back into the phone and then perform the update in the thread which worked fine. Sorry I just wanted to update the phone.