hopefully SOMEONE from asus will read this. if not, prime owners email them or whatever.
ASUS-
you need to either-
a- FIX fastboot on primes with unlocked bootloaders.
b- give us working nvflash
c- both
The way we have to do things right now is so dangerous its ridiculous. I should not have to dd a boot image into raw flash, or /try/ to use blobs and the staging partition(which i for some reason can not get to work)
Its great you unlocked the bootloader, and my warranty being voided is fine. But, when there is a greater than necessary risk to hard bricking when there doesnt have to be, it pisses me off.
Right now its safer on other devices that had their bootloaders hacked and never officially unlocked.
DD should not have to be in an updater script, and i should have an easy, fast, relatively safe way to test a developmental kernel/boot.img when theres a high probability it wont work first shot.
I hope broken fastboot was just an oversight that you plan on fixing. At least if i have a soft brick i can just flash a new image, not have to use dd to fix it.
If things stay like this i can guarantee way more people than necessary will end up hard bricking their primes.
/end rant
di11igaf said:
hopefully SOMEONE from asus will read this. if not, prime owners email them or whatever.
ASUS-
you need to either-
a- FIX fastboot on primes with unlocked bootloaders.
b- give us working nvflash
The way we have to do things right now is so dangerous its ridiculous. I should not have to dd a boot image into raw flash, or /try/ to use blobs and the staging partition(which i for some reason can not get to work)
Its great you unlocked the bootloader, and my warranty being voided is fine. But, when there is a greater than necessary risk to hard bricking when there doesnt have to be, it pisses me off.
Right now its safer on other devices that had their bootloaders hacked and never officially unlocked.
DD should not have to be in an updater script, and i should have an easy, fast, relatively safe way to test a developmental kernel/boot.img when theres a high probability it wont work first shot.
I hope broken fastboot was just an oversight that you plan on fixing. At least if i have a soft brick i can just flash a new image, not have to use dd to fix it.
If things stay like this i can guarantee way more people than necessary will end up hard bricking their primes.
/end rant
Click to expand...
Click to collapse
Totally agreed except they need to do a and be. We should already have fastboot working from unlock out the gate. And they should provide nvflash support for those that do choose to unlock based on your reasoning. It only helps us to do more with our warranty voided tablets and also keeps them working when things go wrong. If they want inspired innovation, let us innovate without so much risk!
^^Your right, they should do both.
ASUS, seriously. It's really easy for noobs, and even experienced users, to brick their Prime's. Seriously. Just fix fastboot or give us working nvflash, or preferably both.
Yup, no NVFlash is the biggest reason my prime will remain locked.
Letting you unlock the bootloader is a waste of time if fastboot doesnt work!
NVFlash is the answer though and i see no reason why this cant be released.
Related
I'm 99.9% sold on the Amaze, I will probably be ordering this weekend.
One niggling doubt is the s-off issue. I see that it hasn't been achieved yet, though you can unlock the bootloader via the HTC.com dev code, and that allows perma-rooting and Custom Roms to be installed.
My questions are:
What would S-off achieve? Would there be more impressive roms that use the space and/or resources from /system or somewhere else that can't be touched without S-off? Is a CM 9 possible for the Amaze without S-off? In the CM forums, the "last" word so far is that it hasn't been included on the official list because "it doesn't even have S-off yet".
Is there a difference warranty-wise? I understand the _possible_ implication of asking HTC for the code, they have you in some database that says you unlocked the bootloader. But as for the device itself, is one undoable and the other not?
I understand that flashing kernels would be harder without s-off because it would have to be done via adb, I think I understood. This is no big deal in itself.
Finally: if you unlock the bootloader via the HTC code, and weeks or months down the road an exploit is found to gain S-Off, are you hosed because you used the code and didn't wait?
I'd like to know so I can make my decision before getting the phone. If it's very disadvantageous to use the code rather than wait for S-off, for one reason or another, then I'd have to decide if I can live with only temp-rooting the device.
I am not going to use it on T-Mobile, I'm in Venezuela and will use it with my carrier here, so the unnecessary bloat will be even more of an annoyance, because on top of it sucking, it won't even work; so it would be important for me to at least root to get rid of it.
I'm sorry if my questions are too expansive, I picked up bits and pieces of information in other posts, but none of them answered these questions clearly. Thank you very much to all those who can help me answer them.
el_ochito said:
I'm 99.9% sold on the Amaze, I will probably be ordering this weekend.
One niggling doubt is the s-off issue. I see that it hasn't been achieved yet, though you can unlock the bootloader via the HTC.com dev code, and that allows perma-rooting and Custom Roms to be installed.
My questions are:
What would S-off achieve? Would there be more impressive roms that use the space and/or resources from /system or somewhere else that can't be touched without S-off? Is a CM 9 possible for the Amaze without S-off? In the CM forums, the "last" word so far is that it hasn't been included on the official list because "it doesn't even have S-off yet".
Is there a difference warranty-wise? I understand the _possible_ implication of asking HTC for the code, they have you in some database that says you unlocked the bootloader. But as for the device itself, is one undoable and the other not?
I understand that flashing kernels would be harder without s-off because it would have to be done via adb, I think I understood. This is no big deal in itself.
Finally: if you unlock the bootloader via the HTC code, and weeks or months down the road an exploit is found to gain S-Off, are you hosed because you used the code and didn't wait?
I'd like to know so I can make my decision before getting the phone. If it's very disadvantageous to use the code rather than wait for S-off, for one reason or another, then I'd have to decide if I can live with only temp-rooting the device.
I am not going to use it on T-Mobile, I'm in Venezuela and will use it with my carrier here, so the unnecessary bloat will be even more of an annoyance, because on top of it sucking, it won't even work; so it would be important for me to at least root to get rid of it.
I'm sorry if my questions are too expansive, I picked up bits and pieces of information in other posts, but none of them answered these questions clearly. Thank you very much to all those who can help me answer them.
Click to expand...
Click to collapse
I don't know where to start with all of your questions but I will do my best.
The difference between S-OFF and Unlocked bootloader is that with S-OFF you can flash anything including a radio and supposedly it would give us the ability to update the kernel by recovery. With an unlocked bootloader we cannot update the radio or kernel but can pretty much change everything else. An unlocked bootloader is required to root your device and remove all the bloat that you don't like. You can temp root the device to remove that bloatware however they will re-appear after a reboot. It has been under some debate if in fact using the unlock_code.bin file provided by htcdev is going to void your warranty if your device would require servicing. If it's vital to know that information then call HTC to inquire before unlocking.
Regarding CM9, it is possible but slightly inconvenient since CM9 would almost certainly require a different kernel and since we cannot flash kernels by recovery it would have to be done in a very certain order. Is it currently in the works? To my understanding, yes! Any idea when you can see it as a download here in the forums? Not at this time. Check back daily because things change frequently!
Thanks a lot for your response, Binary. I see you have an Amaze and have indeed unlocked its bootloader, so I guess the real question would be: when and if s-off is achieved, will you be able to do it even though you've already unlocked the bootloader with the .bin file?
Warranty would be terribly hard for me to take advantage of anyways after the initial check. If I don't RMA the unit, then I'm pretty much gambling on the fact that it will work well no matter what, since sending it back to the US from Venezuela would be a major PITA, so I don't really care much about voiding it.
el_ochito said:
Thanks a lot for your response, Binary. I see you have an Amaze and have indeed unlocked its bootloader, so I guess the real question would be: when and if s-off is achieved, will you be able to do it even though you've already unlocked the bootloader with the .bin file?
Warranty would be terribly hard for me to take advantage of anyways after the initial check. If I don't RMA the unit, then I'm pretty much gambling on the fact that it will work well no matter what, since sending it back to the US from Venezuela would be a major PITA, so I don't really care much about voiding it.
Click to expand...
Click to collapse
There is no reason that having an unlocked bootloader will interfere with being able to obtain s-off in the future because we can always relock the bootloader when (or if) it comes down to it.
Binary100100 said:
I don't know where to start with all of your questions but I will do my best.
The difference between S-OFF and Unlocked bootloader is that with S-OFF you can flash anything including a radio and supposedly it would give us the ability to update the kernel by recovery. With an unlocked bootloader we cannot update the radio or kernel but can pretty much change everything else. An unlocked bootloader is required to root your device and remove all the bloat that you don't like. You can temp root the device to remove that bloatware however they will re-appear after a reboot. It has been under some debate if in fact using the unlock_code.bin file provided by htcdev is going to void your warranty if your device would require servicing. If it's vital to know that information then call HTC to inquire before unlocking.
Regarding CM9, it is possible but slightly inconvenient since CM9 would almost certainly require a different kernel and since we cannot flash kernels by recovery it would have to be done in a very certain order. Is it currently in the works? To my understanding, yes! Any idea when you can see it as a download here in the forums? Not at this time. Check back daily because things change frequently!
Click to expand...
Click to collapse
Your words helped me a lot. I was thinking about the diff between s-on/off and lock.unlock bootloader for long. Thanks so much
I'm in over my head. Very much so. I've been flashing for years and a friend of mine has handed off his ATT atrix after making some big mistakes. He was rooted and somehow/for some reason deleted CWM and the new OTA ended up getting his device to this point (photo in attachment). I'm not very familiar with RSD, as luckily I've never found myself in a predicament like this. I've been all over this forum, the pudding/fruitcake/fastboot threads, and although I've seen the 'Don't SBF' warnings everywhere, I don't know what else to do, and I don't want to take any more action without knowing the consequences. I think this is a pretty unique situation. I'm asking for a detailed instruction on getting this phone restored (I've seen some say it's not possible, but other places saying a guy figured out a way). I need the specific links, and specific steps (as I've had much issue with broken links). I have access to ubuntu and windows so whichever is more simple is fine. I could try my luck but I'd rather reach out to someone who knows before hand.
*As far as I know the battery is high enough to flash (it's sitting with the battery pulled for now)
I don't care about retaining root, having a custom recovery or anything of that nature. I just need this phone to be in working condition again. Upon that happening we'd be happy to throw 20$ (via paypal) to whoever can get us there. Thanks in advance.
maybe this will help
I was rescued previously by the nice folks on atrixforums. you can reference this link http://www.atrixforums.com/forum/rescue-squad/6164-se-flash-olympus-help.html
Should be able to flash Romracers CWM via fastboot > http://forum.xda-developers.com/showthread.php?t=1204500 then get back into recovery. You can also flash a Fruitcake in fastboot mode > http://forum.xda-developers.com/showthread.php?t=1163009.
From your picture it looks like the bootloader was unlocked before, and maybe need to issue the unlock command again. This thread may help you > http://forum.xda-developers.com/showthread.php?t=1182871
Looks like ya just need to do the fastboot oem unlock commands to unlock the BL and finish the process....
thanks
Thanks for the quick responses guys, I'm off to work now but I'll try this tonight. Once again thank you.
I had the exact same problem, same thing happened with my phone, don't worry, you're okay!
First, are you sure that's the right SBF? I would confirm whether it is because that's the easiest way. Next, do what others have said and try to flash a recovery on it, from there on you can just unlock the phone and flash any rom.
Hope you get it sorted out.
G-Man. said:
Looks like ya just need to do the fastboot oem unlock commands to unlock the BL and finish the process....
Click to expand...
Click to collapse
brandonmangan - based on your screenshot you posted, you need to do the fastboot oem unlock commands, you flashed the pudding sbf with the unlockable bootloader. Get the fastboot drivers installed and then run the commands as they are listed in the pudding thread. Thats ALL you need to do.
This is my primary concern.
Quote from toastcfh in the one x forum TWRP thread. ......
no, USB mount does not work in recovery. It appears to be locked out in recovery mode. the workarounds to get it working are one of two things.
(1) fastboot boot awesomeRecovery.img (this works because fastboot then boots recovery on the boot/temporary partition. So the you're not actually in recovery mode
(2) Offmode (this works because again you're again not technically in recovery mode. It uses the recovery ramdisk, kernel, and binaries but its still not technically recovery.
On that note I've seen suggestions that it's possibly a recovery issue with cwm and twrp. Unfortunately it doesn't appear to be the case. If it were then in CWM u wouldn't have usb when u fastboot boot the recovery or in offmode (fair assumption since both these options use the same kernel, ramdisk and binaries as recovery?). Can it be fix? Not that i know of. It looks to me like a total radio or bootloader lockout from using USB in recovery. Which means on a radio or bootloader level USB is disabled in recovery mode.
On that note I think we should raise the point to HTC that this locking down of the device does not suite our needs.Key points of fail would be as follows.
(1) Can NOT flash the boot partition from recovery. I've personally contacted HTC on this numerous times and they seem to just not care. Responding with "It's a security issue" and so forth. I would love to know how this is a security issue of any sort. Every other Android device has this ability except HTC devices since they started the HTC unlock ordeal. It's utter fail IMHO and HTC should listen to our needs .
(2) Can NOT flash recovery or boot partitions from system. This issue is NOT a deal breaker and isn't so bad when it comes down to the nitty gritty. But since the issue above exists, flashing with applications like htc dumlock and such were our only options. These work around apps cant be used to flash now because of the lockpout from system and it wouldn't be such an issue if HTC didnt lock us out in recovery from flashing boot.
(3) Can NOT flash P*IMG.zips in hboot/bootloader anymore. For the unlocked device running a custom firmware this is a must. Specially when radio updates and such are needed from the OEM. We seen a big use of this on the Sensation when HTC updated the device from Gingerbread to Ice Cream Sandwich. The update required new hboots, radios, and partitioning to actually use. So in that instead of having to flash a RUU Which didn't exist the only choice was to flash a custom P*IMG.zip that included all the radios and images need to run the builds. At this point we can't update those image/partitions without flashing an RUU. This makes no since and doesn't seem to do anything but make things more difficult on the unlocker to customize and modify their device.
(4) If all the conditions above HAVE to exist. Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
(5) WHAT WAS THE POINT OF HTC UNLOCK? I was to reach out and except us as a community. It was to keep us from having to exploit their firmware and look for holes to gain control of a device we rightfully own. WHAT DID HTC UNLOCK DO? It unlocked the devices at first and with each new revision of the unlock it gets more locked down and harder for us to use it as intended. WHAT DOES THAT LEAD TO? It leads to us hoping someone will take the time out of their life and exploit HTC's firmware so we can have access and control of our devices. I mean, it's bad when u have people poking a device with a paperclip to get a device unlocked to avoid a official unlock.
Bottom line; I'm personally fed up with HTC's unlock. It's absolute crap! It does not serve the purpose it was intended and only makes things harder then they were before. As a devoted HTC customer it has me questioning if my next device will be an HTC. With all the other options that would allow me to spend less time trying to gain proper access to my device and more time actually having fun with it, why choose HTC? Everyone else is shying away for these same issues. Everyone with an HTC unlocked device waits for someone to exploit HTC's firmware and give them a proper unlock. Why not just choose a device without the locked down/unlock instead? IDK but HTC needs to step up and listen to us. Every HTC forum with an HTC Unlock is screaming for these issues to be fixed.
My call to HTC is to fix these issue and/or give us proper documentation on flashing firmware to our devices via custom recoveries. The boot flashing lockout is dumb, pointless, and in NO WAY a security threat AT ALL and is nothing more then a CRAP RESPONSE to something that they sould be working to correct, instead of ignoring. In the end its hurting HTC's relations with developers and is ultimately doing the opposite of what it's original intent.
HTC, PLEASE READ AND LISTEN!!!11ONEone
To everyone else, SPREAD THE WORD!!!ONEone
Click to expand...
Click to collapse
This comes straight from toastcfh himself.
I think that if we all send an email to customer support and follow up something may come of this. Copy what toastchf said into an email send it everyone and then follow up until you get someone who cares. Then tell them about all those people who aren't doing this because they are fed up and switching to Samsung devices.
Sent from my EVO 3D S using XDA
you should edit your post to put his Quote in actual [ QUOTE=toastcfh;25407373]....(quoted post text goes here)...[/QUOTE ] tags(just remove the "space" between the first and last bracket...like I have done so below.
toastcfh said:
no, USB mount does not work in recovery. It appears to be locked out in recovery mode. the workarounds to get it working are one of two things.
(1) fastboot boot awesomeRecovery.img (this works because fastboot then boots recovery on the boot/temporary partition. So the you're not actually in recovery mode
(2) Offmode (this works because again you're again not technically in recovery mode. It uses the recovery ramdisk, kernel, and binaries but its still not technically recovery.
On that note I've seen suggestions that it's possibly a recovery issue with cwm and twrp. Unfortunately it doesn't appear to be the case. If it were then in CWM u wouldn't have usb when u fastboot boot the recovery or in offmode (fair assumption since both these options use the same kernel, ramdisk and binaries as recovery?). Can it be fix? Not that i know of. It looks to me like a total radio or bootloader lockout from using USB in recovery. Which means on a radio or bootloader level USB is disabled in recovery mode.
On that note I think we should raise the point to HTC that this locking down of the device does not suite our needs.Key points of fail would be as follows.
(1) Can NOT flash the boot partition from recovery. I've personally contacted HTC on this numerous times and they seem to just not care. Responding with "It's a security issue" and so forth. I would love to know how this is a security issue of any sort. Every other Android device has this ability except HTC devices since they started the HTC unlock ordeal. It's utter fail IMHO and HTC should listen to our needs .
(2) Can NOT flash recovery or boot partitions from system. This issue is NOT a deal breaker and isn't so bad when it comes down to the nitty gritty. But since the issue above exists, flashing with applications like htc dumlock and such were our only options. These work around apps cant be used to flash now because of the lockpout from system and it wouldn't be such an issue if HTC didnt lock us out in recovery from flashing boot.
(3) Can NOT flash P*IMG.zips in hboot/bootloader anymore. For the unlocked device running a custom firmware this is a must. Specially when radio updates and such are needed from the OEM. We seen a big use of this on the Sensation when HTC updated the device from Gingerbread to Ice Cream Sandwich. The update required new hboots, radios, and partitioning to actually use. So in that instead of having to flash a RUU Which didn't exist the only choice was to flash a custom P*IMG.zip that included all the radios and images need to run the builds. At this point we can't update those image/partitions without flashing an RUU. This makes no since and doesn't seem to do anything but make things more difficult on the unlocker to customize and modify their device.
(4) If all the conditions above HAVE to exist. Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
(5) WHAT WAS THE POINT OF HTC UNLOCK? It was to reach out and accept us as a community. It was to keep us from having to exploit their firmware and look for holes to gain control of a device we rightfully own. WHAT DID HTC UNLOCK DO? It unlocked the devices at first and with each new revision of the unlock it gets more locked down and harder for us to use it as intended. WHAT DOES THAT LEAD TO? It leads to us hoping someone will take the time out of their life and exploit HTC's firmware so we can have access and control of our devices. I mean, it's bad when u have people poking a device with a paperclip to get a device unlocked to avoid a official unlock.
Bottom line; I'm personally fed up with HTC's unlock. It's absolute crap! It does not serve the purpose it was intended and only makes things harder then they were before. As a devoted HTC customer it has me questioning if my next device will be an HTC. With all the other options that would allow me to spend less time trying to gain proper access to my device and more time actually having fun with it, why choose HTC? Everyone else is shying away for these same issues. Everyone with an HTC unlocked device waits for someone to exploit HTC's firmware and give them a proper unlock. Why not just choose a device without the locked down/unlock instead? IDK but HTC needs to step up and listen to us. Every HTC forum with an HTC Unlock is screaming for these issues to be fixed.
My call to HTC is to fix these issue and/or give us proper documentation on flashing firmware to our devices via custom recoveries. The boot flashing lockout is dumb, pointless, and in NO WAY a security threat AT ALL and is nothing more then a CRAP RESPONSE to something that they sould be working to correct, instead of ignoring. In the end its hurting HTC's relations with developers and is ultimately doing the opposite of what it's original intent.
HTC, PLEASE READ AND LISTEN!!!11ONEone
To everyone else, SPREAD THE WORD!!!ONEone
This is the future of HTC unlock and each new device it gets worse. Maybe HTC will listen and address these issues, then again maybe we will just need to find another OEM that supports us and does listen.
Click to expand...
Click to collapse
I read this last night. The man is absolutely correct. I am actually going to write a similar one about Asus with Transformer Prime unlock. Reading his post inspired me. Lol. All his points are extremely valid. It seems that there are manufactures who want to lock people out, makes us wait for them for updates and fight the dev community anyway possible. Then, it seems others are the exact opposite. Other manufacturers would rather the devs here fix it and they don't hear from us. The latter of the two is probably smarter. There are issues with every phone but the ones who are more dev friendly don't catch as much crap for it because at least they are fully open and the devs here can try to fix it.
Sent from my Anthrax infected 3D!
If I've helped you in any way... hit the "Thanks" button.
wait so you "thank" me but dont take the little sec to edit your post and fix it? lol
sgt. slaughter said:
wait so you "thank" me but dont take the little sec to edit your post and fix it? lol
Click to expand...
Click to collapse
Lol s off can be good if you know what your doing . But it can be a curse for those that have no idea . Such as you can screw somethin up .
I think htc isn't bad they just don't want a bunch of folks brickin and frying the CPU on a phone and sending it in sayin it was htc fault .. Tellin em fix it when it was a noobs fault.
Sent from my PG86100 using xda premium
sgt. slaughter said:
wait so you "thank" me but dont take the little sec to edit your post and fix it? lol
Click to expand...
Click to collapse
You're a mod, fix it yourself...
Vdubtx said:
You're a mod, fix it yourself...
Click to expand...
Click to collapse
That's not a mods job. Lol..
Sent from my PG86100 using xda premium
Vdubtx said:
You're a mod, fix it yourself...
Click to expand...
Click to collapse
Not Mod of this forum u dork. lol
sgt. slaughter said:
Not Mod of this forum u dork. lol
Click to expand...
Click to collapse
Lol Where is a donky smiley .
Sent from my PG86100 using xda premium
Pretty much the title sums it up
This is nothing related to unlimited i.o. guys at all first and foremost
If you are willing to risk potentially bricking your inc 4g, in an attempt for either tricking htc dev unlock to accept the inc 4g, or s-off, then please pm me.
Requirements:
willing to have a completely unrecoverable inc 4g that you wont try insurance fraud on to recover
proficient with adb/fastboot commands
completely locked and unrooted
this is not me attempting this by the way (the unlock) :silly:
Thanks for this man, I really don't want to see this phone die. It deserves so much more.
I pmed you nits but I don't think he's on. I'm on a 96 till Wednesday so I can try stuff out. I don't really care if I brick this I just need help with adb stuff
Linch89 said:
I pmed you nits but I don't think he's on. I'm on a 96 till Wednesday so I can try stuff out. I don't really care if I brick this I just need help with adb stuff
Click to expand...
Click to collapse
this should help http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
nitsuj17 said:
Pretty much the title sums it up
This is nothing related to unlimited i.o. guys at all first and foremost
If you are willing to risk potentially bricking your inc 4g, in an attempt for either tricking htc dev unlock to accept the inc 4g, or s-off, then please pm me.
Requirements:
willing to have a completely unrecoverable inc 4g that you wont try insurance fraud on to recover
proficient with adb/fastboot commands
completely locked and unrooted
this is not me attempting this by the way (the unlock) :silly:
Click to expand...
Click to collapse
OK so I'm a pretty good candidate for this:
I have a DINC4G. I don't have phone insurance so won't try to get a replacement. I am very comfortable on the command-line, and have adb working and am familiar with fastboot basics. I am a software dev with RHEL and Ubuntu server admin background. I have a completely locked and unrooted phone. I'm just a bit scared of having a paperweight, though.
I REALLY want to learn more about this, but I'm also a cautious person (having maintained production servers for years). I would like to help, but first need some more understanding of what it is we'll be doing. I'm assuming we'd be changing the bootloader partition, maybe changing a hex value or a few, to turn off security to gain s-off or possibly fake HTCDev unlock.
I've already temprooted and tried remount rw and the symlink/debugfs trick. Personally I'd prefer to continue attempting root via the OS or maybe flashing a custom recovery. Any changes we would make to /system or the recovery partition can be reverted via RUU... way safer IMHO. However, I'm thinking NAND lock is gonna mean our only chance is altering the bootloader (dev unlock or s-off) to gain NAND write.
So, I would like to help, though cautiously. I'd like to perform any changes myself, and might be hesitant about some of them once we delve into the bootloader side of things. I'm totally willing to attempt to exploit the system or recovery partition though. Let me know and we can proceed (with caution).
I am looking at getting this phone. Seeing how it is without even simple CWM (How does this happen on XDA?!) I'll go ahead and build a recovery (and maybe a couple ROM's .
Here is what I need:
Latest Recovery Image
Latest System Image
Latest Boot Image
Latest graphics.c
Willing testers are needed as well.
When applicable:
Root your device
Install Flashify
Download Recovery image
Flash via Flashify.
Done. Custom recovery w/o bootloader unlock
I'll be happy to test out. Just let me know what I need to get ya and where to get it.
Kwongger said:
I am looking at getting this phone. Seeing how it is without even simple CWM (How does this happen on XDA?!) I'll go ahead and build a recovery (and maybe a couple ROM's .
Here is what I need:
Latest Recovery Image
Latest System Image
Latest Boot Image
Latest graphics.c
Willing testers are needed as well.
When applicable:
Root your device
Install Flashify
Download Recovery image
Flash via Flashify.
Done. Custom recovery w/o bootloader unlock
Click to expand...
Click to collapse
I knew it was here somewhere. http://forum.xda-developers.com/showthread.php?p=54945442
I don't know much about Flashify, but I didn't think you could flash anything without bootloader unlock/ Loki.
Can you enlighten me?
Does no good w/o unlocked bootloader, hence why there is nothing available thus far for it.
otherwise myself or others would have already done something.
PlayfulGod said:
Does no good w/o unlocked bootloader, hence why there is nothing available thus far for it.
otherwise myself or others would have already done something.
Click to expand...
Click to collapse
Flashify does not need an unlocked bootloader. It works great on my HTC One Max, SHIELD Portable, and SHIELD Tablet w/o bootloader unlock. Unlocking the bootloader is a requirement of the past.
Kwongger said:
Flashify does not need an unlocked bootloader. It works great on my HTC One Max, SHIELD Portable, and SHIELD Tablet w/o bootloader unlock. Unlocking the bootloader is a requirement of the past.
Click to expand...
Click to collapse
No offense, but dont delude yourself.
Without a viable way to backup and restore, one is just asking for trouble flashing things.
And w/o a unlocked bootloader you cannot flash recovery, esp on this device.
Kwongger said:
Flashify does not need an unlocked bootloader. It works great on my HTC One Max, SHIELD Portable, and SHIELD Tablet w/o bootloader unlock. Unlocking the bootloader is a requirement of the past.
Click to expand...
Click to collapse
You are wrong.
Without even addressing the other models, HTC One Max used emmc based write protection. You CANT write to the recovery patition without using the official unlock, or SunShine/Firewater unlocks.
On top of that, even if you managed to write to the partition, say some how you had some exploit that dropped write protection, you still have to unlock it (or s-off, which is an unlock) because if you didnt hboot would fail the validation of the recovery partition.
jcase said:
You are wrong.
Without even addressing the other models, HTC One Max used emmc based write protection. You CANT write to the recovery patition without using the official unlock, or SunShine/Firewater unlocks.
On top of that, even if you managed to write to the partition, say some how you had some exploit that dropped write protection, you still have to unlock it (or s-off, which is an unlock) because if you didnt hboot would fail the validation of the recovery partition.
Click to expand...
Click to collapse
forgot to add the s-off part! Thanks for calling me on that one. I do so much to these damn things that I forget how I've mutilated their software xD
Kwongger said:
forgot to add the s-off part! Thanks for calling me on that one. I do so much to these damn things that I forget how I've mutilated their software xD
Click to expand...
Click to collapse
LG G3 should fail for a similar reason, the signature checks. LG does not have an "s-off/unlock" to disable them. TMobile obviously isn't checking but AT&T is, I believe Verizon and Sprint do as well.
PlayfulGod said:
No offense, but dont delude yourself.
Without a viable way to backup and restore, one is just asking for trouble flashing things.
And w/o a unlocked bootloader you cannot flash recovery, esp on this device.
Click to expand...
Click to collapse
lgg3root.com
Am I hallucinating while this guy flashes TWRP via Flashify? (I wouldn't put it past me xD) Or does T-mo magically have an unlocked bootloader? If the do, I'll be pissed with Sprint/LG haha.
jcase said:
You are wrong.
Without even addressing the other models, HTC One Max used emmc based write protection. You CANT write to the recovery patition without using the official unlock, or SunShine/Firewater unlocks.
On top of that, even if you managed to write to the partition, say some how you had some exploit that dropped write protection, you still have to unlock it (or s-off, which is an unlock) because if you didnt hboot would fail the validation of the recovery partition.
Click to expand...
Click to collapse
PlayfulGod said:
No offense, but dont delude yourself.
Without a viable way to backup and restore, one is just asking for trouble flashing things.
And w/o a unlocked bootloader you cannot flash recovery, esp on this device.
Click to expand...
Click to collapse
To both of you:
People like you are the reason that I've taken a long break from XDA. The drama and attacks are senseless and absurd. I come here with FREE software, and you criticize and correct me on things even when you're wrong. You punks have no fricking idea about what I know or can do, and you're willing to cut your nose off to spite your face. I have a build booting for ATT and Sprint of TWRP... I am just going to keep it private. You fools don't deserve it. XDA is going to hell, and I'm getting off of the crazy train now.
Mods, please close this thread.
Kwongger said:
lgg3root.com
Am I hallucinating while this guy flashes TWRP via Flashify? (I wouldn't put it past me xD) Or does T-mo magically have an unlocked bootloader? If the do, I'll be pissed with Sprint/LG haha.
Click to expand...
Click to collapse
the tmo g3 (d851) comes with a unlocked bootloader.
PlayfulGod said:
the tmo g3 (d851) comes with a unlocked bootloader.
Click to expand...
Click to collapse
Those bastards. Looks like I'm leaving sprint too ;D
Kwongger said:
To both of you:
People like you are the reason that I've taken a long break from XDA. The drama and attacks are senseless and absurd. I come here with FREE software, and you criticize and correct me on things even when you're wrong. You punks have no fricking idea about what I know or can do, and you're willing to cut your nose off to spite your face. I have a build booting for ATT and Sprint of TWRP... I am just going to keep it private. You fools don't deserve it. XDA is going to hell, and I'm getting off of the crazy train now.
Mods, please close this thread.
Click to expand...
Click to collapse
I didn't insult, attack or anything, I provided factual information to you in an area I am knowledgeable. Yet you came on and just called me a p*nk.
I don't need anything from you, I was trying to help you. I too have a custom images booting from emmc (not from fastboot) on AT&T, this is how I know what i needed to make it happen. My track record more than speaks for itself.
Mod here, dont worry I'll take care of it.
DELETE
Didn't get to the end of the thread.
yup
Kwongger said:
lgg3root.com
Click to expand...
Click to collapse
Neat, a site talking about the tools auto, playful, cube and I wrote.
jcase said:
Mod here, dont worry I'll take care of it.
Click to expand...
Click to collapse
Ah, that's why. I understand why you were so rude.
Kwongger said:
To both of you:
People like you are the reason that I've taken a long break from XDA. The drama and attacks are senseless and absurd. I come here with FREE software, and you criticize and correct me on things even when you're wrong. You punks have no fricking idea about what I know or can do, and you're willing to cut your nose off to spite your face. I have a build booting for ATT and Sprint of TWRP... I am just going to keep it private. You fools don't deserve it. XDA is going to hell, and I'm getting off of the crazy train now.
Mods, please close this thread.
Click to expand...
Click to collapse
I'm sorry... did you just call these both "punks" while at the same time talking about drama and attacks? BWahaha - Pot, meet Mr. Kettle.
This whole thing you're trying to do puts everyone who chooses to use this process in danger of fetching up their device... And that's great you have a build booting - go you. But FFS don't go all "I AM THE GREATEST!" here when you're the one ignoring actually good advice from at least one professional in the industry who has done more for the community as a whole than your little piece of work. Please, keep your work to yourself, and just use it yourself without putting everyone else's devices at risk. Oh - and it seems your long break wasn't long enough - maybe consider extending it if it gets you this worked up over very helpful information.
EDIT: Closing at the request of the very stressed out user.