Related
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
this seems more like a user made htc dev, not what true s-off "bootloader unlocked" would be. non the less it should work fine. this probably wont touch the write enabled protection on the device. the only issues i see is until we are truly unlocked we will always have that "samsung custom" on out bootscreens.
spyz88 said:
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
Click to expand...
Click to collapse
He released his source code and such so we need to have someone compile it into a .bat or .exe so we can flash a custom recovery/rom
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
shabbypenguin said:
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
Click to expand...
Click to collapse
well i cant use it as i don't use linux lol.
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
fix-this! said:
well i cant use it as i don't use linux lol.
Click to expand...
Click to collapse
well if you dont use linux you cant make kernels or recoveries
luckily the loki_flash utility that is used to actually put the patched img onto the device works on android so it doenst matter what kind of computer you have
alacrify said:
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
Click to expand...
Click to collapse
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
just means soon we will have bootloader unlocked.... patience
lorijuan1024 said:
just means soon we will have bootloader unlocked.... patience
Click to expand...
Click to collapse
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Bjray said:
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
Click to expand...
Click to collapse
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Update: nand backup was successful. Good start for us, just need the perm fix, but for now, it rocks, it was so nice to see the recovery screen. SWEET
TheAxman said:
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Click to expand...
Click to collapse
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
fix-this! said:
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Click to expand...
Click to collapse
what i meant was a tool that us people that aren't good with the programming language can use.
fix-this! said:
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
Click to expand...
Click to collapse
Agreed, but I do have a jtag box here in hand, and there is no fix for that either, I might have one phone down soon..:
Incoming update from Samsung in 3....2....1.....
I flashed what shabbypenguin provided in his recovery thread and now have a working recovery on my ATT i337!!! :laugh::good::highfive::fingers-crossed:
Thanks to djrbliss for his awesome work!
mr_blanket said:
Incoming update from Samsung in 3....2....1.....
Click to expand...
Click to collapse
simple solution is to not take the OTA. but yes, i see one coming to.
fix-this! said:
simple solution is to not take the OTA. but yes, i see one coming to.
Click to expand...
Click to collapse
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
mattdm said:
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
Click to expand...
Click to collapse
hopefully adam can get us a more permanent solution. but props to dan for his tool.
Couldn't be happier after I get home from watching the hangover I get to unlock this bad boy
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Hi,
I have installed TWRP and OpenKirin RROS rom, but not satisfied, so I'm looking for how to
relock bootloader, and return to stock EMUI.
My google skills seems to be lost today, as I cant find anything on how to restor the phone.
Anyone here that maybe can help me ?
EDIT: cant pass "your device has been unlocked" ... cant reach anything in the phone, only get bootloop
Best regards
LINJEinc
LINJEinc said:
Hi,
I have installed TWRP and OpenKirin RROS rom, but not satisfied, so I'm looking for how to
relock bootloader, and return to stock EMUI.
My google skills seems to be lost today, as I cant find anything on how to restor the phone.
Anyone here that maybe can help me ?
EDIT: cant pass "your device has been unlocked" ... cant reach anything in the phone, only get bootloop
Best regards
LINJEinc
Click to expand...
Click to collapse
Have you tried reflashing through erecovery?
adriansticoid said:
Have you tried reflashing through erecovery?
Click to expand...
Click to collapse
The thing is, only thing that happen with any button combo is the blue honor screen, no more.
But I have started a ticket at huawei, to see what they say, but i guess it's service.
LINJEinc said:
The thing is, only thing that happen with any button combo is the blue honor screen, no more.
But I have started a ticket at huawei, to see what they say, but i guess it's service.
Click to expand...
Click to collapse
What steps have you done before this happened?
adriansticoid said:
What steps have you done before this happened?
Click to expand...
Click to collapse
After flashing OpenKirin, and not being satisfied, all i did was following the steps to restore
the phone back to stock, flashed original recovery, locked the bootloader, but after all was
done and it was time to reboot, all i got was the blue honor screen, and nothing worked.
LINJEinc said:
After flashing OpenKirin, and not being satisfied, all i did was following the steps to restore
the phone back to stock, flashed original recovery, locked the bootloader, but after all was
done and it was time to reboot, all i got was the blue honor screen, and nothing worked.
Click to expand...
Click to collapse
Do this now:
Boot to fastboot and unlock bootloader
Then flash TWRP latest version
Then flash the B380/381 firmware zip files with the hw zip file before the update.zip
It should now boot properly and you can relock bootloader after that if you want to.
LINJEinc said:
After flashing OpenKirin, and not being satisfied, all i did was following the steps to restore
the phone back to stock, flashed original recovery, locked the bootloader, but after all was
done and it was time to reboot, all i got was the blue honor screen, and nothing worked.
Click to expand...
Click to collapse
I encountered this too. Have you tried wiping data in recovery?
Sent from my Honor 8 using XDA Labs
@Anonshe : I can't even enter fastboot, that is my big problem @adriansticoid : I can't enter anything, all button combos only starts to the blue honor screen, and no more
LINJEinc said:
I can't even enter fastboot, that is my big problem
Click to expand...
Click to collapse
Just shut down your phone then while holding the volume down button connect the cable to your phone. If it still doesn't work try changing cables. You surely can enter fastboot mode regardless of what you have done.
LINJEinc said:
@Anonshe : I can't even enter fastboot, that is my big problem @adriansticoid : I can't enter anything, all button combos only starts to the blue honor screen, and no more
Click to expand...
Click to collapse
That's bad. You might wanna consider the service center.
Sent from my Honor 8 using XDA Labs
@Anonshe: tried four different cables, same thing happens. @adriansticoid: I have a open ticket at huwaei, to see what they have to say, and I guess it will be service.
LINJEinc said:
@Anonshe: tried four different cables, same thing happens. @adriansticoid: I have a open ticket at huwaei, to see what they have to say, and I guess it will be service.
Click to expand...
Click to collapse
Goodluck with that man. I hope you fix it.
Sent from my Honor 8 using XDA Labs
Anonshe said:
Do this now:
Boot to fastboot and unlock bootloader
Then flash TWRP latest version
Then flash the B380/381 firmware zip files with the hw zip file before the update.zip
It should now boot properly and you can relock bootloader after that if you want to.
Click to expand...
Click to collapse
adriansticoid said:
I encountered this too. Have you tried wiping data in recovery?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Now I come so far that the bootloader is unlocked again and twrp installed.
But I can't find B380 zip files, but maybe i'm blind or have bad google skills after having problems
with the phone a few days
LINJEinc said:
Now I come so far that the bootloader is unlocked again and twrp installed.
But I can't find B380 zip files, but maybe i'm blind or have bad google skills after having problems
with the phone a few days
Click to expand...
Click to collapse
You can install a custom ROM for the moment so you can use your phone. I'll search for it later I'm just a bit busy right now.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
You can install a custom ROM for the moment so you can use your phone. I'll search for it later I'm just a bit busy right now.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
looks like it may be solved for me at the moment.
crossing my fingers and typing is hard
LINJEinc said:
looks like it may be solved for me at the moment.
crossing my fingers and typing is hard
Click to expand...
Click to collapse
Glad that you fixed it.
Sent from my Honor 8 using XDA Labs
Is a tone working on this at all by chance? Just curious? .aybe point me in the direction of a sick thread or something please and thank you!
Slipknot8Wwe said:
Is a tone working on this at all by chance? !
Click to expand...
Click to collapse
Nope and never will. There probably is a chance right now if a good programmer could cipher through the mechanism by which the pixel 2 fastboot bug is being exploited. The bug more than likely exists on all pixels. Just need to figure out the proper code to send.
Unfortunately it's beyond my skill set.
Sent from my Pixel using Tapatalk
Feel free to try the ADB command "fastboot flashing lock_critical" Was going to try it later this afternoon. Know that its working for the Pixel2 on 8.1
b00ster23 said:
Feel free to try the ADB command "fastboot flashing lock_critical" Was going to try it later this afternoon. Know that its working for the Pixel2 on 8.1
Click to expand...
Click to collapse
I tried it as well as some xl and 2xl people. It only works on the 2. An assembly language programmer with a debugger might be able to trick the other pixels into thinking they're a 2 and unlock. All I know is a possible way, not the how. I keep typing this in hopes a programmer might see it and give it a shot.
Sent from my Pixel using Tapatalk
b00ster23 said:
Feel free to try the ADB command "fastboot flashing lock_critical" Was going to try it later this afternoon. Know that its working for the Pixel2 on 8.1
Click to expand...
Click to collapse
Ya I've all ready tried it
baknblack said:
I tried it as well as some xl and 2xl people. It only works on the 2. An assembly language programmer with a debugger might be able to trick the other pixels into thinking they're a 2 and unlock. All I know is a possible way, not the how. I keep typing this in hopes a programmer might see it and give it a shot.
Click to expand...
Click to collapse
That's mainly why I posted it to potentially light a fire under someone's ass. I could not imagine that there is not a way.
baknblack said:
Nope and never will. There probably is a chance right now if a good programmer could cipher through the mechanism by which the pixel 2 fastboot bug is being exploited. The bug more than likely exists on all pixels. Just need to figure out the proper code to send.
Unfortunately it's beyond my skill set.
Click to expand...
Click to collapse
Ya same with me. I've tried everything that I can think of and have researched for all past commands for bootloader unlock.
after update experienced problem with BLOD.
after freezing I've managed to boot but for short time.
is there any fix that available like for nexus6p and nexus5x?
Can you get to fastboot/bootloader?
yes, except bootloader locked. can't get enough time to unlock it in settings
Tried to boot recovery from bootloader? I believe it's possible to flash a full ota image with lock bootloader, but someone correct me if i am wrong.
Cheers
Sent from my Google Pixel using XDA Labs
thanks for suggesting, but it wouldn't fix the phone. in order to get to recovery i still have to heat up phone to start appropriately
guotti said:
thanks for suggesting, but it wouldn't fix the phone. in order to get to recovery i still have to heat up phone to start appropriately
Click to expand...
Click to collapse
Have you uhhhhhhhh /tried it/
KittyRgnarok said:
Have you uhhhhhhhh /tried it/
Click to expand...
Click to collapse
yes, the phone reboots before finish
So, it is heating when you try booting bootloader and then recovery?
Sent from my Google Pixel using XDA Labs
yep, it won't start without heating
So it's heating itself even when booted to only bootloader?
That's very weird, never heard of that before.
When that's the case, maybe it's time for a replacement
Any warranty left maybe?
Sent from my Google Pixel using XDA Labs
Sgace said:
Tried to boot recovery from bootloader? I believe it's possible to flash a full ota image with lock bootloader, but someone correct me if i am wrong.
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Cosmic Radiation said:
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Click to expand...
Click to collapse
If it's bootlooping, how did you see OEM unlock is greyed out?
Sent from my Google Pixel using XDA Labs
Cosmic Radiation said:
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Click to expand...
Click to collapse
I have 2 Pixels that both have the same symptom. I was lucky enough to get them to boot so I could unlock the bootloader, but flashing the factory image didn't make any difference. Based on what I've seen on the Google forums, it appears some of theses devices have faulty memory which is most likely the cause of the bootloop. Both of mine have Samsung memory. I'd be curious if your device does as well.
Sgace said:
If it's bootlooping, how did you see OEM unlock is greyed out?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
jman315 said:
I have 2 Pixels that both have the same symptom. I was lucky enough to get them to boot so I could unlock the bootloader, but flashing the factory image didn't make any difference. Based on what I've seen on the Google forums, it appears some of theses devices have faulty memory which is most likely the cause of the bootloop. Both of mine have Samsung memory. I'd be curious if your device does as well.
Click to expand...
Click to collapse
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Cosmic Radiation said:
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Click to expand...
Click to collapse
Do you have a Verizon pixel maybe? Cause OEM unlock should not be grayed out, even with locked bootloader.
Sent from my Google Pixel using XDA Labs
Cosmic Radiation said:
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Click to expand...
Click to collapse
No, neither device is reliable or usable. Sometimes after it's been off for a while, it will power on and be functional for a short period of time. If the memory is faulty, then I believe the motherboard has to be replaced which isn't worth the cost of the repair. I may contact google support and see if they may give me a trade in credit for a pixel 2 or 3.
my pixel turned out to be verizon, i was able to unlock bootloader and flash a factory image.. The problem still exists. Bootloops are still happening:crying:
Cosmic Radiation said:
my pixel turned out to be verizon, i was able to unlock bootloader and flash a factory image.. The problem still exists. Bootloops are still happening:crying:
Click to expand...
Click to collapse
Yep. Same issue here. Our devices are likely paperweights I'm afraid.
Can confirm, I woke up to an infinite bootloop this morning after applying the December security patch. Seems to be a hardware issue that just kills the phone.
Have you guys have tried to cool the phone down like putting it on top of an ice bag with saltwater, like a zip lock bag, give it a minute on top of the brine and then try? Should give you some time until you can get into the rom and tap the unlock button?
I was just curious when you guys put it in fastboot mode what does your device say. most of everything in mine is blank, when I was on the pixel this is how I always made sure my bootloader was updated. I wish I would have paid attention when I was stock to see if it was blank there too.
mac796 said:
I was just curious when you guys put it in fastboot mode what does your device say. most of everything in mine is blank, when I was on the pixel this is how I always made sure my bootloader was updated. I wish I would have paid attention when I was stock to see if it was blank there too.
Click to expand...
Click to collapse
It should look like this https://www.google.com/search?q=one...UIEigD&biw=1920&bih=969#imgrc=TYY0oOveTbDeSM:
whatthekj said:
It should look like this https://www.google.com/search?q=one...UIEigD&biw=1920&bih=969#imgrc=TYY0oOveTbDeSM:
Click to expand...
Click to collapse
Weird it doesn't give you the version
mac796 said:
Weird it doesn't give you the version
Click to expand...
Click to collapse
Is that the screen youre getting on your OP7P or something else?
whatthekj said:
Is that the screen youre getting on your OP7P or something else?
Click to expand...
Click to collapse
No that's it. Is that what yours shows. Or does it give you the bootloader info?
mac796 said:
No that's it. Is that what yours shows. Or does it give you the bootloader info?
Click to expand...
Click to collapse
Its what mine shows as well. No bootloader info.