Hey everyone. Out of pure desperation, this is my first post here because I'm absolutely at a loss of what to do.
So I first rooted my Optimus G Pro with Super One Click, then used FreeGee to get CWM Recovery on there, which I heard unlocks the bootloader, too. I then tried to flash the CyanogenMod ROM on this forum, and didn't have any "errors" during install. After this, however, when I rebooted, I was simply met with the "Secure Booting Error: Device UnLock!! so Boot Success!!" message.
I can access CWM-based Recovery 6.0.3.3 still, but can't find a way to put files onto my SD card now. Any ideas? Can I fix this error? Should I just reinstall stock? If so, where do I get it, and how can I put it onto my SD card?
I'd really appreciate any help, guys. Also, if you for sure have a way to get CWMRecovery to boot up, I seem to only get it going with luck.
Thanks for any help or input, guys. I'm pretty distraught, especially since this phone is so new.
usamablackbelt said:
Hey everyone. Out of pure desperation, this is my first post here because I'm absolutely at a loss of what to do.
So I first rooted my Optimus G Pro with Super One Click, then used FreeGee to get CWM Recovery on there, which I heard unlocks the bootloader, too. I then tried to flash the CyanogenMod ROM on this forum, and didn't have any "errors" during install. After this, however, when I rebooted, I was simply met with the "Secure Booting Error: Device UnLock!! so Boot Success!!" message.
I can access CWM-based Recovery 6.0.3.3 still, but can't find a way to put files onto my SD card now. Any ideas? Can I fix this error? Should I just reinstall stock? If so, where do I get it, and how can I put it onto my SD card?
I'd really appreciate any help, guys. Also, if you for sure have a way to get CWMRecovery to boot up, I seem to only get it going with luck.
Thanks for any help or input, guys. I'm pretty distraught, especially since this phone is so new.
Click to expand...
Click to collapse
Try to wipe/factory reset/cache/dalvik and if it doesnt boot and you didnt make any backup from stock rom before cm installation you have to reinstall the stock firmware again
Sent from my LG-P880 using Tapatalk 2
GRG13 said:
Try to wipe/factory reset/cache/dalvik and if it doesnt boot and you didnt make any backup from stock rom before cm installation you have to reinstall the stock firmware again
Sent from my LG-P880 using Tapatalk 2
Click to expand...
Click to collapse
So I've decided I'm okay with going back to Stock Rom for now. If I can't access the phone via USB (at least from my computer) what choices do I have? I'm looking in sideloading. Does that seem pretty alright?
You are supposed to get that secure boot error message when u unlock bootloader and when u flash cm10.1 or any 4.2 rom your SD card becomes a file called 0. It can be accessed in a file manager that has root access and it will b in a mnt. folder. It takes a while for cm to boot so after the lg logo it should b around 5 minutes of black screen.
sent from my OG PRO using tapatalk 4
adizzle23 said:
You are supposed to get that secure boot error message when u unlock bootloader and when u flash cm10.1 or any 4.2 rom your SD card becomes a file called 0. It can be accessed in a file manager that has root access and it will b in a mnt. folder. It takes a while for cm to boot so after the lg logo it should b around 5 minutes of black screen.
sent from my OG PRO using tapatalk 4
Click to expand...
Click to collapse
Okay, so I guess I'm not worried about the boot error message anymore, but I can't seem to get anything to happen. I get the LG logo with the error message, then nothing. I waited about 8 minutes before to no luck. I DID see the CyanogenMod logo once or twice, but it just stalled and didn't do anything. I'm thinking it's a battery thing, but in this state, I can't seem to find a way to charge it.
I did a few different methods of trying to reinstall stock rom (since I'm thinkin now I'll just wait until an official release of CM is available). For the LG Flash Tools version, it's saying my BIN doesn't match with my DLL or something (I'll be more specific when I have a chance). When I do the R&D Test Tool, it says my battery doesn't have enough charge to go through with the update (which is what's making me think my battery is gone).
Right now I have my phone plugged into a wall outlet with CWMRecovery open, because I read somewhere that you can charge your phone that way if you need to.
I'm kind of at a loss, guys. Any specific ideas or help?
I understand that this error is normal as it should be: http://forum.xda-developers.com/showpost.php?p=45094932&postcount=148
Hey everyone! I have a little problem: When I reboot my phone I can not go into cwm... I have an Optimus G Pro with cm10.2. cm10.2 works fine, but i have no change going into recovery mode... When I reboot into recovery there is a lying android figure. What can I do?
usamablackbelt said:
Hey everyone. Out of pure desperation, this is my first post here because I'm absolutely at a loss of what to do.
So I first rooted my Optimus G Pro with Super One Click, then used FreeGee to get CWM Recovery on there, which I heard unlocks the bootloader, too. I then tried to flash the CyanogenMod ROM on this forum, and didn't have any "errors" during install. After this, however, when I rebooted, I was simply met with the "Secure Booting Error: Device UnLock!! so Boot Success!!" message.
I can access CWM-based Recovery 6.0.3.3 still, but can't find a way to put files onto my SD card now. Any ideas? Can I fix this error? Should I just reinstall stock? If so, where do I get it, and how can I put it onto my SD card?
I'd really appreciate any help, guys. Also, if you for sure have a way to get CWMRecovery to boot up, I seem to only get it going with luck.
Thanks for any help or input, guys. I'm pretty distraught, especially since this phone is so new.
Click to expand...
Click to collapse
I had the same problem, I copied CM and Gapps to a microSD card and flashed it from there!
fishingnet said:
Hey everyone! I have a little problem: When I reboot my phone I can not go into cwm... I have an Optimus G Pro with cm10.2. cm10.2 works fine, but i have no change going into recovery mode... When I reboot into recovery there is a lying android figure. What can I do?
Click to expand...
Click to collapse
faced the same issue a while back.......... I had to flash back to stock, reroot and install lokified cwm from freegee. But while doing so, do not disable LG security. After that, I can access recovery normally. BYW, this happened when I flashed 4.3 based rom from a non-loki supported cwm.
Hope this helps...... BTW I am using E988.
usamablackbelt said:
Hey everyone. Out of pure desperation, this is my first post here because I'm absolutely at a loss of what to do.
So I first rooted my Optimus G Pro with Super One Click, then used FreeGee to get CWM Recovery on there, which I heard unlocks the bootloader, too. I then tried to flash the CyanogenMod ROM on this forum, and didn't have any "errors" during install. After this, however, when I rebooted, I was simply met with the "Secure Booting Error: Device UnLock!! so Boot Success!!" message.
I can access CWM-based Recovery 6.0.3.3 still, but can't find a way to put files onto my SD card now. Any ideas? Can I fix this error? Should I just reinstall stock? If so, where do I get it, and how can I put it onto my SD card?
I'd really appreciate any help, guys. Also, if you for sure have a way to get CWMRecovery to boot up, I seem to only get it going with luck.
Thanks for any help or input, guys. I'm pretty distraught, especially since this phone is so new.
Click to expand...
Click to collapse
-----------------
Hello,
I have the same problem with the optimus f120k
When I attempt to reboot show the message:
secure booting error
cause: boot certification verify
Can I recover the phone?
Can I access the phone?
I'd really appreciate any help
Tanks
Hi I rooted the phone, then install the FreeGee , and always start the phone in recovery mode! what can I do for that start with the system normally and not the recovery???
Thank you!
I suspect that FreeGee does something wrong to our devices!
I tried EVRYTHING but still stuck on CWM
E988
same error on F240K E988
Is there any solution for that?
You must flash it back with lg flashtool
Sent from my LG-E986 using xda app-developers app
That message only says that the bootloader is "unlocked." If it didn't say Boot Success then you'd have a problem. After a fresh flash it takes a few minutes before the phone is usable.
Sent from my Carbon LG-E980
tomi001 said:
You must flash it back with lg flashtool
Sent from my LG-E986 using xda app-developers app
Click to expand...
Click to collapse
Yes, after the bootloop problem, I have flashed back with lg flashtool, but i hope will be a solution for that bootloop problem...
LG E-989
reflashing a recovery fixed my recovery bootloop
was using philz_touch_6.15.4-e980 when this happened and I'm not sure if reflashing the same recovery would have fixed it
I had TWRP-2.6.1.0-E980-LOKIFIED-E986HACKED.zip on sd from here so I flashed it and restarted recovery again but after that it booted normally
ULTRAM4X said:
Yes, after the bootloop problem, I have flashed back with lg flashtool, but i hope will be a solution for that bootloop problem...
LG E-989
Click to expand...
Click to collapse
For real? DO NONE OF YOU KNOW HOW TO SEARCH?!?!??!?!? There are 2 threads I created, one in general. One in Q&A. Read through those. There was no need for you to flash back to complete stock. I guess that's what y'all get for not searching (@@)
Sent from my LG-E980 using xda app-developers app
Is there any solution for that?
Hi my n7100 died the other day, then when powered back on was stuck in a boot loop, returned to stock and got the unable to mount efs invalid argument text, now its still stuck in a boot loop with a flash count of 8 so cant be sent in for repair. I have tried a couple of different uk stock roms for my n7100 also a custom beanstalk all stick 1 on boot logo. when in recovery it shows up unable to mount efs invalid arguement, any help would be greatly appreciated im lost without my phone
LifeOfALegend said:
Hi my n7100 died the other day, then when powered back on was stuck in a boot loop, returned to stock and got the unable to mount efs invalid argument text, now its still stuck in a boot loop with a flash count of 8 so cant be sent in for repair. I have tried a couple of different uk stock roms for my n7100 also a custom beanstalk all stick 1 on boot logo. when in recovery it shows up unable to mount efs invalid arguement, any help would be greatly appreciated im lost without my phone
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2420881
How it can corrupt :
- Any bad flashing, mishandling system modification can cause this.
- Also It can be corrupted by downgrading stock ROM. If you flash any old ROM (older to first ME6) on newer ROM (ME6 or any other rom released after ME6) it can corrupt EFS. Basically newer ROM believed to have new kernel that changes EFS data which older Modems can't read and results to fail in reading IMEI.
Click to expand...
Click to collapse
If it is your case, follow the instructions in that thread.
Ive tried the recovery modem flash, no joy. Even if i could get the phone to boot past the 1st logo that would be a start
LifeOfALegend said:
Ive tried the recovery modem flash, no joy. Even if i could get the phone to boot past the 1st logo that would be a start
Click to expand...
Click to collapse
You're not giving much details.
What rom was installed on your device before you got bootloop? Was it official or custom?
What rom did you try to install after you got bootloop? Is it official or custom?
Before the bootloop I was stock rom rooted, then I tried flashing stock rom to fix the bootloop it didnt work so I tried beanstalk 4.2.2 for n7100. I'm at my wits end here I don't know what to try next?
Hey guys, I'm now trying to fix my problem for 2 days straight, but I think I'm just too noobie.
After using my phone regularly in the evening and putting it into standby afterwards, i woke up the next morning and saw my phone in a bootloop (just the pulsating Samsung logo).
My Note 2 was rooted. but I had the original firmware (4.3 I think).
All I can do now is booting into recovery (I had to reinstall CWM since it was gone) and boot into download modus.
Also, I get the error: E:failed to mount /efs (Invalid argument)
When I just let it sit for a few minutes, it sometimes plays the startup animation with sound, which is sometimes ending abruptly and after a few minutes more it just boots into recovery.
When I'm in CWM-Recovery, I can't use ADB (phone is not listed)
What I have tried:
Wipe data/factory reset
Install the stock-rom with Odin (one-part, I cant find a three-parted one)
Install a custom rom
I'm looking forward to see any helpful suggestions, also I have to apologize for my bad English, I'm not a native speaker :angel:
What third part?
ceomaverick said:
What third part?
Click to expand...
Click to collapse
PDA, phone and CSC, or is that unnecessary?
Re flash firmware....
Sent from my GT-N7100 using XDA Premium 4 mobile app
cruelscene said:
Re flash firmware....
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you mean flashing a firmware in CWM, I've already done that.
#push
Please guys, I really need help
Did odin show you some error messages? Anyway where did you download the firmware from? are you sure its the correct one?
Usually bootloop problems are solved by flashing the stock firmware. Please check the version of the firmware you have and make sure its the last relase and the correct one (there are a lot of note 2 models)
- Try flashing with a formatted sd or without the sd
- try to change usb port/cable/pc
- redownload the firmware from another site and try to reflash
- do you have a backup? can you revert to that?
- do you have a ESF backup?
When flashing via Odin please follow:
1. click on “PDA” button and choose the “.tar.md5” file from the folder where you’ve extracted the downloaded firmware file.
2.Ensure that only “Auto Reboot” and “F. Reset” are checked in Odin, do not make any other changes.
3.click on “Start” button to begin the flashing process.
4.As soon as the flashing process has completed, you will see a “PASS” message in Odin and your device will reboot automatically.
-after you flash the stock firmware try to wait at least 15 min for the first boot, then if it wont boot go on the original recovery and try wiping cache and factory reset then reboot and see if you are lucky.
- anyway keep us updated, more info = more chances to understand the problem = usually more chances to fix it
Well, I don't know why, but I tried flashing TWRP instead of CWR a few minutes ago and tried fixing the efs error with the help of this thread : http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056 .
ADB commands did not work with CWR, but using TWRP I was able to use them, now my Note is turning on again.:good:
Obviously i was too dumb to make any backups of my efs folder, so now I just have got the developer IMEI and can't use mobile service.
Any suggestions?
SquatBaby said:
Well, I don't know why, but I tried flashing TWRP instead of CWR a few minutes ago and tried fixing the efs error with the help of this thread : http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056 .
ADB commands did not work with CWR, but using TWRP I was able to use them, now my Note is turning on again.:good:
Obviously i was too dumb to make any backups of my efs folder, so now I just have got the developer IMEI and can't use mobile service.
Any suggestions?
Click to expand...
Click to collapse
please check this post by dr. ketan http://forum.xda-developers.com/showthread.php?t=2420881 got all the info you need
or try this https://www.youtube.com/watch?v=Pai4BH3AWq8 (never tried it)
giovait said:
please check this post by dr. ketan http://forum.xda-developers.com/showthread.php?t=2420881 got all the info you need
or try this https://www.youtube.com/watch?v=Pai4BH3AWq8 (never tried it)
Click to expand...
Click to collapse
none of the methods seem to work for me.
is there anything else I can do?
Anyone got some advice?
Hi,
I have a samsung gt-n7100 it hangs on the samsung galaxy note II logo and afterwards the android bot appears to be loading...then a red exclamation marks pops up and many error messaged appear such as failed to mount efs etc.
Android System Recovery is - KOT49H.N7100XXUFNE1
I have tried odin3, but it fails every single time....failed to write to nand in short.
I tried using the recovery pit and 4.1.2 recovery files, but same it fails every time and I have noticed that on the phone sometimes there is invalid magic string.
I am thinking that it could be the bootloader since it cannot be downgraded, but the link nd3 bootloader to flash is down and can't try that, but it can be anything.
Can anyone suggest anything? maybe even a way to flash phylz recovery and then flash a custom rom?
Am clueless and any help is appreciated.
Thanks!
use different ver. of odin or kies recovery.
what info do you have in odin?
hey I had same problem stuck on logo and could not use odin becouse of same problem. so it was long time ago and I dont remember in details but what I did was, I used microSD. moved rom files in it and installed them with recovery.Sorry my english is weak but if you dont have cwm recovery or twrp recovery try to find them for odin.I think I did not have them working too but I found recovery to installed with odin and It worked.no NAND error or things like that.so try to install recovery with odin and then put rom files on sd card(if you have it).since then I haven't tryed to install any stock rom using odin becouse I still have that NAND error and I dont want my phone to die in my hands . GOOD LUCK!
Are you using the original Samsung USB cable? Tried different USB ports?
Hello guys. I'm new here. So, my note 2 restarted after i woke up and then it stuck at bootscreen. When i put it in recovery mode, it seems all things cannot be mounted e.g data,efs, system etc because no such file or directory. And then I flashed with odin then it said "NAND write start FAIL". What is going on with my phone? I searched this problem on google and most users said that it's EMMC corrupted. Can someone here clarify? Do i have to send my phone to repair or is there any other way to fix it?
Which file failed to flash in Odin? You used the latest stock ROM from sammobile.com?
What you have described happened to me not long ago ( woke up, bootloop, recovery mode errors ( can't mount bla bla ), getting Nand write fail with Odin when trying to flash anything). Came to the conclusion that I have a corrupt Emmc chip. Ended up buying a motherboard. You can try what is stated in this thread (didn't work for me, but good luck):
https://forum.xda-developers.com/showthread.php?t=2154890
You should try to format everything like data, system... then try to reflash rom
yeah that happened to me too last week i just bought a newer phone i didn't think repairing a 4 year old phone would be worth it
audit13 said:
Which file failed to flash in Odin? You used the latest stock ROM from sammobile.com?
Click to expand...
Click to collapse
Yes i was on 4.4.2 XXUFND4 firmware
Which file failed to flash in Odin? Was is aboot.mbn, system.img, etc?