Database Info

So lost.. need help

So I (foolishly) tried to root and flash the Android Revolution ROM onto my phone but as I should have expected, I failed.I have a plethora of problems, and I am not sure what my best course of action is:
so
1) I factory reset, so I have no recovery or ROM on my phone currently
2)My phone is in a bootloop (loads the HTC screen with a disclaimer saying "this build is for development... yadda yadda yadda" and then reboots
3)My phone will NOT powerdown, I have tried to power down my phone through bootloader, and it re"boots" and returns to bootloader once again.
4)I cannot flash any files from my PC to my phone, for example: When I try to flash boot_signed.img from the Rogers Evita Stock ROM, using
fastboot flash boot boot_signed.img, I get an error message saying "FAILED <remote: signature verify fail>" and this occurs for all files I have tried to flash
5)I have tried using ARUWizard to try and get the stock ROM onto my phone with no avail. From reading the forums I believe it is because my phone is using version 1.94.631.3 but the ARUWizard can only update to previous versions which is not allowed? (I am still very confused about this) one alternative I found on the forums was to create something called a goldcard but that required a microSD card which my phone does not have capabilities for.
So this is my dilemma, I think I am thoroughly screwed... any help or advice would be appreciated

You should still have twrp recovery even if you factory reset. Reboot into twrp, mount sd, transfer over a Rom that will work, wipe all and flash
Sent from my One X using xda premium

The_Zodiac said:
You should still have twrp recovery even if you factory reset. Reboot into twrp, mount sd, transfer over a Rom that will work, wipe all and flash
Sent from my One X using xda premium
Click to expand...
Click to collapse
I go to recovery, and it just goes immediately back to bootloader :s

I suggest starting with this thread and see what results you get.
You flashed a ROM for a different device that has a different partition layout, and that ROM installer may have possibly wiped out your partitions and left the device unrecoverable except through a JTAG brick repair

Have you tried flashing twrp again?
Sent from my One X using Xparent Green Tapatalk 2

If you're getting to the splash screen, you're not bricked. Don't start the unbricking stuff yet.
You need to get to bootloader and push a new recovery image. You probably screwed up your recovery partition when you flashed that Tegra 3 rom.
Once you've got recovery back, you just need to flash a correct rom.
If that doesn't work, try running a ruu from bootloader.

iElvis said:
If you're getting to the splash screen, you're not bricked. Don't start the unbricking stuff yet.
You need to get to bootloader and push a new recovery image. You probably screwed up your recovery partition when you flashed that Tegra 3 rom.
Once you've got recovery back, you just need to flash a correct rom.
If that doesn't work, try running a ruu from bootloader.
Click to expand...
Click to collapse
Okay, Ive got recovery back, but I need help either flashing the rom or running a ruu from bootloader. I am unsure of how to do either.
I tried flashing my ROM using:
fastboot flash ROM PJ83IMG.zip
but then I got the FAILED <remote: signature verify fail> message again

paoul.sukii said:
Okay, Ive got recovery back, but I need help either flashing the rom or running a ruu from bootloader. I am unsure of how to do either.
I tried flashing my ROM using:
fastboot flash ROM PJ83IMG.zip
but then I got the FAILED <remote: signature verify fail> message again
Click to expand...
Click to collapse
If you have recovery again why not try the method I listed?
Sent from my One X using xda premium

paoul.sukii said:
Okay, Ive got recovery back, but I need help either flashing the rom or running a ruu from bootloader. I am unsure of how to do either.
I tried flashing my ROM using:
fastboot flash ROM PJ83IMG.zip
but then I got the FAILED <remote: signature verify fail> message again
Click to expand...
Click to collapse
Just go into your custom recovery, mount sdcard, move the rom over, and flash in recovery.

The_Zodiac said:
If you have recovery again why not try the method I listed?
Sent from my One X using xda premium
Click to expand...
Click to collapse
Alright, well i tried installing the ZIP I had, and it said it failed...
Maybe I should try a different zip? could someone suggest a good ROM for me that is compatible with my phone? (dont want to make the same mistake again)
I just want a ROM that has Sense, and is running at least ICS. Stability and speed are my main concerns, thanks!

paoul.sukii said:
Alright, well i tried installing the ZIP I had, and it said it failed...
Maybe I should try a different zip? could someone suggest a good ROM for me that is compatible with my phone? (dont want to make the same mistake again)
I just want a ROM that has Sense, and is running at least ICS. Stability and speed are my main concerns, thanks!
Click to expand...
Click to collapse
Before you do anything else, you should probably double check what phone you have.
Android Revolution HD (http://forum.xda-developers.com/showthread.php?t=1562603) is NOT for the AT&T/Rogers One X or the Telstra One XL.
If you have an international One X, then you're in the wrong place. If you do have one of the phones listed above, then you need to go here and download one of those roms. Then flash using what The_Zodiac suggested.

jeffwyeh said:
Before you do anything else, you should probably double check what phone you have.
Android Revolution HD (http://forum.xda-developers.com/showthread.php?t=1562603) is NOT for the AT&T/Rogers One X or the Telstra One XL.
If you have an international One X, then you're in the wrong place. If you do have one of the phones listed above, then you need to go here and download one of those roms. Then flash using what The_Zodiac suggested.
Click to expand...
Click to collapse
If I have the HTC One X Evita with Rogers, will http://forum.xda-developers.com/showthread.php?t=1868236&highlight=rogers work?

paoul.sukii said:
If I have the HTC One X Evita with Rogers, will http://forum.xda-developers.com/showthread.php?t=1868236&highlight=rogers work?
Click to expand...
Click to collapse
Yessir, that'll work. (I've heard good things about that ROM, though I haven't tried it myself).
Just FYI, the One X on AT&T and Rogers is known internationally as the One XL, and as far as codenames go, is known as the Evita, as you pointed out. The international One X is the Endeavor, and ROMs are not cross-compatible. If you stay in the "AT&T, Rogers HTC One X, Telstra One XL" sub-forums here, you should be alright.

What version of twrp are you using? Try rolling back to a 2.3.x version. 2.4.x seems to have some issues.

iElvis said:
What version of twrp are you using? Try rolling back to a 2.3.x version. 2.4.x seems to have some issues.
Click to expand...
Click to collapse
Okay, I think I am going to go to bed, and try to approach this problem tomorrow.
I am running TWRP 2.4.x so I may try and downgrade that tomorrow. I used adb to push the ROM to my phone and it is on my sdcard
However, when I try to install the ROM, it tells me that it failed... I tried clearing all caches etc but i keep getting the same errors. The weirdest part is that when I reboot my phone, the ROM disappears...
The error that I am getting is:
E:Unable to mount '/sdcard'
E:Unable to recreate android secure folder.
E:Unable to mount '/sdcard'
E:unable to mount '/sdcard'
Updating partition details...
E:Unable to mount storage.
E:Unable to mount /sdcard during GUI startup.
Running boot script...
Finished running boot script.
E:Unable to mount /sdcard when trying to read settings file.
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
Click to expand...
Click to collapse
This is the message that is displayed in recovery, to the letter, I'm not sure if this helps...
Obviously something to do with my sdcard is wrong, preventing connection between the sdcard and something else, but maybe you guys could dig deeper, past the elementary
Thank you guys for the help you've given me so far, the outlook for my phone is much brighter now, I will check back tomorrow and continue to try and fix my phone!

Your sdcard is indeed corrupted.
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL
Walk through that guide using the files for the Evita on that page, it should fix your sdcard. After that you can go ahead and push the rom to the sdcard again and then reflash and see if that does the trick!

jeffwyeh said:
Your sdcard is indeed corrupted.
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL
Walk through that guide using the files for the Evita on that page, it should fix your sdcard. After that you can go ahead and push the rom to the sdcard again and then reflash and see if that does the trick!
Click to expand...
Click to collapse
Thank all of you so much! my problem is resolved! Phone is working great!

paoul.sukii said:
Thank all of you so much! my problem is resolved! Phone is working great!
Click to expand...
Click to collapse
Awesome! Glad to hear it!

twrp problem - cannot see files

So I installed ASUS 4.2.1 Build 10.6.1.15.3. I followed the instructions for installing the twrp.blob via fastboot. All of this worked.
Now when boot into recovery mode, TWRP sees no files. If you click the log on the upper right hand side, it's filled with errors like:
E:Unable to find partition size for '/misc'
E:Unable to find partition size for '/staging'
E:Unable to find partition size for '/data'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
E:Unable to mount '/cache'
And so on... I cannot see the files that I have placed in the folders both for internal storage and for a 8GB Micro SD. I'm at a loss. At this point, I'm not even sure how to reflash the ASUS image so that I might start completely over, though I don't know why I'd want to. Any ideas?

I was having the same issue and this worked for me http://forum.xda-developers.com/showthread.php?t=1672108&page=76&nocache=1. its a couple of post down.

Sounds like you flashed a recovery with -JB at the end instead of -42. The -JB recoveries are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader (OTA version 10.6.x). ASUS changed a bunch of important filesystem stuff in the 4.2 bootloader. When you flashed the 4.1 recovery, it erased all your device nodes (the file representation of the hardware on the system, specifically where each filesystem partition resides), so as far as your recovery is concerned, you don't have any internal storage. That's why it can't open anything.
So far, nobody has been able to recover a tablet in this condition.
Also, this is the wrong section. This thread belongs in the Q&A section. It has nothing to do with development.

EndlessDissent said:
Sounds like you flashed a recovery with -JB at the end instead of -42. The -JB recoveries are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader (OTA version 10.6.x). ASUS changed a bunch of important filesystem stuff in the 4.2 bootloader. When you flashed the 4.1 recovery, it erased all your device nodes (the file representation of the hardware on the system, specifically where each filesystem partition resides), so as far as your recovery is concerned, you don't have any internal storage. That's why it can't open anything.
So far, nobody has been able to recover a tablet in this condition.
Also, this is the wrong section. This thread belongs in the Q&A section. It has nothing to do with development.
Click to expand...
Click to collapse
I used fastboot and rewrote the recovery with the "42" one and it fixed my issues.

Ah. I apologize for picking the wrong section. So there's no way to reflash my device via fastboot?

maddog94d said:
I used fastboot and rewrote the recovery with the "42" one and it fixed my issues.
Click to expand...
Click to collapse
Wow. Ok, let me give that a shot.

maddog94d said:
I used fastboot and rewrote the recovery with the "42" one and it fixed my issues.
Click to expand...
Click to collapse
That doesn't work for most people. Typically, the tablet freezes as soon as fastboot tries to write anything. The correct recovery can never be flashed. Maybe you got lucky. Maybe your situation was slightly different.
Also, the link you posted doesn't seem to lead to a post with any sort of guide. On my phone, in the XDA Premium app, it opens the last page of the TWRP thread, specifically to f69m's most recent post, in which he says that this situation has caused lots of bricks. Ironic, IMO.

sorry bout where the link lead to. it was on the last page explaining what happened. maybe i did get lucky, all i did was the same method for fastboot for the recovery install.

And it worked. Thanks for the head's up. Sorry again for choosing the wrong forum.

I didn't use the link. I just reflashed the 42 twrp using fastboot and it worked.

Glad it worked for you.... maybe 2 of us got lucky lol

maddog94d said:
sorry bout where the link lead to. it was on the last page explaining what happened. maybe i did get lucky, all i did was the same method for fastboot for the recovery install.
Click to expand...
Click to collapse
Other than one poor soul being told that his tablet might be bricked, there is nothing on that page dealing with the OP's problem. The other posts are about flashing a -42 recovery on the 10.6.1.8 OTA and having to update to the 10.6.1.15.3 OTA to fix it.
Edit: it seems like I'm trying to argue something. I'm not. I'm just confused about exactly where the link should have gone.
Also, maybe the fact that you and the OP are on the newest OTA made a difference. Almost everybody I've seen with that problem did it on the first 4.2 OTA. Maybe ASUS fixed something in the newest updates. The newest updates fixed custom recoveries in general, so it could have had other fixes, like for fastboot.

The real question now, is it safe to use custom ROM's on top of this 4.2.2 JB? I suddenly am worried about messing with it...

strakajagr said:
The real question now, is it safe to use custom ROM's on top of this 4.2.2 JB? I suddenly am worried about messing with it...
Click to expand...
Click to collapse
As long as you pay attention to which recovery you're using, there shouldn't be a big problem. That is, if you're positive that the fix worked. Have you made any backups or tried wiping cache/Dalvik? The recovery no longer gives you "can't mount" errors?
If it seems to be working properly, flashing ROMs shouldn't be an issue, but I don't blame you for being cautious. If in doubt, just stick to the stock ROM.

Right, I'm in business. I already used it to flash superuser, and then verified that I have root. Everything seems to be in order.
I'd been using 10.6.1.15.3, so maybe that's why this worked.

Same thing happened to me. It ended up being that i was on the older OS. I followed this thread to the T
http://forum.xda-developers.com/showthread.php?t=2187982
Works perfect!
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

Hi!
Also, here has been described the same situation, in the simplest way possible !
Good luck !

I don't have fastboot or adb available to use, am I out of luck?
Mine just boots into twrp every time. Cannot mount anything. No recovery available on boot. I just get the unlocked message in the top left corner on boot. I can't even stop the boot using the volume buttons. How can I get fastboot/adb back?

Hmmmm....
strakajagr said:
I didn't use the link. I just reflashed the 42 twrp using fastboot and it worked.
Click to expand...
Click to collapse
Two folks who "got lucky." Interesting.

Thread moved,
Please keep all questions to the Q&A section, the development section is for development threads only

[Q] Same thing, only different.

Okay, I have the same problem as the guy in this thread: https://forum.xda-developers.com/showthread.php?t=2571779&highlight=wiped+all+partitions , but only have a few differences. I now have no sdcard or sdcard\ext partitions... Says zero megs. Thankfully I back my stuff up everytime I sync up to my pc. Anywho, I believe I need to run RUU mode and reinstall ICS factory. Here is what happened: I have had the phone rooted and S-OFF for about a week and have made a few backups. I went into recovery and made another backup. Rebooted into system, saved contacts, and rebooted back into bootloader by accident. Well when I went to hit "recovery" option, I went down one too any times and hit factory reset. Now, when I go into recovery, there is not any restore points, nor any sdcard options available. I cant mount up usb mass storage in TWRP because there is no sdcard partition...Hrmmmmm...... I guess the actual question is, "Do I need to run RUU and that will probably, maybe fix it?"
Tid Bits:
TWRP v2.6.3.0
***tampered***
***unlocked***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT- 2.14.0000
RADIO- 0.24P.32.09.06
OpenDSP- v34.1.0.45.1219
eMMC-boot

Its a known issue that doing a factory reset in bootloader on a modded EVITA corrupts the SD card. Plug the phone into a Windows PC, go to device manager, find the SD and format it FAT32. Its that simple.
Question 16 in the FAQs: http://forum.xda-developers.com/showthread.php?t=2136172

at which point i should be able to push a rom to the phone and get my OS back, correct? as of right now, i have no OS, but full recovery.

That's right. Format it then copy a ROM across to flash.
Sent from my Evita

Just did that. Had to reflash superSU before flshing a rom. It will not flash the ROM, it says that E: Error executing updater binary in zip 'blah, blah,blah' It did this with the last ROM i tried flashing. Any ideas?

lil_phreek said:
Just did that. Had to reflash superSU before flshing a rom. It will not flash the ROM, it says that E: Error executing updater binary in zip 'blah, blah,blah' It did this with the last ROM i tried flashing. Any ideas?
Click to expand...
Click to collapse
What ROM are you trying to flash, and what recovery are you using?
Sent from my One X using XDA Premium 4 mobile app

TWRP 2.6.3
Illusion 4.4.2

lil_phreek said:
TWRP 2.6.3
Illusion 4.4.2
Click to expand...
Click to collapse
Are you using the modified version of 2.6.3.0? The official version won't flash 4.4 ROMs. Also, there's no need to flash any Superuser zip, but if there was you'd need to flash it after the ROM.
Sent from my Evita

lil_phreek said:
TWRP 2.6.3
Illusion 4.4.2
Click to expand...
Click to collapse
There have been multiple reports in that thread of failed flashings with the unofficial twrp. There are some CWM versions available for 4.4 Roms though. I think the first few pages of the Beanstalk thread should get you going with that.
Sent from my One X using XDA Premium 4 mobile app

"wishing I was Kenny right now" My mistake on not paying attention to the fine print....I will check out that other thread. Thanks. I will post in a bit and let you guys know how it works out for me.

Don't forget to click the "Thanks" button for any posts that you found helpful.

Sorry for the delay guys. Literally as soon as I got my phone fixed, my laptop, which I use for all my necessary phone needs, slowly closed all its windows down, shut off, and mysteriously lost its OS.... LOL, one thing fixed, another down. Oh well. Anyway, I did exactly as was said in the other thread, and it worked like a charm. I am currently running Beanstalk 4.4, and it is an amazing rom. Love it. And thanks for all the help. I am heading back over to the Infuse forum to try and fix the other phone....

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.

[Q] Nexus 5 rooted

I recently rooted my Nexus 5 to 4.4.2 from Chainfire, but I didn't think too much about it.
Now I wonder, what happens when the phone will want to update to 4.4.3 (or whatever the new version will be)?
Will it cause problems? Will it update without problems? Will I have to erase all data and flash the stock build?

If there was a 4.4.3 update, you probably won't have to erase your data. You will probably keep root and nothing will happen. Might see a new system app installed, but that is pretty much it

But, will I have to download the build from Chainfire, or will the OTA just work normally?

The OTA should work just fine.

BigLisy said:
But, will I have to download the build from Chainfire, or will the OTA just work normally?
Click to expand...
Click to collapse
The OTA will work fine until you install a custom firmware
Sent from my Nexus 5 using Tapatalk

AFAIK, if you want to install an OTA update, you need to have a stock recovery as well! Since your rooted, OTA updating your device can create problems.
Correct me if I'm wrong..

BigLisy said:
I recently rooted my Nexus 5 to 4.4.2 from Chainfire, but I didn't think too much about it.
Now I wonder, what happens when the phone will want to update to 4.4.3 (or whatever the new version will be)?
Will it cause problems? Will it update without problems? Will I have to erase all data and flash the stock build?
Click to expand...
Click to collapse
Hi,
Take a look here: [INFO] Nexus 5 OTA Help-Desk...

Please just read "OTA help-desk" thread in General.

rootSU said:
Please just read "OTA help-desk" thread in General.
Click to expand...
Click to collapse
+1 there is a lot of misinformation in this thread
Sent from my Nexus 5

vin4yak said:
AFAIK, if you want to install an OTA update, you need to have a stock recovery as well! Since your rooted, OTA updating your device can create problems.
Correct me if I'm wrong..
Click to expand...
Click to collapse
you are wrong.
custom recoveries only prevent the OTA from installing automatically on reboot (if that)

Zepius said:
you are wrong.
custom recoveries only prevent the OTA from installing automatically on reboot (if that)
Click to expand...
Click to collapse
I've had no issues installing the ota with twrp. of course you lose the custom recovery and the stock recovery Is installed.
Sent from my Nexus 5