Description:
This is the stock ROM extracted from the leaked 1.12.651.2 RUU I posted earlier with a few modifications.
NOTE: This has not been tested yet considering I do not have the device. As soon as it releases I will test it and confirm. Also, this is not the latest build for the EVO 4G LTE, so there will be updates to this once I get a system dump of the newest build off the phone. This still can be used as a base for any new rom though.
Modifications:
Superuser.apk & su binary (SuperSU by Chainfire)
Busybox 1.19.3
Patched boot.img for 24/7 root via adb.
Future Additions:
Deodexed version coming soon.
Requirements:
EVO 4G LTE
Unlocked bootloader
Custom recovery
Downloads
Jewel_1.12.651.2_Stock_Odex.zip
Download Info
Jewel_1.12.651.2_Stock_Odex.zip MD5: 6b2174e7196ba148f7bd3c276a0e1e0b
And we have a rooted ROM before release. Looks like we've avoided the E3D doldrums... Good thing this is the phone I used my upgrade on
EDIT: Wow, I'm an ungrateful brat. I meant to put a 'thank you' in there somewhere. Good work.
Boom. This phone is already rockin'.
Sent from my HTC Incredible 2 using Tapatalk 2
Amazing! thank you
Sent from my SPH-D710 using xda premium
Sweet that this is out already, days before release day. Thanks!
Sent from my Newtered 3vo.
OP,
You might want to change your updater-script and re-up. This won't flash as is at all.
Never did understand posting a ROM before it's been tested and the device is out, but good job being the first one to do it, I guess!
I have the option to buy out the rest of my contract for $75 to get this phone. I've had the OG EVO since day one and still love it, but can get this one w/o having to pay any contract penalties. My biggest concern and hopefully you guys can help me with this is the unremovable battery. Is this going to be a problem? Does this Evo whip the arse of the OG Evo in terms of specs?
Thanks!
-viperboy- said:
Never did understand posting a ROM before it's been tested and the device is out, but good job being the first one to do it, I guess!
Click to expand...
Click to collapse
It's not a bad thing as long as you know the mount points. His updater-script has it as MTD partitions because dsixda's kitchen didn't have a mount point file for the Jewel. It's atleast not something that would brick a phone, just wouldn't flash.
EDIT: Hey Viper...did you see my tweet?
Good catch, don't know why I didn't think of that. I'll update it today. Does anyone mind sharing the system mount point? Obviously I don't know what it is yet....
-viperboy- said:
Never did understand posting a ROM before it's been tested and the device is out, but good job being the first one to do it, I guess!
Click to expand...
Click to collapse
I haven't worked with ROMs since 2010 on the HeroC, so cut me some slack man lol. Also, thanks for the recognition of posting first.. I guess! I wasn't really going for the title of first-poster... but I guess it could stick
regaw_leinad said:
Good catch, don't know why I didn't think of that. I'll update it today. Does anyone mind sharing the system mount point? Obviously I don't know what it is yet....
Click to expand...
Click to collapse
Here they all are:
Code:
cat /proc/emmc
dev: size erasesize name
mmcblk0p23: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffe00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p35: 4dfffc00 00000200 "system"
mmcblk0p30: 00140200 00000200 "local"
mmcblk0p36: 0dfffe00 00000200 "cache"
mmcblk0p37: 89fffe00 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p38: 27be00000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
mmcblk0p17: 02d00000 00000200 "radio"
mmcblk0p18: 00a00000 00000200 "adsp"
mmcblk0p16: 00100000 00000200 "dsps"
mmcblk0p19: 00500000 00000200 "wcnss"
mmcblk0p20: 007ffa00 00000200 "radio_config"
mmcblk0p24: 00400000 00000200 "modem_st1"
mmcblk0p25: 00400000 00000200 "modem_st2"
mmcblk0p32: 00040000 00000200 "skylink"
mmcblk0p33: 00040000 00000200 "cdma_record"
^^Any speculation why they went to such a small blocksize. The evo 4g had 20000 (or even 40000) erase blocks IIRC.
-viperboy- said:
Never did understand posting a ROM before it's been tested and the device is out, but good job being the first one to do it, I guess!
Click to expand...
Click to collapse
OMG are you getting a 4g lte!?!
RegawMod?
Sent from my MB855 using xda premium
mquinn24 said:
RegawMod?
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Hahaha yo what's up!!? It's been a while! I actually plan on bringing that somewhat back for this phone
alainater said:
OMG are you getting a 4g lte!?!
Click to expand...
Click to collapse
Please stay on topic.
regaw_leinad said:
Hahaha yo what's up!!? It's been a while! I actually plan on bringing that somewhat back for this phone
Click to expand...
Click to collapse
I now know what phone I'm getting
Sent from my MB855 using xda premium
regaw_leinad said:
Description:
This is the stock ROM extracted from the leaked 1.12.651.2 RUU I posted earlier with a few modifications.
NOTE: This has not been tested yet considering I do not have the device. As soon as it releases I will test it and confirm. Also, this is not the latest build for the EVO 4G LTE, so there will be updates to this once I get a system dump of the newest build off the phone. This still can be used as a base for any new rom though.
Modifications:
Superuser.apk & su binary (SuperSU by Chainfire)
Busybox 1.19.3
Patched boot.img for 24/7 root via adb.
Future Additions:
Deodexed version coming soon.
Requirements:
EVO 4G LTE
Unlocked bootloader
Custom recovery
Downloads
Jewel_1.12.651.2_Stock_Odex.zip - Odexed - DOWNLOAD COMING SOON
Download Info
Jewel_1.12.651.2_Stock_Odex.zip MD5: af32146c61e427c47a91f5b8809f8cd8
Click to expand...
Click to collapse
There is Nothing like a stock base
2 more days and counting...
I just talked to Sprint today as I pre ordered the LTE and been waiting on my shipping info , I called today as the release is suppose to be this Friday and they are saying customs is holding up the shipment and they have pushed back the national release date ... anyone else confirm?
Related
I have an LG Optimus M and it would be appreciated if someone could develop a ROM for it. You can find the LG Optimus community at androidforums .com/lg-optimus-m Thanks alot.
I recently purchased the Optimus M and am seconding this request for a ROM.
I would also like to see this happen. Thanks in advance!
Maybe you guys should setup a beer fund.
By the way, I'll have a look at it.
Edit:
And yes, I've taken this from a topic on Androidforums, but it is true. I don't have an Optimus M myself, so:
1) I need a dump of your system.img (replacement apks for people that deleted them by accident).
2) Boot.img (which includes the necessary files like the kernel).
3) Splash.img (to take a look or change metro splash screen.
4) recovery.img (to make a modified recovery).
Edit2:
And a phone to test it on. Beer fund anyone?
i have manage to get a bin not img file and all of the apks
ill send it through message
primluis said:
i have manage to get a bin not img file and all of the apks
ill send it through message
Click to expand...
Click to collapse
Yeah I've got your message. Did you do:
Code:
adb pull system
?
no i got it after i did the update but i now have the
Boot.img
System.img
Recovery.img ill send it in a message
primluis said:
no i got it after i did the update but i now have the
Boot.img
System.img
Recovery.img ill send it in a message
Click to expand...
Click to collapse
Thanks dude, that files are vital! I've already found a custom recovery, now I'll just have to optimize it for the Optimus M. The key-layout is different but that can easily be fixed by replacing default.prop (or build.prop, not completely sure. I can't check it now, I'm on another laptop now)
I'd really appreciate if people could help testing the recovery once it has been published. It won't brick your device.
I would be willing to test it, as long as nothing bad could happen.
lionrain said:
I would be willing to test it, as long as nothing bad could happen.
Click to expand...
Click to collapse
There's a slight little chance it explodes like a nuke when it boots, but except for that little issue, it won't do any damage.
Hey, just thought I'd jump in. I'm pretty much new to smartphones. Since I found xda, I've managed to read enough to learn root explorer, root my Optimus M, delete the bloatware, change the boot, learn adwlauncher and download rom manager.
So how can I help make a custom ROM happen? I think I know enough to flash my own device, except for the recovery/backup stuff worries me.
*Also, my roommate deleted browser.apk on his optimus m (rooted obv), factory reset a few times and has the usual broke market/google problems. Any hope for his phone; he has phone insurance w/metro.
Thank you
Landmand said:
Hey, just thought I'd jump in. I'm pretty much new to smartphones. Since I found xda, I've managed to read enough to learn root explorer, root my Optimus M, delete the bloatware, change the boot, learn adwlauncher and download rom manager.
So how can I help make a custom ROM happen? I think I know enough to flash my own device, except for the recovery/backup stuff worries me.
*Also, my roommate deleted browser.apk on his optimus m (rooted obv), factory reset a few times and has the usual broke market/google problems. Any hope for his phone; he has phone insurance w/metro.
Thank you
Click to expand...
Click to collapse
I think I'm going to base it on an Optimus S/One ROM, all the Optimus phones are pretty similar under the hood.
Thijs96 said:
I think I'm going to base it on an Optimus S/One ROM, all the Optimus phones are pretty similar under the hood.
Click to expand...
Click to collapse
you should talk to richiedaze over at androidforums he is working on it to maybe you can help each other
primluis said:
you should talk to richiedaze over at androidforums he is working on it to maybe you can help each other
Click to expand...
Click to collapse
Yeah I was already thinking of it. I'll take it in consideration. I'm hoping to finish the recovery today!
Edit:The recovery is finished, I replaced the kernel and build.prop. It will be online soon, with a guide included!
http://hotfile.com/dl/94265275/38612ea/recovery.img.html
Place it on your SD-card, than issue in Busybox (make sure to have 'su' rights!) Blue is reaction from terminal
Code:
cat /dev/zero >> /dev/mtd/mtd2
[COLOR="Blue"] write: No space left on device [this is ok, you can ignore][/COLOR]
flash_image boot /sdcard/mynewimage.img
primluis said:
no i got it after i did the update but i now have the
Boot.img
System.img
Recovery.img ill send it in a message
Click to expand...
Click to collapse
Wait wait wait. BTW hi fellow dudes from androidfourms.
You said after the update. Is he working with the files from 2.2.1 and not 2.2?
We need a custom recovery, kernel and rom for 2.2!! Not the evil 2.2.1.
Plus the source for 2.2 for the Optimus M has been released and can be found here: www .lg.com/global/support/opensource/opensource.jsp and choosing "Mobile Phones" from the dropdown menu and typing in LGMS690
If this guy needs the 2.2 files and not the 2.2.1 file they are obtainable.
I was gonna test this recovery but not if it's the 2.2.1 version.
andyo70 said:
Wait wait wait. BTW hi fellow dudes from androidfourms.
You said after the update. Is he working with the files from 2.2.1 and not 2.2?
We need a custom recovery, kernel and rom for 2.2!! Not the evil 2.2.1.
Plus the source for 2.2 for the Optimus M has been released and can be found here: www .lg.com/global/support/opensource/opensource.jsp and choosing "Mobile Phones" from the dropdown menu and typing in LGMS690
If this guy needs the 2.2 files and not the 2.2.1 file they are obtainable.
I was gonna test this recovery but not if it's the 2.2.1 version.
Click to expand...
Click to collapse
I'm in contact with this guy. We're discussing the plans and who does what.
I'm in contact with this guy too as he is also an active member of the androidfourms sub-forum for the Optimus M and has since downgraded his phone back to 2.2 after he gave you the Boot.img, System.img & Recovery.img. Those ones were more than likely from 2.2.1 which running stock was unabled to even be rooted.
You say you want testing done but by your wording you seem to want to keep this all hush, hush. If that's the case no bother. If you want no extra help then so be it.
I will provide he proper files for 2.2 though.
Boot.img - dl.dropbox.com/u/12074340/LGOptimusM-MS690/2.2-Boot.img
System.img - dl.dropbox.com/u/12074340/LGOptimusM-MS690/2.2-stock/system.img
Recover.img - dl.dropbox.com/u/12074340/LGOptimusM-MS690/2.2-stock/recovery.img
Splash.img - dl.dropbox.com/u/12074340/LGOptimusM-MS690/2.2-stock/splash.img
System APK's - dl.dropbox.com/u/12074340/LGOptimusM-MS690/2.2-stock/app.zip
You're welcome.
andyo70 said:
I'm in contact with this guy too as he is also an active member of the androidfourms sub-forum for the Optimus M and has since downgraded his phone back to 2.2 after he gave you the Boot.img, System.img & Recovery.img. Those ones were more than likely from 2.2.1 which running stock was unabled to even be rooted.
You say you want testing done but by your wording you seem to want to keep this all hush, hush. If that's the case no bother. If you want no extra help then so be it.
I will provide he proper files for 2.2 though.
Boot.img - dl.dropbox.com/u/12074340/LGOptimusM-MS690/2.2-Boot.img
System.img - dl.dropbox.com/u/12074340/LGOptimusM-MS690/2.2-stock/system.img
Recover.img - dl.dropbox.com/u/12074340/LGOptimusM-MS690/2.2-stock/recovery.img
Splash.img - dl.dropbox.com/u/12074340/LGOptimusM-MS690/2.2-stock/splash.img
System APK's - dl.dropbox.com/u/12074340/LGOptimusM-MS690/2.2-stock/app.zip
You're welcome.
Click to expand...
Click to collapse
no sorry my bad does are the 2.2 files not the 2.2.1..that i pull out of the androidforums
So then this recovery is built from 2.2 files correct? And have you personally tested it?
F*** it we'll do it live!!!!! LOL!
I'm about to flash this thing to my phone even though we have no custom rom to use with it yet. Pray for a good outcome.
Since yesterday i have been unable to send or receive any mms. I searched and i came up with something about flashing down to 2.1 and then get something to do with apns off the market and restore then flash back???? Can somebody please point me in the right direction. Im running Ginger Tazz 11
rickyjohn said:
Since yesterday i have been unable to send or receive any mms. I searched and i came up with something about flashing down to 2.1 and then get something to do with apns off the market and restore then flash back???? Can somebody please point me in the right direction. Im running Ginger Tazz 11
Click to expand...
Click to collapse
Download a 2.1 Rom such as xtrsense. Boot into recovery and make a nandroid backup of what you are currently using. Do a full wipe and flash the 2.1 rom. Boot it up and sign into google. Open market and install apn backup/restore. Open the app and backup apn's. Reboot into recovery and restore the backup of your rom. Once you boot open market and install apn backup/restore again. Open the app and restore apn's. I know it's worked for others and another guy had suggested another app that doesn't require the flashing but I forget what it was and how he said to do it. Hope this helps and you get things back working again
rickyjohn said:
Since yesterday i have been unable to send or receive any mms. I searched and i came up with something about flashing down to 2.1 and then get something to do with apns off the market and restore then flash back???? Can somebody please point me in the right direction. Im running Ginger Tazz 11
Click to expand...
Click to collapse
Before you take that step, try something easier first:
1. Download "APN OnOff" from the market and install it.
2. Run it and and choose "Show APN list" in the middle of the screen.
3. Press the Menu soft key and choose "Reset to default" on the right.
4. You can try it again now, if this doesn't work, reboot and try again.
If that doesn't work:
A. Download and install "APN Backup and Restore" from the market.
B. Download the zip file I have attached.
C. Unzip it and put the xml file that's in there in a folder called "ApnBackupRestore" in the root of the SD card.
D. Run APN Backup and Restore and choose "Delete APNs". Then choose "Restore APNs" and restore them from the xml file I gave you, which should automatically be listed when you choose that.
Once again, you can try before and after a reboot. Hopefully one of these methods works for you.
Edit: @CondemnedSoul, we were typing at the same time.
FYI the APN backup I attached is from a version of xtrSENSE that was based off the July OTA (probably xtrSENSE v4.5 through 4.6.5). Fresh from a boot, without having done anything else first.
roirraW "edor" ehT said:
Before you take that step, try something easier first:
1. Download "APN OnOff" from the market and install it.
2. Run it and and choose "Show APN list" in the middle of the screen.
3. Press the Menu soft key and choose "Reset to default" on the right.
4. You can try it again now, if this doesn't work, reboot and try again.
If this doesn't work, download and install "APN Backup and Restore" from the market.
Download the zip file I have attached. Unzip it and put the xml file that's in there in a folder called "ApnBackupRestore" in the root of the SD card.
Run APN Backup and Restore and choose "Delete APNs". Then choose "Restore APNs" and restore them from the xml file I gave you, which should automatically be listed when you choose that.
Once again, you can try before and after a reboot. Hopefully one of these methods works for you.
Click to expand...
Click to collapse
I was hoping you'd be in here before long. That's what I was trying to remember and couldn't lol. Didn't feel like looking through tazz's thread for it so I went with what I knew lol.
CondemnedSoul said:
I was hoping you'd be in here before long. That's what I was trying to remember and couldn't lol. Didn't feel like looking through tazz's thread for it so I went with what I knew lol.
Click to expand...
Click to collapse
LMAO! I didn't even feel like going through Tazz's thread to copy and paste what I already wrote to someone else.
I wonder if btbf0 keeps some of his advice in text files? I should keep this one in a text file for future use, eh?
roirraW "edor" ehT said:
LMAO! I didn't even feel like going through Tazz's thread to copy and paste what I already wrote to someone else.
I wonder if btbf0 keeps some of his advice in text files? I should keep this one in a text file for future use, eh?
Click to expand...
Click to collapse
You reading my mind bro? Lol. I was thinking the same thing as I was typing lol. I don't know how many times I've typed that now I don't have a backup of apns to offer. I've never had that problem. Lol
Sent from my Ginger Tazz using XDA App
CondemnedSoul said:
You reading my mind bro? Lol. I was thinking the same thing as I was typing lol. I don't know how many times I've typed that now I don't have a backup of apns to offer. I've never had that problem. Lol
Sent from my Ginger Tazz using XDA App
Click to expand...
Click to collapse
That depends. Are you Vulcan? j/k I've never had that problem once, either. I originally used that second method to help when tethering used to fail for me, and it did help. Then I found APN OnOff, and it was that much quicker and simpler, especially if you don't have a backup handy. It seems to have helped at least some people with SMS/MMS problems just like the second method does. Who knows if it can ever completely replace the second method so I'll keep recommending both just in case.
roirraW "edor" ehT said:
That depends. Are you Vulcan? j/k I've never had that problem once, either. I originally used that second method to help when tethering used to fail for me, and it did help. Then I found APN OnOff, and it was that much quicker and simpler, especially if you don't have a backup handy. It seems to have helped at least some people with SMS/MMS problems just like the second method does. Who knows if it can ever completely replace the second method so I'll keep recommending both just in case.
Click to expand...
Click to collapse
I downloaded that file.... Just in case.. lmao. I'm kinda wondering something too. Gonna do some research
CondemnedSoul said:
I downloaded that file.... Just in case.. lmao. I'm kinda wondering something too. Gonna do some research
Click to expand...
Click to collapse
I am both scared and intrigued! Like watching an impending accident!
You realize the OP isn't going to recognize his own thread when he gets back here?
roirraW "edor" ehT said:
I am both scared and intrigued! Like watching an impending accident!
You realize the OP isn't going to recognize his own thread when he gets back here?
Click to expand...
Click to collapse
That's ok.... I'm confused lmao. I'm looking at the apn's and comparing them to some of the ones in the rom's I have on my hd and trying to come up with an idea but things aren't making sense lmao. He won't recognize it but that's ok.. he got what he needs in your reply lol.
BTW... check your pm box
CondemnedSoul said:
That's ok.... I'm confused lmao. I'm looking at the apn's and comparing them to some of the ones in the rom's I have on my hd and trying to come up with an idea but things aren't making sense lmao. He won't recognize it but that's ok.. he got what he needs in your reply lol.
BTW... check your pm box
Click to expand...
Click to collapse
I have looked into APNs enough sometime in the past that I noticed weird things, too. Such as the differences between the July OTA APNs and those in non-stock based ROMs, but obviously the non-stock based ROMs work, at least most of the time and definitely do to start with. Bizarre. If the APNs are so critical, why do other APNs work at all?
Edit: I wonder if the APNs included with the March OTA are any different?
roirraW "edor" ehT said:
I have looked into APNs enough sometime in the past that I noticed weird things, too. Such as the differences between the July OTA APNs and those in non-stock based ROMs, but obviously the non-stock based ROMs work, at least most of the time and definitely do to start with. Bizarre. If the APNs are so critical, why do other APNs work at all?
Edit: I wonder if the APNs included with the March OTA are any different?
Click to expand...
Click to collapse
Not sure if they are yet or not...
I'm wondering if any of the people having this issue have or had quick settings installed at some point or if they have it currently and use it. Seems to mess up the Incredible's apns. I found this post on another site and would be intereted if one of these guys with the mms problem would be willing to make a backup of their apns and post it to see if something is being disabled like what's happened before on the dinc. If so It could possibly be real easy to fix lol. Check it out...
http://androidforums.com/776817-post3.html
roirraW "edor" ehT said:
I have looked into APNs enough sometime in the past that I noticed weird things, too. Such as the differences between the July OTA APNs and those in non-stock based ROMs, but obviously the non-stock based ROMs work, at least most of the time and definitely do to start with. Bizarre. If the APNs are so critical, why do other APNs work at all?
Edit: I wonder if the APNs included with the March OTA are any different?
Click to expand...
Click to collapse
CondemnedSoul said:
Not sure if they are yet or not...
Click to expand...
Click to collapse
They're exactly the same, I just looked. At least as far as the APNs in the March 2011 OTA released by btbf0 compared to the APNs in xtrROM v5.0, which was released before the March 2011 OTA (not to be confused with xtrSENSE v5.0, which was released after and based on the March 2011 OTA).
CondemnedSoul said:
I'm wondering if any of the people having this issue have or had quick settings installed at some point or if they have it currently and use it. Seems to mess up the Incredible's apns. I found this post on another site and would be intereted if one of these guys with the mms problem would be willing to make a backup of their apns and post it to see if something is being disabled like what's happened before on the dinc. If so It could possibly be real easy to fix lol. Check it out...
http://androidforums.com/776817-post3.html
Click to expand...
Click to collapse
Another good reminder. I forgot I might not have had specific SMS/MMS issues, but I did have a problem with Data at all, and I used Quick Settings back in June or July around that time. I found that it was Quick Settings method, at least at the time, for turning data on and off. Apparently Quick Settings isn't alone in this, some apps/widgets still use this "evil" method. I'm under the impression that EasySwitch, which I bought when running xtr ROMs, but is redundant under CM6+ with notification power widgets, uses a proper method for turning data on and off.
I wonder if anyone knows why the APNs used in the non-stock based ROMs are different from the stock APNs, and why they work anyway.
roirraW "edor" ehT said:
I wonder if anyone knows why the APNs used in the non-stock based ROMs are different from the stock APNs, and why they work anyway.
Click to expand...
Click to collapse
I don't know... the stock one has all the 0's where the rom's have different numbers. All the roms are the same but not the same as the stock and the stock has 3 apn's where the roms I've looked at so far have 2. I have no idea lol.
CondemnedSoul said:
I don't know... the stock one has all the 0's where the rom's have different numbers. All the roms are the same but not the same as the stock and the stock has 3 apn's where the roms I've looked at so far have 2. I have no idea lol.
Click to expand...
Click to collapse
I see only 2 APNs in the stock ROM. Now, I'm confused.
Code:
apns version="6">
<apn carrier="Android"
mcc="310"
mnc="995"
apn="internet"
user="*"
server="*"
password="*"
mmsc="null"
/>
<!--apn carrier="TelKila"
mcc="310"
mnc="260"
apn="internet"
user="*"
server="*"
password="*"
mmsc="null"
/-->
</apns>
This is the ones from the July OTA though lol
PHP:
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns count="3">
<apn name="CDMA" numeric="00000" mcc="000" mnc="00" apn="0" user="null" server="null" password="null" proxy="null" port="" mmsproxy="" mmsport="" mmsprotocol="" mmsc="" type="*" />
<apn name="Production" numeric="00000" mcc="000" mnc="00" apn="1" user="null" server="null" password="null" proxy="null" port="" mmsproxy="" mmsport="" mmsprotocol="2.0" mmsc="http://mms.vtext.com/servlets/mms" type="mms" />
<apn name="Android" numeric="310995" mcc="310" mnc="995" apn="internet" user="*" server="*" password="*" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="null" type="null" />
</apns>
CondemnedSoul said:
This is the ones from the July OTA though lol
PHP:
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns count="3">
<apn name="CDMA" numeric="00000" mcc="000" mnc="00" apn="0" user="null" server="null" password="null" proxy="null" port="" mmsproxy="" mmsport="" mmsprotocol="" mmsc="" type="*" />
<apn name="Production" numeric="00000" mcc="000" mnc="00" apn="1" user="null" server="null" password="null" proxy="null" port="" mmsproxy="" mmsport="" mmsprotocol="2.0" mmsc="http://mms.vtext.com/servlets/mms" type="mms" />
<apn name="Android" numeric="310995" mcc="310" mnc="995" apn="internet" user="*" server="*" password="*" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="null" type="null" />
</apns>
Click to expand...
Click to collapse
That reminds me, that I think there's an inconsistency between what APNs the flashable ROM files contain, and what ends up being in a running ROM. Are those three from the actual OTA file or from a running OTA ROM?
What I've given so far are from the flashable March 2011 OTA file provided by bftb0 (Reference ROM v1) and xtrROM v5.0 (based on the July OTA), without actually flashing them and looking in system/etc.
I just looked and FlashBack21 v2 (no radio version) has the same APNs in the flashable file.
roirraW "edor" ehT said:
That reminds me, that I think there's an inconsistency between what APNs the flashable ROM files contain, and what ends up being in a running ROM. Are those three from the actual OTA file or from a running OTA ROM?
What I've given so far are from the flashable March 2011 OTA file provided by bftb0 (Reference ROM v1) and xtrROM v5.0 (based on the July OTA), without actually flashing them and looking in system/etc.
I just looked and FlashBack21 v2 (no radio version) has the same APNs in the flashable file.
Click to expand...
Click to collapse
Ok... those were from the file you posted in post 3..
Sent from my Ginger Tazz using XDA App
I cannot get get Senseless to bootup after reimstall... All I get is a black screen... How do I do a recovery so I can get Sensless back?
Kilch said:
I cannot get get Senseless to bootup after reimstall... All I get is a black screen... How do I do a recovery so I can get Sensless back?
Click to expand...
Click to collapse
You should learn not to flash unstable ROMs based off unstable leaks for a start. Try flashing an older boot.img from Fastboot.
Deathbyfugu said:
You should learn not to flash unstable ROMs based off unstable leaks for a start. Try flashing an older boot.img from Fastboot.
Click to expand...
Click to collapse
Yea, first time this has ever happened... How can I get boot.img and get it on there.
Kilch said:
Yea, first time this has ever happened... How can I get boot.img and get it on there.
Click to expand...
Click to collapse
Download the "stock rooted kernel" from http://themikmik.com/showthread.php?10674-ROM-MikRoms-Ineffabilis-v1-0-12-31-11-Sense-3-5-Beats-Tweaks-1-02-605-6 extract the boot.img from the PH98IMG.zip and place it in the same folder you have Fastboot located in. The execute (with your phone in the fastboot menu) "fastboot flash boot ~/path/to/your/boot.img" then after that (hopefully) works "fastboot reboot". Look here for more info: http://wiki.cyanogenmod.com/wiki/Fastboot
Lastly - learn from your mistakes. You can brick your phone more easily than you think.
Deathbyfugu said:
Download the "stock rooted kernel" from http://themikmik.com/showthread.php?10674-ROM-MikRoms-Ineffabilis-v1-0-12-31-11-Sense-3-5-Beats-Tweaks-1-02-605-6 extract the boot.img from the PH98IMG.zip and place it in the same folder you have Fastboot located in. The execute (with your phone in the fastboot menu) "fastboot flash boot ~/path/to/your/boot.img" then after that (hopefully) works "fastboot reboot". Look here for more info: http://wiki.cyanogenmod.com/wiki/Fastboot
Lastly - learn from your mistakes. You can brick your phone more easily than you think.
Click to expand...
Click to collapse
fastboot shall work just fine.
nice write up!
Deathbyfugu said:
Download the "stock rooted kernel" from http://themikmik.com/showthread.php?10674-ROM-MikRoms-Ineffabilis-v1-0-12-31-11-Sense-3-5-Beats-Tweaks-1-02-605-6 extract the boot.img from the PH98IMG.zip and place it in the same folder you have Fastboot located in. The execute (with your phone in the fastboot menu) "fastboot flash boot ~/path/to/your/boot.img" then after that (hopefully) works "fastboot reboot". Look here for more info: http://wiki.cyanogenmod.com/wiki/Fastboot
Lastly - learn from your mistakes. You can brick your phone more easily than you think.
Click to expand...
Click to collapse
Thank you so much. I am DLing it now. Will let you know how I make out. Thanks again.
All set. Thank you sooo much. BAck up and running.
Steve
now click the THANKS button!
And then click it on Deathbyfugu's post too.
Sent from my ADR6425LVW using Tapatalk
feralicious said:
And then click it on Deathbyfugu's post too.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Done to both posts. I forgot about that. Thanks for the reminder.
Deathbyfugu said:
You should learn not to flash unstable ROMs based off unstable leaks for a start. Try flashing an older boot.img from Fastboot.
Click to expand...
Click to collapse
Well... not if you are not experienced with Android rooting and flashing.
Marine6680 said:
Well... not if you are not experienced with Android rooting and flashing.
Click to expand...
Click to collapse
Can't learn to swim without getting your feet wet.
Glad it worked for you! I've had some panics back in my Captivate days
Sent from my ADR6425LVW using xda premium
Marine6680 said:
Well... not if you are not experienced with Android rooting and flashing.
Click to expand...
Click to collapse
LMAO, that was cute and funny. LEarning curve. This is how I learn with little time I have. he he
MrSmith317 said:
Can't learn to swim without getting your feet wet.
Click to expand...
Click to collapse
Yes, Mr Smith, you're so correct. Besides, I love to tinker, even it means I brick the darn thing.
Deathbyfugu said:
Glad it worked for you! I've had some panics back in my Captivate days
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Brings me back to my DInc days. Do, crash and burn, then learn. Thanks again.
No problems unlocking/rooting ever. It just comes from making sure you download all pertinent original files and be ready to rollback as needed. Don't just jump in like a crazy person.
... Like I did the first time I rooted my DINC.
Sent from my Unlocked/Rooted Rezound running CleanROM 2.0/AmonRa
So I have just installed CleanROM 2.0 Ice Cream Sandwich Edition and I have to admit, HUGE improvements since last night. Very happy I finally got ICS.
One question I have though... when will we see a Senseless version. I'm running ADW rather than the Sense. Not a huge fan of it. lol
Kilch said:
So I have just installed CleanROM 2.0 Ice Cream Sandwich Edition and I have to admit, HUGE improvements since last night. Very happy I finally got ICS.
One question I have though... when will we see a Senseless version. I'm running ADW rather than the Sense. Not a huge fan of it. lol
Click to expand...
Click to collapse
Senseless is already there
Sent from my Transformer TF101 using xda premium
blestsol said:
Senseless is already there
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Yea, I saw and I'm excited. Hopefully by next weeks end, I'll have it in my HTCR.
Now that we have s-off can the devs please start adding the kernel to the rom so we can flash it all in one?
I just think that it will make it easier for the average user.
Devs have become accustomed to packaging roms this way for quite some time and many users are still having issues getting S-Off.
I wouldn't be surprised if the next round of updates packaged the Kernel/Rom together.
I due time my friend.
Sent from my ADR6425LVW
Be nice if someone familiar with the process or the script could just post how to add the boot.IMG to current roms so we could add them in and flash in recovery. Think con posted templates, but assuming we would still need a script added. Otherwise, I am patient
Sent from my ADR6425LVW using xda premium
mjh68 said:
Be nice if someone familiar with the process or the script could just post how to add the boot.IMG to current roms so we could add them in and flash in recovery. Think con posted templates, but assuming we would still need a script added. Otherwise, I am patient
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
It should work if you just put the boot.img inside the kernel folder of the roms zip. I just flashed a kernel with cons template and it worked perfectly
The way I have done it to my GB ROM is to add the following code to the updater-script and remove the previous code written by con. It worked fine in GB but so far I have had no luck with ICS. I have PMed a couple of the pros for a little assistance and try and figure out what the issue could be.
This is the code used in previous ROMs:
Code:
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
The Devs already know how to do it..just a matter of implementation.
Sent from my ADR6425LVW
Marcismo55 said:
The Devs already know how to do it..just a matter of implementation.
Sent from my ADR6425LVW
Click to expand...
Click to collapse
Well I'm still waiting for them to let me in on the big secret. Con said the code should work and he would look into it if/when he gets time. Also brought it up with scott and I believe he was going to look at it as well. I do know of another way of doing it (like they do on the Xoom) but I would need some additional information.
for anyone interested the ROM with the kernel (flashes when you flash the ROM) is posted here as a test:
http://forum.xda-developers.com/showpost.php?p=25228652&postcount=78
My 3.6 ROM has both versions now. Give it a try and let me know how it works for you.
NilsP said:
My 3.6 ROM has both versions now. Give it a try and let me know how it works for you.
Click to expand...
Click to collapse
Ya i'm not doing both versions in my ROMs. I just don't see it as being necessary. If you have the kernel in place already there is no need to reflash it. All it does is make me want to blow my brains out every time I can't boot into recovery because of the damn PH98IMG. Thats just me though its good to see you supporting both. Reality is I would rather just post the kernels separate then to have the phone create the images.
zone23 said:
Ya i'm not doing both versions in my ROMs. I just don't see it as being necessary. If you have the kernel in place already there is no need to reflash it. All it does is make me want to blow my brains out every time I can't boot into recovery because of the damn PH98IMG. Thats just me though its good to see you supporting both. Reality is I would rather just post the kernels separate then to have the phone create the images.
Click to expand...
Click to collapse
Same here...
TB13 said:
Same here...
Click to expand...
Click to collapse
Glad I'm not the only one..
Due to the nature of the s-off method many people decided to forego s-off. Getting s-off was quite difficult and many people are still having issues with the timing. I don't see devs switching to adding the kernel to their .zips unless they put downloads for both s-off and s-on devices.
Sent from my ADR6425LVW using XDA
So hi guys,
I have a Desire X which i unfortunately upgraded to Jelly Bean. Knowing HTCs bullshat update stuff, it seems unlikely that they will fix the sound issues. To me, the sound issue sounds like a fcked up EQ or something. Can we use the libs & files from 4.0.4 in JB to fix the issue?
Race55.
race55 said:
So hi guys,
I have a Desire X which i unfortunately upgraded to Jelly Bean. Knowing HTCs bullshat update stuff, it seems unlikely that they will fix the sound issues. To me, the sound issue sounds like a fcked up EQ or something. Can we use the libs & files from 4.0.4 in JB to fix the issue?
Race55.
Click to expand...
Click to collapse
As eager as u were for the update (including me), HTC had to hurry up releasing untested updates. Dont give up on a company so soon. This kind of stuff happens. A mid-range phone has a usable life of almost 2 years where it always gets major/minor updates. After that, the devs do the magic (The classic desire has 4.2.2 now and been living for 4+ years).
Trust me, people says Xperia and some samsung phones of equal price are better then what HTC offers, then do one thing,
1.Check the build quality
2. Check the design.
3. Check the interface quality
4. Check the price.
HTC ticks most of the marks always. Really try to use an Xperia or Touchwiz interface and ull be hating it very soon (I know i would).
Rest is your decision. You can root and try to come back to an ICS rom, it should be possible technically, but i dont know for certain until i try it myself.
Regards
Yasir
neXus PRIME said:
As eager as u were for the update (including me), HTC had to hurry up releasing untested updates. Dont give up on a company so soon. This kind of stuff happens. A mid-range phone has a usable life of almost 2 years where it always gets major/minor updates. After that, the devs do the magic (The classic desire has 4.2.2 now and been living for 4+ years).
Trust me, people says Xperia and some samsung phones of equal price are better then what HTC offers, then do one thing,
1.Check the build quality
2. Check the design.
3. Check the interface quality
4. Check the price.
HTC ticks most of the marks always. Really try to use an Xperia or Touchwiz interface and ull be hating it very soon (I know i would).
Rest is your decision. You can root and try to come back to an ICS rom, it should be possible technically, but i dont know for certain until i try it myself.
Regards
Yasir
Click to expand...
Click to collapse
I have always had HTC Devices, so i know my stuff pretty well. The point is, the Jelly Bean update upgraded the hboot, so that the older stuff won't work. I dunno if anyone has tried a ruu yet? It might work.
neXus PRIME said:
As eager as u were for the update (including me), HTC had to hurry up releasing untested updates. Dont give up on a company so soon. This kind of stuff happens. A mid-range phone has a usable life of almost 2 years where it always gets major/minor updates. After that, the devs do the magic (The classic desire has 4.2.2 now and been living for 4+ years).
Trust me, people says Xperia and some samsung phones of equal price are better then what HTC offers, then do one thing,
1.Check the build quality
2. Check the design.
3. Check the interface quality
4. Check the price.
HTC ticks most of the marks always. Really try to use an Xperia or Touchwiz interface and ull be hating it very soon (I know i would).
Rest is your decision. You can root and try to come back to an ICS rom, it should be possible technically, but i dont know for certain until i try it myself.
Regards
Yasir
Click to expand...
Click to collapse
Yes, someone please try reverting back to ics
Ehm.... http://forum.xda-developers.com/showthread.php?t=1399331 Maybe we can try something similar for our Desire X?
?
SaadCrackz said:
Yes, someone please try reverting back to ics
Click to expand...
Click to collapse
Why does htc have to limit their devices so much? The brand will die if this continues...
Look at samsung or sony you get full root no s-on or anything...
race55 said:
Ehm.... http://forum.xda-developers.com/showthread.php?t=1399331 Maybe we can try something similar for our Desire X?
Click to expand...
Click to collapse
Not possible with this method.
But you can use a custom ICS ROM with some edit to the mount point in the updater-script.
Or restore an ICS nand backup
?
ckpv5 said:
Not possible with this method.
But you can use a custom ICS ROM with some edit to the mount point in the updater-script.
Or restore an ICS nand backup
Click to expand...
Click to collapse
I think i have an ics nandroid backup do you want me to upload it?
SaadCrackz said:
Why does htc have to limit their devices so much? The brand will die if this continues...
Look at samsung or sony you get full root no s-on or anything...
Click to expand...
Click to collapse
Look at Samsung's complicated system... There's this Odin thing, download mode, roms in tar files... HTC is simple. They unlock our bootloader, and they let us use fastboot(official android tinkering tool distributed by Google). Then look at GUIs. Touch wiz is horrible, ugly and unthemeable. Then look at sense.
Flowed from my HTC branded muffin...
SaadCrackz said:
I think i have an ics nandroid backup do you want me to upload it?
Click to expand...
Click to collapse
Which Nand backup that you have, for which CID, which version no. ?
OK...
ckpv5 said:
Which Nand backup that you have, for which CID, which version no. ?
Click to expand...
Click to collapse
My nand backup is for CID 0_16, Version 1.18.401.1, January 2013
EDIT: Its for cwm
SaadCrackz said:
My nand backup is for CID 0_16, Version 1.18.401.1, January 2013
EDIT: Its for cwm
Click to expand...
Click to collapse
I see.. for 1.18.401.1 we have RUU so there is no need for a Nand backup.
Thanks for the offer.
?
ckpv5 said:
I see.. for 1.18.401.1 we have RUU so there is no need for a Nand backup.
Thanks for the offer.
Click to expand...
Click to collapse
Can i use it if i wanna go back to ics?
SaadCrackz said:
Can i use it if i wanna go back to ics?
Click to expand...
Click to collapse
Ahh... sorry... I miss the title of this thread...
No.. you can't use the RUU to go back to ICS but you need to make a Custom Stock ICS ROM with the new mount point for JB and also the ICS boot.img with it's modules.
I always keep changing ICS ROM and JB ROM on my One X which has a JB hboot.
Can You Make One?
ckpv5 said:
Ahh... sorry... I miss the title of this thread...
No.. you can't use the RUU to go back to ICS but you need to make a Custom Stock ICS ROM with the new mount point for JB and also the ICS boot.img with it's modules.
I always keep changing ICS ROM and JB ROM on my One X which has a JB hboot.
Click to expand...
Click to collapse
Can you make one for our desire X ?
SaadCrackz said:
Can you make one for our desire X ?
Click to expand...
Click to collapse
No I will not as I don't really have time to provide support.
I gave all the tips so any Dev can make one or users can mod any available ICS ROMs to work on a JB hboot. It just need a change of mount point in the updater-script.
ckpv5 said:
No I will not as I don't really have time to provide support.
I gave all the tips so any Dev can make one or users can mod any available ICS ROMs to work on a JB hboot. It just need a change of mount point in the updater-script.
Click to expand...
Click to collapse
So, it will be possible to flash (for example) MyOneDx after updating to JB?
MaartenXDA said:
So, it will be possible to flash (for example) MyOneDx after updating to JB?
Click to expand...
Click to collapse
Yep... even your ROM should work. Just change the mount point in updater-script and use the recovery for JB by atis112.
And use ICS boot.img either stock, atis112 kernel or neXusPRIME kernel.
ICS mount point:
mmcblk0p25: 3bdffe00 00000200 "system"
mmcblk0p27: 0ffffe00 00000200 "cache"
mmcblk0p26: 4cfffe00 00000200 "userdata"
mmcblk0p28: 017ade00 00000200 "devlog"
JB mount point:
mmcblk0p24: 3bdffe00 00000200 "system"
mmcblk0p26: 0f000000 00000200 "cache"
mmcblk0p25: 4cfffe00 00000200 "userdata"
mmcblk0p28: 017ade00 00000200 "devlog"
ckpv5 said:
Yep... even your ROM should work. Just change the mount point in updater-script and use the recovery for JB by atis112.
And use ICS boot.img either stock, atis112 kernel or neXusPRIME kernel.
ICS mount point:
mmcblk0p25: 3bdffe00 00000200 "system"
mmcblk0p27: 0ffffe00 00000200 "cache"
mmcblk0p26: 4cfffe00 00000200 "userdata"
mmcblk0p28: 017ade00 00000200 "devlog"
JB mount point:
mmcblk0p24: 3bdffe00 00000200 "system"
mmcblk0p26: 0f000000 00000200 "cache"
mmcblk0p25: 4cfffe00 00000200 "userdata"
mmcblk0p28: 017ade00 00000200 "devlog"
Click to expand...
Click to collapse
Imma try this, I hope it works. Jelly bean sucks arse. Can I also restore my 4.0.4 nandroid?
Sent from my Desire X, raped by HTCs Jelly Bean update
Did i do it right?
ckpv5 said:
Yep... even your ROM should work. Just change the mount point in updater-script and use the recovery for JB by atis112.
And use ICS boot.img either stock, atis112 kernel or neXusPRIME kernel.
ICS mount point:
mmcblk0p25: 3bdffe00 00000200 "system"
mmcblk0p27: 0ffffe00 00000200 "cache"
mmcblk0p26: 4cfffe00 00000200 "userdata"
mmcblk0p28: 017ade00 00000200 "devlog"
JB mount point:
mmcblk0p24: 3bdffe00 00000200 "system"
mmcblk0p26: 0f000000 00000200 "cache"
mmcblk0p25: 4cfffe00 00000200 "userdata"
mmcblk0p28: 017ade00 00000200 "devlog"
Click to expand...
Click to collapse
Is this good?