I've tried to lock the bootloader. But after locking the bootloader the phone restarts and shows the message that Can't Find Valid Operating System.
In FastBoot Mode it shows:
Secure Boot -Yes
Device State - Locked
My Bootloader Version - TMZ20k
Baseband Version - g8998-00253-1809191716
What's the solution?
Hope you didn't try to lock the bootloader without being fully stock...
If so, you've just bricked your phone.
If you're fully stock, you can bootloader unlock the phone again and start over.
ilal2ielli said:
Hope you didn't try to lock the bootloader without being fully stock...
If so, you've just bricked your phone.
If you're fully stock, you can bootloader unlock the phone again and start over.
Click to expand...
Click to collapse
The phone was in full stock.
I didn't changed any rom.
How can I unlock the phone again and start over?
msnahad98 said:
The phone was in full stock.
I didn't changed any rom.
How can I unlock the phone again and start over?
Click to expand...
Click to collapse
does your computer recognize your phone?
if so make sure you have up to date adb/fastboot
boot into bootloader then open command prompt
type fastboot flashing_unlock
why did you relock your bootloader?
maybe try deuce's script or the all in one tool. They're pretty handy
Edmontonchef said:
does your computer recognize your phone?
if so make sure you have up to date adb/fastboot
boot into bootloader then open command prompt
type fastboot flashing_unlock
why did you relock your bootloader?
maybe try deuce's script or the all in one tool. They're pretty handy
Click to expand...
Click to collapse
Yes My Computer recognize my phone.
After entering this command "fastboot flashing unlock"
It Shows:
FAILED (remote: 'Flashing Unlock is not allowed')
Have you tried adb sideloading an ota file?
If that doesn't work I'm not sure what else you can do.
msnahad98 said:
I've tried to lock the bootloader. But after locking the bootloader the phone restarts and shows the message that Can't Find Valid Operating System.
In FastBoot Mode it shows:
Secure Boot -Yes
Device State - Locked
My Bootloader Version - TMZ20k
Baseband Version - g8998-00253-1809191716
What's the solution?
Click to expand...
Click to collapse
By chance did you turn off OEM unlocking and USB debugging before you locked the bootloader? If so, it's......Brickhouse time! :fingers-crossed:
Badger50 said:
By chance did you turn off OEM unlocking and USB debugging before you locked the bootloader? If so, it's......Brickhouse time! :fingers-crossed:
Click to expand...
Click to collapse
Yes unfortunately I've turned off OEM unlocking and USB debugging before locking the bootloader.
Isn't there any kind of solution???:crying:
If you're under warranty you can return it.
Edmontonchef said:
If you're under warranty you can return it.
Click to expand...
Click to collapse
I don't have any warranty.
msnahad98 said:
Yes unfortunately I've turned off OEM unlocking and USB debugging before locking the bootloader.
Isn't there any kind of solution???:crying:
Click to expand...
Click to collapse
msnahad98 said:
I don't have any warranty.
Click to expand...
Click to collapse
You could try sideloading the OTA through stock recovery like @Edmontonchef suggested. I don't think it'll work, but at this point, anything is worth a try.
Could somebody PLEASE sticky a warning on every section to NOT RELOCK BOOTLOADER?? Pretty please??
CyberpodS2 said:
Could somebody PLEASE sticky a warning on every section to NOT RELOCK BOOTLOADER?? Pretty please??
Click to expand...
Click to collapse
While that would be nice my friend, I also think that there is enough information out there already that if users were willing to search for it, they would find out quickly that this is a no no. Unless of course, it's done in the correct manner. :fingers-crossed:
Why did you relock the bootloader? What advantage did you expect to gain from that?
CyberpodS2 said:
Could somebody PLEASE sticky a warning on every section to NOT RELOCK BOOTLOADER?? Pretty please??
Click to expand...
Click to collapse
Badger50 said:
While that would be nice my friend, I also think that there is enough information out there already that if users were willing to search for it, they would find out quickly that this is a no no. Unless of course, it's done in the correct manner. :fingers-crossed:
Click to expand...
Click to collapse
You mean, put THAT sticky right next to the sticky that states, SEARCH FIRST, or the one that states "generic questions belong in the Q&A section for each device"?
Edited out of compassion
Az Biker said:
You mean, put THAT sticky right next to the sticky that states, SEARCH FIRST?
Or next to the sticky that states "generic questions belong in the Q&A section for each device"?
Or any of the other 100s of stickies that the vast majority never read?
Those stickies?
I'm actually AMAZED at the "right now, immediate gratification" mentality of so many people nowadays.
I have this $800+ device, I want to customize it, what should I do first?
1) read the OPs and research the guides for my device PRIOR to messing with it,
or
2) skip all the research and OPs and flash my new device the way I flashed my Note 3 from five years ago?
Who in their ever loving right mind picks 2??????
Click to expand...
Click to collapse
Amen by brother! No truer words have ever been spoken! :good:
Badger50 said:
Amen by brother! No truer words have ever been spoken! :good:
Click to expand...
Click to collapse
I feel bad for new members like the OP. No doubt this will be a learning moment for him, and he seems sharp enough that I think he'll be okay down the road and will do the research needed before customizing his devices.
The members who have been with Xda for years and STILL don't research, read OPs, read stickies.... those are the folks who chap my hide
Az Biker said:
I feel bad for new members like the OP. No doubt this will be a learning moment for him, and he seems sharp enough that I think he'll be okay down the road and will do the research needed before customizing his devices.
The members who have been with Xda for years and STILL don't research, read OPs, read stickies.... those are the folks who chap my hide
Click to expand...
Click to collapse
Yeah, don't let it get ya down Hoss! Some folks just like learning things the hard way I reckon. We both did. And, in the long run, they'll be better off for it :good:
Related
OK so we got a SE Experia Arc S LT18i with 1253-8238_4.0.1.A.0.165 ('prototype' model on loan from a friend = prehistoric!) and looking into upgrading the thing if at all possible.
So if I am correct it's a case of: 1st: Root, 2nd: Unlock bootloader, 3rd: Install recovery, 4th: Flash ROM of choice
Bootloader is locked and phone not rooted.
Tried using Flashtool to root phone but it is greyed out so tried Tools > Root > Force zergRush = fail, (not tried Force psneuter/Emulator ?)
Tried unlocking bootloader using Flashtool, but this also failed (SE unlock website wanted IMEI code one digit less than the phone reports?!! got a code by ditching the first 0 of the IMEI, but didn't work anyway - crashed phone)
Attempted to root using command line ADB method to push zergRush and execute the script, but this too doesn't work (phone crashes and reboots).
Fastboot? I have it installed but not yet come across any how-to's that use this (did I say yet? )
The apps available on Play Store seem to be automations of above methods for one-click users.
Further exhaustive reading/searching here and on talk.sonymobile.com leads me to believe that the first step might be to flash a different kernel version before it's possible to root, after which everything else should fall into place...I'm up for trying this but of course don't want to risk bricking the phone, so backing up first would be a good plan, *but* I need root to be able to install recovery! I know enough about booting operating systems to know that changing kernel version with a locked boot loader might just result in bork! This is where the expertise of you guys comes in!! Maybe you know that flashing another (similar?) kernel will be fine with Fashtool even without unlocking bootloader and rooting phone? Perhaps I missed a simple and easy way of rooting? Any suggestions very welcome - thanks in advance!
FYI: *I only run Linux* so pointing me at any of the windows tools on offer is of no help to me
Oh and PS: yes I have searched and found a ton of helpful info, well actually *way too much* info to the point of saturation and confusion!! :laugh:
There can never be too much information, yours and others problem is that you try rushing through it, because if you didn't you'd find the answers you were looking for.
Sent from my CM9'd Arc
XperienceD said:
There can never be too much information, yours and others problem is that you try rushing through it, because if you didn't you'd find the answers you were looking for.
Sent from my CM9'd Arc
Click to expand...
Click to collapse
Well it's not the quantity of info, but the quality of info! Failing that the filtration system used to distill the good stuff out!
Anyroads, I was still hoping for someone to chip in with something like "Yeah go for it, that will work fine"! or "Don't do it, try this instead"!
I'm believing from my readings so far, that short of flashing an incorrect radio, or interrupting a flash process, it isn't easily possible to brick an Arc?
acesabe said:
Anyroads, I was still hoping for someone to chip in with something like "Yeah go for it, that will work fine"!
Click to expand...
Click to collapse
I would have just tried it instead of starting a thread to ask, failing that I would have then read the stickys/guides explaining how to unlock and root.
acesabe said:
it isn't easily possible to brick an Arc?
Click to expand...
Click to collapse
No, you would just use the flashtool to flash a stock ROM.
XperienceD said:
I would have just tried it instead of starting a thread to ask, failing that I would have then read the stickys/guides explaining how to unlock and root.
Click to expand...
Click to collapse
Well, that's because you are XperienceD!
No, you would just use the flashtool to flash a stock ROM.
Click to expand...
Click to collapse
Ok cool, so Flashtool can be used to save an unbootable device too then...
acesabe said:
Well, that's because you are XperienceD!
Click to expand...
Click to collapse
It's how I got to be experienced. :silly:
acesabe said:
Ok cool, so Flashtool can be used to save an unbootable device too then...
Click to expand...
Click to collapse
Yep, you just need to flash a stock ROM.
XperienceD said:
I would have just tried it instead of starting a thread to ask, failing that I would have then read the stickys/guides explaining how to unlock and root.
Click to expand...
Click to collapse
Me too.
Thread closed.
[SOLVED] I followed this thread to get everything updated and make sure I was all stock, and then went to bootloader and ran fastboot flashing lock to relock the bootloader. Everything working great now.
I'm trading my Verizon Pixel XL for a normal Pixel, and need to relock the bootloader first. I haven't installed a custom kernal or ROMs or anything, so can I just lock via fastboot safely?
I don't want to do something that will brick it!
I'm aware this is stupid and I'd rather just leave it, but dude is sketched out by warning on startup and won't trade till it's gone :/
Thanks!
[Edit] it should maybe be noted that I haven't installed any updates since rooting, and I'm not sure if those are important first or not?
burnface said:
[SOLVED] I followed this thread to get everything updated and make sure I was all stock, and then went to bootloader and ran fastboot flashing lock to relock the bootloader. Everything working great now.
I'm trading my Verizon Pixel XL for a normal Pixel, and need to relock the bootloader first. I haven't installed a custom kernal or ROMs or anything, so can I just lock via fastboot safely?
I don't want to do something that will brick it!
I'm aware this is stupid and I'd rather just leave it, but dude is sketched out by warning on startup and won't trade till it's gone :/
Thanks!
[Edit] it should maybe be noted that I haven't installed any updates since rooting, and I'm not sure if those are important first or not?
Click to expand...
Click to collapse
Hey man, do you remember which FW built were you on ? NDE63X ?
andrep182 said:
Hey man, do you remember which FW built were you on ? NDE63X ?
Click to expand...
Click to collapse
Yes if you are stock you can safely lock the bootloader.
run
fastboot flashing lock
phone will factory reset and appear frozen on that screen 30seconds or so.
milan187 said:
Yes if you are stock you can safely lock the bootloader.
run
fastboot flashing lock
phone will factory reset and appear frozen on that screen 30seconds or so.
Click to expand...
Click to collapse
Cool man, thanks!
andrep182 said:
Hey man, do you remember which FW built were you on ? NDE63X ?
Click to expand...
Click to collapse
Damn. I honestly don't remember... I didn't do enough with that phone for anything specific to stick out.. Sorry!
burnface said:
Damn. I honestly don't remember... I didn't do enough with that phone for anything specific to stick out.. Sorry!
Click to expand...
Click to collapse
It's all good man. My heart was pounding as I about to hit 'yes' for locking my bootloader. Did the deed and all is well =) Thanks!
This is my 4th LG phone but this is giving me problems even unlocking the bootloader. Any help would be appreciated.
Is this of any help?
https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-k20-plus-t3616248
Professor Woland said:
Is this of any help?
https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-k20-plus-t3616248
Click to expand...
Click to collapse
I wish. At&t has the bootloader locked down. All the other steps will probably work. Twrp would have to be built for M255. Thanks for the response.
So, you don't have "allow device to be OEM unlocked" option in developer options?
Professor Woland said:
So, you don't have "allow device to be OEM unlocked" option in developer options?
Click to expand...
Click to collapse
I do. Tried enabling, but still trying to get a grip on it.
Update: still can't enter fastboot mode. It just reboots like normal.
Can't I run the oem unlock command while in download mode?
mikefeFe said:
Can't I run the oem unlock command while in download mode?
Click to expand...
Click to collapse
No.
pvineeth97 said:
No.
Click to expand...
Click to collapse
Any way you know to unlock bootloader?
mikefeFe said:
Any way you know to unlock bootloader?
Click to expand...
Click to collapse
Maybe bootloader patching might work. Will look into it later.
pvineeth97 said:
Maybe bootloader patching might work. Will look into it later.
Click to expand...
Click to collapse
I appreciate your help. If you need anything from my phone, just let me know.
Did you ever have any success unlocking the phone?
I am trying to do the same thing and running into the same problems.
please help us!
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
hope someone with a kind hearted intellectual brain will make this happen ? please help us damn it
jamers14 said:
Did you ever have any success unlocking the phone?
I am trying to do the same thing and running into the same problems.
Click to expand...
Click to collapse
Nothing yet. I am waiting to hear something from @pvineeth97 on the issue. I'll contact him and see where we stand. ?
mikefeFe said:
Nothing yet. I am waiting to hear something from @pvineeth97 on the issue. I'll contact him and see where we stand.
Click to expand...
Click to collapse
You guys have Android 7.0?
pvineeth97 said:
You guys have Android 7.0?
Click to expand...
Click to collapse
Yep & thank you MikeFefe!
Did anyone ever find a solution to this?
diazi said:
Did anyone ever find a solution to this?
Click to expand...
Click to collapse
Not as of yet. Sorry.
Hey all, just got this phone, I had originally "done some research" when I was at the att store, and found root instructions for the lg k20 PLUS (missed that plus part). So I bought the phone and now im finding out there's currently no root method, which means, as usual, I have to at least try. I warn you, I'm no fulltime dev, so don't get too excited, im the kind of guy that still needs plenty of help with this stuff, but I'm setting up a dev environment and digging in.
My question right now is, has anyone been able to access the bootloader? I read thru the k20plus root topic a bit and they say to use
#adb reboot bootloader#
or hold VOLDOWN and plug usb while powered off.
Nothing seems to bring me to a bootloader.
#adb reboot bootloader#
reboots the device and I assume it tries to boot the bootloader and fails, because windows chirps as if it's been disconnected, then my device proceeds to boot up normally.
Holding VOLDOWN and plugging the usb makes the phone show a splash screen momentarily and then switch to the powered off charging screen.
Has anybody been able to access the bootloader?
-BMFC
Still waiting here too. ??
What u mean with "bootloader" are fastboot.
To get into download-mode hold Vol+ & plug-in usb
Fastboot may for u arivable but u have to wipe ur recovery partition first.
Then reboot into recovery...but wait !
It's look like freeze..plug-in usb and hit on ur PC "fastboot device"
Welcome !
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Update: I have returned my device to Google and they processed a replacement
i am just curious, how were planning on flashing a rom with locked bootloader?
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Paradoxxx said:
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Click to expand...
Click to collapse
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Yeah at that point... Not sure what is Google saying about that. Maybe RMA it ?
Saying something like that should work.
"I was using my device, and suddenly it froze and nothing responded. It suddenly rebooted and shown this error message."
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Sorry didn't get, What do you mean by OP has nothing to loose?
Badger50 said:
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
How did you recover your devices from that state earlier when you did the same thing?
ram4ufriends said:
Sorry didn't get, What do you mean by OP has nothing to loose?
Click to expand...
Click to collapse
since your phone is now essentially a brick, you can try just about anything without worry of bricking your phone.
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
You cannot flash full images, but you can still flash OTAs... download the full OTA instead, and install (sideload) it from the stock recovery. Be sure to select the SAME build number you were on to begin with- eg. If you were on 8.1, use the 8.1 OTA. There will be a mode there for "Apply update from ADB". You put the phone into "sideload mode" and then send the OTA to the phone via adb. This will work regardless whether you have usb debugging enabled or not. Follow the directions given on the included link.
ram4ufriends said:
How did you recover your devices from that state earlier when you did the same thing?
Click to expand...
Click to collapse
I didn't. They are still paperweights sitting in a drawer!
I got the same message yesterday after doing... God knows what. I can't even remember what went wrong.
My first thought was to flash a factory image. But it didn't helped at first. Probably, because i was trying to flash another factory image and not the one that came as stock on my phone.
So if you don't remember, which image it was, try all of them Hopefully, you'll get your phone booted again.
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
dontbeweakvato said:
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
Click to expand...
Click to collapse
Meh...you know how it is bro....**it happens!
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
ArminasAnarion said:
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
Click to expand...
Click to collapse
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
mitchdickson said:
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
ArminasAnarion said:
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
Click to expand...
Click to collapse
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
mitchdickson said:
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
ArminasAnarion said:
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
Click to expand...
Click to collapse
What's wrong with it? You're telling him to call Google and say that for some reason, all the sudden his device won't boot.
This is why I don't fault Verizon for selling bootloader locked phones.
Sent from my taimen using XDA Labs
hi guys please help me i get this error on the screen ". The device will not start." and i can't use my phone, i can't enter the recovery mode (i get the same error) and the device state locked ! please help me
19 views no reply ! Up
Chouiyekh said:
19 views no reply ! Up
Click to expand...
Click to collapse
Tried reflashing stock?
djcrystals said:
Tried reflashing stock?
Click to expand...
Click to collapse
i can't because the bootloader is locked, please help to find a way to revive my mobile (i don't know i there is a box or something else to install the os even the bootloader locked)
the problem happened when i tried to relock the bootloader, unfortunately i don't know the place of purchase because i'm a second hand and i don't know the person who sold me the phone where to live we just met through the internet and we don't have google support in Morocco
Chouiyekh said:
i can't because the bootloader is locked, please help to find a way to revive my mobile (i don't know i there is a box or something else to install the os even the bootloader locked)
the problem happened when i tried to relock the bootloader, unfortunately i don't know the place of purchase because i'm a second hand and i don't know the person who sold me the phone where to live we just met through the internet and we don't have google support in Morocco
Click to expand...
Click to collapse
If you were not on full stock rom without root, or anything custom, and you turned off OEM unlocking and USB debugging, then locked the bootloader, you are basically hosed my friend
Look at this point it just needs to be said... PEOPLE STOP RE-LOCKING THE DARN BOOTLOADER!!
PERIOD!!
There are literally a half dozen posts this week with probably bricked phones and a good amount of them are this same root cause.
CyberpodS2 said:
Look at this point it just needs to be said... PEOPLE STOP RE-LOCKING THE DARN BOOTLOADER!!
PERIOD!!
There are literally a half dozen posts this week with probably bricked phones and a good amount of them are this same root cause.
Click to expand...
Click to collapse
Your preaching to the choir ol friend! While I agree with you 100%, some things are best learned the hard, and expensive way! I've done it twice myself.
The carpenters rule should apply to these phones as well...."measure twice, cut once" :good:
I remember and I'm sure that i left USB debugging enabled, and the bootloader locked, so is there any hope ?
Chouiyekh said:
I remember and I'm sure that i left USB debugging enabled, and the bootloader locked, so is there any hope ?
Click to expand...
Click to collapse
Did you leave OEM unlocking on as well? And, were you on full stock, non rooted rom?
Badger50 said:
Did you leave OEM unlocking on as well? And, were you on full stock, non rooted rom?
Click to expand...
Click to collapse
i left it in this case, OEM unlocking OFF and USB debugging ON, and i was on full stock, rooted rom , the problem happened when i tried to unroot and relock the bootloader
any hopes please please guys, i'm ready to donate for the one who will help i promise
Chouiyekh said:
any hopes please please guys, i'm ready to donate for the one who will help i promise
Click to expand...
Click to collapse
My friend.....you could give me or anybody else 10 thousand bucks, and it's still not going to solve your problem I'm sorry to say. You should have unrooted the phone first, then fastbooted the factory image, or do a factory reset, and made sure that OEM unlocking & USB debugging were left on until you were done locking the bootloader. Sorry man, but there's not much you can do without at least a stock recovery, so....accept the loss, learn from your mistake, and move on. Many of us here, including myself, have been there as well. What you choose to learn from it is up to you
Badger50 said:
My friend.....you could give me or anybody else 10 thousand bucks, and it's still not going to solve your problem I'm sorry to say. You should have unrooted the phone first, then fastbooted the factory image, or do a factory reset, and made sure that OEM unlocking & USB debugging were left on until you were done locking the bootloader. Sorry man, but there's not much you can do without at least a stock recovery, so....accept the loss, learn from your mistake, and move on. Many of us here, including myself, have been there as well. What you choose to learn from it is up to you
Click to expand...
Click to collapse
Thank you so much, i will accept this loss as you said and absolutely i will learn from it. Tupac was right " that which does not kill me can only make me stronger "
Chouiyekh said:
Thank you so much, i will accept this loss as you said and absolutely i will learn from it. Tupac was right " that which does not kill me can only make me stronger "
Click to expand...
Click to collapse
No problem my friend. As they say "s#*t happens"
And your quote isn't from Tupac, it's from the philosopher Frederick Nietzsche in 1888. :laugh:
Badger50 said:
No problem my friend. As they say "s#*t happens"
And your quote isn't from Tupac, it's from the philosopher Frederick Nietzsche in 1888. :laugh:
Click to expand...
Click to collapse
Easy to mistake the two...
Badger50 said:
No problem my friend. As they say "s#*t happens"
And your quote isn't from Tupac, it's from the philosopher Frederick Nietzsche in 1888. :laugh:
Click to expand...
Click to collapse
hahaha, what a big mustache he has
CyberpodS2 said:
Easy to mistake the two...
Click to expand...
Click to collapse
Oh absolutely it is! Almost like twins! ???
Badger50 said:
Oh absolutely it is! Almost like twins!
Click to expand...
Click to collapse
:laugh::laugh::laugh:
Chouiyekh said:
:laugh::laugh::laugh:
Click to expand...
Click to collapse
have you tried flashing the official ota image as that doesnt require an unlocked bootloader so it coud be worth a shot
kevtrysmoddin said:
have you tried flashing the official ota image as that doesnt require an unlocked bootloader so it coud be worth a shot
Click to expand...
Click to collapse
You are correct. Unfortunately, he has no stock recovery anymore