Develop Bugs

Clockwork Recovery port?

So, I was reading up a bit on the guide to porting Clockwork Recovery, and decided to build it yesterday. Everything was fairly easy to do, but I forget this is Motorola we're talking about, and realized the hard way that our phone has a locked bootloader and won't work with a custom recovery.
I saw there's a workaround used on the Droid X, Droid 2, and Defy that isn't really a true recovery, but close enough for our purposes. Unfortunately, I'm far from an actual dev, and there's no handy guide for me to follow to port something like that over to our device, so I thought I'd throw this post out there to see if anyone else was capable of it, or at least able to point me in the right direction.
For reference, here's the thread about the Defy recovery. I'll likely pull the sources down and muck about a bit with it, but if anyone has any tips on how to do this, or better yet wants to do it themselves, please do. If you don't have a flipside, I can gladly provide any info or files from the phone, and I've already had to restore from .sbf a handful of times so it's not like I'm afraid of testing it.

http://forum.xda-developers.com/showpost.php?p=12244509&postcount=159
Try this

just picked up a flipside for my niece. As there doesnt appear to be alot of info or options available for it. Where shall we begin? I might donate my xperia x10 to her so that i might be able to assist in seeing what can come of the flipside. pm and lets see what we can get cracking.
As i love my xperia. all info that you can give me will be appreciated and i will work on it when i have the flipside with me for testing.

polovinamozga said:
http://forum.xda-developers.com/showpost.php?p=12244509&postcount=159
Try this
Click to expand...
Click to collapse
Worked like a charm. lol. cwm on flipside thanks to your posting this link. thanks

and then what?

polovinamozga said:
http://forum.xda-developers.com/showpost.php?p=12244509&postcount=159
Try this
Click to expand...
Click to collapse
does this work on a flip side running 2.2?
Sent from my MB508 using Tapatalk

iXNyNe said:
does this work on a flip side running 2.2?
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
No.
Sent from my MB860 using XDA App

bakageta said:
So, I was reading up a bit on the guide to porting Clockwork Recovery, and decided to build it yesterday. Everything was fairly easy to do, but I forget this is Motorola we're talking about, and realized the hard way that our phone has a locked bootloader and won't work with a custom recovery.
I saw there's a workaround used on the Droid X, Droid 2, and Defy that isn't really a true recovery, but close enough for our purposes. Unfortunately, I'm far from an actual dev, and there's no handy guide for me to follow to port something like that over to our device, so I thought I'd throw this post out there to see if anyone else was capable of it, or at least able to point me in the right direction.
For reference, here's the thread about the Defy recovery. I'll likely pull the sources down and muck about a bit with it, but if anyone has any tips on how to do this, or better yet wants to do it themselves, please do. If you don't have a flipside, I can gladly provide any info or files from the phone, and I've already had to restore from .sbf a handful of times so it's not like I'm afraid of testing it.
Click to expand...
Click to collapse
Nice
But I wish could be more out of the track
But to be honest, here we r only couple of people noising about blurs and blurt softwares...
anyhow, sooner or later there will be useful help for what people looking for their 508
Can u tell me whose hardware is more reliable, Motorola or Sony ericson
and to what extent if you compare the 508 processor with phone 3g in speed...
I recently got my modified battery with an over all estimated 1450 mah, though its thin NW ND Hard for me to shut its drawback but battery is now superb and unbelievable
4.40 hours of continuous skype video calls
Ps add comments
Sent from my MB508 using xda premium

Incredible-S roms on Dinc2?

Now that we have S-off (thanks alpharev donations def on the way) and we are working at getting a recovery wouldnt it be possible to port incredible-s roms, since they are almost the exact same phone? Different radios and a few other things? Im not a dev, just wondering if anyone is considering that. Since there are a ton of roms out already for the Inc-S.

Incredible S has official support of CM (no release yet that I'm aware of, haven't checked in a couple days). I don't see why this can't be extended to the I2.

nimdae said:
Incredible S has official support of CM (no release yet that I'm aware of, haven't checked in a couple days). I don't see why this can't be extended to the I2.
Click to expand...
Click to collapse
I miss CM7. I had a G2 that I rooted (painstaking root process by hand and terminal emulator) and that was such a great stable rom. I tried a few others MIUI, Mexidroid... ect. All in all CM7 was the best. I would be so happy if they support it. Although I do have to say, im really starting to get used to Sense. Its a really nice interface. If I had to have one, ide take this of stupid motoblur or touchwiz anyday.

I stopped using Sense in lieu of LauncherPro some time ago as that was the environment I was use to while using CM7. Can't wait to get back to CM7 so the bloat is gone and I get the unleash the full potential of my I2.

I would love to see MIUI, I had it on my original INC and I love it. Weekly updates and it seems like they just keep improving it. Very fast and stable. Long way from where it started.

I recently sold my inc and now I'm stuck with a palm pre plus. I was going to hold out for the droid 3 or bionic but if the inc 2 gets cm support I will have a hard time not buying one.

nfcrockett said:
I recently sold my inc and now I'm stuck with a palm pre plus. I was going to hold out for the droid 3 or bionic but if the inc 2 gets cm support I will have a hard time not buying one.
Click to expand...
Click to collapse
We already have a couple CM devs expressing interest.

nfcrockett said:
I recently sold my inc and now I'm stuck with a palm pre plus. I was going to hold out for the droid 3 or bionic but if the inc 2 gets cm support I will have a hard time not buying one.
Click to expand...
Click to collapse
wtf a Palm Pre Plus?!?!?! id rather have a blackberry lol.
na all jokes aside..come back to the Incredible side of the device world, you will not be let down.

haha I'm glad someone feels me, I lucked out and have been using my buddy's inc but he ended up selling it so as I type I'm activating the pre *sad face*

xgunther said:
We already have a couple CM devs expressing interest.
Click to expand...
Click to collapse
That makes me happy in my pants.

To answer the OP's question. Yes. Incredible S --> Incredible 2 ports will be disgustingly easy.
As a matter of fact, we should be able to make a universal 'patcher' that you can flash after any incredible S rom to make it 100% dinc2 compatible. No porting necessary.
1- Flash Incredible S rom
2- Flash patcher script
3- Done city

deficitism said:
To answer the OP's question. Yes. Incredible S --> Incredible 2 ports will be disgustingly easy.
As a matter of fact, we should be able to make a universal 'patcher' that you can flash after any incredible S rom to make it 100% dinc2 compatible. No porting necessary.
1- Flash Incredible S rom
2- Flash patcher script
3- Done city
Click to expand...
Click to collapse
Well that would be Incredible (no pun intented)

It's possible it could be that simple. However, I suspect we will need a different kernel and different driver set. I believe our radio hardware is slightly different (I could be wrong on this), as well as filesystem layout.
Of course, we can't know this for sure until the work actually starts. I suspect it'll be easy to port over, but not THAT easy, unfortunately. Considering AlphaRev is using only a slightly modified hboot from the IS for the I2, it very well could be that easy

nimdae said:
It's possible it could be that simple. However, I suspect we will need a different kernel and different driver set. I believe our radio hardware is slightly different (I could be wrong on this), as well as filesystem layout.
Of course, we can't know this for sure until the work actually starts. I suspect it'll be easy to port over, but not THAT easy, unfortunately. Considering AlphaRev is using only a slightly modified hboot from the IS for the I2, it very well could be that easy
Click to expand...
Click to collapse
i would imagine your right. the radios are gonna be different on account of the incS being GSM and the inc2 being CDMA. hopefully it is easy though, and hopefully it comes soon.

deficitism said:
To answer the OP's question. Yes. Incredible S --> Incredible 2 ports will be disgustingly easy.
As a matter of fact, we should be able to make a universal 'patcher' that you can flash after any incredible S rom to make it 100% dinc2 compatible. No porting necessary.
1- Flash Incredible S rom
2- Flash patcher script
3- Done city
Click to expand...
Click to collapse
I disagree on how easy that will be, you will need a different RIL (and associated files, including phone.apk and settings.apk most likely) along with a different kernel.

jcase said:
I disagree on how easy that will be, you will need a different RIL (and associated files, including phone.apk and settings.apk most likely) along with a different kernel.
Click to expand...
Click to collapse
Everything you mentioned can be done with just a few lines in a patcher. I've done it before. It's not rocket science. And when its done, it can be universally applied to all roms between the two devices. Even a tiny bit of logic to determine source vs sense. (otherwise resulting in two patchers)

deficitism said:
Everything you mentioned can be done with just a few lines in a patcher. I've done it before. It's not rocket science. And when its done, it can be universally applied to all roms between the two devices. Even a tiny bit of logic to determine source vs sense. (otherwise resulting in two patchers)
Click to expand...
Click to collapse
I would be very interested in seeing this done in a few lines. I am fully aware of the possibility of doing it, I just don't see it happening easily and in a few lines.
I'm not arguing or bashing, I would just like to see it. Please link me to your previous incarnation of such a patcher

jcase said:
I would be very interested in seeing this done in a few lines. I am fully aware of the possibility of doing it, I just don't see it happening easily and in a few lines.
I'm not arguing or bashing, I would just like to see it. Please link me to your previous incarnation of such a patcher
Click to expand...
Click to collapse
You are getting bashy. And you are clearly trying to belittle my statements by requesting direct links to my work, in order to disprove something you know damn well is possible. We have been doing between the desire/evo/inc/n1/etc for a long time now. Even kiddie kitchens have a button to 'port' a rom.
Regardless of how many 'lines' a script would be, flashing would be dead simple by the end user. And yes, creating it should be very easy on my end.

My d**k is bigger than yours!
Sent from my ADR6350 using XDA App

deficitism said:
You are getting bashy. And you are clearly trying to belittle my statements by requesting direct links to my work, in order to disprove something you know damn well is possible. We have been doing between the desire/evo/inc/n1/etc for a long time now. Even kiddie kitchens have a button to 'port' a rom.
Regardless of how many 'lines' a script would be, flashing would be dead simple by the end user. And yes, creating it should be very easy on my end.
Click to expand...
Click to collapse
Lol ok dude whatever, I made it clear I simply wanted to see it. I'm not a ./autohack dev, so I am unfamiliar with what those kinds of devs are doing, hence me asking to see. Nothing more or less than simple curiosity.
You getting all defensive/pissed over such a simple request, is pretty darn funny. Will have to screen shot this one.

Fully bricked T989 after trying to install villainrom

Hi all,
I'm hoping I'm posting this in the right place and with the right format.
I have a rooted T-Mobile Samsung Galaxy S2 device, and after trying to install Villainrom 3.0.0 (VillainROM-3.0.0-signed.zip) through the Clockworkmod recovery console, it is completely bricked. Installation said it finished successfully, I then chose 'Reboot' through the CWR console, and the device went dead.
It won't turn on, or boot into recovery or download modes. I removed the battery and SIM for 10 minutes, and same results. When connecting the device to the computer, I hear the "Device failed to connect" sound. If I try to press the power button, I hear the "device connected" sound followed immediately by the "device failed to connect" sound. The fact that it is responding at all to the USB cable being connected, is the only hope I have left that I can do something about it. Odin does not show it connected though (I saw in another thread that someone was able to use it despite the device not turning on).
I would appreciate any advice before I try ordering a USB jig and / or visiting a support center and hoping they somehow replace it within warranty by making another story.

Next time you should really be careful when installing ROMs................. Make sure they are supported by your phone............... That's all the advice I can give.
Your only options now is to try a USB jig or sending it to a support center so...

Yup, you need to make sure the ROM you want is supported.. other than our dev section, everything else you will find is for the i9100.
Completely different phone.

I think your only options are jig or warranty
Sent from my SGH-T989 using XDA App

Yeah - this happens when you flash a ROM for a totally different device.
You could try flashing a T989 kernel and see if that helps - but the International SGS2 has a Exynos processor - yours is a Snapdragon - along with some other differences.
You can also try using ODIN to flash a stock tar and ROM back - it's not really bricked - but you'll need to do some reading to hopefully avoid such disastrous results again

I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
How could I use ODIN when the device doesn't respond to any kind of button combo and doesn't go into download or recovery modes? is there a way to force ODIN to recognize a bricked device?

erangalp said:
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
Click to expand...
Click to collapse
The answer to your question is common knowledge and in fact has already been answered in this thread even. Le sigh.
Sent from my SGH-T989 using XDA App

TJBunch1228 said:
The answer to your question is common knowledge and in fact has already been answered in this thread even. Le sigh.
Click to expand...
Click to collapse
I appreciate everyone trying to help, but this is not very helpful. Obviously it wasn't common knowledge for me, otherwise this wouldn't have happened - and I did read up a lot about this. And where in this thread does it answer about the difference in hardware?
Please bear in mind that I'm not an android developer, so what seem like common knowledge to you about internal difference in devices is not that obvious.

How many times in these forums does it say don't flash if you don't know what you are doing. If you don't know what you are doing ask questions. Maybe bricking your phone will teach you a lesson.

are you able to go into Download mode with a USB Jig?
(you can always make your own if you can add up enough spare resistor to amount 301k)
if you can then you can try flashing the stock Odin ROMs
erangalp said:
Hi all,
I'm hoping I'm posting this in the right place and with the right format.
I have a rooted T-Mobile Samsung Galaxy S2 device, and after trying to install Villainrom 3.0.0 (VillainROM-3.0.0-signed.zip) through the Clockworkmod recovery console, it is completely bricked. Installation said it finished successfully, I then chose 'Reboot' through the CWR console, and the device went dead.
It won't turn on, or boot into recovery or download modes. I removed the battery and SIM for 10 minutes, and same results. When connecting the device to the computer, I hear the "Device failed to connect" sound. If I try to press the power button, I hear the "device connected" sound followed immediately by the "device failed to connect" sound. The fact that it is responding at all to the USB cable being connected, is the only hope I have left that I can do something about it. Odin does not show it connected though (I saw in another thread that someone was able to use it despite the device not turning on).
I would appreciate any advice before I try ordering a USB jig and / or visiting a support center and hoping they somehow replace it within warranty by making another story.
Click to expand...
Click to collapse

erangalp said:
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
How could I use ODIN when the device doesn't respond to any kind of button combo and doesn't go into download or recovery modes? is there a way to force ODIN to recognize a bricked device?
Click to expand...
Click to collapse
Hmm - well let's see... a simple Google search to compare the phones would tell you that it's definitely not the same device. A little more reading might be in order though...
1. different screen sizes
2. different SoC (system-on-chip, i.e. processor)
3. different basebands/radios
4. etc.
All of those combine to a different device.
Now as relating to ODIN - I honestly don't see why you couldn't get into ODIN. A jig might help but I doubt it.

erangalp said:
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
How could I use ODIN when the device doesn't respond to any kind of button combo and doesn't go into download or recovery modes? is there a way to force ODIN to recognize a bricked device?
Click to expand...
Click to collapse
With very little research....
Galaxy S2 (International) - i9100
Dual-core 1.2GHz ARM Cortex-A9 processor, Mali-400MP GPU, Exynos chipset
T-Mobile/Telus Galaxy S2 - T989/D
1.5 GHz Scorpion dual-core processor, Adreno 220 GPU, Qualcomm APQ8060 Snapdragon chipset
This difference in specification should be the FIRST thing keeping you away from flashing a i9100 ROM on a T989...

erangalp said:
I appreciate everyone trying to help, but this is not very helpful. Obviously it wasn't common knowledge for me, otherwise this wouldn't have happened - and I did read up a lot about this. And where in this thread does it answer about the difference in hardware?
Please bear in mind that I'm not an android developer, so what seem like common knowledge to you about internal difference in devices is not that obvious.
Click to expand...
Click to collapse
Well - how about this answer given above which does in fact provide the answer for you:
jerdog said:
You could try flashing a T989 kernel and see if that helps - but the International SGS2 has a Exynos processor - yours is a Snapdragon - along with some other differences.
Click to expand...
Click to collapse

How can you know what you don't know? I have previously rooted my galaxy S2 and installed various ROMs without a problem. I now have this new T-mobile device since I switched carriers. I could I know that what worked for my previous Galaxy S2 won't work for this one? why should I "be taught a lesson"?
I would really appreciate if someone could give me a helpful answer - I can't use ODIN to flash since I can't boot up the device in any mode. Is there any way to make ODIN recognize a bricked device? the computer does make the USB connected sound for a sec there. Please guys, anything helpful instead of telling me how "should've known", because really, if I could I would. Nobody here ever had a faulty ROM installation?

erangalp said:
I appreciate everyone trying to help, but this is not very helpful. Obviously it wasn't common knowledge for me, otherwise this wouldn't have happened - and I did read up a lot about this. And where in this thread does it answer about the difference in hardware?
Please bear in mind that I'm not an android developer, so what seem like common knowledge to you about internal difference in devices is not that obvious.
Click to expand...
Click to collapse
Jerdog covered the differences in hardware for you. In fact it was exactly above your post explaining that you were unaware of the differences in hardware. 95% of us here are not devs... All you gotta do is read. There are dozens of threads already from folks who have already made your mistake. Read read read. And if you think you've read enough, read more. The difference in processor is one of the most commonly known and discussed things about this phone. Good luck with your phone.
Edit: regarding an actual solution, just try to do a warranty exchange. Play dumb.
Sent from my SGH-T989 using XDA App

This thread happens 30 times a day, very annoying. People will never learn
Sent from my SGH-T989 using xda premium

TJBunch1228 said:
Edit: regarding an actual solution, just try to do a warranty exchange. Play dumb.
Click to expand...
Click to collapse
Thanks, will do that.
Sorry guys, it was an honest mistake. I didn't bother googling it, because I assumed it was the same hardware. Obviously, a sorry mistake, but we're all human. Thanks again to all who tried to help, sorry if annoyed anyone with my problem (and I did search the forum before posting, none of the other threads offered any solutions to my case).
Cheers

If you just assumes it was the same, that basically means you are.clueless and don't even know anything about the phone, in other words, you should not be flashing if you don't know what you are doing
Sent from my SGH-T989 using xda premium

Yup, it's unfortunate - people try to flash VR onto their device, then find it's not compatible...
If there's something I can do to the zip to prevent it flashing on these devices, I will gladly do it, but since they bear the SGS2 name, the standard check for "galaxys2" likely won't help us...
If you try the jig, it SHOULD in theory work, if the hardware is fine. But I have no experience of this, it's a case of stabbing blind in the dark

erangalp said:
Thanks, will do that.
Sorry guys, it was an honest mistake. I didn't bother googling it, because I assumed it was the same hardware. Obviously, a sorry mistake, but we're all human. Thanks again to all who tried to help, sorry if annoyed anyone with my problem (and I did search the forum before posting, none of the other threads offered any solutions to my case).
Cheers
Click to expand...
Click to collapse
Hey - we all make mistakes - and you own up to it - that's a good thing.
I wouldn't personally recommend taking it back for a warranty exchange and playing dumb. If you can go without your device for a few days go on eBay and get a jig. Try that and then flash with ODIN back to stock. It's better than driving up the overall costs for others (trickle-down) for something you did yourself.
My $0.02.

[Q] [DEV] Bootloader Progress

Is there anyone who has made any headway in their research on cracking or unlocking the bootloader? My short research confirms that it is using a 256-bit encryption algorithm, but I've not identified the algorithm used, nor do I think it would matter, as I really have no intention of doing a cryptanalysis on something that strong and I doubt anyone else would, either. Out of curiousity, though: anyone know offhand?
I'm curious to know what methods you guys are attempting to employ and what, if any, other research has already been done. I'd like to help, where I can.

**** if i knew more about it id take a crack at it but unfortunately i lack the skills required. Guess its time to learn huh.

grayn0de said:
Is there anyone who has made any headway in their research on cracking or unlocking the bootloader? My short research confirms that it is using a 256-bit encryption algorithm, but I've not identified the algorithm used, nor do I think it would matter, as I really have no intention of doing a cryptanalysis on something that strong and I doubt anyone else would, either. Out of curiousity, though: anyone know offhand?
I'm curious to know what methods you guys are attempting to employ and what, if any, other research has already been done. I'd like to help, where I can.
Click to expand...
Click to collapse
Vache and I worked on it yesterday for about 6 hours. We didn't get it cracked yet but we are making progress. Don't bother with trying to get your SBK (secure boot key) because A: you won't be able to crack the encryption & B: we have a "secret" way to extract it from the tablet (shhhhh!) (and no, we won't share it just yet, sorry )

timbrendelaz said:
Vache and I worked on it yesterday for about 6 hours. We didn't get it cracked yet but we are making progress. Don't bother with trying to get your SBK (secure boot key) because A: you won't be able to crack the encryption & B: we have a "secret" way to extract it from the tablet (shhhhh!) (and no, we won't share it just yet, sorry )
Click to expand...
Click to collapse
Ahh. Yes, it looks like I noticed vache's call for test in the ROOTED thread a bit late, sent him a PM a couple hours ago.
If you guys need another "Linux guy" or a fresh set of eyes, feel free to PM me. I'll keep poking about the system on my own, in the mean time, as well. Good luck on the research!

This is great news!

This is awesome. Keep up the good work.
Sent from my PG86100 using Tapatalk

timbrendelaz said:
Vache and I worked on it yesterday for about 6 hours. We didn't get it cracked yet but we are making progress. Don't bother with trying to get your SBK (secure boot key) because A: you won't be able to crack the encryption & B: we have a "secret" way to extract it from the tablet (shhhhh!) (and no, we won't share it just yet, sorry )
Click to expand...
Click to collapse
reallllyy appreciate the times you guys are putting into this.

I'm curious how the bootloader is different from the acer iconia a500? If it is not, couldn't we use the same technique from there?

will this thing never gonna get unlocked?
i think i should just sell that piece of ****

TheUndertaker21 said:
will this thing never gonna get unlocked?
i think i should just sell that piece of ....
Click to expand...
Click to collapse
Go for it, the Developers of the XDA community don't owe you anything and if this is how you are going to help (by complaining) then you are better off selling this wonderful device. Patience is a key thing with this device, just like the atrix its just a matter of time.

Lightsword1942 said:
I'm curious how the bootloader is different from the acer iconia a500? If it is not, couldn't we use the same technique from there?
Click to expand...
Click to collapse
Yes, different bootloader, due to both having different versions of hc. The A100 is newer, has newer programming, and leaves us with a different place to start. I myself have tried putting every single script of my A100 into an emulator on my PC to attempt to "reverse engineer" the bootloader to try to decrypt it, but that was unsuccessful for many reasons.
ummmmm............ could you repeat that?

Rather new to androids but I would consider myself a Linux guru. I just picked up an A100 on an open box sale and I would like to get involved in cracking the bootloader on this device. I am a professional low level developer and I have contributed to the development of several major open source projects including Gentoo and Fedora.
I also own a new Samsung Nexus S. Whose working on this now? Is there anything you need help with?

vamman said:
I also own a new Samsung Nexus S. Whose working on this now? Is there anything you need help with?
Click to expand...
Click to collapse
Our biggest challenge with this device is the 256bit encrypted bootloader from hell.. if you know a cryptologist, or some one at acer, that would help a ton
Sent from my MB860 using XDA App
Sent from my MB860 using XDA App

I tried not cracking the bootloader but loading a second init. This proved beyond my skills. I am more a infrastructure and SQL guy then developer.
I would love to have this thing cracked open but I must say with a few tweeks this is a fast stable tablet. I do not know what I would want changed other then the native bluetooth PAN menu.

I just received my a100 from best buy, order placed on black friday.
I would love to see the bootloader cracked.
Keep up the good work guys.
Sent from my MB855 using Tapatalk

I for one would love to see some development on the a100! If there is anything I can do to help just let me know. Im not a dev but I have been tinkering since ms-dos in 1982, and I am very eager to see some development on this tablet, especially usb host mode. good luck!!

painter_ said:
I tried not cracking the bootloader but loading a second init. This proved beyond my skills. I am more a infrastructure and SQL guy then developer.
I would love to have this thing cracked open but I must say with a few tweeks this is a fast stable tablet. I do not know what I would want changed other then the native bluetooth PAN menu.
Click to expand...
Click to collapse
That's the route Im going as well, so far I've compiled 2nd-init and it runs, but it crashes right after initalizing the memory and reboots the tablet (I dont think I have the correct memory address of init for the hook to work properly so it reboots the device). I've also tried log's kexec hack and I dont think it works. Asks for a kernel to load, which I dont have but, I dont think our current kernel supports kexec, so a module would have to be compiled for it. Im no kernel developer (I understand how they work, and how to mod an existing one, but building onne from scratch not so much). With kexec, it requires a special kernel the starts up where your current kernel resides in memory, so it would be harder to get working than 2nd-init.

cracking the encryption
I am not sure what type of file this is but I am fairly experienced with cracking and have access to a small render farm with plenty of gpu power and john the ripper installed. I could give it a go at cracking the password. let me know if I can help.

burn.phreak said:
I am not sure what type of file this is but I am fairly experienced with cracking and have access to a small render farm with plenty of gpu power and john the ripper installed. I could give it a go at cracking the password. let me know if I can help.
Click to expand...
Click to collapse
You can't really brute force this kind of thing, we need to use some sort of exploit, would take millions of years or something like that.

Lightsword1942 said:
You can't really brute force this kind of thing, we need to use some sort of exploit, would take millions of years or something like that.
Click to expand...
Click to collapse
I have brute forced a lot before its worth a shot, I wouldn't say its our best shot but it's worth a look and gives me something to occupy my time.

[Q] How to fix front camera

Hello I have a Htc evo 4g+ and we build cyanogenmod10 4.1.1.
However, there is one probelm. This rom doesn't work front camera!!!
So I change the lib file.... libOlaengine,libcameraclient,libcameraface....
I had to modify the files associated with the camera lib file
but isn't work...
help me!:crying:

Well for one, you state that you have the Evo+ which is almost an entirely different phone, and just swapping libs around won't fix your camera. You need the drivers for it. I'm not sure if they've been released for that phone or not.

ah ha
death-by-soap said:
Well for one, you state that you have the Evo+ which is almost an entirely different phone, and just swapping libs around won't fix your camera. You need the drivers for it. I'm not sure if they've been released for that phone or not.
Click to expand...
Click to collapse
oh then this device similar at evo 3d?

Majordeveloper said:
oh then this device similar at evo 3d?
Click to expand...
Click to collapse
I'm assuming so. Its specs were a step above the OG from what I remember. Much like the 3D.
Sent from my SPH-L710 using xda premium

has anyone found out the issue? i'm trying to fix my cameras on my evo 3d in evervolv custom rom, also it seems that audio is out too.. :sadface: