It seems it is not possible to get _exactly_ stock jellybean without applying the OTA update from IMM30D.
The new bootloader (LC03) seems to have a different partition table than the old one (LA03).
The phone won't boot if I flash LC03 on top of the Koush jb-takju.zip Jellybean update, and CWM can't mount the /data partition.
My guess is future OTA updates won't work running the "stockiest" Jellybean I can manage going from a takju device (LA03/XXLF1/JRN84D)
Anyone have any suggestions?
I did it by copying new boot loader, radio and the JB zip to SD card. Pushed cwm via fast boot, went into cwm and cleared out all the data and caches. Flashed new boot loader, then new radio and finally the ROM zip. Rebooted and I had the full works.
The key was to do them in one go without reboot. There was a guide on here somewhere that I followed.
Sent from my Galaxy Nexus using xda premium
So just to clarify... I've flashed bigxie's JB v2 stock deodexed ROM, as well as the new Radio. I can't flash the bootloader now?
bucketsort said:
[snip]
It seems it is not possible to get _exactly_ stock jellybean without applying the OTA update from IMM30D.
Click to expand...
Click to collapse
Of course you can. You must be doing something wrong. Step-by-step instructions in post #2 here.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
uansari1 said:
So just to clarify... I've flashed bigxie's JB v2 stock deodexed ROM, as well as the new Radio. I can't flash the bootloader now?
Click to expand...
Click to collapse
You CAN.
I flashed LC03 just fine after flashing Koush's jb-takyu.zip
Even flashed it and the radio seperate times several days later, no issues, no need to do it all at once.
nxt said:
I flashed LC03 just fine after flashing Koush's jb-takyu.zip
Even flashed it and the radio seperate times several days later, no issues, no need to do it all at once.
Click to expand...
Click to collapse
Same here.
I flashed LC03 just fine after flashing Koush's jb-takyu.zip
Even flashed it and the radio seperate times several days later, no issues, no need to do it all at once.
Click to expand...
Click to collapse
Yeah, works fine for me too.
Thanks guys..
Sent from my Nexus S using Tapatalk 2
How different is the partition table? Any idea why?
It obviously works without the new bootloader but I can see the concern.
Is the userdata partition jolted around at all?
Will a nandroid restore of data work properly from the old table to the new one ?
I figure I'll just wait until an official release is available entirely in fastboot format, then make the necessary changes.
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
How different is the partition table? Any idea why?
It obviously works without the new bootloader but I can see the concern.
Is the userdata partition jolted around at all?
Will a nandroid restore of data work properly from the old table to the new one ?
I figure I'll just wait until an official release is available entirely in fastboot format, then make the necessary changes.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Although I haven't verified it yet, I don't think there is any difference in partitioning. (I think the OP was having other issues.) Users with the LC03 bootloader AND with earlier bootloaders have had no issues. When I get around to it, I'll pull off the partition sizes with the LC03 bootloader and compare them to the sizes of the LA03 bootloader (as seen here).
Related
This is official stock image build backed up cwm recovery fastboot flash.
just unrar,
then drag folder to your backup folder inside your clockworkmod folder on your phone,
then open rom manager,
then click restore,
then your back to stock,
or just go into recovery and select restore,
if you use or dl it plz click the thx button,
it is not rooted nothing added or taken away, pure STOCK 4.0.4 IMM76i XXLA2
http://www.mediafire.com/?f7fp251ajobw025
saving this for future use!
nice work! I love it!
Nice....
One question though...
I have franco kernel and different radio flashed on my GN, so if I would recover this image would I get stock kernel and radio which is stated in post?
YES
Hey thanks,
is it gonna get OTAs?
yes but i think you will have to lock bootloader tho for official updates,,,fastboot oem lock
Is this the official updated with the GSM fix or something else?
image files from google source its the official one
thanks for posting this. the CMW backup includes a radio image? what version of CWM is included? i was under the impression that CWM DOES NOT backup radio images. i already have the same radio and prefer not to flash it again. thanks.
Thanks it will be really useful!
sloppy1 said:
yes but i think you will have to lock bootloader tho for official updates,,,fastboot oem lock
Click to expand...
Click to collapse
You shouldn't have to re-lock the bootloader for OTAs.
hi,
I have a problem with this rom (i also already put Franco latest stable kernel on it) regarding Facebook app.
Text and messages are transparent, the only thing i can see is pics of my contacs. Any text is missing.
Do you have any ideas how i could fix it?
sloppy1 said:
yes but i think you will have to lock bootloader tho for official updates,,,fastboot oem lock
Click to expand...
Click to collapse
I got OTA update with root & unlocked bootloader, but it failed to apply because of some asserts in the script that checked MD5 hash of certain files incl build.prop, and I'd made some tweaks. So YES to OTA.
The best ROM around here so far !!!!!!!!
Hi, may i know how can i root this rom? i download and restore the 2nd one already. but still show no rooted access. I try GNex toolkit and Easiest Root Toolkit both fail to root it.
Thanks.
OwenChiang said:
Hi, may i know how can i root this rom? i download and restore the 2nd one already. but still show no rooted access. I try GNex toolkit and Easiest Root Toolkit both fail to root it.
Thanks.
Click to expand...
Click to collapse
the second one is rooted im using it lol, in fastboot i flashed cwm touch recovery from there i installed su then made backup nothing else done ,no alterations at all,try downloading rommanager from market and reflash recovery
asds said:
hi,
I have a problem with this rom (i also already put Franco latest stable kernel on it) regarding Facebook app.
Text and messages are transparent, the only thing i can see is pics of my contacs. Any text is missing.
Do you have any ideas how i could fix it?[/Q reput the rom bk on and try without putting another kernel on
Click to expand...
Click to collapse
Ok i'll try asap
---------- Post added at 08:44 PM ---------- Previous post was at 08:30 PM ----------
Erf, stock kernel didnt fix the problem, looks like it's a imm76I problem :/
I'm reseting it right now to see (dalvik, wipe and cache.)
After full reset, problem still here. So i think it's a firmware related bug :/
I flashed the pre rooted one. But it says I don't have root. How do I fix this?
Hello guys,
I have a HTC One X from Vodafone, rooted, unlocked, stock rom, custom recovery, and today (FINALLY ) I received the OTA update to Jelly Bean.
I downloaded it and tried to install it using the custom recovery but it was failing on some assert. I guessed that it was because of the recovery so I flashed back the stock recovery and tried to install; fail again.
Went online and found the directory for the update log and saw an entry saying that there was a problem trying to verify the stock Dropbox apk that comes with the phone and that is placed on /system/apps. I read somewhere that if you modify something on the stock apks the OTA would fail, and unfortunatelly I did, I flashed the Galaxy S3 Dropbox apk on my phone, but that's not the problem, the problem is that I deleted the flashed Dropbox and the stock Dropbox from /system/apps without knowing it and the OTA is still failing.
My guess is that if I can flash the stock Dropbox apk to /system/apps, the OTA will try to verify it and will succeed, and therefore I'll have finally Jelly Bean on my branded device (as I said, is just a guess) so if someone could please send me the stock Dropbox apk, the one located in /system/apps as well as any other file located there that could possibly be related to Dropbox app, it will be very very appreciated.
If you guys think that I'm missing something here and even after flashing the stock Dropbox apk the OTA will still fail for some karma related reasons, please let me know and help me out.
If you need any other info from my phone let me know too.
If you need the .zip file with the official update from Vodafone I have it too.
Thanks in advance.
TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.
nemer12 said:
TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.
Click to expand...
Click to collapse
Well yes I have stock recovery (replaced the custom recovery yesterday) and stock kernel, I haven't changed the kernel yet, and according to the log the problem is with Dropbox. I'll try to find it and paste it here so you guys can see it.
Thanks.
Just flash the RUU, update OTA and reroot.
Alright, will do and I'll let you know how it goes. Thanks
Netrunner16 said:
Alright, will do and I'll let you know how it goes. Thanks
Click to expand...
Click to collapse
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
If you only unlocked the bootloader the update should run fine !!! If it fails you did change some more !
prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.
And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !
Netrunner16 said:
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.
Click to expand...
Click to collapse
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level
prankstarr said:
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level
Click to expand...
Click to collapse
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !
MarcelHofs said:
And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !
Click to expand...
Click to collapse
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...
Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:
prankstarr said:
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...
Click to expand...
Click to collapse
But you said you had CWR, you need to flash the stock recovery back and then try the update.
MarcelHofs said:
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !
Click to expand...
Click to collapse
Okay cool - will try although I thought I flashed stock recovery. I got rid of CMR when I got in from work today ... recovery img was in the fastboot folder i used when unlocking bootloader.
---------- Post added at 12:20 AM ---------- Previous post was at 12:14 AM ----------
Netrunner16 said:
But you said you had CWR, you need to flash the stock recovery back and then try the update.
Click to expand...
Click to collapse
Yes, I thought i flashed stock before but am about to confirm
The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense
MarcelHofs said:
Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:
Click to expand...
Click to collapse
Yes, sorry - i did read it and it did say 2.17xxx...I downloaded the recovery you pointed me to but expect i need to re-unlock the bootloader. (I re-locked it before thinking that was causing the issue...)
Anyway, soon I should know if this works
By the way, I really appreciate you helping me - i've been trying to sort this out all evening!
---------- Post added at 12:34 AM ---------- Previous post was at 12:29 AM ----------
MarcelHofs said:
The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense
Click to expand...
Click to collapse
There is a good chance you are correct. The file in my fastboot folder said recovery and I assumed it was what I was after but it may have been connected to something that I was told to download in the unlocking process (I followed a guide on Youtube by a chap called cursed4eva)
I'm reunlocking the bootloader now because I got an error wh3n i tried to flash that recovery img. "writing 'recovery'... FAILED (remote: not allowed)"
---------- Post added at 01:24 AM ---------- Previous post was at 12:34 AM ----------
Okay - so I
1/ reunlocked the bootloader which basically wiped the phone back to its initialt state all be it with an unlocked bootloader.
2/ once again completed the OTA download of Vodafone Jellybean for the One X
3/ flashed the 2.17 recovery img that Marcel provided
4/ tried to update
5/ am currently looking at a download / progress bar! (YESSSS!)
6/ am hoping this works!
Thanks a lot Marcel. I very much appreciate your patience!
dr9722 said:
Just flash the RUU, update OTA and reroot.
Click to expand...
Click to collapse
I already have the RUU for my phone, and I was planning to follow this tutorial: http://forum.xda-developers.com/showthread.php?t=1660807
But I was thinking, what if I flash only the system.img instead of all the 3 files? I already have the stock recovery (the one you provided) and I've never changed the boot.img so I still have the stock one.
What about if I flash the system.img only, and then try the OTA update? Do you think that would work?
Thanks for the help.
Yes you can try that, the phone is already wiped with unlocking the bootloader, i never tried it. But in logical terms it is possible yes. If doesn't work you can always run the complete ruu !
That's weird, I'm getting error 00000006 when trying to flash the system.img.
Reading on other posts that's related to the size of the file, which is around 1 GB. If I can't flash the system.img I think I wont be able to run the entire RUU either.
Do you know a way to bypass this error?
Well, some days ago I accidentally encrypted my gnex, and many attempts to undo the encryption failed.
But this time, the **** was bigger than the hole.
I wiped ALL the data(YES I WENT FULL RETARD) and now I cant boot the android neither flash the stock ROM by common ways.
So guys, how can i flash again to the stock rom?
lotusgg said:
Well, some days ago I accidentally encrypted my gnex, and many attempts to undo the encryption failed.
But this time, the **** was bigger than the hole.
I wiped ALL the data(YES I WENT FULL RETARD) and now I cant boot the android neither flash the stock ROM by common ways.
So guys, how can i flash again to the stock rom?
Click to expand...
Click to collapse
more info please how are you flashing what version do you have what have you tryed ill help if i can but i need info please
lotusgg said:
Well, some days ago I accidentally encrypted my gnex, and many attempts to undo the encryption failed.
But this time, the **** was bigger than the hole.
I wiped ALL the data(YES I WENT FULL RETARD) and now I cant boot the android neither flash the stock ROM by common ways.
So guys, how can i flash again to the stock rom?
Click to expand...
Click to collapse
You can follow efrants guide in general.
Sent from my Nexus
Alpha_wolf said:
more info please how are you flashing what version do you have what have you tryed ill help if i can but i need info please
Click to expand...
Click to collapse
There is no version since I wiped everything, i got no boot, only the fastboot and the cwm recovery. Trying to flash stock rom.
bk201doesntexist said:
You can follow efrants guide in general.
Sent from my Nexus
Click to expand...
Click to collapse
I cant follow any guide, since in gnex toolkit any version I select wont recognize my device. At least i did not tryied every version.
lotusgg said:
I cant follow any guide, since in gnex toolkit any version I select wont recognize my device. At least i did not tryied every version.
Click to expand...
Click to collapse
You don't need a toolkit, that guide doesn't use one or recommend one.
cupfulloflol said:
You don't need a toolkit, that guide doesn't use one or recommend one.
Click to expand...
Click to collapse
Exactly, who said anything about toolkits?
Sent from my Nexus
I want to flash CM10.2 on my rooted 4.3 MK3 s3. Is it possible to flash that rom on the phone although Cm10.2 is android 4.2.2?
Thanks!
WoodenDiamond71 said:
I want to flash CM10.2 on my rooted 4.3 MK3 s3. Is it possible to flash that rom on the phone although Cm10.2 is android 4.2.2?
Thanks!
Click to expand...
Click to collapse
As long as the file you download does not downgrade the boot loader. ROM zips will not do this unless otherwise noted. Flashing tar files through ODIN can brick your phone if you downgrade Android version number because tar files reflash every part of the phone, including bootloader.
sent from my GS3
joeyhdownsouth said:
As long as the file you download does not downgrade the boot loader. ROM zips will not do this unless otherwise noted. Flashing tar files through ODIN can brick your phone if you downgrade Android version number because tar files reflash every part of the phone, including bootloader.
sent from my GS3
Click to expand...
Click to collapse
You're correct about the downgrading the bootloader part since i have learned my lesson the first time, but as far as flashing the rom is concerned my recovery will not flash it and i get the broken android as the background and my recovery says the installation was aborted. I am using philz touch recovery 6 btw.
WoodenDiamond71 said:
You're correct about the downgrading the bootloader part since i have learned my lesson the first time, but as far as flashing the rom is concerned my recovery will not flash it and i get the broken android as the background and my recovery says the installation was aborted. I am using philz touch recovery 6 btw.
Click to expand...
Click to collapse
You should be also getting a status 7 error, because the bootloader you currently have (MK3) is not listed as one of the "approved" bootloaders in the updater-script for any 4.3.x ROM based on AOSP. You will need to go into the updater-script and modify one of the lines to match your bootloader, or get rid of the assert lines altogether. Any KitKat 4.4.x ROM's will have your bootloader listed, so this is not necessary for the newest ROM's.
How would I do that? Is there a tutorial I can follow
Sent from my SPH-L710 using Tapatalk
WoodenDiamond71 said:
How would I do that? Is there a tutorial I can follow
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/791952-all-in-one-guide-modifying-custom-sprint-roms-virgin-mobile-use.html
This is a tutorial I have put together on Android Forums for the rooted Virgin Mobile community (SGS3), since we have to always modify or delete the asserts in order to get Sprint ROM's to flash on our phones. Principle is the same for any Sprint user in your situation. I also just made a YouTube video showing how to do the relevant parts of my tutorial.
https://www.youtube.com/watch?v=IZnYSrUIXKM
Hope this helps! Feel free to PM me if need be for any clarification.
Sweet!! Thanks I'll check it out later once I get out of work. Thanks once again I'll pm if it worked
Sent from my SPH-L710 using Tapatalk
So I formatted both slots in TWRP one time and rebooted into bootloader and proceeded to flash all.bat my nmf26U which I believe is the latest Verizon rendition or am I wrong? Well after that boots then I proceed to wipe n flash pure Nexus ROM and my problem is everything is flawless except the wifi the wifi works good for like a minute but then the performance drops significantly. Now I'm not sure if the baseband is wrong or I need to update radio or I'm going about it all wrong flashing updated radios and basebands with pure Nexus. Isn't it the same thing if I flash all.bat nmf26u then just wipe and flash the ROM doesn't that give me updated radios? Some insight would really be appreciated as I have no idea how this pixel works exactly. How can I make a good starting point again for reflashing, flash nmf26q to both slots? Then take it from there? Sorry for the wall of text
vidfinnx said:
So I formatted both slots in TWRP one time and rebooted into bootloader and proceeded to flash all.bat my nmf26U which I believe is the latest Verizon rendition or am I wrong? Well after that boots then I proceed to wipe n flash pure Nexus ROM and my problem is everything is flawless except the wifi the wifi works good for like a minute but then the performance drops significantly. Now I'm not sure if the baseband is wrong or I need to update radio or I'm going about it all wrong flashing updated radios and basebands with pure Nexus. Isn't it the same thing if I flash all.bat nmf26u then just wipe and flash the ROM doesn't that give me updated radios? Some insight would really be appreciated as I have no idea how this pixel works exactly. How can I make a good starting point again for reflashing, flash nmf26q to both slots? Then take it from there? Sorry for the wall of text
Click to expand...
Click to collapse
This would probably be posted in the ROM thread. Beans would be able to give you more info for sure.
vidfinnx said:
So I formatted both slots in TWRP one time and rebooted into bootloader and proceeded to flash all.bat my nmf26U which I believe is the latest Verizon rendition or am I wrong? Well after that boots then I proceed to wipe n flash pure Nexus ROM and my problem is everything is flawless except the wifi the wifi works good for like a minute but then the performance drops significantly. Now I'm not sure if the baseband is wrong or I need to update radio or I'm going about it all wrong flashing updated radios and basebands with pure Nexus. Isn't it the same thing if I flash all.bat nmf26u then just wipe and flash the ROM doesn't that give me updated radios? Some insight would really be appreciated as I have no idea how this pixel works exactly. How can I make a good starting point again for reflashing, flash nmf26q to both slots? Then take it from there? Sorry for the wall of text
Click to expand...
Click to collapse
NMF26V is the Verizon vendor image. If you flashed the other that's probably why your radios aren't working. You also didn't need to flash the factory image to update everything but since you flashed the wrong one you should probably get the correct factory image and make sure you flash it just in case.
OK so right now I flashed nmf26q I didn't download the v one because it says Europe on it and on Verizon's website it says nmf26u is the latest update...
Attached screenshot...V is the latest for Verizon?
Also what all do I exactly need to update since I'm running pure nexus right now and how do I go about just flashing only what I need
vidfinnx said:
Attached screenshot...V is the latest for Verizon?
Click to expand...
Click to collapse
Your Screenshot says U. V is for Europe.
---------- Post added at 10:07 PM ---------- Previous post was at 10:06 PM ----------
vidfinnx said:
Also what all do I exactly need to update since I'm running pure nexus right now and how do I go about just flashing only what I need
Click to expand...
Click to collapse
Pure Nexus uses the V vendor.
I don't know how much it matters but I'm running the v image right now on Verizon and everything is fine. On pure Nexus I had to use the v image to get the radios to even work.
Its really weird because I used the U image and the radios freak out really bad like WiFi messes up something fierce,like something weird happens with the WiFi ping. so I went back to the Q image and bootloader and radios etc then reflashed back to pure nexus and all seems OK except for an unusually high battery drain it feels like. Debating flashing elemental x kernel.