Hi,
Recently bought an Xperia Go and as I live in Japan and am on Softbank network the setups/customizations/ROMs are sometimes a pain to find out.
I managed to make it by gathering info from here and there, so I though to share all that in one place to possibly help someone else fighting with same issues.
I'm a long time user of HTC Desire and been going through various custom ROMs.
For Japan Softbank operator environment I have always needed to separately install a special mms.apk.
Once I found out that in Sony case the app is in fact called conversations.apk I began to uncover from several Japanese forums how to untangle Xperia.
I'm not going to list all the unnecessary steps I went through, or repeat the instructions from other posts, otherwise this post would go on forever... But I will state the main parts where I encountered problems or where you might want to pay extra attention.
I was using a fresh installed Win7 PC which I happened to have at hand - to avoid any problems of previously installed programs or drivers, so I first installed JDK and SDK...
1. First I tried the unmodded phone with Softbank access points, but as expected the MMS sending/receiving was not possible. To play around with the messaging applications, I needed to root the phone. For that I needed to first unlock the bootloader and then flash a pre-rooted kernel
1. Go came installed with .162 kernel. I let it OTA updgrade to .184
2. Unlocked bootloader http://unlockbootloader.sonymobile.com/instructions
- Here I had some problems with the driver installation. I found out a solution from Nerre http://forum.xda-developers.com/showthread.php?t=1678219: post #6
-Keep the Device Manager open
-Connect the phone and quickly choose to change driver
-Disconnect the phone again (because it goes into normal mode)
-Choose to install a driver from the computer, choose "All devices" and "have disk".
-Browse to the folder with the .inf
-Now, before clicking Next, connect the phone again and quickly hit Next.
Click to expand...
Click to collapse
-Copy AdbWinUsbApi.dll and AdbWinApi.dll from platform-tools to tools (this was my own finding)
!! Due to user stupidity I had to relock my bootloader once, good instructions here from jozinek http://forum.xda-developers.com/showthread.php?t=1799005 so I ended up installing Flashtool as well. Good tool, that.
- Then finally got it done
Code:
C:\Program Files (x86)\Android\android-sdk\tools>fastboot.exe -i 0x0fce getvar version
version: 0.5
finished. total time: 0.000s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot.exe -i 0x0fce oem unlock 0x[my key]
...
(bootloader) Unlock phone requested
OKAY [ 0.087s]
finished. total time: 0.087s
C:\Program Files (x86)\Android\android-sdk\tools>
3. Next I installed a rooted kernel from driversax http://forum.xda-developers.com/showthread.php?t=1829729 but this one had problems with mounting of the SD card (you can find various comments on the thread), so I had to find an alternative one
4. With this kernel from krachlatte http://forum.xda-developers.com/showthread.php?t=1839865 all was a Go! pun intended
EDIT: There's a recovery for this as well now, which is fantastic!
Code:
C:\Program Files\Android\android-sdk\platform-tools>fastboot.exe -i 0x0fce flash boot Kernel6.0.B.184ro.secure.elf
sending 'boot' (4708 KB)...
(bootloader) USB download speed was 20784kB/s
OKAY [ 0.245s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 0.606s]
finished. total time: 0.855s
C:\Program Files\Android\android-sdk\platform-tools>
5. Installed Superuser, BusyBox and Root Explorer from Play store
6. Minato128 had been playing around with the messaging on Xperia S http://d.hatena.ne.jp/minato128/20120417/1334659736 so I thought the process must be similar for Go, as well
adb shell
su
mount system
cd system/app
# mv Conversations.apk Conversations.apk.bak
mv Conversations.apk Conversations.apk.bak
# ls Con*
ls Con*
ContactsImport.apk
Conversations.apk.bak
# ^C
C:\android-sdk-windows\platform-tools>adb install Mms.apk
2830 KB/s (898553 bytes in 0.310s)
pkg: /data/local/tmp/Mms.apk
Success
Click to expand...
Click to collapse
They were using the mms.apk modded by Jake http://blog.yo-ki.com/post/Android-22-Froyo-Softbank-MMS.aspx but that did not work for me. Actually it never had before with Desire, either.7. I extracted mms.apk that I have successfully used with my Desire ROMs from Takuo http://takuo.jp/junk/Mms.apk/OLD/ - update-mms-20100908.01-sense-froyo-signed.zip and transferred it to the phone
8. Using Root Explorer I renamed system/app/conversations.apk to conversations.apk.bak and transferred Mr Takuo's mms.apk to system/app
9. Installed mms.apk using the stock app Astro, which has a nice "Install" feature
FYI the APN settings for Softbank, I'm using a black SIM from iPhone (which is why I have to modify mms.apk, to change the user agent to, for example, iPhone. Softbank has only locked phones and additionally no Sonys on their lineup so we are forced to "hack" a bit )
Code:
Name: Smile MMS
APN: smile.world
Port: 0
Username: dna1trop
Password: so2t3k3m2a
MMSC: http://mms/
MMS proxy: smilemms.softbank.ne.jp
MMS port: 8080
MCC: 440
MNC: 20
Authentication type: PAP or CHAP
APN Type: mms
Name: Smile Internet
APN: smile.world
Username: dna1trop
Password: so2t3k3m2a
MCC: 440
MNC: 20
Authentication type: PAP or CHAP
I create separate APs for MMS and Internet, most probably that's not necessary, though
Everything works now.
Thanks "Go" to
Nerre
jozinek
driversax
krachlatte
Jake san at http://blog.yo-ki.com/
Minato128 san at http://d.hatena.ne.jp/minato128/
Kitame Takuo san at http://blog.takuo.jp/
And to Sony for being a good sport and supporting open source development!
I merely collected the info on one post.
As there is no forum section for Xperia Go I posted this here, many Go related posts seem to have ended up in this section.
Admins be so kind as to relocate this post to more appropriate location, if this is not the right place.
BR,
-Petteri
...apparently no need to use modified kernel, root, messaging app, anything.
Just download Go SMS from the Play Store, hit the settings right and message away.
BR,
-P
MrFastXX said:
Hi,
Recently bought an Xperia Go and as I live in Japan and am on Softbank network the setups/customizations/ROMs are sometimes a pain to find out.
I managed to make it by gathering info from here and there, so I though to share all that in one place to possibly help someone else fighting with same issues.
I'm a long time user of HTC Desire and been going through various custom ROMs.
For Japan Softbank operator environment I have always needed to separately install a special mms.apk.
Once I found out that in Sony case the app is in fact called conversations.apk I began to uncover from several Japanese forums how to untangle Xperia.
I'm not going to list all the unnecessary steps I went through, or repeat the instructions from other posts, otherwise this post would go on forever... But I will state the main parts where I encountered problems or where you might want to pay extra attention.
I was using a fresh installed Win7 PC which I happened to have at hand - to avoid any problems of previously installed programs or drivers, so I first installed JDK and SDK...
1. First I tried the unmodded phone with Softbank access points, but as expected the MMS sending/receiving was not possible. To play around with the messaging applications, I needed to root the phone. For that I needed to first unlock the bootloader and then flash a pre-rooted kernel
1. Go came installed with .162 kernel. I let it OTA updgrade to .184
2. Unlocked bootloader http://unlockbootloader.sonymobile.com/instructions
- Here I had some problems with the driver installation. I found out a solution from Nerre http://forum.xda-developers.com/showthread.php?t=1678219: post #6
-Copy AdbWinUsbApi.dll and AdbWinApi.dll from platform-tools to tools (this was my own finding)
!! Due to user stupidity I had to relock my bootloader once, good instructions here from jozinek http://forum.xda-developers.com/showthread.php?t=1799005 so I ended up installing Flashtool as well. Good tool, that.
- Then finally got it done
Code:
C:\Program Files (x86)\Android\android-sdk\tools>fastboot.exe -i 0x0fce getvar version
version: 0.5
finished. total time: 0.000s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot.exe -i 0x0fce oem unlock 0x[my key]
...
(bootloader) Unlock phone requested
OKAY [ 0.087s]
finished. total time: 0.087s
C:\Program Files (x86)\Android\android-sdk\tools>
3. Next I installed a rooted kernel from driversax http://forum.xda-developers.com/showthread.php?t=1829729 but this one had problems with mounting of the SD card (you can find various comments on the thread), so I had to find an alternative one
4. With this kernel from krachlatte http://forum.xda-developers.com/showthread.php?t=1839865 all was a Go! pun intended
EDIT: There's a recovery for this as well now, which is fantastic!
Code:
C:\Program Files\Android\android-sdk\platform-tools>fastboot.exe -i 0x0fce flash boot Kernel6.0.B.184ro.secure.elf
sending 'boot' (4708 KB)...
(bootloader) USB download speed was 20784kB/s
OKAY [ 0.245s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 0.606s]
finished. total time: 0.855s
C:\Program Files\Android\android-sdk\platform-tools>
5. Installed Superuser, BusyBox and Root Explorer from Play store
6. Minato128 had been playing around with the messaging on Xperia S http://d.hatena.ne.jp/minato128/20120417/1334659736 so I thought the process must be similar for Go, as well
They were using the mms.apk modded by Jake http://blog.yo-ki.com/post/Android-22-Froyo-Softbank-MMS.aspx but that did not work for me. Actually it never had before with Desire, either.7. I extracted mms.apk that I have successfully used with my Desire ROMs from Takuo http://takuo.jp/junk/Mms.apk/OLD/ - update-mms-20100908.01-sense-froyo-signed.zip and transferred it to the phone
8. Using Root Explorer I renamed system/app/conversations.apk to conversations.apk.bak and transferred Mr Takuo's mms.apk to system/app
9. Installed mms.apk using the stock app Astro, which has a nice "Install" feature
FYI the APN settings for Softbank, I'm using a black SIM from iPhone (which is why I have to modify mms.apk, to change the user agent to, for example, iPhone. Softbank has only locked phones and additionally no Sonys on their lineup so we are forced to "hack" a bit )
Code:
Name: Smile MMS
APN: smile.world
Port: 0
Username: dna1trop
Password: so2t3k3m2a
MMSC: http://mms/
MMS proxy: smilemms.softbank.ne.jp
MMS port: 8080
MCC: 440
MNC: 20
Authentication type: PAP or CHAP
APN Type: mms
Name: Smile Internet
APN: smile.world
Username: dna1trop
Password: so2t3k3m2a
MCC: 440
MNC: 20
Authentication type: PAP or CHAP
I create separate APs for MMS and Internet, most probably that's not necessary, though
Everything works now.
Thanks "Go" to
Nerre
jozinek
driversax
krachlatte
Jake san at http://blog.yo-ki.com/
Minato128 san at http://d.hatena.ne.jp/minato128/
Kitame Takuo san at http://blog.takuo.jp/
And to Sony for being a good sport and supporting open source development!
I merely collected the info on one post.
As there is no forum section for Xperia Go I posted this here, many Go related posts seem to have ended up in this section.
Admins be so kind as to relocate this post to more appropriate location, if this is not the right place.
BR,
-Petteri
Click to expand...
Click to collapse
I did everything as you said and then
I finally manage to unlock the bootloader .
I follow the instructions http://unlockbootloader.sonymobile.com/instructions
And when I reach to step 14 cmd do nothing .
So what I did ?????
Just copy-paste the
(fastboot.exe - AdbWinApi.dll - AdbWinUsbApi.dll)
from
android-sdk/platform-tools
to the direction of my cmd shows when I open it
e.x. (c:\Users\Acer>)
And everything works .
THANKS !!!!!!!!!!!
Related
Hi, I'm looking for the best windows software to install APK file into my Xperia X10 or to any android phone , and to be a win7 compatible .
thanks in advance
I like iAPK, which makes APK installing a drag-and-drop task.
http://forum.xda-developers.com/showthread.php?t=716806
machhho said:
Hi, I'm looking for the best windows software to install APK file into my Xperia X10 or to any android phone , and to be a win7 compatible .
thanks in advance
Click to expand...
Click to collapse
Try these guys there the shiznit all this stuff worked for me on my
x10a ATT USA Now 2.1.1updated
Benchmarks are 750ish per the Quadrant app
ATT and Rogers (Thank you again BluechipJ for the settings and Video)Settings are at the bottom of this post but it’s a good thing to check all your settings and write them down before you start.
Also at the bottom of the post are the apps that work for me I can get 36 to 48 hours of normal use checking mail,news weather and facebook. And about 24 hours of heavy web use downloads,videos and surfing and then some.
Also before “I” started I did a factory reset and went to SU updates and did a repair ( And did a reboot “restarted” )So I started with a fresh up to date phone. Then followed the guides To the letter.
These guys now what there doing I have had no problems at all with my phone signals and operations are even better now but you be the judge.
[FLASHTOOL GUIDE] HOW TO for n00bies
Thank you
rendeiro2005 Senior Member for the Guides,Tools and Roms.
http://forum.xda-developers.com/showthread.php?t=928343
I use 2.8 if you are a noobie like me it works.
( [UPDATE 22/03/2011] Flashtool BETA version 0.2.9.1 )
Thank you
Bin4ry Senior Member and Androxyde Senior Member for the Guides,Tools and Roms.
And watch the video ( http://www.youtube.com/watch?v=B9_pFOxPJUY )
Thank you BluechipJ for the video and Settings.
This video is old but the updated 2.8 flasher works fine you can root and all the stuff in it works fine. [UPDATE 22/03/2011] Flashtool BETA version 0.2.9.1.
Read the new forums for the new roms if you want something other then the 2.1.1updated
ALL WAYS RUN FLASHTOOL IN Administrator (right click app click run as Administrator) do not click open (on XP pro any way) but read the forums for your OS I’m sure it’s there. Be sure to check DATES and updates on forums
And this thread it has some good stuff.
http://forum.xda-developers.com/showthread.php?t=955703
Thank you DooMLoRD Senior Member For Guides,Tools and Roms.
ROOT FIRST check perm then Install xRecovery, then all rest. Read the forum on how to.
Also check ALL DATES on ALL Posts,roms an apps "software" you download. And use only Updated Stuff but be careful of Beta just check in the Forum for what works and what doesn’t also check back or better yet Subscribe to XDA and to THAT forum and Senior Member so you can keep up to date on your x10
Oh and the biggest thing to remember is to THANK ALL THESE GUYs. So cools have fun be patient and read all BEFORE you start.
DO NOT KILL APPs they will just restart again and kill battery power
If you want to stop an app use Titanium Backup freezer
Thank you again BluechipJ for the settings
USA AT&T APN (3G) Settings:
Name: AT&T
APN: wap.cingular
Proxy: [blank]
Port: [blank]
Username:[email protected] [case sensitive]
Password:CINGULAR1 [case sensitive]
Server: [blank]
MMSC: http://mmsc.cingular.com
MMS Proxy: wireless.cingular.com
MMS Port: 80
MCC:310
MNC:410 (note. this could also be 310, 41 or 15)
APN Type: [blank]
Rogers APN (3G) Settings:
APN Name: Rogers [doesn't matter]
APN: rogers-core-appl1.apn [a p p L ONE]
Proxy: Not Set Port: Not Set
Username: Not Set
Password: Not Set
Server: Not Set
MMSC: http ://mms.gprs.rogers.com
MMS Proxy: 10.128.1.69
MMS Port: 80
MCC: 302
MNC: 720
APN Type: Not Set
How toTurn off all Call Forwarding not ( voicemail or caller ID ) on ATT network. #002# in dial pad and press call. This works in USA and ?.
You have to do this every time you check call forwarding settings for it to work all the time because every time you check the button it resets back to default which is on.
X10 Test mode
From the unlock screen, do not unlock but press
1.6
Menu Back Back Menu
Back Menu Menu Back
2.1
Home Back Back Home
Back Home Home Back
Phone/battery/Usage info: *#*#4636#*#*
IMEI number: *#06#
Be careful with this one it may or may NOT work
Enter to phone menu without SimCard - after Wrong PIN: press NO:
* * 0 4 * 0 0 0 0 * 0 0 0 0 * 0 0 0 0 #
Information about SIMLOCK:
Software version: *#8377466#
AGAIN BE CAREFUL WITH SOME CODES I'M NOT RESPONSIBLE IF YOU PUT IN THE WRONG CODES OR THEY DO NOT WORK ON YOUR PHONE
if this helps please click the thanks button
Hey guys quick question. I have noticed on my LG optimus T that sending or recieving pictures messages are of horrible quality, its almost like when sent tmobile compresses them down BIG TIME. doesnt matter if its taken at 3mp and sent or a quality picture recieved they are all really crappy? how do i fix this, same thing happens on different messaging apps as well.
Could this be something i would have to contact tmobile about, or is this ROM related (ie some compression mms setting?)
running LOL (2.2.2) w/ paolom70's v4 kernel..... stock messaging app (thought others dont change the problem)
edit - its almost as if the phone is resizing images before they are sent (take a pic with the camera at 2mp and it only uses 17kb of the 300k alotment) same for when the messages are recieved.... could this be some issue with my APN?
Name: T-Mobile US
APN: epc.tmobile.com
Proxy: <not set>
Port: <not set>
Username: None
Password: None
Server: <not set>
MMSC: [http]://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: <not set>
MMS Port: <not set>
MCC: 310
MNC: 260
APN Type: <not set>
nd4spdbh said:
edit - its almost as if the phone is resizing images before they are sent
Click to expand...
Click to collapse
Of course it is... Go SMS has settings for this crap. Regardless, if you want to send good unmangled pictures, use email and not MMS.
nd4spdbh said:
Hey guys quick question. I have noticed on my LG optimus T that sending or recieving pictures messages are of horrible quality, its almost like when sent tmobile compresses them down BIG TIME. doesnt matter if its taken at 3mp and sent or a quality picture recieved they are all really crappy? how do i fix this, same thing happens on different messaging apps as well.
Could this be something i would have to contact tmobile about, or is this ROM related (ie some compression mms setting?)
running LOL (2.2.2) w/ paolom70's v4 kernel..... stock messaging app (thought others dont change the problem)
edit - its almost as if the phone is resizing images before they are sent (take a pic with the camera at 2mp and it only uses 17kb of the 300k alotment) same for when the messages are recieved.... could this be some issue with my APN?
Name: T-Mobile US
APN: epc.tmobile.com
Proxy: <not set>
Port: <not set>
Username: None
Password: None
Server: <not set>
MMSC: [http]://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: <not set>
MMS Port: <not set>
MCC: 310
MNC: 260
APN Type: <not set>
Click to expand...
Click to collapse
I've checked everywhere I can find inside the rom to do with mms settings, can't see anything related to quality.. I myself noticed this and it has been bugging me, I've resorted to emailing people photos
I said that Go SMS has the settings. It does not come with ROMs, go install it from Market.
(Please do NOT quote irrelevant stuff.)
As dr.notor said, GoSMS will take care of the problem. After a quick search for "mms compression" in this section, I learned from this thread that GoSMS is capable of replacing the stock MMS app entirely. That is, if you uninstall Mms.apk and configure GoSMS correctly, it will handle all system calls to the MMS app. The notes at the beginning of the thread I linked explain how the process goes down.
Also, many other devices have various modified Mms.apk available. Some of them simply raise the MMS limit to 5MB, and others also disable image scaling/compression unless the limit is breached. The HTC Evo 4G has one of each fix, and I'm seeing a combo fix for the Samsung Epic 4G.
The Evo fixes are specific to HTC's framework, but if you're comfortable doing a little experimentation, you might be able to get away with replacing Mms.apk with the modified one for the Epic, found here.
Good luck!
thats the thing... i have tried gosms, and handcent, and both exhibit the same problem.... take a quality picture and upon attachment it gets resized (albeit not as much in go and handcent) but when received it looks horrible... down around 6kb.
i switched back to the stock rom and it does not do this, it resizes the images properly. so its obvious its some setting within the rom.... now to find that setting.
If you have not already, try messing with the user-agent for your MMS app. If the default isn't working, an iPhone u-a may help. Also, when using GoSMS, be sure that "preserve image resolution" is checked.
You say that the stock ROM does not exhibit this problem - have you tried pushing Mms.apk from the stock ROM over to your current one and rebooting? (Be careful if you do - always be prepared to 'adb push' a backup of any APK you replace in case of failure!)
Sent from gingerbread-evo-deck
OK so i grabbed the original Mms.apk from the original rom, popped it on my sd card then
adb shell
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# rm /system/app/Mms.apk
# cp /sdcard/Mms.apk /system/app/
# chmod 644 /system/app/Mms.apk
the app is now uninstalled (and if i try to use a previous shortcut to the messaging app it says application is not installed)
could this be because its a stock app.... and the rom i am using is deodex'd?
its definietly not the user agent, i unpacked both the Mms.apk in the rom i am using and the stock Mms.apk and the useragent line is exactly the same... in fact the entire mms_config.xml is exactly the same.....
this leads me to believe its something other than the Mms app...
regardless of what app (stock Mms, gosms, handcent....) the picture received that i send back to my phone, someone else sends to my phone, or someone else receives, the picture is all of 100px tall. when i switch back to the stock rom it sends decent quality pictures that are resized properly to fit within the 300kb window.
nd4spdbh said:
OK so i grabbed the original Mms.apk from the original rom, popped it on my sd card then
adb shell
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# rm /system/app/Mms.apk
# cp /sdcard/Mms.apk /system/app/
# chmod 644 /system/app/Mms.apk
the app is now uninstalled (and if i try to use a previous shortcut to the messaging app it says application is not installed)
could this be because its a stock app.... and the rom i am using is deodex'd?
Click to expand...
Click to collapse
A lot of things can cause trouble when replacing system apps. First, I would deodex the stock Mms.apk. Second, rm /system/Mms.apk. If you use TB, have it clean your DC (Menu->More->Clean up the Dalvik cache ...) and push Mms.apk again. If you don't use TB, wipe the DC from recovery before pushing Mms.apk. Android should recognize it automatically while running, but if not, reboot. If it still fails to recognize your pushed apk, try pushing it with the name, com.android.mms.apk, instead. Also, shortcuts sometimes break when replacing APKs, so launch from the app drawer when in doubt.
If the stock Mms.apk fails to solve the problem, you likely have a framework issue, or perhaps even a library issue.
Sent from gingerbread-evo-deck
not to sound like a noob, but how does one go about deodexing an APK?
im going to try and play around with different roms n whatnot... thought it seems like devoid does pretty much the same thing....
i wonder if i should call up tmobile and see if they have the right phone on record for my account.
It's been a while since I've had to deodex anything, but let's see if I can recall the steps properly...
(Before you begin, make sure you can execute "java -version" from a command line. In case it fails, or is not installed, here is a nice guide on Java and the Windows Command Prompt, hosted at Princeton.)
Now, on to the deodexing:
1. Download baksmali-x.x.x.jar and smali-x.x.x.jar from this Google Code project to a folder of your choosing.
2. Navigate to the folder where you placed baksmali and smali. Extract the entire /system/framework directory from your odexed ROM here. Also extract the APK and its odex to your folder. Your folder should now look something like this:
Code:
.\framework\
.\baksmali-x.x.x.jar
.\smali-x.x.x.jar
.\Something.apk
.\Something.odex
3. Open a command prompt in your folder. (Tip: On Windows 7, you can hold shift and right-click in the empty space inside the folder, then choose "Open command window here...") The following commands will disassemble your odex, then reassemble it into a classes.dex file.
Code:
java -Xmx512m -jar baksmali-x.x.x.jar -d framework -x ODEX.FILE
java -Xmx512m -jar smali-x.x.x.jar out -o classes.dex
(Substitute x.x.x with the baksmali and smali version numbers, and ODEX.FILE with your odex name.)
4. You should now have a new folder named "out." This contains the disassembled code. You should also have a new file named "classes.dex," which contains the reassembled code in non-odexed form. Using 7-zip, WinRAR, or similar, open up the APK you extracted earlier and add your new classes.dex file to it. Your APK is now deodexed - push it!
5. ???
6. Profit!
haha thanks man, i shall give that a try tomorrow and report back.
thanks for all your help
A whole lot simpler way to deodex and lots of others - use HTC Kitchen
dr.notor said:
A whole lot simpler way to deodex and lots of others - use HTC Kitchen
Click to expand...
Click to collapse
I would be pretty hesitant to install Cygwin or a virtual machine just to use a shell script to automate a task, instead of typing, (or simply copy-pasting,) one or two commands.
Kitchen looks impressive though. I'm on Linux, and I maintain my own toolchain because automation scripts often become outdated, but Kitchen apparently addresses both of these things!
Thanks, Doc!
Sent from gingerbread-evo-deck
I get this error every time when using htc dev boot unlocker. error: cannot load 'unlock_code.bin'
any ideas please
Is the unlock_code.bin file in the same directory as all the other unlock files?
still wont work
My Unlock_code.bin file is in the same file as the fastboot, yet it still wont load...
UPDATE
FIXED: had to change the directory in Command Prompt from c:\user to the location of the .bin file.
Duckvdm said:
My Unlock_code.bin file is in the same file as the fastboot, yet it still wont load...
UPDATE
FIXED: had to change the directory in Command Prompt from c:\user to the location of the .bin file.
Click to expand...
Click to collapse
finally something worked for me
blackbolo said:
finally something worked for me
Click to expand...
Click to collapse
I have the same problem, exactly like the op posted, but I did change the directory to the same one where the unlock bin file was which also included the 3 files that htcdev.com/bootloader told me to put in there (such as fastboot)
But still doesn't work. In fact I can provide a screenshot clearly showing the directory where the unlock file and other files are, aswell as my command prompts and errors.
Please help me don't disregard my post : P I have been trying to figure this out for hours, I even called htcdev support and they couldn't help, told me to ask in forums LOL? why is there a support number if they won't help?
pontypool said:
I have the same problem, exactly like the op posted, but I did change the directory to the same one where the unlock bin file was which also included the 3 files that htcdev.com/bootloader told me to put in there (such as fastboot)
But still doesn't work. In fact I can provide a screenshot clearly showing the directory where the unlock file and other files are, aswell as my command prompts and errors.
Please help me don't disregard my post : P I have been trying to figure this out for hours, I even called htcdev support and they couldn't help, told me to ask in forums LOL? why is there a support number if they won't help?
Click to expand...
Click to collapse
*facepalm* Um Sir, if your fastboot, adb, and UNLOCK_TOKEN files are all in the folder "aaa" why are you directing your command prompts to the non-existent "abd" folder? In your case the very first thing you should be typing into the command prompt is: cd E:\aaa Now you can actually execute fastboot commands because that is where all the files are.
JnNn98 said:
*facepalm* Um Sir, if your fastboot, adb, and UNLOCK_TOKEN files are all in the folder "aaa" why are you directing your command prompts to the non-existent "abd" folder? In your case the very first thing you should be typing into the command prompt is: cd E:\aaa Now you can actually execute fastboot commands because that is where all the files are.
Click to expand...
Click to collapse
my mistake. i had two folders aaa and abd with identical files. but the error still remains nevertheless, as seen in the new screenshot
it's just a stupid mistake of mine. i didnt put the CD part in.. i assume that was for people who had the files on a cd.
* walks away in shame *
pontypool said:
my mistake. i had two folders aaa and abd with identical files. but the error still remains nevertheless, as seen in the new screenshot
it's just a stupid mistake of mine. i didnt put the CD part in.. i assume that was for people who had the files on a cd.
* walks away in shame *
Click to expand...
Click to collapse
So does it work now? BTW "cd" is just something you would type when you have to change the directory in the cmd, it actually has nothing to do with actual CD's (Compact Discs)
---------- Post added at 03:38 PM ---------- Previous post was at 03:22 PM ----------
pontypool said:
my mistake. i had two folders aaa and abd with identical files. but the error still remains nevertheless, as seen in the new screenshot
it's just a stupid mistake of mine. i didnt put the CD part in.. i assume that was for people who had the files on a cd.
* walks away in shame *
Click to expand...
Click to collapse
So does it work now? BTW "cd" is just something you would type when you have to change the directory in the cmd, it actually has nothing to do with actual CD's (Compact Discs)
JnNn98 said:
So does it work now? BTW "cd" is just something you would type when you have to change the directory in the cmd, it actually has nothing to do with actual CD's (Compact Discs)
---------- Post added at 03:38 PM ---------- Previous post was at 03:22 PM ----------
So does it work now? BTW "cd" is just something you would type when you have to change the directory in the cmd, it actually has nothing to do with actual CD's (Compact Discs)
Click to expand...
Click to collapse
yes it works now. I realise now, but at the time I assumed it was a suggested directory if the files are stored on a cd.
Unknown error
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
E:\Documents and Settings\MovilSol#2\Desktop>fastboot flash unlocktoken unlock_code.bin
error: cannot load 'unlock_code.bin': Unknown error
Please help me! D:
That should be a capital U in Unlock_code.bin
Sent from my Evo 3D CDMA using xda premium
xion009 said:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
E:\Documents and Settings\MovilSol#2\Desktop>fastboot flash unlocktoken unlock_code.bin
error: cannot load 'unlock_code.bin': Unknown error
Please help me! D:
Click to expand...
Click to collapse
Try to generate the Unclock_code.bin from htcdev website again.
Replace the new file in the fastboot directory . It should work .
XDA-Dev. said:
Try to generate the Unclock_code.bin from htcdev website again.
Replace the new file in the fastboot directory . It should work .
Click to expand...
Click to collapse
I already tried to generate the unlock_code.bin alot of times in htcdev and none works /:
error
Duckvdm said:
My Unlock_code.bin file is in the same file as the fastboot, yet it still wont load...
UPDATE
FIXED: had to change the directory in Command Prompt from c:\user to the location of the .bin file.
Click to expand...
Click to collapse
yes thanks for that mate was getting same eror so i dropped the 2 files into the path that command prompt was displaying
Help Im having the same problem
Im using a window pc runing windows 8. I have done everthing gotten the .bin file and now i get cannot load 'unlock_code.bin
Thank you! This fixed my issue, though it was a small blow to my ego (seems obvious in retrospect). Still having trouble actually rooting my phone, but at least I'm closer now?
Use kingoroot in fastboot mode no need unlock code.bin
Try it
Can't get my Unlock_code.bin to initiate
I have all my files in one folder and I still cannot get this last step to initiate and I am meet with the following
Johns-MacBook-Pro:~ johnsummersjr$ Users/johnsummersjr/Desktop/Android/fastboot flash unlocktoken Unlock_code.bin
-bash: Users/johnsummersjr/Desktop/Android/fastboot: No such file or directory
Johns-MacBook-Pro:~ johnsummersjr$
/Users/johnsummersjr/Desktop/Screen Shot 2015-11-30 at 9.59.55 PM.png
HTC BootLoader Via Macbook pro
JohnSnow2015 said:
I have all my files in one folder and I still cannot get this last step to initiate and I am meet with the following
Johns-MacBook-Pro:~ johnsummersjr$ Users/johnsummersjr/Desktop/Android/fastboot flash unlocktoken Unlock_code.bin
-bash: Users/johnsummersjr/Desktop/Android/fastboot: No such file or directory
Johns-MacBook-Pro:~ johnsummersjr$
/Users/johnsummersjr/Desktop/Screen Shot 2015-11-30 at 9.59.55 PM.png
Click to expand...
Click to collapse
UPDATE 12/3/15
I got everything into one directory and entered: /Users/johnsummersjr/Desktop/HTC\ Unlock\ BootLoader/adt-bundle-mac-x86_64-20140321/sdk/platform-tools/fastboot unlocktoken Unlock_code.bin. Yet I am met with the following
Johns-MacBook-Pro:~ johnsummersjr$ /Users/johnsummersjr/Desktop/HTC\ Unlock\ BootLoader/adt-bundle-mac-x86_64-20140321/sdk/platform-tools/fastboot unlocktoken Unlock_code.bin
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
Fixed
cal4877 said:
I get this error every time when using htc dev boot unlocker. error: cannot load 'unlock_code.bin'
any ideas please
Click to expand...
Click to collapse
use fastboot folder provided by htc
you can find it on htc site
first select your device for unlocking bootloder then on next page there have given steps 1,2,3..
on the last there will be fastboot downloading links :good:
It will absolutely solve your problem
I have only personally tested this on Agrabren's Disarmed Toaster ROM (CDMA)
This is my first guide, so bear with me I'm creating this because I've noticed that MetroPCS users of the Evo 3D are a minority on these forums, and as a result, there isn't much support in the department of MMS picture messaging for AOSP ROMs. I've been looking for a solution for awhile (especially since the changes made to the messaging app for CM10) and I've finally got it working.
Requirements:
- You must have completed this guide (minus the MMS part, as it's for Sense only)
- You'll need an AOSP based Jelly Bean ROM. I've only tested it on CM10 myself, can't confirm if others work. Only tested on 4.1.2, though it may work on 4.2.X
- You'll need a file explorer with root access installed
- You'll need these files
- You'll need just a bit of patience
Instructions:
- Download the files above, unzip and transfer them to your SD card
- Download "Epic4gtouch-jbfk09-metropcs-mms-fix-signed.zip" by oakieville from this thread and transfer it to your SD card (do not unzip this particular file!)
- Open a file manager that has root access
- Copy "apns-conf.xml" to /system/etc
- Copy "mms.apk" to /system/app (replace the original one) (This may reboot your phone, mine did once while doing this step)
- [Optional] Copy "eri.xml" to /data (this will replace all "Sprint" carrier banners to "MetroPCS")
- Reboot to recovery, flash "Epic4gtouch-jbfk09-metropcs-mms-fix-signed.zip"
- Reboot
- Open the "Voice Dialer" app (it should be installed on the ROM already) and say "Open APNs"
- A prompt should appear saying "Open APNs". Select it.
- Hit the settings key and select "New APN"
- Enter the following in all lowercase letters:
Code:
Name: metropcs
APN: internet
Proxy: [COLOR="red"]Do not modify[/COLOR]
Port: [COLOR="red"]Do not modify[/COLOR]
Username: [COLOR="red"]Do not modify[/COLOR]
Password: [COLOR="red"]Do not modify[/COLOR]
Server: [COLOR="red"]Do not modify[/COLOR]
MMSC: http://mms.metropcs.net:3128/mmsc
MMS proxy: wap.metropcs.net
MMS port: 3128
MCC: [COLOR="red"]Do not modify[/COLOR]
MNC: [COLOR="red"]Do not modify[/COLOR]
Authentication type: [COLOR="red"]Do not modify[/COLOR]
APN type: mms
APN protocol: [COLOR="red"]Do not modify[/COLOR]
APN roaming protocol: [COLOR="red"]Do not modify[/COLOR]
Bearer: [COLOR="red"]Do not modify[/COLOR]
- Hit the settings key again and save the APN.
- Reboot your phone
- Try sending a picture message to confirm it works
If you followed the steps correctly and in order (yes, the order matters very much!) it should work. I ran through the process a few times using backups & fresh installs to make sure it worked for me. Again, this has only been tested on CyanogenMod 10, so results may vary for different ROMs.
Credit:
Agrabren - The MMS APK provided is a modified version of the one included in his Disarmed Toaster ROM, which is also the ROM I used to test all of this on
oakieville - For the flashable zip that does a lot of the work
The Evo 4G & the Epic 4G Touch forums - Spent a lot of time looking through various guides and MMS fixes for various ROMs
I hope this helps anybody who wanted to run CM10 on their MetroPCS Evo 3D's!
This is great news! Congrats metros owners, now all that's left is a full fix for virgin lol
DarkRazorZ said:
II have only personally tested this on Agrabren's Disarmed Toaster ROM (CDMA)
This is my first guide, so bear with me I'm creating this because I've noticed that MetroPCS users of the Evo 3D are a minority on these forums, and as a result, there isn't much support in the department of MMS picture messaging for AOSP ROMs. I've been looking for a solution for awhile (especially since the changes made to the messaging app for CM10) and I've finally got it working.
Requirements:
- You must have completed this guide (minus the MMS part, as it's for Sense only)
- You'll need an AOSP based Jelly Bean ROM. I've only tested it on CM10 myself, can't confirm if others work. Only tested on 4.1.2, though it may work on 4.2.X
- You'll need a file explorer with root access installed
- You'll need these files
- You'll need just a bit of patience
Instructions:
- Download the files above, unzip and transfer them to your SD card
- Download "Epic4gtouch-jbfk09-metropcs-mms-fix-signed.zip" by oakieville from this thread and transfer it to your SD card (do not unzip this particular file!)
- Open a file manager that has root access
- Copy "apns-conf.xml" to /system/etc
- Copy "mms.apk" to /system/app (replace the original one) (This may reboot your phone, mine did once while doing this step)
- [Optional] Copy "eri.xml" to /data (this will replace all "Sprint" carrier banners to "MetroPCS")
- Reboot to recovery, flash "Epic4gtouch-jbfk09-metropcs-mms-fix-signed.zip"
- Reboot
- Open the "Voice Dialer" app (it should be installed on the ROM already) and say "Open APNs"
- A prompt should appear saying "Open APNs". Select it.
- Hit the settings key and select "New APN"
- Enter the following in all lowercase letters:
Code:
Name: metropcs
APN: internet
Proxy: [COLOR="red"]Do not modify[/COLOR]
Port: [COLOR="red"]Do not modify[/COLOR]
Username: [COLOR="red"]Do not modify[/COLOR]
Password: [COLOR="red"]Do not modify[/COLOR]
Server: [COLOR="red"]Do not modify[/COLOR]
MMSC: http://mms.metropcs.net:3128/mmsc
MMS proxy: wap.metropcs.net
MMS port: 3128
MCC: [COLOR="red"]Do not modify[/COLOR]
MNC: [COLOR="red"]Do not modify[/COLOR]
Authentication type: [COLOR="red"]Do not modify[/COLOR]
APN type: mms
APN protocol: [COLOR="red"]Do not modify[/COLOR]
APN roaming protocol: [COLOR="red"]Do not modify[/COLOR]
Bearer: [COLOR="red"]Do not modify[/COLOR]
- Hit the settings key again and save the APN.
- Reboot your phone
- Try sending a picture message to confirm it works
If you followed the steps correctly and in order (yes, the order matters very much!) it should work. I ran through the process a few times using backups & fresh installs to make sure it worked for me. Again, this has only been tested on CyanogenMod 10, so results may vary for different ROMs.
Credit:
Agrabren - The MMS APK provided is a modified version of the one included in his Disarmed Toaster ROM, which is also the ROM I used to test all of this on
oakieville - For the flashable zip that does a lot of the work
The Evo 4G & the Epic 4G Touch forums - Spent a lot of time looking through various guides and MMS fixes for various ROMs
I hope this helps anybody who wanted to run CM10 on their MetroPCS Evo 3D's!
Click to expand...
Click to collapse
Glad u like my work not sure if u notice i actual have an aosp flashable zip for the evo 3d in 3d forum u would prob still need the mms.apk and apns-conf.xml from my epic zip because I left evo3d before jellybean so the aosp zip isn't for jelly bean but I do have a cm10 zip for epic4g touch, the reason u have to place the file with root explorer instead of the zip doing it for u is because the zip is for epic4g touch and has different mount points then evo3d so the zip cant mount system to add files also don't add new apn in apns menu just reset apns to defualt it will fill in metro apns for u as long as apns-conf.xml is placed in /system/etc first that's where defualt apns r read from so if u reset to defualt it sets them for u if apns don't show up in apn menu it is because build.prop needs to be edited change 310120 to 310027 if anyone would like I could just build a cm10 flashable zip to do it all for u
Has anyone tested this MMS fix on a stock Jelly Bean ROM for Galaxy S2 or S3?
In particular, I'm running ODIN GB08 latest version of Jelly Bean as of Feb, 2013 on a fully flashed and rooted Sprint Epic 4G Touch (Sprint's brand of the Samsung Galaxy S2) on MetroPCS. Anyone know if this method or any other will work for this version of Jelly Bean on these phones?
I am trying to unlock my HTC Incredible 4G on Verizon to load a new ROM onto it. All of my attempts have failed up to this point, by using the WinDroid v2.3 automated tool. I get the following output during the process:
Code:
Task:
1) WINDROID USERS CHOOSE THIS OPTION!
2) Set CID to SuperCID (11111111) - Requires Root
3) Revert CID to original state (VZW__001) - Requires Root
4) Re-lock the bootloader
5) Install recovery
6) Put phone into temp-root mode
10) Exit
Choose a task: 1
========================
= Step 1: Temp-Root =
========================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA************ device
Under "List of devices attached" above, you should see your device
listed (looks like HTXXXXXXXXXX).
Do you see your device (Y/N)? y
Now unlock your device and confirm the restore operation.
By the time you are done reading this sentence, it should be safe to
accept the restore prompt on your device. You should not have a backup
password set on your phone, so leave both password fields empty.
If this process is successful, the script will continue. If not, this
shell will run forever and you must exit by closing this window.
When you see this message, the restore is complete. Your phone will
now reboot to what looks like an unusable state (be patient!). A
status bar will show across the top, but there will be no ring unlock.
This is good! Wait for the script to begin step 2: SuperCID.
========================
= Step 2: SuperCID =
========================
Your phone's CID is being modified to SuperCID. Once complete, your
phone will reboot to the bootloader.
2+0 records in
2+0 records out
1024 bytes transferred in 0.025 secs (40960 bytes/sec)
142 KB/s (1024 bytes in 0.007s)
31 KB/s (1024 bytes in 0.032s)
2+0 records in
2+0 records out
1024 bytes transferred in 0.035 secs (29257 bytes/sec)
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.011s]
finished. total time: 0.012s
Just above, you should see (bootloader) cid: 11111111
1) Yes, my cid is 11111111. Keep going.
2) No, my cid is VZW__001. Factory reset and try again.
3) No, my cid is VZW__001. Exit the script.
There are two things I notice here:
1) My phone is not identified as "HTxxxxxxxxxx" but rather "FA**********".
2) It appears to work, with the reading and writing of the files, but then it doesn't work.
One thing that I noticed was that when I go into the bootloader when this does not work, I get the first attachment.
When I go to the "Recovery" option, then I get the second attachment.
It appears that I originally put a ROM or S-off'd and unlocked my phone, but somehow lost the unlock and can't figure out how to fix it.
Any help in figure it out would be appreciated.
Do you know which OTA is currently on the phone? The unlock method depends greatly on which one is installed. Assuming you're on the latest, try this method: http://forum.xda-developers.com/showthread.php?t=2664460 The script looks slightly different than what you've posted above.
junkmail9 said:
Do you know which OTA is currently on the phone? The unlock method depends greatly on which one is installed. Assuming you're on the latest, try this method: http://forum.xda-developers.com/showthread.php?t=2664460 The script looks slightly different than what you've posted above.
Click to expand...
Click to collapse
Thanks for the input.
My device is at the most current OTA: 2.19.605.2 710RD
Android: 4.0.4
Kernel:
3.0.8-01625-g9d06ef9
[email protected] #1
SMP PREEMPT
I tried the link that you pointed to with no success. I got the following error messages:
Code:
/sdcard/cid: cannot open for write: Read-only file system
remote object '/sdcard/cid' does not exist
The system cannot find the file specified.
cannot stat 'cid': No such file or directory
/sdcard/cid: cannot open for read: No such file or directory
rm failed for /sdcard/cid, No such file or directory
Could Not Find C:\Users\Keith\Downloads\cid
I've tried just the straight-forward process of a number of different scripts. I think there is something specific that I am missing.
keithsmessina said:
Thanks for the input.
My device is at the most current OTA: 2.19.605.2 710RD
Android: 4.0.4
Kernel:
3.0.8-01625-g9d06ef9
[email protected] #1
SMP PREEMPT
I tried the link that you pointed to with no success. I got the following error messages:
Code:
/sdcard/cid: cannot open for write: Read-only file system
remote object '/sdcard/cid' does not exist
The system cannot find the file specified.
cannot stat 'cid': No such file or directory
/sdcard/cid: cannot open for read: No such file or directory
rm failed for /sdcard/cid, No such file or directory
Could Not Find C:\Users\Keith\Downloads\cid
I've tried just the straight-forward process of a number of different scripts. I think there is something specific that I am missing.
Click to expand...
Click to collapse
Sorry for the delay in response. Looking again at your screenshot in the OP, you are indeed missing the CID. It should appear between "FIREBALL" and "HBOOT":
I have not dealt directly with that one before, but I would imaging that during temproot, you'll need to recreate the directory. I vaguely recall in a post in this forum on how to manually push a different CID via memory chunk. That might be the best approach to rebuild that area so that you can get going again.
Two questions for the general community:
1. Does anyone know if flashing the RUU will restore the CID?
@keithsmessina - It probably wouldn't hurt to try this anyway. I am guessing it will fail due to lack of CID.
2. Will sending the following command work while phone is in bootloader if the phone is not s-off and the \sdcard\CID directory is missing? What, if any other damage could occur if the \sdcard\CID directory is missing?
Code:
fastboot oem writecid VZW__001
junkmail9 said:
Two questions for the general community:
1. Does anyone know if flashing the RUU will restore the CID?
@keithsmessina - It probably wouldn't hurt to try this anyway. I am guessing it will fail due to lack of CID.
2. Will sending the following command work while phone is in bootloader if the phone is not s-off and the \sdcard\CID directory is missing? What, if any other damage could occur if the \sdcard\CID directory is missing?
Code:
fastboot oem writecid VZW__001
Click to expand...
Click to collapse
Thank you for the suggestions.
1. I tried this, but got the message: "Main version is older." I think I can only do that if my version is lower than the current RUU.
2. I tried the fastboot write, but I got:
Code:
(bootloader) fighter_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) sdcc_init_memory_device done
(bootloader) SD clock freq = 19MHz....
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.172s]
finished. total time: 0.174s
When I tried: adb devices with the phone at "fastboot USB", I didn't see anything, so I think it failed for that reason. I tried killing adb, removing and reinserting the USB, adn then running adb devices, but still comes up empty.
I'm really at a loss, but appreciate the help from you guys.
I managed to figure out the read-inly access. HTC Sync Manager started each time and grabbed the SD card before the script could do anything. I renamed the HTC Sync Manager to stop it from running. Then I re-ran the script and got:
Code:
2+0 records in
2+0 records out
1024 bytes transferred in 0.002 secs (512000 bytes/sec)
333 KB/s (1024 bytes in 0.003s)
71 KB/s (1024 bytes in 0.014s)
2+0 records in
2+0 records out
1024 bytes transferred in 0.002 secs (512000 bytes/sec)
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.010s]
finished. total time: 0.012s
So, I am still not getting the right CID, but progress nonetheless.
Try uninstalling all HTC software rather than renaming it. Also I believe
http://forum.xda-developers.com/showthread.php?t=2664460 does not require the super cid.
From my Chroma Flo
wmuflyer said:
Try uninstalling all HTC software rather than renaming it. Also I believe
http://forum.xda-developers.com/showthread.php?t=2664460 does not require the super cid.
From my Chroma Flo
Click to expand...
Click to collapse
Thank you for that. I don't know how many times I've gone through it, but I finally got that you just have to do step 6 rather than step 1 to get S-Off. I now have S-Off with TWRP.
The next problem that I am running into is getting an error message when trying to flash the pacman fireball ROM:
Code:
This package is for device: fireballx; this device is .
Really appreciate all the help in getting me to this point.
Need to use the modified TWRP. Read the OP carefully it takes a bit of work, it swaps partitions so you have more space for apps.
Edit: OP in the PAC thread.
Sent from my Nexus 5 using XDA Free mobile app
wmuflyer said:
Need to use the modified TWRP. Read the OP carefully it takes a bit of work, it swaps partitions so you have more space for apps.
Edit: OP in the PAC thread.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I realize that I kept running into an issue changing one of the file systems during that first process which meant that only one of them changed: the "Data" filesystem.
The "Internal Storage" filesystem gave me an MTP error, but then said it finished successfully. It stayed as a vFAT filesystem.
I did get Liquidsmooth up and running with PaGapps, but am now looking for a way to resize my partitions, as there isn't much room left to install apps.
People have looked at resizing the partitions but nobody has had any luck. The partition change seems to be the best bet it was set up by MDMower for his CM builds http://mdmower.cmphys.com/cyanogenmod-fireball/ it might give you more information to make the swap. Beeko has stopped work on Liquid Smooth so for current Android 5.x PAC or CM are the choices and they only work with the partition swap. I have PAC on my Fireball but will probably try CM 12.1 soon.
keithsmessina said:
Thank you for that. I don't know how many times I've gone through it, but I finally got that you just have to do step 6 rather than step 1 to get S-Off. I now have S-Off with TWRP.
Click to expand...
Click to collapse
Excellent! Glad you got it done.
junkmail9 said:
Excellent! Glad you got it done.
Click to expand...
Click to collapse
I've managed to swap the partitions and get the Pacman ROM installed, thanks to the instructions you sent me, wmuflyer. No hiccups with the Pacman ROM, it seems to be polished and working flawlessly. Thanks again for all the help, guys! Really appreciate it.