Related
Ok, so I flashed cleanrom ex, and on reboot I got a security error.
I tried to get to recovery, but it wipes data and immediately reboots.
I've tried flashing the stock rom, but lg flash tool tells me it's the wrong device (now thinks it's a D802).
I've been trying to get into TWRP on scrosler and samsunggalaxystig's advice, first by repeatedly trying an adb reboot recovery, then by writing a batch script to do it repeatedly in order to catch it before it reboots.
Problem is, I don't know if I had already had ADB drivers installed on this computer for the G2 (had rooted while at work), and despite installing them more than once, I don't think the device actually has enough time to be recognized as I still have an unrecognized "g2" in device manager while TWRP is wiping.
Any ideas? Is there any way I can force the install of the ADB driver without having it connected for more than 20 seconds? Spitballing... would it be possible to actually flash a D802 image so I could then root, change the build.prop to D800, and then flash the D800 image?
Totally at a loss at this point.
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
kureta said:
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
Click to expand...
Click to collapse
No problem if you brick a sammy phone. its easy to flash stock rom. How did you brick your g2?
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
lastdeadmouse said:
Ok, so I flashed cleanrom ex, and on reboot I got a security error.
I tried to get to recovery, but it wipes data and immediately reboots.
I've tried flashing the stock rom, but lg flash tool tells me it's the wrong device (now thinks it's a D802).
Totally at a loss at this point.
Click to expand...
Click to collapse
Why did flashing a rom leads you to that error? Sorry but not familiar with your roms but is this rom really for your LG G2 model?
lastdeadmouse said:
Ok, so I flashed cleanrom ex, and on reboot I got a security error.
I tried to get to recovery, but it wipes data and immediately reboots.
I've tried flashing the stock rom, but lg flash tool tells me it's the wrong device (now thinks it's a D802).
I've been trying to get into TWRP on scrosler and samsunggalaxystig's advice, first by repeatedly trying an adb reboot recovery, then by writing a batch script to do it repeatedly in order to catch it before it reboots.
Problem is, I don't know if I had already had ADB drivers installed on this computer for the G2 (had rooted while at work), and despite installing them more than once, I don't think the device actually has enough time to be recognized as I still have an unrecognized "g2" in device manager while TWRP is wiping.
Any ideas? Is there any way I can force the install of the ADB driver without having it connected for more than 20 seconds? Spitballing... would it be possible to actually flash a D802 image so I could then root, change the build.prop to D800, and then flash the D800 image?
Totally at a loss at this point.
Click to expand...
Click to collapse
Hey I'm in the exact same position as you... did you manage to figure out a way to get into recovery?
kureta said:
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
Click to expand...
Click to collapse
twrp corrupted my cache partition and the phone could not boot. i tried to flash cwm while in twrp and i guess i messed up recovery and/or boot partitions. al i could get was fastboot. i flashed a boot.img i got from somewhere in here. now it says security error and it does not boot. it does not enter into fasboot. i can enter into recovery mode but it is the stock lg recovery and if i choose "delete all data", which is the only option, it gives an error and restarts.
if i try to flash stock firmware as described in this post it stops at 49%.
kureta said:
twrp corrupted my cache partition and the phone could not boot. i tried to flash cwm while in twrp and i guess i messed up recovery and/or boot partitions. al i could get was fastboot. i flashed a boot.img i got from somewhere in here. now it says security error and it does not boot. it does not enter into fasboot. i can enter into recovery mode but it is the stock lg recovery and if i choose "delete all data", which is the only option, it gives an error and restarts.
if i try to flash stock firmware as described in this post it stops at 49%.
Click to expand...
Click to collapse
I am on the same boat, same problem, and don't know what else to do...hope someone could help us out.
Yep me to same issue. Pretty much tried 6 different methods and still stuck
Solution
IF you still have guys this issue i have solusion for you .
This happened to me yesterday too
1. Download ADB drivers for LG G2 LINK
2. Download LG Mobile Support Tool you can find this here LINK
3. HOLD VOLUMEUP + POWER button to enter the download mode and connect your device to pc
4. Run LG Mobile Support Tool ( if your device vas found click settings select upgrade firmware this will download for you 1.9 GB STOCK FIRMWARE
5. Enjoy your mobile
Any luck anyone? I can't get the suggestion in the last post to work because my phone just goes from the LG Logo to Security Error. I can't get to download mode. Or recovery. Or get ABD to see it.
Odd
quatrix1 said:
IF you still have guys this issue i have solusion for you .
This happened to me yesterday too
1. Download ADB drivers for LG G2 LINK
2. Download LG Mobile Support Tool you can find this here LINK
3. HOLD VOLUMEUP + POWER button to enter the download mode and connect your device to pc
4. Run LG Mobile Support Tool ( if your device vas found click settings select upgrade firmware this will download for you 1.9 GB STOCK FIRMWARE
5. Enjoy your mobile
Click to expand...
Click to collapse
i have to choose upgrade recovery and it gets past analyzing then doesnt show a bar for downloading software...
HELP!!!!!!!!!!!!!!!!!!!!!
Can someone help me I successful in installing twrp though autorec apk and the same for rooting my g2. I flashed cm with nightlies and noticed that twrp had a update. I downloaded the zip and try flashing it like flash a recovery in flashify but that din't work and readed that zip flashing though twrp didn't work but renumber this video and though it would update my recovery to 2.7.1 but it was successful in doing so but when I got to recovery it was 2.7.0. That not the problem form there I tried to boot into my system. Then it turn off though that I passed power off instead but when turn my g2 back on I found that I had a security error show up then turn back off. So can someone help show me a tutorial on unbick or a way to remove error. Also I have the d800 and i have some idea without going though unbicking a hard factory rest or flasing twrp form there site in fastboot. Finally that lg mobile support tool say that im up to date. I think doing the autorec twrp recovery locked as my phones recovery like trying to flash a rom with a locked bootloader.
Ok guys i trying to help cause it happen to me too,sorry for my english too slow but i try,when you try go twrp with volume up+power buttom it still show security errow,that ok your device not hardbrick yet,when you try volume down+power buttom it show hard reset it does mean it clear all rom,picture in internal but it go to twrp again,and them just flash another rom in your device and it done,have great day piece
I had the same problem on my G2 was using twrp to flash cyanogenmod not sure what i did and phone rebooted to show security error message. I entered recovery mode (power and volume down release when logo pops up and press power and volume down again hold for a second then tap both buttons a few times) pulled up the option to factory reset so i did and it booted me into twrp and allowed me to flash cyanogenmod correctly this time and the phone started back up with no problems. hope this can help someone else as well.
Anybody know the solution?
I also have the security error boot loop after flashing KK baseband files... I tried to enter recovery mode by holding vol down & power button but it wont work...
it does work when i enter download mode (vol up + power button), but i don't want to have to download the stock LG ROM..
anybody know how to by pass the security error boot loop to allow me to reflash?
kureta said:
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
Click to expand...
Click to collapse
if you still bricked. try this
get your tools from here: http://forum.xda-developers.com/showthread.php?t=2432476
keep reading or follow above thread. both will work.
best of luck.
After all the drivers installed correctly
make sure your phone is connected to the
com41 port change it if it already not ( Under device manager > Go to Ports (COM & LPT). You should see LGE AndroidNet etc... Right click it and go to Properties > Port Settings > Advanced > Change COM Port Number to COM41 > OK > OK > Close Device Manager )
run flash tool
1. choose type CDMA
2. chose PhoneMode: DIAG
leave rest as it is.
3. choose your kdz file.
then go to download mode
1. power off
2. press and hold vol + key and plug usb cable
3. done )
We have go 2 flashing modes.
1. Normal Flash is for flash with keeping data
2. CSE flash is totally new start preffered.
hope this helps.
thanks but it was a long time ago and I further messed up things, ended up sending it for warranty. they have replaced the device.
me too messed up my cell 1st i was on cloudy g2 v2.1 installed cm11 nightlies but the camera was not so good so then installed cloudy g2 v2.1 n since then i was having problem regarding sound during call and also some hard noise like siren starts randomly, i searched alot but didnt got any solution. wiped all many times (including internal storage ). but no luck then i thought i might be baseband error so i just downloaded auto recovery n flashed it n then stuck into security error but thank GOD i had custom rom in my sd card that time i flashed it back but still em having the sound error.
lastdeadmouse said:
Ok, so I flashed cleanrom ex, and on reboot I got a security error.
I tried to get to recovery, but it wipes data and immediately reboots.
I've tried flashing the stock rom, but lg flash tool tells me it's the wrong device (now thinks it's a D802).
I've been trying to get into TWRP on scrosler and samsunggalaxystig's advice, first by repeatedly trying an adb reboot recovery, then by writing a batch script to do it repeatedly in order to catch it before it reboots.
Problem is, I don't know if I had already had ADB drivers installed on this computer for the G2 (had rooted while at work), and despite installing them more than once, I don't think the device actually has enough time to be recognized as I still have an unrecognized "g2" in device manager while TWRP is wiping.
Any ideas? Is there any way I can force the install of the ADB driver without having it connected for more than 20 seconds? Spitballing... would it be possible to actually flash a D802 image so I could then root, change the build.prop to D800, and then flash the D800 image?
Totally at a loss at this point.
Click to expand...
Click to collapse
kureta said:
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
Click to expand...
Click to collapse
k2thejx5 said:
Yep me to same issue. Pretty much tried 6 different methods and still stuck
Click to expand...
Click to collapse
Hey guys, I was in the same boat for a little but was able to fix it by downloading the 801C firmware and flashing it. The firmware file should be a KDZ extension and you should also download LG Flash Tool 2014. Turn the phone on by holding the Power button and Volum up while it is plugged into your computer(It has to be plugged into a computer with LG phone drivers or it won't work).
Follow this tutorial and you will be set.
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Start at step 17 on Method 1 and you should be golden.
Hope this helps guys!
This is not the first time i root an android device but it is the first time im doing it on an S5, nonetheless I am pretty much stuck right now.
I tried to install CF-Auto-Root-klte-kltexx-smg900f.tar using Odin from here, it installed with no problems, but when the phone restarted I get:
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
and then it shuts down.
I tried to enter recovery mode by doing power+vol up+menu but nothing happens ?
Can anyone help ?
EDIT: ok, so I did manage to get it running again by flashing openrecovery-twrp-2.8.5.0-gt-klte. This got me past the "Recovery is not seandroid...", but all in all I still didn't manage to get root access...
I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
You don't flash .img - you flash .tar
*Detection* said:
You don't flash .img - you flash .tar
Click to expand...
Click to collapse
I did flash .img.tar actually. Still no effect - boots to regular recovery. Can't figure this out...
i get in the same situation...why still rebooting in original recovery?
i installed this one CF-Auto-Root-klte-kltexx-smg900f.tar with odin with succes but still have
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
then when i boot i get a black screen with all application error....the only way to get it back working was to wipe factory reset in original recovery.
what can i do to get it working so i can install custom roms?
thx in avance
seaskyways said:
I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
Click to expand...
Click to collapse
I can't seem to get the coustom recovery installed, and after some digging i found this :
manubhargav said:
Actually the problem was that custom recovery(twrp here) was not installed at all, that above mentioned error occurs when you try to install SuperSU.zip from stock recovery<3e>.
This happens because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:
VL4DST3R said:
I can't seem to get the coustom recovery installed, and after some digging i found this :
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:
Click to expand...
Click to collapse
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
---------- Post added at 05:36 AM ---------- Previous post was at 05:32 AM ----------
xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
manubhargav said:
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...
VL4DST3R said:
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...
Click to expand...
Click to collapse
Ah, So the problem you're facing is NOT getting into recovery mode
There are 2 ways to solve the problem, (1st -> flashing recovery.tar again, 2nd-> flashing stock firmware)
First method:
Enter "Download Mode" by holding down "Volume Down"+ "Home" + "Power" button.
Flash recovery.img again and check if it boots into recovery this time.
Sometimes this may not work and you may need to try flashing firmware
Second method:
Download Firmware from here
Open odin in your PC
Enter "Download mode"
Connect the device to PC using USB
Flash the PDA, BL, AP, CSC etc.
Alternatively, You can flash the firmware using SmartSwitch
manubhargav said:
Ah, So the problem you're facing is NOT getting into recovery mode
Click to expand...
Click to collapse
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.
VL4DST3R said:
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.
Click to expand...
Click to collapse
Which Kernel version are you in? Which TWRP version did you try? Install other custom recoveries? On locked bootloader?
Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"
VL4DST3R said:
Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"
Click to expand...
Click to collapse
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).
manubhargav said:
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).
Click to expand...
Click to collapse
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.
VL4DST3R said:
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.
Click to expand...
Click to collapse
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
Boot Rom and go into settings/aboutphone/ click build number rapidly.
Developer settings should appear, then go into developers options/ click on "root access" and enable it.
---- now test if its working . however....
2)
If its not working, take yourself back into twrp and flash that supersu beta.
----now test again. However ....
3)
If it doesn't work again .
go back to stock 5.0 rom>>> put twrp on >>> and flash DAT supersu .
now test ya rom again. However.........
4)
If it dont work again ..
go back to stock 4.4 rom>>> put twrp on>>> and flash a random supersu.
now test ya rom again. However.....
5)
if that doesn't work again,
Go back to stock rom through (odin) and restart the process from the top .
btw the "recovery is not seandorid enforcing" is normal . not an error.
GeniusisHere said:
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
---- now test if its working . however....
2)
----now test again. However ....
3)
If it doesn't work again .
now test ya rom again. However.........
4)
If it dont work again ..
now test ya rom again. However.....
5)
if that doesn't work again, .
Click to expand...
Click to collapse
First of all holy **** what an answer... let's SLOW DOWN a bit first, shall we ?
Secondly you lost me from step 1, I don't want CyanogenMod, I want the default Samsung 5.0 with TouchWiz (contrary to popular belief I actually like it).
Also I would really like to know (from someone that actually knows why this happens) why is it reverting to default recovery and how can I stop it from doing so ? manubhargav had an interesting idea, but sadly it doesn't work for everyone (as someone else mentioned on that other post)
So I'm guessing no one knows the answer to my problem considering almost a moth has passed...
I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
RL is still there with LP too
Hello, Before starting this Thread i wanna say sorry for my bad english.
Want to Install Stock ROM Lollipop. But the System Cannot Flash/Install that ROM.
Previous, i'm using Ressurection Remix 5.8.5 . All Went Normally, Until i decided wanna back to Stock ROM and get this error.
Situations :
* The Device Stuck on Boot Logo, and No responsibility
* The Device cannot Reach Recovery, Adb, fastboot, even not detected in Device Manager when i Wanna try Flash using QFIL
* Vol Up+Down + Power Buttons Not Works, Only Blink Blue on screen and then reboot.
Chronologic
1. I'm using TWRP 3.2.1 , Wiped System, Data, Cache. And then start flashing Stock ROM
2. When Process, it says Update failed
3. Using Minimal ADB, I tried to flash Stock Lollipop Recovery. And failed.
4. Accidentally, i typed "Adb Reboot recovery.img" which should fastboot Boot Recovery.img
5. The Device rebooted and Stuck on Logo, Until Now
Anyone pls help, Any comment helpful very appreciated.
Thank You for ur attention.
Remove and re-insert the battery. Then hold volume down + power button and see if the phone boots into download mode. If it does, then connect it to a pc with adb installed and see if adb detects it. If all goes right, you could try to install twrp recovey and afterwards install stock firmware through it. Google search A6000_S056_150924_WC51.zip and download the firmware and copy it to the external sd card then flash using twrp.
Although guessing by the state of your phone it seems unlikely that this will work. But give it a try. Hope it helps.
Thanks! It Worked
user0u said:
Remove and re-insert the battery. Then hold volume down + power button and see if the phone boots into download mode. If it does, then connect it to a pc with adb installed and see if adb detects it. If all goes right, you could try to install twrp recovey and afterwards install stock firmware through it. Google search A6000_S056_150924_WC51.zip and download the firmware and copy it to the external sd card then flash using twrp.
Although guessing by the state of your phone it seems unlikely that this will work. But give it a try. Hope it helps.
Click to expand...
Click to collapse
I Try your Method, and its Worked. Now I can use my phone Use As usual.
Thank You very Much!
Thanks man you are so awesome successfully flashed Android lollipop ROM in my Lenovo A6000+ thank you so much
I need help tooo
user0u said:
Remove and re-insert the battery. Then hold volume down + power button and see if the phone boots into download mode. If it does, then connect it to a pc with adb installed and see if adb detects it. If all goes right, you could try to install twrp recovey and afterwards install stock firmware through it. Google search A6000_S056_150924_WC51.zip and download the firmware and copy it to the external sd card then flash using twrp.
Although guessing by the state of your phone it seems unlikely that this will work. But give it a try. Hope it helps.
Click to expand...
Click to collapse
I am having same issues but when its in download mode my pc shows alot of drives n asking me to format it n the downloder is not reading my phone n the fastboot is showing the remote error n adb doesnt detect my phone at all......i need helppp
Hi everyone...
Two days ago, and a few hours after installing the 8.1 update, my mom's J7 touchscreen was unresponsive, including the power button. It ran out of battery, and after I restarted it this morning, it goes to recovery mode after it tries installing system update and the No command screen is displayed.
I've searched on the web for hours and hours for solutions but none of them have worked, most probably because it requires the phone to be connected to the PC, and my PC (Windows 10) isn't even seeing the phone via USB (can't use ODIN nor ADB). BTW, the debug option most probably wasn't turned on prior to soft brick.
Phone Info:
SM-J730G J730GDXS5BRK1
No root
Error on recovery screen (the SD card has been taken out):
======================================
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# MANUAL MODE v1.0.0#
Successfully verified dmverity hash tree
=======================================
Additional info: As I've mentioned, the power button isn't responsive, so I press the volume down button to choose the recovery options. I've tried all recovery options except for:
Wipe data / factory reset, as the phone data isn't backed up (mom doesn't want to lose the personal data as much as possible)
Apply update from ADB
Apply update from SD card
All other options are looping back to the recovery screen after installing system update screen.
Lastly, in recovery, there's an option at the bottom that states "Lacking storage booting". I'm sure that would mean something to someone reading this that would help solve the issue.
An OS downgrade or same 8.1 fix is preferred, as long as the phone data is intact. Any and all help would be much appreciated.
Try "Emergency Software Recovery" feature in Samsung Smart Switch for PC.
It could be a hardware issue as well. Clean your USB charging port with a brush and a drop of alcohol. Then dry with a hair drier.
Good evening, have you tried installing the latest version of the firmware by odin?
If not, try this.
probably its touch stopped working after the update because it was not original (already it has been changed) or it can be other cases ..
if you still can not install the newest firmware downloaded from the sammobile site you can do the second procedure.
Such you will find in this same forum.
In it you use the pc miracle box application and downgrade to 7.1.
this is the title of the post.
follow all procedures.
and it will be all right.
Fix Touch does not work on Samsung J7 Pro (J730G, J730GM) when updating Android 8.1
https://forum.xda-developers.com/ga...ix-touch-samsung-j7-pro-j730g-j730gm-t3850177
PS: Putting it into download mode: Turn the device on by holding the volume down buttons + Home + Power
Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.
Marius.Banderas said:
Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.
Click to expand...
Click to collapse
Then when you get to step II open the twrp and go into settings and uncheck the prompt option to install supersu if it is checked. whenever you do something in twrp uncheck this option. I do not know if this will be your problem but this always happens to me, if not clear at the time of restart the cell phone is in the loop screen exactly because of this option.
Cloud1245 said:
Then when you get to step II open the twrp and go into settings and uncheck the prompt option to install supersu if it is checked. whenever you do something in twrp uncheck this option. I do not know if this will be your problem but this always happens to me, if not clear at the time of restart the cell phone is in the loop screen exactly because of this option.
Click to expand...
Click to collapse
Checked TWRP Settings and there's no option / tickbox for supersu. I think one thing that I'm doing wrong is that I'm formatting data in TWRP during the wipe process instead of just sliding it to restore factory settings. I will try again later today after work.
Also, one thing I've noticed after flashing TWRP is that I have to enter recovery mode twice - the first time, it goes to the No command error screen then goes to stock recovery. Only after a reboot in the stock recovery would the phone enter TWRP recovery.
Marius.Banderas said:
Checked TWRP Settings and there's no option / tickbox for supersu. I think one thing that I'm doing wrong is that I'm formatting data in TWRP during the wipe process instead of just sliding it to restore factory settings. I will try again later today after work.
Also, one thing I've noticed after flashing TWRP is that I have to enter recovery mode twice - the first time, it goes to the No command error screen then goes to stock recovery. Only after a reboot in the stock recovery would the phone enter TWRP recovery.
Click to expand...
Click to collapse
Just one more thing. In tutorials on how to install twrp. when you enter twrp the first thing you should do is format the data. then install the rmm state prenormal and bypass files and only then install magisk or a custom rom.
---------- Post added at 11:10 PM ---------- Previous post was at 11:05 PM ----------
Cloud1245 said:
Just one more thing. In tutorials on how to install twrp. when you enter twrp the first thing you should do is format the data. then install the rmm state prenormal and bypass files and only then install magisk or a custom rom.
Click to expand...
Click to collapse
https://youtu.be/UOACi_sUDQY
do only steps 1, 4, 5, 6, 7, and 8 of the video description.
Will be all right!
Marius.Banderas said:
Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.
Click to expand...
Click to collapse
Before trying to flash TWRP, first flash a full stock firmware and make sure your can at least boot all the way up to the main screen.
Once that works, only then try to flash any custom recovery or custom rom.
Same prob
I've just faced the same problem a few days after my update as well. Did you figure out how to get it back to normal? Thank you!
uz91 said:
I've just faced the same problem a few days after my update as well. Did you figure out how to get it back to normal? Thank you!
Click to expand...
Click to collapse
that is a drk error
you can modification the stock firmware with 7z program
1. open your stock firmware go to AP file
2. click rename than erase the (.md5)
3. extarct the file
4. find (system) file
5. make a (.tar) file with (7z) program with the that system file
6. flash
7. done
Seems I found a way to semi brick my SM-T500. I was attempting to install the LOS 18.1 ROM just posted in the guide section. Some how I got the "can only install official" error message on my download screen after flashing TWRP. Made the mistake of flashing only the stock AP without BL or CSC and now I can't get into either recovery or download modes. Holding vol up and down and plugging in USB cable does nothing. Same with holding power button and either vol up or down. Blank screen. Can only power on and boot to system.
Did you install twrp and can you get into recovery. I had similar problem but was still able to get into download mode from power off. However to do so I had to boot into twrp and select reboot and power off... from that menu you can also boot directly to download mode... I know that doesnt halp much if you hadnt installed twrp yet... but thought I would throw that out there...
wizzdome said:
Did you install twrp and can you get into recovery. I had similar problem but was still able to get into download mode from power off. However to do so I had to boot into twrp and select reboot and power off... from that menu you can also boot directly to download mode... I know that doesnt halp much if you hadnt installed twrp yet... but thought I would throw that out there...
Click to expand...
Click to collapse
I can't boot TWRP or download. The only thing that will boot is system. Can't even get to the lock/unlock screen.
can you connect to adb shell? and try #reboot download
or #reboot twrp. I figure if you get to download you can reflash stock and start over.
Also when your trying to boot into recovery try not being plugged in. Not sure about this device but a lot of older Samsung's that I had would not let me get into recovery if I was plugged in during boot.
Locked oem mode
Locked download mode
Locked wipe factory
Locked update from sd card
Recycling item...
Need factory reset
I saw alot of issues with twrp so I tried Magick for first time ever on my SM-T500 and had a minor hiccup bc I wasn't paying attention to firmware and installed an old AP with newer firmware but ended up just reflashing the whole tablet with the same firmware as the AP that is required for Root and presto it worked! AND HEY IM DEF A NEWBIE!
housemusix said:
Locked oem mode
Locked download mode
Locked wipe factory
Locked update from sd card
Recycling item...
Need factory reset
Click to expand...
Click to collapse
Yeah I've run into the same thing, I originally missed the step to run Magisk after I flashed the patched tar and rebooted into the System and it triggered the "Prenormal KG state" problems. Finally I managed to flash stock ROM back and got to exactly where you are now.
I was able to just flash the patched Magisk AP without CSC and BL, and now it will only go to stock recovery and was able to get TWRP to work once but couldn't factory reset or wipe cache due to (which I assume was) a ton of mounting failures when it loaded.
Anyone else have suggestions to get this thing stable so I can flash LOS? I can get to Download mode.
hello, I post this because it's seems the same subject. I have to password protected (forget password) original rom tablet (non root). For me the datas are not important , I just want to remove the password or reflash with original rom. I downloaded Odin , usb driver and correct firmware. I select AP firmware with Odin, I see the connexion (COM3 green) and it's stuck to "setup connexion".
My problem is that it's impossible to enter in download mode.
When I try to shutdown the tablet, it ask me for a password.
When I press for seconds the power button , after few second I see the Samsung Logo and the tablet restarts.
I try to press volume up, volume up and volume down etc...but each combinaison...no recover, no download mode, nothing and impossible to flash . is it normal ? how to do to unsticked SetupConnetion ?
regards
bruno
housemusix said:
Locked oem mode
Locked download mode
Locked wipe factory
Locked update from sd card
Recycling item...
Need factory reset
Click to expand...
Click to collapse
This is not the same as my problem. My problem is that I flashed AP without BL and the two don't match. It isn't that things are locked but that I can't boot to anything but system. Can't boot recovery or download so I can't flash ANYTHING. Not even stock.