[Q&A] Team Infernal FakeCid AUTOMATIC bootloader unlock - Verizon HTC Droid Incredible 4G LTE

Q&A for Team Infernal FakeCid AUTOMATIC bootloader unlock
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Team Infernal FakeCid AUTOMATIC bootloader unlock. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

FakeCID Automatic Unlock Failed
Here's a screenshot. I don't know if the failure to write the files to the SD card caused the failure. Did I miss anything on setting this up? I exited the script rather than do a factory reset. I saw the note about doing a factory reset and then trying again, but if this is related to the file write failure, I'd rather not reset the phone and have to set it all back up again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I assume you're working on getting s-off. Working from that I expect you have the most recent update from almost a year ago. If you do then this thread should get you to where you want to go.
crokett said:
Here's a screenshot. I don't know if the failure to write the files to the SD card caused the failure. Did I miss anything on setting this up? I exited the script rather than do a factory reset.
Click to expand...
Click to collapse

No. I am working on unlocking the bootloader so I can install a custom recovery. Hence the thread title. Is S-Off a requirement to unlocking the boot loader? I didn't see anything that says it is.

S-off makes installing ROMs easier because you don't need to extract the boot.IMG each time. S-off gives you more options but opens you up to a little more risk of you mess up. Read a bit more on the differences between an unlocked bootloader and s-off. If I can find a few links I'll as then tomorrow to help you out.
Sent from my Nexus 7 using XDA Free mobile app

Thanks. I have done some reading and I am reasonably familiar with S-OFF. I think my problem is that I need to factory reset the phone before I try the bootloader unlock. The HTCDev site doesn't support this phone for a bootloader unlock. I'm not quite ready to do a factory reset yet so I will wait a bit longer.

Installing a custom ROM will require a factory reset, so when you're ready for that go for it. An app like this https://play.google.com/store/apps/details?id=com.koushikdutta.backup makes the transition much easier.

Ok I believe I know why the unlock is failing. My sdcard for some reason is getting mounted as read only, or at least the script thinks it is.
This is from the script:
Code:
db shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4"
and line that tries to dump the mcblk0p4 file to the sdcard to pull it to the PC fails. I thought that the error I was getting was related to backups. this page:
http://forum.xda-developers.com/showthread.php?t=1986346
says that you need to remove mmcblk0p4 from the directory if you run the script multiple times.
So it appears that after the 'adb restore fakebackup.ab' command is run, at least on this phone the sdcard is mounted as read-only. Is there a way around this? can adb push/pull the file from phone storage directly to and from my PC if I want to edit the file manually?
Or, does anybody have a backed up modified file for this phone that they can send me? I am stuck at dumping the file to the sdcard so that I can modify it, but I think I can push a modified file to the phone so that I can then go to HTCDev to get it unlocked

An update. I followed the manual steps and was able to get the file with the CID in it off the phone. I edited it as per the directions, then pushed it back to the phone and used dd to push it back to /dev/block however after I rebooted the phone and did the readcid command, it still has the stock Verizon CID. Any help?

One last update, I tried both the manual method and the automatied script after factory resetting the phone. That did not work either. Any suggestions? I'd really like to get this phone rooted if I can. If it helps or matters, my phone device type starts with an FA, not the HT that the script calls out.
The script works up to the point that I run the dd command to write the modified file back to /block. The dd command works, but checking the OEMCID it is still the Verizon CID. Do I need to S_OFF the phone first? I didn't think that was related to this.

crokett said:
One last update, I tried both the manual method and the automatied script after factory resetting the phone. That did not work either. Any suggestions? I'd really like to get this phone rooted if I can. If it helps or matters, my phone device type starts with an FA, not the HT that the script calls out.
The script works up to the point that I run the dd command to write the modified file back to /block. The dd command works, but checking the OEMCID it is still the Verizon CID. Do I need to S_OFF the phone first? I didn't think that was related to this.
Click to expand...
Click to collapse
After reading the thread, I am not sure why you wouldn't just go with s-off instead of only unlocking the bootloader. Yes, there's more risk in having an s-off phone, but it does make life much easier overall. However, If you are able to s-off the phone, you're done - no need to further work on unlocking the bootloader because the phone is fully unlocked (and it will stay that way unless you explicitly lock it). It also seems as though the s-off methods are now more tried and true for this phone versus just unlocking the bootloader.
Instead of continuing to struggle to just unlock the bootloader, you may try just going full out s-off. Just back up what you can - contacts to Google Contacts, USB cable to pull off your files/music/whatever to your PC, etc. then go for it. Make sure you are using the s-off method that matches your phone's current version.
Good luck!

junkmail9 said:
After reading the thread, I am not sure why you wouldn't just go with s-off instead of only unlocking the bootloader. Yes, there's more risk in having an s-off phone, but it does make life much easier overall. However, If you are able to s-off the phone, you're done - no need to further work on unlocking the bootloader because the phone is fully unlocked (and it will stay that way unless you explicitly lock it). It also seems as though the s-off methods are now more tried and true for this phone versus just unlocking the bootloader.
Instead of continuing to struggle to just unlock the bootloader, you may try just going full out s-off. Just back up what you can - contacts to Google Contacts, USB cable to pull off your files/music/whatever to your PC, etc. then go for it. Make sure you are using the s-off method that matches your phone's current version.
Good luck!
Click to expand...
Click to collapse
thanks for confirming that. I misunderstood what S_OFF did, else I might have done it sooner. I did not realize that it also unlocks the phone as a whole. I thought it gave access to the radios, etc which I wasn't necessarily interested in.

crokett said:
thanks for confirming that. I misunderstood what S_OFF did, else I might have done it sooner. I did not realize that it also unlocks the phone as a whole. I thought it gave access to the radios, etc which I wasn't necessarily interested in.
Click to expand...
Click to collapse
Yep. S-Off is the full unlock. Once achieved, you can do whatever you want to the phone, including updating the radio (be very careful!), install a custom recovery, install a new kernel (from the SD card), install full ROMs without needing to push anything separately, mess with partitions, etc. IMHO it is the best way to go, but just be careful after achieving s-off, one wrong keystroke or click while connected to your PC, you can very easily make yourself an expensive paper weight.
Also, if you are installing custom ROMs, on this phone it does make a difference which recovery is installed. ViperLTE will not install properly with a CWM variant, but installs just fine with TWRP.

Success!!! many thanks to wmuflyer for pointing me to rumrunner for S_OFF. the phone is now S_OFF and the bootloader is unlocked. thanks for all the suggestions.

Congratulations. Now the fun begins. And remember you can always use the thanks button.
Sent from my Nexus 7 using XDA Free mobile app

Hi everyone, my phone is s-off but locked bootloader how can I unlock it?

Related

Help!! 0x1000 error but retained RSD protocol support

I update to 2.3.4 through android recovery...but i did something wrong doing an sbf through RSD lite. But now i have this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IDK if i can flash anything else...can somebody help me...
well you have the fastboot option, did you try to fastboot a good IMG?
i haven't tried anything...how can i fastboot an IMG?
darth_twins said:
i haven't tried anything...how can i fastboot an IMG?
Click to expand...
Click to collapse
go to the dev forum and learn how to install via fastboot. you should be able to download the .img files for a specific OS, and then via your computer and USB flash it onto your phone.
http://forum.xda-developers.com/showthread.php?t=1163342
p.s. some "just checking" questions:
1. did you unlock your bootloader?
2. do you have tenfar's most recent CWM installed?
3. how far into the 2.3.4 install did you get, before it failed, and what version of SBF did you try to flash back to?
ok...
1. i never unlock the bootloader
2. i don't have a CMW installed
3 i installed sucessfully the 2.3.4 but then tried to unlock the bootloader ...well that's how i get in this mess
in that case, you probably should have read this thread then (stickied at the top of the dev forum):
http://forum.xda-developers.com/showthread.php?t=1160408
you've got a hard brick... hard lesson to learn. next time make sure you're more familiar with what you're doing with the device and all the risks and solutions. sorry
My understanding of hard brick is that you wouldn't have rsd or fastboot access. Based on the stickie threads that could happen after trying to flash a full sbf only, not the pudding one. I think you have a soft brick and there are lots of threads on how to recover from that, just search around. You should be able to use fastboot from here to flash some new boot and system images. Good luck.
Edit: whatever you do, do not rsd a full sbf from where you are, which will cause a hard brick.
Sent from my MB860 using XDA App
You can rsd a full image if it has pudding included.
Sent from my MB860 using XDA Premium App
Use rsd to flash this sbf it should work.
http://www.multiupload.com/4K3C9VS9IJ
Sent from my MB860 using XDA Premium App
Am I understanding that people are getting this error just trying to use the pudding to unlock the bootloader?? I thought it was still safe to do, even if you did already use the "official" OTA update through android recovery.
Its getting so confusing around here.
Sent from my MB860 using XDA App
One thing before we begin, unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything.
Here is what I did to unlock my bootloader and gain root.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/show....php?t=1136261 Original Post about pudding.
DO NOT FLASH ANY SBF UNTILL YOU COMPLETE THE ENTIRE STEP OR YOU WILL HARD BRICK aka phone will be a paper weight.
Once you flash pudding phone won't boot instead will go to a text only 14 option screen and say something like, No OS found, failed to boot 0x1000. Here is a picture for people who are freaking out. http://forum.xda-developers.com/attachment.php?attachmentid=651901&d=1310422138 .Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/show....php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread.
http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone afterwards.
Jnewell05 said:
One thing before we begin, unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything.
Here is what I did to unlock my bootloader and gain root.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/show....php?t=1136261 Original Post about pudding.
DO NOT FLASH ANY SBF UNTILL YOU COMPLETE THE ENTIRE STEP OR YOU WILL HARD BRICK aka phone will be a paper weight.
Once you flash pudding phone won't boot instead will go to a text only 14 option screen and say something like, No OS found, failed to boot 0x1000. Here is a picture for people who are freaking out. http://forum.xda-developers.com/attachment.php?attachmentid=651901&d=1310422138 .Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/show....php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread.
http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone afterwards.
Click to expand...
Click to collapse
Thanks for clearing that up, I thought we could still do it.
Sent from my MB860 using XDA App
Jnewell05 said:
One thing before we begin, unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything.
Here is what I did to unlock my bootloader and gain root.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/show....php?t=1136261 Original Post about pudding.
DO NOT FLASH ANY SBF UNTILL YOU COMPLETE THE ENTIRE STEP OR YOU WILL HARD BRICK aka phone will be a paper weight.
Once you flash pudding phone won't boot instead will go to a text only 14 option screen and say something like, No OS found, failed to boot 0x1000. Here is a picture for people who are freaking out. http://forum.xda-developers.com/attachment.php?attachmentid=651901&d=1310422138 .Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/show....php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread.
http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone afterwards.
Click to expand...
Click to collapse
I have the same error "Failed to boot 0x1000" but i don't have the available modes menu. the phone shows this message for about 3 seconds and then shuts off ... any help will be appreciated.
Just a note this happened after me installing the new 4.5.9.1
hakemcpu said:
Just a note this happened after me installing the new 4.5.9.1
Click to expand...
Click to collapse
And then what did you do?
mysticdrew said:
And then what did you do?
Click to expand...
Click to collapse
I then tried to support Arabic for the GB using this link
http://forum.xda-developers.com/showthread.php?t=1062761
when copying "libandroid_runtime.so" and "libicuuc-arabic.so" the phone turned off and when i tried to open it, it stayed at the motorola sign.
at that time i was able to to see the boot menu when i press and hold the volume down, I tried to restore the system the way it was before GB, some posts stated that downgrading to 4.1.83 will hard brick the phone, so i tried to install 4.1.57 Stock rom and Now i am stuck with this error
If anybody could help because it is not possible for me to return it to the US to get fixed and then get it back here.
Any help is appreciated.
hakemcpu said:
I then tried to support Arabic for the GB using this link
http://forum.xda-developers.com/showthread.php?t=1062761
when copying "libandroid_runtime.so" and "libicuuc-arabic.so" the phone turned off and when i tried to open it, it stayed at the motorola sign.
at that time i was able to to see the boot menu when i press and hold the volume down, tried to install 4.1.5.2 Stock rom and Now i am stuck with this error
If anybody could help because it is not possible for me to return it to the US to get fixed and then get it back here.
Any help is appreciated.
Click to expand...
Click to collapse
how did you try to install the 4.1.5.2 stock rom? sbf RSD? If so, then you're likely hard bricked with no chance of recovery. Sorry. If you can still get into fastboot mode then you have a chance.
mysticdrew said:
how did you try to install the 4.1.5.2 stock rom? sbf RSD? If so, then you're likely hard bricked with no chance of recovery. Sorry. If you can still get into fastboot mode then you have a chance.
Click to expand...
Click to collapse
yes i used RSD mode
mysticdrew said:
how did you try to install the 4.1.5.2 stock rom? sbf RSD? If so, then you're likely hard bricked with no chance of recovery. Sorry. If you can still get into fastboot mode then you have a chance.
Click to expand...
Click to collapse
isn't there any other way even if it is difficult i can give it a shot
hakemcpu said:
isn't there any other way even if it is difficult i can give it a shot
Click to expand...
Click to collapse
No sorry it is dead. There were warnings all over the forum.

RegawMOD EVO 4G LTE Rooter - Update thread

The Development thread has been opened. Please refer HERE
This is THE best root method I have ever used. Y'all are gonna love this.
Very sweet- cannot wait! If you guys need a tester, let me know.. I'm still stock.
Totally excited about this new development. Thanks for sharing and caring.
Sent from my EVO using XDA
You guys are the best!!!
Now that is how I like it, rooting for dummies, no offense. Looking forward to it to root and open up this Beauty and the Beast phone.
Thanks,
Ian B
Very Cool. If we are rooted but still have bootloader locked will we be able to use the automated bootloader unlock option? Or does the phone have to be completely stock?
What about those of us already rooted via the method available?
Will your method also unlock the bootloader for those already rooted OR is this method only workable from an Unrooted and Locked beginning point?
Does my question make sense?
Mr Ian B said:
Now that is how I like it, rooting for dummies, no offense. Looking forward to it to root and open up this Beauty and the Beast phone.
Thanks,
Ian B
Click to expand...
Click to collapse
That is what I've always been striving for in everything I release. Easy to use and understand.
purock said:
Very Cool. If we are rooted but still have bootloader locked will we be able to use the automated bootloader unlock option? Or does the phone have to be completely stock?
Click to expand...
Click to collapse
typhoonikan said:
What about those of us already rooted via the method available?
Will your method also unlock the bootloader for those already rooted OR is this method only workable from an Unrooted and Locked beginning point?
Does my question make sense?
Click to expand...
Click to collapse
I have had the exact same thought process while developing this, and my answer right now is, most likely. I haven't tested what happens if you try to unlock the bootloader when it's already unlocked. If you are already rooted and have a locked bootloader still, this will work. Just remember that unlocking the bootloader resets your ROM to stock (deletes all user data). All this will be tested before release and answered clearly though
Regaw,
Would it be possible to have an alternate version or option that solely does the recovery image? Let's say someone already were able to get SU on their device with the other method but struggled with fastboot, for example. They wouldn't necessarily want to start over with a new, unrooted/stock ROM.
Is this possible or perhaps too remote of a request to be relevant? I'm in that small minority now I guess, lol.. Got tampered screen, got root on phone, but cannot get recovery pushed to it.
logie said:
Regaw,
Would it be possible to have an alternate version or option that solely does the recovery image? Let's say someone already were able to get SU on their device with the other method but struggled with fastboot, for example. They wouldn't necessarily want to start over with a new, unrooted/stock ROM.
Is this possible or perhaps too remote of a request to be relevant? I'm in that small minority now I guess, lol.. Got tampered screen, got root on phone, but cannot get recovery pushed to it.
Click to expand...
Click to collapse
Unfortunately, you have to unlock the bootloader before you can flash a recovery, and unlocking erases all user data on the phone anyways. So, you really do have to start over. But this application takes care of everything.
Just tested the process on my OG EVO (I left out the actual rooting/flashing so I didn't ruin my phone ) but the process looks nice and works well
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wait am I understanding this correctly that this will unlock the bootloader and HTC will be none the wiser? Because that would be awesome!
Sent from my EVO 4G LTE
Well, it uses your phone's unlock token (obviously has to in order to unlock your own device), but not your login information to htcdev. Every time you call
Code:
fastboot oem get_identifier_token
the token is randomly seeded (different), so I don't know exactly how "traceable" the token is back to your device.
I didn't want to use htcdev to unlock my bootloader, so I've been waiting for something like this.
very impressive! but you're taking all the fun away, lol
O.M.J said:
very impressive! but you're taking all the fun away, lol
Click to expand...
Click to collapse
Trust me.. I know what you mean But that's why I made it look similar to a terminal on the phone haha, had to make it seem cool to us somehow
EDIT: grrrrrrrrrrrrrrrrrrrrrrrrrrrr
clownfart said:
I didn't want to use htcdev to unlock my bootloader, so I've been waiting for something like this.
Click to expand...
Click to collapse
well ur still using HTC Dev with this in a sense...so dont think your avoiding that one...like he said you just dont have to log into it with your account...though if that was your only worry of HTC Dev Unlock then you could just create a fake acocunt on there to unlock the device...
outstanding work though regaw!!
makes it nice for those users that dont wanna mess with fastboot and all...to unlock...
So this will give me S-off?
just kidding - saw you removed the video link when I got back to my comp, something wrong with the vid?

[Q] Help with unlocking bootloader? HTC Incredible 4g LTE

I recently bought a Verizon/HTC Incredible 4g LTE and I was wanting to install cyanogenmod. I was able to find many tutorials to unlock the bootloader, but none of them have been successful.
I keep getting linked to this post:
Code:
http://forum.xda-developers.com/showthread.php?t=1986346&
It works until I get to "adb restore fakebackup.ab" where my phone goes to "Full Restore" but asks for device encryption password, and restore my data is greyed out.
I continued to the next step anyways to get the error: "link failed No such file or directory" endlessly
Since it said there would be errors i continued anyways and had a $ at the end instead of #
Please help!!
elijahkan14 said:
I recently bought a Verizon/HTC Incredible 4g LTE and I was wanting to install cyanogenmod. I was able to find many tutorials to unlock the bootloader, but none of them have been successful.
I keep getting linked to this post:
Code:
http://forum.xda-developers.com/showthread.php?t=1986346&
It works until I get to "adb restore fakebackup.ab" where my phone goes to "Full Restore" but asks for device encryption password, and restore my data is greyed out.
I continued to the next step anyways to get the error: "link failed No such file or directory" endlessly
Since it said there would be errors i continued anyways and had a $ at the end instead of #
Please help!!
Click to expand...
Click to collapse
Have you tried the automatic method on the same link you just mentioned? That's the way I did it. I had a few snags myself but they all disappeared when I tried it on a different computer. I also read several places to try a new USB. You could also try this all-in-one tool kit — http://forum.xda-developers.com/showthread.php?t=1758682 I've used it for a couple of different thins and it has been very usefull. You can use it to unlock your bootloader.
I'm not sure about your specific problem but I hope this is helpful.
Kienan said:
Have you tried the automatic method on the same link you just mentioned? That's the way I did it. I had a few snags myself but they all disappeared when I tried it on a different computer. I also read several places to try a new USB. You could also try this all-in-one tool kit — http://forum.xda-developers.com/showthread.php?t=1758682 I've used it for a couple of different thins and it has been very usefull. You can use it to unlock your bootloader.
I'm not sure about your specific problem but I hope this is helpful.
Click to expand...
Click to collapse
I can't get any of these methods to work
elijahkan14 said:
I can't get any of these methods to work
Click to expand...
Click to collapse
1. Make sure you are on the latest software: 2.17.605.2
2. Factory reset your phone
3. Slowly go through the manual instructions here: [Script] Automated Unlock/SuperCID/Temp-Root scripts for Windows and Linux
So, I've unlocked this phone before.
Just got a replacement.
EVERYTIME I put the token code in and summit I get failed!
screenshot of the error:
http://s28.postimg.org/z8obp6h58/Untitled.jpg
I tired a few different codes and nothing.
HELP?
I'm on bootloader 1.60000
Still no luck.
It tells me in bootloader its tampered but with s-on and still locked.
BlowUpTheOutsideWorld said:
I'm on bootloader 1.60000
Still no luck.
It tells me in bootloader its tampered but with s-on and still locked.
Click to expand...
Click to collapse
I was having difficulty with the SuperCID hack, and it appears that it was due to an OTA update. I was able to following the directions prescribed here, but I had HBOOT 1.15 and not 1.16. The basic idea is to
1. Gain "temp-root" access using the loop-restore trick together with the fake_backup.ab file.
The next steps were failing for me. I was able to verify that mmcblk0p4 had been copied over correctly, with the "modded" version, but each time the boot loader was rebooted, it would be replaced with the original version containing VZW__001, and not 11111111. However apparently all that needed to be done to reach S-OFF status was:
2. Run Rumrunner after obtaining temp-root status. The Rumrunner binary unlocks the phone and places it in S-OFF status.

[Q] First time poster and I really need help!

Hey guys. Need a big hand here. So I have a HTC One on contract from Three in the UK.
I rooted the phone and all that jazz and decided on putting a custom ROM on my device.
However while in TWRP I wiped the phone and seemingly all the contents on it, including TWRP.
Now I have a bricked phone that boots into recovery/ the bootloader only. I've tried flasing
RUU files on but it fails with the error code 140? I don't know much about this I'm quite a noob.
In recovery the information is as follows:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4A. 17. 3250. 14
OpenDSP-v31.120.274.0617
OS-2.24.401.0
eMMC-boot 2048MB
Please help me. I've read through wonderful guides by other patrons on this website but nothing seems to work.
I'm at my wits end.
Thank you in advance for any help.
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Borden Rhodes said:
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Click to expand...
Click to collapse
I unlocked the bootloader originally by getting a specific code from HTC and using it through the command prompt I think. I can go into the bootloader and it has all the fastboot, recovery, factory reset business there. Trying factory reset does nothing. I've downloaded HTC toolkit 2.2 and I tried initially pushing ROMS to flash to TWRP, but it would never detect my phone. Then I stupidly did a full wipe through TWRP and now that's disappeared. All that's left is the bootloader now. I've tried forcing RUU updates through the HTC toolkit but it always fails. So does running the normal RUU process. I can't seem to find the correct one for Three UK. The most I've been able to do is re-lock the bootloader and I'm running out of ideas. Thank you for your reply. I feel so helpless!.
If I've read your message correctly, you are doing everything through the HTC toolkit and not through the Android SDK. Frankly, I don't know how the former works. Especially if the HTC Toolkit isn't detecting your phone, you may want to run over to http://developer.android.com/sdk/ and fetch the SDK for your system and set it up. You don't need the ADT Bundle, just the SDK Tools link at the bottom. This may make it easier for other, more knowledgeable people debug your phone, since they all use the SDK. The weaponry you'll be using is all in the <sdk install location>/tools directory, so get a command prompt window pointed there (by the by, are you using Windows, Mac or Linux?)
If you already have your SDK up, or once you do, you'll want to get familiar with the fastboot command, described in this post: forum.xda-developers.com/showthread.php?t=2277112 . What we want to do is see whether we can flash a new recovery ROM.
As long as you don't attempt to flash over the bootloader, you shouldn't super-brick your phone. Based on the message in your original post, your bootloader may have relocked itself. If your first attempt at installing a new recovery ROM doesn't work, then you'll have to use the procedure you used originally to unlock your bootloader. If you've forgotten how to do that, then these instructions (which assume you're using the SDK) should help: http://wiki.cyanogenmod.org/w/Install_CM_for_m7.
You're currently using TWRP, which I've personally found buggy. Until you have a functioning phone again, you may want to use ClockworkMod (CWM) Recovery instead: http://www.clockworkmod.com/rommanager. It has fewer features, but at least they work properly. If flashing ROMs over fastboot is new to you, there are plenty of guides on the Interwebs to help you. I'll also try to walk you through it if you let me know where you're getting stuck. The critical thing, considering that there are many types of HTC One, is to make sure that you flash the ROM that exactly matches your phone. If you flash the wrong ROM, you probably won't break your phone any more than it is, but let's try not to test that theory. If you're not positive which phone you have, say so and we'll help you find out.
Let us know once you have CWM on your phone or where you got stuck. The advantage of using the SDK, too, is that you can copy and paste the output right back to the forum.
I hope I understood everything correctly. Let me know if I haven't.

root for lg tribute dynasty sprint version

anyone find root method for android 7.1.2 lg tribute dynasty? if so please help if not we need to develope one
Ehacksa said:
anyone find root method for android 7.1.2 lg tribute dynasty? if so please help if not we need to develope one
Click to expand...
Click to collapse
No we realy want root for this phone
Ditto for root on lg tribute dynasty
Mag xx said:
No we realy want root for this phone
Click to expand...
Click to collapse
Ditto for root on lg tribute dynasty, would like to have it. Just putting it out there as a request, thanks.
if we get a custom recovery first get root will be easier
Are there any updates on this?
Can you unlock the bootloader on the sprint/boost variant? If so we can make a TWRP recovery for it and flash magisk for root
jasonmerc said:
Can you unlock the bootloader on the sprint/boost variant? If so we can make a TWRP recovery for it and flash magisk for root
Click to expand...
Click to collapse
Yeah you can unlock the bootloader. All you need to do is go to dev options and enable OEM unlock. I was wondering if there's any cross compatibility between LG software and if it's at all possible to root it using a TWRP recovery intended for a similar phone. I don't want to try it on my new phone yet though considering the risky nature of rooting.
Kevin4762 said:
Yeah you can unlock the bootloader. All you need to do is go to dev options and enable OEM unlock. I was wondering if there's any cross compatibility between LG software and if it's at all possible to root it using a TWRP recovery intended for a similar phone. I don't want to try it on my new phone yet though considering the risky nature of rooting.
Click to expand...
Click to collapse
That's not all you need to do. Once you flip the oem unlock switch you then need to reboot to the bootloader and run the appropriate command--THEN you will really see if your bootloader can be unlocked. I don't know the command off hand but a google search should say what it needs to be
And as far as your other question, yes it is possible to use twrp for a similar phone. However it doesn't look like there is a similar phone with a similar chipset like this that has twrp already but I could be wrong. Note that cross compatibility like this is only for custom firmware like twrp, stock firmware IS NOT CROSS COMPATIBLE.
jasonmerc said:
That's not all you need to do. Once you flip the oem unlock switch you then need to reboot to the bootloader and run the appropriate command--THEN you will really see if your bootloader can be unlocked. I don't know the command off hand but a google search should say what it needs to be.
Click to expand...
Click to collapse
You're right there's more, I wasn't familiar with how bootloaders were unlocked until you mentioned that. After some research, unfortunately, LG has pretty much nailed tight the bootloader for all but a select few LG devices. Still, I followed a guide on how to use ADB and Fastboot in an attempt to reboot into bootloader, but sadly all it does is restart the phone normally. As far as I know, it's impossible to unlock the bootloader on this phone so I guess we're all SOL when it comes to rooting.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kevin4762 said:
You're right there's more, I wasn't familiar with how bootloaders were unlocked until you mentioned that. After some research, unfortunately, LG has pretty much nailed tight the bootloader for all but a select few LG devices. Still, I followed a guide on how to use ADB and Fastboot in an attempt to reboot into bootloader, but sadly all it does is restart the phone normally. As far as I know, it's impossible to unlock the bootloader on this phone so I guess we're all SOL when it comes to rooting.
Click to expand...
Click to collapse
Try the process anyway. My friend said he managed to unlock it on a device that wasn't listed but that was a while ago. If there's something where you put in a serial number or IMEI see if it'll take yours
jasonmerc said:
Try the process anyway. My friend said he managed to unlock it on a device that wasn't listed but that was a while ago. If there's something where you put in a serial number or IMEI see if it'll take yours
Click to expand...
Click to collapse
So far I've tried booting to bootloader through recovery mode and ADB, both ending up booting to the system normally. I'm not sure I understand what you mean by "something where you put in a serial number or IMEI." Is there any way you can find out how your friend managed to do this?
Kevin4762 said:
So far I've tried booting to bootloader through recovery mode and ADB, both ending up booting to the system normally. I'm not sure I understand what you mean by "something where you put in a serial number or IMEI." Is there any way you can find out how your friend managed to do this?
Click to expand...
Click to collapse
For some LG phones there's a process you have to go through on their website to request an "unlocking binary". I believe its something like Motorola's bootloader unlock program. You put in some phone specific info (s/n, IMEI, or something) and if its eligible to be unlocked LG will send you an unlocking binary. Then once you get the binary there's some sort of special fastboot command you have to enter, utilizing that binary, to open up your bootloader
I haven't done this myself so I don't 100% know the process, but this is what I've heard other people discussing in the past. I'll reach out to people and see if I can find the site again
jasonmerc said:
For some LG phones there's a process you have to go through on their website to request an "unlocking binary". I believe its something like Motorola's bootloader unlock program. You put in some phone specific info (s/n, IMEI, or something) and if its eligible to be unlocked LG will send you an unlocking binary. Then once you get the binary there's some sort of special fastboot command you have to enter, utilizing that binary, to open up your bootloader
I haven't done this myself so I don't 100% know the process, but this is what I've heard other people discussing in the past. I'll reach out to people and see if I can find the site again
Click to expand...
Click to collapse
First off, I appreciate you taking the time to help me out. I found what you're talking about, but it's specific to only a few devices and LG SP200 isn't one of the models listed. Also, in order to get the device ID, you first need to enter fastboot mode, which I can't get to work.
[email protected] every cool phone i get i cant root ... :/
Alldayismokebomb said:
[email protected] every cool phone i get i cant root ... :/
Click to expand...
Click to collapse
I think they skipped over the "Unlock OEM" in the developer settings. The device is a mcv150 close to the cv1. Search up LG Aristo 2 TWRP and see if the TWRP flashes to your device. If it works then I can fix the device specific bugs.
It appears that no one has replied to this thread in almost 3 years (as of this post). To resurrect this thread, I have quite a couple of things about this device to say:
I don't think accessing the bootloader is possible for whatever reason. I've tried rebooting into the bootloader (with "Enable OEM Unlock" enabled) through adb reboot bootloader but to no avail.
Root is possible.The Tribute Dynasty (SP200) contains a MediaTek MT6750 SoC. Combined with the last security patch being November 1, 2019 (an interesting coincidence), this makes this device vulnerable to the mtk-su temporary root exploit.
I remember following a guide somewhere else on XDA, but I can't recall which guide (nor can I find it right now). I remember using mtk-easy-su for this purpose, but then that's all I can remember.
There might be some other developments with this phone that I might know about, but all of this I find from experience.

Categories

Resources