Does anyone have or know where to get this update. Iam looking for the actual OTA, unmodified, untouched rom. I figure they would have it posted in these forums, but all i am finding is modified ucla 2.3.6.
right now, both cdshepherd's and silver03wrx's 2.3.6 UCLA3 roms are 'stock'. I guess it depends on what you mean "bone stock". Both of their roms were directly extracted from the system dump of the recent ATT OTA update. As a matter of fact silver and others were able to extract the stock UCLA3 modem and UCLA3 kernel and package them up as separate zips... their roms now have the kernel baked in as well. cd and silver will most likely be taking their roms and customizing (i.e., theming, new features, debloating etc), but for now (2/25/12), they are both based on same stock system dump.
Think he means a rom that's not rooted, untouched, unthemed, etc. I'm honestly looking for the same thing... A UCLA3, untouched rom that you can flash in CWM would be nice.
Only thing is that I believe they needed root access in order to pull the rom from their phone after they updated, so all the builds they pulled/copied from their phone have root.
Fortune090 said:
Think he means a rom that's not rooted, untouched, unthemed, etc. I'm honestly looking for the same thing... A UCLA3, untouched rom that you can flash in CWM would be nice.
Only thing is that I believe they needed root access in order to pull the rom from their phone after they updated, so all the builds they pulled/copied from their phone have root.
Click to expand...
Click to collapse
Amen, yes that is what I would like too. Although I am not sure it would be possible to get that without root? A "dd" command would need root, and also a new recovery (if going the nandroid route). I would be curious as to how to take a "dump" of all partitions without being rooted.
i believe this rom has the att bloatware removed.
http://forum.xda-developers.com/showthread.php?t=1509978
Related
Hi all, I am looking for a rooted stock ROM.
I know, I could take a stock ROM, install it, unlock my phone, install SU, relock it.
But I would loose all of my data.
Is there a stock rooted rom flashable with CWM available?
TIA
lmerega said:
Hi all, I am looking for a rooted stock ROM.
I know, I could take a stock ROM, install it, unlock my phone, install SU, relock it.
But I would loose all of my data.
Is there a stock rooted rom flashable with CWM available?
TIA
Click to expand...
Click to collapse
There are nandroid copies of stock 2.3.3 in the development section.
The problem is, if you flash one of those, you're going to lose all your data anyways, aren't you? At least the stuff not on your sdcard.
Also, unless you're still on the 2.3.2 and below bootloader you can't flash clocwork recovery without unlocking the bootloader.
I could probably give clearer advice if I knew what state your phone is currently in:
I assume your bootloader is locked since you don't want to unlock it, but what version of the OS are you on? Are you already rooted on a pre-2.3.3 rom? Do you have titanium backups of your apps/data?
lmerega said:
Hi all, I am looking for a rooted stock ROM.
I know, I could take a stock ROM, install it, unlock my phone, install SU, relock it.
But I would loose all of my data.
Is there a stock rooted rom flashable with CWM available?
TIA
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=971690
The above is exactly that, but it is also deodexed.
Master™ said:
http://forum.xda-developers.com/showthread.php?t=971690
The above is exactly that, but it is also deodexed.
Click to expand...
Click to collapse
Now I have yours installed, but I cannot understend hat is the difference between deodexed and original.
I mean, I know you can theme a deodexed rom, but I cannot understand the REAL difference.
I mean: deodexed and stoch are identical?
No.
Why? What is not included in the deodexed one?
Why shoud it be better than a stock one?
[EDIT] Found the difference:
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
Click to expand...
Click to collapse
Now I understand why it is deodexed
Now I want to find a way to root the stock ROM without unlock... there must be a method.
Several months ago I purchased a NS4G on Craigslist. I wanted to use it as an iPod touch without the data. It came rooted with SuperUser. The phone keeps prompting me to OTA to 2.3.7 (it's currently on 2.3.5) I used Gingerbreak to unroot and it worked, SuperUser is now gone. However, ClockWorkMod Recovery is still present and 2.3.7 won't install. The phone reboots, goes to about 1/3 of the progress bar, and then fails. I just want to get the phone on completely stock 2.3.7, in preparation for the coming 4.0 OTA.
Hopefully the solution doesn't involve flashing a custom ROM, I've never done that before. Thanks!!
No need to get it OTA, you can just flash the stock ICS ROM found in the stickies of the development forum of this phone. Of course follow instructions closely.
Sent from my Nexus S using xda premium
But I'm selling it and need it to be completely 100% original and stock, which is what the buyer requested..
You want to use fastboot to flash a stock recovery. Peter Alfonso has them all listed on his site.
Thanks. I'm really not familiar with fastboot, and is there any way you could give me a link with instructions or the files I need? My build number is GRJ90.
And if there's anyway for me to avoid a rooted stock ROM, that'd be great. Just pure stock 2.3.7.
The stock image on Rom manager has the recovery bootloader included.
Flash a stock gb rom from cwm. You will find a list of them in either general or android development threads, not sure which. Completely stock, unrooted and as far as I remember the stock recovery is included. If not then the person will never know anyway as if someone doesn't want any non stock features then they won't know how to get to recovery anyway.
Actually I don't think they have stock recovery. Just flash the stock rom and then fastboot flash the stock recovery like was mentioned above. All you need to type is:
Fastboot flash recovery xxxxx.img
Xxxxx.img is the name of the image file you download.
Don't cheat the buyer...Tell him exactly what he's buying...And that you returned thedevice back to stock again.It's just not worth it.
I need to get back to stock kernel for tf101.
Currently i'm running 8.5.6.13-root-cwm and clemsyn kernel version 22
and i'm looking to move to a stock .19(root+cwm) then move on to ICS using:
http://forum.xda-developers.com/showthread.php?t=1438433
where can i find the stock kernel i need and what is necessary to install it?
have a look here:
http://www.xdafileserver.nl/index.php?dir=ASUS/Asus+Transformer+(TF101)/ROMS/
especially in folder "stock rom by gee one"
Thank you, This will be very helpful!
This is still very helpful but i can only see that it has the ICS roms. looking for the HC rom that includes stock kernel, or stock kernel stand alone if either exists
Finky said:
I need to get back to stock kernel for tf101.
Currently i'm running 8.5.6.13-root-cwm and clemsyn kernel version 22
and i'm looking to move to a stock .19(root+cwm) then move on to ICS using:
http://forum.xda-developers.com/showthread.php?t=1438433
where can i find the stock kernel i need and what is necessary to install it?
Click to expand...
Click to collapse
Hi Finky,
because you have CWM already installed, I think you can just flash an ICS stock rom or custom rom.
for US read this:
http://forum.xda-developers.com/showthread.php?t=1622333
for ww read this:
http://forum.xda-developers.com/showthread.php?t=1627301
Make sure you read the threats because .21 has root problems, but make sure you install OTA root keeper.....in the developers forum are also CWM version of .17 that is rootable....read well before starting.
goodluck....
nlheiz said:
Hi Finky,
because you have CWM already installed, I think you can just flash an ICS stock rom or custom rom.
for US read this:
http://forum.xda-developers.com/showthread.php?t=1622333
for ww read this:
http://forum.xda-developers.com/showthread.php?t=1627301
Make sure you read the threats because .21 has root problems, but make sure you install OTA root keeper.....in the developers forum are also CWM version of .17 that is rootable....read well before starting.
goodluck....
Click to expand...
Click to collapse
So if i were to flash an ICS rom or HC rom, it will overwrite kernel and set it back to stock kernel?
Also i have made some system apk changes awhile back, would those be an issue?
Finky,
I just read the two threads, and it seems that every one with a custom kernel has problems. So, seems you just have to follow the thread that you put in your 1st post to make sure you get ride of your custom kernel.
Or, you can cwm flash the revolver rom (has the standard kernel of ICS inside) or one of the other custom roms (I use Revolver). that way you have ICS although it is custom. maybe that is some thing for you to do....or you want asus rom?
ok so I was an original GS III owner (I preordered, used the original root66, waited for the unlocked bootloader, etc.)
I just rx'ed a 2nd replacement because the power button fell off my first replacement (my 1st gsIII had a faulty modem).
This one came preloaded with the 2nd OTA (VRALHE)
I was wondering the correct method to go about setting it up...
1.) odin the original root66 VRALF and continue in the same way I did with my original one (dd a TWRP and the insecure bootloader)?
2.) I could follow the directions in section 1 here: http://forum.xda-developers.com/showthread.php?t=1762709
and odin a pre-rooted VRBLJ1. It then says I can just go ahead and add a custom recovery (it mentions the EZ app but I'd rather just dd. then do the insecure aboot the same way)
3.) I could follow the directions here: http://forum.xda-developers.com/showthread.php?t=1974114
it mentions ODINing the VRBLJ1 leak and then ODINing a custom recovery but the recoveries INCLUDE "VRBLJ1 Bootchain." Why?
according to Invisiblek (http://rootzwiki.com/topic/29256-ro...-unlock-sch-i535-d2vzwverizon-galaxy-s-iii/):
What the locked bootloader prevents us from doing is flashing, via odin, a custom recovery or kernel. What we can do however, is revert to an older (semi-insecure) bootchain which we have acquired, flash our custom recovery, and then continue on from our freshly flashed custom recovery by flashing an unlocked bootloader and anything else we want.
Kernels from the newer OTA's prevent us from doing this process. We'll need to flash a kernel too...
Click to expand...
Click to collapse
he mentions flashing the VRALEC and then later (after flashing the VRALF2 kernel and a custom recovery) the VRALF2 bootchain. His explanation makes sense, but the other threads say to use the VRBLJ1 bootchain. why all the conflicting info?
Also, as I wrote this I used the rootDebugFS thing on my freshly rx'ed VRALHE. i then dd'ed a recovery and the insecure aboot. Everything is working fine. So what's all the fuss about? and will I encounter problems if I try to odin anything, like invisiblek said?
Thanks
preusstang said:
ok so I was an original GS III owner (I preordered, used the original root66, waited for the unlocked bootloader, etc.)
I just rx'ed a 2nd replacement because the power button fell off my first replacement (my 1st gsIII had a faulty modem).
This one came preloaded with the 2nd OTA (VRALHE)
I was wondering the correct method to go about setting it up...
1.) odin the original root66 VRALF and continue in the same way I did with my original one (dd a TWRP and the insecure bootloader)?
2.) I could follow the directions in section 1 here: http://forum.xda-developers.com/showthread.php?t=1762709
and odin a pre-rooted VRBLJ1. It then says I can just go ahead and add a custom recovery (it mentions the EZ app but I'd rather just dd. then do the insecure aboot the same way)
3.) I could follow the directions here: http://forum.xda-developers.com/showthread.php?t=1974114
it mentions ODINing the VRBLJ1 leak and then ODINing a custom recovery but the recoveries INCLUDE "VRBLJ1 Bootchain." Why?
according to Invisiblek (http://rootzwiki.com/topic/29256-ro...-unlock-sch-i535-d2vzwverizon-galaxy-s-iii/):
he mentions flashing the VRALEC and then later (after flashing the VRALF2 kernel and a custom recovery) the VRALF2 bootchain. His explanation makes sense, but the other threads say to use the VRBLJ1 bootchain. why all the conflicting info?
Also, as I wrote this I used the rootDebugFS thing on my freshly rx'ed VRALHE. i then dd'ed a recovery and the insecure aboot. Everything is working fine. So what's all the fuss about? and will I encounter problems if I try to odin anything, like invisiblek said?
Thanks
Click to expand...
Click to collapse
I'm assuming since VRBLJ1 is the newest JB leak then it uses the newer boot chain. The only reason you would need that boot chain to unlock the bootloader is if you used Odin to flash the newest VZW JB leak onto your phone. Then you would need it to unlock the VRBLJ1 JB leak. If you are are any of the ICS stock ROMs and want to unlock you can use the old way of doing it. The post you are reading from invisiblek is old, it was when we were on the VRALFW stock ROM.
Now I have no clue why you would want to use Odin to flash the newest JB leak when you can do it by downloading the version of the ROM made to be flashed with TWRP or CWM. I would love to have a dev or someone knowledgeable about these things to chime in and tell us if there is any benefit to using Odin to update to the newest JB leak or if there is no difference between having the JB leak or one of the OTA's on your phone before you flash a ROM.
Sent from one of the many Anthropomorphic Personalities on the Disc
shangrila500 said:
I'm assuming since VRBLJ1 is the newest JB leak then it uses the newer boot chain. The only reason you would need that boot chain to unlock the bootloader is if you used Odin to flash the newest VZW JB leak onto your phone. Then you would need it to unlock the VRBLJ1 JB leak. If you are are any of the ICS stock ROMs and want to unlock you can use the old way of doing it. The post you are reading from invisiblek is old, it was when we were on the VRALFW stock ROM.
Now I have no clue why you would want to use Odin to flash the newest JB leak when you can do it by downloading the version of the ROM made to be flashed with TWRP or CWM. I would love to have a dev or someone knowledgeable about these things to chime in and tell us if there is any benefit to using Odin to update to the newest JB leak or if there is no difference between having the JB leak or one of the OTA's on your phone before you flash a ROM.
Sent from one of the many Anthropomorphic Personalities on the Disc
Click to expand...
Click to collapse
Its just another way of basically doing the same thing. If your already rooted and have cwm recovery, then flashing a J1 rom via cwm or twrp recovery is by far the easiest method. Now if your stock and unrooted, it would be easier to odin root66 J1 , then unlock and get cwm recovery via the ez unlock/recovery apps. This is why I have 2 different methods in my guide...I also chose to not flash bootchains unless its a last resort because they can perma brick a device if something goes wrong. Also I like to use methods that dont trip the flash counter, makes for one less thing to do if the device ever needs to be returned.
droidstyle said:
Its just another way of basically doing the same thing. If your already rooted and have cwm recovery, then flashing a J1 rom via cwm or twrp recovery is by far the easiest method. Now if your stock and unrooted, it would be easier to odin root66 J1 , then unlock and get cwm recovery via the ez unlock/recovery apps. This is why I have 2 different methods in my guide...I also chose to not flash bootchains unless its a last resort because they can perma brick a device if something goes wrong. Also I like to use methods that dont trip the flash counter, makes for one less thing to do if the device ever needs to be returned.
Click to expand...
Click to collapse
Gotcha, that's been bothering me for a few days. I remember when I was flashing on my RAZR that the stock OTA was the base for everything and if you didn't have the latest OTA some of the ROMs wouldn't run on your phone until you updated and some of the older ROMs wouldn't work until they had been updated to work on the newest OTA or leak. The ROMs were just overlays and usually only added a little bit of added performance or functionality.
Would updating to the latest OTA via Odin add any benefits like it did on the RAZR ? I know the RAZR wasn't unlocked and we weren't flashing ROMs like we do on the GS3 but.....
Sent from one of the many Anthropomorphic Personalities on the Disc
no not on samsung devices...you can go from f2 to the latest with no issues.
droidstyle said:
no not on samsung devices...you can go from f2 to the latest with no issues.
Click to expand...
Click to collapse
No I get that, I was meaning are there any positive side effects from using the newest JB leak as your base ROM before flashing a new one. Like flashing the new JB leak via Odin, then unlocking and flashing a new ROM on top of it. Will there be any benefits like there were on the RAZR or when we flash in custom recoveries does it completely do away with the stock ROM that was on the system partition and replace it with whatever we flash? I know on the RAZR you would use the ROM you were on as a base you flash whatever else you wanted and there were benefits to having a certain OTA as your base before you flashed. I don't think I'm doing a very good job of phrasing my question, I apologize for that. Its just a hard question to put into words.
Sent from one of the many Anthropomorphic Personalities on the Disc
shangrila500 said:
No I get that, I was meaning are there any positive side effects from using the newest JB leak as your base ROM before flashing a new one. Like flashing the new JB leak via Odin, then unlocking and flashing a new ROM on top of it. Will there be any benefits like there were on the RAZR or when we flash in custom recoveries does it completely do away with the stock ROM that was on the system partition and replace it with whatever we flash? I know on the RAZR you would use the ROM you were on as a base you flash whatever else you wanted and there were benefits to having a certain OTA as your base before you flashed. I don't think I'm doing a very good job of phrasing my question, I apologize for that. Its just a hard question to put into words.
Sent from one of the many Anthropomorphic Personalities on the Disc
Click to expand...
Click to collapse
no not on samsung devices...the reason you needed to do that on the moto device is because of the locked bootloader. meaning you couldnt replace the kernel, so you had to ota to the latest, then root , recovery, and flash rom. since our device is fully unlocked, we dont have to worry about this. most if not all roms for d2vzw are packaged with a kernel. so it does not matter what current base your on, flashing a rom will overwrite it.
droidstyle said:
no not on samsung devices...the reason you needed to do that on the moto device is because of the locked bootloader. meaning you couldnt replace the kernel, so you had to ota to the latest, then root , recovery, and flash rom. since our device is fully unlocked, we dont have to worry about this. most if not all roms for d2vzw are packaged with a kernel. so it does not matter what current base your on, flashing a rom will overwrite it.
Click to expand...
Click to collapse
That's what I thought. I was just wanting a little clarification on that. Thanks man!!!
Sent from one of the many Anthropomorphic Personalities of the Disc
I currently have S-Off and have it rooted through Weaksauce and SuperSu I believe. I have flashed ROMs through TWRP but did not like them, so I recovered back into my 4.4.2 stock. If I update to 4.4.4 by Verizon's OTA, will I lose my root and S-Off?
kinda a noob but...
steezy123 said:
I currently have S-Off and have it rooted through Weaksauce and SuperSu I believe. I have flashed ROMs through TWRP but did not like them, so I recovered back into my 4.4.2 stock. If I update to 4.4.4 by Verizon's OTA, will I lose my root and S-Off?
Click to expand...
Click to collapse
I'm not a hundred percent but I think the only way you lose it is if it upgrades the boot.img search for tigers posts because from the way it sounded to me if you flashed back to stock you'd have all ready lost your s-off.... Unless you've flashed one of the stock with the boot.img and recovery img removed. If so I'm pretty sure your good for the firmware upgrade if it'll ota without stock (or forged) boot.img file... Anyway man I'm slightly baked and never been accused of being smart enough to remember **** I read two weeks ago so search "tigerstown" posts and threads and read man and when you understand all a bit better than me then come message me and we'll discuss it a bit so it'll stick to my head a lil longer than last time man. Hope my rambleing might have shed some light on the subject or at least pointed you to the posts that know lol goodluck
The only way to "lose" s-off is to issue the fastboot command to set that flag which many smart people would never advise you do anyway. Nothing we are talking about here will do that automatically.
If you're s-off and on a custom Rom of any sort, I would recommend updating the firmware through tigerstown's method the previous poster referred to. If you're going to the trouble to flash everything necessary to take the ota, you may as well just flash his file and be done.
If you prefer stock, I would recommend you flash a stock-based Rom like CleanRom or NuSense. They come pre-rooted with some bloat removed and just a few tweaks added like write-protection removed, init-d support, etc.
If you really insist on running pure stock with root then you should at least root properly by uninstalling weak sauce and flashing the su binaries in recovery.
cntryby429 said:
The only way to "lose" s-off is to issue the fastboot command to set that flag which many smart people would never advise you do anyway. Nothing we are talking about here will do that automatically.
If you're s-off and on a custom Rom of any sort, I would recommend updating the firmware through tigerstown's method the previous poster referred to. If you're going to the trouble to flash everything necessary to take the ota, you may as well just flash his file and be done.
If you prefer stock, I would recommend you flash a stock-based Rom like CleanRom or NuSense. They come pre-rooted with some bloat removed and just a few tweaks added like write-protection removed, init-d support, etc.
If you really insist on running pure stock with root then you should at least root properly by uninstalling weak sauce and flashing the su binaries in recovery.
Click to expand...
Click to collapse
Thanks for all help, I'll start readin up. Just one question: let's say I update my firmware to 4.4.4 from Verizon's OTA, will I be able to flash this clean rom via TWRP? http://forum.xda-developers.com/showthread.php?t=2732877
The only reason I ask is because it says the user must be running 4.4.4 firmware to flash the rom and the only way I know how to get 4.4.4 is from Verizon's OTA
You can get everything you need from Verizon's 4.4.4 release by flashing the no boot no recovery file from the tigerstown thread mentioned earlier. It's the first file listed in his op. The rest of the ota contains the recovery (which you don't want since you need your custom recovery to flash custom ROMs) and the boot.img/kernel (which you don't need since every room comes with a kernel). It's not wrong till go back to stock to take an ota, it's just unnecessarily difficult when people like tigerstown make it so easy for us to accomplish the same thing.