Related
hello, with last night gingerbread leak many of us unrooted users or myself a rooted user who was to lazy to download the rooted verison because the download link was broken. are now stuck with know way of going back. now not everyone cares about beeing stuck but my self and others miss out of the option to root i personaly miss my bamf asop rom that i was falling in love with. from what i gather we are in a holding pattern at the moment i was wondering if any of the great devs over here had attempted or mad any progess in rooting this last leak or if we have found a method to role back to mr2 so we could root that. any insight would be appricated
Didn't alpharev and unrevoked just release a new method that works with the tbolt? I know they released its a beta, but it works on the inc2 with gb
Sent from my ThunderBolt using XDA App
i dont think that will work for the tbolt
Before saying it won't work on TBolt try it out. Also I believe it does work. I'm not sure if it will work with this new leak but it works on the TBolt from what I've seen.
i do apolgize the post went out before it was finished and because im new to this fourm i have to wait 5mins before making any changes. i would love to try it its worth a shot can someone post me a link and ill report back if it works
this is exactly why i do not install leaked radios or leaked shipped ruu's.
I know it works on the Inc 2 and I'm almost positive that it included the tbolt in the list of devices when your downloading the beta code. It allows you to root the shipped gb on the Inc 2, may work on this version of gb as well.
Sent from my ThunderBolt using XDA App
just trade your TBolt for an LG Revolution. everyone says that one's the best.
Just go over to the Inc 2 forum here on xda and in general section there should be a thread about rooting gb.
http://forum.xda-developers.com/showthread.php?t=1219246
Sent from my ThunderBolt using XDA App
ok i think i can see the light next issue when i download the program and run it the screen just shows for a second and then goes away is there any other way to get the serial number because it does look like this will work
yodatom10 said:
ok i think i can see the light next issue when i download the program and run it the screen just shows for a second and then goes away is there any other way to get the serial number because it does look like this will work
Click to expand...
Click to collapse
The Revolution and AlphaRevX sites appear to be down for the time being, so even if it does work, it won't without being able to obtain a key for the beta release through the website.
Assuming you still have S-off and a recovery, i.e. you didn't flash the RUU, all hope isn't lost. However if you did, I'm glad I'm not you at the moment.
loonatik78 said:
The Revolution and AlphaRevX sites appear to be down for the time being, so even if it does work, it won't without being able to obtain a key for the beta release through the website.
Assuming you still have S-off and a recovery, i.e. you didn't flash the RUU, all hope isn't lost. However if you did, I'm glad I'm not you at the moment.
Click to expand...
Click to collapse
no stupid me did not wait for the download to be fixed flashed the ruu. and am stuck with s on and sense
yodatom10 said:
ok i think i can see the light next issue when i download the program and run it the screen just shows for a second and then goes away is there any other way to get the serial number because it does look like this will work
Click to expand...
Click to collapse
Isn't it under the battery or on the back cover? Or somewhere in settings, about?
Were you able to get a beta key?
Sent from my ThunderBolt using XDA App
kallyjk said:
Isn't it under the battery or on the back cover? Or somewhere in settings, about?
Were you able to get a beta key?
Sent from my ThunderBolt using XDA App
Click to expand...
Click to collapse
i found the serial number in the about section and it spit out a beta key were do i go from there
rooting on gingerbread is pretty much the same process as before, just subbing out psneuter for fr3vo.
I GOT ROOT WOHO thanks to all xda is a amazing place
This is why I would encourage everyone who is rooted to install that hard patched hboot in the dev forum and this problem wouldn't exist. Also not flashing RUUs carelessly Helps but I digress. The only problem with the patched hboot is getting back to s-on is a bit harder. You have to use fastboot with a special command to flash an s-on hboot. Personally I think everyone who is rooted should learn how to use fastboot and ADB anyway but once again digressing. (prob not a real word LOL)
As far as fixing the issue hopefully the Revolutionary tool will still work on that build just have to check the hboot version. If not, as stated previously replacing psnueter with frEVO in the original downgrade process should work.
Edit: sorry a little late I suppose.
Sent from my HTC Thunderbolt
Glad this all worked out for you Yoda, you sounded pretty peeved over at AC Hope you learned a lesson!
Wow, glad you got it fixed. At least now you'll know to be more patient in the future ;-)
Sent from my HTC Thunderbolt running Uber BAMF
I i have painstakingly deodexed this whole rom . Trying to get this apk . Its a system file so it wont just install..
And renaming my current blurhome to blurhome.apk.bak causes forcecloses and i have to battery pull
its obviously beyond me because even when i do get it to recognize, it says This is not a blur device
i even setup motoblur and still no go
i also left my blurhome.apk there as well.. Still no go
this droid 3 blurhome should just work . But obviously its missing some dependiencies. If anyone can figure it out let me know
http://www.multiupload.com/Z9B7BSVMG0
here is the entire system dump
or atleast what autodeotool would deodex without physically having the phone
An Android dependency walker would be real nice right now
Probably have more luck if the entire deodexed system dump was posted.
I got the whole dump, everything I've tried so far is being a pain in the butt to deodex the whole thing >_<
Sent from my Moto ATRIX 4g DROID
Im sure im close though
Sent from my Moto ATRIX 4g DROID
I got everything from the framework folder deodex, just the app folder screws up :/ but yeah im close lol
Sent from my Moto ATRIX 4g DROID
Well i got everything deodex finnaly work if ne one wants it let me know?
Sent from my Moto ATRIX 4g DROID
any
luck?
Its 325 a.m here lol haven't played around with it yet but I got all the framework and apps all deodex and I mean everything and about time to lol
Sent from my Moto ATRIX 4g DROID
Edit: This Is It>>>http://www.4shared.com/file/ImzjgtzM/droid3deodex.html if anyone wants it ;
i would try..
ZOMBI3 said:
Well i got everything deodex finnaly work if ne one wants it let me know?
Sent from my Moto ATRIX 4g DROID
Click to expand...
Click to collapse
i'd try installing it..did u get it up and running?
Oh I haven't done ne thing more yet then getting it deodex. That's what I meant when I said got it to work,sorry for ne confusion, but two nights ago I don't remember what I did to the blurhome2 apk exactly i was up real late,but I manage to get it working for a short while like it would display got to add some widgets to it then I encountered force closes right away? And I used xultimate to deodex if you two were wondering
Sent from my Moto ATRIX 4g DROID
This is the droid bionic dump deodex, from mydroidworld, http://www.multiupload.com/PUNT30M31T im sure we will be able to get the blurhome2 apk to work from this because im sure the blurhome2apk from droid 3 is missing something because its like 6ish mb, and the blurhome2apk from the bionic is 13ish mb just a lit more then the blurhome apk from our atrix, i got the camera from it working without any problems and the bionic livewallpaper from it....take a look at this i doubt i'll be able to do anything right now with it been super busy thanks cheers
Edit it the cam disappears after 2 reboot :/
Edit: Oops I meant the DROID 3 blur2 is 8ish mb not 6 hah
Sent from my Moto ATRIX 4g DROID
Hmmm...
MOD - First off i dont really know if itll help but i decompiled the apk and edited the androidmanifest.xml file which i changed the min sdk to 9 and the target to 11 the recompiled and installed everything is working besides a bit of lag but im going to edit the apk some more tom and theme to my tastes. First public mod so if it helps please hit the thank button or give some credit.
grizzfu said:
MOD - First off i dont really know if itll help but i decompiled the apk and edited the androidmanifest.xml file which i changed the min sdk to 9 and the target to 11 the recompiled and installed everything is working besides a bit of lag but im going to edit the apk some more tom and theme to my tastes. First public mod so if it helps please hit the thank button or give some credit.
Click to expand...
Click to collapse
Is it the one from the bionic? That I posted?
Yea, Like i said i dont know if it does any good to change it because i tried to install it and drop it in the system/apps folder neither worked but this did.
Could just be a fluke idk.
Well that's awesome still, so I was wondering about the camera It works at first then it the disappears in the app drawer the second time I reboot? Got ne ideas? And do u think u could post the blur2 apk the u modify? Id love to try it
The D3 Camera is readily available through the Dev forums alot of rom developers offer it as a addon CWM File and i use it everyday with no issues. Did you drop the apk in the system folder or install it?
And yea ill upload the blurhome2.apk in just a min. Crappy upload speeds here.
Here Ya Go - http://www.multiupload.com/LMNZFJ74YJ
Did notice that you cant select it to be the default launcher, i have to click on the MBSetup icon then skip the setup to get back to it? Ill look into this a little later my head hurts to bad right now.
Eh I don't like the DROID 3 cam cuz of the 5mp issue lol n the bionic cam I drop it in system apps rw r r, that's awesome I hate crappy upload speeds lol sorry
Thank you your awesome
Sent from my Moto ATRIX 4g DROID
Didn't notice this before, but according to http://stats.cyanogenmod.com/ , there are two installs for 'daytona' (codename for Droid X2).
Also, cvpcs recently tweeted "i'll see what i can muster together. need to get some DX and X2 stuff posted".
Good news? Old news?
I didn't know they had even started on the X2, I knew the X1 already had it, or an RC at least.
cvpcs, who I believe ported CM4DX, just recently got the X2, but has been busy with life.
Also, the Droid X is becoming, or already is, an official CM supported device.
Before my brother got his X2, I was trying to get the CM7 build on it, but couldn't find the correct one on their site, this was almost 2 months ago though.
Actually I'm pretty sure that was me... I've been working on porting some cyanogen components out of an unofficial atrix build and one of the few things that did work was stats. Installed it twice
Sent from my DROID X2 using xda premium
drapp said:
Actually I'm pretty sure that was me... I've been working on porting some cyanogen components out of an unofficial atrix build and one of the few things that did work was stats. Installed it twice
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Do tell plz
They were just some of the apps i pulled from my cm7 on my old droid 2. I have however Been messing around on the ATRIX forums of cyanogen and noticed nighties being posted so I've been pulling as much as I can out in an effort to port it minus the kernel tweaks. As far as progress goes I've gone from it not installing at all, to starting to install and failing for a few different reasons, to installing successfully but stuck at boot logo... after 4 hours of sbfing and flashing my current status is successfully installs but starts bootlooping about 3 mins into powering on and not sure what my next move should be. Haven't gotten it to launch yet. 2 more sbfs and subsequent framework edits and im calling it a night
drapp said:
They were just some of the apps i pulled from my cm7 on my old droid 2. I have however Been messing around on the ATRIX forums of cyanogen and noticed nighties being posted so I've been pulling as much as I can out in an effort to port it minus the kernel tweaks. As far as progress goes I've gone from it not installing at all, to starting to install and failing for a few different reasons, to installing successfully but stuck at boot logo... after 4 hours of sbfing and flashing my current status is successfully installs but starts bootlooping about 3 mins into powering on and not sure what my next move should be. Haven't gotten it to launch yet. 2 more sbfs and subsequent framework edits and im calling it a night
Click to expand...
Click to collapse
Stupid question but did you remember to Wipe Everything Individually... From data to dalvic cache?
ericerk said:
Stupid question but did you remember to Wipe Everything Individually... From data to dalvic cache?
Click to expand...
Click to collapse
Yeah, wiped cache and delvik b4 nandroiding to save a little space, and again after just in case. Wiped data then installed. After install, wiped batt stats and fixed permissions while still in tenfars recovery. Then rebooted. After boot loop went into stock recovery and wiped data/cache again. Still no luck. [email protected]#ty thing is I go out of the country on business for a month so not gonna have time. Im working with the 1.2rc3 eclipse and the ATRIX or as is its referred to on CM site. olympus nightly 3 as my main base. Im thinking of downgrading to 2.3.3 just to try it with the x2 ATRIX port as a base instead, may help compatibility I think. The problem is I dont know just how much of cyanogen the custom kernel affects. Or if its only the cpu controls and various system tweaks. I do iphone development for a living yet ironically switched my own phone to a DROID 2 a couple months ago bc a friend had one lying around and my iphone screen broke. Found how to jailbreak(root) it a couple hours later. Had heard of cyanogen from a friend. Found a nightly found clockwork mod and fell in luv. That phone stopped charging and Verizon gave me an early upgrade to the x2 a couple weeks ago so here I am... Even if I can't make a full port my 2nd goal is a theme engine port. I have all the apks and frameworks from the newest ATRIX cm nightly its just trying to figure out what needs to be replaced or deleted to stop it from conflicting with another running process. For instance I got the theme chooser app to install In eclipse but either something in the frameworks the systemui.apk or framework-res.apk causes it to force close. It may even be the few blur components that are left. I've got a day left to work on this then im gone for a month. And does anybody know off hand if theme engine is in any way controlled by the kernel. Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Sent from my DROID X2 using xda premium
If at first u dont succeed... sbf and flash again lmfao
Sent from my DROID X2 using xda premium
drapp said:
If at first u dont succeed... sbf and flash again lmfao
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Yup yup xDD
---------- Post added at 01:25 AM ---------- Previous post was at 01:20 AM ----------
drapp said:
Yeah, wiped cache and delvik b4 nandroiding to save a little space, and again after just in case. Wiped data then installed. After install, wiped batt stats and fixed permissions while still in tenfars recovery. Then rebooted. After boot loop went into stock recovery and wiped data/cache again. Still no luck. [email protected]#ty thing is I go out of the country on business for a month so not gonna have time. Im working with the 1.2rc3 eclipse and the ATRIX or as is its referred to on CM site. olympus nightly 3 as my main base. Im thinking of downgrading to 2.3.3 just to try it with the x2 ATRIX port as a base instead, may help compatibility I think. The problem is I dont know just how much of cyanogen the custom kernel affects. Or if its only the cpu controls and various system tweaks. I do iphone development for a living yet ironically switched my own phone to a DROID 2 a couple months ago bc a friend had one lying around and my iphone screen broke. Found how to jailbreak(root) it a couple hours later. Had heard of cyanogen from a friend. Found a nightly found clockwork mod and fell in luv. That phone stopped charging and Verizon gave me an early upgrade to the x2 a couple weeks ago so here I am... Even if I can't make a full port my 2nd goal is a theme engine port. I have all the apks and frameworks from the newest ATRIX cm nightly its just trying to figure out what needs to be replaced or deleted to stop it from conflicting with another running process. For instance I got the theme chooser app to install In eclipse but either something in the frameworks the systemui.apk or framework-res.apk causes it to force close. It may even be the few blur components that are left. I've got a day left to work on this then im gone for a month. And does anybody know off hand if theme engine is in any way controlled by the kernel. Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
If you still have time to give it (X2) back i'd recommend it,Get a Bionic or something or the droid 3, something thats more popular, d3 has cm7 booting same with the bionic, don't lock your self in a crap phone if you don't absolutely have to...
drapp said:
Yeah, wiped cache and delvik b4 nandroiding to save a little space, and again after just in case. Wiped data then installed. After install, wiped batt stats and fixed permissions while still in tenfars recovery. Then rebooted. After boot loop went into stock recovery and wiped data/cache again. Still no luck. [email protected]#ty thing is I go out of the country on business for a month so not gonna have time. Im working with the 1.2rc3 eclipse and the ATRIX or as is its referred to on CM site. olympus nightly 3 as my main base. Im thinking of downgrading to 2.3.3 just to try it with the x2 ATRIX port as a base instead, may help compatibility I think. The problem is I dont know just how much of cyanogen the custom kernel affects. Or if its only the cpu controls and various system tweaks. I do iphone development for a living yet ironically switched my own phone to a DROID 2 a couple months ago bc a friend had one lying around and my iphone screen broke. Found how to jailbreak(root) it a couple hours later. Had heard of cyanogen from a friend. Found a nightly found clockwork mod and fell in luv. That phone stopped charging and Verizon gave me an early upgrade to the x2 a couple weeks ago so here I am... Even if I can't make a full port my 2nd goal is a theme engine port. I have all the apks and frameworks from the newest ATRIX cm nightly its just trying to figure out what needs to be replaced or deleted to stop it from conflicting with another running process. For instance I got the theme chooser app to install In eclipse but either something in the frameworks the systemui.apk or framework-res.apk causes it to force close. It may even be the few blur components that are left. I've got a day left to work on this then im gone for a month. And does anybody know off hand if theme engine is in any way controlled by the kernel. Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
2nd init for the x2 was created on GB. I believe our ATRIX ports use 2nd init. Naven and dragon just made them flashable in CWM by including the 2nd init hack in the flash.
drapp said:
Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Click to expand...
Click to collapse
the posted 2nd-INIT in dev section for us works on gb if that is what you are referring to.
About CM7 & 2nd-init
the 2nd init that is used for all motorola devices (except the ATRIX) for cyanogenmod is designed for both froyo and gb. It has a check in there to see if the executable bit exists and figure out what to do from there. that way any motorola device could (in theory) use it. I know that this version of 2nd init works for the X2 and will pretty much be used when it comes to porting over cm7. We're going to have to use GB as our base (not Froyo) simply because of the requirements of our kernel (which we can't change).
About my involvement
now i know that I was original one who was trying to crank out cm7 and that it kinda died out. that doesn't mean that i don't play around with it from time to time. I'm starting from scratch, but if naven and/or cvcps or whomever get it running before I do, more power to them. I have little to no time to work with this, but I know what approach i'm taking this time. It is to simply base it off the ATRIX (obviously) but then work in the 2nd-init and edify scripts that the X uses. I kinda did that the first time, but got too mixed up in all of the details.
I don't want anyone to think that because I'm working on it that any results will arise. I'm merely trying to say that someone is working on it. Just maybe not as fast or with as much time as you guys will like. I want to have CM7, too. But we don't have a team or anything so it takes a lot of work.
@dragonzkiller
Quick question. I understand the 2nd INIT allows scripts to be ran at bootup to alter the kernel in a "temporary" environment(ie. Whatever settings are in place in the Init.d folder is used instead of default.. blah blah), at least that is my understanding of it. But the question here is
What does 2nd Init have to do with CM7? Or MIUI? To my understanding it simply allows scripts to Be ran in front of the Kernel settings. Unless I am wrong, What does this have to do with Heavily Modified roms if you are simply allowing a performance boost, etc?
Peperm1nt said:
@dragonzkiller
Quick question. I understand the 2nd INIT allows scripts to be ran at bootup to alter the kernel in a "temporary" environment(ie. Whatever settings are in place in the Init.d folder is used instead of default.. blah blah), at least that is my understanding of it. But the question here is
What does 2nd Init have to do with CM7? Or MIUI? To my understanding it simply allows scripts to Be ran in front of the Kernel settings. Unless I am wrong, What does this have to do with Heavily Modified roms if you are simply allowing a performance boost, etc?
Click to expand...
Click to collapse
Here's a link to cvpcs blog entry regarding 2nd-init when he was porting CM to Droid X.
http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works
Peperm1nt said:
@dragonzkiller
Quick question. I understand the 2nd INIT allows scripts to be ran at bootup to alter the kernel in a "temporary" environment(ie. Whatever settings are in place in the Init.d folder is used instead of default.. blah blah), at least that is my understanding of it. But the question here is
What does 2nd Init have to do with CM7? Or MIUI? To my understanding it simply allows scripts to Be ran in front of the Kernel settings. Unless I am wrong, What does this have to do with Heavily Modified roms if you are simply allowing a performance boost, etc?
Click to expand...
Click to collapse
2nd-init allows us to have a new init.rc script, not just scripts in general and in reality has no affect on init.d unless the init.rc script is told to do so. Basically 2nd-init kills the init process (and all spawned processes) that uses the stock init.rc and uses a new one which we copy during hijacking the boot process and starts the init process again.
The root directory (where init.rc lies) of our phone is writable, but is reflashed every time the phone boots up, thus erasing any changes we might have made to init.rc (kinda defeats the purpose of having a custom script). This script is the script that gets everything set up during the boot sequence starting roughly around the time the motorola logo first shows up and all through the boot animation. We need to have a custom init.rc to get our phone's environment setup for CM7.
Our problem arises when we have to have the script satisfy both the OS and the kernel. Motorola's kernel expects certain criteria to be fulfilled within the phone to allow it to do it's thing. If these aren't satisfied, the kernel panics and reboots the phone (hence why we get bootloops). We can use logging (a rather tedious, slow, and painful method) of finding out where the kernel panics, and adjust as needed. But we need to have the environment ready for CM7 also, so those changes need to be in there without causing a kernel panic.
"Heavily modified" is a bad way to put it, more like "non-BLUR." If we could get CM7 working we can use the init and build files/setup/etc to allow us to have more ROMs based of AOSP. MIUI is based off of AOSP and in theory if we figure out CM7 we can even have AOSP ourselves. In fact the ATRIX recently got a port of AOSP (albeit buggy, but still).
The link above to cvpcs's blog goes into the details about it. It's really good read.
dragonzkiller said:
The link above to cvpcs's blog goes into the details about it. It's really good read.
Click to expand...
Click to collapse
It is also written in a '2nd init for dummies' fashion. Don't be afraid to read it!
Sent from my DROID X2 using XDA App
I agree this phone is one big piece of poo!
SE7EN- said:
I agree this phone is one big piece of poo!
Click to expand...
Click to collapse
I don't remember seeing anyone in this thread say that. Who are you agreeing with?
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
vipirius said:
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
Click to expand...
Click to collapse
I wanna know too...
bump.
vipirius said:
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
Click to expand...
Click to collapse
HMZX said:
I wanna know too...
bump.
Click to expand...
Click to collapse
I think you can definitely test w/o causing permanent damage. For the smoothest test experience, you'll want to be familar with a custom recovery and the backup/restore modes available along with the type of internal memory unlock used on the device (Revolutionary or HTC official method).
Once you're familar with the basics, it would be fairly simple to test. The combinations for testing, off the top of my head, would be:
1) Sensation kernel and EVO 3D ROM.
2) Sensation kernel and Sensation ROM.
3) EVO 3D kernel and Sensation ROM.
Speaking from experience, once you're familar with how to load kernels and ROMs, the process is fairly generic across devices once write access to the internal memory is obtained.
Again, I'll re-iterate the importance of making a proper backup and being familar with the restoration process.
There are only two main hazards which come to mind:
1) Make sure NOT to flash the radio, bootloader, or any other file. ONLY flash kernel/system partitions.
2) Before flashing kernel/system partitions ensure the partition sizes between devices are the same, or EVO 3D is larger. Not sure the device limits and stops partitions from overwriting each other as I know some older devices did not and this caused an unrecoverable damage.
I'm sure if I missed anything, somebody else will post up. Hope that helps provide some technical background and logic to the approach! Keep us updated!
Thanks for the reply. I'm already familiar with flashing kernels/roms and how to make a nandroid backup etc so that isn't a problem. However I have 1 question, how exactly would I find the partition sizes of the sensation, I couldn't find it on the internet and I don't have a sensation that I can check.
Anyways I found a few posts on the forums of people claiming sensation roms work almost flawlessly except for the camera, so the next question would be if there are any apk's/libs etc. I can copy to the sensation rom to get the camera working. I'm no dev myself so I don't have a clue, but if someone could tell me I would appreciate it. Thanks.
Well you can't just flash a sensation ROM out of the box. You would at least need to change the mount points in the updater script otherwise you will get nothing. Regarding the camera, there are libs in /system/lib like liboemcamera.so and such. Not sure fixing the camera would be as simple as copying libs over from our phone though.
Sent from my PG86100 using Tapatalk
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
EDIT 2: I just saw you were talking about the gsm 3d, I did this on the CDMA. The process would be the exact same though.
Yeah I have a GSM phone so that's why I said GSM. Also wouldn't porting to the GSM version be easier then to the CDMA version since the sensation is also GSM?
Anyways I'm kinda busy today but I will try to see if it boots on my phone tomorrow and post my results. I'll.also try to get the camera to work by copying libs like you suggested.
Sent from my HTC EVO 3D X515m using XDA App
vipirius said:
Thanks for the reply. However I have 1 question, how exactly would I find the partition sizes of the sensation, I couldn't find it on the internet and I don't have a sensation that I can check.
Anyways I found a few posts on the forums of people claiming sensation roms work almost flawlessly except for the camera, so the next question would be if there are any apk's/libs etc. I can copy to the sensation rom to get the camera working. I'm no dev myself so I don't have a clue, but if someone could tell me I would appreciate it. Thanks.
Click to expand...
Click to collapse
Answer to first question: partition sizes are generally mentioned in a handful of different locations depending on the device: /proc/partition(s), /proc/emmc or /proc/mtd off the top of my head. Since the devices are similar and others have already tried this approach, probably not a concern, but none the less never hurts to learn more!
Answer to second question: the cameras (2 of them for 3D) on this device, along with the 3D display are the two biggest difficulties in porting AOSP such as CM to this device, in my opinion. they use closed source proprietary code from HTC. this requires a bit of reverse engineering and kanging from other random sources in order to get a final working product. personally, i wouldnt invest the time/effort into it, but others might find it a beneficial endeavor for themselves. either way, you're guaranteed to learn a bit about cameras! as stated above, all android libraries are loaded in /system/lib.
For the camera, I view android as having essentially three components contributing to a fully functional camera.
1) Camera drivers in the kernel
2) Camera libraries in /system/lib
3) Camera application apk file for Android UI
These three need to work together to at least some degree in order for there to be some functionality in the camera.
Gumby63 said:
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
Click to expand...
Click to collapse
Might be more off topic but could related also to this OP depending on his approach. If you encounter the boot animation this is generally a good sign the kernel has fully loaded and is handing off to the ramdisk/init process.
There are two possible situations at this point
1) If the boot animation loops, i.e. starts over and over, this shows there is an issue with Android/ramdisk init process. Adb has generally been loaded by this point and the issue should be outlined in logcat showing the specific .apk file along with line number which makes for a great starting point in troubleshooting.
2) If the boot animation starts/completes but the device completely reboots back to the splash screen, this is more difficult to troubleshoot. I'm not aware of a great approach to this but I might start by glancing at the /proc/last_kmsg file along with executing adb logcat as soon as I see the boot animation in an attempt to grab the logcat before the device reboots itself.
Good luck and keep us updated!
joeykrim said:
Might be more off topic but could related also to this OP depending on his approach. If you encounter the boot animation this is generally a good sign the kernel has fully loaded and is handing off to the ramdisk/init process.
There are two possible situations at this point
1) If the boot animation loops, i.e. starts over and over, this shows there is an issue with Android/ramdisk init process. Adb has generally been loaded by this point and the issue should be outlined in logcat showing the specific .apk file along with line number which makes for a great starting point in troubleshooting.
2) If the boot animation starts/completes but the device completely reboots back to the splash screen, this is more difficult to troubleshoot. I'm not aware of a great approach to this but I might start by glancing at the /proc/last_kmsg file along with executing adb logcat as soon as I see the boot animation in an attempt to grab the logcat before the device reboots itself.
Good luck and keep us updated!
Click to expand...
Click to collapse
Well yeah it completely reboots back to the splash screen. During the bootanimation, I can't get a logcat and adb says there is no device connected. This isn't my first port but I've never had this happen lol. I'll look into what you said.
Sent from my HTC Flyer P510e using Tapatalk
Well, I successfully installed Android Revoltion HD 3.6.13, It boots, everything seems to work, however I didn't test GPS and BT yet. And the camera is well, half working I guess. The camera app opens, and i can see the controls etc but no image comes, and when I press the capture button the flash pops but the app FC's after that. I'm gonna try flashing [MOD] Camera from HTC Amaze 4G, v0.11 and see if it works. If it doesn't I'll copy over all the camera related libs I can find from my old ROM and see if it works then.
Edit: Hahahaha yessss it works I just flashed the Amaze camera app and now camera works only 2D of course but it's enough for me. I'll keep testing for a few days and of there aren't any serious bugs I can find I'll be using this as my daily driver from now on
Edit2:Audio doesn't seem to work If I can't get that fixed then this ROM will be useless :/
vipirius said:
Edit2:Audio doesn't seem to work If I can't get that fixed then this ROM will be useless :/
Click to expand...
Click to collapse
then move over the proper sound drivers also located in /system/lib, /system/lib/modules and /system/lib/soundfx
t3project said:
then move over the proper sound drivers also located in /system/lib, /system/lib/modules and /system/lib/soundfx
Click to expand...
Click to collapse
Yeah that's what I was going to do, but thanks anyways. I'll report back on my success.
Gumby63 said:
Well you can't just flash a sensation ROM out of the box. You would at least need to change the mount points in the updater script otherwise you will get nothing. Regarding the camera, there are libs in /system/lib like liboemcamera.so and such. Not sure fixing the camera would be as simple as copying libs over from our phone though.
Sent from my PG86100 using Tapatalk
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
EDIT 2: I just saw you were talking about the gsm 3d, I did this on the CDMA. The process would be the exact same though.
Click to expand...
Click to collapse
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
PMGRANDS said:
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
Click to expand...
Click to collapse
im not sure what you read but IT WAS WRONG..........
while you can do some of this stuff from your phone, you can not do a complete port properly without a computer
PMGRANDS said:
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
Click to expand...
Click to collapse
Yeah like t3project said, that is wrong.
But anyhow, I replaced the boot.img simply by opening the two ROMs with winrar and then deleting and replacing it. And to extract the kernel, you would need to split the boot.img either using a kitchen or some other tools that do the job.
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Gumby63 said:
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Click to expand...
Click to collapse
Aren't you on the CDMA EVO? If you are wouldn't the radios be completely different since the sensation is a GSM device? So maybe that's what's causing the reboot issues. I mean as far as I know even porting from the CDMA EVO to the GSM EVO is hard so wouldn't porting from the sensation to the CDMA EVO be even harder?
vipirius said:
Aren't you on the CDMA EVO? If you are wouldn't the radios be completely different since the sensation is a GSM device? So maybe that's what's causing the reboot issues. I mean as far as I know even porting from the CDMA EVO to the GSM EVO is hard so wouldn't porting from the sensation to the CDMA EVO be even harder?
Click to expand...
Click to collapse
this is only patrialy the problem. flashing roms doesnt affect the radio so that wouldnt change but i there are some other libs that need to be moved that are associated with communication to the radio. cant remember which off the top of my head
Gumby63 said:
Yeah like t3project said, that is wrong.
But anyhow, I replaced the boot.img simply by opening the two ROMs with winrar and then deleting and replacing it. And to extract the kernel, you would need to split the boot.img either using a kitchen or some other tools that do the job.
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Click to expand...
Click to collapse
Yeah I thought the article I read was Bull****! I wish I could remember where I read it to show you guys what it said but just can't remember for ****... Lol!
Well Thanks for Confirming guys...
I would really like to dual boot between joelz's rezound bamf .8 rom and bamfx rom.
Is it possible to run this app even though the rezound is unsupported? If so I'm not sure what to enter for the manual variables. I also am not sure if s-on will prevent the functionality of this app.
cincyelite22 said:
I would really like to dual boot between joelz's rezound bamf .8 rom and bamfx rom.
Is it possible to run this app even though the rezound is unsupported? If so I'm not sure what to enter for the manual variables. I also am not sure if s-on will prevent the functionality of this app.
Click to expand...
Click to collapse
lol, I feel like I've read this message about 3 times now. Contact the dev for app boot manager.
Idk where you might have possibly came to that idea. But im just wondering if it will work if the variable are entered correctly. If not what apps will work to dual boot roms.
cincyelite22 said:
Idk where you might have possibly came to that idea. But im just wondering if it will work if the variable are entered correctly. If not what apps will work to dual boot roms.
Click to expand...
Click to collapse
Can't dual boot with that app since you have to switch kernels in hboot. Might be able to dualboot two gb roms or two ics roms though
Sent from my ADR6425LVW using XDA
I checked Boot Manager's forum and it looks like one of their dev's has a Rezound and is working on getting it to work.
Hey, just wanted you all to know that I am good friends with Gflam and Conap both of the devs at Init2winitapps. I am also a moderator in the forums over there. I have been talking to Gflam alot lately about a bunch of stuff and I can verify that at this moment Conap is working on officially suppporting the rezound. It may take a little while but I have complete faith in both of them to get this up and running. I also believe that they are working on getting the Droid Razr working but dont qoute me on that.
---------- Post added at 01:24 PM ---------- Previous post was at 01:13 PM ----------
They also have a new file explorer out called slide explorer with awesome features unlike any other file explorer... check it out!
We released boot manager with rezound support yesterday it's pretty straight forward to use it's the same as all the other devices you just have to drop the boot.img or ph98IMG in the rom zip that the developer of the rom usually supplies and then just run the install as you would any other device (see our how to video for more instructions)
http://www.youtube.com/watch?v=bU0VJ1jmbx8
When they release the s-off tool for rezound will you guys change the app accordingly?
Sent from my INCREDIBLE, faster than a THUNDERBOLT, REZOUND!
it's conaps phone so i know he'll be keeping it up to date so yea you guys will be kept in the loop for sure
By the way apophis9283 what happened to you in gtalk you're not in my friends list any more tried to tell you about it as soon as we released but you weren't there did i delete you by accident or did you go invisible or something?
Lol, gflam. I thought you deleted me.... I woke up one day and you werent there. Kinda like a one night stand....
Sent from my INCREDIBLE, faster than a THUNDERBOLT, REZOUND!
hmm well that's odd ha anyway i'll pm you my gtalk again send me a request
glad yall have it working been waiting for this app to work on the rezound!
Great work guys
I cant wait till we get s-off, then it will be just like it was on my og inc
Sent from my INCREDIBLE, faster than a THUNDERBOLT, REZOUND!
I know someone mentioned this in the Bamf Evita thread. But I also experienced freezing on my rom using boot manager. Now I dont want to call this out as a bug because I was in a rush to setup my second rom and I accidently hit ext2, dont know if that could have caused it, and I forgot to drop a boot img in the rom also, so it ended up failing to install the second rom. However, i didnt get a chance to do it correctly and noticed freezing and lock ups.
So, now that we have S-OFF, what's the progress on getting Boot Manager to fully work on S-OFF? Anxiously awaiting a fully-functional Boot Manager so that I can go ROM-crazy! Lol!
Seriously, I'm patient. Just curious as to an estimate of when we might see Boot Manager using S-OFF on the Rezound.
Thanks for all your hard work guys!
i hope they are working on it now and will release an update soon
so give it time.
sent from my S-OFF, INCREDIBLE, faster than a THUNDERBOLT, REZOUND!
Works fine for me...
Works fine for me as well. Ive booted between innef gb and newts onexxx ics just fine.
Sent from my ADR6425LVW using xda premium
so yall are saying it works fine on s-off ? im asking bc i havent tried installing any new roms with it yet