Related
Does anyone know if this will also work on the DInc?
http://forum.xda-developers.com/showthread.php?p=6800690
supagene said:
Does anyone know if this will also work on the DInc?
http://forum.xda-developers.com/showthread.php?p=6800690
Click to expand...
Click to collapse
not a chance unless/until we get an engineering build for the incredible (they tend to be hard to come by sometimes)
NAND has already been unlocked through a patched hboot on the Incredible, we're just waiting for a possible release.
Is this what you are referring to?
"Team unrEVOked is proud to announce that we and @AndroidBruce have the first HTC Incredible with a patched bootloader." - 6:00 PM Jul 16th via web
http://twitter.com/unrevoked
supagene said:
Is this what you are referring to?
"Team unrEVOked is proud to announce that we and @AndroidBruce have the first HTC Incredible with a patched bootloader." - 6:00 PM Jul 16th via web
http://twitter.com/unrevoked
Click to expand...
Click to collapse
Yup. Of course, that doesn't mean they're going to release soon, or maybe not at all, since there's a very real risk of bricking when you're ****ing with hboot.
Noob question here. I tried to search for the answer but couldn't find one.
Why would I want to do this when it seems to me that all of the options are available when I root the phone with Unrevoked3? Is there something more we gain with this full nand unlock?
Some applications try to write to /system for example AdFree so they can modify the hosts file. Currently none of the applications can actually write on the DInc because we only have write permissions when in recovery mode only. Once NAND is fully unlocked, we'll have all the applications running as expected.
supagene said:
Some applications try to write to /system for example AdFree so they can modify the hosts file. Currently none of the applications can actually write on the DInc because we only have write permissions when in recovery mode only. Once NAND is fully unlocked, we'll have all the applications running as expected.
Click to expand...
Click to collapse
I'd love to be able to use metamorph so I don't have to update themes so much... pushing apks with the phone booted really helps me to develop themes as well. Nand unlocked is something I miss about my old android phones....
heavensblade23 said:
Yup. Of course, that doesn't mean they're going to release soon, or maybe not at all, since there's a very real risk of bricking when you're ****ing with hboot.
Click to expand...
Click to collapse
Why would they announce and never release? If the were able to make an easy root app, I hope they can release something for the nand unlock. I wonder how long it will take them to release...
Sent from my ADR6300 using XDA App
supagene said:
Why would they announce and never release? If the were able to make an easy root app, I hope they can release something for the nand unlock. I wonder how long it will take them to release...
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
They say they don't want to release the vulnerability they exploit for the NAND flash unlock because they don't want to to go away (get "fixed" by htc).
You can read about it at their wiki if you go to their site, select the Incredible, and select "More Info?"
ok too much misinformation seems to be getting linked together. so just this once ill comment.
we do have a few completely nand unlocked devices now. we have some more experimentation to go with hboot before it will be worthy of release, ie the fastboot commands. patching it is a slower process as you are correct, its easy to brick. we will be planning a release but do not presently have a timeframe. one problem is while with recovery a error would be corrected by trying again, hboot will brick. so if we do release its going to be a slightly technical process requiring more thought and knowledge so that you have the best chance of success.
aotothemax said:
They say they don't want to release the vulnerability they exploit for the NAND flash unlock because they don't want to to go away (get "fixed" by htc).
You can read about it at their wiki if you go to their site, select the Incredible, and select "More Info?"
Click to expand...
Click to collapse
The vulnerability has already been shown... i have a copy of the zip saved on my PC and can unlock my nand at will.. You go into hboot and type in some commands and then reboot and upon reboot into android your NAND is unlocked and you can do anything you want including write to /system while in actual android... then upon rebooting your phone a second time your nand relocks by default...
The reason i know this works is that i did the nand unlock and AdFree was able to successfully install a new hosts file on my phone with no problems.. and that program needs specific /system write access while in android itself... also i can remove files in my /system folder while in android using root explorer on the phone itself, without have to do adb at all
what unrevoked is trying to do now is make it permanent where it stays unlocked after a reboot.. but for now its pretty simple, all i have to do is not turn off my phone and my nand will stay unlocked
Shadowmite and Joe92T, thanks for clearing things up for everyone. I hope nobody goes looking for that zip and bricks their device before unrEVOked's release.
mahkee said:
Shadowmite and Joe92T, thanks for clearing things up for everyone. I hope nobody goes looking for that zip and bricks their device before unrEVOked's release.
Click to expand...
Click to collapse
The whole thread it was located in has been deleted because it was a leaked file and not an official release,the only people that have it are unrevoked and the people lucky enough to download the attachment before the mods found out
I'm glad it's being worked on. Once it works running true linux on the phone will be possible as would dual booting the phone.
Oh, I didn't know that. Thanks for clearing that up!
Sent from my ADR6300 using XDA App
sorry. Edited for your protection
The Dinc is my first android phone (from blackberries), but from what I can tell, HTC seems to not be as anal about exploits found as some other Android phone makers. I like that.
Does a full NAND unlock allow deleting system apps that were previously not able to be uninstalled with the device on ?
Yes that's what it means,
Sent from my HTC Incredible using Tapatalk
It does not like our phones. Has great options but.......it sucks. Everytime I flash it on my phone my recovery goes bad in a cpl days. Never had this problem with RA. Do a search rom manager pops up all over the place with bad recoveries. Stop using it ppl. Im sure ill get flamed for this but oh well. Kinda tired of reading of noobs that fall victim to a .apk that seems very easy to use until it craps out and then your stuck at the airport with a bad recovery and ADB no where in sight. Or even if u had ADB you still have no clue how to fix it!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=742007
http://forum.xda-developers.com/showthread.php?t=762325
http://forum.xda-developers.com/showthread.php?p=7443928&highlight=revovery#post7443928
I couldn't agree more.
never used it thank goodness.........
Never happened to me
EDIT: Sorry for my rudeness, anyways, people should know that it's not the greatest idea to use rom manager with cm5/cm6. It has already been established that it may be a bad idea to use the program with the following roms. Sorry I get really cranky in the mornings, not the best idea to come onto the forum with some old news :|
protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
I have never used it and I agree with him just from all the posts I have seen related too it messing up people's recovery images. Does that make me stupid?
I've used it for a few weeks now with no problems on my MyTouch on 1.6, 2.1, and 2.2 ROMs. Not saying others aren't having legitimate issues, but people in general are much more likely to post negative reports than positive ones.
protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
hahahahaha good one. Not to stupid to use it. the ui is very simple and easy to use. Flash clockwork or flash alternate. What im to stupid to do is figure out how to fix it after it kills recovery. but thank you for your input, I'm sure it will help someone out.
protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
Please lead us retartds through your install procedure, current rom, set-up so we can be as learndededed as you. I have had cm5&6 with ra installed upon initial set up. No swap/ noext1234, stock mt3g spl 2.22.23.02 radio. Nothing special. I even did it with the donut mytouch rom w/root.I only use basic apps, nothing that would interfere with recovery. to me it seems that when u flash a cpl different roms a day is when it hangs up. I can usually get the phone to boot back up, which gives me a chance to get back into rom manager and flash ra recovery back to the phone. the last cpl times I had to wipe cache before it would actually flash RA recovery. so basically if u can get the phone to boot past the splash screen go to rom manager and flash the **** out of ra recovery until it works. First we found out that clockwork didnt like flashing zip's and backups on low batteries 30% and lower. then the always fun recoverly log issue(cant recall the exact error right now) and of course the cant get to recovery issue. I know it's not a widesporead problem but it is a problem that renders phones useless until u can find someone nice enough to help u and not treat u like a retard. Not everyone knows as much about phones as you guys do....congratulations you know all there is about phones. go learn some ****ing human decency, if u have nothing helpful to say then shut up.
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
arefin said:
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
hmmmmm. Maybe since its flashing clockwork from inside rom manager is what might be killing it for some of us. tonight I will try just flashing clockwork outside of rom manager and see how that goes. i like clockwork's set up and it is easy to use, just kinda freaks me out when my recovery goes bad.
arefin said:
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
but at the same time thats why it is a part of rom manager. one click recovery flasher. to make it "easy". i highly doubt you can go into rom manager and incorrectly flash clockwork recovery. its a one click thing
it's also spoken out at many threads at xda that flashing the recovery from within the OS causes issues, so trying to install the recovery from PC or even RA1.7 should be a better option.
I'm considering that you already know the commands for that. better luck! remember, clock work will allow you to flash anything without signing - meaning? you can edit any update.zip to your liking and then forget about all the trouble of signing it before flashing. a simple toggle should do the trick while you are in recovery mode happy flashing.
Sent from my T-Mobile G1 using XDA App
It is either a case of your phone, sd card setup/left over files etc..
I use rom manager on every phone I root with no problems since its release. 6 G1's, 3 Fender LE's, 7 Mytouch 1.2 and 4 Evos. Sometimes, it takes couple seconds to show up or go into recovery, but that doesnt mean its gone. Recovery cant just dissapear without something either trying to over write it or it being erased.
crypysmoker said:
It is either a case of your phone, sd card setup/left over files etc..
I use rom manager on every phone I root with no problems since its release. 6 G1's, 3 Fender LE's, 7 Mytouch 1.2 and 4 Evos. Sometimes, it takes couple seconds to show up or go into recovery, but that doesnt mean its gone. Recovery cant just dissapear without something either trying to over write it or it being erased.
Click to expand...
Click to collapse
Im gonna give it one more try. I dont think I have ever.....
flashed clockwork from rom manager
reboot into recovery from rom manager right then (read some where that on some roms when u reboot to recovery using the regular way it might mess up....not sure about this one).
wipe everything (clockwork wipes more that amon ra)
reflash any rom
in my case... above steps then in this order
flash fireats custom mtd part 1.1
super E
Gapps
overclock update
fireats custom mtd part 1.2
anyone see a issue with what I have done so far??
Ok I will post back when clockwork fails again.....and if not f-in sweet
chrisgto4 said:
It does not like our phones. Has great options but.......it sucks. Everytime I flash it on my phone my recovery goes bad in a cpl days. Never had this problem with RA. Do a search rom manager pops up all over the place with bad recoveries. Stop using it ppl. Im sure ill get flamed for this but oh well. Kinda tired of reading of noobs that fall victim to a .apk that seems very easy to use until it craps out and then your stuck at the airport with a bad recovery and ADB no where in sight. Or even if u had ADB you still have no clue how to fix it!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=742007
http://forum.xda-developers.com/showthread.php?t=762325
http://forum.xda-developers.com/showthread.php?p=7443928&highlight=revovery#post7443928
Click to expand...
Click to collapse
chrisgto4 said:
hahahahaha good one. Not to stupid to use it. the ui is very simple and easy to use. Flash clockwork or flash alternate. What im to stupid to do is figure out how to fix it after it kills recovery. but thank you for your input, I'm sure it will help someone out.
Click to expand...
Click to collapse
You found your answer within the first example link that you provided, look at post #3:
http://forum.xda-developers.com/showthread.php?t=742007
rom manager is not for idiots like yourself. rom manager is a great tool for many different phones. sometimes it doesnt flash a recovery correctly maybe it be poor service to download the recovery, or low memory when flashing it. an advanced user (who its made for) can still flash recovery via fastboot, and have all the helpfulness and easy ui of rom manager and easy access to cm nightlies.
dont knock a dev who works on many different phones, and dont rely on noob application reports and bad reviews. anyone who finds rom manager crap is just a poor android user.
tehseano said:
sometimes it doesnt flash a recovery correctly maybe it be poor service to download the recovery, or low memory when flashing it.
dont rely on noob application reports and bad reviews. anyone who finds rom manager crap is just a poor android user.
Click to expand...
Click to collapse
i didn't want to get into this pointless discussion, but you have made a ****ty argument for rom mgr, you have confirmed that it doesn't work properly in certain circumstances, which is a good enough reason to not bother with it.
also, why shouldn't we rely on bad reviews? that's the point of a review, to give some idea about what experience to expect.
(i have never used it myself, amon ra recovery is enough for me.)
I agree it is an 'easy' shortcut that is not the best decision.. Like for example I think it killed my phone. I repaired permissions via rom manager, rebooted as it told me to and now my g1 wont boot past the g1 logo. I could install from a backup but the backup is 1+ month old (my error oops!). I am hoping to find a solution... Really dont wanna wipe everything..
warsng said:
i didn't want to get into this pointless discussion, but you have made a ****ty argument for rom mgr, you have confirmed that it doesn't work properly in certain circumstances, which is a good enough reason to not bother with it.
also, why shouldn't we rely on bad reviews? that's the point of a review, to give some idea about what experience to expect.
(i have never used it myself, amon ra recovery is enough for me.)
Click to expand...
Click to collapse
I made a perfectly good argument. Yes it can "mess up", but thats not at the fault of the app. It's at the fault of the phone. There are things that can go wrong that Koush cannot control. It is for ADVANCED users as a quick helpful UI for recovery-based operations. People that don't know what they're doing, or only half-way do shouldn't be using it. However, too many Android users *think* they are advanced enough, yet 5 minutes after using it, post a "PLEASE HELP, PHONE IS BROKEN", because they DON'T know what they're doing.
I'm not saying that all bad reviews are missguied, but I can assure that 90% of them are from noobs that have no idea what they're doing. They rooted their phone because someone told them it was cool, and they have absolutetly no idea whats in their hands and what they can do with it. Let alone, how to properly work it and fix problems. It's easy as pie to point out noobs from those crowds of users, those 3 links in the OP's post are all perfectly examples. People who came to XDA, signed up, never posted anything, then messed up and came crying to the board asking for help (usually in Android Development because people like them, and the OP too, don't how to to post in the correct section).
So for the last time, if you don't know what you're doing on your phone, don't do it. Just because you have root, and an app says "for root users", doesn't mean its for you, which EVERYONE assumes it is. It's piss-poor users like that, that ruin app reviews and the name of Android everywhere.
tehseano said:
I made a perfectly good argument. Yes it can "mess up", but thats not at the fault of the app. It's at the fault of the phone. There are things that can go wrong that Koush cannot control. It is for ADVANCED users as a quick helpful UI for recovery-based operations. People that don't know what they're doing, or only half-way do shouldn't be using it. However, too many Android users *think* they are advanced enough, yet 5 minutes after using it, post a "PLEASE HELP, PHONE IS BROKEN", because they DON'T know what they're doing.
I'm not saying that all bad reviews are missguied, but I can assure that 90% of them are from noobs that have no idea what they're doing. They rooted their phone because someone told them it was cool, and they have absolutetly no idea whats in their hands and what they can do with it. Let alone, how to properly work it and fix problems. It's easy as pie to point out noobs from those crowds of users, those 3 links in the OP's post are all perfectly examples. People who came to XDA, signed up, never posted anything, then messed up and came crying to the board asking for help (usually in Android Development because people like them, and the OP too, don't how to to post in the correct section).
So for the last time, if you don't know what you're doing on your phone, don't do it. Just because you have root, and an app says "for root users", doesn't mean its for you, which EVERYONE assumes it is. It's piss-poor users like that, that ruin app reviews and the name of Android everywhere.
Click to expand...
Click to collapse
Get a clue , its a program any gimp, including you, can install from the market, it is made in such way ...the fact that it dosent fail to write the recovery in fastboot mode means nothing!
This program shouldnt let the G1 user flesh any rec image. Till that happens it is the DEV's fault. Shouldnt be in the G1 CM's either.
Please try this and report back. The following procedure worked on a brand new Desire S with S-ON so I am assuming it will work on incredible as well.
With phone on go to:
Settings/Power/
Uncheck "fast Boot"
exit settings
Turn phone off
Boot with Power and volume down
wait
select "Recovery"
hit power to select
wait
you will now get a stupid icon on screen that won't go away
hit power and volume up
you should now be in recovery
From here you should be able to install a ROM as long as it is signed.
You may also be able to do some hackery if plugged into usb while in this screen using ADB or Fastboot. Please try and report back.
Best
Ty
Ref:http://forum.xda-developers.com/showthread.php?p=13216354#post13216354
Confirmed working.
Tried is on my S-ON IS.
You get into Android Recovery <3e> =)
Technically it should be possible to debrand a network branded handset with a P***.zip file on an sdcard?? Or am i barking up the wrong tree?
Yep, S-ON IS will boot into recovery using this method. Though I haven't flashed a ROM or tried any 'hackery' as yet.
Thanks for posting back with confirmation.
Hopefully some folks with some badass adb-foo will hit back with some test results on using adb or fastboot in this mode.
I am sure "fastboot oem unlock" won't work but one can dream.
Hope someone can try simply running these 2 commands in the recovery mode:
adb devices
and
fastboot devices
and let us know if either work.
Ty
Won't work, fastboot doesn't recognize it and adb is disabled in HTC recovery, I thought (but not sure) that usb is disabled completely. Almost everything has been tried to hack the recovery. But it checks the files to many times, so exploits through scripts doesn't work. It checks the file's signature before flashing and since hijacking cannot be done it will be one hell of a job. A lot of high skilled hackers tried it already for a month almost non-stop.
But if you can come up with a way to exploit, your the god in here haha
So its Not possible to sign a custom ROM? Apks Care able, so why no Rom?
shared from my HTC IncS using the xda app
Yes, it work but it show "E:Can't open /cache/recovery/command"
what's wrong on my device?
yes works on bell/canada s-on is now can someone post virgin gb update zip pls
erhm sorry for being a partypooper but, this is totally normal that u can enter recovery....
Leave it to hawky to make it short and simple
Sent from my HTC Incredible S using XDA App
You can sign a Rom, but it is not signed with HTC's key, they keep it private, the device has a public key within it, which can see if its from HTC, go look at a wiki about public and private keys/signing. Will make it a lot clearer!
So no use
Big step! I think we are closer to root!
Recovery working on my IS S-On, hope some devs will be able to make something for IS soon....
It's no step at all.... This is already known and found useless. Unless HTC releases signed s-off bootloader. So this "discovery" is already known and not worth anything
I think bruce needs another 20 steps, maybe than he realises he actually moved sidewards instead LOL
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
I think bruce needs another 20 steps, maybe than he realises he actually moved sidewards instead LOL
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
root has already been found. but it's costly. XTC Clip. I'm luckily beta tester and will be getting 5 extra clips to S-OFF any android phone... holla
Let me say I had an EVO and used Unrevoked to root it and all I did was use that for wifi.
So now I have an unrooted Nexus. I am in a position that I want some of the custom things but have not rooted and a lot of this technical stuff floors me at this point and I do not want to brick my phone.
Can anyone tell me what it means to install via recovery, how to do a backup and what deoxxed (I know it is spelled wrong) is?
I want to put a custom home screen, I like the blue market I see and I like the clear MMS that is posted, but the install instructions just confuses me.
Sorry if this is a stupid question, but I really am wanting to customize my Nexus 4G.
steveh552 said:
Let me say I had an EVO and used Unrevoked to root it and all I did was use that for wifi.
So now I have an unrooted Nexus. I am in a position that I want some of the custom things but have not rooted and a lot of this technical stuff floors me at this point and I do not want to brick my phone.
Can anyone tell me what it means to install via recovery, how to do a backup and what deoxxed (I know it is spelled wrong) is?
I want to put a custom home screen, I like the blue market I see and I like the clear MMS that is posted, but the install instructions just confuses me.
Sorry if this is a stupid question, but I really am wanting to customize my Nexus 4G.
Click to expand...
Click to collapse
Check out the One Click Root thread in the Nexus S 4G Development section. See if that helps a little more. Your probably going to get flamed for posting this in this section, but oh well. Read that and try to get rooted first. Then if you need more help after that feel free to shoot me a PM and ill try to help you more. Read different threads as well, just search XDA for root NS4G. Hit me up if you need some help with anything.
Sent from my Nexus S 4G using XDA Premium App
steveh552 said:
Let me say I had an EVO and used Unrevoked to root it and all I did was use that for wifi.
So now I have an unrooted Nexus. I am in a position that I want some of the custom things but have not rooted and a lot of this technical stuff floors me at this point and I do not want to brick my phone.
Can anyone tell me what it means to install via recovery, how to do a backup and what deoxxed (I know it is spelled wrong) is?
I want to put a custom home screen, I like the blue market I see and I like the clear MMS that is posted, but the install instructions just confuses me.
Sorry if this is a stupid question, but I really am wanting to customize my Nexus 4G.
Click to expand...
Click to collapse
I went through the exact same thing. If you start reading more threads it will start coming to you. When you root, you need the drivers (adb and fastboot) installed on your computer, they come with either pdanet or sdk which you can find the download links to with a quick search of the forums. Find the stickied section of NS4G dev section and those should have all the files you need. Cwm is Clockwork Mod Recovery. It is flashed after unlocking the bootloader using a command prompt. After rooting and flashing cwm, you boot into recovery(cwm) and follow the instructions from a root guide to flash your new rom. I think BuglessPete has a great tutorial on root and flashing a rom. Find that and you're good to go. Don't get discouraged. It is NOT as hard or complicated as it seems. You will be surprised at how simple these guys have made it for us newcomers. Make sure you give them a thanks.
Sent from my Nexus S 4G using XDA Premium App
So it was a day from you know what. I got rooted first this morning, I did the first update that I wanted which was the blue market, epic fail. I spent the whole day trying to get my market to work again, no go. I had not backed up (stupid me) and when put that new market in it was a FC galore. I tried downloading other market apk's including the market that is due to be released and none would install. I ended up flashing the phone with Oxygen ROM. Now I have to get the phone back to the way I like it, lots of apps to download (not sure why they did not restore since I am set to back up/restore from google servers) and go from there.
I will be doing more I am sure, lots of reading to do. Thanks to the two of you.
Lets see if we can get
- Locked bootloader
- Custom rom security issues
and maybe other security related problems in one development thread and how we make apps to get around this
I take the lead for now, since i started testing custom roms (JellyBean) right now.
and the DRM check at bootup is important to get around, otherwise we end up, having to restore a v10 image again and again, too often.
i suspect that it can be done using a bind folder. but lets see where this takes us.
just update with other issues seen.
Dexter_nlb said:
Lets see if we can get
- Locked bootloader
- Custom rom security issues
and maybe other security related problems in one development thread and how we make apps to get around this
I take the lead for now, since i started testing custom roms (JellyBean) right now.
and the DRM check at bootup is important to get around, otherwise we end up, having to restore a v10 image again and again, too often.
i suspect that it can be done using a bind folder. but lets see where this takes us.
just update with other issues seen.
Click to expand...
Click to collapse
Sounds little bit like Chinese for me but hope you can get a break through and goodluck for all who trying to make it for us an even great phone
ok, i have had my jellybean semi running and oneX rom running, both not very functional, as most hardware did not work well.
the lgdrmserver kept crashing on me as well, but probably less important.
the solution i made was the early boot used the original libraries from /lib from and vendor/lib , so i simply mapped the 2 files in /lib with a symlink to the /system/drm folder and ran the wallpaper binary and it worked fine.
secondly changed a vold binary to be a little script, that
1: bind'd new libraries for drm in drm2 folder (mount -obind drm2 drm) so the new booting os would get related files.
2: start vold
and the workaround seemed to do just fine for the drm security check.
IF it fails during regular boot if you unintentionally copied over the files, do not worry. booting into safe mode (keep VOL UP pressed and press power) you can connect with a shell and bypass the check, and fix your failure and reboot.
Hi
Is DRM checking forced from kernel?
Can we live without it?
no, its called from init.d
Dexter_nlb said:
Lets see if we can get
- Locked bootloader
- Custom rom security issues
and maybe other security related problems in one development thread and how we make apps to get around this
I take the lead for now, since i started testing custom roms (JellyBean) right now.
and the DRM check at bootup is important to get around, otherwise we end up, having to restore a v10 image again and again, too often.
i suspect that it can be done using a bind folder. but lets see where this takes us.
just update with other issues seen.
Click to expand...
Click to collapse
It is allways exciting to see people like you fellow.
Curious, courageous, openminded, wise and most of all doing all without expecting anything.
Success on your way..:good:
Dexter_nlb, You're a hero :good:
When will be released some beta?
since we have root, shouldnt init.d be accessable and easily modifyable?
The Troll said:
since we have root, shouldnt init.d be accessable and easily modifyable?
Click to expand...
Click to collapse
its part of the boot.img (ramdisk), so not really, but the 2nd-init makes it possible to make a new ramdisk and start it. but its only ramdisk, not the kernel, which remains static.
downgrade mode?
sorry, im a htc user thinking of buying this phone.. *since s3 isn't tegra, not thd games and one x kinda sucks with the lack of sd card and stuff..*
but htc has a dorwngrade mode.. 2 exposed connectors close to the camera.. short circuit them to access downgrade mode.. and then flashable though linux..
if im right, that should give u open access to bootloader..
evo 3d cdma used this method to get s-off.. as in bootloader unlocked and accessable with all write restrictions removed on all partitions..
oh forgot to meantion, this can brick ur device.. actually downgrade mode itself is a bricking method.. so i'd be careful *assuming this method is true for gs as well*
The Troll said:
downgrade mode?
sorry, im a htc user thinking of buying this phone.. *since s3 isn't tegra, not thd games and one x kinda sucks with the lack of sd card and stuff..*
but htc has a dorwngrade mode.. 2 exposed connectors close to the camera.. short circuit them to access downgrade mode.. and then flashable though linux..
if im right, that should give u open access to bootloader..
evo 3d cdma used this method to get s-off.. as in bootloader unlocked and accessable with all write restrictions removed on all partitions..
oh forgot to meantion, this can brick ur device.. actually downgrade mode itself is a bricking method.. so i'd be careful *assuming this method is true for gs as well*
Click to expand...
Click to collapse
nah, we haven't nothing to lose... someone should try it
The Troll said:
but htc has a dorwngrade mode.. 2 exposed connectors close to the camera.. short circuit them to access downgrade mode.. and then flashable though linux..
if im right, that should give u open access to bootloader..
evo 3d cdma used this method to get s-off.. as in bootloader unlocked and accessable with all write restrictions removed on all partitions..
Click to expand...
Click to collapse
i believe you reference a different hardware platform not Nvidia based. o4x is nvidia tegra3 and different from omap and other platforms security wise.
can you link to the tegra fuse , you reference here? (fuse is a connector which will break the firmware open and full access granted, but can also cause firmware to not load, since fuse is broken)
reas0n said:
nah, we haven't nothing to lose... someone should try it
Click to expand...
Click to collapse
flash image GUI..
someone rooted should try that first..
also, unlimited.io <--- website.. for details of the downgrade mode trick..
http://forum.xda-developers.com/showthread.php?t=1547695
http://forum.xda-developers.com/showthread.php?t=1491107
http://forum.xda-developers.com/showthread.php?t=1563342
http://forum.xda-developers.com/showthread.php?t=1627917
the basic idea of this is 2 connectors close to the camera.. short circuit them to switch the phone to downgrade mode *QHSUSB_DLOAD*.. bricking the device and mounting all partitions as read and writable.. then using linux to find the right partition to flash/dump the hboot *the bootloader*
at the end, if it uses fastboot/adb, i dun think this will be too different from the evo 3d..
try it.. but dont say i didnt warn you..
im not sure its a fuse, its more of a reset?
also, i dont exactly have the phone *yet* so i cant tell..
but for the 3d, its exposed.. 2 holes in the back under the cover, next to the camera..
http://unlimited.io/juopunutbear-public-beta-0-1/instructions/evo-3d-cdma-shooter/
or you can find a schematic of the phone itself..
if you dont mind me asking, whats the reason for the lack of devs?
this is an excellent phone..
is it the extreme security?
iphone got a jailbreak too :/
ok, this is a QUALCOMM solution, not for our tegra3 based platform
Dexter_nlb said:
ok, this is a QUALCOMM solution, not for our tegra3 based platform
Click to expand...
Click to collapse
how did one x get the kernels running?
**edit.. nvm.. htcdev.. forgot..
Hope you guys can pass by all that anoyeingsecurity. Would like to buy that phone but without real controll over the hardware aand custom rom community i would seariously reconsider buying it...
Dexter, the One X solution is for Tegra3 devices. The QUALCOMM-Device is called HTC One XL. So if the chipset is nearly the same, there must be a solution? If I could code anything, I would. But I cannot
Hilmy said:
Hope you guys can pass by all that anoyeingsecurity. Would like to buy that phone but without real controll over the hardware aand custom rom community i would seariously reconsider buying it...
Click to expand...
Click to collapse
Instead of trying to bypass, people should be asking LG for an unlock mechanism. I've been talking to them about this for over half a year, and today they still feel there is no demand for it (unlock tools)
Show of hands: How many people here have actually e-mailed LG asking for an unlock procedure, for this or any other of the current locked generation?
aremcee said:
Instead of trying to bypass, people should be asking LG for an unlock mechanism. I've been talking to them about this for over half a year, and today they still feel there is no demand for it (unlock tools)
Show of hands: How many people here have actually e-mailed LG asking for an unlock procedure, for this or any other of the current locked generation?
Click to expand...
Click to collapse
do you have the mail address we can use? then we can engage a mailrobot to send them 10000s of mails regarding the unlocker, and maybe they will follow asus and motorola/google on this one.
Dexter_nlb said:
do you have the mail address we can use? then we can engage a mailrobot to send them 10000s of mails regarding the unlocker, and maybe they will follow asus and motorola/google on this one.
Click to expand...
Click to collapse
I'd rather not forewarn them by asking for a contact for this
My personal opinion: a mailrobot would be a bad idea, they'd just filter it out. Actual users, with actual devices (serial numbers in the message and all that) would carry much more weight than just generic "gimme". From experience... petitions don't work, either, unless they hit visible news outlets;
My suggestion would be to hit a support contact, consistently (instead of dispersing the message to random contacts); most companies will escalate any issue given enough occurrences of it. On the other hand, I can't find contacts besides the country-specific ones at http://www.lg.com/global/supports/service-sites.jsp ...