Related
Hello all,
LG Optimus G Pro user here (LG-F240S). I recently rooted my phone, then used Gomdol's tool, which roots the phone and installs CWM recovery at the same time. I had initially thought that the application also unlocks the bootloader, but since then found out it doesn't.
Anyways, the first time rebooted into recovery, I flashed a ROM (specifically for F240S), which wasn't successful for some reason. Now, when I boot up the phone, it keeps saying "Secure Booting Error! Cause: boot certification verify"
I have tried everything, from the Volume down + Power + Home to erase everything and do the factory reset, but it doesn't work. I have also downloaded the stock firmware, and tried the KDZ_FW_UPD application to flash the stock firmware, which also did not work (Extract File Error). My last resort was using LGMobile Support Tool, but it keeps telling me to recharge my battery (my batter is currently recharged to 100%, and the USB is plugged in, so something is very wrong here).
I would really appreciate any help, It's been 3 days now without being able to use my phone and it sucks
Thanks!
J
Might wanna try this
ca12bon said:
Hello all,
LG Optimus G Pro user here (LG-F240S). I recently rooted my phone, then used Gomdol's tool, which roots the phone and installs CWM recovery at the same time. I had initially thought that the application also unlocks the bootloader, but since then found out it doesn't.
Anyways, the first time rebooted into recovery, I flashed a ROM (specifically for F240S), which wasn't successful for some reason. Now, when I boot up the phone, it keeps saying "Secure Booting Error! Cause: boot certification verify"
I have tried everything, from the Volume down + Power + Home to erase everything and do the factory reset, but it doesn't work. I have also downloaded the stock firmware, and tried the KDZ_FW_UPD application to flash the stock firmware, which also did not work (Extract File Error). My last resort was using LGMobile Support Tool, but it keeps telling me to recharge my battery (my batter is currently recharged to 100%, and the USB is plugged in, so something is very wrong here).
I would really appreciate any help, It's been 3 days now without being able to use my phone and it sucks
Thanks!
J
Click to expand...
Click to collapse
Hey mine did this i used the instruction in the thread below but i had the e980 so you might have to get your stock files but worth a try?
http://forum.xda-developers.com/showthread.php?t=2302660
Simply follow this method
http://forum.xda-developers.com/showthread.php?t=2396048
Hey man, I'm in the same boat, but I have the E988. What did you end up doing?
any idea?????
tase25 said:
Hey man, I'm in the same boat, but I have the E988. What did you end up doing?
Click to expand...
Click to collapse
i have the same problem here!! E975 when i dot the classic staff for custom rom i go to recovery i i see this in to my phone....boot certification verify
stock rom 4.4.2kk....what i mast do guys plz help
ca12bon said:
Hello all,
LG Optimus G Pro user here (LG-F240S). I recently rooted my phone, then used Gomdol's tool, which roots the phone and installs CWM recovery at the same time. I had initially thought that the application also unlocks the bootloader, but since then found out it doesn't.
Anyways, the first time rebooted into recovery, I flashed a ROM (specifically for F240S), which wasn't successful for some reason. Now, when I boot up the phone, it keeps saying "Secure Booting Error! Cause: boot certification verify"
I have tried everything, from the Volume down + Power + Home to erase everything and do the factory reset, but it doesn't work. I have also downloaded the stock firmware, and tried the KDZ_FW_UPD application to flash the stock firmware, which also did not work (Extract File Error). My last resort was using LGMobile Support Tool, but it keeps telling me to recharge my battery (my batter is currently recharged to 100%, and the USB is plugged in, so something is very wrong here).
F240S user here bro. I feel you
I would really appreciate any help, It's been 3 days now without being able to use my phone and it sucks
Thanks!
J
Click to expand...
Click to collapse
on your boot certification problem, I had that same problem before and made me panic for two days. I tried LG mobile support tool and worked for the first time. few weeks ago, I also encountered the same error on LG Mobile support tool (battery error,right?) I used I also used the KDZ_FW_UPD application and yes, extract error. but you know what the magical thing is? I found the G2 KDZ flasher from the G2 thread..
even if this was from G2 thread, it worked for my device.
here is the link and of course thanks to @hyelton for bringing this wonderful fix. now, I don't have to worry about bricking my phone again(except for hard bricking, of course).
http://forum.xda-developers.com/showthread.php?t=2432476
one more thing: make sure you download the KDZ. there is a thread here that links to that. but I think you have the right kdz now so just follow the steps. make sure you are in download mode press volume up and down (only the volume up and down. not the home or power) and then plug the cord.
guys, this happens when installing custom rom with lg stock rom in it and your device is not fully unlock. to lessen the hassle of worrying trying to reflash to the stock rom and downloading those huge files..just download any custom pure android rom , slimkat, cm11, etc then flash to your recovery..it would boot again without that error on boot certification. only that your on pure android rom but that's ok
nuvkyl20 said:
guys, this happens when installing custom rom with lg stock rom in it and your device is not fully unlock. to lessen the hassle of worrying trying to reflash to the stock rom and downloading those huge files..just download any custom pure android rom , slimkat, cm11, etc then flash to your recovery..it would boot again without that error on boot certification. only that your on pure android rom but that's ok
Click to expand...
Click to collapse
How do i flash the rom when i cant get into recovery? I have the same issue om my rooted g pad whit stockrom. I want to flash cyagenmod.
HELP PLEASE! My Lg G Pro e988 stays forever on this "Secure booting error! Cause: boot certification verify! Can't get in download mode. I have tryed all sort of combination keys but everytime this error pops up. My phone was on stock rom, then an official update started to download and ask me to reboot. After reboot this error!
HELP!
You should be able to get in download mode by following these steps. First take out the battery for atleast 5seconds, put it back in, then press and hold both vol + and vol - and within 2seconds plug in the usb cable, your computer should make the sound of a new device connected, when you hear that let go of the volume keys. The screen should say download mode now.
Sent from my LG-E980 using XDA Free mobile app
ivoh95 said:
You should be able to get in download mode by following these steps. First take out the battery for atleast 5seconds, put it back in, then press and hold both vol + and vol - and within 2seconds plug in the usb cable, your computer should make the sound of a new device connected, when you hear that let go of the volume keys. The screen should say download mode now.
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't work! I did exactly what you say. No sound on pc, just that error on phone screen and no download mode
What should I do?
Thanks
Try booting into recovery, hold power and vol -. Or try power and vol +
Sent from my LG-E980 using XDA Free mobile app
ivoh95 said:
Try booting into recovery, hold power and vol -. Or try power and vol +
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
I have sent it to warranty and they told me that the phone was rooted, they sent me a picture with the back of the phone showing the imei and serial number and a front picture showing me that the phone has the app SuperSu.
They told me that the phone need a new motherboard that cost ~340 $.
Why do they need a new motherboard ? because the phone was not hard bricked.
I will get my device back.
Is possible to get it back with some modifications? I mean if they managed to boot it and see the SuperSu app.
I know to work with LG Flash Tool, so all I need is to put it to download mode.
All the above key combination didn't work. Power and vol- or power and vol+ ......
I will contact you again when i'll have my device.
Thanks!
yackmaan said:
I have sent it to warranty and they told me that the phone was rooted, they sent me a picture with the back of the phone showing the imei and serial number and a front picture showing me that the phone has the app SuperSu.
They told me that the phone need a new motherboard that cost ~340 $.
Why do they need a new motherboard ? because the phone was not hard bricked.
I will get my device back.
Is possible to get it back with some modifications? I mean if they managed to boot it and see the SuperSu app.
I know to work with LG Flash Tool, so all I need is to put it to download mode.
All the above key combination didn't work. Power and vol- or power and vol+ ......
I will contact you again when i'll have my device.
Thanks!
Click to expand...
Click to collapse
Any updates?
Long story with guys at warranty. I asked them to prove that the phone in those pictures is mine. From the picture showing my imei, yes is mine. But from the picture showing supersu app....they don't convince me. Every phone could have installed supersu app without being rooted. So i asked them to provide me another picture that will show the google account that was registered on phone and another with all my apps installed. They didn't send me such photos.
If they managed to revive my device and showing me there is a supersu app, that means they don't need to change the motherboard.
Am i right?
So i get my phone back working and they cut my warranty.
I tried vol+ and vol- and usb cable and download mode appeared.
Thankd!
yackmaan said:
Long story with guys at warranty. I asked them to prove that the phone in those pictures is mine. From the picture showing my imei, yes is mine. But from the picture showing supersu app....they don't convince me. Every phone could have installed supersu app without being rooted. So i asked them to provide me another picture that will show the google account that was registered on phone and another with all my apps installed. They didn't send me such photos.
If they managed to revive my device and showing me there is a supersu app, that means they don't need to change the motherboard.
Am i right?
So i get my phone back working and they cut my warranty.
I tried vol+ and vol- and usb cable and download mode appeared.
Thankd!
Click to expand...
Click to collapse
I smell something weird about LG. They probably put SuperSU on there or they got the wrong phone. Anyway i'm sure the community will help Don't lose faith/hope yet
About the warranty, its very complicated.
The store from which the phone was buyed, took it and send it to another warranty dealer authorized by LG, i guess, which was not named LG.
At last, I sold the phone, i own an lg g2 now and recently flash official lollipop.
Gladly and after some fails and always getting the secure boot certification error, i managed to access the download mode and with LG Flash Tool installed the stock .kdz on my LG L90 D405n.. thx for all the hints..
Before of this secure boot my e988 was working but no download mode. I've encountered this on a LG G2, so after some search i've found out that I must downgrade the bootloader. So, I rooted my device and installed autorec.apk from here http://forum.xda-developers.com/showthread.php?t=2715496 that fixes the " no download mode " .
I don't know how to skip the secure boot error. If someone managed please share with us!
Boot : Error Certification Verify
Hi. I am new to this thread although i had used this thread many times with issues i have had. There is this one issue im having that i can't seem to figure out which im usually good at doing by following forums or threads.
A couple weeks ago i had rooted my LG G Pad 7.0 V410 LTE tablet from AT&T. I had TWRP downloaded into it and i had flashed Candy5 it worked perfectly i just didn't like how it looked so i tryed to flash it back to original stock OS. But now when i boot my tablet up it goes to the LG screen and at the top left it says Boot : Error Certification Error. This has me dumbfounded on what i should do. when i connect the tablet to the computer nothing pops up no tablet connects to the computer. I tryed downloading the drivers and everything but nothing seemed to work. I need help with this issue please!!
I didn't know where else to post this issue due to being new!!!
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
yakub234go said:
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
Click to expand...
Click to collapse
Thanks for the response. I've tried this a dozen times, but unfortunately (this is going to sound weird) since it's not completely bricked it is only detected as Moorefield for a few seconds when started. This allows the xfstk tool to detect it and begin the download, but not long enough to complete the process so it times out. The only development access I have to the phone now is via adb, but since I don't have root I'm very limited in what I can do via command line. Since I can't access fastboot I can't achieve root. It's just a comedy of errors now.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
sukhwant717 said:
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
Click to expand...
Click to collapse
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
kidnova said:
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
Click to expand...
Click to collapse
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
mrperalta said:
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
Click to expand...
Click to collapse
I've tried this many times, but it only shows Moorefield for a few seconds. I'm assuming this is because it has a fully operational OS so it doesn't stay in the generic USB device mode.
EDIT: I misread your original post. Holding power and volume DOWN does keep connect it in Moorefield. Thanks so much for that. The problem now is that once xFSTK gets to downloading the OS it reboots the phone which takes it out of USB mode and disconnects the tool. I'm still stuck where I was before, but that's a little progress. Any other thoughts?
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
kidnova said:
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
Click to expand...
Click to collapse
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
"those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds"
Click to expand...
Click to collapse
-sukhwant717
mrperalta said:
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
-sukhwant717
Click to expand...
Click to collapse
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
kidnova said:
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
Click to expand...
Click to collapse
Hi, got the same issues, I've read many posts. Tried all of the million options. What was your final way of doing it, do you remember?
Hello,
i dropped my phone last night and at first boot phone clock changed and i could not connect wifi. i tried to connect wifi today but it did not worked. Thats why i opened hidden menu by using *#546368#*855# test my phone if there is a hardware problem or not. i clicked first option then second option my phone got reset but i got Secure booting error after that and it stuck. Then i opened twrp by using factory data reset option. i got backup of my data from twrp menu.
What should i do now?
Notes:
- i use twrp + android 6.0 rooted firmware
- i dont know if can can install apk since i cant open android system
- i dont want to install stock rom by a pc because i think i will lose all info on phone and ont be able to get them back without twrp.
juba08 said:
Hello,
i dropped my phone last night and at first boot phone clock changed and i could not connect wifi. i tried to connect wifi today but it did not worked. Thats why i opened hidden menu by using *#546368#*855# test my phone if there is a hardware problem or not. i clicked first option then second option my phone got reset but i got Secure booting error after that and it stuck. Then i opened twrp by using factory data reset option. i got backup of my data from twrp menu.
What should i do now?
Notes:
- i use twrp + android 6.0 rooted firmware
- i dont know if can can install apk since i cant open android system
- i dont want to install stock rom by a pc because i think i will lose all info on phone and ont be able to get them back without twrp.
Click to expand...
Click to collapse
Hello,
You need to install Mr.Bump (click on it to download it) and move it to your Phone (Go to TWRP,connect your phone with your PC,move the file to your phone)Then click install and select "Mr.Bump.zip" file.
Greetings.
thanks you but i bricked my phone last night now it does not even open or charge. Thats i have done so far:
i used auto rec on my lg g3 d855 phone. https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012 i had stock lg 6.0 30b firmware provided in this topic. it said succsfull and after the reset phone did not open and it does not respod to any button also dont get charge there is just black screen. is there there any way yo fix this?
do you think something like this topic help this issue?
https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
juba08 said:
thanks you but i bricked my phone last night now it does not even open or charge. Thats i have done so far:
i used auto rec on my lg g3 d855 phone. https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012 i had stock lg 6.0 30b firmware provided in this topic. it said succsfull and after the reset phone did not open and it does not respod to any button also dont get charge there is just black screen. is there there any way yo fix this?
do you think something like this topic help this issue?
https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
Click to expand...
Click to collapse
It would be better not to flash those kdz files.
You could have asked here before proceeding,but it doesn't matter now.
For the topic that you sent,I'm not sure that it will work.
So,can enter in Download mode (Click on it to see how to enter)
If you can,please reply.
Sotiris02 said:
It would be better not to flash those kdz files.
You could have asked here before proceeding,but it doesn't matter now.
For the topic that you sent,I'm not sure that it will work.
So,can enter in Download mode (Click on it to see how to enter)
If you can,please reply.
Click to expand...
Click to collapse
i have done everything on that topic i went ok until last steps but at last i still got black screen and cant enter download mode or boot. but pc recognizes the phone as lge androidnet usb now in device manager. it was Qualcomm 9008 at start.
juba08 said:
i have done everything on that topic i went ok until last steps but at last i still got black screen and cant enter download mode or boot. but pc recognizes the phone as lge androidnet usb now in device manager. it was Qualcomm 9008 at start.
Click to expand...
Click to collapse
Hmm Try this guide Unbrick guide (it's officially for D855)
thanks it worked in second time now i can enter download mode i am flashing with lg flash tool. the problem is i could not install twrp before. i tried 5 roms + autorec, twrp manager and twrp offical app. and all resulted failing to open clock work mode. now i will try with D85530B_00_1217_32G.kdz
i have twrp backup in my sd card that why i am trying to boot into twrp for more than 24 hours. i hope i can do this. i winn never use eutorec i will use offical twrp app next time.
i can open android but i cant open twrp i got error boot vefication failed. i can use phone like that but i want to get my backup. if i cant i will have to install apps one by one and i will also lose some files, contacts, data etc.
I picked up my UK V30 H930 yesterday all fine and saw that LG have unlocked the bootloader on my model so I went ahead and tried it along with trying the alpha TWRP build
So I thought id write about what went wrong and how I recovered from it.
I made the mistake of letting the phone auto update to 10v software verion before I did this. As I had 10f on before when I bought the phone.
I went to load in all the software needed to unlock the bootloader and proceeded to do so but in my haste of the user data being wiped taking a longer then I thought it would I unpluged the phone to try "fastboot flash unlock unlock.bin" again . No such luck already unlocked. It booted back in fine so I thought everything was ok but that was the moment I thought could have caused my entire night to be ruined.
I thought with the bootloader saying it was unlock it was now fine to flash TWRP on now so went to do that and discovered it would no longer boot into the rom anymore coming up with the LG V30 Logo and just staying put. Thought it must be my 10v software version messing it up. Ok ill try to flash a 10f stock kdz. After about an hour or so of 'Finding my feet' with the phones boot methods for download mode, Fastboot and recovery I found that twrp was being strange with mounting the phone tried otherways eventually got the phone talking to the pc by using uppercut with LGUP and having the phone in download mode and the port com channel in device mananger set to com 41. After about 4 tries of flashing KDZ's to the phone it would just come with a "erasing" circle and proceed to get stuck on boot logo again so I messed about with .dlls and tried to other methods. Still nothing.
Now I tried LG Bridge's "Update error recovery" and I was actually talking to the phone for the 1st time so i let it do its thing which took well over an hour to download the kdz file. "Fine just work please". it got to the updating stage at 5% and froze and the phone being in download mode hadnt done a thing. I tried again but still nothing. Eventually now at 6am and having been up all night I went to give up but I manged to get it on to fastboot mode and by chance came across "flashing lock_bootloader" tried and it and it locked tthe bootloader back up (this thing of LG saying it cannot be undone must be rubbish?) now before I tried anything I rebooted the phone . IT BOOTED! onto the fresh 10v KDZ i had installed on it but before anything I wanted to see if it would now run with a unlocked bootloader on its own with no TWRP installed. It works! Now i just need a method of rooting but im now ready at least.
Hope this helps anyone with simular troubles.
Also had some trouble yesterday after trying out some Magisk modules.
On reboot it sometimes got stuck in the LG V30 screen, and sometimes even the bootanimation came up, but it didnt finish the boot lol
Only installed and adblock btw, and tried the Xposed module. Uninstalled that again btw. Now only using Adblock.
Phone also seems to need Power + Vol- to force shutdown for me, not only Power like other phones. Also didnt manage to find a way to boot into recovery when the phone is off, only found a way to get into the factory reset screen ?
sadly i dont have a working sdcard currently (my 3 year old 128GB one is read only for some reason, atleast changes dont get applied), so ill wait for a new one to mess around more ^^
Also working on a LOS14.1 build atm (it compiled, but didnt adapt all parts of thr device tree yet, and no idea if i have all vendor files lol)
SGCMarkus said:
Also had some trouble yesterday after trying out some Magisk modules.
On reboot it sometimes got stuck in the LG V30 screen, and sometimes even the bootanimation came up, but it didnt finish the boot lol
Only installed and adblock btw, and tried the Xposed module. Uninstalled that again btw. Now only using Adblock.
Phone also seems to need Power + Vol- to force shutdown for me, not only Power like other phones. Also didnt manage to find a way to boot into recovery when the phone is off, only found a way to get into the factory reset screen
sadly i dont have a working sdcard currently (my 3 year old 128GB one is read only for some reason, atleast changes dont get applied), so ill wait for a new one to mess around more ^^
Also working on a LOS14.1 build atm (it compiled, but didnt adapt all parts of thr device tree yet, and no idea if i have all vendor files lol)
Click to expand...
Click to collapse
Ive just managed to get 10f on so ill retry flashing twrp now.
Are you sure your sdcard doesnt have a little read/write switch on it . Im sure i remember so of them used to have one.
Dreamxtreme said:
Ive just managed to get 10f on so ill retry flashing twrp now.
Are you sure your sdcard doesnt have a little read/write switch on it . Im sure i remember so of them used to have one.
Click to expand...
Click to collapse
nope, doesnt have one. Neither windows nor Linux fail at writing on it, or when deleting files, but as soon as I re-insert the SDCard all changes are reversed. Formatting doesnt work anymore, unknown error. Tried that in Windows, Linux and in the Phone (Androids formatting crashed, TWRPs produced an error after it timed out)
Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Hyldran0 said:
Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Click to expand...
Click to collapse
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
xdausernl said:
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
Click to expand...
Click to collapse
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Hyldran0 said:
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Click to expand...
Click to collapse
It is quite easy to turn the device off, for that to happen you have to press and hold the on/off button. You'll see that the device will shutdown and try to reboot and then finally shuts down again and stay off, then release the on/off button.
Are you sure trying to flash the correct firmware with correct changes, etc??
Please share with us the device and Android version, as well as the stock ROM version with changes you're trying to flash.
Put (copy and paste) the output of Odin below.
Another way to get the firmware flashed is by using Heimdall, but for that to happen you first need to rename the extension of the stock ROM (remove .md5 and leave .tar) and than extract all seperate pieces that are contained within the stock ROM.
All those extracted pieces from the stock ROM you have to upload seperately onto Heimdall and try to flash them to your tablet, one by one.
Heimdall you'll find 'here' or use FWUL instead which has Heimdall pre installed, download is to be found 'here' and install it on a USB medium a stick, to put FWUL onto USB, use Balena-Etcher and the download is to be found 'here'.
Micro USB cable does work, but if you're unsure, try another one and make sure using the correct drivers too.
Using Odin, make sure the tablet is recognised and 'connected' in Odin, also make sure 'repartitioning' is unchecked.
If you've used the wrong Odin version, flashing will fail!
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Hyldran0 said:
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Click to expand...
Click to collapse
You're welcome.
Hi, complete novice here, does anyone know where I can get a working Firmware for my Tab 3 v7 (SM-210)?
I have searched through various forum articles here, and tried to install with several builds but none will install. The only one that gets anywhere near is the JASBR build by gr8nole. It appears to install, but on restart, the TAB just sits on the "Samsung Tab3" start screen.
I read that I may need to flash the firmware 4.4.4 (Kit Kat), but can't find it!
The unit is not totally bricked (yet), as I can run TWRP 2.8, with which I created a backup of the original build, but when I try to restore the backup, it fails at just over 31%.
Can anyone help please?