[Q] Locked Bootloader? - Shield Q&A

Anybody have any insight into whether or not the bootloader will be locked? Since there has never been a device directly from NVIDIA before we really don't have anything to go off of, or do we?

blaxer said:
Anybody have any insight into whether or not the bootloader will be locked? Since there has never been a device directly from NVIDIA before we really don't have anything to go off of, or do we?
Click to expand...
Click to collapse
It's required to ship locked as to support certain video features. But it also support 'fastboot oem unlock'. And yes, I've confirmed that it works.

agrabren said:
It's required to ship locked as to support certain video features. But it also support 'fastboot oem unlock'. And yes, I've confirmed that it works.
Click to expand...
Click to collapse
So, I'm assuming this means that it will shipped locked, but the bootloader is unlockable...

jadengore said:
So, I'm assuming this means that it will shipped locked, but the bootloader is unlockable...
Click to expand...
Click to collapse
Yes. Exactly what I'm saying.
Sent from my HTC One using XDA Premium HD app

Sounds as easy as Nexus devices. That would be great.

agrabren said:
Yes. Exactly what I'm saying.
Click to expand...
Click to collapse
And what about sources/binary blobs?

Adanedhil said:
And what about sources/binary blobs?
Click to expand...
Click to collapse
I don't have any details on that.

What key combo do you use to access the bootloader? Yes I know about adb reboot bootloader.
Sent from my Nexus 7 using Tapatalk 4 Beta

lol3caring said:
What key combo do you use to access the bootloader? Yes I know about adb reboot bootloader.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Back and Home while powering on.

Unlocked!
Guys, I just unlocked my bootloader! Here's a link for the ADB/Fastboot drivers, and I've attached below a link of what the bootloader unlock screen looks like!
{
"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"
}

jadengore said:
Guys, I just unlocked my bootloader! Here's a link for the ADB/Fastboot drivers, and I've attached below a link of what the bootloader unlock screen looks like!
Click to expand...
Click to collapse
I'll be posting details tomorrow on how to backup your most critical partitions (the ones that cannot be rebuilt if lost).
Stay tuned.

So is it bad that I unlocked today?
Sent from my SHIELD using xda app-developers app

agrabren said:
I'll be posting details tomorrow on how to backup your most critical partitions (the ones that cannot be rebuilt if lost).
Stay tuned.
Click to expand...
Click to collapse
I am really looking forward to your update on backing up the partitions.
After we just need a custom recovery to cleanly push SU to /system.

I can't wait for SU.
With active cooling I can't wait to see how far this SOC can be pushed. :fingers-crossed:

For anyone that cares I was able to re-lock the bootloader but unlike a nexus this is still marked as flagged for a voided warranty.

agrabren said:
I'll be posting details tomorrow on how to backup your most critical partitions (the ones that cannot be rebuilt if lost).
Click to expand...
Click to collapse
Be aware that even backing up all critical partitions does not protect you from permanently bricking your device. I'm thinking about the bootloader partition. If you erase or modify it, Shield will just not be able to boot anymore (because it has to be signed) and you will end with a brick. So don't ever do anything that could tamper with the bootloader. There are a few other partitions that are also needed to boot and that you don't want to mess with.
Partitions like boot, system, or userdata are safe though, and that's enough for all customization needs.

Gnurou said:
Be aware that even backing up all critical partitions does not protect you from permanently bricking your device. I'm thinking about the bootloader partition. If you erase or modify it, Shield will just not be able to boot anymore (because it has to be signed) and you will end with a brick. So don't ever do anything that could tamper with the bootloader. There are a few other partitions that are also needed to boot and that you don't want to mess with.
Partitions like boot, system, or userdata are safe though, and that's enough for all customization needs.
Click to expand...
Click to collapse
Agreed, although I'm somehow doubtful that a signed nvflash image won't make it's way into the light, which can repair a destroyed bootloader (as well as other partitions).

agrabren said:
Agreed, although I'm somehow doubtful that a signed nvflash image won't make it's way into the light, which can repair a destroyed bootloader (as well as other partitions).
Click to expand...
Click to collapse
I agree it would be nice, but for now there are none and it's probably safer to make no assumption about its future availability.

Gnurou said:
I agree it would be nice, but for now there are none and it's probably safer to make no assumption about its future availability.
Click to expand...
Click to collapse
Agreed. Tomorrow I'll check if an unlocked devices allows you to write over the bootloader. I don't *think* it does. I'm not even sure if the required "safe" partitions can be written over. But anyway, still going to get the list for everyone to be safe.

agrabren said:
Agreed. Tomorrow I'll check if an unlocked devices allows you to write over the bootloader. I don't *think* it does.
Click to expand...
Click to collapse
AFAIK it does and I'm not sure you even want to risk trying this . There is no purpose, SHIELD will not boot if the bootloader is changed even the slightest bit anyway, and if anything goes wrong before you restored the bootloader your device will become a brick.
If you want to play with fire anyway, make sure you raw-copied the partition from rooted Android first so you can restore it immediatly after.
And no matter what, don't reboot while the bootloader partition is altered!

Related

[Q] I posted the ICECREAMSANDWICH video and now my phone is locked

What do I do now?
Please explain, locked?
Turn it off if you can. If it's being wiped yank the battery out.
Use adb to install cwr. Then boot back into recovery and make a nandroid backup. Then share it!
Sent from my Nexus S using xda premium
lynyrd65 said:
Please explain, locked?
Turn it off if you can. If it's being wiped yank the battery out.
Click to expand...
Click to collapse
how would I know if it's being wiped?
I'm guessing it would be if Google found out abou it. Or if the phone was stolen.
motu0083 said:
how would I know if it's being wiped?
I'm guessing it would be if Google found out abou it. Or if the phone was stolen.
Click to expand...
Click to collapse
If you can't do anything they are probably trying to. TRY TO TURN IT OFF!
After you turn it off (by any means necessary including yanking the battery), follow the tutorial for rooting you phone then make a nandroid backup of what you have using CWM then mount your phone via USB and upload the back up.
After making a back up you may be able to safely wipe your cache and data. It could provide you with a working phone and provide the rest of us with a nice treat!
lynyrd65 said:
If you can't do anything they are probably trying to. TRY TO TURN IT OFF!
After you turn it off (by any means necessary including yanking the battery), follow the tutorial for rooting you phone then make a nandroid backup of what you have using CWM.
After making a back up you may be able to safely wipe your cache and data. It could provide you with a working phone and us with a nice treat!
Click to expand...
Click to collapse
ok, battery is out.
i'm guessing the lock will not interfere with rooting my phone?
even if i was able to root it, is my phone unuseable now because it's flagged or something?
motu0083 said:
ok, battery is out.
i'm guessing the lock will not interfere with rooting my phone?
even if i was able to root it, is my phone unuseable now because it's flagged or something?
Click to expand...
Click to collapse
Not necessarily, It probably is but I don't know how google's software works. If I had to guess you could probably get it working again by wiping data and cache.
Be sure to remove your sim card as well.
motu0083 said:
ok, battery is out.
i'm guessing the lock will not interfere with rooting my phone?
even if i was able to root it, is my phone unuseable now because it's flagged or something?
Click to expand...
Click to collapse
*Tin Foil Out*.
I'm still confused on how it's "locked"....... *looking over shoulder*
BlackHawkA4 said:
*Tin Foil Out*.
I'm still confused on how it's "locked"....... *looking over shoulder*
Click to expand...
Click to collapse
idk, never experienced it before. I just assume it's what happens when you lose a phone and then remotely secure it so it can't be accessed.
BlackHawkA4 said:
*Tin Foil Out*.
I'm still confused on how it's "locked"....... *looking over shoulder*
Click to expand...
Click to collapse
Google has the ability to force ota to your phone and remote wipe
OP, if your phone works on T-Mobile 3G (not edge) follow this guide up until this point
select Recovery
then it should boot into this screen, if not then repeat the steps to download the image
{
"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"
}
at this point instead of installing a rooted rom go to back up and restore then select Backup.
wait for it to finish then connect your phone to your computer via usb then go back to the main menu and select Mounts and Storage then select mount USB storage.
search for a folder called clockworkmod on your computer and make it into a zip file. If you're awesome then you could upload it to mediafire and post the link.
Next select unmount after copying to your pc then go back to the main menu. Select wipe data/factory reset then select wipe cache partition. The phone is now factory reset and COULD boot.
lynyrd65 said:
Google has the ability to force ota to your phone and remote wipe
OP, if your phone works on T-Mobile 3G (not edge) follow this guide.
Click to expand...
Click to collapse
but wait, what exactly was it doing. I don't remember seeing that posted, lol.
wow Google just OTA'ed your phone.
OTA-OWNED!
This topic is relevant to my interests, but not sure if troll... I'll be watching this

			
				
Either way, I appreciate the entertainment in my last hour of work...
Someone needs to get on IM with this Guy and walk him through the process of dumping the rom.
He should remove sim card and turn off wifi until its backed up.
Sent from my Nexus S using xda premium
I wonder if the other 2 people who posted similar threads have been compromised.
Have i said too much?
Luxferro said:
Someone needs to get on IM with this Guy and walk him through the process of dumping the room.
He should remove sim card and turn off wifi until its backed up.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
battery and sim is out. i'm trying to read up on what im supposed to do now.
motu0083 said:
idk, never experienced it before. I just assume it's what happens when you lose a phone and then remotely secure it so it can't be accessed.
Click to expand...
Click to collapse
hey OP. you need to get ahold of an experienced Android developer so he can walk you through with dumping the OS, etc.
also, post more videos/screenshots of the menus and what not.
thanks!
im taking this thread to twitter. lets see what happens!
aohus said:
hey OP. you need to get ahold of an experienced Android developer so he can walk you through with dumping the OS, etc.
also, post more videos/screenshots of the menus and what not.
thanks!
im taking this thread to twitter. lets see what happens!
Click to expand...
Click to collapse
Don't do that! We'll all be compromised!

[Q] Soft Bricked - No storage - Wont flash stock recovery

I was texting on my phone when it crashed. I was running SlimKat official release with franco kernel 25 for two weeks. Phone had been running great! Now it bootloops on the google logo and doesn't recognize the 32gb of memory. Wont mount any of the partitions in recovery. When in recovery (TWRP) and I opt to reboot to bootloader or reboot is says NO OS. Now as well all I can do with fastboot is relock the phone. I wanted to reflash the recovery to stock as Google will exchange the phone. When I try and flash the stock recovery in the terminal command window everything looks like its flashing good however when I boot into recovery it still boots TWRP.
Help please. :crying:
what do you mean all you can do is relock the phone in fastboot? that doesnt make sense.
what commands are you trying to do when you flash the stock recovery?
Flash the entire factory image. If you get errors your eMMC is probably toast and you should warranty it.
Sent from my Nexus 5
did you use toolkit for rooting?
Simonna said:
did you use toolkit for rooting?
Click to expand...
Click to collapse
You ask because of his troubleshooting expertise or because you think that toolkits and CF.. are killing emmc?
I have seen this problem from people using the manual method and the toolkits as well.
I strongly think that the question to ask is whether they have a 16GB or 32GB phone.
GUGUITOMTG4 said:
You ask because of his troubleshooting expertise or because you think that toolkits and CF.. are killing emmc?
I have seen this problem from people using the manual method and the toolkits as well.
I strongly think that the question to ask is whether they have a 16GB or 32GB phone.
Click to expand...
Click to collapse
I think that toolkits are killing emmc because I saw more users who used toolkits for rooting, and then their phones just dead.But maybe it's just a coincidence..
Toolkits does not kill emmc. This is just coincidence.
emmc died on the phone
Tapatalk-kal küldve az én Nexus 5-el
Simonna said:
I think that toolkits are killing emmc because I saw more users who used toolkits for rooting, and then their phones just dead.But maybe it's just a coincidence..
Click to expand...
Click to collapse
I don't think it's tool kits either. Keep in mind that more people use tool kits than don't. So even though you see more of what appears to be emmc failure with tool kit users there are more of them. I've seen it with people who have not used tool kits a well as those that have.
Sent from my Nexus 5
jd1639 said:
I don't think it's tool kits either. Keep in mind that more people use tool kits than don't. So even though you see more of what appears to be emmc failure with tool kit users there are more of them. I've seen it with people who have not used tool kits a well as those that have.
Sent from my Nexus 5
Click to expand...
Click to collapse
It's not toolkits. It's the luck of the draw. How many N5's sold compared to how many that have had fried nand is what needs to be looked at. That figure is going to be very hard to come by. It could be a normal percentage of failure or it could be high or low. Did Google cheap out on the memory to make the phone more affordable? Or did they put quality memory in and cut some other corners as well as cut their profit margin? All questions that none of us on XDA will, most likely, ever know. The one thing you can be certain of though, toolkits aren't the cause of these failures.
I also had this problem, I couldn't do anyting. I left it sitting there for the night.
The next morning, it booted up like nothing happened
El Daddy said:
Flash the entire factory image. If you get errors your eMMC is probably toast and you should warranty it.
Sent from my Nexus 5
Click to expand...
Click to collapse
Google says they will warranty it however the bootloader wont stay locked and fastboot says it successfully flashes the stock recovery.
But when I reboot the phone into bootloader it says unlocked again and the recovery stays TWRP no matter what I flash. Im lost. It doesn't make any sense....
Looks like I may have to send it in as is however I'm concerned they wont warranty it when they get it back unlocked with TWRP.
{
"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"
}
rooteddesire said:
google says they will warranty it however the bootloader wont stay locked and fastboot says it successfully flashes the stock recovery.
But when i reboot the phone into bootloader it says unlocked again and the recovery stays twrp no matter what i flash. Im lost. It doesn't make any sense....
Looks like i may have to send it in as is however i'm concerned they wont warranty it when they get it back unlocked with twrp.
Click to expand...
Click to collapse
Zepius said:
what do you mean all you can do is relock the phone in fastboot? that doesnt make sense.
what commands are you trying to do when you flash the stock recovery?
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
fastboot oem lock
and so on....
it says its successful, however its obviously not.
RootedDesire said:
fastboot flash recovery recovery.img
fastboot oem lock
and so on....
it says its successful, however its obviously not.
Click to expand...
Click to collapse
Then I reboot and get this
its definitely the stock recovery i extracted and placed in my fastboot folder
RootedDesire said:
Google says they will warranty it however the bootloader wont stay locked and fastboot says it successfully flashes the stock recovery.
But when I reboot the phone into bootloader it says unlocked again and the recovery stays TWRP no matter what I flash. Im lost. It doesn't make any sense....
Looks like I may have to send it in as is however I'm concerned they wont warranty it when they get it back unlocked with TWRP.
Click to expand...
Click to collapse
That's because your eMMC is dead. It can't be written to.
Sent from my Nexus 5
yet another brick in the wall
Just got the same issue. TWRP show internal storage size 0. Can't flash anything. Can't lock.
Is somebody researching this problem? I have several JetFlash USB drives. Sometimes they becomes read-only. But with their software I can "unbrick" these drives. Maybe, we can find a solution for our Nexus 5. I can participate in testing.
XeeV said:
Just got the same issue. TWRP show internal storage size 0. Can't flash anything. Can't lock.
Does somebody researching this problem? I have several JetFlash USB drives. Sometimes they becomes read-only. But with their software I can "unbrick" these drives. Maybe, we can find a solution for our Nexus 5. I can participate in testing.
Click to expand...
Click to collapse
Highly unlikely. AFAIK when your eMMC is dead, it's dead forever.
exb0 said:
Highly unlikely. AFAIK when your eMMC is dead, it's dead forever.
Click to expand...
Click to collapse
But it's not dead. It is readable. I can't write. But, maybe there is a workaround like with JetFlash USB drives. I have 2 JetFlash sticks. They became read-only: I could read, but could't write, even with dd or fdisk (they works OK, but after reinserting everything is as it was before). But there is a software: it erases JetFlash drives and I can write again.
XeeV said:
Just got the same issue. TWRP show internal storage size 0. Can't flash anything. Can't lock.
Is somebody researching this problem? I have several JetFlash USB drives. Sometimes they becomes read-only. But with their software I can "unbrick" these drives. Maybe, we can find a solution for our Nexus 5. I can participate in testing.
Click to expand...
Click to collapse
I had the same issue yesterday, I reflashed stock via fastboot and it fixed the issue, I couldnt flash/wipe/connect to adb or anything, when I tried to mount it showed internal storage size 0, so I went back to the bootloader and flashed all the stock stuff via fastboot and it did the trick for me.
Pawelss said:
I had the same issue yesterday, I reflashed stock via fastboot and it fixed the issue, I couldnt flash/wipe/connect to adb or anything, when I tried to mount it showed internal storage size 0, so I went back to the bootloader and flashed all the stock stuff via fastboot and it did the trick for me.
Click to expand...
Click to collapse
I can reflash a stock, but it writes nothing. It only shows, that it's writing. I can flash CWM instead TWRP. But after a reboot there will be my old TWRP. I can do "fastboot oem lock" and it show "locked", but after reboot it show "unlocked". All is read-only but no errors when writing.
---------- Post added at 09:17 PM ---------- Previous post was at 09:00 PM ----------
Nexus 5 has Sandisk SDIN8DE4. In datasheet there is "Enhanced Write Protection":
----------------------------------------------------------------------------------------------------------------------------------------
To allow the host to protect data against erase or write, the iNAND supports two levels of write
protect command 10 :
• The entire iNAND (including the Boot Area Partitions, General Purpose Area Partition, and
User/Enhanced User Data Area Partition) may be write-protected by setting the permanent
or temporary write protect bits in the CSD.
• Specific segments of the iNAND may be permanently, power-on or temporarily write
protected. Segment size can be programmed via the EXT_CSD register.
For additional information please refer JESD84-A441 standard.
----------------------------------------------------------------------------------------------------------------------------------------
and "H/W Reset":
----------------------------------------------------------------------------------------------------------------------------------------
Hardware reset may be used by host to reset the device, moving the card to a Pre-idle state and
disabling the power-on period write protect on blocks that was set as power-on write protect before
the reset was asserted. For more information, refer to JESD84-A441 standard.
----------------------------------------------------------------------------------------------------------------------------------------
Maybe, there is a way to turn off write protection of just do a hardware reset (but no to loose bootloader)?
Is anybody here familiar with eMMC, chips and JESD84-A441 standard?

[Q] Impossible to flash bootloader/recovery/rom

Hi everyone !
Here I am in a really bad situation...
I bought a second hand phone with a rom issu and the guy who had it told me he ahd no time to waste trying to make it work again, I decided to buy it thinking that nothing could resist a factory reset via ADB.
But, and if I'm here today, it's because I'm in a such a situation, I need some help, and hope you guys can find a solution or at least some leads.
when I got it:
- model 16 GB D821
- The battery was not correctly attached in the phone (i did open it and put it back how it should be and seems to work)
- it is root, bootloader unlock, with Teamwin recovery version 2.6.3.2
- bootloader version HHZ11D
I can launch the teamwin recovery, it's asking for a password when it's starts, i don't know whay BUT I did a data format seeing that some people had some problem with it and did that to fix it
In Teamwin I got 0mb of storage and no OS installed, again it could be fixable via ADB
Now the best !
I can't flash anything on the phone. I can connect to it, it's well detected, I can control it (via ADB or Fastboot) and I can even had a temporary recovery with the nexus toolkit. but:
-Impossible to flash the bootloader, I do everything right, there is not "error" but at the end nothing changes, I'm back with the HHZ11D version and not the latest on I'm trying to get the HHZ11Z.
-Impossible to flash the recovery, same as the bootloader, version teamwin 2.6.3.2.
-impossible to flash a rom, and I don't have one anyway....
Here we are, I think I tried everything, but any clue would be appreciated. I hope I can fix this...
Thanks for your help.
And finally a picture of my fastboot -w when I do one, does it seem normal to you ?
{
"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"
}
Try in fastboot, fastboot oem lock. Then reboot and see if the bootloader is locked. I'm guessing it isn't and your emmc is bad.
Sent from my Nexus 5
nothing will stick, emmc fried.
samersh72 said:
nothing will stick, emmc fried.
Click to expand...
Click to collapse
Is there anything I can do ? Seems not...
Can I change it ?
RealMyop said:
Is there anything I can do ? Seems not...
Can I change it ?
Click to expand...
Click to collapse
No, you're hosed. Rma would be the option but not in your case. You're not going to be able to flash anything.
Sent from my Nexus 5
RealMyop said:
Is there anything I can do ? Seems not...
Can I change it ?
Click to expand...
Click to collapse
Did bootloader get locked?
GUGUITOMTG4 said:
Did bootloader get locked?
Click to expand...
Click to collapse
Yes I can lock back the bootloader.
RealMyop said:
Yes I can lock back the bootloader.
Click to expand...
Click to collapse
If you can lock it, unlock it again then fastboot flash the cache.img from the factory image
Sent from my Nexus 5
You may be lucky. here you will find the cache.img on method 2. If it doesn't work, do the method 1
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
GUGUITOMTG4 said:
You may be lucky. here you will find the cache.img on method 2. If it doesn't work, do the method 1
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
I did try and it's not working either... Is there a part in the phone I can change to fix this ?
RealMyop said:
I did try and it's not working either... Is there a part in the phone I can change to fix this ?
Click to expand...
Click to collapse
The mother board
Sent from my SAMSUNG-SGH-I727

Bricked? + FRP Moto G 3

Hello,
I have ran out of things to try with this phone - hoping someone out there knows if there is something that can be done.
Was given the device to remove the FRP (Factory reset protection). I set up fastboot, adb drivers and started messing around with it.
First of all, I tried upgrading to the newest MM version for it using the official images from the Motorola website - turns out it does not remove the google account lock, and the version was different than the ones they use in the 'FRP bypass' videos.
Then, I tried downgrading it to 5.1.1 (the same way I did to MM, using fastboot), and some of the commands failed - resulting in the phone not booting up, unless I go straight for the Vol down + power button to get to the bootloader.
Lastly, I tried flashing an older version of MM, only to get 'failed to validate system image' on boot (picture below). Is there something that could fix this/remove the damn FRP? The warranty does not matter, the thing is unusable - any kind of ROM etc. would do. Debugging is disabled.
{
"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"
}
The loader, currently:
was the phone stolen? because why would anyone hard reset their device, just asking.
dont know any solution for you
and btw.. NEVER try to downgrade your device it can cause problems, as you see
Not sure, it was given as a collateral for a job or something, and the guy disappeared. Basically, it is either try and make it usable or just throw it away. Trying to figure out what are the options at the moment.
HelpMeruth said:
was the phone stolen? because why would anyone hard reset their device, just asking.
dont know any solution for you
and btw.. NEVER try to downgrade your device it can cause problems, as you see
Click to expand...
Click to collapse
You need to re-flash the latest firmware you flashed to your device boot again. To downgrade you have to unlock the bootloader first, but the OEM unlock setting in developer settings must be turned on, what I think you can't do with the FRP lock.
coolizard said:
You need to re-flash the latest firmware you flashed to your device boot again. To downgrade you have to unlock the bootloader first, but the OEM unlock setting in developer settings must be turned on, what I think you can't do with the FRP lock.
Click to expand...
Click to collapse
Ok, I flashed it again, it's 6.0.0. I even managed to get into the settings by doing the usual FRP bypass, however, this version does not have the developer options enabled by clicking the build number, and the 'users' setting is not there, therefore I cannot enable USB debugging like everyone does.
Your first error was upgrading to the latest version, because the newest version they have fixed.
I don't know if this will help, but in fastboot mode try to format system, and reflash the stock!
ExaHamza said:
Your first error was upgrading to the latest version, because the newest version they have fixed.
I don't know if this will help, but in fastboot mode try to format system, and reflash the stock!
Click to expand...
Click to collapse
I realize my mistake now :/ Tried formatting, reflashing.. I guess it's called Factory Reset Protection for a reason eh
Enirox said:
I realize my mistake now :/ Tried formatting, reflashing.. I guess it's called Factory Reset Protection for a reason eh
Click to expand...
Click to collapse
have you unlocked?
Sent from my MotoG3 using Tapatalk
ExaHamza said:
have you unlocked?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
No, I have not. Had a real laugh though - I was able to access the settings - disable setup wizard - open chrome using google now, download apk's (like nova launcher) and have a home screen, browse apps all while FRP'ed. No go on the debugging/reset though :crying:
If can install apps try to root it with kingroot, and replace the stock recovery with TWRP, then format everything, and put another ROM into, after that reflash your stock. I don't know if you can do this without unlocking the bootloader.
I have seen some devices allowing do root + TWRP, without unlocking the bootloader. But you can try it!
Sent from my MotoG3 using Tapatalk

Root?

Is the zs551kl officially bootloader-unlockable and able to be rooted?
If that's the case, it would mean it's a much better phone than many of the latest flagships: sdcard, jack, FM radio, dual SIM, larger battery, stereo speakers, more complete GPS, good resolution screen, etc.
I haven't seen anything yet, but I assume it's coming. I don't think there will be a lot of roms though.
Let's pray that someone popup with that
rblanca said:
Let's pray that someone popup with that
Click to expand...
Click to collapse
Have you got this device? There is aTWRP available, but I'm not sure if anyone has successfully rooted, etc.
temporarium said:
Have you got this device? There is aTWRP available, but I'm not sure if anyone has successfully rooted, etc.
Click to expand...
Click to collapse
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader....but ASUS has made public the app to unlock the bootloader.
---------- Post added at 11:41 PM ---------- Previous post was at 11:33 PM ----------
temporarium said:
Have you got this device? There is aTWRP available, but I'm not sure if anyone has successfully rooted, etc.
Click to expand...
Click to collapse
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader neither install TWRP ....but ASUS has made public the app to unlock it.
rblanca said:
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader....but ASUS has made public the app to unlock the bootloader.
Click to expand...
Click to collapse
Have you tried this?
https://forum.xda-developers.com/zenfone-4-pro/development/recovery-twrp-3-1-1-0-zs551kl-t3692186
All you need is a way to flash root.
rblanca said:
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader....but ASUS has made public the app to unlock the bootloader.
Click to expand...
Click to collapse
Out of curiosity, what made you choose this phone over all the others? How do you like it so far? Pros\cons?
temporarium said:
Have you tried this?
https://forum.xda-developers.com/zenfone-4-pro/development/recovery-twrp-3-1-1-0-zs551kl-t3692186
All you need is a way to flash root.
Click to expand...
Click to collapse
No, because , like I said before...until we have a Rooted kernel available to download or a custom rom to install there is no point on install TWRP or unlock the bootloader....I'm pretty sure that in the next months there are going to be Roms and Custom Kernels (Rooted), it's too soon the phone was released on October (the past month).
About what made me chose this phone...it was
- Unlockeable Bootloader
- Snapdragon 835 as CPU
- 6 GB of Ram
- Good camera
- ASUS it's a good brand.
- FM raido
The phone its pretty damn fast...multitasking is amaizing...the battery dont seems so well like my, now broken, LG G5 but at least it runs for 1 day and a few hours but maybe its due the "new phone effect" (you play with it more the first days of use XD)
Magisk should give you root as long as bootloader can be unlocked.
I'll watch this space for root as I'm about to go get one myself because Snapdragon 835, then I have 15 days to test it on one game to decide whether to keep or return, lol.
motopig said:
Magisk should give you root as long as bootloader can be unlocked.
I'll watch this space for root as I'm about to go get one myself because Snapdragon 835, then I have 15 days to test it on one game to decide whether to keep or return, lol.
Click to expand...
Click to collapse
That's what I thought: once you unlock the bootloader and ADB-flash TWRP, you should be able to install SuperSU or Magisk (with corresponding manager app) and be good to go. So please test and let us know if you can.
temporarium said:
That's what I thought: once you unlock the bootloader and ADB-flash TWRP, you should be able to install SuperSU or Magisk (with corresponding manager app) and be good to go. So please test and let us know if you can.
Click to expand...
Click to collapse
Sorry to disappoint you but I'm not going to unlock my bootloader right now....the reason the phone its new (and expensive), there isn't a single rom to install or kernel to flash (on my LG G5 you have to flash another kernel in order to have root, but maybe that has change).
More importante there isnt any unbrick guide yet if something fails plus my phone it's not being selled on my country so there isn't any kind of warranty or repair service if something fails. WIth 6gb of ram I can deal with some ASUS apps pre installed so I dont need to root it right now.
But like a said before...its a great phone...damn faster one! i'll recommend it.
Even if one wanted to unlock the bootloader to try things out, it is not possible right now anyway.
Tried it with Asus' official unlock app (just got the phone today! :victory, and the app simply crashes before it even gets to talk to the bootloader, so there is currently no way to do it. Fastboot still reports the device as locked.
Maybe I should have tried it before applying the latest OTA update, but oh well!
rblanca has a point though, with no way to restore the phone should something go seriously wrong, I won't try any more exotic methods to try to crack open that bootloader at the moment either. The various guides that float around on the web look dangerous at best.
rblanca said:
Sorry to disappoint you but I'm not going to unlock my bootloader right now....the reason the phone its new (and expensive), there isn't a single rom to install or kernel to flash (on my LG G5 you have to flash another kernel in order to have root, but maybe that has change).
More importante there isnt any unbrick guide yet if something fails plus my phone it's not being selled on my country so there isn't any kind of warranty or repair service if something fails. WIth 6gb of ram I can deal with some ASUS apps pre installed so I dont need to root it right now.
But like a said before...its a great phone...damn faster one! i'll recommend it.
Click to expand...
Click to collapse
I understand your concern. No worries!
damnaliens said:
Even if one wanted to unlock the bootloader to try things out, it is not possible right now anyway.
Tried it with Asus' official unlock app (just got the phone today! :victory, and the app simply crashes before it even gets to talk to the bootloader, so there is currently no way to do it. Fastboot still reports the device as locked.
Maybe I should have tried it before applying the latest OTA update, but oh well!
rblanca has a point though, with no way to restore the phone should something go seriously wrong, I won't try any more exotic methods to try to crack open that bootloader at the moment either. The various guides that float around on the web look dangerous at best.
Click to expand...
Click to collapse
We'll just have to sit tight.
Root!
Good news!
Asus fixed the unlock app ( https://www.asus.com/de/Phone/ZenFone-4-Pro-ZS551KL/HelpDesk_Download/ ) and bumped it to version 9.1.0.0
It now successfully unlocks the device's bootloader. I went ahead and did it since I already voided my warranty when trying to unlock it with the previous, bugged version anyway.
Works fine, fastboot reports the bootloader as unlocked. Device contents got factory-wiped as per announced in the app, so make sure to back up your things if you wanna do it. :silly:
Edit:
Aaaaand rooted with Magisk.
{
"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"
}
After installing TWRP I just followed this guide here: https://forum.xda-developers.com/ze...ide-how-to-root-acces-magisk-manager-t3678678
Applies 1:1 to the Zenfone 4 Pro as well and worked flawlessly. :fingers-crossed:
Nice work! Does Android Pay work with magisk on this phone?
@bahua78
Android Pay isn't available in my country yet, so I can't test this. Maybe somebody else can find out. :0
Is it possible to update firmware via a memory card with root?

Categories

Resources