Related
Hello all, I am still fairly new to the root/Android scene and I've run into a problem.
Firstly, my Nexus' bootloader is unlocked and I'm running and older Franco.Kernel (4.0.1 and 1.4GHZ OC). Now, the problem is, my phone has notified me that a newer OS version is available. When I go to install it, the phone reboots but right after - the little Droid appears with a red caution sign and the phone stays that way until the battery is pulled.
What am I missing here? Any help is greatly appreciated.
P.S. I'm a n00b.
Try relocking bootloader then installing update. And then unlock again.
Sent from my Galaxy Nexus using Tapatalk
anton2009 said:
Try relocking bootloader then installing update. And then unlock again.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
No... He's not going to be able to update just because he locked the bootloader.
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
Redefined81 said:
Hello all, I am still fairly new to the root/Android scene and I've run into a problem.
Firstly, my Nexus' bootloader is unlocked and I'm running and older Franco.Kernel (4.0.1 and 1.4GHZ OC). Now, the problem is, my phone has notified me that a newer OS version is available. When I go to install it, the phone reboots but right after - the little Droid appears with a red caution sign and the phone stays that way until the battery is pulled.
What am I missing here? Any help is greatly appreciated.
P.S. I'm a n00b.
Click to expand...
Click to collapse
In order to properly take an OTA and have it install you're going to have to be on the stock ROM, recovery, radios, everything. You can be unlocked and rooted, but you can't have changed anything else. Because you've flashed another kernel, you're probably going to have to flash the update manually.
heifica 798.
martonikaj said:
No... He's not going to be able to update just because he locked the bootloader.
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
In order to properly take an OTA and have it install you're going to have to be on the stock ROM, recovery, radios, everything. You can be unlocked and rooted, but you can't have changed anything else. Because you've flashed another kernel, you're probably going to have to flash the update manually.
Click to expand...
Click to collapse
Thanks! How and where would I go about doing this?
Sorry, but remember, I'm still really new to all of this.
Redefined81 said:
Thanks! How and where would I go about doing this?
Sorry, but remember, I'm still really new to all of this.
Click to expand...
Click to collapse
I'd pass that question to someone more knowledgeable than I on the subject. I wouldn't wanna give you improper guidance. Not sure how your custom kernel comes in to play when flashing.
All I know is you won't be able to take the regular OTA in your current state.
Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806
El Daddy said:
Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
Is this going to un-root and/or lock my bootloader again?
You should have learned how to go back to stock before flashing anything...
El Daddy said:
Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
That is overkill. Just go here: http://code.google.com/android/nexus/images.html and download the version of Android you are using. Extract the boot.img file from within, and flash that with fastboot. Now you are back to the stock kernel, and the update will install automatically (assuming of course that you did not make other changes).
EDIT: You will not lose root, your bootloader will still be unlocked, and all of your data/settings will still be there.
efrant said:
That is overkill. Just go here: http://code.google.com/android/nexus/images.html and download the version of Android you are using. Extract the boot.img file from within, and flash that with fastboot. Now you are back to the stock kernel, and the update will install automatically (assuming of course that you did not make other changes).
EDIT: You will not lose root, your bootloader will still be unlocked, and all of your data/settings will still be there.
Click to expand...
Click to collapse
Thank you so much!
I know I may seem a tad annoying, but I just don't want to mess up my phone, lol!
How do I go about installing this?
I DL Fastboot & it's drivers. Extract the IMG (just so you know, I'm currently yakjuxx, not yakju - does that matter?) to the same directory as Fastboot then enter my phone into Fastboot mode. The thing is, I'm unfamiliar with the command prompts to get it going. I'll be doing it on Windows 7. Help would be appreciated!.
I know I've asked a lot, and I thank you.
Redefined81 said:
Thank you so much!
I know I may seem a tad annoying, but I just don't want to mess up my phone, lol!
How do I go about installing this?
I DL Fastboot & it's drivers. Extract the IMG (just so you know, I'm currently yakjuxx, not yakju - does that matter?) to the same directory as Fastboot then enter my phone into Fastboot mode. The thing is, I'm unfamiliar with the command prompts to get it going. I'll be doing it on Windows 7. Help would be appreciated!.
I know I've asked a lot, and I thank you.
Click to expand...
Click to collapse
I'm not sure it matters if you are yakju or yakjuux (as I think all the stock GSM kernels for ITFL41F are the same), but just to be sure, go here and download my nandroid back up of yakjuux ITL41F. In the archive, you will find a boot.img file (which is the file you need). Extract it.
All you have to do it put the boot.img file in the same directory as your fastboot.exe file, reboot your device into fastboot mode, and plug it into your PC. Open a command prompt in that directory and type fastboot devices to make sure you PC recognizes your device. Then type fastboot flash boot boot.img
Done.
Now, obviously this assumes that you already have the drivers set up properly...
efrant said:
I'm not sure it matters if you are yakju or yakjuux (as I think all the stock GSM kernels for ITFL41F are the same), but just to be sure, go here and download my nandroid back up of yakjuux ITL41F. In the archive, you will find a boot.img file (which is the file you need). Extract it.
All you have to do it put the boot.img file in the same directory as your fastboot.exe file, reboot your device into fastboot mode, and plug it into your PC. Open a command prompt in that directory and type fastboot devices to make sure you PC recognizes your device. Then type fastboot flash boot boot.img
Done.
Now, obviously this assumes that you already have the drivers set up properly...
Click to expand...
Click to collapse
Fastboot can flash boot.imgs, awesome, I likely would've been a muppet and made a CWM zip. I learn something new that I love about my GN every day.
mudferret said:
Fastboot can flash boot.imgs, awesome, I likely would've been a muppet and made a CWM zip. I learn something new that I love about my GN every day.
Click to expand...
Click to collapse
The "fastboot flash" command is specifically for flashing full images to partitions on the device, e.g., system, userdata, boot, recovery, bootloader, radio, splash1, etc.
I have modified the Yakju Galaxy Nexus factory images by completely wiping my Nexus, restoring using the factory images supplied by Google, rooting them and repacking the images with root intact.
After trying so many ROMs that are available, sometimes I think, especially considering the latest releases from Google, that stock is the way to go. Flashing it using these images is my preferred method, being the cleanest, and I have provided these for your convenience as I haven’t seen them anywhere else only ever seen flashable ROMs (i.e. from Recovery) based on the factory images, etc...
These are:
Factory Images “yakju” for Galaxy Nexus “maguro” (GSM/HSPA+)
Android 4.1.2 (JZO54K) with SU binary only
Android 4.1.2 (JZO54K) with SU binary and SuperSU app
Download links are here. MD5 and SHA1 sums are listed so you can check the downloads.
You have to use Fastboot to flash these to your device. The only requirement is that your device's bootloader is unlocked, which you can easily do, but be warned that this will wipe your user data as will flashing these factory images.
To Unlock Bootloader (in the terminal):
Code:
fastboot oem unlock
Unzip the factory image and just run the flash-all.sh in a Linux terminal or flash-all.bat in the Windows command line.
thanks 'mate! I'm gonna try this out in a bit last time I was on stock was still 4.1.1, and my current custom ROM is still on that version.
What are actually the differences of 4.1.1 and 4.1.2? Just thought you had any idea.. :cyclops:
In 4.1.2 I've noticed better battery life like others have reported and notifications can now be expanded and shrunk if you hold on them and drag up and down.
Sent from my Galaxy Nexus using Tapatalk 2
rhed said:
thanks 'mate! I'm gonna try this out in a bit last time I was on stock was still 4.1.1, and my current custom ROM is still on that version.
What are actually the differences of 4.1.1 and 4.1.2? Just thought you had any idea.. :cyclops:
Click to expand...
Click to collapse
Google the changelog..............
Gave you the fishing rod, fish yourself.
https://www.google.com.sg/search?q=...65784e5eeb7334&bpcl=35466521&biw=1360&bih=643
It would be really helpful if someone could help how to install this using a Mac?
Now that's more like it:good: People should start using fastboot more often other than toolkits:good:Learn to install drivers on your computer. Thanks for posting :highfive: I just hope people take the time and learn it..
harisn said:
It would be really helpful if someone could help how to install this using a Mac?
Click to expand...
Click to collapse
I'm not 100% sure as I have never used a Mac for that but there's a good guide here.
Hey, thanks for the links, just want to ask, if I'm already rooted and unlocked my bootloader, if I flash this via fastboot, will it erase my apps/internal memory/photos and such? Quite curious it's just the unlocking the bootloader that deletes all data. Will like inquiries. Thanks!
MoZuFi93 said:
Hey, thanks for the links, just want to ask, if I'm already rooted and unlocked my bootloader, if I flash this via fastboot, will it erase my apps/internal memory/photos and such? Quite curious it's just the unlocking the bootloader that deletes all data. Will like inquiries. Thanks!
Click to expand...
Click to collapse
If you just run the script as is, it will wipe everything. The best thing to do is just flash the system.img if you want to retain your data.
"fastboot flash system system.img"
Sent from my Galaxy Nexus using Tapatalk 2
chickenfeeder said:
If you just run the script as is, it will wipe everything. The best thing to do is just flash the system.img if you want to retain your data.
"fastboot flash system system.img"
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot!
Hello Everyone. I'm trying to downgrade the software on my Asus Zenfone 2 to version 2.19.40.20 (currently 2.19.40.20) so I can unlock my bootloader. I've heard that the way to do this is following rooting procedure 1 from the main information thread but flashing the version of the files that you want your system to be. However when I download the zip it has the system.img file broken up in some weird way (apparently you need a tool called WinRar to put it back together again but I really don't want to have to go buy a piece of software I'm only gonna need once). Does anyone know how to put the files back together again, have a put together 2.19.40.20 system.img I can use or have some alternative solution to my problem. I'm currently using a Linux system too so if at all possible I would like for any software to be compatible with Linux. If anyone has any insight I would be highly appreciative.
Don't try to flash selectively, as that is very likely to brick your phone. What you want is the correct full ROM package containing a system.img, boot.img/kernel, fastboot (droidboot.img IIRC), IFWI.zip, and some other important partitions whose names escape me. Don't try to extract parts of it (e.g. just the system.img, boot.img, or bootloader), because the components appear to be interdependent. In particular, flashing the wrong version of the bootloader without flashing the corresponding kernel/system image will more than likely brick it. You should be able to supply the full ROM to fastboot (e.g. fastboot update <package_file>). Double check everything and back up before you proceed! @Tuanies should have some pointers for you in case I missed anything, and I would wait to hear from him before you try this.
WinRAR is free. It's a very small program that takes seconds to download and install. It is very simple to put the system image components back together with WinRAR and then you will have that file plus the other three you need. Please try it, I'm sure you'll manage it.
All I suggest is to get the full firmware of 2.19.40.20 and flash the images one by one, and sideload the firmware using adb...
Hope this helps
Good luck.
I'd just download the full package from that's ~1GB and sideload that via recovery in its entirety. If this is too complicated, I'd advise against attempting it.
Seriously it is just about writing 3 lines on adb... Not that hard
Sent from my ASUS_Z008D using Tapatalk
I did finally manage to get WinRar working. I had to go install it on my brother's computer. After I had the files to flash I had no trouble.
This seems like a good place to ask this I was on .22 and tried unlocking boot loader did not seem to work so I went back into my 2.19 folder and flashed back to 2.19 but was still unable to unlock though it appears possibly unlocked on boot loader shows bootloader unk and question marks on last 2 entries, but apparently I am unable to flash over the bootloader in fastboot it says fail cmd err can anyone tell me what that means? And how to get around it, tried flashing non tethered twrp says it wrote it but won't boot to it
Sent from my ASUS_Z00AD using Tapatalk
You must have done something wrong. I had the two question marks before I unlocked mine. When your bootloader is unlocked your boot screen will be white. If you're not sure what I'm talking about then you're not unlocked.
robopilot99 said:
You must have done something wrong. I had the two question marks before I unlocked mine. When your bootloader is unlocked your boot screen will be white. If you're not sure what I'm talking about then you're not unlocked.
Click to expand...
Click to collapse
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
---------- Post added at 06:09 PM ---------- Previous post was at 05:58 PM ----------
jimchee said:
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
Click to expand...
Click to collapse
The img's I am flashing are from shakalaka, hope thats spelled right
so in fastboot and using adb i did fastboot flash droidboot droidboot.img (enter)
sending droidboot (14410 kb)
Okay (0.622s)
writing "droidboot"
FAILED < Remote: flash_cmds error !
so this is the answer I am getting when trying to flash droidboot
so any ideas would be great
jimchee said:
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
---------- Post added at 06:09 PM ---------- Previous post was at 05:58 PM ----------
The img's I am flashing are from shakalaka, hope thats spelled right
so in fastboot and using adb i did fastboot flash droidboot droidboot.img (enter)
sending droidboot (14410 kb)
Okay (0.622s)
writing "droidboot"
FAILED < Remote: flash_cmds error !
so this is the answer I am getting when trying to flash droidboot
so any ideas would be great
Click to expand...
Click to collapse
I had to flash 4 files as it appears you are trying to do. The error is definitely not good. I'm not sure what it means though. Hopefully someone else knows what to do. I'm pretty sure being on this up to date bootloader is your issue. Did you manage to somehow flash the other 3 files?
robopilot99 said:
I had to flash 4 files as it appears you are trying to do. The error is definitely not good. I'm not sure what it means though. Hopefully someone else knows what to do. I'm pretty sure being on this up to date bootloader is your issue.
Click to expand...
Click to collapse
Yep I figure that might be it, just not sure what to do next, every other file flashes whether I am going up or down thinking of trying to flash older than 19 and then hopefully able to its to 2.19, but hopefully someone knows the proper way
Sent from my ASUS_Z00AD using Tapatalk
The files that I flashed I got from here. Don't know if that's where you are getting yours.
What I did is I downgraded to version Z00A_WW_2.19.40.18 of everything (I was warned about flashing different versions of different things so be careful). I then used the bootloader unlock method detailed in section 5 of the resource thread. I think your problem is that the files you are flashing are not pre-rooted. I used the files from section 3.1, method 1 of the same thread. The system.img was broken up in some strange fashion but I can send you the put together version somehow if you would like.
robopilot99 said:
What I did is I downgraded to version Z00A_WW_2.19.40.18 of everything (I was warned about flashing different versions of different things so be careful). I then used the bootloader unlock method detailed in section 5 of the resource thread. I think your problem is that the files you are flashing are not pre-rooted. I used the files from section 3.1, method 1 of the same thread. The system.img was broken up in some strange fashion but I can send you the put together version somehow if you would like.
Click to expand...
Click to collapse
I am using the pre rooted ones from shakalaka and i can get boot, recovery and system to flash but unable to get droidboot to flash and that is what I can't figure out even when i downgrade with all the other files i can't get bootloader unlocked
I couldn't find the files you were referring too. However I really don't know enough about fastboot to really help you resolve the error message. Hopefully someone a little more experienced will come along soon.
robopilot99 said:
I couldn't find the files you were referring too. However I really don't know enough about fastboot to really help you resolve the error message. Hopefully someone a little more experienced will come along soon.
Click to expand...
Click to collapse
They are the same files that you are using from mega.nz and my fastboot knowledge is not great either, so I'll just wait around and see if anyone with more knowledge can help me out, thanks for yoyr help though it's appreciated
@jimchee you are typing the wrong command to flash droidboot. its "fastboot flash fastboot droidboot.img"
Niropa said:
@jimchee you are typing the wrong command to flash droidboot. its "fastboot flash fastboot droidboot.img"
Click to expand...
Click to collapse
Thanks Niropa, I knew there was reason this works now I really appreciate the help
Just a quick note to let everyone know that everything worked without a hitch now have unlocked bootloader and twrp installed.
Sent from my ASUS_Z00AD using Tapatalk
I'm having a problem with my nexus 5x. Yesterday, I decided I would factory restore my nexus from it being custom ROMd. I booted it into fastboot mode and relocked the bootloader, which wiped all the data. Then, when I went to flash the nought factory image, CMD and fastboot kept telling me my device is locked and I cannot flash to it. Because I locked the bootloader when the custom rom was still on it, it wont start up. I've downloaded older marshmallow builds from google too but they all give the same messages when flashing any of the files, including running the flash all command, saying that my device is locked and I cannot flash to it. Can anyone please help?
Jeez man! Locking the bootloader is the very last thing you do - if you do it at all because there's no good reason for it!
Cross my fingers: Do you have stock recovery installed?
If yes, you can adb sideload a OTA image.
If no, you're toast
https://developers.google.com/android/nexus/ota
berndblb said:
Jeez man! Locking the bootloader is the very last thing you do - if you do it at all because there's no good reason for it!
Cross my fingers: Do you have stock recovery installed?
If yes, you can adb sideload a OTA image.
If no, you're toast
https://developers.google.com/android/nexus/ota
Click to expand...
Click to collapse
Not toast. @arx160le would only have to flash the TOT to get it working again. He could do that regardless if he didn't feel like sideloading.
PiousInquisitor said:
Not toast. @arx160le would only have to flash the TOT to get it working again. He could do that regardless if he didn't feel like sideloading.
Click to expand...
Click to collapse
I cant seem to find a tot for 16 gb nexus 5x. Things arent look too good rn lmao.
arx160le said:
I cant seem to find a tot for 16 gb nexus 5x. Things arent look too good rn lmao.
Click to expand...
Click to collapse
Flash the 32. Boot to stock recovery and sideload the OTA. Problem solved.
Sent from my XT1650 using Tapatalk
PiousInquisitor said:
Flash the 32. Boot to stock recovery and sideload the OTA. Problem solved.
Sent from my XT1650 using Tapatalk
Click to expand...
Click to collapse
I just saw post 123 and thats what I did aha. It's working. Thank you so much.
Please help. I can not get to recovery. I can get to fastboot, but it is unrecognizable when i plug it in to a windows machine. It will recognize it when i plug it into MacOS. However the bootloader is locked, it will not allow me to unlock the bootloader from fastboot.
Caligula36 said:
Please help. I can not get to recovery. I can get to fastboot, but it is unrecognizable when i plug it in to a windows machine. It will recognize it when i plug it into MacOS. However the bootloader is locked, it will not allow me to unlock the bootloader from fastboot.
Click to expand...
Click to collapse
Follow the same guide that was just posted above. It's the only fix. Make sure you install all the drivers and boot the phone into download mode.
Windows tends to be a bugger sometimes when it comes to driver installs. My business laptop has 7 professional, my personal laptop has Windows 10. I never know which one will load the drivers I need.
You might just want to try a different computer if one is available. Or you could just delete any LG drivers you already have loaded and start fresh.
Sent from my Nexus 5X using Tapatalk
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)