Database Info

How to: CyanogenMod your G1 from scratch incl hardspl

for the t-mobile g1 with 1.6 firmware and some number stuff like drc92 and other G ones that won't cooperate..
to mod it from a stock (t-mobile nl) rom.
What u need :
1 sd-card (preferably more then 128mb)
1 pc running windows (i run win 7 ultimate)
1 usb cord
1 phone-internet connection (there is a wifi version too but since i find it not neccesary i wont link it. instead if you dont have phone internet : just download the packages on pc and put them in the G1)
1 app from market called : mybackup (you can use it for backing up contacts and stuff.. backup to sdcard and copy it to pc)
Backup
-download app MyBackup from the google marketplace and make a backup of programs and contacts (if you dont have phone-internet then get it from pc)
Preparing Gold Card:
- insert sd card into G1 and format it (whatever sd card and whatever format (there is only one on G1 hehe so go find it. also format is to be found in G1.)
- attach to pc and copy the RC7 image(DREAIMG.NBH) on the sd card in the G1 (do not detach from pc, i know you wanted to)
- goto appstore and download terminal emulator (as it says like that)
- open Terminal Emulator on G1
- type:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
- write down the code somewhere, its ur CID thingy
- push backbutton
Reverse the CID:
Begin: 1c5356555344202010051cc3b7008cf4
1c 53 56 55 53 44 20 20 10 05 1c c3 b7 00 8c f4 (yes i copied it from you thnx - normal code... add the spaces so your CID looks like this (your own CID not this one )
f4 8c 00 b7 c3 1c 05 10 20 20 44 53 55 56 53 1c - reversed one (note the couples are reversed)
00 8c 00 b7 c3 1c 05 10 20 20 44 53 55 56 53 1c - now change the first two digit to 00
so you will have something looking like this: 008c00b7c31c0510202044535556531c (this is example CID so use ur own!)
- goto revskills and get a goldcard image with the code ur having now. revskills page
- now get the mail and save the attachement in a dir
Making your Goldcard:
- right-click and open as admin Hxd editor
- in HxD editor :
- goto extra menu and open disk > choose psysical disk > ur sd card
- goto extra menu and open disk image > choose the received file from mail called : goldcard.img and press ok on the popup saying some about 512
- now go to this tab goldcard and goto topmenu and edit>choose select all and then topmenu again and copy
- now go to first tab (ur sdcard) and select 00000000 to 00000170 with mouse (mark it)
- goto top menu and select edit> write
- now goto top menu and save
- pull the G1 out of pc
- yes you can
- ok now pull the battery out (or shutdown if u have the time)
- press camera button+power so it will give this rainbow 3 color shizzle
- you see a gray screen saying some words you probably wanna read.
- now press power to confirm overwrite the rom thing
- reboot by holding the two phone buttons (hangup and answer)and press menu or home and back (im not sure but one of these work and you see something saying it updates some stuff.
(if this dont work in ur G1 (specially latest versions) you can use a sdhc usb cardreader or a windows mobile phone or anything else with direct disk acces mode , probably nokia and sony ericsson too)
on the next boot you will have the old RC7
(if you have no internet on phone you can skip the next 2 lines and download the package and copy it to the G1 (dont know where so if anyone can tell me it would be nice to help people out )
- fill in your google account stuff
- Download Android "Telnet" application from the Market.
- Download recovery.img and copy it to your SD card. rename it to recovery.img
- Download the Hard SPL and copy the zip file to the SD card. (this is for G1 drea110 htc dream only so be carefull as this stuff can ruin your phone)
- All files must be on the root of your SD card.
- turn off the phone and detach from the pc
Rooting your G1- RC7 phone:
On RC7 Rom and lower, anything you type into your keyboard is also being run in a hidden console with root permissions.
To get root access, do the following:
- Restart your phone. Wait for your phone to start up fully and show the home screen.
- Unlock it by pressing menu after you typed code for sim and it fully started ( it will auto-lock itself)
- Hit the enter key twice,(Yes, it will start up a contact search, so you can see what you type . aint it cool) type "telnetd" and press enter.
- start telnet application you downloaded before on G1 and connect to localhost. (if you dont see localhost and connect window you have wrong app or need to reboot another time). If you connect successfully, you will have a root prompt "#".
Type the following into Telnet (these commands will give you root access for now):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Power off your phone by pressing send/hangup&menu together when its done.
Now you have the modified recovery and root !
Now that you have root and stuff, you will want to apply "Hard SPL" to your phone. HardSPL includes engineer SPL and is what will allow you to apply any rom image from any other regions
(like UK on US phones, UK on dutch and vice versa), create full backups of your phone, install the latest build from the Android source, enable usb on recovery mode, usually resurrect your phone if it is "bricked" and give you allways root and ability to flash another rom. Allows fastboot. Fastbooting of images allows the flashing of 1:1 images of system, data, boot, cache, pretty much everything.
You have already downloaded the file to your SD card, so now you can apply it.
-Start up in recovery mode by holding home and pressing power.
-You will now enter recovery mode. You should see an exclamation.
-If you do not see a menu on screen, press Alt-L to show the menu. It is supposed to show the modified recovery menu.
-select update from zip to apply the update.zip (hardspl) from the SD card.
-After the update is complete, hold Home and press Back to restart.
ok your G1 europe 1.6 or whatever version is now unlocked.
Installing your modded rom:
now download this europe rom (or here: link ) and this cyanogen update mod
(here are more roms: android-roms make sure you READ what is needed for this roms as these all need different recovey and things which are all nicely written to you in the help and readme files that come with it.)
- copy both files to root of the sd-card
- detach G1 and shut it down
- press home and start to get into the menu
- wipe device
- wipe cache
- install from zip the europe rom and do not reboot or anything else
- install cyanogenMod
- after it finish press both talk&hangup button and tap menu
- its probably giving the recovery menu . take out the battery and put it in and start the phone normally
- wait a long while for the phone to setup and i donno what the heck it needs to do but let it.
enjoy...
THnx to this greatfull forum-members like myself, moneytoo, amon ra, cyanogen, mark_v, persiansown who do this coz few others can and they have a sort of happy feeling doing it.

hi.
this isnt working for me. i used the hex editor to copy sections 00000000 to 00000170 from goldcard.img to my sdcard, then shut down and turned on phone with HOME+POWER, it "hangs" on phone with exclamation mark image. if i press home+power again i'm presented with default android recovery. i did put DREAMIMG.NBH to the root of my sdcard.
that means no confirming anything... what am i doing wrong then?

Seriously, use 1Clickroot.

maxisma said:
Seriously, use 1Clickroot.
Click to expand...
Click to collapse
1clickroot doesn't work with 1.6, does it?

greglord said:
1clickroot doesn't work with 1.6, does it?
Click to expand...
Click to collapse
The new should work in theory.. idk..

greglord said:
hi.
this isnt working for me. i used the hex editor to copy sections 00000000 to 00000170 from goldcard.img to my sdcard, then shut down and turned on phone with HOME+POWER, it "hangs" on phone with exclamation mark image. if i press home+power again i'm presented with default android recovery. i did put DREAMIMG.NBH to the root of my sdcard.
that means no confirming anything... what am i doing wrong then?
Click to expand...
Click to collapse
thats probably coz i mixed up buttons for starting the rainbowscreen updating mechanism.. sorry for that
i dont own or have a G1 so im not used to the button layout
edit: you can in that screen press Alt-L to get the menu , once u have the recovery.img installed it will change there to the menu of the modded recovery

maxisma said:
The new should work in theory.. idk..
Click to expand...
Click to collapse
i have no idea
but it might be handy to put a link to the file you mentioned instead of shouting it without researching the fact whether it works or not in 1.6

can anyone quickly tell me what the advantages of having the hard spl are? all iv done is rooted, (via 1 click) and then flashed cyanogens latest. radio was already up-to-date. just wondered if flashing new spl changes anything? many thanks

Hard SPL enables you to install roms like Hero or others that have a large "update".zip

bbuchacher said:
Hard SPL enables you to install roms like Hero or others that have a large "update".zip
Click to expand...
Click to collapse
Actually...The Haykuro SPL allows that...

Ace42 said:
Actually...The Haykuro SPL allows that...
Click to expand...
Click to collapse
Right. HardSPL (and DangerSPL) are something that allow fastboot. Fastbooting of images allows the flashing of 1:1 images of system, data, boot, cache, pretty much everything.
You should always have HardSPL/DangerSPL installed so you can fastboot a nandroid image as a worstcase scenario.
Jesus, the amount of noobiness is this thread is astounding.

persiansown said:
Right. HardSPL (and DangerSPL) are something that allow fastboot. Fastbooting of images allows the flashing of 1:1 images of system, data, boot, cache, pretty much everything.
You should always have HardSPL/DangerSPL installed so you can fastboot a nandroid image as a worstcase scenario.
Jesus, the amount of noobiness is this thread is astounding.
Click to expand...
Click to collapse
thnx for clearing that out
as i said i dont own a G1 i modded a friends one . so i dont know anything about this G1 but getting a new rom on it hehe.
i choose the hardspl as precaution and it seemed pretty stable from what i read.
i choose the 1.5 recovery as i thought it should have the same recovery image as the rom . dont know about that. it is the 1.4 recovery with some extras which are usefull, cant deny that.
i choose the rom as it seemed to be the most stable at the moment and allows thetering . this is why i needed to rom upgrade in the first place. second place that i just like modding and unlocking so that one can do everything with the device as it is yours anyway.

APEX.7 said:
can anyone quickly tell me what the advantages of having the hard spl are? all iv done is rooted, (via 1 click) and then flashed cyanogens latest. radio was already up-to-date. just wondered if flashing new spl changes anything? many thanks
Click to expand...
Click to collapse
it is allready answered in the how to ..

I can vouch for the OP tutorial working on the Australian Optus(Singtel) HTC Dreams wtih DRD20 build. Just waiting on that final epic long load up now.

Anacche said:
I can vouch for the OP tutorial working on the Australian Optus(Singtel) HTC Dreams wtih DRD20 build. Just waiting on that final epic long load up now.
Click to expand...
Click to collapse
I'm also G1 / 1.6 / DRD20 ... it's sounds good news for me ...

Hahahhahahh.....
this post should be named "The Most Difficult Way to Root your G1". How bout this.....downgrade to 1.5, DL one click root, and you're done.

Please help!!! Pleasee!
Do help me out on this one. I really can't seem to actually make my SD card into the gold card part. Whenever i plug it in the G1 or on a USB reader it tells me it's damage and needs to format.
i have two questions, Can i flash SPL first, then do a downgrade then flash recovery?
2nd : If i can't then can i flash recovery, flash spl then do a downgrade to RC7?
if so how do i flash my recovery?
DO HELP ME OUT PLEASEE! i've been on this for days!!!

I know that this is going to cause problems and fighting but, I cannot read this thread and not say anything in good conscious.
With the amount of errors and misinformation in this thread, perhaps the OP should leave the tutorials and how-to's to the people that actually HAVE a G1, have modified ROMs on their phone, and can support the questions that are asked in the thread.
Just my two cents, but I have a feeling that my words are supported judging from the general consensus of the previous posts.
~DM

DirectMatrix said:
I know that this is going to cause problems and fighting but, I cannot read this thread and not say anything in good conscious.
With the amount of errors and misinformation in this thread, perhaps the OP should leave the tutorials and how-to's to the people that actually HAVE a G1, have modified ROMs on their phone, and can support the questions that are asked in the thread.
Just my two cents, but I have a feeling that my words are supported judging from the general consensus of the previous posts.
~DM
Click to expand...
Click to collapse
Id have to second that, while I may not have many posts here on XDA,I've rooted and rebuilt and replaced screens from 7 G1's using the how to's and wiki's here on XDA(thanks devs). My thought is if it the current guides work we should prob stick with them unless someone else figures a better faster way.(ie;one click root). By the way,just wanna say,I've never charged anyone to root their phone or fix one. The knowledge I've gained I learned here,it wasn't something I developed and I think its wrong for people to take open knowledge they didn't come up with and charge other people for it like I've seen at some of these cell phone repair shops and on craigslist. If your gonna charge for the knowledge then pay the people you gained the knowledge from. Sorry for going off topic,just had to vent.

[Tutorial]Gigabyte G1305 / Orange Boston unlock and upgrade to 2.1 with CMLMod 1.5.1

I won't follow this thread anymore since i have sold my Boston. Anyway you can find more informations on htcmania.com (use google translate if you don't speak spanish)
EDIT: Upgrade to CMLMod 1.5 based on Muchtel ROM (below outdated CML 1.4)
With this tutorial you sould be able to unlock your Orange Boston (aka GigaByte G1305 Codfish, Apanda A60, WellcoM A88, Vibo A688, Cincinnati Bell Blaze f800, Commtiva Z71, Muchtel A1, Chinavision Excalibur, Motorola Greco, Nexian A890) and install CMLMod 1.5.1 (or 1.4) (by c.martinez.lozano) based on the ROM Muchtel 2.1 (eclair)​
Main advantages/disadvantages of CMLMod 1.5.1:
+Unlocked device (can use any SIM)
+Android 2.1 (Eclair)
+Root access with Superuser permissions
+Preinstalled programms and other features
+Easy SD partitioning and more features thanks to the new recovery
+Optional App2SD
+Processor speed adjustable in a range between 122 and 600MHz (with the possibility to set variable processor speed to have performance and longer battery life at the same time)
+Other features: 3 different launchers, flash light, setcpu, app2SD in one click, other preinstalled apps and tweaks
=Camera autofocus not working (like on stock ROM)
=Different UserInterface (in my opinion better, but that's subjective)
-You may loose the warranty on your device
-IMEI may change, to restore your original IMEI use the tutorial in my second post
-Languages not fully implemented (english is working fully, other languages settable with LocaleSwitch but not fully integrated )
Important!!! There may be the risk of damaging your phone in an irreparable way! Be aware also by installing this ROM you will loose your warranty! I do not take any responsability for the status of your device!​
I translated the tutorials on htcmania.com
All credits to c.martinez.lozano and pindemon from htcmania.com
​
Requirements
Hardware requirements:
-Phone model: Orange Boston (aka GigaByte G1305 Codfish, Apanda A60, WellcoM A88, Vibo A688, Cincinnati Bell Blaze f800, Commtiva Z71, Muchtel A1, Chinavision Excalibur, Motorola Greco, Nexian A890)
Edit: never seen a phone with so many different names!!!
-PC operating system: Windows XP 32 bit with SP3 and .NET Framework 2.0 and Winrar installed. Do not try with Windows XP working on a virtual machine!!!. Seems to work also on other Windows 32 bit operating. Does NOT work with Windows7 64 bit
-USB to micro USB cable (comes with the phone)
Software requirements For CMLMod 1.5.1:
Firmware Apanda A60 1.6.2
Firmware CMLMod 1.5.1 (this file already contains RUT 1.2.2 and the Phone drivers)
Additional for CMLMod 1.4 (Outdated):
RUT 1.2.2
Phone drivers
Firmware Apanda A60 2.1.9
Firmware CMLMod 1.4
Tools like adb, fastboot, etc
Ready to start! make sure you have enough battery left (at least 30%)
PART 1: Installing Apanda 1.6.2
Unpack the file Phone drivers on your desktop, or another place, but remember where
install RUT_V1_2_2. At the end you will have to reboot your pc. Reboot it
[*]Unpack the firmware 1.6.2 from the archive Hipi1_6_2.rar and you get a file ending with .nb0
[*]Execute RUT (the shortcut should be on your desktop). The program reminds us to prepare the USB cable and to have all the drivers installed. (For Vista or Seven 32 bit: right click on the RUT shortcut. on the menu select Properties-->Compatibility check Run this program in compatibility mode for: and select Windows XP (Service Pack 3) then press OK, then right click on the Rut shortcut and select Run as administrator)
[*]In the next window, look for the firmware just to unpacked (the .nb0 file) and select it.
[*]The instructions tell you what to do: disconnect the phone from your pc (if connected), remove and reinsert the battery to your phone
[*]Hold the camera button and the volume up button pressed and then press the power button to enter recovery menu.
[*]Once the recovery menu, connect your phone to your computer. If we never connected in recovery, it requires new drivers. They are in the inside the Folder we unpacked in step 1 inside the subfolder AndroidX32 for 32 bit operating systems (if it later asks for drivers again, select the same folder again).
[*]The installer will detect your phone. If not, enter the Device Manager and check that all devices are correctly installed.
[*]From now on, follow the on-screen instructions and wait, it takes a while.
[*]Once complete, we have the new firmware installed. Our phone will restart and (after a while) show us something in chinese. Touch the right on-screen button to select the english language.
[*]When your phone is on check your IMEI by dialing *#06# and then press the call button and write it down. Now check the IMEI written on the phone under the battery. If the IMEI is the same, go on with PART 2. if the IMEI changes, use the tutorial in my second post to restore the original IMEI.
Now your phone is unlocked but you have the chinese version of Android 1.6
PART 2: Installing CMLMod 1.5.1 (for CMLMod 1.4 skip this and go to PART 2 OLD)
Unpack the file CMLMod1.5.rar
Run the programm RUT once again, and select the newCMLMod1.5.nb0 file you got
Repeat the same steps described in PART 1: 6.-10.
Now on your phone open the main menu and then CMLMod1.5 to configure App2SD select Configurar Apps2sd, then partitionar SD the phone will restart into recovery mode.
Now select Partition sdcard, Partition SD and confirm with the Home key. set swap=0, Ext2=512 (is more then enough! you can also set less) and Confirm twice again.
Then press the back button and select APP2SD if you want your apps being installed on your sd in the Ext2 partition.
Attention!!! if after you want your apps being installed on your phone memory you have to make a Wipe, that means, your data will be lost.
Always in CMLMod1.5 you can select a launcher, install flash lite and install setcpu to set the speed of the phone's processor with the possibility of variable speed.
FINISH!!!​
PART 2 OLD: Installing Apanda 2.1.9
Unpack the file Hipi_2_1_9GMS.rar and you get the file Hipi2_1_9_GMS版.nb0. Rename this file in Hipi2_1_9_GMS.nb0 (the chinese symbol can make problems)
Run the programm RUT once again, and select the new Hipi2_1_9_GMS.nb0 file you got
Repeat the same steps described in PART 1: 6.-10.
Now you have the chinese version of Android 2.1
PART 3 OLD: Installing CMLMod 1.4
Unzip the archive CMLMod1.4zip copy the 3 files inside and paste them into the folder A688
Remove and reinsert the battery of your phone
Press and hold the volume down and the end call buttons and then press the power button
Now your phone starts in fastboot mode. Connect it to your PC
Press on your keyboard Windows+R in the pop up window type "cmd" and press Enter
In the dos window type "cd.." (off course without ") and press Enter, until you are in C:\
Now type "cd A688" Enter, then "fastboot getvar version" Enter. If the answer is "0:5" procede, otherwise control if your drivers are correctly installed
Type "fasboot -w" Enter
Type "fastboot flash system system.img" Enter (wait 2-3 min. until it finishes)
Type "fastboot reboot"

Tutorial: Restore your original IMEI
Wrong IMEI seems to lead to a lot of different strange problems while using the phone. So if your IMEI changed after flashing an other ROM it might be better to restore the original one.
All Credits to c.martinez.lozano
Attention!!! this process is delicated!!! I have no responsability for any damages to your phone!​
Dowload this File: and Unpack it to "C:\IMEI"
Go into C:\IMEI and execute setup. This will install PSAS
Execute MadEdit (answer NO), in MadEdit click File-->Open and choose NVList.nvr and we see a lot of numbers
Scroll down until on the left grey side you see "000020C0" and on the same line in the white part you see the numbers ".. .. .. .. 1A 23 45 67 89 AB CD EF...." this is the BAD IMEI
Now open notepad (on your pc) and write down your correct IMEI (found under your battery) putting in front "A" and separing every 2 characters (E.g. if your IMEI is "324867523906130" write "A3 24 86 75 23 90 61 30") and now invert every coupe of letters (in this case you would have "3A 42 68 57 32 09 16 03") *NOTE: thanks to jhonburton for better example
In MadEdit instead of the BAD IMEI "1A 23 45 67 89 AB CD EF" write (replace it) the number you got (in this case "3A 42 68 57 32 09 16 03")
Save the file and close MadEdit
Disconnect from your PC and turn off your phone and restart it into Recovery mode (Camera+Vol. up+Power). Reconnect it to your PC and if necessary install the drivers
Run PSAS (you installed it before) and choose Hardware Forensics-->Use Mobile Ports
Right to Serial Com Port select COM? - Smartphone 2009 Wireless USB Moden. The ? stands for a number. So very important!!! remember for Example if ?=3, remember COM3
Go to the tab Codes (QC) and click on Send SPC
Go to the tab Dialog Port (QC) and on the second drop down menu left to the button Lets go select Restore NVItems (Binary) and then press Lets go
Select the NVList.nrv (we have changed before) and click Open
IMPORTANT Once the process is complete, closed PSAS
Download and install QPST
Launch QPST Configuration
Click on the tab Ports and select Add New Port... and there you write the COM? port you had to remember before (in my example write "COM3") and click OK
In the tab Active Phones now you should see your phone. If not something went wrong.
Click on Start Clients-->SERVICE PROGRAMMING
A window with our phone will pop up. We select OK
Select Load from file and choose the 00000000_sp.qcn inside the folder c:\IMEI and click Open
Click Write to Phone and wait until your phone restarts, with your new IMEI.
Check your IMEI again by dialing *#06# now it should be correct
If your IMEI is still wrong, check accurately if you did everything right (correct number in NRV file etc etc...) if nothing helps procede with following steps:
Turn on the phone in download mode ( Hang up + Vol. Up + Power) and flash Apanda 1.6.2 again
Repeat all the steps of the Tutorial to restore your IMEI
If this didn't help install Apanda 1.6.1 always with the phone in download mode
Repeat all the steps of the Tutorial to restore your IMEI
If you still have problems, try to find another PC with WindowsXP SP3 32bit where you can try again.
Sooner or later you will be able to get you IMEI right (i think so)

thanx a ton suriya I've unlocked my blaze f800

You forget to explain how to use app2sd on CMLMod1.4
Thank's about your translate!!.
Sorry about my bad english

thanks alot. really good tutorial!
i didnt encounter any problems at all, not even those specified by you in the tutorial. as for the underclocked cpu, i see that as an advantage: this android version is faster with lower cpu frequency then the original one (at least for me), and thus, less battery is consumed.
if u dont care about ur phone's warranty (i dont), i really recommend this upgrade.
so far seems stable, but the bug when u place a call and u don't here ringing, persists.
Thanks alot, again!

Is it possible to flash the phone with this room using ROM Manager?
And if following your method do we have to do PART1 of the tutorial? i allready have my phone unlocked and have Android 1.6 for example.
thanks!

I have problem with Imei. After flash it is chaged. And i use this tutorial for restore imei but it didn´t work and my imei is still different thet under battery. And i have problem whit wifi. Maybe bad IMEI is reason for don´t working Wifi
Sorry for my poor english

c.martinez.lozano said:
You forget to explain how to use app2sd on CMLMod1.4
Click to expand...
Click to collapse
I will do as soon as i have my sd (i think it will arrive this week) and i will also translate how to bring it back to 600MHz. By the way, THANKS TO YOU!!!!
floroiu.andrew said:
but the bug when u place a call and u don't here ringing, persists.
Click to expand...
Click to collapse
Explain me better. Do you mean, when you call someone you don't hear this "tuuut-tuuut"? cause if it's that i don't have this bug
by the way if you didn't read it look here, about battery optimization.
nuno_mdj said:
Is it possible to flash the phone with this room using ROM Manager?
And if following your method do we have to do PART1 of the tutorial?
Click to expand...
Click to collapse
ROM Manager doesn't support our phone as far as i know.
I wouldn't skip that part! seems strange but i think i have red that people got trouble if skipping PART 1
gru15 said:
I have problem with Imei. Maybe bad IMEI is reason for don´t working Wifi
Click to expand...
Click to collapse
Try once again step by step. start with PART 1 again. be careful you don't forget anything. Use this version of QPST and a new .nrv file this time. if this does not help we will find a solution together looking step by step (in case c.martinez.lozano is an expert).
By the way wich kind of phone do you have, and from wich country? And wich operating system has your computer?

So i have Orange Boston from Slovakia and i am using WIN vista 32-bit. I read original post on htcmania but it is spanish so i dont understand everything, but some people write there that this tutorial must be use whe RUT is in download mode while i am installing 1.6.2 rom. I don´t know when is RUT in download mode...
And your qpst want serail !!!!

gru15 said:
So i have Orange Boston from Slovakia and i am using WIN vista 32-bit. I read original post on htcmania but it is spanish so i dont understand everything, but some people write there that this tutorial must be use whe RUT is in download mode while i am installing 1.6.2 rom. I don´t know when is RUT in download mode...
And your qpst want serail !!!!
Click to expand...
Click to collapse
Sorry i replaced the qpst links.
ok... not download mode but compatibility mode.
you right click on tha RUT shortcut. on the menu select Properties-->Compatibility check Run this program in compatibility mode for: and select Windows XP (Service Pack 3) then press OK
Now right click on the RUT shortcut again and select Run as administrator.
Try that way. then try that imei stuff again!
cheers
P.S. Anyway if you know where you can use an XP (32 bit) with SP3 i am confident everything will work if you do it step by step

ok IMEI is correct now. But i have a problem with wifi. On any 2.1 rom cant find any network but when i flash 1.6.2 it find. So i dont know where is a problem.

gru15 said:
ok IMEI is correct now. But i have a problem with wifi. On any 2.1 rom cant find any network but when i flash 1.6.2 it find. So i dont know where is a problem.
Click to expand...
Click to collapse
Ok good you restored your IMEI. About WIFI. Best thing is if you ask on htcmania because i don't know what to do.
When you have an answer and corrected your problem please post it here. So i add it to first post cuz other people may have the same issue.

CMLMod 1.5 with some nice new features is on the way!!!

there is in italian version too?

gru15 said:
So i have Orange Boston from Slovakia and i am using WIN vista 32-bit. I read original post on htcmania but it is spanish so i dont understand everything, but some people write there that this tutorial must be use whe RUT is in download mode while i am installing 1.6.2 rom. I don´t know when is RUT in download mode...
And your qpst want serail !!!!
Click to expand...
Click to collapse
dont remember exactly, but in some parts of the tutorial, you have to "Run as administrator" the given applications (RUT, etc). i used win7 32bit, and no problem.

ady_uaic said:
there is in italian version too?
Click to expand...
Click to collapse
No. But with LocaleSwitch you can select italian then most things are in italian. Settings (impostazioni) is still in English, and no italian dictionary on the stock keyboard. you can install another keyboard, to solve this. But wait for CML 1.5. Maybe some better.
floroiu.andrew said:
dont remember exactly, but in some parts of the tutorial, you have to "Run as administrator" the given applications (RUT, etc). i used win7 32bit, and no problem.
Click to expand...
Click to collapse
Yeah thanks for your confirmation. I wrote it on the first page.
cheers suriya

oki..thx for info. but, what does exactly that locale switch app? what are the changes?

Please add Nexian A890 (Indonesian version of this device) on the list too. Here, in Indonesia, we can bring it to the official service center to upgrade it.

ady_uaic said:
oki..thx for info. but, what does exactly that locale switch app? what are the changes?
Click to expand...
Click to collapse
with it you can select languages wich are present in the phone. Italian is also partially present. most things then are in italian. except the settings menu, the camera menu, the date on the lockscreen and maybe something else
minori_aoi said:
Please add Nexian A890 (Indonesian version of this device) on the list too.
Click to expand...
Click to collapse
thanks mate. added

It worked on my Cincinnati bell Blaze,but I can't get the IMEI to change. all works but
the Internet connection, WIFI does work.
Thanks for the 2.1 Upgrade

[UPDATE: 2011.11.16] [RECOVERY] [ROOT] G2x Gingerbread 2.3.3 Stock using Linux

Follow the chronological order of the listed items...
1. Several things to KNOW and DO BEFORE starting:
- this is for Linux (that is your computer OS is Linux based) users ONLY!
- Mac (though UNIX based) and Windows users GO somewhere else!
- this REPLACES your stock recovery w/ clockwork recovery; this is NOT the same as installing rom manager from the market, which won't work on your "unrooted" phone anyway, go ahead try it
- this does NOT root your phone by itself, you need to follow all the directions
- be sure your battery is FULLY CHARGED, even though you'll be removing it for part of the directions
- COPY a rom of your choice to your external sd (ONLY if using ctso's procedure or using the updated clockwork recovery zip file labeled "external," otherwise copy the rom to the internal sd); I recommend CyanogenMod 7.1.0.1 Stable
- follow the procedure listed in #2
2. Procedure for replacing your stock recovery w/ clockwork recovery:
- SEE UPDATE BELOW as this flashes clockwork recovery v3.0.2.4
***********************************************************************************************************************************
The following procedure was provided by xda member ctso...many thanks to him!
***********************************************************************************************************************************
http://forum.xda-developers.com/showthread.php?t=1044326&highlight=recovery
***********************************************************************************************************************************
Again, thanks to ctso for the UNIX terminal bash script! Be sure to THANK him yourself!
***********************************************************************************************************************************
UPDATE:
- download one of the attached clockwork recovery zip files (they include nvflash) below INSTEAD of ctso's "nvflash-recovery.tgz" to have the newer clockwork v4.0.1.5
- use the "external" file to have clockwork read files from your external sd card
- OR use the "internal" file to have clockwork read files from your internal sd card
- THANKS to krylon360 for the updated clockwork
3. Several things to DO AFTER your DONE with the procedure by ctso above:
- reboot device into clockwork recovery by holding the POWER button and VOL DOWN button, let go when you see the word "ANDROID" in the mid-left, upper portion of the screen (occurs after the LG logo appears)
****I can't stress the next 4 items in bold red enough BEFORE proceeding to load your new rom****
***If you don't do this, you're a fool***
- be sure to "wipe data/factory reset"
- be sure to "wipe cache partition"
- be sure to go to "mounts and storage" then "format /system" then "format /data" then "format /cache"
- be sure to go to "advanced" and "Wipe Dalvik Cache"
- NOW, you may INSTALL the rom you copied to your sd card in #1
- be patient! You may not get feedback that the rom is loading! Let it sit for ~10min.
- once finished the clockwork recovery menu will reappear
- be sure to go to "advanced" and "Fix Permissions"
- be sure your battery is FULLY CHARGED, go to "advanced" then "Wipe Battery Stats"
- your done; you now have "rooted" and "rom'ed" your device!
_____________________________________________________________________________________________
- I'm NOT responsible if you "BRICK" your phone
- If you don't understand what Linux is, you probably shouldn't be elevating the user privileges by "rooting" a phone that runs the linux kernel
- Do as I say, not as I do
- If I'm coming across as an asshole, it's because I probably am; I'll try to be nicer next time
- Developers put in a lot of their time and talent into projects for us for free, be sure to THANK them and DONATE to them
_____________________________________________________________________________________________
- LG P999, Rooted, CyanogenMod v7.1.0.1 Stable
- HP dv7t w/ Debian Linux

interesting
but usability does it actually bring to the phone

navendugoyal said:
but usability does it actually bring to the phone
Click to expand...
Click to collapse
Endless ....

navendugoyal said:
but usability does it actually bring to the phone
Click to expand...
Click to collapse
If you have to ask, then you probably shouldn't be "rooting" your mobile.

navendugoyal said:
but usability does it actually bring to the phone
Click to expand...
Click to collapse
You obviously have never checked the G2x Development Forum... lol

I used to have a G2x that was preloaded with Froyo 2.2, but since then have swapped phones for a newer G2x that was preloaded with Gingerbread 2.3.3. Both phones were brand new when purchased. Using the Froyo model, I was easily able to root and flash customer recovery i.e., super one click and NVFlash, however with the preloaded Gingerbread model, neither option works. I understand that I am supposed to just NVFlash clockworkmod recovery and then flash a custom 2.3.3 rooted ROM, but during the battery pull and plugging in the device while holding VOL UP + VOL DOWN, I no longer get the SW lettering on the screen. I have the exact same APX drivers and NVFlash that worked perfectly on my Froyo based G2x. Did LG change something to not allow official preloaded 2.3.3 devices to recognize APX drivers? Is anyone else experiencing this issue from a brand new 2.3.3 based G2x?
---------- Post added at 02:43 AM ---------- Previous post was at 02:38 AM ----------
I only ask this because I went as far as installing Ubuntu OS to obtain the linux NVflash method to see if the drivers work under a different operating system. I then got stuck on ctso's description of "you should see device listed under "lspci." I typed in "lspci" into ubuntu's version of command prompt and did not see any android device connected. What am I supposed to be looking for exactly?

leonblade45 said:
I used to have a G2x that was preloaded with Froyo 2.2, but since then have swapped phones for a newer G2x that was preloaded with Gingerbread 2.3.3. Both phones were brand new when purchased. Using the Froyo model, I was easily able to root and flash customer recovery i.e., super one click and NVFlash, however with the preloaded Gingerbread model, neither option works. I understand that I am supposed to just NVFlash clockworkmod recovery and then flash a custom 2.3.3 rooted ROM, but during the battery pull and plugging in the device while holding VOL UP + VOL DOWN, I no longer get the SW lettering on the screen. I have the exact same APX drivers and NVFlash that worked perfectly on my Froyo based G2x. Did LG change something to not allow official preloaded 2.3.3 devices to recognize APX drivers? Is anyone else experiencing this issue from a brand new 2.3.3 based G2x?
---------- Post added at 02:43 AM ---------- Previous post was at 02:38 AM ----------
I only ask this because I went as far as installing Ubuntu OS to obtain the linux NVflash method to see if the drivers work under a different operating system. I then got stuck on ctso's description of "you should see device listed under "lspci." I typed in "lspci" into ubuntu's version of command prompt and did not see any android device connected. What am I supposed to be looking for exactly?
Click to expand...
Click to collapse
At that point it is not an Android device. It is an Nvidia APX device. If you have a Windows computer handy (friend or at work) just use the One-Click Recovery Flasher method.

Listen to me very carefully...
leonblade45 said:
I used to have a G2x that was preloaded with Froyo 2.2, but since then have swapped phones for a newer G2x that was preloaded with Gingerbread 2.3.3. Both phones were brand new when purchased. Using the Froyo model, I was easily able to root and flash customer recovery i.e., super one click and NVFlash, however with the preloaded Gingerbread model, neither option works. I understand that I am supposed to just NVFlash clockworkmod recovery and then flash a custom 2.3.3 rooted ROM, but during the battery pull and plugging in the device while holding VOL UP + VOL DOWN, I no longer get the SW lettering on the screen. I have the exact same APX drivers and NVFlash that worked perfectly on my Froyo based G2x. Did LG change something to not allow official preloaded 2.3.3 devices to recognize APX drivers? Is anyone else experiencing this issue from a brand new 2.3.3 based G2x?
---------- Post added at 02:43 AM ---------- Previous post was at 02:38 AM ----------
I only ask this because I went as far as installing Ubuntu OS to obtain the linux NVflash method to see if the drivers work under a different operating system. I then got stuck on ctso's description of "you should see device listed under "lspci." I typed in "lspci" into ubuntu's version of command prompt and did not see any android device connected. What am I supposed to be looking for exactly?
Click to expand...
Click to collapse
************************************************************************************************************
************************************************************************************************************
thank you, for a detailed question. i appreciate that. i am glad you understand the basic concept of replacing the stock recovery, this helps immensely.
************************************************************************************************************
read carefully and thoroughly!
************************************************************************************************************
************************************************************************************************************
First, some questions and a bit of information...
1. did you install ubuntu linux as a virtual machine (guest) (i.e. using vm ware or virtual box) while using another os as a host (main) os?
2. ...or did you erase your previous os and replace it with ubuntu linux?
3. ...or are you dual booting ubuntu linux w/ windows or some other os (i only ask this to AVOID confusion in any further communicae)?
4. for the rest of this discussion we will assume you are EITHER dual booting w/ a linux os OR you erased your previous os and replaced it w/ some flavor of linux; if we HAD assumed that you were "virtualizing" a linux guest os inside of a host system like windows, then the unix bash script that ctso wrote MAY NOT work b/c virtual systems (regardless if vm ware or oracle's vrtual box) sometimes fowl up, for lack of better explanation at this point, and may not be able to identify usb connected devices properly
Second, some information...
1. a linux os (i.e. linux mint, ubuntu, debian, cent os, fedora, arch, open suse, slackware etc., etc.) does NOT need drivers to communicate to your linux kernel mobile as windows does. the linux os communicates, so to speak, to the linux that is running in your mobile handset
2. windows needs apx drivers to translate, if you will, windows/dos speak into linux/unix speak; again, the apx drivers mean NOTHING to linux b/c it does NOT need them and further more CAN NOT use them as they are for windows based computers only
3. windows' super oneclick/nv flash will NOT work w/ ANY g2x that has stock gb on it, even though it did work w/ a g2x that has stock froyo; this may change in the future (if this has changed tell me; though the info is personally useless to me b/c i have ran linux since 1999)
Third, more information...
1. the unix command 'lspci', literally means "list all pci devices" in unix speak, which, to reinforce again, is NOT understood by windows (for the most part; though dos was formulated off the unix structure)
2. the 'lspci' command is used just so you can verify that your g2x is connected to your linux computer, nothing more; and it is NOT necessary for any of ctso's procedure, he's just being complete
3. if you typed 'lspci' into the linux/unix terminal (what windows users like to call a command prompt), you would NOT see 'g2x' or anything of that nature listed; you would see a listing such as '00:05.0 PCI bridge: blah blah' (just an example!) that would indicate your mobile device is connected
4. so, do NOT worry about 'lspci'
Fourth and finally, more information and hopefully, a solution...
1. now, let's move on to more lessons in linux
2. let's pretend you downloaded ctso's script "flash-recovery.sh," how do you use it?
3. remove your mobile's battery
4. hold down VOL UP + VOL DOWN
5. simutaneously, connect your g2x to your computer (remember it better be running linux for this to work!)
6. release VOL UP + VOL DOWN
7. nothing will happen on your mobile (no "updating" or anything) and nothing will happen on your computer running linux (no windows popping up, no devices found, nothing!)
8. at this point, you could type 'lspci' into the linux/unix terminal (what windows users like to call a command prompt), but you won't b/c you don't know what you're looking at anyway
9. now, open the linux/unix terminal (what windows users like to call a command prompt)
10. navigate, yes, navigate through the folders using the terminal to where you downloaded ctso's script "flash-recovery.sh"
11. let's pretend you have the script and the ACCOMPANYING FILES that you got from ctso in a folder named 'linux' on your desktop
12. when you opened the terminal, you saw something that looked like this...
"[email protected] ~ $" w/o the quotes
13. navigate to the desktop by typing...cd Desktop
[email protected] ~ $ "cd Desktop" w/o the quotes, the "D" in desktop is capitalized and no spaces after the $
14. navigate to the folder named 'linux' that has all the goodies, not just the bash script, that ctso gave us (you are NOT going to directly use these other files, but the bash script DEPENDS on them!)
[email protected] ~/Desktop $ "cd linux" w/o the quotes
15. now, your in the folder named 'linux'
[email protected] ~/Desktop/linux $
16. now what? you will type the following...sudo bash flash-recovery.sh
[email protected] ~/Desktop/linux $"sudo bash flash-recovery.sh" w/o the quotes
17. you will be prompted for your user password, type it and press enter!
18. your mobile's screen will magically light up and say, "updating" or "SW" or whatever
19. when the terminal says the recovery image was transferred successfully, disconnect the mobile from the computer's usb, regardless of the mobile still displaying "SW"/"updating"!
20. you're done
21. i'm exhausted
_____________________________________________________________________________
- I'm NOT responsible if you "BRICK" your phone
- If you don't understand what Linux is, you probably shouldn't be elevating the user privileges by "rooting" a phone that runs the linux kernel
- Developers put in a lot of their time and talent into projects for us for free, be sure to THANK them and DONATE to them
__________________________________________________ __________________________
- LG P999, Rooted, Gb 2.3.3 Tweaked v1.2.2 by Xboarder
- HP dv7t w/ Debian Linux

If windows didn't exist, it would be a better world...
leonblade45 said:
I used to have a G2x that was preloaded with Froyo 2.2, but since then have swapped phones for a newer G2x that was preloaded with Gingerbread 2.3.3. Both phones were brand new when purchased. Using the Froyo model, I was easily able to root and flash customer recovery i.e., super one click and NVFlash, however with the preloaded Gingerbread model, neither option works. I understand that I am supposed to just NVFlash clockworkmod recovery and then flash a custom 2.3.3 rooted ROM, but during the battery pull and plugging in the device while holding VOL UP + VOL DOWN, I no longer get the SW lettering on the screen. I have the exact same APX drivers and NVFlash that worked perfectly on my Froyo based G2x. Did LG change something to not allow official preloaded 2.3.3 devices to recognize APX drivers? Is anyone else experiencing this issue from a brand new 2.3.3 based G2x?
---------- Post added at 02:43 AM ---------- Previous post was at 02:38 AM ----------
I only ask this because I went as far as installing Ubuntu OS to obtain the linux NVflash method to see if the drivers work under a different operating system. I then got stuck on ctso's description of "you should see device listed under "lspci." I typed in "lspci" into ubuntu's version of command prompt and did not see any android device connected. What am I supposed to be looking for exactly?
Click to expand...
Click to collapse
****************************************************************************************************************
jboxer said:
At that point it is not an Android device. It is an Nvidia APX device. If you have a Windows computer handy (friend or at work) just use the One-Click Recovery Flasher method.
Click to expand...
Click to collapse
****************************************************************************************************************
jboxer, I appreciate you trying to help leonblade45 , but...
****************************************************************************************************************
You are confusing the issue.
- apx drivers are NOT needed in a linux based os (i.e. ubuntu linux) and WILL NOT work in linux
- leonblade is trying to use linux, but is getting confused w/ windows knowledge he may have regarding drivers and why they are needed for windows
- windows' oneclick (as far as i know; if i'm wrong, correct me) is NOT currently able to flash the recovery onto any g2x running STOCK GB
- PLEASE SEE MY POST BELOW leonblade's QUESTION
- thank you

linux_user9 said:
If you have to ask, then you probably shouldn't be "rooting" your mobile.
Click to expand...
Click to collapse
Or he could be new and getting a feel for rooting.
Why do you people need to say rude things like this?

Oh well...
blestsol said:
Or he could be new and getting a feel for rooting.
Why do you people need to say rude things like this?
Click to expand...
Click to collapse
****************************************************************************************************************
Mr. bletsol:
- remember "rooting" or granting super user access to the linux kernel is NOT BENIGN
- Aesthetics of the mobile is NOT a good enough reason to "root", functionality/usability is understandable
- I'll say it until I'm blue in the face (which seems to be, what it takes when trying to educate windows and mac users): If you don't understand what Linux is, you probably shouldn't be elevating the user privileges by "rooting" a phone that runs the linux kernel

I see. Thanks linux_user9, your explanation is much more clear than the instructions provided by ctso. This has been a great help. I actually did end up partitioning my drive and fulling installing Ubuntu along side the Windows 7 OS. The only reason I got rid of my originally rooted G2x was because I could not escape the plagued GPS-lock problems from installing a CM7-based rom. I bought the preloaded 2.3.3 G2x in hopes of rooting it and installing an OTA 2.3.3 based rom right from the get go.

Glad to hear it!
leonblade45 said:
I see. Thanks linux_user9, your explanation is much more clear than the instructions provided by ctso. This has been a great help. I actually did end up partitioning my drive and fulling installing Ubuntu along side the Windows 7 OS. The only reason I got rid of my originally rooted G2x was because I could not escape the plagued GPS-lock problems from installing a CM7-based rom. I bought the preloaded 2.3.3 G2x in hopes of rooting it and installing an OTA 2.3.3 based rom right from the get go.
Click to expand...
Click to collapse
I'm glad to hear that the instructions were of use, please forgive me if I came across stern or condescending. I am also glad to hear you are exploring the world of linux and that you're one-step closer to completely replacing windows!
linux_user9

leonblade45 said:
I see. Thanks linux_user9, your explanation is much more clear than the instructions provided by ctso. This has been a great help. I actually did end up partitioning my drive and fulling installing Ubuntu along side the Windows 7 OS. The only reason I got rid of my originally rooted G2x was because I could not escape the plagued GPS-lock problems from installing a CM7-based rom. I bought the preloaded 2.3.3 G2x in hopes of rooting it and installing an OTA 2.3.3 based rom right from the get go.
Click to expand...
Click to collapse
Yeah, I did that dual-booting a year ago as well. And then, after 2-3 weeks, I switched. I've been Windoze-free for a year now.
(lol... sounds like out of rehab)

G2X Root with linux
WINNING!!!
Ubuntu lucid. Worked perfectly.

softbrick
So I have an lg g2x running gingerbread 2.3.3 and I went through this procedure. Everything seemed to work as described except that the phone now will not boot. I get to the LG screen but then the buttons just blink and shuts down.
I must have missed a step somewhere, though I am not sure where that might have happened. In any case, I would like to get this working or, at the very least, get the phone back and working.
Any advice is appreciated.

Soft-Brick
cyberlync said:
So I have an lg g2x running gingerbread 2.3.3 and I went through this procedure. Everything seemed to work as described except that the phone now will not boot. I get to the LG screen but then the buttons just blink and shuts down.
I must have missed a step somewhere, though I am not sure where that might have happened. In any case, I would like to get this working or, at the very least, get the phone back and working.
Any advice is appreciated.
Click to expand...
Click to collapse
2011.12.05
cyberlync:
I am sorry to hear that you're having issues with the procedure. Let me first say that I didn't receive your message until yesterday, as I choose to receive only weekly updates via email on posts that I create.
If your issue is resolved, let me know. What you're describing in your post is what is called a "boot loop," if I'm understanding you correctly.
PLEASE READ ALL OF THE INSTRUCTIONS (I know that I can be long-winded)
First, several questions for you:
1. What Linux distro are you using (i.e. Debian, Linux Mint, LMDE, Ubuntu, CentOS, etc.)? Also, what version of Linux distro are you using (i.e. Debian 6.0, Linux Mint 11, etc.) Hopefully, you're not running Linux as a VM in a Mac or Windows host.
2. What Android distro or "rom" did you decide to use (i.e. CyanogenMod, Bionix, EDT, WeaponG2x, Tsugi, etc.)? You may need to download a "fresh" copy of the "rom" in case it is damaged, corrupt or incomplete. Again, I highly recommend Cyanogenmod 7.1.0.1 Stable (Don't forget to install "gapps" if you want Google Apps in CM7)
3. With your mobile off, are you able to boot into Clockwork Recovery by HOLDING DOWN THE VOL DOWN KEY and the POWER BUTTON simutaneously, THEN RELEASING them after the initial splash screen has displayed (the splash screen image will depend on which Android distro you're using; i.e. the LG logo.)?
4. Which Clockwork Recovery are you using, that is, what is the version number (if you don't know, tell me the color that the text is appearing; i.e. orange, red, blue, etc.)? Did you use ctso's recovery flash image or one of the updated attached one's that I provided, courtesy of krylon?
Second, there's GOOD NEWS if you can boot into Clockwork Recovery, the "fix" will be much quicker. Boot into Clockwork Recovery, then do the following:
1. Check to ensure that you have a copy of the "rom," that you downloaded onto your computer, on your mobile by going to (the power button is the enter key, vol keys allow scrolling up/down) --> install zip from sdcard > choose zip from sdcard; if you do NOT have this on the sdcard, all is NOT lost in the short-term provided you used the EXTERNAL recovery flash image from krylon that I provided or the ONLY recovery flash image from ctso. If you have used the INTERNAL recovery flash image (and depending on which "rom" you have chosen, as some have re-ordered the P999's mount points), make your life easier and REPEAT THE INSTRUCTIONS IN THE OP USING THE EXTERNAL IMAGE, otherwise you may need to download the Android Debugging Bridge (ADB) from the Google developer's website and I'll have to administer some Linux/UNIX command-line instructions. IF THIS IS THE CASE, I DON'T MIND HELPING YOU, BUT IT MAY BE EASIER TO CHAT IN ICQ OR ANOTHER ONLINE MESSAGING SERVICE.
2. PROCEED TO THE FOLLOWING IF YOU USED AN EXTERNAL RECOVERY IMAGE AND HAVE A "ROM" ON YOUR MOBILE'S SDCARD:
a) If you do NOT have a "rom" on your EXTERNAL SDCARD, connect your mobile via USB to your computer, boot into Clockwork Recovery, then go to: mounts and storage > mount USB storage, press enter (power button). Then copy the "rom" to your device's EXTERNAL sdcard (NOT THE 5.8GB SDCARD [IF APPEARING; IT MAY NOT DEPENDING ON WHICH "ROM" YOU'VE CHOSEN AS SOME RE-ORDER THE P999'S MOUNT POINTS], THAT IS YOUR INTERNAL SD); next > unmount USB storage. Safely Remove drive (right-click) via the Linux file manager.
b) NOW DO THE FOLLOWING FROM MY OP:
- be sure to "wipe data/factory reset"
- be sure to "wipe cache partition"
- be sure to go to "mounts and storage" then "format /system" then "format /data" then "format /cache"
- be sure to go to "advanced" and "Wipe Dalvik Cache"
- NOW, you may INSTALL the rom you copied to your sd card
- be patient! You may not get feedback that the rom is loading! Let it sit for ~10min.
- once finished the clockwork recovery menu will reappear
- be sure to go to "advanced" and "Fix Permissions"
- be sure your battery is FULLY CHARGED, go to "advanced" then "Wipe Battery Stats"
3. This should've fixed it.
More questions/problems? We'll work through it.
linux_user9

[Q] Samsung Focus 1.3 and Clean Rom with StraghtTalk

Well finally all my Samsung Focus's are off of AT&T contract and I am am moving them over to StraightTalk. The first one I moved three months ago to them still doesn't do MMS due to Samsung not exposing the settings and Samsung locking down the old way of breaking into the file system and dropping the XML.
I was thinking about flashing the Clean ROM 2.01a on one of the phones and then trying to get MMS working with that one under StraightTalk. Anyone have any recommendations for have made this work for the Samsung Focus?
Thanks...

I got it to work!
After a couple of house piecing together information from a few other posts here on XDA I the Focus 1.3 updated to Tango using clean ROM and was able to side load the StraghtTalk package and MMS works great. Only downside is that I had to erase the phone such is life. Now I only have to update two more phones.
Here is the steps that I took:
Get the files needed
Download clean ROM 2.01a from XDA Developers: http://forum.xda-developers.com/showthread.php?t=1528984
Get the Samsung drivers from XDA Developers: http://forum.xda-developers.com/showthread.php?t=961956
Get the new bootloader from XDA Developers: http://forum.xda-developers.com/showthread.php?p=22278269
Get the StaightTalk XAP from XDA Developers: http://forum.xda-developers.com/showpost.php?p=35737150&postcount=263
Windows Phone 7.1 SDK for Windows Phone Deployment: https://dev.windowsphone.com/en-us/downloadsdk
Get the installs going
Install the Samsung drivers
Install the windows phone SDK
Install New Bootloader
Put phone into upload mode: POWER + VOLUME UP + CAMERA
Launch the bootloader install: DFT_MLI_SAM1.exe
Follow instructions
Wait till successful and reboot phone
Install New ROM
Reset the data in phone: 'Settings' -> 'about' -> 'reset your phone' -> 'yes' -> 'yes'
At screen off hold VOLUME DOWN + CAMERA
Use the "Cancel" option on the screen: "<-" Back arrow
You should see the new bootloader screen
Plug phone into computer
Run DFT_WPI_SAM1.exe from Clean ROM directory
Follow instructions
Will take a long time to boot with the white bar advancing
Initial setup of phone "Microsoft account" etc. Also connect once to Zune to name phone as before
Phone is now ready to use leave plugged into computer and Zune running
Set Phone Up for StraightTalk
Phone will probably be pin locked so best to run the WindowsBreak from the phone: http://windowsphonehacker.com/windowbreak
Click "WindowBreak Me"
Tap on "windowbreak" A browser window should open up. Ignore it.
Launch Diagnostics on the phone Dial *#9908#
Select "windowbreak" from the dropdown list
Press Save and reboot the device
Make sure phone is still connected to Zune
Launch application deployment from sdk
Deploy the straghttalk XAP (rename from zip to xap) before deploying
Go to diagnostics and dial *#9908#
Select StraightTalk from drop down
Press Save and reboot phone.
Test a MMS and you should be all set

[Root] H901 - For Newbies!

None of the methods in this thread are my own work. I struggled with getting my phone rooted for a long time and spend 10s of hours on the process. I had never rooted before and was therefore unfamiliar with all the terms, unfamiliar with how to complete all the recommended checks to ensure one had the right model, etc. There were several helpful threads but most approach the subject with the assumption that one knows something about the process. In this post I lay out what worked for me in a step-by-step way and what you have to do to achieve my results.
#1 Ensure you have a H-901 motherboard and not the Korean F600 motherboard by checking the sticker, and checking “About Phone” -> “Hardware Info” -> “Model number” in settings. These must both be LG-H901…from what I can tell the community has only developed technique for the H-901 variant.
#2 Get a micro SD card and load it with Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 , and if you have Marshmallow or Lollipop and want Nougat (much better experience IMHO), load the files in this thread: https://forum.xda-developers.com/tmobile-lg-v10/development/h901-t-mobile-nougat-v30b-twrp-t3639203 And maybe this thread as well (read both and then decide): https://forum.xda-developers.com/tm.../h901-t-mobile-nougat-v30c-flashable-t3744648
#3 Ensure you have unlocked your bootloader. (apparently only for T-mobile LG v10s since other carriers lock the bootloader) The FWUL virtual machine root method will not work if you have not done so. This is an entire process in itself. The following 2 videos which show how to root android 6.0 or earlier (process will not work with Nougat, 7.0, since some fastboot commands are missing). https://youtu.be/OtXlokk6JkQ , https://youtu.be/PPLwFGxLQA4
Also, this thread may be helpful. https://forum.xda-developers.com/tm...t-mobile-bootloader-factory-unlocked-t3236224 , download the nexus root toolkit here for easy ADB command entry http://www.wugfresh.com/nrt/ —we will only use the “Advanced Utilities” -> ”Manual Input” -> ”Launch CMD Prompt”. When it prompts you to select a phone, select the first option and then for android version select Android *** Any. Don’t use any of the other commands because they are not configured for your device.
If you get a “waiting for device” error while attempting the fastboot oem unlock command in the above thread, see: https://forum.xda-developers.com/tmobile-g4/help/fastboot-waiting-device-t3489789 Great video which shows how to change drivers. You will need to do this, I found a number of drivers that were already on my PC from google and Samsung worked although I didn’t have the specific one mentioned in the above thread. Don’t be afraid to experiment… you can always try another driver. And don’t require it to be hardware compatible. Ignore the warning message: https://youtu.be/nQjg6ePnGAc
---------------------------------------------
NOW that you have your bootloader unlocked you can proceed to actually flash the TWRP image as per this thread: https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942
Notes before beginning:
-To enter download mode to begin: Plug a USB cable into your phone with your phone powered off, hold down on the Vol Up button and plug the USB cord into your computer. It should immediately boot into download mode. Exiting Download mode after flash: pull battery…no damage will be done.
-To enter recovery after flashing TWRP: power off the phone then hold both the down volume and power at the same time. When you see the black LG screen briefly release the power button and then press it again while not letting the volume down up. You will see a screen asking if you want to delete all user settings. Say YES (via the volume and power keys—no touch input). You will see a screen asking if you want to delete all user data. Say YES (the data is only deleted if TWRP loads successfully) You will briefly see the black LG bootup screen. TWRP or factory recovery will load. Or if you did not unlock your bootloader, it will say recovery is corrupted and cannot be trusted, and then boot normally without changing your settings or deleting files.
-Additional note: as of 7-23-18 some commands had changed:
From V20 forum, Brian (runningnak3d) has moved to gitlab.com. So instead of github.com, we have to use a new git repository that Brian created in gitlab.com.
cd
mv lglaf lglaf_BAK
git clone https://gitlab.com/runningnak3d/lglaf
cd lglaf
git pull
git checkout v10-miscwrte
There are additional comments in the thread. Some timeout errors may be solved by: 1 - Download the VirtualBox extension pack: https://download.virtualbox.org/vir..._VirtualBox_Extension_Pack-5.2.8.vbox-extpack
2 - Go to File / Preferences / Extensions / click the + and browse to where you downloaded it.
3 - Once installed, with the VM off, right click on the VM, and go to settings. Click on USB, and pick USB 3.0. If your machine doesn't have a USB 3 port, pick 2.0.
But frankly, simply up arrow after a timeout error to load the last command on the command line and hit enter again. Simply keep doing this until it works. You know it works because no dialog appears for several minutes before informing one of success.
**Upgrade to Nougat after Flashing TWRP and booting to Recovery steps: (I did a full wipe as suggested by this thread: https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594 before flashing the v30b upgrade then full Nougat zip, and then flashing Magisk. I flashed the 3 zips sequentially. I was afraid Nougat would not boot successfully because the zip files are less than 2 gb combined but success! You may want to also flash the 30c upgrade before flashing Magisk for a total of 4 zip flashes. I did not try this. However doing all this means no backups are done so if there is a problem you may have to flash a KDZ with the LG UP tool (don’t ask me how).
As a final note, I cannot answer specific questions about the various processes provided or errors you may encounter that I have not listed in this write up since I have not experienced them. A bit of research on your part may be required, but this post should provide you with a huge head start compared to where I started. Good luck!

Methods to get unlimited mobile hotspot, very useful if you're on the $50 MetroPCs (owned by T-mobile) unlimited plan. All you $70 T-mobile plan suckazzz! https://forum.xda-developers.com/tm...ited-tetherting-hotspot-t3825144#post77249285
I would actually recommend using a USB tether client and forgoing root access if tethering is your only objective and you are trying to be efficient with your time. However, with root you can install all these cool apps!: https://www.digitaltrends.com/mobile/best-android-root-apps/
The following caught my eye:
-Rec: screen record
-liveboot: boot animation (does not work with Magisk)
-Servicely: checks to see which apps are using a lot of battery and lets you suppress them
-Adblock Plus
-Titanium backup: very powerful phone backup application & bloatware remover look into for quickly switching over to a different lg v10
-Greenify: put apps into hibernation
-System tuner: get lots of info about you phone but be careful making changes
-ES file explorer: dig into the android system
-Disk digger: recovers deleted files (photos only?)