Database Users

[Q] What did autorec do to my phone?!?

Hi all,
Let me try to walk you through everything that I've done to try and get some help here.
I have an lg g2 sprint (lg-ls980)
1. When I got it I first upgraded to android 4.4.2
2. Then I rooted using stump root
3. I installed xposed and a few xposed modules....I then decided Id rather have a different rom, so
4. I used autorec (which to my understanding changed my kernel in order to workaround boot loader and install twrp? is that accurate?)
5. Booted to twrp, wiped data and installed cyanogenmod and gapps
After this I get stuck and can't boot past the lg logo, so I booted back to recovery and restored my backup. So I did the same and tried pacrom this time with the same results.
I then decided that if I'm going to be stuck with stock rom I at least want my knock on back, so I flashed the patched kernel and same thing- stuck at lg logo....
I know I downloaded the correct zip files and placed them on the root, and always wiped before flashing.
Then I went into download mode on the lg support tool to try to get back to factory, but it says my firmware and recovery is up to date. The odd thing is that the lg support tool shows my phone as ls740 rather than ls980... is this because of something that autorec changed? Do I need to download zip files for ls740 instead? So confused..
About phone in my g2s settings shows android version 4.4.2 and kernel version 3.4.0
Anyways, if anyone could help me to successfully get one of these roms to flash and get back to the kernel that supports the knock code I would really appreciate it.
Thanks in advance!

Cant install a Costum ROM

Greetings to everyone,
I would be happy if you can help me with a little problem on my Note 4.
For some reason I cant install a costum ROM on my Note 4 (N910F).
As soon as I have installed a ROM like NameLessROM the phone reboots, shows the Samsung logo for about 10 seconds, reboots, shows the logo, reboots, ...
Its the same thing happened to me once whileI tried to boot it with no system partition (wiped it)
I am using the newest TWRP.
Anyone got a solution?
Greetings
Robin

Sorry Robin for "hijacking" your thread but we're in the same boat
I'm having the exact same problem with my SM-N910F.
I've rooted the device using Odin3 and "CF-Auto-Root-trlte-trltexx-smn910f.tar.md5". This thread: http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
That went fine and I checked the root privillige afterwords with a terminal app on the phone. I issued the SU command and got at .....root#. Don't know if thats the right/best way to check it!
After rooting the phone I still had the stock recovery tool so again with Odin3 I installed "philz_touch_6.59.0-trlte.tar.md5".
This also went fine and I can now access "PhilZ Touch 6" recovery tool.
From here I've tried installing three different ROM's ("GlamourS6v3_1", "Super.Fast&LolliFamous™[S6+Style+v2][PART.4.0.]_BOC3" and "Super.Fast&LolliFamous_[.PART.6.0.]_BOD2") but keeps ending up with a phone that just keeps rebooting.
When I install the ROM I start with the "Clean to install a new ROM" option and after that install ZIP. The ROM's are located on my SD card.
The installation succed and when I reboot the phone just continues to reboot.
Any good advise?
Regards
John

You have to flash via odin the right modem and bootloader for the ROM that you're trying to install

mone, your a genius! Or maybe you just read the instructions more carefully than I did
I found the exact info and links in the ROM thread and everything is working now.
Thanks!
/John

RDieker201 said:
Greetings to everyone,
I would be happy if you can help me with a little problem on my Note 4.
For some reason I cant install a costum ROM on my Note 4 (N910F).
As soon as I have installed a ROM like NameLessROM the phone reboots, shows the Samsung logo for about 10 seconds, reboots, shows the logo, reboots, ...
Its the same thing happened to me once whileI tried to boot it with no system partition (wiped it)
I am using the newest TWRP.
Anyone got a solution?
Greetings
Robin
Click to expand...
Click to collapse
Okay for Nameless ROM to work on N910F you have to install the SimplKernel and need to update your bootloader and modem accordingly.
imladris said:
Sorry Robin for "hijacking" your thread but we're in the same boat
I'm having the exact same problem with my SM-N910F.
I've rooted the device using Odin3 and "CF-Auto-Root-trlte-trltexx-smn910f.tar.md5". This thread: http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
That went fine and I checked the root privillige afterwords with a terminal app on the phone. I issued the SU command and got at .....root#. Don't know if thats the right/best way to check it!
After rooting the phone I still had the stock recovery tool so again with Odin3 I installed "philz_touch_6.59.0-trlte.tar.md5".
This also went fine and I can now access "PhilZ Touch 6" recovery tool.
From here I've tried installing three different ROM's ("GlamourS6v3_1", "Super.Fast&LolliFamous™[S6+Style+v2][PART.4.0.]_BOC3" and "Super.Fast&LolliFamous_[.PART.6.0.]_BOD2") but keeps ending up with a phone that just keeps rebooting.
When I install the ROM I start with the "Clean to install a new ROM" option and after that install ZIP. The ROM's are located on my SD card.
The installation succed and when I reboot the phone just continues to reboot.
Any good advise?
Regards
John
Click to expand...
Click to collapse
If I''m not mistaken your phone model is N910F, if so you are flashing the incorrect ROMs as the ones you listed are for the exynos variant. So please look for ROMs in the correct thread "Galaxy Note 4 Android Development (Snapdragon)" And using PHilztouch recovery is not recommend and so I would advise you to install TWRP,
N910F = Trltexx
N910G = trltedt
Exynos:
N910C = treltexx

Lg g2 no os at all

Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)

If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC

Spumpkin said:
Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)
Click to expand...
Click to collapse
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk

renzo090513 said:
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk
Click to expand...
Click to collapse
cm11 => jb bootloader
cm12, cm12.1 and cm13 => kk bootloader

klemenSLO said:
If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC
Click to expand...
Click to collapse
The current version is 2.8.7.3. Should I try other versions?

Did you solve the issue? Or is it still not allowing you to get into your F/W?

staylecrate said:
Did you solve the issue? Or is it still not allowing you to get into your F/W?
Click to expand...
Click to collapse
Hi!
I tried to install TWRP version 2.6.6.3, but it fails to flash it so I'm stuck with the version 2.8.7.3. All I'm able to enter is just the recovery mode. I can't enter the download mode so I can't flash the stock firmware.
Currently I'm out of ideas. I can't flash any OS, the TWRP fails everytime and creates errors.

Try flash bumped kernel like lp dorimanx then flash bumped bootstak then lp rom like cloudy or stock. Or google this: lg g2 unbrickable now xda ...that work for me

Rooted, Custom Rom a huge fail

Hello dear Community!
It is depressing that my first appearance here is to ask for help, but I am going crazy.
So, I tried to Root my phone via Odin + CF Autoroot klte and it seemed to have been a success.
The root checker also said, that my device was rooted so I went on and installed TWRP to be able to install Lineage OS.
After getting Lineage to work I got a few error messages suddenly popping up, telling me that either "Music had stopped" or other android operation were closed because they didn't work properly.
I tried to install Gapps, it seemed to have worked but I was only able to open and enter the store once, afterwards the store never managed to load and then the app closed itself after starting it.
So I checked again with Root Checker, but this time it gave me an error message, too. It said, that my device was not rooted properly.
I guess this is were I made it worse by deciding to just root the phone again. Obviously, it didn't work either.
Afterwards I thought that maybe installing The Original Android OS and then unrooting the phone would be the best solution to be able to start anew.
First I tried to flah Lineage again and that made it impossible for me to boot the phone. The farthest I got was the setup page, were it tells you Hello and were you can choose a Language, but clicking the arrow key didn't do anything at all.
The recovery mode was also not the TWRP one anymore, but the original Android one and that was a huge problem for me.
Then I tried to flash the 6.1 OS for the S5 (I made sure it was the correct version), but now it is stuck at the "Samsung" screen while it boots.
It never boots though.
I don't know what to do anymore.
Please, I beg you, could anyone help me out?

Don't flash the latest Lineage OS ROM
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke

mattybourke1994 said:
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
Click to expand...
Click to collapse
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.

Kinloch said:
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Click to expand...
Click to collapse
Thank you so much for your fast reply!
-> I flashed the newest Version for klte via Odin, but I can't get into the boot mode.
I only am able to enter the download mode. What can I do now?

Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.

Kinloch said:
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Click to expand...
Click to collapse
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.

AsylumAlice said:
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
Click to expand...
Click to collapse
just flash supersu in twrp

AronFerr said:
just flash supersu in twrp
Click to expand...
Click to collapse
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.

AsylumAlice said:
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
Click to expand...
Click to collapse
yes just flash it but no wipes

Stuck in TWRP as custom roms are not booting after flashing with TWRP

Hello,
i got a second phone for my GF as i was really happy with this phone and had it flashed without any issues before. This second phone is used and was over a year in use from the guy i've bought it from. It was 100% fine and he always used the shipped Android with it.
So i went on, got the latest TWRP for the phone. Flashed it without any issues and tried to install LineageOS from their website. Flashed it and tried to flash TWRP back as LOS replaces it. I wanted to use TWRP install the backups. But that's where it started to go wrong. Lineage seemed to have been gone from that point on. I couldn't get it to work again, even with reflashing and such. I've downloaded CRDroid and Paranoid and tried them but no luck. Non of them where booting up and TWRP stays showing a warning about "No OS installed".
After some more digging, i've found some posts stating that i would need newest firmware and venders. I've downloaded and flashed them but this made it even worse. The phone started to be stuck in fastboot. I got it working again by flashing latest MIUI version with Xiaomi Flash Tool.
Then i've installed TWRP again but somehow any rom i flash does not boot. The phone starts with the MI logo and flashes once and loads TWRP. There is no message about missing OS or any kind or error when flashing any of these roms.
Anyone able to help me?