Related
OK, i searched and found some threads on the matter but that was for the Prime. also found some other issues with the unlocker dealing with an un-recognized serial number or no data connection.
anyway, a little about my tablet. purchased it from a friend, brand new, sealed in box. serial numbers match (between box and device) i rooted right away since i was on the .17 firmware, did the OTA root keeper thing. the OTA was pushed to my device that same day, it updated just fine. a couple days later the .30 update was pushed to my device...took that as well just fine. so i was running stock .30 firmware but was rooted. I tried the unlock tool in that state, and got the message below. so i started reading and saw a reset could fix it...so i did that.....no dice.
did a "cold reboot" (volume down and power until the message pops up and just let it time out for the 10 seconds to clear caches and what-not.)
tried again....Nothing.
i have tried it while tethered to my Nexus, and connected to my home wi-fi with no luck.
what is my next step? should i downgrade to .17 and give it another go? is this possible without a computer (at work and would like to do it today)
is this just an ASUS server issue and just "bad timing" to unlock...or does this go deeper than that?
thanks for all your help....pulling out my hair trying to figure this out.
its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.
Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.
EndlessDissent said:
Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.
Click to expand...
Click to collapse
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?
turdbogls said:
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?
Click to expand...
Click to collapse
Yeah, I think that's how it works. When I downgraded to .17 to root way back when, I used Wolf's method, which used ADB. I think either way will work fine.
OK, can anyone confirm or post a link or something to the exact method of an "on the device" downgrade method.
the only things i am finding online are Wolf method which involves ADB.
can i simply put the .zip or blob (which one?) on the root of internal memory.
turn off tablet
hold volume down +power
hit volume down
then volume up
and it will install the .17 system?
I am working late tonight with no access to my home computer for the next couple of days probably
ok, i actually got of work early and was able to downgrade via ADB. i am on stock .17 firmware right now doing a factory reset and then i will be giving it a go one more time.
edit: Annnnd....it didnt work >)
Damn. The worst part is that Asus refuses to help people in your situation. All I can suggest now (hopefully someone can suggest something better), is to try everyday, at least once. Some people get it to work like that.
I really wish I could help more. The most trouble I had with unlocking was signing into my Google account (I have 2-step authentication). I was on .30 rooted, and it worked perfectly. I know that's not what you want to hear. I just have no idea why it would work fine for some people and not work for others. The serial number issue was bad enough, but now, people with working serials can't use the unlocker? That's preposterous, and Asus needs to fix it.
Well....what can ya do. I am going to call Asus tomorrow and see if they can verify my SN is in the database.
I'd I can unlock...great!
If I cant , well I will still enjoy my rooted tf300 and wait patiently for my JB OTA.
I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.
EndlessDissent said:
I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.
Click to expand...
Click to collapse
I hope you are right....I dont expect it to be before a stable CM10 is released....but i do have high hopes to see it before the end of August.
FWIW, i am back on stock .30 rooted sofware. back at square 1
but i will be trying the unlock tool every day until JB arrives or it works...lol
also contacted ASUS (e-mail) about the issue, they told me to factory reset and see if that worked.....hope they can help me out even more when replying to my reply.
mikaole said:
its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.
Click to expand...
Click to collapse
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!
Saintom said:
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!
Click to expand...
Click to collapse
lol
I'll give them some BS about a neighbor having the same issue and having them enter it into thier database fixed it.....that should work.
the announcement of an almost complete (BT and camera dont matter to me) AOKP JB build has me making this call in about an hour. I want this done SOOOO bad now
OK, so i called them with some BS about not getting updates and asked them to put my number in their "system"
the guy said that my SN was in there now.
still no dice on the unlocker app.
how long does it take to become "activated" in their system. should i be waiting a day before expecting results?
still nothing today...anyone else get this message and have it resolved?
i read a thread where a bunch of people are getting the same error (over on the TF Prime forums) it just wasn't working for some reason...then one day, boom, it started working again.
so maybe it is something on ASUS' end and they either shut it down or it just isn't working right now.
anyone successfully unlock their device in the last week?
turdbogls said:
anyone successfully unlock their device in the last week?
Click to expand...
Click to collapse
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).
bsaman said:
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).
Click to expand...
Click to collapse
I hate you for being able to do it so easy...lol
i have unrooted, i have factory reset a couple times, i have downgraded to .17 and factory reset then...nothing
I WAS getting OTA's though. so i guess i am just going to have to wait for official JB...i would love to be running AOKP JB on my 2 main devices.
Did you manage to get this working?
I just got a notification on my phone about a new moto software update. Will it make it harder for my to flash, root, or mod my phone?
Everything is still stock on the phone i havent done any mods yet
The official bootloader unlock should work regardless, so no if you don't mind doing the official unlock method.
I've heard the exploit to get root without the official unlock has been closed, but I think someone else said they found a way around it. I don't know either way, I officially unlocked the device the day I got it
Is there a new update? post/after asa14?
Checked around but after seeing the old do this if you cant upgrade threads pop up I was curious.
Seen some traces of the 9.8.2Q JellyBean update for the Q, but don't know it's current status.
Interesting and good news, Just checked and mine stated not update available sadly..
Gxkon said:
I just got a notification on my phone about a new moto software update. Will it make it harder for my to flash, root, or mod my phone?
Everything is still stock on the phone i havent done any mods yet
Click to expand...
Click to collapse
Can you share what this update is, OP? The small update from last month or is this Jelly Bean?
swintec said:
Can you share what this update is, OP? The small update from last month or is this Jelly Bean?
Click to expand...
Click to collapse
I dont know it dont look like a new os. One was around 60 mb then i had a small 7 mb update
arrrghhh said:
The official bootloader unlock should work regardless, so no if you don't mind doing the official unlock method.
I've heard the exploit to get root without the official unlock has been closed, but I think someone else said they found a way around it. I don't know either way, I officially unlocked the device the day I got it
Click to expand...
Click to collapse
Yeah, the motofail2go exploit to root works only if you haven't updated. After rooting, you can save root by Voodoo OTA rootkeeper, temp unroot, install any updates, then restore root with OTA rootkeeper. Works great, and you keep your warranty. But of course you can't flash any ROMs or anything, but you can still use Titanium backup, other programs that require root.
see this thread:
http://forum.xda-developers.com/showthread.php?t=2053444
Has ASUS accidently blocked NVFlash through the JB update or was it purposely blocked in the JB 4.1.1 update?
Any word from ASUS about unblocking NVFlash in the future updates?
What are the odds of an explot in future updates?
Sign this if you havent already :good:https://www.change.org/petitions/asus-nvidia-revert-changes-in-jb-bootloader-that-prevent-nvflash
ronniereiff said:
Has ASUS accidently blocked NVFlash through the JB update or was it purposely blocked in the JB 4.1.1 update?
Click to expand...
Click to collapse
It was never officially supported - we always had to use a hacked bootloader to get the blob, and a special tool to enable nvflash. With the JB update they added signature verification for bootloader updates - I don't know if they did it to block nvflash, but I doubt that it was the main reason.
I doubt it too.
Having said that, if I was Asus I wouldn't want users messing with NVflash either so it's no loss to them that you don't have it. If you use the device as they intended it you wouldn't need nvflash.
sbdags said:
If you use the device as they intended it you wouldn't need nvflash.
Click to expand...
Click to collapse
...or CROMI.
IMHO, they should give users who unlock their tablet their unique SBK. Since unlocking voids the warranty anyway, it would be only fair to give users full control over their device.
_that said:
...or CROMI.
IMHO, they should give users who unlock their tablet their unique SBK. Since unlocking voids the warranty anyway, it would be only fair to give users full control over their device.
Click to expand...
Click to collapse
Agreed but they have never done this. I had the original TF101 which on the first few revisions had a working NVFlash. Thesame thing happened. The version I bought had a updated bootloader and the NVFlash was a thing of the past.
The same has happened on the prime and on the TF300 as well as the infinity.....
Asus have no reason to give it to us really. In fact they make money by us not having it from people who have to send in bricked devices. Which by all accounts they replace the mainboard on and don't use any flashing tools to recover although I suspect they could do it that way. Unless they reflash with a new serial???
sbdags said:
Asus have no reason to give it to us really.
Click to expand...
Click to collapse
Yes, unfortunately - as long as nobody offers a more open device with similar capabilities.
Hello, I am just wondering if any of you guys received a firmware upgrade recently.
I upgraded to this firmware which I believe was built early this month and it seems like it can't be rooted and my Google play keeps on crashing.
I did some searches and there seems to be no results regarding tf700 and this build. Anyone?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
lairusi said:
Hello, I am just wondering if any of you guys received a firmware upgrade recently.
I upgraded to this firmware which I believe was built early this month and it seems like it can't be rooted and my Google play keeps on crashing.
I did some searches and there seems to be no results regarding tf700 and this build. Anyone?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Looks like they are doing a new release for the TF700 which is not unexpected seeing as they just did one for the TF300 and ME301 as well. The same problem exists on those two devices. Asus have closed the root loophole motochopper has been using. As of now there is no known root method other than unlocking.
What waste of their time...instead of fixing things like the lag, on screen keyboard output and browser compatability they get all paranoid about someone fixing it for them...
Duhhh....
flhthemi said:
What waste of their time...instead of fixing things like the lag, on screen keyboard output and browser compatability they get all paranoid about someone fixing it for them...
Duhhh....
Click to expand...
Click to collapse
S'alright, unlock and flash my CROMi-X 5 which is based on their later 10.6.1.27.1 release anyway
@sbdags
When I get mine back, if it's fixed, I intend to do just that might be the only good way to get any use of my 700!
you won't be let down by cromi 5 beta
I'm amazed by this rom
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
So, does anyone have a changelog for this or know if it's possible to keep root with Voodoo OTA and this update?
On the other hand, I may be sending my tablet to ASUS for repairs. If they update to this firmware, does factory reset revert to an older version I can root without unlocking?
Thanks!
[EDIT] link to dlpkgfile: https://www.dropbox.com/sh/d8etgzh3gha1xsv/8sVi2SL_7R
daemonios said:
So, does anyone have a changelog for this or know if it's possible to keep root with Voodoo OTA and this update?
On the other hand, I may be sending my tablet to ASUS for repairs. If they update to this firmware, does factory reset revert to an older version I can root without unlocking?
Thanks!
[EDIT] link to dlpkgfile: https://www.dropbox.com/sh/d8etgzh3gha1xsv/8sVi2SL_7R
Click to expand...
Click to collapse
I have sent mine in for digitizer repairs...so I'm sitting here worried about the same thing...I hope they don't flash my stuff..as of this moment, I don't think there is a way back.
Motorola did this to me with a Photon 4G phone right before they said they wouldn't be updating the OS beyond 2.3 they OTA'd my phone so I can't put a ROM on it. Guess what, no mo moto for this dude and now there won't be any more Asus either, pretty soon I won't be buying anything but I'll have a lot of money!
flhthemi said:
I have sent mine in for digitizer repairs...so I'm sitting here worried about the same thing...I hope they don't flash my stuff..as of this moment, I don't think there is a way back.
Motorola did this to me with a Photon 4G phone right before they said they wouldn't be updating the OS beyond 2.3 they OTA'd my phone so I can't put a ROM on it. Guess what, no mo moto for this dude and now there won't be any more Asus either, pretty soon I won't be buying anything but I'll have a lot of money!
Click to expand...
Click to collapse
I recently got mine back from RMA for a digitizer repair and they didn't touch the OS or f/w install. And no problems with the repair - went very well overall.
Sigh...So much for Motochopper.
sbdags said:
Looks like they are doing a new release for the TF700 which is not unexpected seeing as they just did one for the TF300 and ME301 as well. The same problem exists on those two devices. Asus have closed the root loophole motochopper has been using. As of now there is no known root method other than unlocking.
Click to expand...
Click to collapse
Thanks for the post, sdbags. :good: I've been struggling with Motochopper ever since I got the OTA a day ago. I thought I was doing something wrong, and have been ripping out my hair. You have saved an old man's sanity.
And I was soooo happy to see that I had gotten and OTA and my build was now 10.6.1.14.10, up from 10.6.1.14.8. Ah well.. just have to wait for another motochopper. Anyway, thanks again. :highfive:
Reggie777 said:
Thanks for the post, sdbags. :good: I've been struggling with Motochopper ever since I got the OTA a day ago. I thought I was doing something wrong, and have been ripping out my hair. You have saved an old man's sanity.
And I was soooo happy to see that I had gotten and OTA and my build was now 10.6.1.14.10, up from 10.6.1.14.8. Ah well.. just have to wait for another motochopper. Anyway, thanks again. :highfive:
Click to expand...
Click to collapse
There was one user reporting to have kept root with OTA root keeper. You could downgrade to .8, .10 does not seem to have any real advantage anyway...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
There was one user reporting to have kept root with OTA root keeper. You could downgrade to .8, .10 does not seem to have any real advantage anyway...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
I have taken the update and used OTA rootkeeper. Worked fine for me, root explorer, busybox and other root apps all working.
sparksd said:
I recently got mine back from RMA for a digitizer repair and they didn't touch the OS or f/w install. And no problems with the repair - went very well overall.
Click to expand...
Click to collapse
Good to hear! My only question is will they do it under warranty as it expired on the very day the digitizer started acting up
daemonios said:
So, does anyone have a changelog for this or know if it's possible to keep root with Voodoo OTA and this update?
On the other hand, I may be sending my tablet to ASUS for repairs. If they update to this firmware, does factory reset revert to an older version I can root without unlocking?
Thanks!
[EDIT] link to dlpkgfile:
Click to expand...
Click to collapse
Hi daemonios
This is the dlpkgfile WW version ?
I apply the upgrade but Voddo OTA don't want to restore my root
So i will try to downgrade to .8 and i need the dlpkgfile if OTA isn't available again ...
thanks
flhthemi said:
Good to hear! My only question is will they do it under warranty as it expired on the very day the digitizer started acting up
Click to expand...
Click to collapse
sparksd said:
I recently got mine back from RMA for a digitizer repair and they didn't touch the OS or f/w install. And no problems with the repair - went very well overall.
Click to expand...
Click to collapse
For my digitizer recalibration repair they downgraded it to 4.1, and it won't upgrade now (just doesn't find any updates, on stock).
Sylm said:
Hi daemonios
This is the dlpkgfile WW version ?
I apply the upgrade but Voddo OTA don't want to restore my root
So i will try to downgrade to .8 and i need the dlpkgfile if OTA isn't available again ...
thanks
Click to expand...
Click to collapse
I have read from quite a few users who were able to keep root with Voodoo. Don't know what went wrong for you?? Did you temp unroot before updating?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
I have read from quite a few users who were able to keep root with Voodoo. Don't know what went wrong for you?? Did you temp unroot before updating?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Dont't know what exactly
Apply OTa fine, go to Vodoo to restore Root
/system supports root protection and Protectected su copy available checked
click Restore root get messages ok but no more check and device not rooted
I don't temp un-root because i never do it for previous OTA..
Downgrade in .8 OK
Root motochoppper OK
Restore App and config with TB OK
Now i just have to OTA again and cross fingers ..
Sylm said:
Dont't know what exactly
Apply OTa fine, go to Vodoo to restore Root
/system supports root protection and Protectected su copy available checked
click Restore root get messages ok but no more check and device not rooted
I don't temp un-root because i never do it for previous OTA..
Downgrade in .8 OK
Root motochoppper OK
Restore App and config with TB OK
Now i just have to OTA again and cross fingers ..
Click to expand...
Click to collapse
In cases like this temp unroot usually helps.
Bad update
Hi to all,
I´ve just update my TF700T to the latest firmware JOP40D.US_epad-10.6.1.14.10-20130801 but all goes wrong.
First, every app I´ve installed has been stopped, no one works. Every time that i want to launch an app, appears the message "sorry, the XXXX app has stopped...", the same with a lot of processes: "sorry, the process XXXX has stopped"
Second, I try to fixit rebooting the pad, but evrery time I reboot it, or shut off and then power on it, is the same: "android is updating/upgrading: optimizing nn applications of mm"
What should I do, i´m desperate my TF700T is unusable.
I´m root, not unlocked. I activate the survival mode in the SuperSu app to try to mantain the root.
Thank you very much in advanced.
update:
I made a cold reset, wipe data and nothing works. Now I can´t enter on the system, because when I need to configure my google account, i receive a message the process com.google.process.gapps has stopped.
I also try made a RCK, but i got the android with the red triangle with the exclamation inside.
juliusce said:
Hi to all,
I´ve just update my TF700T to the latest firmware JOP40D.US_epad-10.6.1.14.10-20130801 but all goes wrong.
First, every app I´ve installed has been stopped, no one works. Every time that i want to launch an app, appears the message "sorry, the XXXX app has stopped...", the same with a lot of processes: "sorry, the process XXXX has stopped"
Second, I try to fixit rebooting the pad, but evrery time I reboot it, or shut off and then power on it, is the same: "android is updating/upgrading: optimizing nn applications of mm"
What should I do, i´m desperate my TF700T is unusable.
I´m root, not unlocked. I activate the survival mode in the SuperSu app to try to mantain the root.
Thank you very much in advanced.
update:
I made a cold reset, wipe data and nothing works. Now I can´t enter on the system, because when I need to configure my google account, i receive a message the process com.google.process.gapps has stopped.
I also try made a RCK, but i got the android with the red triangle with the exclamation inside.
Click to expand...
Click to collapse
I got this error when mine upgrade to 10.6.1.14.10, too...
I managed to fix this by following "Alternative Firmware update Method" in http://forum.xda-developers.com/showpost.php?p=28374043&postcount=1
You may download 10.6.1.14.8 from Asus web site, downgrade the device, root it if you want to, and then apply OTA upgrade again.
As a friendly reminder to those unfamiliar with unlocking/re-locking their bootloaders;
Unless your on 100% stock, and planning on reselling your phone, don't re-lock the bootloader.
For some reason re-locking the bootloader while you have a custom ROM installed will cause the phone not to boot (in a way, soft bricking it.)
And, leave "OEM unlocking" in the "Developer Options" CHECKED, once that is unchecked you cannot unlock the phone once a soft brick happens.
The official advice from Essential about re-locking your phone is ONLY for the official firmware. Pretend they never said that on their site, it has caused more trouble then necessary. It's even dangerous to re-lock while running the Oreo beta.
Concerning un-bricking the device, at the moment there is no known way.
And it will be this way until someone figures out a way to exploit the bootloader or reverse engineer it.
So please don't flood this thread with asking for help to un-brick your device, I nor anyone else can help you on that at this given time, all I'm doing is trying to is prevent that happening.
So, safe unlocking! And happy holidays!
EDITS:
1) According to some reports, when you lock your bootloader it will also automatically untoggle the "OEM Unlocking" option.
2) It appears when re-locking the phone on a non-stock ROM some partitions are becoming corrupt, and resulting in the "red boot warning" screen. Under most circumstances you can fix that screen, but not while the bootloader is locked (since you need the fastboot flash command.)
3) When the partitions become corrupt you cannot boot into any mode, including the stock recovery. This is why Essential's suggestions are pointless at this stage of the brick.
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
avd said:
Should be pinned and in the OP of every mod thread
Click to expand...
Click to collapse
totally agree, i made this "trick" with one of my first android phone and it never happen me again. But new user who would flash Los or other rom should be aware of this issue, specially when jtag is not an option. As far we'll make some powerfull 500$ brick :crying:. it's our duty to make people aware of this. @invisiblek you guy made an incredible work and so fast but like he said i think you should warn people of the risk in the OP
avd said:
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Ellises said:
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Click to expand...
Click to collapse
It's very easy to ask for a thread to get stuck to the top.
Just use the report post button, and ask, whether or not becomes a sticky is up to the Mods.
How to Report a Post.
Sent from my XT1254 using XDA Labs
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
ericzhf said:
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
Click to expand...
Click to collapse
Ellises said:
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
Click to expand...
Click to collapse
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
ericzhf said:
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
Click to expand...
Click to collapse
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
tech_head said:
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
Click to expand...
Click to collapse
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
ericzhf said:
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
Click to expand...
Click to collapse
FDR is not "back to stock".
You must to a full flash to get back to stock.
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Ellises said:
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Click to expand...
Click to collapse
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
I could also mention on their stock build page it wants you to unlock the bootloader to manually update through the bootloader. But on the oreo beta page it mentions nothing about having to be unlocked, or locked to do it via the stock recovery. So the average user could presume they need to be unlocked.
NaterTots said:
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
Click to expand...
Click to collapse
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
No.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Obamaloominaty said:
No.
Click to expand...
Click to collapse
tech_head said:
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Click to expand...
Click to collapse
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
WiddleyScudds said:
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
Click to expand...
Click to collapse
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
tech_head said:
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
Click to expand...
Click to collapse
I just got an ota notification for OPM1. 180104.092. think I'll be safe I I take it, then factory reset and then lock? Because I can't seem to locate stock NMK24B to flash. Maybe I'm not looking hard enough .