http://forum.xda-developers.com/general/rooting-roms/cnc-bootloader-bootloader-access-phone-t3169432
could something like this help with the unlocking of our bootloader ? or am i not getting how it works all together ?
well if you brave enough to test it ...
it states "unless you softbrick there is no bl mode" which assumes you have a bl mode if you softbrick it. If it's true it's cool and unlock via fastboot might work. if it's not true, you've just softbricked your phone without any way to recover.
Someone brave with Equipement protection plan may want ot backup his phone and try the method and if it softbricks just file a claim with assurion and wait 3 days for a replacement living without phone.
Another problem is - the thread in the link mentions the cnc-bootloader without actual link to it or any other way to download, otherwise maybe I'd try it
there was a user in the root development thread who backed up/deleted laf.img in order to boot to fastboot, which worked but i think it didnt respond to any commands. i bricked my first g4 trying the same but i didnt enter the right command and deleted aboot by accident oops.
found that post
http://forum.xda-developers.com/showthread.php?p=62085237
just wanted to share what seemed like a possibility at helping with the current bootloader status...
as much as id love to try, i have no idea how to but would gladly work with someone that could go with me step by step...
if **** hits the fan , warranty should cover the damage and i could roll back to my trusty G2 till i get the phone back
Related
My HOX was in this rom & kernell tripndroid_endeavoru-ota-eng.noeri_002.zip
http://forum.xda-developers.com/showthread.php?t=1784185
after install tripndroid_endeavoru-ota-eng.noeri_003.zip and flash thats kernel([email protected] #2)
my device do not allow me to flash other kernel(in bootloader allow and flashing successful but in phone os show [email protected] #2) OR do not allow to lock boot loader AND in TWRP recovery all operation same as format system, data, install new rom and other operations doing successful but after reboot phone i see nothing happen, and see last rom with last kernel last and last user data;
Who know anyway to go out from read only HOX?
How did you install that rom? Because that download link was deleted i think a month ago?
the v003 noeri kernel is the culprit of that hard bug.
Basically, you are now in apx mode. you can't do anything about it, even trip whacked his phone cause of numerous failed attempt to fix it.
Sorry dude but your phone was bricked. no other option but to send it to service center. hope you are still under warranty and your provider accept the repair for free:angel:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
if i am of any help, please hit the thanks button:good:
Sorry to say this mate but you're totally bricked.
Only a new motherboard will help...
Its best to search on how to brick your bootloader properly .....when the service center can't read/boot your bootloader anymore they don't know if it was actually unlocked before. This way you have more chance of a free repair. Because when they see the tripnraver stuff they are unlikely going to fix it under warranty/hardware defects.
but my HOX not have waranty or garanti!
i think wait to s-off to solve read only problem...
I hope you get it sorted when we get s-off !
I also have one in read-only, and I've done some investigations.
I'd rather say it's the emmc controller that's busted, in which case we won't be able to do anything as long it's not functional (I don't think even the official s-off methods will work). On the other hand, while bricking, the write protection went off and I could write some partitions, until it settled to read-only (my goal, back then, was apx). I find this interesting because this might be an short (but dangerous) way to s-off. Still, we need to identify the exact commit that holds the guild.
PS: if you don't have warranty, try changing the emmc chip, might be cheaper.
Ok so I read the FAQ and understand that the r800a uses a paid for unlock of the bootloader. Seems like bs but its whatever.
You cant seem to pm anyone instantly and the webpage it links to, to go about unlocking it that way just doesnt load anything really.
How can I go about getting this show on the road and unlocking my bootloader so I can actually do fun stuff with my phone and at least over clock it as thats all I really wanna achieve out of it?
Sure this kinda craps been asked a million times but when the faqs links no longer work I dont know what else im supposed to do.
Already used super one click and rooted the phone that part was easy enough.
there's a hope
Hi, i'm new, i hope i'm not breaking any rule with this.
If you got this:
Code:
Rooting Status:
Bootloader unlock Status: No
Then you are unable to unlock your bootloader without pay, but it does not mean you are not able to do fun stuff like you said , you only need to do a test point, give a look to this tutorial TUTORIAL, follow all steps, it is not necessary to sold a clip to usb, you just need to bridge the red points shown at bottom of this post POST . Now you wont be able to flash any .img in fastboot , you should flash .ftf basebands and kernels in flashmode, then flash rom with CWM then enjoy your phone .
I'm no an english speaker so i'm sorry if my english is not good, you can see THIS post which xplains better than me.
And here you can find all (i think) kernels for xplay in ftf ready to flash.
Hope i was helpful. Good luck. :fingers-crossed:
I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!
westonnate said:
I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!
Click to expand...
Click to collapse
If you wanna fix it quick then just do an RUU (t-mobile one) and after you've done that use Sunshine to root, unlock and S-OFF your phone. All though Sunshine costs $25 it is a sure fire to work.
You can find a tutorial for the RUU in the t-mobile forum I believe, not sure as im replying to this before I go to bed but it should have one. If by some chance "TMO" doesn't mean T-Mobile then my bad. Anyways if you get confused take your time and do your research or wait for someone else or me to assist you further.
Also if you used Xposed then that could be the problem, I've had it randomly bootloop me after days of use, just google the Xposed deactivate script zip or Uninstaller script and flash it to remove it. If you don't have it then don't do this part.
Lastly I doubt you'll regret buying an M8 after you get it setup properly, it's a great phone but of course that's just mine and a lot of people's opinion. Anyways good luck and hope one of my solutions fix it! If not then don't be afraid to ask more questions or request further assistance whether from me or someone else.
S1L3nTShaDoWz said:
If by some chance "TMO" doesn't mean T-Mobile then my bad.
Click to expand...
Click to collapse
It does, although T-Mobile is a huge carrier in Europe, and AFAIK only the US T-Mob variant has an RUU (and not immediately clear what version the OP has).
You can flash custom roms without s-off, and have you tried wiping cache and fixing permissions? Idk if that'd solve it or not but worth a try.
Hey guy's,
Hopefully This is in the right place. Please assist in anyway you possibly can. This phone is not a brick, but it might aswell be. I have tried literally every kind of reset unbrick guide I can find for the past 2 months, and nothing works.
From what I can tell it is a driver issue, but even installing the meta mediatek preloader, and drivers does not seem to work. I have tried a fresh install of windows 8.1, windows 7, and xp. nothing works. I can not install the adb drivers for this device, because the phone will not even boot into recover. Recovery is corupted or something. I do have an mtkdroidtools backup, but can not flash it with sp flash because it always gives the error "THIS IS A SECURE BASEBAND CHIP PLEASE LOAD AUTHENICATION FILE". I've worked with kirito9 which was a big help in understanding a few things, but we could not get it sorted. I will stop talking now, and post something useful.
BTW:mobile upgrade tool s does not work either. I get terminal read failure.
As of now im on windows 8.1 with drivers installed. I have posted a couple of videos to show whats going on. Hopefully they will help. I can post some logs, but I honestly dont know which ones you would want, I have a lot of them, and have tried so many things I dont know where to begin again. In the zip file there is 2 videos, and the original mtk.log.
I forgot to mention that, this all started when I wanted to root, and install a custom recovery. I believe I used the guide on here but cant remember seeing as it was a while ago. Also the phone does not vibrate at all. Like I said I have a backup, but I dont remember much about it I dont know how reliable it is, and if I read back with sp flash or not. I believe I had to right? idk. thanks in advance.
https://drive.google.com/file/d/0B_DyVUIoGhqBSXlhbkNhdVNCR1k/view?usp=sharing
Wow I cant believe nobody has run into this problem. That or you guy's are just busy which I totally understand.. I'm just really frustrated. I think I am going to try to return it to t-mobile. You gotta know when your defeated, and this is it. This phone has been a nightmare.... I just hate giving up. I broke it, and I wanted to fix it.
Anyway if this was in the wrong lace to post please let me know. thanks.
I called t-mobile, and told them it didnt work. They asked the normal questions, and agreed to replace it. The guy said they are going to check it out to verify condition. Once they play with it enough to power it on they will see the flash error.
Is this something to worry about? also, is there a way to make sure it doesnt power on? I know thats shady, I just cant afford the deductible right now seeing as i'm out of work at the moment.
TireIron431 said:
I called t-mobile, and told them it didnt work. They asked the normal questions, and agreed to replace it. The guy said they are going to check it out to verify condition. Once they play with it enough to power it on they will see the flash error.
Is this something to worry about? also, is there a way to make sure it doesnt power on? I know thats shady, I just cant afford the deductible right now seeing as i'm out of work at the moment.
Click to expand...
Click to collapse
Hey man, I cant really help with unbricking it. Mediatek chips are not my strong point but i just wanted to say logically if the recovery is corrputed and the rom is corrupted and the bootloader is not playing ball then unless the chips have a write counter/modification check then you should be okay I reckon.
Good luck though
I still have it because I wanted to at least make it boot ok, but to no avail. I got the replacement and made a good back up with mtk droid, but I still get the error.
The phone is an Identical copy of my last one, and still no go. I even tried to flash it with the new phone, I get the same error. so I guess im a monkey, and cant do it right. If it's doing the same thing with the new phone as it is with the bricked one, than its me right?
I did notice that I cant create a scatter file with the create scatter button(its greyed out) I can only make one through the firmware.info.
This is the phone info from both phones.
Hardware : MT6581
Model : ALCATEL ONE TOUCH 4037T
Build number : ALPS.KK1.MP1.V2.10
Build date UTC : 20140918-073410
Android v : 4.4.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V34.P13, 2014/09/18 15:26
Kernel v : 3.4.67 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP Mon Sep 8 10:47:59 CST 2014
Uboot build v : ----- should be root shell
LCD Driver IC : 0-nt35512_dsi_vdo_tdt_lcm_drv
From what I have read this is actually a 6572 chip. Is this correct? I was just thinking that maybe droid tools wasn't reading it right, or backing it up right. Droid tools creats a 6582 scatter file, but my phone says 6581, and I saw 6572. Which one is it? I cant find or make a 6581, so I do not know what to do. I have tried both phones with all of the different drivers, with the different scatters, and I always get error 5000 secure baseband chip.
Hello TireIron, in these moments I am passing through the same despair that you suffered with your telephone, I have done the same steps exactly than for the ones that you passed, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.I have done the same steps you passed for, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.
I don't know, if at the end you could solve the problem and recovering the telephone, if so, what solution did you find? I would thank you for if you shared the solution.
Thanks from the start.
danymt87 said:
Hello TireIron, in these moments I am passing through the same despair that you suffered with your telephone, I have done the same steps exactly than for the ones that you passed, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.I have done the same steps you passed for, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.
I don't know, if at the end you could solve the problem and recovering the telephone, if so, what solution did you find? I would thank you for if you shared the solution.
Thanks from the start.
Click to expand...
Click to collapse
Your issue is you flashed with the secure bootloader still active, as to why your having issues flashing it back... I've been searching around for a Custom Recovery/ROM, I'll check back in if I find anything on Disabling the Secure Bootloader, as I see it your not going to be able to restore (even to STOCK) without Unlocking the Bootloader/ And/Or Reactivating it upon re-flash.... So far no luck on finding a way to disable it, but just started a couple hours ago....
Mike
UPDATE:
ok Upon more searching it appears at the moment you need an NCK BOX...
https://www.google.com/search?q=unl...-8#newwindow=1&q=disable+secure+boot+on+4037t
http://www.ebay.vn/mo-ta-san-pham-281534386171.html
Hello guys!
After much research on the internet about unbrick for Moto Z2 Force, after many forums, tutorials, tools, blankflash, etc., I've came to the conclusion: I've not found anyone who has managed to recover a Moto Z2 Force from a hardbrick with a locked bootloader.
Many are hopeful that it is possible to do so, but I believe it is no more than a fairy tale.
If you succeeded, please help others to get it too.
andrecesarvieira said:
Hello guys!
After much research on the internet about unbrick for Moto Z2 Force, after many forums, tutorials, tools, blankflash, etc., I've came to the conclusion: I've not found anyone who has managed to recover a Moto Z2 Force from a hardbrick with a locked bootloader.
Many are hopeful that it is possible to do so, but I believe it is no more than a fairy tale.
If you succeeded, please help others to get it too.
Click to expand...
Click to collapse
My second Z2 kept bricking and locking itself. My only saving Grace was I was able to unlock it since I had the unlock code still and since it wouldn't boot, it would accept the unlock code. It is a slot ab issue where if your phone never took an OTA (I flash all to Oreo and tried flashing DU and AOSP before taking an OTA to open slot B). This caused the phone to lock itself and go a little nuts. But it was unlocked then locked due to slot issues, so it shouldn't count. Maybe my story is a fairy tale ... No... I remember spending the hour trying to figure out why this thing wouldn't install an AOSP rom but my other would just fine, then facepalm when I figured I just needed to take an OTA.
This person had a locked bootloader and we were able to sort through and get it back to good. Maybe yours is a little worse off, idk, but the gist should be the same. I'm not sure what you've tried. whether you can load os, etc. Here is a link to the thread where we finally got it sorted, it's a little hit and miss, but maybe it'll get you going in the right direction.
https://forum.xda-developers.com/z2-force/help/help-help-help-deep-cable-flash-cable-t3925742
41rw4lk said:
This person had a locked bootloader and we were able to sort through and get it back to good. Maybe yours is a little worse off, idk, but the gist should be the same. I'm not sure what you've tried. whether you can load os, etc. Here is a link to the thread where we finally got it sorted, it's a little hit and miss, but maybe it'll get you going in the right direction.
https://forum.xda-developers.com/z2-force/help/help-help-help-deep-cable-flash-cable-t3925742
Click to expand...
Click to collapse
Alas this person had a different problem from me. It sounds like they had something of a pseudo-lock that just needed a nudge to get the kernel to recognize the OEM unlock had been authorized.
The above thread may prove useful to people who have had issues with locked bootloader but who have access to the system.
I do not have access to the system. fastboot oem blankflash command is "restricted" for me. Yet it still classifies both slots as bootable, it just refuses to boot them, which is not enough to trigger any emergency download apparently. It seems this person never succeeded in doing that, because they found an easier way.
I'm really trying to figure out if buying a cable would be worth it, but I have doubts. I was able to access my usb hub and manually short the pin using a voltmeter and some wire to find which traces were connected -- exactly mimicking the action of most "deepflash" cables.
No dice.
That, and I read that the MSM8998 doesn't use the same programmer as other qualcomm androids, possibly uses an older one, and I haven't found any reference to which one. I think blankflash should be possible on these phones, but triggering edl seems impossible from my position, since I have no adb but I do have a basically useless bootloader, which aggressively overrides edl. :angel:
Basically the way I see this, my bootloader thinks its serving a purpose: fending off modified system files, which I unwittingly made its only function when I locked it. It is forbidden from handing over the power of my z force to a patched OS. Since the bootloader exists, and is technically able to boot, it's just not allowed, edl will never be activated because it utterly defeats android security. edl is the backdoor that opens when everything else is completely gone or unintelligible. Is that accurate? :cyclops:
I am beginning to accept that my phone was not meant to be rooted really in the sense that, yes, its Linux and you can, but it's basically been booby trapped by Lenovo and if you fall for the logic I did at first, and try relocking it at the first sign of strange behavior, you have to buy a new phone. Exactly what they want.