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
Related
All I would like to do is get my (not unlocked, but un-rooted) back to a stock recovery (I think?) and a stock OS. I want to be able to do updates OTA as they arrive on my phone, and the only reason I rooted in the first place was to get Gingerbread from CM7 and they didn't work. It got stuck in a endless boot loop and once I finally got a nightly working, it wasn't even worth it to me anymore.
I have used this thread: http://forum.xda-developers.com/showthread.php?t=614850
and done hours and days of research to try and solve my problem and get me to where I would like to be. I'd like to think I am not a noob to Android but clearly I am and I can't achieve 100% of my goal.
Where I am currently: Stock image, not sure of recovery, unrooted, bootloader unlocked.
Where I would like to be: Stock everything (I know I cannot relock the bootloader) just like when I bought it, so I can patiently wait for Gingerbread to push OTA whenever Google solves the issues.
Thank you and I apologize.
That guide has pretty much all the information you need. Flashing the stock HTC images and stock recovery will enable you to get OTA updates.
Read my signature, find "Unroot/restore" guide, look for the part for unlocked bootloaders.
Clearly that did not work for me or I would not have posted my concern.
@Jack_R1 I will attempt this again, thanks.
rynstphn said:
Clearly that did not work for me or I would not have posted my concern.
@Jack_R1 I will attempt this again, thanks.
Click to expand...
Click to collapse
You didn't explain where you got stuck, what you attempted, what went wrong and couldn't even state your recovery image. The guide you linked to is there for a reason, it works, however onlyif you follow it correctly without jumping in with 2 feet. If in future you require more precise help perhaps you should give precise information.
Perhaps the OP has encountered some of the issues i've posted about HERE?
Don't mean to kind of hi-jack this thread...
Don't mean to kind of hi-jack this thread but on the related topic of rooting the N1...is there some way to root it and still receive the OTA update for gingerbread(whenever it will come out)?
I did look through the threads and found nothing related unless it was further discussed on page x of 25, for example.
Also, are all wallpapers 960/980 by 800 for the N1 and other android phones? Is this so that when you scroll through screens you will still be able to see the image? That was the only possible answer I could think of.
Thanks in advance.
CTR01 said:
Don't mean to kind of hi-jack this thread but on the related topic of rooting the N1...is there some way to root it and still receive the OTA update for gingerbread(whenever it will come out)?
I did look through the threads and found nothing related unless it was further discussed on page x of 25, for example.
Also, are all wallpapers 960/980 by 800 for the N1 and other android phones? Is this so that when you scroll through screens you will still be able to see the image? That was the only possible answer I could think of.
Thanks in advance.
Click to expand...
Click to collapse
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Thanks!
DirkGently1 said:
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Click to expand...
Click to collapse
Awesome! Thanks for the reply and details.
DirkGently1 said:
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Click to expand...
Click to collapse
Having a custom recovery has NOTHING to do with your ROM's ability to receive OTA updates... it has to do with you ROM, not your recovery.
And, as mentioned, rooting or unlocking has no impact on you being able to receive OTA updates.
Sent from my Nexus One using XDA App
efrant said:
Having a custom recovery has NOTHING to do with your ROM's ability to receive OTA updates... it has to do with you ROM, not your recovery.
And, as mentioned, rooting or unlocking has no impact on you being able to receive OTA updates.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Sorry, but that is wrong.
http://forum.xda-developers.com/showpost.php?p=10871795&postcount=1
Read that post. There is a stock recovery supplied in case anybody wishes to recieve future OTA updates.
DirkGently1 said:
Sorry, but that is wrong.
http://forum.xda-developers.com/showpost.php?p=10871795&postcount=1
Read that post. There is a stock recovery supplied in case anybody wishes to recieve future OTA updates.
Click to expand...
Click to collapse
Uh, sorry, but NO. What he says in that post is incorrect.
I have been using a custom recovery since I first got my Nexus One, and I have received EVERY OTA update.
EDIT: But hey, don't take my word for it. Try it yourself.
efrant, for clarification, do the OTAs auto install, or do you have to manually flash them?
Sent from my Nexus One using XDA App
danger-rat said:
efrant, for clarification, do the OTAs auto install, or do you have to manually flash them?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
So, in my setup (which is a rooted-but-otherwise-stock ROM and Amon_RA's 1.9.0 recovery), I receive OTA updates, and they auto-install with no problem (as Amon_RA's 1.9 recovery does not verify signatures). Note, however, that every OTA update also does two things: 1) it removes the permissions on the su binary (which obviously disables root access), and 2) it copies two files (/system/recovery-from-boot.p and /system/etc/install-recovery.sh) back onto the system partition, which will flash the stock recovery back to your devices as soon as you reboot. You will need to root first (either manually or by flashing ChainsDD su update before you reboot, or use SOC), then delete the two files, then reflash the custom recovery you want.
This is true only for Amon_Ra's 1.9 and later recoveries that either don't verify signatures at all, or allow turning verification off.
Jack_R1 said:
This is true only for Amon_Ra's 1.9 and later recoveries that either don't verify signatures at all, or allow turning verification off.
Click to expand...
Click to collapse
Yes, you are correct for the installation part of the update. However, you can have any recovery whatsoever, and it will not impact you receiving OTA update notifications.
efrant said:
Yes, you are correct for the installation part of the update. However, you can have any recovery whatsoever, and it will not impact you receiving OTA update notifications.
Click to expand...
Click to collapse
Yep, that's correct.
Cool
thanks for all the other responses to my question! I will look into this further when i have more time
Of course you can still 'receive' OTA but what's the point if you can't install them? I'm pretty sure that everybody understands the distinction!
DirkGently1 said:
Of course you can still 'receive' OTA but what's the point if you can't install them? I'm pretty sure that everybody understands the distinction!
Click to expand...
Click to collapse
If you read post 14, you will see that you CAN install them with a custom recovery...
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Have you checked with Root Checker Basic to see if you even have Root? If you didn't follow the Super Guide step by step your phone could have relocked after you turned your phone off/on.
If it still fails to update you could try SuperUser Update Fixer.
Yes I have check with root checker.
This may be a dumb question but how do I uninstall Superuser? When I go to the typical application management it does not give me the option. I have done an install again to overwrite the files and nothing changed there.
I followed the instructions step by step (though obviously I messed up somewhere...)
Sent from my HTC PH39100 using XDA App
Kraizk said:
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Click to expand...
Click to collapse
Interesting... maybe your root didn't stick. We had a little trouble with that before but pirateghost fixed the CWM ROOT zip. You have a working CWM Recovery, correct?
In the superguide, I have a second option for root in case the first doesn't work. In your case, go ahead and try the second option. The one involving the supertool. That should get you perm root. If that doesn't even work, then we might have to put you back to stock and go at it again.
EDIT: BEFORE TRYING THE SUPERTOOL, try flashing the new CWM ROOT VER2 zip from CWM recovery and see if root sticks.
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Kraizk said:
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Click to expand...
Click to collapse
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
*Just a clarification*
You have to unroot your phone to get rid of it Idk why I put uninstall/reinstall earlier...still out there from last night I guess.
slapshot30 said:
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
Click to expand...
Click to collapse
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Kraizk said:
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Click to expand...
Click to collapse
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
slapshot30 said:
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
Click to expand...
Click to collapse
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Kraizk said:
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Click to expand...
Click to collapse
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Kraizk said:
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Click to expand...
Click to collapse
It's no problem, this isn't a dumb question or easy issue by any means. If the method I directed to you doesn't work, let me know. There is another way to do it without all the code.
slapshot30 said:
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Click to expand...
Click to collapse
Worked perfectly. I flashed it back to stock using the thread you linked me to. Then I did the CWM Root method and so far so good. I appreciate all of your help
Nice, I'm glad you were able to get everything working.
Sent from my HTC PH39100 using xda premium
Can the Hasoon2000 kit still root the HTC Vivid(4.0.3)? I have found no answer to this as that is why am asking.
At the moment it can't he is working on updating script to work on ics.
Sent from my HTC PH39100 using xda premium
megatronisbeast
Did the toolkit work for you? Ive seen several of your post, and was woundering if it did. Did you have to do anything different other than the instructions?
The toolkit does work, just can't root at the moment.
Sent from my HTC PH39100 using xda premium
megatronisabeast
Would you happen to know about how long it takes to script? I'm just woundering because I hate the new update and would like to root(s-off) and then flash a rom. I liked sense but want vanilla-android. Thanks again for your helpful post. I'm not asking if you know an ETA or anything like that, just from your experience.
playerjunglejosh said:
Would you happen to know about how long it takes to script? I'm just woundering because I hate the new update and would like to root(s-off) and then flash a rom. I liked sense but want vanilla-android. Thanks again for your helpful post. I'm not asking if you know an ETA or anything like that, just from your experience.
Click to expand...
Click to collapse
Really don't know that info, however if you want to get root but don't want to wait there are other ways to do it. Let me know if you are interested and I will post them up. Consider though it will take longer than it would using the toolkit.
megatronisabeast
I'll try pretty much anything. I've rooted several devices, so findind a new way for another one won't hurt. Only thing that I really would like to do is avoid making a gold card, but if you have to do that I think I will wait for the toolkit. Thanks!! Do you know if it's possible to temp root, flash a kernal with cwm, and then flash a rom?
Here is what you need to do to root your phone, etc.
First thing is to download android sdk:
http://developer.android.com/sdk/index.html
It will allow you to send files to your phone from your computer-no s-off so can't flash kernel in recovery only fastboot.
While that is downloading if you haven't already you need to unlock boot loader by going to:
http://htcdev.com/
Don't forget to keep the unlock code so if you need to relock your boot loader.
Next, it sounds like you want to flash a custom rom. If so the best one in my opinion is found here:
http://www.wcxxperia-nce.com/index.php
You have to register to see the vivid section.
Once there you will download the zip file, put a copy on your phone, the other copy unzip and place the boot.img and wcx recovery in the same folder that you have the fast boot file that you downloaded earlier from sdk.
Then you put your phone into hboot mode, plug it in to usb port, make sure on phone screen is says fast boot usb in red.
Then open command prompt in your folder with fast boot by clicking shift and the right mouse button.
Type in these commands:
fastboot flash boot boot.img
fastboot flash recovery wcxrecovery.img
After those steps power down phone, unplug from computer, return to hboot, click on recovery, then flash the zip file that you placed on there earlier.
That's it, you got it root and all.
Also if you do use his rom, restart phone 3 times to settle phone in and cycle battery 3 times to make sure everything is working correctly.
Here is a video if you feel overwhelmed to help guide you brought to you by randong!
http://www.youtube.com/watch?v=xEWa_lUd2bY&feature=youtu.be
Hope this has helped you!
You can use wild child's recovery to perm root ics check it site for the video if you need proof
Sent from my HTC PH39100 using xda premium
We just need S-OFF so we can simplify this entire thing by using CWM. It's so much easier being able to flash a scripted .zip package in there than dealing with fast boot.
Sent from my HTC Vivid
slapdaddy said:
We just need S-OFF so we can simplify this entire thing by using CWM. It's so much easier being able to flash a scripted .zip package in there than dealing with fast boot.
Sent from my HTC Vivid
Click to expand...
Click to collapse
True, I just wish I knew how long "scripting" takes. I know the video is very clear, and that I'm very good with technology, however I do think that there is a good chance I might mess up...thus I believe I will wait, but I will do some more research be4 deciding what to do
playerjunglejosh said:
True, I just wish I knew how long "scripting" takes. I know the video is very clear, and that I'm very good with technology, however I do think that there is a good chance I might mess up...thus I believe I will wait, but I will do some more research be4 deciding what to do
Click to expand...
Click to collapse
I've never done it myself but it shouldn't be that difficult. I think I'm just spoiled coming from the Inspire - it was rooted, S-OFF'd, and had a few custom ROMs up the within a couple days of its launch. The level of development for that device was extreme from the very beginning.
Sent from my HTC Vivid
True, I still have an Inspire and the development is still booming. I personally just wish HTC would have made the Vivid as dependable as the Inspire, bc my Vivid has all sorts of problems. Turns off randomly, and each time when it turns back on it says "upgrading android" and then it optimizes the apps for ICS. Most of the time it won't flip my pictures(rotate)<--yes auto rotate is on...but all in all HTC went down in quality with the Vivid. Personally this is why I want to root, that way I don't have to worry with HTC screwing up the update.
it does work but i have found that busybox isnt installed/installed correctly and have had to install it from the market for titanium backup to recognize my root.
A reply to numerous posts...you don't need S-OFF on the Vivid, developers have yet to figure out how to do so. It's rumored some users have received their phones shipped with S-OFF, but to my knowledge it's not because of any modifications.
Follow this thread to accomplish everything Hassons2000 tool is trying to do for the Vivid. I didn't work for me either.
****read the following thread VERY carefully***
http://forum.xda-developers.com/showthread.php?t=1416836.
If you have any questions, feel free to ask me.
?
so at the moment there is no real way to root the vivid with stock ICS and basically everything stock? im kindaconfused
Kurrytacos said:
so at the moment there is no real way to root the vivid with stock ICS and basically everything stock? im kindaconfused
Click to expand...
Click to collapse
The link I provided in my previous post will teach you every thing you need to know. It is definately possible If you get stuck on any particular step or if something doesn't make sense, feel free to ask me to explain.
akafarmer said:
A reply to numerous posts...you don't need S-OFF on the Vivid, developers have yet to figure out how to do so. It's rumored some users have received their phones shipped with S-OFF, but to my knowledge it's not because of any modifications.
Follow this thread to accomplish everything Hassons2000 tool is trying to do for the Vivid. I didn't work for me either.
****read the following thread VERY carefully***
http://forum.xda-developers.com/showthread.php?t=1416836.
If you have any questions, feel free to ask me.
Click to expand...
Click to collapse
Having S-OFF let's you flash a kernel through recovery. It simplifies the flashing process and makes developing ROM packages easier for the user.
Sent from my HTC Vivid
slapdaddy said:
Having S-OFF let's you flash a kernel through recovery. It simplifies the flashing process and makes developing ROM packages easier for the user.
Sent from my HTC Vivid
Click to expand...
Click to collapse
Do you have S-OFF on your Vivid?
akafarmer said:
Do you have S-OFF on your Vivid?
Click to expand...
Click to collapse
I wish I did. I was ready to do testing for those devs working on S-OFF but my Linux skills are relatively non-existent lol.
Sent from my HTC Vivid
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 ...
As reported by Modaco, it seems that unlocking the bootloader removes some system apps, among them are the Calculator, Flashlight, Ringtone Trimmer and Sound Recorder (and I've seen a report that the Teeter game is gone too).
Now, I haven't got my own One yet, however I do have access to a Canadian variant from work and we've got another one in America running an older build.
It was running 1.27, now it is running 1.28.
I cannot access the data partition, obviously, not even for read (it is not rooted), however using the pm command I managed to discover which packages are located in the preload directory (excluding the carrier specific apps from my variant):
com.android.calculator2
com.htc.flashlight
com.htc.pdfviewer
com.htc.ringtonetrimmer
com.htc.soundrecorder
Initially I thought ODEX files might be needed, but these are located in the data partition and as far as I know there are no ODEX files there (correct me if I'm wrong).
Using Carbon I've backed them up (see attached here), only thing left is to check whether they can be restored and work properly on unlocked Ones. It might not fit every variant, testing required. Perhaps it might even allow using OTA updates.
If you haven't unlocked your bootloader yet, I suggest trying this beforehand instead of the attached files:
Through ADB, use:
adb shell pm list packages -f | find "preload"
Backup these apps using Carbon.
Unlock bootloader.
Restore using Carbon.
Please let me know if this works.
Thank you so much. Flashlight and calculator is working. The Sound Recorder gives me a force close. But it is a beginning. :cyclops:
Re: [WIP] Restoring Missing Apps Post Unlock: Your Help is Needed
MasterOfDesasters said:
Thank you so much. Flashlight and calculator is working. The Sound Recorder gives me a force close. But it is a beginning. :cyclops:
Click to expand...
Click to collapse
If you keep getting a force close then pmease try settings-application manager-sound recorder-clear data.
This should help clear up any force closures.
Also fixing permissions will help but quicker to just go through settings
Sent from my GT-I9300 using xda premium
---------- Post added at 11:06 PM ---------- Previous post was at 11:04 PM ----------
Trekest said:
As reported by Modaco, it seems that unlocking the bootloader removes some system apps, among them are the Calculator, Flashlight, Ringtone Trimmer and Sound Recorder (and I've seen a report that the Teeter game is gone too).
Now, I haven't got my own One yet, however I do have access to a Canadian variant from work (running version 1.27), and we've got another one in America running an older build.
I cannot access the data partition, obviously, not even for read (it is not rooted), however I did spot some of the missing apps in the system partition. I think that if we pull these files from a locked One and push them after unlocking we might not have to rely on flashing a custom rom to get them back.
Edit: or not... I've seen the Camera and have mistaken it for the Calculator... Idiot...
However, and here's the catch, I'm not sure the files remain unaltered between builds. So, here's the to do list:
Identifying the exact list of missing files post-unlocking - there'd probably be odex files missing as well as APKs, which is why we can't just pull these from a custom rom.
Pulling them from locked Ones (assuming they are in the system partition).
Comparing MD5 changes between different builds.
Testing testing testing.
Update: Stupid... this could be even simpler. These are in the data partition, and ES File Explorer can backup the APKs. I'm grabbing them now. We'll still need to figure out how to get the odex files back.
Update 2: OK, I've got 3/4 of the missing apps, the trimmer could not be backed up (attached them). Will have to continue with it tomorrow.
Maybe this tool can help us:
http://forum.xda-developers.com/showthread.php?t=1844032
Click to expand...
Click to collapse
Hi if you want the .odex files back then you could try just taking them out of the system dump or official firmware.
Just an idea mate
Sent from my GT-I9300 using xda premium
Also if you unlock the phone wont accept OTAs. I hope this is a bug and HTC fix it.
OP updated, please try.
ste1164 said:
Also if you unlock the phone wont accept OTAs. I hope this is a bug and HTC fix it.
Click to expand...
Click to collapse
Anyone who unlocks their phone would not take an ota. I have never taken an ota on the six unlocked htc phones I have had. They almost always have a new bootloader.
Sent from my HTC6435LVW using xda premium
wow that sucks.
i'm planning on getting the phone unlocked without modifying the bootloader or anything...
will just unlocking to use different sims have missing apps?
predation said:
wow that sucks.
i'm planning on getting the phone unlocked without modifying the bootloader or anything...
will just unlocking to use different sims have missing apps?
Click to expand...
Click to collapse
No, completely different, unlocking sim and unlocking Bootloader are worlds apart.
fernando sor said:
Anyone who unlocks their phone would not take an ota. I have never taken an ota on the six unlocked htc phones I have had. They almost always have a new bootloader.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Well, I have current an HTC Sensation, and up until the first ICS update I was stock and rooted, getting OTAs as usual.
Sure, I had to keep a backup of the original recovery and flash it through hboot each time before installing an OTA, however they did work.
I'm not planning on flashing a recovery this time around, I plan on just booting it to install Koush's Superuser and keep the stock one. And if it wouldn't work, just to root and go back to the stock recovery. Until I've had enough of stock :silly:
ste1164 said:
Also if you unlock the phone wont accept OTAs. I hope this is a bug and HTC fix it.
Click to expand...
Click to collapse
Its not a bug, HTC has done this purposely so that you cannot update.
And for everyone who says that you wouldnt want to take OTAs anyway, just wait till a nice update rolls around and then you'll be saying different
CNexus said:
Its not a bug, HTC has done this purposely so that you cannot update.
And for everyone who says that you wouldnt want to take OTAs anyway, just wait till a nice update rolls around and then you'll be saying different
Click to expand...
Click to collapse
If your unlocked you would flash that update as a rom. I'm having a hard time accepting that you wouldn't know that
Sent from my HTC6435LVW using xda premium
fernando sor said:
If your unlocked you would flash that update as a rom. I'm having a hard time accepting that you wouldn't know that
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
You would. But sometimes people cant wait long enough for devs to update their roms to the new base
CNexus said:
You would. But sometimes people cant wait long enough for devs to update their roms to the new base
Click to expand...
Click to collapse
And the same people that aren't patient enough and want instant gratification are also the ones that have the greatest tendency to hard-brick devices, who would've thought...
CNexus said:
You would. But sometimes people cant wait long enough for devs to update their roms to the new base
Click to expand...
Click to collapse
Generally updates are anticipated and usually a stock version will be posted soon after the ota. Actually the fact that you can't receive an ota after unlocking will save a lot of noobs from installing a new locked down bootloader.
OTAs can easily be pulled from your cache. Someone would pull it and upload it.
Sent from my HTC6435LVW using xda premium
fernando sor said:
Generally updates are anticipated and usually a stock version will be posted soon after the ota. Actually the fact that you can't receive an ota after unlocking will save a lot of noobs from installing a new locked down bootloader.
OTAs can easily be pulled from your cache. Someone would pull it and upload it.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I know, I'm not trying to say that it would be there thing to do or the right thing to do, I am only saying in general.
But yes, that is how you pull an OTA, and it definitely is helpful to not accidentally (or purposely) unroot your phone.
So, did anyone restore apps? If so, can someone attach the calculator.apk?
Sent from my awesome fridge
MaartenXDA said:
So, did anyone restore apps? If so, can someone attach the calculator.apk?
Sent from my awesome fridge
Click to expand...
Click to collapse
See my OP - it has a carbon backup of all the missing apps. Just get Carbon from the play store (free) and restore them.
If you could also later tell me where it pushed them? (data/app or data/preload)
Trekest said:
See my OP - it has a carbon backup of all the missing apps. Just get Carbon from the play store (free) and restore them.
If you could also later tell me where it pushed them? (data/app or data/preload)
Click to expand...
Click to collapse
Yeah saw it, and found the apps in TrickDroid ROM zip. Thanks for the work here, but I can't test it cause I don't have the one.
Sent from my awesome fridge
I just installed the apks within the zip file and all seems fine
Trekest said:
As reported by Modaco, it seems that unlocking the bootloader removes some system apps, among them are the Calculator, Flashlight, Ringtone Trimmer and Sound Recorder (and I've seen a report that the Teeter game is gone too).
Now, I haven't got my own One yet, however I do have access to a Canadian variant from work and we've got another one in America running an older build.
It was running 1.27, now it is running 1.28.
I cannot access the data partition, obviously, not even for read (it is not rooted), however using the pm command I managed to discover which packages are located in the preload directory (excluding the carrier specific apps from my variant):
com.android.calculator2
com.htc.flashlight
com.htc.pdfviewer
com.htc.ringtonetrimmer
com.htc.soundrecorder
Initially I thought ODEX files might be needed, but these are located in the data partition and as far as I know there are no ODEX files there (correct me if I'm wrong).
Using Carbon I've backed them up (see attached here), only thing left is to check whether they can be restored and work properly on unlocked Ones. It might not fit every variant, testing required. Perhaps it might even allow using OTA updates.
If you haven't unlocked your bootloader yet, I suggest trying this beforehand instead of the attached files:
Through ADB, use:
adb shell pm list packages -f | find "preload"
Backup these apps using Carbon.
Unlock bootloader.
Restore using Carbon.
Please let me know if this works.
Click to expand...
Click to collapse
It works with a relocked bootloader