Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

LEAKED JELLY BEAN ROM!TEMPORARY FAQ! Read First!

OP shadehh

3rd October 2012, 09:04 PM   |  #1  
OP Senior Member
Thanks Meter: 295
 
858 posts
Join Date:Joined: Mar 2011
I'm sure many are seeking for the answer on how to flash this rom? Well then head over to question #7 - for a more informative guide follow this link http://forum.xda-developers.com/show....php?t=1920060

With the release of these jb roms there is a crap load of questions popping up. A lot of cid questions as well which are being repeated over and over. With this thread i hope to put an end to it.

Any questions that pop up i will try to answer as well as add to this list as time passes by, until eventually we have an ota and things settle in. Feel free to ask questions, if i cant answer, another person will. New questions are added to first page.
Quote:

Overview
Q1:I want to install the jelly bean rom that has been leaked, how do i do this?
Q2: How do i check what my cid number is?
Q3: If i update my hboot, will i be able to use my previous ics rom?
Q5:Can i change my cid number, is there an alternative route? I MUST HAVE IT!!
Q6: Must the hboot be updated in order to be able to upgrade to jelly bean in future?
Q7: How do i flash the jelly bean roms?
Q8: On which cids to the firmwares work?
Q9: Will future updates make it possible for us to upgrade without updating hboot?
Q10: Should you install the new rom or wait? (This question might seem silly but i've seen people asking)
Q11:How can i check which RUU i need?

Q12:Is there actually an easier method to update hboot for us custom users in future releases or are following those steps a must for everybody?
Q13: What kernel# does the leaked Jelly Bean kernel have?

Q1:I want to install the jelly bean rom that has been leaked, how do i do this?
A1: The leaked jelly bean roms need a certain cid, not every cid number works. Either you are lucky enough to have it or not.
It is looking bad for branded phones at the moment


Q2: How do i check what my cid number is?
A2:You can download the so called "cid getter" from the app store. Your cid # should be listed on top. If not.....
Alternatively you can try the following command in fastboot:
Fastboot oem readcid


Q3: If i update my hboot, will i be able to use my previous ics rom?
A3: At the moment there is noway you can downgrade to ics once you have acquired jelly bean

Q4:When will we get an official jelly bean update?
A4: This month.
But when? It could be as soon as next week or as late as end of October.



Q5:Can i change my cid number, is there an alternative route? I MUST HAVE IT!!
A5:No. And no.

Q6: Must the hboot be updated in order to be able to upgrade to jelly bean in future?
A6:So far the answer seems to be leaning more towards a yes then a maybe or no.

Q7: How do i flash the jelly bean roms?
A7: 1. Relock bootloader: - fasboot oem lock
2. Boot device
2a. If device reboots to bootlader mode then flash a stock ruu and reboot to phone mode (ensure usb debugging is on - Settings/Developer options)
3. From command prompt enter: -adb reboot oem-78
4. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip
5. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken Unlock_code.bin
6. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
7. Flash boot.img from rom zip: - fastboot flash boot boot.img
8. Flash rom zip through recovery
9. Reboot and enjoy

Thank you ClydeB1 for the steps

Q8: On which cids to the firmwares work?
A8:
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__J15


Q9: Will future updates make it possible for us to upgrade without updating hboot?
A9: It's too early to tell, however, from what i've read this looks like it won't be possible.

Q10: Should you install the new rom or wait? (This question might seem silly but i've seen people asking)
A10: That is up to you. However, i'll list the pros and cons
pros: More fluid, has a bunch of improvement as well as power saver option. Wireless lan as well as radio signal seem to get established much faster.
cons: Limited number of roms, not really much variation. It's a leak, and a leak has bugs - so don't expect it to run at 100%
That also means, no miui, no cm10,ice cold jelly(at least a lot of stuff in the original android development section) close to nothing at the moment. However, if jelly bean satisfies you then i see no reason why you shouldn't update.
Gaming:For the HoX game lovers out there, it's probably safe to say that you should not upgrade just yet. Certain kernels are probably not supported which enhance your gaming experience.

Q11:How can i check which RUU i need?
A11: Open cmd.exe and type "fastboot getvar version-main" without quotes.

Q12:Is there actually an easier method to update hboot for us custom users in future releases or are following those steps a must for everybody?
A12: Nope, at least not for s-on devices. -Mike1986_(ARHD)

Q13: What kernel# does the leaked Jelly Bean kernel have?
A13: 3.1.10
Last edited by shadehh; 4th October 2012 at 11:26 PM.
The Following 33 Users Say Thank You to shadehh For This Useful Post: [ View ]
3rd October 2012, 11:20 PM   |  #2  
ClydeB1's Avatar
Recognized Contributor
Thanks Meter: 4,346
 
10,696 posts
Join Date:Joined: May 2009
Donate to Me
More
Perhaps add the steps again to flash:

Before you start take a backup of your sd card and ensure that your phone is charged, at least 70% to be safe
1. Relock bootloader: - fastboot oem lock
2. Boot device
2a. If device reboots to bootlader mode then flash the appropriate stock ruu for your device and then reboot to phone mode (ensure usb debugging is on - Settings/Developer options) (To find which ruu to flash run fastboot getvar version-main, or else you can try the odexed Stock rom + boot.img from Mike's thread)
3. From command prompt enter: - adb reboot oem-78
4. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip (NB! If this step fails, immediately rerun the cmd and it should work the 2nd time)
5. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken Unlock_code.bin
6. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
7. Flash boot.img from rom zip: - fastboot flash boot boot.img
8. Flash rom zip through recovery
9. Reboot and enjoy

Edit: Updated method for flashing from hboot 1.23 to 1.28
1. Relock bootloader - fasboot oem lock
2. Enter command - fastboot oem rebootRUU
3. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip (NB! If this step fails, immediately rerun the cmd and it should work the 2nd time)
4. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken Unlock_code.bin
5. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
6. Flash boot.img from rom zip: - fastboot flash boot boot.img
7. Flash rom zip through recovery
8. Reboot and enjoy
Last edited by ClydeB1; 11th November 2012 at 02:32 PM. Reason: Added additional info
The Following 10 Users Say Thank You to ClydeB1 For This Useful Post: [ View ]
3rd October 2012, 11:25 PM   |  #3  
dani_nec's Avatar
Senior Member
Flag Barcelona
Thanks Meter: 104
 
639 posts
Join Date:Joined: Apr 2012
More
Another question to clarify ..
we must install the RUU after just lock the bootloader , right?

I understand that it is absolutely necessary, as the custom rom in "relocked" did not start, right?
3rd October 2012, 11:26 PM   |  #4  
Senior Member
Flag Bay Area, California
Thanks Meter: 19
 
382 posts
Join Date:Joined: Jan 2012
More
can u list the CID's that are valid in the OP please?
3rd October 2012, 11:28 PM   |  #5  
ClydeB1's Avatar
Recognized Contributor
Thanks Meter: 4,346
 
10,696 posts
Join Date:Joined: May 2009
Donate to Me
More
Quote:
Originally Posted by dani_nec

Another question to clarify ..
we must install the RUU after just lock the bootloader , right?

I understand that it is absolutely necessary, as the custom rom in "relocked" did not start, right?

For some it does appear to reboot, so try that first, if not then you will need to flash a stock ruu.
Quote:
Originally Posted by itismadhan

can u list the CID's that are valid in the OP please?

Firmware will only flash on the phones with the following CID
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__J15
3rd October 2012, 11:35 PM   |  #6  
dani_nec's Avatar
Senior Member
Flag Barcelona
Thanks Meter: 104
 
639 posts
Join Date:Joined: Apr 2012
More
Perfect.

As we know that RUU corresponds with our CID? I for example, taking the HTC__102 ...

All of these questions is to help more people who may have the same doubts lol
3rd October 2012, 11:52 PM   |  #7  
robocik's Avatar
Recognized Developer
Flag Malmö
Thanks Meter: 3,732
 
5,112 posts
Join Date:Joined: Sep 2008
Donate to Me
More
Quote:
Originally Posted by dani_nec

Perfect.

As we know that RUU corresponds with our CID? I for example, taking the HTC__102 ...

All of these questions is to help more people who may have the same doubts lol

here is a list of cids and regions, maybe that helps...
http://forum.xda-developers.com/show....php?t=1195475
The Following User Says Thank You to robocik For This Useful Post: [ View ]
4th October 2012, 12:00 AM   |  #8  
dani_nec's Avatar
Senior Member
Flag Barcelona
Thanks Meter: 104
 
639 posts
Join Date:Joined: Apr 2012
More
Quote:
Originally Posted by robocik

here is a list of cids and regions, maybe that helps...
http://forum.xda-developers.com/show....php?t=1195475

Ok, I know that .. but in the name of the only places RUU asia, europe etc etc. .. CID does not indicate that RUU is for each

understand because in my case, a German HTC__102 the correct RUU would be this:

RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radi o_2.1204.135.20_release_274900_signed

correct? CID for all of Europe (not anchored to company phones of course) would be the same RUU
4th October 2012, 12:14 AM   |  #9  
Senior Member
Thanks Meter: 138
 
670 posts
Join Date:Joined: Nov 2007
More
Quote:
Originally Posted by dani_nec

Ok, I know that .. but in the name of the only places RUU asia, europe etc etc. .. CID does not indicate that RUU is for each

understand because in my case, a German HTC__102 the correct RUU would be this:

RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radi o_2.1204.135.20_release_274900_signed

correct? CID for all of Europe (not anchored to company phones of course) would be the same RUU

You just can use the (odexed) ROM + Recovery + Boot Image from Mikes Thread here: http://forum.xda-developers.com/show....php?t=1546970

Works fine though. Did that on mine (HTC_102) no Problem
4th October 2012, 12:16 AM   |  #10  
dani_nec's Avatar
Senior Member
Flag Barcelona
Thanks Meter: 104
 
639 posts
Join Date:Joined: Apr 2012
More
Quote:
Originally Posted by Higgins12

You just can use the (odexed) ROM + Recovery + Boot Image from Mikes Thread here: http://forum.xda-developers.com/show....php?t=1546970

Works fine though. Did that on mine (HTC_102) no Problem

Ok!! Thanks for the info.. I Download in this moment

But, the RUU indicated for my it's correcto?

thanks

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes