Database Info

[Q] Returning to stock [i9020a]

I just wanted to make sure that I understood the process of returning my phone to stock before I make a mistake.
All I've done since I purchased the phone was root it and unlock the bootloader. I have not loaded any custom roms.
So If I understand this correctly I need to:
1) Flash the Stock Image (which should include the stock recovery?)
2) Use fastboot to lock the bootloader
The reason I'm wanting to return the phone to stock is to receive OTA updates. I never use any apps requiring root, and don't plan on loading any custom roms.
I never did find a 2.3.4 stock image for the I9020A..

you should actually be able to get ota updates no problem. it'll just remove root every time you update.
it's probably not a good idea to lock the bootloader though cause if you ever want to unlock it again in the future you'll have to wipe everything from your phone. your best bet is to just flash stock recovery so you can install the update
i'm pretty sure that works, but hopefully someone else can verify just so you don't get some bad information lol

I heard the same thing about OTA updates. If you're phone is rooted and you're using the original rom, you'll get the update but you'll have to root your phone once again.
I haven't tried this myself so I cannot verify it.
It's just the word on the street, you know!

EraqEE said:
I heard the same thing about OTA updates. If you're phone is rooted and you're using the original rom, you'll get the update but you'll have to root your phone once again.
I haven't tried this myself so I cannot verify it.
It's just the word on the street, you know!
Click to expand...
Click to collapse
you need stock everything, so stock kernel, rom, radio, etc... the op should be fine to update if they flash stock recovery though. rooting is simple from there

dmuntean said:
I just wanted to make sure that I understood the process of returning my phone to stock before I make a mistake.
All I've done since I purchased the phone was root it and unlock the bootloader. I have not loaded any custom roms.
So If I understand this correctly I need to:
1) Flash the Stock Image (which should include the stock recovery?)
2) Use fastboot to lock the bootloader
The reason I'm wanting to return the phone to stock is to receive OTA updates. I never use any apps requiring root, and don't plan on loading any custom roms.
I never did find a 2.3.4 stock image for the I9020A..
Click to expand...
Click to collapse
where can i find a method to return a phone thats unlocked and rooted? any help would be appreciated.
Sent from my Inspire 3G.

bdpyo said:
where can i find a method to return a phone thats unlocked and rooted? any help would be appreciated.
Sent from my Inspire 3G.
Click to expand...
Click to collapse
I would like to do the same, I have a Fido/ATT I9020A and I'm having a hard time finding a stock nandroid backup to restore my phone with...
Anyone?>

bump
Sent from my Inspire 3G.

Here is stock 2.3.4 (GRJ22) with UCKD1 Radio & KA3 Bootloader.. http://dl.dropbox.com/u/7812800/Stock-GRJ22-i9020A-unsigned.zip Flash via ClockworkMod Recovery (due to it being unsigned zip)
I extracted and packaged it from my i9020a (and tested it on there).

how do you recomend flashing?
Sent from my Inspire 3G.

bdpyo said:
how do you recomend flashing?
Sent from my Inspire 3G.
Click to expand...
Click to collapse
Sorry forgot to add that to post... since its unsigned you need to flash via ClockworkMod Recovery.

kibmcz said:
Sorry forgot to add that to post... since its unsigned you need to flash via ClockworkMod Recovery.
Click to expand...
Click to collapse
Thanks kibmcz ! I'm a n00b when it comes to this but when you say flash via ClockworkMod you mean get into clockwork recovery mount the usb, transfer the zip onto the SD card and then <<Install from zip>> ?
Is that the method?

davis2k said:
Thanks kibmcz ! I'm a n00b when it comes to this but when you say flash via ClockworkMod you mean get into clockwork recovery mount the usb, transfer the zip onto the SD card and then <<Install from zip>> ?
Is that the method?
Click to expand...
Click to collapse
Yep that method works

kibmcz said:
Yep that method works
Click to expand...
Click to collapse
Thanks again kibmcz, so I just completed the flash, then did a fastbook oem lock.
Seems to be working fine except for one thing...
When I go into settings and hit Sound I get a Force close when I try and select a new ringtone...
Should I try reflashing again?

davis2k said:
Thanks again kibmcz, so I just completed the flash, then did a fastbook oem lock.
Seems to be working fine except for one thing...
When I go into settings and hit Sound I get a Force close when I try and select a new ringtone...
Should I try reflashing again?
Click to expand...
Click to collapse
Didn't happen on mine (In fact im using a self rooted rom based on that exact stock zip) try doing a wipe in stock recovery.

after flashing that does it take it back to out of box condition?
reason i ask is because i bought a already rooted and unlocked one here from market place and i want to return it to stock firmware, radio, kernel and such to recieve OTA updates and what not.
your info is greatly appreciated
Sent from my Inspire 3G.

bdpyo said:
after flashing that does it take it back to out of box condition?
reason i ask is because i bought a already rooted and unlocked one here from market place and i want to return it to stock firmware, radio, kernel and such to recieve OTA updates and what not.
your info is greatly appreciated
Sent from my Inspire 3G.
Click to expand...
Click to collapse
Using my zip yes... it flashes Bootloader, Radio, Boot, System and on first boot (and any other time recovery changes) Recovery is flashed. All you got to to is lock the bootloader and that wipes user data and usb storage.

hey man i appreciate you coming forward with a solution, ive yet to recieve the phone but wanted to prepare.
my goal is to flash everything back to stock and start completly over whereas i have no clue what method was originally used to root and unlock the bootloader.
when the time comes hope you dont mind a PM if i have any extra questions.
Sent from my Inspire 3G.

Just did the method using the stock ROM provided by kibmcz "thanks BTW!"
Phone is back to stock, working like it did when I first bought it. Had a little trouble with some Force Close issues but did a factory reset/data clear of the cache and all that before re-flashing, and it seems to be working Vanilla!

bdpyo said:
hey man i appreciate you coming forward with a solution, ive yet to recieve the phone but wanted to prepare.
my goal is to flash everything back to stock and start completly over whereas i have no clue what method was originally used to root and unlock the bootloader.
when the time comes hope you dont mind a PM if i have any extra questions.
Sent from my Inspire 3G.
Click to expand...
Click to collapse
Great and thanks DM all you want i don't mind. Oh and i now got stock 2.3.6 (GRK39F) uploaded.
Code:
[B][URL="http://dl.dropbox.com/u/7812800/Stock-GRK39F-I9020a-unsigned.zip"][B]Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader[/B][/URL][/B]
Works on: I9020A
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.

kibmcz said:
Great and thanks DM all you want i don't mind. Oh and i now got stock 2.3.6 (GRK39F) uploaded.
Code:
[B][URL="http://dl.dropbox.com/u/7812800/Stock-GRK39F-I9020a-unsigned.zip"][B]Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader[/B][/URL][/B]
Works on: I9020A
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Click to expand...
Click to collapse
So all I have done to my nexus s is root and cwm and kernel. I can do the ota to 2.3.6 or flash your package?
Running build GTJ61 and I9020AUCKE1 2.3.4 stock.
Sent from my Nexus S using xda premium

[Q]Manual update from 2.3.6 to 4.0.3/4.0.4

Hi,
Helping my friend with a Nexus S flash her device to ICS. After some probing, I think her device is a I9020T, from the baseband I9020XXKF1 and build GRK39F. Please correct me if I'm wrong.
So I've instructed her to download the 4.0.3 IML74K update from here to the root folder of her sdcard
I've had experience flashing zip files on HTC phones using CWM, but not on a stock unrooted Google device. Is the procedure the same? By that I mean booting to recovery, selecting the zip file to apply, apply it, then reboot.
Does she need to factory reset/wipe dalvik/wipe cache/etc?
Thanks!

Try the following, you could restore the device the factory settings before but it shouldn't be neccessary.
1. Download the official firmware
2. Rename it update.zip.
3. Copy it over to the internal storage space on your Nexus S.
4. Power your device off and then hold power and volume up to boot into the device’s bootloader.
5. Select Recovery using the volume keys and then confirm.
6. You’ll soon see a warning triangle and an arrow. Hold the power button and hit volume up.
7. A menu will pop up where you’ll want to select Apply update from /sdcard. Select update.zip.
8. It will install and you’ll want to select reboot system now.

Thanks. That worked for 4.0.3. However, 4.0.4 doesn't seem to work. Keeps throwing an error.

goister said:
Thanks. That worked for 4.0.3. However, 4.0.4 doesn't seem to work. Keeps throwing an error.
Click to expand...
Click to collapse
As of ics recovery you can no longer flash updates manually, that's why its throwing a error
You need CWM or to wait for the OTA
Sent from my ice cream powered Nexus S

2 steps
1) flash CWM, instaructions : http://andwise.net/?p=268
2) update to 4.0.4, instructions: http://andwise.net/?p=275

Thanks. Is there an easier procedure that doesn't involve sending ADB commands? My friend isn't very tech savvy.

goister said:
Thanks. Is there an easier procedure that doesn't involve sending ADB commands? My friend isn't very tech savvy.
Click to expand...
Click to collapse
Its fastboot to flash cwm
If you can't use fastboot your only choice is to wait for OTA
Sent from my ice cream powered Nexus S

andwise said:
2 steps
1) flash CWM, instaructions : http://andwise.net/?p=268
2) update to 4.0.4, instructions: http://andwise.net/?p=275
Click to expand...
Click to collapse
This worked perfectly.
from stock un-rooted 2.3.6 - 4.0.4 OTA Download (fL9fwa99.zip)
t-mobile GT-i9020T

Or once you are on 4.0.3, go to Settings | about Phone | and check for system updates.
You can also try to dial *#*#CHECKIN#*#*

Are the updates global or by region?

Google seems to have released official images for various Nexus S phones, including the i9020t, over at http://code.google.com/android/nexus/images.html
Can these be flashed over 4.0.3 using the stock recovery?

andwise said:
2 steps
[...]
Click to expand...
Click to collapse
Worked like a charm. official 2.3.6 to 4.0.4

goister said:
Google seems to have released official images for various Nexus S phones, including the i9020t, over at http://code.google.com/android/nexus/images.html
Can these be flashed over 4.0.3 using the stock recovery?
Click to expand...
Click to collapse
you can do them with fastboot on bootloader mode but it will erase all you data. Check the first page where i posted 2 steps where you can do an incremental update

[Q] Help Needed: Return to stock Honeycomb 4G LTE

First:
Hoping someone can provide some assistance. I would like to get back to stock ICS 4.0.4 on my Verizon Xoom 4G LTE since i am hoping that 4.1.1 will be released soon OTA. Does anyone have stock 4.0.4 download? With or without root is fine. Stock 3.X would be ok to. I just want to get back to stock.
Second: In case anyone has any ideas
I have several 4.0.4. Nandroids that will not restore for me in CWM. Very recently I did two things that I am wondering if might have caused part of the problem:
1) Upgraded to new CWM 6.0.1.9
2) Flashed a test 4.2 ROM
Thoughts?

puothy said:
First:
Hoping someone can provide some assistance. I would like to get back to stock ICS 4.0.4 on my Verizon Xoom 4G LTE since i am hoping that 4.1.1 will be released soon OTA. Does anyone have stock 4.0.4 download? With or without root is fine. Stock 3.X would be ok to. I just want to get back to stock.
Second: In case anyone has any ideas
I have several 4.0.4. Nandroids that will not restore for me in CWM. Very recently I did two things that I am wondering if might have caused part of the problem:
1) Upgraded to new CWM 6.0.1.9
2) Flashed a test 4.2 ROM
Thoughts?
Click to expand...
Click to collapse
Nevermind....finally found files I was looking for. just took some digging!

Care to share the process? I'm thinking of doing the same thing

nbajwill55 said:
Care to share the process? I'm thinking of doing the same thing
Click to expand...
Click to collapse
I started with MZ602_HLK75D (trying to find where I downloaded from. If you can't find let me know and I will put it on drop box)
You will lose everything on you internal SD card so make sure to pull anything you want off your Xoom before you start. USB Debugging needs to be enabled as well
Extract the MZ602_HLK75D zip file so you have: boot.img, system.img, recovery.img, userdata.img and place these files in your SDK folder
Open a command prompt by SHIFT + RIGHT CLICK on your SDK FOLDER
Adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
After it reboots and you sign in etc it will check for upgrade and there will be a few Honeycomb upgrades before you get back up to 4.0.4 (locked and w/out root & w/out CWM but you can just redo that part too)

I cannot find the file MZ602_HLK75D.zip. Could you provide a link? Thanks.

Let me know if this works:
https://www.dropbox.com/s/cstj6gwxhcfaxm7/MZ602_HLK75D.zip?n=95544115
tselling said:
I cannot find the file MZ602_HLK75D.zip. Could you provide a link? Thanks.
Click to expand...
Click to collapse

puothy said:
Let me know if this works:
https://www.dropbox.com/s/cstj6gwxhcfaxm7/MZ602_HLK75D.zip?n=95544115
Click to expand...
Click to collapse
Thanks

tselling said:
I cannot find the file MZ602_HLK75D.zip. Could you provide a link? Thanks.
Click to expand...
Click to collapse
Motorola has put them back up at -> https://motorola-global-portal.custhelp.com/app/standalone/rom-images

KidJoe said:
Motorola has put them back up at -> https://motorola-global-portal.custhelp.com/app/standalone/rom-images
Click to expand...
Click to collapse
thank you for sharing. Wish I had this several months ago. Took my hours to find a live link so I could download the file.

puothy said:
Let me know if this works:
https://www.dropbox.com/s/cstj6gwxhcfaxm7/MZ602_HLK75D.zip?n=95544115
Click to expand...
Click to collapse
Thanks for the files and instructions. Not planning to return to stock anytime soon but these are good to have just in case.

[RUU] [OTA] T-Mobile US Android 4.3 OTA (3.24.531.3) w/ Nandroid, Firmware & Radio

[RUU] [OTA] T-Mobile US Android 4.3 OTA (3.24.531.3) w/ Nandroid, Firmware & Radio
T-Mobile USA OTA to Android 4.3 Jelly Bean
Build: 3.24.531.3
Android 4.3, Sense 5.0
* includes Wi-Fi Calling​
This is the actual OTA Zip file that is downloaded and then flashed during the update process. I saw that T-Mobile's instructions tell users they must check through their phone, and are not providing a download link.
I extracted it off of my phone's SD Card before I updated, so it is untouched, it comes as T-Mobile distributed it.
DISCLAIMER
I am sharing this so everyone can have access to the official OTA. What you do with it from here is not my responsibility, nor do I care. Enjoy. I am not claiming ownership, nor am I claiming this will be much help by itself.
Update 10/23
The community has spoken, and this has brought a lot of stock options for the end user. As of 10/23 (today), we now have the OTA, a full Nandroid TWRP backup, two versions of the firmware, the radio only and now the RUU itself. The OP has been fully updated with links and credits to everything. Thank you to the Android community, this thread is a pretty great example of open source and people coming together with end products. Thanks for all the help here as well.
DOWNLOADS
RUU
3.24.531.3 T-Mobile RUU: http://forum.xda-developers.com/showthread.php?p=46756958
* thanks to Behold_this
OTA
*UPDATED 10/21 8PM*
My DropBox Link: https://db.tt/MWAGXkFc
Mirror Link: http://www.mediafire.com/?xjwbggpj5pw0l1l
* thanks to Mikey
NANDROIDS
TWRP Backup, No Root: http://forum.xda-developers.com/showpost.php?p=46695324&postcount=50
* thanks to Mikey
FIRMWARE
FIRMWARE (slim): http://forum.xda-developers.com/showpost.php?p=46691733&postcount=30
* does not include: boot.img, recovery.img or hboot.img
* thanks HTC_Phone
FIRMWARE + HBOOT: http://forum.xda-developers.com/showpost.php?p=46694631&postcount=43
* contains modded hboot without red warning text
* thanks to HTC_Phone
RADIO
RADIO: http://forum.xda-developers.com/showpost.php?p=46684321&postcount=339
* flashable radio only zip can be found here
* thanks to Mikey

Thanks for the link

Just removed the radio from this update and made it into a flashable zip........
http://forum.xda-developers.com/showpost.php?p=46684321&postcount=339

Mikey said:
Just removed the radio from this update and made it into a flashable zip........
http://forum.xda-developers.com/showpost.php?p=46684321&postcount=339
Click to expand...
Click to collapse
Any chance you can mirror the OTA? Dropbox terminated the OPs link

frettfreak said:
Any chance you can mirror the OTA? Dropbox terminated the OPs link
Click to expand...
Click to collapse
Uploading it now.......give me a couple minutes

TJD319 said:
T-Mobile USA OTA to Android 4.3 Jelly Bean
Build: 3.24.531.3
Android 4.3, Sense 5.0
* includes Wi-Fi Calling​
This is the actual OTA Zip file that is downloaded and then flashed during the update process. I saw that T-Mobile's instructions tell users they must check through their phone, and are not providing a download link. I am just sharing this with the community for developmental purposes. Hopefully, this may bring Wi-Fi Calling addons to ROMs like ViperOne and others I'm sure.
I extracted it off of my phone's SD Card before I updated, so it is untouched, it comes as T-Mobile distributed it.
DropBox Link: https://db.tt/MWAGXkFc
Click to expand...
Click to collapse
So after hours of searching through the forums, I just wanted to clarify a couple of questions.
I have S-Off and unlocked bootloader but Stock Rom - NOT rooted and stock recovery. I also have the original MID/CID - 0713000 / T-MOB010.
I can still get the latest OTA - 3.24.531.3? The only requirement for the OTA is CID/ MID, stock recovery and stock ROM, correct?
Also, If I go ahead update it, My HBOOT will be updated to 1.54 and Bootloader will be locked but I still will retain s-OFF, correct?
And the only way in future to flash a custom ROM is via, htcdev bootloader unlock?
Thank You!!

Mikey said:
Just removed the radio from this update and made it into a flashable zip........
http://forum.xda-developers.com/showpost.php?p=46684321&postcount=339
Click to expand...
Click to collapse
f_v_man said:
So after hours of searching through the forums, I just wanted to clarify a couple of questions.
I have S-Off and unlocked bootloader but Stock Rom - NOT rooted and stock recovery. I also have the original MID/CID - 0713000 / T-MOB010.
I can still get the latest OTA - 3.24.531.3? The only requirement for the OTA is CID/ MID, stock recovery and stock ROM, correct?
Also, If I go ahead update it, My HBOOT will be updated to 1.54 and Bootloader will be locked but I still will retain s-OFF, correct?
And the only way in future to flash a custom ROM is via, htcdev bootloader unlock?
Thank You!!
Click to expand...
Click to collapse
I am pretty sure you need to relock the bootloader, and have stock recovery. AFAIK those are the requirements. HBOOT may be 1.55 as that is the latest but you SHOULD still keep s-off. But i make no promises. lol But yes, you will have to go to HTCDEV and get your unlock key again if you wantt o flash another rom (its a really easy process though)

TJD319 said:
T-Mobile USA OTA to Android 4.3 Jelly Bean
Build: 3.24.531.3
Android 4.3, Sense 5.0
* includes Wi-Fi Calling​
This is the actual OTA Zip file that is downloaded and then flashed during the update process. I saw that T-Mobile's instructions tell users they must check through their phone, and are not providing a download link. I am just sharing this with the community for developmental purposes. Hopefully, this may bring Wi-Fi Calling addons to ROMs like ViperOne and others I'm sure.
I extracted it off of my phone's SD Card before I updated, so it is untouched, it comes as T-Mobile distributed it.
DropBox Link: https://db.tt/MWAGXkFc
Click to expand...
Click to collapse
Anyways to get a nandroid or to pull /system on an installed update.

I'm currently on a custom 4.2.2 ROM with Firmware 2.24.401.1, HBOOT 1.54, S-OFF, Super CID, and TWRP 2.6 bootloader on T-Mobile HTC One.
What is the process to upgrade to this OTA? Or is there a better to go to latest base, firmware, etc.?

Mikey said:
Uploading it now.......give me a couple minutes
Click to expand...
Click to collapse
Here you go
http://www.mediafire.com/download/xjwbggpj5pw0l1l/OTA_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3-1.27.531.11_release_337024c11bis4e2ha8yy5i.zip

I was on a rooted stock TMo ROM in order to get the update. However, i kept my Bootloader unlocked S-OFF, and I was rooted. Only thing really required is the stock odexed 4.1.2 ROM and the Stoxk boot and Recovery. SOFF doesnt matter, for me it didnt.
I was on Viper 4.2.2. I restored a nandroid of my stock 4.1.2 rooted, and all I then did was flash TMO stock recovery in fastboot.
Sent from my HTC One using XDA Premium 4 mobile app

TJD319 said:
I was on a rooted stock TMo ROM in order to get the update. However, i kept my Bootloader unlocked S-OFF, and I was rooted. Only thing really required is the stock odexed 4.1.2 ROM and the Stoxk boot and Recovery. SOFF doesnt matter, for me it didnt.
I was on Viper 4.2.2. I restored a nandroid of my stock 4.1.2 rooted, and all I then did was flash TMO stock recovery in fastboot.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The OTA doesn't help developers, they need the patched APK's after the OTA is installed.

SmiLey497 said:
The OTA doesn't help developers, they need the patched APK's after the OTA is installed.
Click to expand...
Click to collapse
I was answering someone's question about if they need the bootloader relocked or not.
As far as the devs go, now they've got the OTA and can do whatever they or anyone else wants with it. Its not really a crime to share.
Sent from my HTC One using XDA Premium 4 mobile app

Thanks for the upload. Question, to flash this, its just like flashing a firmware update, with the silver HTC on the screen? Pushed through ADB?
Rob

cvseuy said:
I'm currently on a custom 4.2.2 ROM with Firmware 2.24.401.1, HBOOT 1.54, S-OFF, Super CID, and TWRP 2.6 bootloader on T-Mobile HTC One.
What is the process to upgrade to this OTA? Or is there a better to go to latest base, firmware, etc.?
Click to expand...
Click to collapse
1. Restore nandroid backup for stock 4.1.2
2. Make sure boot.img and recovery.img are from stock T-Mobile.
3. Get OTA
OR
Download and install the stock T-Mobile ODEX ROM. Flash the ROM, doesnt matter if its rooted or not. Make sure it has stock recovery and boot images. And you can get OTA.
Sent from my HTC One using XDA Premium 4 mobile app

TJD319 said:
I was answering someone's question about if they need the bootloader relocked or not.
As far as the devs go, now they've got the OTA and can do whatever they or anyone else wants with it. Its not really a crime to share.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Said by a developer
"ota is just a patch, patches the existing files, with new code, there isn't a whole apk there. is useless unless you have a phone to apply patch on and then pull system"
that's why I was asking. No ROM can include stuff like Wi-Fi calling without the patched APK's.

i noticed this is a higher build number compared to the att 4.3 version

SmiLey497 said:
Said by a developer
"ota is just a patch, patches the existing files, with new code, there isn't a whole apk there. is useless unless you have a phone to apply patch on and then pull system"
that's why I was asking. No ROM can include stuff like Wi-Fi calling without the patched APK's.
Click to expand...
Click to collapse
Once again, i completely get this and for someone who wants to provide a full system dump would be great. But im not wiping yet, so i cant do that. Also, the OTA file contains an encrypted firmware.zip file which is completely independent of the patched apks. That's why Mikey posted the Radio. This is the whole reason I gave it to the community.
Anyway, im done. Im not trying to argue about some stupid OTA. If you don't want it, then don't download it.
Sent from my HTC One using XDA Premium 4 mobile app

So, I noticed a problem on 4.3 when trying to boot a recovery in fastboot. According to the following thread, Android 4.3 bootloader has changed the function of this fastboot command:
Code:
fastboot boot recovery_twrp.img
Reference URL of same solved issue on N4: http://forum.xda-developers.com/showthread.php?t=2380675
Now, we have to retrigger the command somehow inputting the right information in. When i ran the regular command, it says downloading ...OK and goes through the regular steps, but the phone hangs on the bootloader screen.
It never actually loads the custom recovery, just completely freezes the bootloader. I tried a couple different recoveries (CWM, TWRP) and they just don't do anything except lock up the phone.
I want to preserve my stock partitions and make a backup. I plan to go back to my 4.1.2 and perform the update, then load it and wipe so i can provide the stock nandroid backup for full throttle development. So if anyone knows the current command to boot a custom recovery in fastboot on 4.3, let me know.
Sent from my HTC One using XDA Premium 4 mobile app

TJD319 said:
So, I noticed a problem on 4.3 when trying to boot a recovery in fastboot. According to the following thread, Android 4.3 bootloader has changed the function of this fastboot command:
Code:
fastboot boot recovery_twrp.img
Reference URL of same solved issue on N4: http://forum.xda-developers.com/showthread.php?t=2380675
Now, we have to retrigger the command somehow inputting the right information in. When i ran the regular command, it says downloading ...OK and goes through the regular steps, but the phone hangs on the bootloader screen.
It never actually loads the custom recovery, just completely freezes the bootloader. I tried a couple different recoveries (CWM, TWRP) and they just don't do anything except lock up the phone.
I want to preserve my stock partitions and make a backup. I plan to go back to my 4.1.2 and perform the update, then load it and wipe so i can provide the stock nandroid backup for full throttle development. So if anyone knows the current command to boot a custom recovery in fastboot on 4.3, let me know.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You ran this one correct,
Code:
fastboot -c "lge.kcal=0|0|0|x" boot twrp.img
because that's the only solution I've seen so far, I'll try to look further.

Updating Baseband/Modem before flash 4.3 ROM

I've scoured the forum looking for an answer to my exact question but haven't come up with one that really satisfies it.
I'm looking to flash a 4.3 ROM (probably old&slow's:http://forum.xda-developers.com/showthread.php?t=2591895).
I'm currently running CleanROM 7 (http://forum.xda-developers.com/showthread.php?t=1832070).
In the thread it states it was based off VRBMF1 firmware. old&slow states (as do most other 4.3 ROM dev's for issues relating to the partition structure I believe) that you have to be running ML1 or earlier bootloader.
My baseband version is LG7 (I535VRLG7).
I guess my question is two fold. I'm a bit confused on the semantics. So I'm getting that generally the bootloader matches up with the baseband version. But in my case because my ROM and Baseband are mismatched, it seems like I'm running a newer bootloader (MF1) then my baseband (LG7)?
My real question is do I need to flash a new Baseband or Firmware (or Both) before doing any ROM flashing?
I understand invisiblek's post about only giving the baseband update. So should I flash the latest baseband?
Will any of this have any effect if I decide to flash a 4.4 ROM?
Any help is much appreciated!

justinnotjason said:
I've scoured the forum looking for an answer to my exact question but haven't come up with one that really satisfies it.
I'm looking to flash a 4.3 ROM (probably old&slow's:http://forum.xda-developers.com/showthread.php?t=2591895).
I'm currently running CleanROM 7 (http://forum.xda-developers.com/showthread.php?t=1832070).
In the thread it states it was based off VRBMF1 firmware. old&slow states (as do most other 4.3 ROM dev's for issues relating to the partition structure I believe) that you have to be running ML1 or earlier bootloader.
My baseband version is LG7 (I535VRLG7).
I guess my question is two fold. I'm a bit confused on the semantics. So I'm getting that generally the bootloader matches up with the baseband version. But in my case because my ROM and Baseband are mismatched, it seems like I'm running a newer bootloader (MF1) then my baseband (LG7)?
My real question is do I need to flash a new Baseband or Firmware (or Both) before doing any ROM flashing?
I understand invisiblek's post about only giving the baseband update. So should I flash the latest baseband?
Will any of this have any effect if I decide to flash a 4.4 ROM?
Any help is much appreciated!
Click to expand...
Click to collapse
Baseband (radio) is kind of your own taste and choice, some are doing great with older baseband and some are doing better with newer baseband. If you don't have any issue with signal drops or such then you can keep your baseband. Flashing a 4.4 rom which don't include baseband (baseband only included with full stock firmware). Or later, if you decided to flash new basaeband it would be fine too. If you're using MF1 baseband you should be OK to flash 4.4 rom.

buhohitr said:
Baseband (radio) is kind of your own taste and choice, some are doing great with older baseband and some are doing better with newer baseband. If you don't have any issue with signal drops or such then you can keep your baseband. Flashing a 4.4 rom which don't include baseband (baseband only included with full stock firmware). Or later, if you decided to flash new basaeband it would be fine too. If you're using MF1 baseband you should be OK to flash 4.4 rom.
Click to expand...
Click to collapse
Makes sense. I'd probably prefer to be running a newer baseband since my current one does, once in a blue moon, cut out. But I'd probably wait until after I've flashed a rom and know it's working before doing it. Just so I can isolate any issues that pop up from either flash.
But you're saying that I'm right to think that my bootloader is MF1 and my baseband is fine at LG7?

justinnotjason said:
Makes sense. I'd probably prefer to be running a newer baseband since my current one does, once in a blue moon, cut out. But I'd probably wait until after I've flashed a rom and know it's working before doing it. Just so I can isolate any issues that pop up from either flash.
But you're saying that I'm right to think that my bootloader is MF1 and my baseband is fine at LG7?
Click to expand...
Click to collapse
You can go up to MB1 modem which is the latest just before ML1 (4.3 modem). I believe LG7 is ICS modem which is old...pretty old.

buhohitr said:
You can go up to MB1 modem which is the latest just before ML1 (4.3 modem). I believe LG7 is ICS modem which is old...pretty old.
Click to expand...
Click to collapse
Thanks. Yeah, I didn't update the firmware/radio when I upgraded to JB. I just flashed the MF1 firmware/baseband and all seems good. Will use it over the next day and rom tomorrow.
After the firmware update my s3 is trying to run software update. I'm still trying to search what files I need to rename to stop this (I did it last year when I ROM'd my phone initially).

justinnotjason said:
Thanks. Yeah, I didn't update the firmware/radio when I upgraded to JB. I just flashed the MF1 firmware/baseband and all seems good. Will use it over the next day and rom tomorrow.
After the firmware update my s3 is trying to run software update. I'm still trying to search what files I need to rename to stop this (I did it last year when I ROM'd my phone initially).
Click to expand...
Click to collapse
If the OTA already downloaded, delete it here /cache/fota
To disable the OTA:
Rename or freeze the apps with Titanium backup:
otacerts.zip located in /etc/security - rename to otacerts.zip.bak
Rename fwupdate.odex, fwupdate.apk located in /system/app
and freeze SDM1.0 located in /system/app

buhohitr said:
If the OTA already downloaded, delete it here /cache/fota
To disable the OTA:
Rename or freeze the apps with Titanium backup:
otacerts.zip located in /etc/security - rename to otacerts.zip.bak
Rename fwupdate.odex, fwupdate.apk located in /system/app
and freeze SDM1.0 located in /system/app
Click to expand...
Click to collapse
EDIT:
Thanks.
Now I'm just troubleshooting why I can't seem to rename otacerts or change permissions. It's like SuperSU isn't giving it root permissions, but I granted it....weird....
ES File Explorer is giving me a "task failed" when I try to rename it. When I delete it it says "read-only" file system. I realize I need to mount it as R/W but when I try to change permissions in properties it gives me a "Sorry, Operation Failed".
I must be missing a step...hmmmm

justinnotjason said:
EDIT:
Thanks.
Now I'm just troubleshooting why I can't seem to rename otacerts or change permissions. It's like SuperSU isn't giving it root permissions, but I granted it....weird....
ES File Explorer is giving me a "task failed" when I try to rename it. When I delete it it says "read-only" file system. I realize I need to mount it as R/W but when I try to change permissions in properties it gives me a "Sorry, Operation Failed".
I must be missing a step...hmmmm
Click to expand...
Click to collapse
Try using Root Browser instead (free app in Play Store, seems I have more success renaming files using RB versus ES File Explorer).

justinnotjason said:
But you're saying that I'm right to think that my bootloader is MF1
Click to expand...
Click to collapse
No, you are wrong to think that. If you're on a custom rom then you're definitely not on a "VRBMF1" bootloader. Your bootloader is the same one we are all using, from a pre-release, S3 with an unlocked bootloader on ICS.
Sent from my SCH-I535 using Tapatalk 4

Nomad1600 said:
Try using Root Browser instead (free app in Play Store, seems I have more success renaming files using RB versus ES File Explorer).
Click to expand...
Click to collapse
Huh...interesting...that worked without a hitch....Thank you!
SlimSnoopOS said:
No, you are wrong to think that. If you're on a custom rom then you're definitely not on a "VRBMF1" bootloader. Your bootloader is the same one we are all using, from a pre-release, S3 with an unlocked bootloader on ICS.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I see.....i just flashed the MF1 firmware zip from the link provided in invisiblek's thread (http://forum.xda-developers.com/showthread.php?t=1788313), would that have updated my bootloader? How would I even tell on this phone. I read somewhere the information is provided in recovery someplace.

justinnotjason said:
I see.....i just flashed the MF1 firmware zip from the link provided in invisiblek's thread (http://forum.xda-developers.com/showthread.php?t=1788313), would that have updated my bootloader? How would I even tell on this phone. I read somewhere the information is provided in recovery someplace.
Click to expand...
Click to collapse
Just stop thinking about the bootloader lol you only need to be concerned about the bootloader if you're going from fresh, out of the box S3 to rooted and unlocked bootloader prior to flashing a custom rom OR if you accepted this 4.3 OTA (because the bootloader is locked). Generally the build number and the baseband will match. Pretty sure that's what you mean. The build number is which OTA the rom is based on. The bootloader is of no concern for you so long as you continue to flash custom roms and ignore OTAs.
Sent from my SCH-I535 using Tapatalk 4

SlimSnoopOS said:
Just stop thinking about the bootloader lol you only need to be concerned about the bootloader if you're going from fresh, out of the box S3 to rooted and unlocked bootloader prior to flashing a custom rom OR if you accepted this 4.3 OTA (because the bootloader is locked). Generally the build number and the baseband will match. Pretty sure that's what you mean. The build number is which OTA the rom is based on. The bootloader is of no concern for you so long as you continue to flash custom roms and ignore OTAs.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Ah I see. Makes sense.
Nah I was actually curious about the bootloader, but your post makes sense. Seems like as longs as it's unlocked, not to worry about it.
And yeah I understand the build number, and I just updated my baseband. I suppose I'll start looking into flashing some newer ROMs.
The only thing I noticed was that I have to update my CWM to flash any 4.4 ROMs. So I'm gunna look into that.