[RADIO/GUIDE/TWEAK]Radio JK1,JK8,KB1,KB2,KB3,KD1,KF1 & UCKD1,KE1,KF1 with HSPDA Tweak
[RADIO/GUIDE] Radio JK1, JK8, KB1, KB2, KB3, KD1, KF1, UCKD1, UCKE1 and UCKF1
Radio Flash (Fastboot&ADB)
Radio Flash (Fastboot&ADB)
Click to expand...
Click to collapse
Radio for I9020a/I9020t/I9023
Radio JK1/Radio JK8
Radio KB1
Radio KB3
Radio KD1
Radio KF1
Radio KI1 <<= I9020a DO NOT FLASH!
Click to expand...
Click to collapse
Radio for I9020a ONLY
Radio UCKB2
Radio UCKD1
Radio UCKE1
Radio UCKF1
Radio UCKF1 (Version 2)
Radio UCKJ1 (LASTEST)
Click to expand...
Click to collapse
Radio for Korea Carrier ONLY
Radio KC1
Click to expand...
Click to collapse
Radio Patch for I9020T ONLY
Radio KD1 =>> KF1
Click to expand...
Click to collapse
For those who has IMEI problems, please CLICK HERE!!
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What to know before you start flashing radio?
1. Back up your EFS folder. Click here for the method of backup.
2. Check your phone MODEL (I9020A, I9020T & I9023).
3. Flash the CORRECT RADIO according to your phone model.
4. OPTIONAL After download the radio file, check your downloaded file md5 sum. Click here for the md5 sum
5. After flashing, check your radio baseband at Setting > About Phone > Baseband.
Want to have higher 3G speed connection? Use HSDPA Tweak
Lost your 3G Connection? Here's the solution:How to retrieve 3G connection?
Got question to ask? Read FAQ first
Want to Back up your EFS folder? Click here for the method of backup.
Click to expand...
Click to collapse
Method of Flashing Radio
Method 1 (ClockWorkMod Recovery):
1, Reboot into recovery,
2, Select "select zip from SD card"
3, Locate where your radio file is
4, Select it and "yes"
5, Wait for it to reboot and you're done!
Method 2 (FASTBOOT + ADB):
(FOR WINDOWS Operation System only, NOT FOR MAC OS)
Part 1
1, Download Radio Flash (Fastboot&ADB).zip
2, Extract the folder to Desktop.
3, Open the extracted flash folder.
Part 2
1, Download the radio.zip file you would like to flash from the link above/attachment below.
2, Extract it to Desktop.
3, Copy the "radio.img" file from the folder and paste it into the Radio Flash Folder you had extracted in PART 1.
Part 3
1, Connect your Nexus S to computer (USB Debugging turn on, SD card mount turn off)
2, Double left click the "START HERE.bat" and command prompt window will open/run.
3, Type: "adb reboot bootloader". (The adb reboot bootloader will take the device directly to fastboot) OR boot the phone to bootloader by pressing the volume up key with power key at the same time.
4, Once your phone has rebooted in to bootloader screen, type "fastboot devices" to ensure your device is detected.
5, After confirm your device is detected with serial number, type "fastboot flash radio radio.img".
6, Once its done, type "fastboot reboot".
7, You're good to go
Method 3 (ROM MANAGER):
(Not recommended , but still if method 2 and 3 cant work, use this AT YOUR OWN RISK)
1, Install Rom Manager from Market.
2, Open Rom Manager and select "Install rom from SD".
3, Locate the file where you put the Radio file downloaded.
4, Flash it with Dalvik Cache wipe (Data and Cache wipe NOT required)
5, Enjoy it
Click to expand...
Click to collapse
HSDPA Tweak (Higher/Faster Data Connection Speed)
Method 1 (Via Root Explorer):
Code:
[SIZE="3"]1, Open "Root Explorer" and mount R/W.
2, Go to "system" and you will find there is a file name "build.prop".
3, Right click (By holding at the file) and there is menu pop out.
4, Scroll down and select edit in Text Editor.
5, Type in those few line of words below into the last line of the text.
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hsdpa.category=16
ro.ril.hsupa.category=8
6, Save the file and reboot your phone TWICE.[/SIZE]
Method 2 (Via ADB and USB debugging):
Code:
[SIZE="3"]Part 1
1, Download the Radio Flash (Fastboot&ADB).zip from above.
2, Extract the folder to Desktop.
3, Open the extracted flash folder.
Part 2
1, Connect your Nexus S to computer (USB Debugging turn on, SD card mount turn off)
2, Double left click the "START HERE.bat" and command prompt window will open/run.
3, Type: "adb pull /system/build.prop" and DO NOT close the command prompt.
4, In that folder, you will now see a file name "build.prop"
5, Open with notepad/text editor and add in these lined of code. (Copy and paste)
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hsdpa.category=16
ro.ril.hsupa.category=8
6, Then save the file.
7, Type in "adb remount" in the command prompt.
8, Type in "adb push build.prop /system/build.prop" in the command prompt.
9, Reboot your phone TWICE and it should be good to go.[/SIZE]
For those who want to know what those lines means, click here
Click to expand...
Click to collapse
FAQ
Click the word "FAQ" above to go to FAQ section.
Disclaimer: I assume you will have the knowledge regarding Rado (Baseband) to flash this radio update, I shall not be liable for anything that happen to your phone, including the procedure and method.
Everything was tested on my phone, not every phone is the same
Note: Extras credit to steve.garon, soniko, iamxeph , sheek360, BrainMaster and others who provided me the radio and answer
Thanks...
Still can't figure out why I get only 3G-UMTS (instead of HSDPA) with the KD1 baseband.
KB3 works fine.
Radio MD5 Sum
How to verify your MD5 sum?
1. Download this MD5 Sum Checker
2. Extract it to desktop.
3. Open the md5.exe
4. Copy the md5 sum at below and go back to the md5.exe
5. Click "browse" and select your downloaded file.
6. Check complete
Click to expand...
Click to collapse
Legend:
The 1st MD5 sum is for the ZIP file of the radio.
The 2nd MD5 sum below the word "RADIO" is for the radio.img inside the zip file.
XXJK8-radio-nexuss-unsigned
62C574774252E7FDA93845E4C61AD704
Radio.img
642E353E6E180FB0C48491FECD80079B
Click to expand...
Click to collapse
XXJK8-V1-radio-nexuss-unsigned
869016540339302EE646ECBA81080637
Radio.img
642E353E6E180FB0C48491FECD80079B
Click to expand...
Click to collapse
XXKB1-GRI40-radio-nexuss-unsigned
4805C255F10EEF8B1BD54AA2D27BC30E
Radio.img
942C7F6339E6ADA5A58CF656C3F1FD4A
Click to expand...
Click to collapse
Radio Nexus S [XXKB3]
4E9C9CF4D6470BE800E00F8508B9C175
Radio.img
EBC55CCF390A9C310F4F3E8B6F178E59
Click to expand...
Click to collapse
XXKD1-GRJ22-radio-nexuss-unsigned
57659F04148EBFA849EF523544F2A3DD
Radio.img
9E136A81C2D67648BB7E6642A7C805D5
Click to expand...
Click to collapse
XXKF1-radio-nexuss-signed
365270BE137EED7DCA351386A8CDDEB9
Radio.img
9E0E2086FBC5ADCFF88E6CA0BFE2D0B8
Click to expand...
Click to collapse
UCKD1-GRJ22-radio-nexuss-unsigned-sgaron
6BCA6A970E72424D55546CA484DF431A
Radio.img
2106935507A3C874D0EEFC5DF6AB60BF
Click to expand...
Click to collapse
UCKE1-GRJ22-radio-nexuss-unsigned
E37672AD207DFA0A565EAA8C12CA5402
Radio.img
705AC305D5A0131D26562A2065485B87
Click to expand...
Click to collapse
UCKF1-radio-nexuss-unsigned
B8E70F9245CF01DB10BF13870D1E341B
Radio.img
07CD2DD58418877BEA268F877931F886
Click to expand...
Click to collapse
XXKB2-radio-nexuss-unsigned
7CA2DC12E00D592099C123FF057BE995
Radio.img
4E926FDF96A2350C85604B1A00009DC5
Click to expand...
Click to collapse
XXKC1-radio-nexuss-unsigned
3D6745E0F5E55443EC1CB7CF01D99A36
Radio.img
4BCC117E9248E39FB2A0D800D072CC7C
Click to expand...
Click to collapse
Radio Attachment 2
I'm currently using KB3. I get good network at home but poor at work. KD1 seemed to give me the opposite!
Is one of these radios generally better for the UK?
How to retrieve 3G Data Connection
Method 1:
Code:
1. Go to Dialer. Dial *#*#4636#*#*
2. Go to Phone information. Choose the preferred network to
"GSM Auto PRL" or "CDMA Auto PRL" or whatever you have.
3. Scroll down, deactivate and activate Phone Radio.
4. Press Menu button.
5. Select Phone frequency, then choose your country.
6. In the previous menu push the Home button to go back to Homescreen.
7. Reboot.
[I](By Brainmaster)[/I]
Method 2:
(Advise: Before you play with it, please back up it. Click here for the method of backup.)
Code:
1. Use "Root Explorer" and navigate to [B]/efs[/B] directory
2. Mount "R/W"
3. Cut these three files [B]nv_data.bin[/B] , [B]nv_data.bin.md5[/B] and [B]nv.log[/B]
4. Paste it at the ROOT of the SD Card.
5. Reboot your phone and you will have your 3G connection back.
[I](By alexwbaule)[/I]
[/QUOTE][/SIZE]
Click to expand...
Click to collapse
window7 said:
Generally, for Australia, KD1 is better
Not sure for UK
Anyone from UK can give me some feedback?
Click to expand...
Click to collapse
I personally find kb3 slightly better in the uk, but not by much. Both radios offer good reception on Vodafone.
Sent from my Nexus S using XDA App
KB3 works on i9020a! Just flashed it last night.
I would not recommend flashing radio's with Rom Manager.
Not flashing it properly might cause some serious problems.
KD1 only allowed me a UTMS connection on my 9020A, just flashed this KB3 and hack to HSDPA . Much faster
Thank you.
sent from my next level bacon apparatus
Anyone in Spain tried it??
Impressions?
antiochasylum said:
KD1 only allowed me a UTMS connection on my 9020A, just flashed this KB3 and hack to HSDPA . Much faster
Thank you.
sent from my next level bacon apparatus
Click to expand...
Click to collapse
What hack for HSDPA?
I am using the KD1 radio on a I 9020t in the USA.
Sent from my Google Nexus S using XDA App
Im using KD1 in USA as well but would KB3 be better?
HSDPA Tweak (Higher/Faster Data Connection Speed)
Method 1 (Via Root Explorer):
Code:
[SIZE="3"]1, Open "Root Explorer" and mount R/W.
2, Go to "system" and you will find there is a file name "build.prop".
3, Right click (By holding at the file) and there is menu pop out.
4, Scroll down and select edit in Text Editor.
5, Type in those few line of words below into the last line of the text.
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hsdpa.category=16
ro.ril.hsupa.category=8
6, Save the file and reboot your phone TWICE.[/SIZE]
Method 2 (Via ADB and USB debugging):
Code:
[SIZE="3"]Part 1
1, Download the Radio Flash (Fastboot&ADB).zip from above.
2, Extract the folder to Desktop.
3, Open the extracted flash folder.
Part 2
1, Connect your Nexus S to computer (USB Debugging turn on, SD card mount turn off)
2, Double left click the "START HERE.bat" and command prompt window will open/run.
3, Type: "adb pull /system/build.prop" and DO NOT close the command prompt.
4, In that folder, you will now see a file name "build.prop"
5, Open with notepad/text editor and add in these lined of code. (Copy and paste)
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hsdpa.category=16
ro.ril.hsupa.category=8
6, Then save the file.
7, Type in "adb remount" in the command prompt.
8, Type in "adb push build.prop /system/build.prop" in the command prompt.
9, Reboot your phone TWICE and it should be good to go.[/SIZE]
For those who want to know what those lines means, click here
Click to expand...
Click to collapse
I used an earlier posted KD1 on my 9020a and its identical to KB3 to me. HSDPA all the way and the speedtests are about the same.
Reception flat out sucks on the NS though compared to other phones.
window7 said:
As to your question,
It is actually using HSDPA when it is able as sometimes it just wont show the H icon This is one of the glitch.
You tested both radio on your I9020A or I9020T?
Click to expand...
Click to collapse
No no, I have the H icon.. using CM7. so it's not that glitch... I'm checking on the About->Status settings anyway.
Tested both. KB3 is working great. KD1 - no HSDPA
liorry said:
No no, I have the H icon.. using CM7. so it's not that glitch... I'm checking on the About->Status settings anyway.
Tested both. KB3 is working great. KD1 - no HSDPA
Click to expand...
Click to collapse
I've noticed this as well. I was using KD1 for like a month or so, and then I saw this thread and noticed that I was getting HSDPA a lot more..I would on occasion see it on KD1 but not too often, even when I had damn good signal. I am happy using KB3 and the speeds are pretty damn good.
When I try and apply the KB3 to my 9020A I get a "Signature verification Failed" What am I missing?
Is KB3 the default radio that my stock Nexus S has?
Beako said:
Is KB3 the default radio that my stock Nexus S has?
Click to expand...
Click to collapse
The Robelus versions come with kb2.
Related
hi there,
so i am slightly new at this and have searched for hours and hours trying to find a consistent formula for rooting and installing my g1 to cyanogen mod 4.2 (or latest stable one, thus not cm 5). I seriously stayed up until 1am last night and now i am at work (started at 8) still searching.. I have used google, youtube, and several other cm sites. Basically the problem is there is not one guide and I am not sure if because I followed the CM wiki guide if i can switch because I am having problems with that one. So one question: does anyone know which is the latest and verifiably the best CM 4.latest guide to installing?
I am pretty sure i have rooted the phone because I successfully downgraded to RC29, the old school android OS. However when I try completing this guide: [cant put a URL in but the webpage title is: "G1 CM4.2 installation" and I already completed this wikiguide title: "Full Update Guide - G1/Dream Firmware to CyanogenMod" but it continues into the next page to install cm)
I get freaking stuck. I put all three files on my SD and when I try to push "Alt-A" there is not an option there for it, its not an option on my recovery mode menu. I tried putting the files back there after reformatting several times but still no 'alt-a' so I am stuck on step 5 because there is no option for step 5 on my recovery mode on the above web guide..
Does this mean I did not install something? should I try and install the ota radio, cm update, drc83 zip files separately (like load one on the sd card and install it, then reformat the sd card and then repeat with the other two files?) ? If so what order should I do that in??
Sorry I suck and have not been able to find these answers, there are just a plethora of guides and I am not confident in my modding to start deviating away from the wiki guide in case I brick my beautiful g1..
thanks so much, this has been a huge headache for me.. i literally spent 4 hours yesterday trying to get to this step.. aww...
At Step 5 select "apply any zip from sd" in Recovery.
Select "DRC83_base_defanged.zip" on your SD.
Press Home to confirm flashing.
Then select "update-cm-4.2.x-signed.zip" on your SD to flash CyanogenMod.
After everything is completed reboot your Phone normally.
Edit:
Here is the Link to the Tutorial.
zerocoolriddler said:
At Step 5 select "apply any zip from sd" in Recovery.
.
Click to expand...
Click to collapse
Yup you hit the nail on the head. Sorry I must not have been too clear on what was I was saying earlier. That is exactly the problem, you see I would select that in recovery mode, But "apply any zip from SD" is not there! Did I load some file wrong??
It only gives me:
Android system recovery utility
E: Can't open /cache/recovery/command
Home+Back - reboot system now
ALt+L - toggle log text display
Alt+S - apply sd:update.zip
Alt+W - wipe data/factory reset
could it be this: "E: Can't open /cache/recovery/command" that is the problem? I only found one reference to this message during my internet searches and the guy said it always says that..
So you have CM-Recovery?
Flash Amon_RA`s Recovery, it´s more comfortable to me. I´m using 1.6.2.
For G1: http://forum.xda-developers.com/showthread.php?t=566669
For MT3G(Magic 32b): http://forum.xda-developers.com/showpost.php?p=4029315&postcount=1
Nope. I am also using Flash Amon_RA's recovery.. (v1.6.2)
I loaded it up on the flash drive and also used telnet app to flash it in (wrong terminology? I typed it in the telnet box and hit return and it gave me the # # which I read means I did it right)
Try flashing again using fastboot.
Following Points should be listed:
1. Reboot system now
2. Go to console
3. USB-MS Toggle
4. Backup/Restore
5. Flash zip from sdcard
6. Wipe
7. Partition sdcard
8. Other
9. Power off
Install via Fastboot:
Copy recovery-RA-dream-v1.6.2.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img
maybe i get something wrong
but did you boot into the recovery menu already? (press home and power when you turn the phone on)
from there you can choose your task with the trackball nice and easy...
(you r from vienna?)
zerocoolriddler said:
Try flashing again using fastboot.
Following Points should be listed:
1. Reboot system now
2. Go to console
3. USB-MS Toggle
4. Backup/Restore
5. Flash zip from sdcard
6. Wipe
7. Partition sdcard
8. Other
9. Power off
Install via Fastboot:
Copy recovery-RA-dream-v1.6.2.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img
Click to expand...
Click to collapse
those points are not listed!
I did not try flashing via fastboot before but rather via terminal app.. Do I need some special software for fastbooting? Amon_RA's post says i need "Requires engineerings SPL!" which I do not have ..
and I now I loaded it via fastboot and I cant get out of it! how do I reboot out of fastboot? Because I can do not know how to "fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img" .. can you explain that in more detail?
skarboy- no i am not from vienna but the USA. and yea I tried to boot from the recovery menu but when i am there it does not show the option of flashing zip from sd (see above)
You did not succesfully apply the recovery image then. Find amon_ra 1.6.2, rename it to recovery.img (make sure that you don't accidentally name it to recovery.img.img because of windows explorer on your computer). Put it on the root of your sdcard. From there, open the telnet app and type "su", then type "flash_image recovery /sdcard/recovery.img" power back on to recovery (home+power), and apply DRC83, CM4.2.15.1, and radio 2.22.23.02.
mejorguille said:
You did not succesfully apply the recovery image then. Find amon_ra 1.6.2, rename it to recovery.img (make sure that you don't accidentally name it to recovery.img.img because of windows explorer on your computer). Put it on the root of your sdcard. From there, open the telnet app and type "su", then type "flash_image recovery /sdcard/recovery.img" power back on to recovery (home+power), and apply DRC83, CM4.2.15.1, and radio 2.22.23.02.
Click to expand...
Click to collapse
oh okay. shoot.. I followed your instructions. do I hit return after typing 'su' in telnet? I did and then typed in the flash image stuff and hit return again. it gave me '##'
i am not rebooting in recovery.. hopefully it will work .
can i have all 4 files on the SD card at the same time? or should i erase it then load the DRC83, CM4.2.15.1, and radio 2.22.23.02 files??
also if i dont get the alt+a option should i just keep trying ??
EDIT: NOPE IT did not work, maybe I should just rename the file recovery, i looked under file properties last time but it didnt say it was hiding the file extension.. I am not quite sure what I am doing wrong.. if someone could show lead me through each individual step by step that would be swell.. of post a video (not outdated).
awwwwwww this is soo painful
austriker27 said:
oh okay. shoot.. I followed your instructions. do I hit return after typing 'su' in telnet? I did and then typed in the flash image stuff and hit return again. it gave me '##'
i am not rebooting in recovery.. hopefully it will work .
can i have all 4 files on the SD card at the same time? or should i erase it then load the DRC83, CM4.2.15.1, and radio 2.22.23.02 files??
also if i dont get the alt+a option should i just keep trying ??
EDIT: NOPE IT did not work, maybe I should just rename the file recovery, i looked under file properties last time but it didnt say it was hiding the file extension.. I am not quite sure what I am doing wrong.. if someone could show lead me through each individual step by step that would be swell.. of post a video (not outdated).
awwwwwww this is soo painful
Click to expand...
Click to collapse
First make sure you have all the files needed (recovery.img, DRC83_base_defrangled, CM4.2.15.1, and radio 2.22.23.02). Tell me if you are missing anything. Load them all up on your sdcard. Make sure that none of the files are in any folders. Next you are going to want to download the "terminal emulator" app from the market (by ZTA). Once downloaded, open the app and type "su" (enter). After that, type "flash_image recovery /sdcard/recovery.zip"(enter). Type "reboot recovery" (enter). If you do not see this image below, then something went wrong.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(note, that image shows 1.7 but you are going to want to install 1.6.2. v1.7 is for CM5-based roms)
okay, so after a much needed break of watching the US draw with England (world cup!!) i am back..
yes I have all of those files but my radio file is different (older?).. It is "ota-radio-2_22_19_26I".. should I have the radio file you mentioned? can you link it to me?
EDIT: Okay I found that file that you referenced and downloaded it. I will throw it in my sd card instead of the 26I because it sounds like it is a better radio flash..
also the 'radio', update cm, and DRC83 files are really zipped folders (.zip) that I have not extracted. Do I need to extract the contents into a folder and put the files from these extracted folders on the SD card root (so that there are ZERO folders on the sd? (no one mentioned this)
and so I use terminal emulator as opposed to telnet?? I was using telnet before because the CM wikiguide says so..
You don't need to unzip. They're zipped to flash via Recovery.
Flash the Recovery via Fastboot.
PS: It's called Terminal, not Telnet. ;-)
mejorguille said:
First make sure you have all the files needed (recovery.img, DRC83_base_defrangled, CM4.2.15.1, and radio 2.22.23.02). Tell me if you are missing anything. Load them all up on your sdcard. Make sure that none of the files are in any folders. Next you are going to want to download the "terminal emulator" app from the market (by ZTA). Once downloaded, open the app and type "su" (enter). After that, type "flash_image recovery /sdcard/recovery.zip"(enter). Type "reboot recovery" (enter). If you do not see this image below, then something went wrong.
(note, that image shows 1.7 but you are going to want to install 1.6.2. v1.7 is for CM5-based roms)
Click to expand...
Click to collapse
okay so I tried all that.. and freaking a! awwwwww no success it just gave me the old screen like before
when I typed in "su" it said permission denied so I think I have to go back and do something that I missed. I cant keep track of how many times I have done everything, then erased then tried again.. I wish someone would be specific and just walk me through this without skipping a single detail..
zerocoolriddler said:
You don't need to unzip. They're zipped to flash via Recovery.
Flash the Recovery via Fastboot.
PS: It's called Terminal, not Telnet. ;-)
Click to expand...
Click to collapse
this is exactly what i am talking about everyone is saying something different:
here is the CM site telling me to use telnet:
Open Android Telnet Client and type (include all spaces)
flash_image recovery /sdcard/recovery.img [enter]
If completed correctly you will simply see # # appear on your screen beneath the line you've just typed. If you get the "permission denied" message, type "su" (without quotes), press enter and repeat the previous step. If you get a file not found message, you may need to remount your sd card or make sure you typed the file name correctly.
Press Home key and proceed to next step
austriker27 said:
okay, so after a much needed break of watching the US draw with England (world cup!!) i am back..
yes I have all of those files but my radio file is different (older?).. It is "ota-radio-2_22_19_26I".. should I have the radio file you mentioned? can you link it to me?
EDIT: Okay I found that file that you referenced and downloaded it. I will throw it in my sd card instead of the 26I because it sounds like it is a better radio flash..
also the 'radio', update cm, and DRC83 files are really zipped folders (.zip) that I have not extracted. Do I need to extract the contents into a folder and put the files from these extracted folders on the SD card root (so that there are ZERO folders on the sd? (no one mentioned this)
and so I use terminal emulator as opposed to telnet?? I was using telnet before because the CM wikiguide says so..
Click to expand...
Click to collapse
the 2.22.23.02 radio is newer and its supposed to have better reception and less battery usage as compared to the .26I radio but the difference should be minimal. Everything is supposed to be in a zipped folder exept for the recovery image. Terminal is similar to telnet in that you can put in commands but it works a little different. It is what I usually use to flash recovery's, etc, so since telnet was not working for you I though terminal might make a difference.
Again, open terminal and type:
Code:
su(enter)
flash_image recovery /sdcard/recovery.img(enter)
reboot recovery(enter)
Tell me if this works.
Edit:look at my next post
austriker27 said:
this is exactly what i am talking about everyone is saying something different:
here is the CM site telling me to use telnet:
Open Android Telnet Client and type (include all spaces)
flash_image recovery /sdcard/recovery.img [enter]
If completed correctly you will simply see # # appear on your screen beneath the line you've just typed. If you get the "permission denied" message, type "su" (without quotes), press enter and repeat the previous step. If you get a file not found message, you may need to remount your sd card or make sure you typed the file name correctly.
Press Home key and proceed to next step
Click to expand...
Click to collapse
The "su" command signifies root access. If it says permission denied, then that means that you are not rooted or you skipped a step.
CYANOGEN WIKI said:
Rooting the phone
You need to have root (or 'admin') access to the phone so that you can install whatever software you want and not just what your provider gives you. This is not the same as unlocking your phone.
Finish booting up your phone, and sign-in to your Google account.
If you don't have access to a 3G network, then follow the G1 logon to google via wifi guide to sign-in via wifi. The original guide to do this is out of date.
You could try and add your networks provider's APN. To do this press Menu key -> APN Settings, press Menu again -> Add APN and enter 4 things: Name, MCC (Mobile Country Code), MNC Mobile Network Code and APN - all this info should be available here: http://en.wikipedia.org/wiki/Mobile_network_code and on your network provider's site. The image you booted with might also have the extensive APN list. If so, and you can't get a data connection, then you might try the wifi guide.
Once you're at the Home screen, open the keyboard, and press the Enter (Return) button twice.
Type
telnetd [enter]
Typing will bring up the Contacts screen, but you can just ignore that.
There will be no indication to let you know you did it right. Just continue on to the next step.
If you get an error when trying to connect (step 5), try pressing Enter twice and type "telnetd" and press Enter again
Open the Android Market, and install "Telnet" by ClockworkMod (Formerly by Koushik Dutta)
Open Android Telnet Client, enter "localhost" in the large text box and press connect. (You may have to enter "23" in the smaller text box on the right)
Click to expand...
Click to collapse
Do those steps again.
okay so I am in the telnet client and have entered localhost and 23 and hit return. so now i am in a black screen. i typed in what cm wikiguide told me and it gave me :
## (good sign!)
now do I turn off the phone and go into recovery mode or this where I am missing a step??
Sorry I am so ornery (wow and i can spell) there are just a number of things frustrating me.. besides me knowing this should only take like 2 hours at the most and knowing I keep messing up some mundane detail or something.. Also I am doing it in windows on my macbook and the wireless keeps disconnecting. Also I would take photos of the screens to show you but I do not have any photo software on the windows partition of my laptop (i mostly use mac os x) so I cannot... and i am very tired from working 6 days a week (and only getting 6 hours of sleep last night due to this issue) and frustrated from this whole fiasco.. And I have a headache.. yup call me a whiner if ya want but i am just trying to explain why i am kinda mad...
HALELUJAH! it worked and the android system recovery looks like your image mejor!!!!!!!! hopefully this works, i will let you know.. thanks soo much! i have no idea what i did differently
YESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
wow so that wasnt a giant headache, although now i pretty have the process memorized and have learned tons in the process. I think I may have the longest time to root a g1 record so far of any human haha... Lets see I worked on it yesterday from 8pm-1am while kind of watching world cup. This morning for about 2 hours from 9-1130 at my job. And this afternoon for about 2 hours..So like 9 hours give or take an hour of two.. NEW RECORD!! haha
THANKS SO MUCH for you help guys I love you. Especially mejor because he/she lead me down the finishing stretch... Now to install apps2sd (after my class 6 card comes) and take a nap
Just finished the S-OFF using alpharevx, want to know how to do the permanent ROOT.
Any tips?
http://forum.xda-developers.com/showthread.php?p=14693680
check this out, pretty detailed
There is a Sticky at top of the IncS General Forum about this.
You need to install gingerbreak on your phone it's here http://forum.xda-developers.com/showthread.php?t=1044765 and Open Gingerbreak and click Root Device. that's all.
nikkuy said:
You need to install gingerbreak on your phone it's here http://forum.xda-developers.com/showthread.php?t=1044765 and Open Gingerbreak and click Root Device. that's all.
Click to expand...
Click to collapse
Not quite...
I have rooted 4 IncS wit GingerBreak now, and non of them succede first time.
2 got rooted thrid time i ran GB, and 2 of them i had to take the SD card out when the error message came.
But GinderBreak can root the IncS, but somthimes you need some "Ninja" tricks.
Are you done?
geeti said:
http://forum.xda-developers.com/showthread.php?p=14693680
check this out, pretty detailed
Click to expand...
Click to collapse
This just worked for me - it was simple in the end!
I used a spare SD card (I don't think I needed to), just copy/pasted the clockwork recovery .zip file to the card (not in a folder on the card) and rebooted, holding volume down on start-up. After that, it automatically prompted me to install the file, so I let it install.
Then, I rebooted the phone and deleted the above file from the SD card, and replaced it with the signed root .zip file and rebooted with the volume down button again.
Just follow the steps, one by one, 'To root:' in the above linked post, after you have installed the recovery file - it worked first time for me and was actually simple to follow!!
My phone works as it always has done (as you would expect/hope), but now I have root - confirmed with Root Explorer app from Market.
Thanks to all involved in the linked post above.
I also tried GingerBreak a few times but it just didn't work for me, so I gave this a go and it worked first time.
jkolner said:
Not quite...
I have rooted 4 IncS wit GingerBreak now, and non of them succede first time.
2 got rooted thrid time i ran GB, and 2 of them i had to take the SD card out when the error message came.
But GinderBreak can root the IncS, but somthimes you need some "Ninja" tricks.
Click to expand...
Click to collapse
My phone is still on 2.2 Froyo, Gingerbreak is for 2.3 correct?
geeti said:
http://forum.xda-developers.com/showthread.php?p=14693680
check this out, pretty detailed
Click to expand...
Click to collapse
I dont quite understand step 4, 5, 6:
4. Extract recovery.img from the archive and put it with fastboot.
5. Put the phone is Fastboot USB mode (HINT: Android is not up and running - access it from your hboot screen - see how below)
6. fastboot flash recovery <recovery.img> <<< from a command line (use root for Linux- sudo ./fastboot yadda)
Step 4, it says put it with fastboot, does it mean after i extracted the recovery.img, move it to the same folder with the fastboot app (i.e. to the folder android-win-tools where the fastboot app is located?).
Step 5, Fastboot USB mode, this is done by holding the volume down button and the pressing the power button, when the white screen comes up, select Fastboot, and then plug the phone back to the computer via USB?
Step 6, after the phone is plugged to the computer via USB, double click on the fastboot app (the one inside the android-win-tools folder) and when the black prompt screen comes up, type in Linux- sudo ./fastboot yadda?
Btw, I am on Windows computer, not Linux, so is the command prompt Linux- sudo ./fastboot yadda correct?
Also, if I want to bluetooth the su-2.3.6.1-ef-signed.zip to the phone, will it go directly to the SD root location? If not, when I do clockworkmod recovery and "install zip from sdcard", will it able to locate the file?
netwr said:
I dont quite understand step 4, 5, 6:
4. Extract recovery.img from the archive and put it with fastboot.
5. Put the phone is Fastboot USB mode (HINT: Android is not up and running - access it from your hboot screen - see how below)
6. fastboot flash recovery <recovery.img> <<< from a command line (use root for Linux- sudo ./fastboot yadda)
Step 4, it says put it with fastboot, does it mean after i extracted the recovery.img, move it to the same folder with the fastboot app (i.e. to the folder android-win-tools where the fastboot app is located?).
Step 5, Fastboot USB mode, this is done by holding the volume down button and the pressing the power button, when the white screen comes up, select Fastboot, and then plug the phone back to the computer via USB?
Step 6, after the phone is plugged to the computer via USB, double click on the fastboot app (the one inside the android-win-tools folder) and when the black prompt screen comes up, type in Linux- sudo ./fastboot yadda?
Btw, I am on Windows computer, not Linux, so is the command prompt Linux- sudo ./fastboot yadda correct?
Also, if I want to bluetooth the su-2.3.6.1-ef-signed.zip to the phone, will it go directly to the SD root location? If not, when I do clockworkmod recovery and "install zip from sdcard", will it able to locate the file?
Click to expand...
Click to collapse
No, follow step 6 you use command line like this: "fastboot flash recovery C:\recovery.img". After you choose "install zip from sdcard" you have to choose the location where you put the file you want to install.
coy1987 said:
No, follow step 6 you use command line like this: "fastboot flash recovery C:\recovery.img". After you choose "install zip from sdcard" you have to choose the location where you put the file you want to install.
Click to expand...
Click to collapse
So this is exactly how it should be typed in the command prompt?
fastboot flash recovery C:\recovery.img
Are the rest of other steps correct?
I am still getting stuck at the Clockworkmod installation part, without this I cannot get to the root step.
I extracted the android-win-tools.zip, which contains the following files:
adb
AdbWinApi.dll
AdbWinUsbApi.dll
android-info
fastboot
and then extracted the cwm-vivow-4.0.0.4-recovery.img.zip, contains the following:
recovery.img
then I moved all the above 6 files directly to the C: directory. After that went into cmd and typed the prompt exactly like following:
fastboot flash recovery C:\recovery.img
Did I miss anything? Because after typing that line and hit return it came out nothing. Is that prompt correct?
Why not root with superoneclick -> download clockworkmod from market and install recovery from app? Work perfectly for me...
Sent from my HTC Incredible S
adaca said:
Why not root with superoneclick -> download clockworkmod from market and install recovery from app? Work perfectly for me...
Sent from my HTC Incredible S
Click to expand...
Click to collapse
clockworkmod from market, is it aka ROM Manager?
This app won't work because it requires a ROOT phone, which is what I am trying to do.
Yes, and before use superoneclick.
Sent from my HTC Incredible S
adaca said:
Yes, and before use superoneclick.
Sent from my HTC Incredible S
Click to expand...
Click to collapse
How did you get it from market, is it not up currently
Superoneclick is not from market, use google. Its for rooting.
Sent from my HTC Incredible S
You can also try Gingerbreak if you can't get SuperOneClick to work (again you'll have to search for this as it's not in the market).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just installed SuperOneClick and clicked Root, it said the phone is rooted successfully. Then clicked on the "allow non market apps" and the result said non-market apps enabled.
But then I went to market and installed a screen cap app (one needs root), launched the app and it said Root required - Your phone does not appear to be rooted or has not been given root privileges.
Did the SuperOneClick really root it?
doctorsax said:
You can also try Gingerbreak if you can't get SuperOneClick to work (again you'll have to search for this as it's not in the market).
Click to expand...
Click to collapse
Does Gingerbreak work with 2.2?
READ THE WARNING
READ THE ENTIRE POST
DETAILED INSTRUCTIONS AFTER FILE
I am not responsible for bricked devices, firings due to the alarm not going of, thermonuclear war caused by a missed phone call or anything that goes wrong because of this. Try at your own risk (it'll work if you do it right)
Click to expand...
Click to collapse
I just finished flashing the 4.3 Factory images without losing user data.
I was previously running 4.2.2 Stock unrooted, with an unlocked bootloader.
You can do this simply by taking the .sh or .bat file they provide and removing the
Code:
-w
flag from the
Code:
fastboot update
command
This is my modified flash-all.sh for a mac:
Code:
#!/bin/sh
# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
sleep 5
fastboot update image-occam-jwr66v.zip
Prerequisites:
1. Download the file for flashing from here.
2. Make sure your bootloader is unlocked. If it is not, you will have to unlock it which WILL WIPE YOUR DEVICE. Wait for the OTA or make a backup somewhere if you like your data. If you want to unlock the bootloader use:
Code:
fastboot oem unlock
Detailed steps:
1. Extract the downloaded tgz. You should have the following files: bootloader-mako-makoz20i.img, flash-all.bat, flash-all.sh, flash-base.sh, image-occam-jwr66v.zip and radio-mako-m9615a-cefwmazm-2.0.1700.84.img.
2. Depending on your platform open either the flash-all.bat (Windows) or the flash-all.sh (UNIX/Linux/Mac) file in a text editor, and remove the -w flag from the last line.
3. Open a terminal, connect your device, enable USB Debugging and then:
Code:
adb reboot bootloader
sh flash-all.sh
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: This will probably not work if you're running custom recoveries and/or custom ROMs. Having a rooted stock ROM should not be a problem, though you will almost definitely lose root
Is the headphone output fixed? Does it sound louder than before?
vickpick said:
Is the headphone output fixed? Does it sound louder than before?
Click to expand...
Click to collapse
There doesn't seem to be any difference to me, but I have fairly crappy headphones.
Raghav Sood said:
There doesn't seem to be any difference to me, but I have fairly crappy headphones.
Click to expand...
Click to collapse
Okay, just making sure, lol. I have the same experience and I was just wondering if I screwed up something while flashing. Thanks!
Raghav Sood said:
I just finished flashing the 4.3 Factory images without losing user data.
I was previously running 4.2.2 Stock unrooted, with an unlocked bootloader.
You can do this simply by taking the .sh or .bat file they provide and removing the
Code:
-w
flag from the
Code:
fastboot update
command
WARNING: This will probably not work if you're running custom recoveries and/or custom ROMs. Having a rooted stock ROM should not be a problem, though you will almost definitely lose root
Click to expand...
Click to collapse
I am sorry for the noob question, but I keep getting an "installation aborted" message when trying to flash the factory image. It's a .tgz file and in the past, i've only flashed .zip's. How do I flash that file?
Thanks
Please make a tutorial more specific
Triune said:
I am sorry for the noob question, but I keep getting an "installation aborted" message when trying to flash the factory image. It's a .tgz file and in the past, i've only flashed .zip's. How do I flash that file?
Thanks
Click to expand...
Click to collapse
You'll have to ensure a couple of things:
Extract the tgz. You'll end up with a bunch of img, sh, zip and bat files. Depending on whether you're on Windows or Mac or Linux, you're going to want to run the flash-all.sh or flash-all.bat file. DO NOT RUN IT RIGHT AWAY. First edit it as shown in the Opening Post.
Also make sure that fastboot is in your PATH variable (you'll get an error saying fastboot is not a command if it isn't)
javier13javier said:
Please make a tutorial more specific
Click to expand...
Click to collapse
Editing the OP with more detailed instructions now
Triune said:
I am sorry for the noob question, but I keep getting an "installation aborted" message when trying to flash the factory image. It's a .tgz file and in the past, i've only flashed .zip's. How do I flash that file?
Thanks
Click to expand...
Click to collapse
After unzipping with 7zip for example, you should have available
image-occam-jwr66v.zip
and other files like bootloader-mako-makoz20i.img and radio-mako-m9615a-cefwmazm-2.0.1700.84.img
Raghav Sood said:
You'll have to ensure a couple of things:
Extract the tgz. You'll end up with a bunch of img, sh, zip and bat files. Depending on whether you're on Windows or Mac or Linux, you're going to want to run the flash-all.sh or flash-all.bat file. DO NOT RUN IT RIGHT AWAY. First edit it as shown in the Opening Post.
Also make sure that fastboot is in your PATH variable (you'll get an error saying fastboot is not a command if it isn't)
Click to expand...
Click to collapse
What do you exactly mean with make fastboot variable? I keep getting the fastboot error.
Infinite104 said:
What do you exactly mean with make fastboot variable? I keep getting the fastboot error.
Click to expand...
Click to collapse
fastboot is part of the developer tools, and Google assumes you have it in your PATH. The Cyanogen Wiki has a great page on how to set that up here
RASTAVIPER said:
After unzipping with 7zip for example, you should have available
image-occam-jwr66v.zip
and other files like bootloader-mako-makoz20i.img and radio-mako-m9615a-cefwmazm-2.0.1700.84.img
Click to expand...
Click to collapse
I've extracted, but what i'm not understanding up to this point is how to flash it. Do you re-zip it then flash it through the stock recovery?
Just a heads up, you have to unzip twice before u get to flash.bat
TGZ, then TAR.
---------- Post added at 09:38 PM ---------- Previous post was at 09:37 PM ----------
Triune said:
I've extracted, but what i'm not understanding up to this point is how to flash it. Do you re-zip it then flash it through the stock recovery?
Click to expand...
Click to collapse
no, you copy all the files into the fastboot folder (iincluding modified bat or sh), then run the bat or sh
Oh and phone should be in download mode and connected.
you don't use the recovery, just press your power down and power and connect when the black screen comes up.
vickpick said:
Just a heads up, you have to unzip twice before u get to flash.bat
TGZ, then TAR.
---------- Post added at 09:38 PM ---------- Previous post was at 09:37 PM ----------
no, you copy all the files into the fastboot folder (iincluding modified bat or sh), then run the bat or sh
Oh and phone should be in download mode and connected.
you don't use the recovery, just press your power down and power and connect when the black screen comes up.
Click to expand...
Click to collapse
That's the difference, i'm in a mac. I don't have a fastboot folder. I wish Google would just release flashable zips. Smh
Triune said:
I've extracted, but what i'm not understanding up to this point is how to flash it. Do you re-zip it then flash it through the stock recovery?
Click to expand...
Click to collapse
Check this:
- YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
- ENABLE USB Debugging via Developer settings (press the build button 7 times to activate it the "settings --> about phone --> Build Number"
- Launch command prompt (start --> run --> "cmd")
- type in command prompt "cd directory where you have the adb & fast boot" for example here is mine "cd C:\Users\sdk\platform-tools"
- Type in the command prompt each step one at a time
"fastboot flash bootloader bootloader-mako-makoz20i.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"fastboot reboot-bootloader"
"fastboot update image-occam-jwr66v.zip"
Will this work if we're on a stock 4.2.2 ROM but with LTE changes (older radio, edited build.prop and soc file?)
Triune said:
That's the difference, i'm in a mac. I don't have a fastboot folder. I wish Google would just release flashable zips. Smh
Click to expand...
Click to collapse
On a mac you should also have fastboot-mac in addition to fastboot.
Replace fastboot in the description with fastboot-mac and you shouldn't get any error messages
bioyuki said:
Will this work if we're on a stock 4.2.2 ROM but with LTE changes (older radio, edited build.prop and soc file?)
Click to expand...
Click to collapse
Just tested, it works fine.
RASTAVIPER said:
Check this:
- YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
- ENABLE USB Debugging via Developer settings (press the build button 7 times to activate it the "settings --> about phone --> Build Number"
- Launch command prompt (start --> run --> "cmd")
- type in command prompt "cd directory where you have the adb & fast boot" for example here is mine "cd C:\Users\sdk\platform-tools"
- Type in the command prompt each step one at a time
"fastboot flash bootloader bootloader-mako-makoz20i.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"fastboot reboot-bootloader"
"fastboot update image-occam-jwr66v.zip"
Click to expand...
Click to collapse
Thats the same of deleting the -w and run the .bat on windows.
EDIT: Ok guys, this will work for windows (you have to install adb on your computer and have bootloader unlocked)
1- Remove the -w from the bat (with any editor), that came with the zip.
2- On cmd put adb reboot bootloader
3- Run the modified bat that dont have the -w, just wait and you will have 4.3.
Proof:
For me I had a custom recovery installed and custom rom, so at first I didn't wipe data. It did not boot. So I flashed twrp, and wiped data, not personal data though, and it booted.
You will find other versions but this is how I did it and how I solved a few common problems. If you do it exactly following the instructions, you should not loose data. I flashed from Android 4.2.2 rooted.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Then if you want to root:
1. On your Mac, download TWRP recovery from here: http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img
2. Connect your Nexus 4 (debug mode) and put it in fastboot mode (point 5 above)
3. In terminal mode enter: ./fastboot flash recovery FILENAME.img (replace FILENAME by the file name of TWRP file you just downloaded)
4. Reboot your phone
5. Download directly from your phone this file (SuperSU): http://download.chainfire.eu/340/SuperSU/SuperSU-JWR66N-S005-130625-1.41.zip
6. Shut down your phone and boot it in recovery mode (Once off, push vol+, vol-, and power all together). Choose recovery mode with vol-
7. Once you are in TWRP recovery mode push "Install", look for SuperSU file you just downloaded and follow instructions to flash the zip file.
That's it! You are now root. All your data are intact.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/ and http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
jipi said:
You will find other versions but this is how I did it and how I solved a few common problems.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/
Click to expand...
Click to collapse
I have the OTA file ... Will this work?
Sent from my Nexus 4 using Tapatalk 2
veteran_troller said:
I have the OTA file ... Will this work?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I have no idea but it takes only a few minutes to download the original factory file.
jipi said:
You will find other versions but this is how I did it and how I solved a few common problems.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/
Click to expand...
Click to collapse
this procedure wipe everything...I updated in this way yesterday
Works
Nice post. Works exactly as described.
Thanks!!
Matt
jipi said:
You will find other versions but this is how I did it and how I solved a few common problems.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/
Click to expand...
Click to collapse
alakyr said:
this procedure wipe everything...I updated in this way yesterday
Click to expand...
Click to collapse
If you did exactly like this it shouldn't have wiped your phone. I did it myself exactly as I describe it!
jipi said:
If you did exactly like this it shouldn't have wiped your phone. I did it myself exactly as I describe it!
Click to expand...
Click to collapse
If you delete userdata.img from zipfile it will not wipe your data.
My data wiped too
I followed everything precisely on a completely stock Nexus 4 and it wiped my data too.. Not to critical for me since I dont do much with my phone so its not a bother but just for reference for others...
Well this method will keep your SD card contents, but will wipe your data/data on internal storage. So depends on what you mean by wipe
Remoteconcern said:
Well this method will keep your SD card contents, but will wipe your data/data on internal storage. So depends on what you mean by wipe
Click to expand...
Click to collapse
My Nexus 4 doesnt have an sd card..
I am sorry for those who have lost data but I did exactly what I have said and preserved all my data without any other manipulation. All my apps are still there, gmail accounts, WiFi passwords, etc... I am not an expert, maybe somebody will be able to explain when data are deleted and when not.
For anyone having trouble flashing on a mac, I kept getting a usb_write error when I tried to flash the system.img. Bootloader and radio flashed just fine, but not the actual rom. I got it working in windows and narrowed the problem down to either the version of adb and fastboot I was using ( they came from a zip in another thread called rootnexus4.zip) or the archive app I was using on macOS (The Unarchiver). Hope this helps someone.
Sent from my Nexus 4 using xda premium
Is the root okay?
Thanks
Root is fine. Using SuperSU 1.43
Sent from my Nexus 4 using xda premium
this didnt wipe /data for me either.
jipi said:
If you did exactly like this it shouldn't have wiped your phone. I did it myself exactly as I describe it!
Click to expand...
Click to collapse
sirry my bad...i used also the -w flag that wipe everything
Sent from my Nexus 4 using Tapatalk 4 Beta
alakyr said:
sirry my bad...i used also the -w flag that wipe everything
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, that was the problem, you didn't follow exactly the process. If you use -w flag it will wipe your data. I am sorry for you.
Noiseboy1176 said:
For anyone having trouble flashing on a mac, I kept getting a usb_write error when I tried to flash the system.img. Bootloader and radio flashed just fine, but not the actual rom. I got it working in windows and narrowed the problem down to either the version of adb and fastboot I was using ( they came from a zip in another thread called rootnexus4.zip) or the archive app I was using on macOS (The Unarchiver). Hope this helps someone.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
It is better to download a fresh version of Android SDK (link on the first post) and then upgrade it following the method as described in the link in point 4. It seems that ADB has to be upgraded to work with 4.2.2 because 4.2.2 implemented a new security feature with certificate.
So, if ADB works fine, don't change anything but if it doesn't, upgrade to the newest version. If you don't know how to do it follow the procedure, it is easy.
jipi said:
It is better to download a fresh version of Android SDK (link on the first post) and then upgrade it following the method as described in the link in point 4. It seems that ADB has to be upgraded to work with 4.2.2 because 4.2.2 implemented a new security feature with certificate.
So, if ADB works fine, don't change anything but if it doesn't, upgrade to the newest version. If you don't know how to do it follow the procedure, it is easy.
Click to expand...
Click to collapse
Agreed. That's what I usually do, but was feeling lazy and the version of adb I had works for everything I've tried so far... Unlocking boot loader on 4.2.2, flashing numerous recoveries, radios etc. So I thought it would be fine. Of course, it is possible that my problem was the archive utility I used to extract the ROM and not adb related at all. Either way, I figured ppl should know in case it happens to them.
Must the bootloader be unlocked to do this flash? Have flash many roms with Windows PC but now Im a mac user and never flashed roms with mac and yesterday i tried and didnt get it is the an video tutorial on this?
Hi everyone, I've tried for months to find a way of getting my sph-720t unlocked for domestic use.
Pokemon came out and I had to get this phone working.
I tried a combination of two guides and got it working, credit goes to
(http://forum.xda-developers.com/showthread.php?t=2530610)
@autoprime and @nicotheandroidguy
(http://forum.xda-developers.com/galaxy-s4-sprint/general/l720-l720t-gsm-unlock-att-tm-t3189063)
nfsmww ( please donate
paypal: [email protected] )
I decided I would try to make it easier and make a guide for you guys that were having the same trouble as me.
This method is for the sprint sph-720T model, this might work on other galaxy s4s, but the links I provided are specific for the 720T model. (so if your trying this on another model, like the 720 - find your own download links, dont use the ones provided
If you are on 4.4.2 or an older version of android - you are good
if you are on a later version - please download the M919 Rom found here and flash it using Odin
1. Make sure your device is rooted. Boot to Recovery - Open Odin and select AP, then flash the autorooter found here.
3. Open Odin, select AP and flash the MK5 modem found here
4 .open super SU and click on disable knox, if it doesnt work the first time, restart the phone - should work as long as your on 4.4.2
5. install this app, run it and click unlock
3) I went to the dialer and typed *#0011# which brought me to the "service mode" Menu.
4) Hit the soft menu key (bottom left of the phone)
Hit back
hit back again
hit key input
enter capital "Q" hit enter
hit key input again and type "0000"
wait 10 seconds, it should bring up the secret menu.
5. Press 2 (CDMA) > Press 1. (COMMON) > NEXT > NEXT > 8 PREF MODE SET > GSM_WCDMA_ONLY
6) Hit the soft menu key and select back until you reach the main menu and select UMTS
then select [1]DEBUG SCREEN > [6]PHONE CONTROL, > [2]FAKE SECURITY CONTROL > set it to ON
7)Press menu and back and select [3] NAS CONTROL. We are going to check a few different settings in this menu so remember how to get here cause I don’t want to repeat myself.
[1] CIPHERING CONTROL = OFF
[2] INTEGRITY CONTROL =ON
[3] SIM CLASS CONTROL = UMTS
[4] REVISION CONTROL = DO NOT TOUCH
[5] RRC(HSPA) CONTROL = DO NOT TOUCH
[6] DUALMODE IMPROVEMENT CONTROL= DO NOT TOUCH
[7] NAS AVOID SECURITY CONTROL= OFF, 0
[8] BIP BLOCK = 1
8) Press menu and back twice then > PHONE CONTROL > Select [7] NETWORK CONTROL > select [1] GFC and make sure that it is set to [1]GSM/(E)GPRS/WCDMA REL8 .
9) Press menu and back and select [2] BAND SELECTION and select WCDMA/GSM ALL for both WCDMA and GSM band preferences. I selected the ALL choice for LTE as well even though I know it isn’t supported for TMOBILE.
10) Under the NETWORK CONTROL menu we just came from select [4] AQUISITION ORDER and change it to [3]UMTS_GSM
11) Press menu and back until you are in the PHONE CONTROL menu and select [5] SIMULATION , press the [2] SW WATCHDOG button 6(six) times and then the [3] HW WATCHDOG 6(six) times. After you hit both of those 6 times, Hold the power down and reboot immediately.
12 ) If you want 4g LTE you must use odin to install TWRP which you can find here
13 ) turn off your phone and boot in to recovery by holding power, volume up and the home button. This is annoying because if you hold it too long it will power off again.
In here you want to click install from zip, select the M919 file. install it and then go to clear cache davik, go to reboot and you are all good!
enjoy. This fix has been brought to you both by imbmiller and nfsmww
I tried both methods but it didnt work until I combined them
interesting... going to try this and get back to you... but after this unlock.... could you use sprint and had the option to switch sims if need be using this rom?
Jonathanlc2005 said:
interesting... going to try this and get back to you... but after this unlock.... could you use sprint and had the option to switch sims if need be using this rom?
Click to expand...
Click to collapse
You can use any network after this unlock. I upgraded to cyanogens marshmallow rom and still have network service.
It worked, screenshot uploaded later
screenshots
Jonathanlc2005 said:
screenshots
Click to expand...
Click to collapse
going to keep testing and ill get back to you
will this work if your on 5.0.1 ok3 lollipop?
Hello,
I have a problem where my phone only connects to LTE. If i force CDMA mode, it just shows full bars but no 3g symbol. Does anyone know of a fix? LTE only has one bar near my new place.
Thanks
chopchopw said:
Hello,
I have a problem where my phone only connects to LTE. If i force CDMA mode, it just shows full bars but no 3g symbol. Does anyone know of a fix? LTE only has one bar near my new place.
Thanks
Click to expand...
Click to collapse
did you do exactly like it says including the radio?
the radio has to be flashed first before anything. i used to be on OH1, switched the radio and used cyanogenmod stable 4.4. then did this mod and it works so far. i havent had a chance to fully test it as i am on vacation but i will hopefully soon
yeah tmobile doesnt work
Great post! Just what I needed!! Can I make a TWRP backup of my CM12.1 ROM on OK3 modem and then then flash M919 rom and follow your directions? After all the steps, can I restore my TWRP backup of CM12.1 ROM and OK3 modem and will it still have domestic sim unlocked?
nyknight77 said:
Great post! Just what I needed!! Can I make a TWRP backup of my CM12.1 ROM on OK3 modem and then then flash M919 rom and follow your directions? After all the steps, can I restore my TWRP backup of CM12.1 ROM and OK3 modem and will it still have domestic sim unlocked?
Click to expand...
Click to collapse
restoring your modem would wipe out the unlock for sure
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Don't know how to install M919 ROM!!!
I need help installing M919 ROM. I have never done this before, so I do not know how to create the file format needed to use with ODIN. I tarred the boot.img file, but it is only 8MB in size; that isn't the file I'm suppose to load, is it?
Need more details than just "install the M919 rom"...
jkh9081 said:
I need help installing M919 ROM. I have never done this before, so I do not know how to create the file format needed to use with ODIN. I tarred the boot.img file, but it is only 8MB in size; that isn't the file I'm suppose to load, is it?
Need more details than just "install the M919 rom"...
Click to expand...
Click to collapse
Install TWRP with Odin, flash ROM from TWRP. That's a link in step 12.
Still struggling with unlocking phone.
bilgerryan said:
Install TWRP with Odin, flash ROM from TWRP. That's a link in step 12.
Thanks for the advice on TWRP; I eventually was able to install TWRP and was able to flash the M919 ROM.
I used odin to install the MK5 modem. I rebooted at this point and it updated 35 applications. The phone
is now booting with the new M919 rom, but I constantly get "Unfortunately, the process
com.android.phone has stopped". I'm on the step where you run SuperSU, but there are no
applications listed, so cannot disable knox. I'm so confused and exhausted from this; been messing
with it all day, but I think progress has finally been made. Will continue tomorrow, hopefully somebody
will have posted more help by then. My current question is should I install a stock 4.4.2 rom then
use the auto-rooter program? I'm wondering if the M919 rom is compatible since getting the errors.
I think I read that once rooted, no need to root again, so maybe just install a stock os.
Click to expand...
Click to collapse
jkh9081 said:
bilgerryan said:
Install TWRP with Odin, flash ROM from TWRP. That's a link in step 12.
Thanks for the advice on TWRP; I eventually was able to install TWRP and was able to flash the M919 ROM.
I used odin to install the MK5 modem. I rebooted at this point and it updated 35 applications. The phone
is now booting with the new M919 rom, but I constantly get "Unfortunately, the process
com.android.phone has stopped". I'm on the step where you run SuperSU, but there are no
applications listed, so cannot disable knox. I'm so confused and exhausted from this; been messing
with it all day, but I think progress has finally been made. Will continue tomorrow, hopefully somebody
will have posted more help by then. My current question is should I install a stock 4.4.2 rom then
use the auto-rooter program? I'm wondering if the M919 rom is compatible since getting the errors.
I think I read that once rooted, no need to root again, so maybe just install a stock os.
Click to expand...
Click to collapse
If the ROM is not rooted you will have to root again, but it's not hard.
Click to expand...
Click to collapse
Some notes to help others.
Being a newbie, I have no idea what I'm doing. So here are some notes that may help others like myself.
NOTE: My phone was previously rooted before starting this unlocking procedure.
In order to install the M919 rom, I had to install the TWRP (Team Win Recovery Project) tool. This was
accomplished by downloading the recovery.img file that was referenced by the link in this post. I had to use
the ODIN tool to install the file, but it had to be converted to a TAR file first. To convert to a TAR file, the
GNU version of TAR was downloaded and installed; I also set the Windows 7 search path to include the
bin directory of the installed tree (the search path allows running 'tar' without having to type
the full path to the program; the path was added by editing the path through the properties of
"My Computer" (right click the My Computer icon to edit). Once tar is installed, cd to where the recover.img
file resides and to the following command:
tar -cvf recovery.img.tar recovery.img
Now you have a recovery.img.tar file that will work with ODIN; install using the file as 'AP' type.
To use ODIN, put your phone in OS flash mode by powering it up by pressing volume down/home/power
buttons. Start up ODIN then plug the phone into the computer and press the volume up button; you will
see a message that the phone has been connected. Click the start button and the tarred image file will
be flashed to the phone. Now when the phone is booted by pressing the volume up/home/power buttons,
it will run the TWRP tool.
To install the M919 rom, boot phone in recovery mode (run the TWRP tool as mentioned above).
The M919 rom file is in a ZIP file which is the correct format for the TWRP tool to install, but the
ZIP file must first be put on your phone's SD card. To get the file onto the phone, you should be
able to remove the SD card and just copy it to the TWRP directory which should have been
created when TWRP was installed. However, I downloaded ADB on my computer and did
the following command from inside a windows CMD window from the directory where the
M919 rom Zip file resided...
adb push jfltetmo_M919UVUEMK2_Stock_Deodexed.zip /sdcard/TWRP
With the zip file on the sdcard (in the phone), click the 'INSTALL" button in TWRP and select
the /sdcard/TWRP/jflt...Deodexed.zip file path to flash to phone.
Installing the MK5 modem.bin file again requires it to be tarred for use with ODIN...
tar -cvf modem.bin.tar modem.bin
So that's where I'm currently at.
FYI, there seems to be a bug with the TWRP tool. If the phone is left inactive for a few
minutes, the screen will dim then lock and cannot: be unlocked. Once locked, the phone must
be powered down and TWRP restarted. So press the back arrow periodically to prevent the
phone from locking.
jkh9081 said:
Being a newbie, I have no idea what I'm doing. So here are some notes that may help others like myself.
NOTE: My phone was previously rooted before starting this unlocking procedure.
In order to install the M919 rom, I had to install the TWRP (Team Win Recovery Project) tool. This was
accomplished by downloading the recovery.img file that was referenced by the link in this post. I had to use
the ODIN tool to install the file, but it had to be converted to a TAR file first. To convert to a TAR file, the
GNU version of TAR was downloaded and installed; I also set the Windows 7 search path to include the
bin directory of the installed tree (the search path allows running 'tar' without having to type
the full path to the program; the path was added by editing the path through the properties of
"My Computer" (right click the My Computer icon to edit). Once tar is installed, cd to where the recover.img
file resides and to the following command:
tar -cvf recovery.img.tar recovery.img
Now you have a recovery.img.tar file that will work with ODIN; install using the file as 'AP' type.
To use ODIN, put your phone in OS flash mode by powering it up by pressing volume down/home/power
buttons. Start up ODIN then plug the phone into the computer and press the volume up button; you will
see a message that the phone has been connected. Click the start button and the tarred image file will
be flashed to the phone. Now when the phone is booted by pressing the volume up/home/power buttons,
it will run the TWRP tool.
To install the M919 rom, boot phone in recovery mode (run the TWRP tool as mentioned above).
The M919 rom file is in a ZIP file which is the correct format for the TWRP tool to install, but the
ZIP file must first be put on your phone's SD card. To get the file onto the phone, you should be
able to remove the SD card and just copy it to the TWRP directory which should have been
created when TWRP was installed. However, I downloaded ADB on my computer and did
the following command from inside a windows CMD window from the directory where the
M919 rom Zip file resided...
adb push jfltetmo_M919UVUEMK2_Stock_Deodexed.zip /sdcard/TWRP
With the zip file on the sdcard (in the phone), click the 'INSTALL" button in TWRP and select
the /sdcard/TWRP/jflt...Deodexed.zip file path to flash to phone.
Installing the MK5 modem.bin file again requires it to be tarred for use with ODIN...
tar -cvf modem.bin.tar modem.bin
So that's where I'm currently at.
FYI, there seems to be a bug with the TWRP tool. If the phone is left inactive for a few
minutes, the screen will dim then lock and cannot: be unlocked. Once locked, the phone must
be powered down and TWRP restarted. So press the back arrow periodically to prevent the
phone from locking.
Click to expand...
Click to collapse
Mine unlocks fine in TWRP 3.0
if any one need direct unlock contact me via pm
Still needing help.
I thought I had my phone unlocked, but made the mistake to trying to upgrade my android version using the Tmobile installation. Now the phone will not boot. I re-installed the M919 ROM, and the phone gets further along, but it shows a message of starting apps then shuts down. How can I get back to where the phone will boot? Thanks for any ideas. Also, can somebody please post a link to the 3.0 version of TWRP; the version I have will lock the screen and cannot be unlocked.
Correction: Phone will only briefly show the Samsung S4 image, then shuts down. Currently the phone will not even startup the TWRP tool; I can still get to the mode where I should be able to load the TWRP tool; looking like the phone maybe too far gone to save.