Develop Bugs

(HELP) once nexus 7 is on it straight away leads to teamwin recovery

Once Nexus 7 (2013) is being on, it straight away leads me to teamwin custom recovery, it doesn't boot to android. Also in teamwin it says that the data can not being mounted

dhaseegaren said:
Once Nexus 7 (2013) is being on, it straight away leads me to teamwin custom recovery, it doesn't boot to android. Also in teamwin it says that the data can not being mounted
Click to expand...
Click to collapse
Did you get this fixed yet? I was stuck in a TWRP bootloop after trying to flash stock 6.0 is that what you did? If all else fails you can try to boot fastboot and flash the stock firmware, that's what I had to do.

Try this:http://forum.xda-developers.com/showthread.php?t=2471341

Android 6 Marshmallow,MRA58V, TWRP, Rooting, MultiRom
Ok my experience with rooting using N7 2013 and Ubuntu adb stuff. (When I say N7 I mean the 2013 version)
Put Marshmallow MRA58V on the N7 (deleted link per prompting) Tried some of the older rooting methods but one thing is certain, TWRP no longer behaves like it did in the past.
I was running a Cyanogenmod ROMs from July and decided to upgrade from scratch. When I get to the TWRP screen to where I expect it to say it will allow me to globally root the device, I get the "Read Only" mumbo jumbo.
One can hit yes or swipe to go on. Doesn't matter what you select.
Once I get TWRP installed, I have it install Elemental X and SU. Ok up to now. Marshmallow boots up fine and dandy to a usable, stock system that's stable. Now for the fun part. When I install Multi-Rom while in Android 6/Marshmallow, the unit goes through the nominal process of installing the app. It goes back into reboot mode, finishes the install and when it reboots again, it gives me the standard MultiRom screen and the choice to boot into "stock". When I select stock, it boots directly to TWRP period. No amount of dinking around allows me to do otherwise. It will only boot into TWRP and not into Marshmallow. I've done 5 installs with various iterations of "rooting" I could find on the internet ( and here) to no avail. I also tried MRA58K ROM
My goal was to have a stock kernel for app stability and an experimental kernel I could experiment with.. Any suggestions? Do I go back to an older ROM from the 4.4 set?
I will say I bricked up the N7 2013 several times. I found if I brought up the boot loader to START in the N7 screen, I could run the sudo ./install.sh command on the Ubuntu box from the ROM directory directly without the adb command. The command prompt responded it was accessing the bootloader but would sit there for awhile. When I hit the on/off button on the N7, the laptop responded with loading the fresh ROM to the N7 2013 and it fired right up with a fresh install from an apparent "bricked" state. Happy for me. I discovered this as I thought I had bricked the device but good 'ol Unbuntu Linux showed on a "dmesg" command
that the N7 was connected to the USB port. I read that someone did the ./install.sh command directly and by golly it was brought back to life.
I did try to backup the system right up to just before I installed multirom during one of the installs. When I got the perpetual boot behavior into TWRP, I restored the backup and the booting behavior still occurred into TWRP only.
Any suggestions for this "script kiddie" here? I hate to be without Multi Rom but I will at least be able to run a stock kernel. I couldn't find anything but the Open Gapps for Marshmallow and I REALLY miss that
shutdown screen that gave me something like 5 choices. Now I can only "shut it off". Best regards, Kurt

Bootloop after Installing Nethunter 2.0 (Nexus 7 2013 Wifi)

Hello everybody,
i hope the xdadevs can help me with my problem.
Since two Days i try to recover my Nexus 7 form a bootloop.
A week ago i flashed Kali Nethunter 2.0 via TWRP on my Device (Nexus 7 2003 Wifi) - Everything worked fine till yesterday.
My device run out of energy so i loaded it and startet it shortly after that.
Then i regognized the bootloop. I tried to restart the device but it had no effect.
After that i tried to boot into the Recovery Mode with TWRP to restore my working backup. But it got stucked on the loading screen of TWRP too.
Now i tried to recover some images and fix the problem with some manuals which seemed promising. - no success
After a while i did something incredible stupid and locked my bootloader again (i wanted to try to lock and unlock it since some tools couldnt flash the stock rom).
The situation right now:
I cant boot up normaly: Stuck while "Google" is displayed
I cant boot in Recovery Mode (TWRP): Stuck on the blue TWRP Logo
If i try to use the Skipsoft Toolkit or something else it fails - or do i miss something
Recover the Stock rom by using the "flash-all.bat" fails because of this (pastebin. c0m/ie0dBv1D). I used the stock rom of Android 4.4.4(razor-ktu84p) because every other stockrom says this (pastebin. c0m/Dz31k8qu).
I wonder why the stock rom needs to get the bootloader unlocked... ive red so much about it that it just works out of the box..... am i doing something wrong ?
If i try to unlock again, the selection screen on the tablet shows up. I choose yes and hit the Power button. At the console the output <bootloader> erasing userdata" shows up and "freezes?!"... nothing happens afterwards.
Thats about it and this is where i am stuck. I would really appreciate if someone could help me ! I would even reward or spend some money on help.
I try to fix it meanwhile and update this post if something new happens.
I had to alternate the links because im a new member, im sorry for that !
Thanks in advanced and sorry for the spelling

did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?

diehard2013 said:
did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?
Click to expand...
Click to collapse
Yeah i tried it but it couldnt fix my problems. Returning to Stock Rom will always tell me that i need the bootloader unlocked... and i cant unlock it.
My PC and Linux Notebook where recognizing before it was bricked. Now it only gets detected in fastboot because it wont start anymore.

[REQ] Help: bootloop after 7.1.1 beta OTA and cannot enter recovery mode

I've been watching several threads for the last few days, and have not seen this exact issue. I would greatly appreciate some help.
Device:
- Nexus 5X LGH790 32GB
- Stock bootloader / fastboot
- Never unlocked / rooted / etc.
The only advanced thing I've done is join the beta program a few months ago to get 7.0 early. Got that without any issue.
Issue:
I received the 7.1.1 OTA on the day it came out. Installed with no problems. The next day, the phone just froze in the middle of regular use. After about 15 seconds, it started boot looping to the Google splash screen. I can hold volume-down to enter fastboot, but when I select recovery mode, it just starts looping again. Pretty much all I could do was power it off. I did find out by accident that if I left it looping for long enough, sometimes it actually loaded normally (I even saw beta program warning/notice). But when I tried using it for more than a minute, it would freeze, reboot, and loop again.
What I've already tried:
- I tried using the WugFresh NRT fix softbrick method. I was able to quickly turn on debugging one of the times that I left it to loop. But when NRT sent a reboot the phone, it threw it back into the loop and NRT stopped recognizing the device.
- I tried to follow the unbrick procedure using a TOT file in this thread: http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766 But even after using LGUP, I still cannot even get into recovery mode.
- I filed a bug in the AOSP here: https://code.google.com/p/android/issues/detail?id=225802.
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.

Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?

DC_Knight said:
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
Click to expand...
Click to collapse
Try fastboot/bootloader mode and fastboot flash the OTA manually.

Update 2: Seems like all the other things I tried over the last few days have caused various unofficial USB drivers to be installed. I've tried uninstalling most of them. I downloaded the google USB driver from latest SDK. But my 5X is still recognized as a Kedacom device when it is sitting at FastBoot.
However, I must have made some progress because I was able to start the sideload process. Unfortunately, I am now stuck on yet another error. The phone hangs at "verifying update package" and then after about 2 minutes... it reboots itself and starts looping again!
I thought I had it. So close. Now I want to throw the phone. Going to sleep, but would be grateful for any other suggestions in the morning.
- DCK

use nrt to erase all partitions, then download 7.1 factory image, unzip and flash one by one the partitions.

DC_Knight said:
...
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Click to expand...
Click to collapse
Sounds like the boot loop issue many people have been having (the hardware/solder issue). It happened to me a few weeks ago after upgrading to Android 7.0. I got a replacement device from google.

If you're bootloader is locked, NRT or any other method to flash the factory image is not going to work. The only suggestion I have is to un-enroll in the beta program and hope your device will boot long enough to flash the ota Google will send the device to get back to 7.0. Note, this will wipe your device.
Sent from my Nexus 9 using XDA-Developers mobile app

Same problem here. It can't be recognized after I reboot to fastboot. So I can't flash anything.

If the device isn't recognized try this http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33. It's worked for a few of us with the same problem
Sent from my Nexus 9 using XDA-Developers mobile app

Enter stock recovery then flash the full ota via adb sideload

LG G4 boot loop into TWRP

Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.

If you can reach download mode you could try reflashing back to stock then starting again.....Hope you get yours fixed - Sorry to say this but mine did a very similar thing only 24 hours before you posted!!! Only mine was on stock FW and was in use at the time - I've now had to swap it as valuebasket who sold me the phone have ceased trading. If yours is a UK model you may be able to get it replaced under warranty - believe that LG guarantee their phones for 2 years and a ruling by the European court said that flashing a custom rom doesn't invalidate any warranties.

I have the same exact issue, I also flashed the latest CM14 nightly and cannot get the device to boot any rom.
I have even tried flashing stock rom but I get the same problem.
From what I have read, the bootloop issue happens once the device boots but I don't seem to be getting that far.
Any ideas?

Ran into the same problem 3 days ago. This is the first time I have encountered a non-revertible issue in 3 years as a cyanogenmod user. This changes my opinion on how safe it is to make use of a custom ROM. I tried to wipe everything, reinstall TWRP, change TWRP with another recovery, reinstall a safe NAND backup of mine.....nothing.....it went into boot loop. Before I read this post, I was convinced my phone encountered the infamous G4 bootloop problem.....now I see there are other examples, so it shouldn't be the case. Long story short, I had to check my device in at the LG assistance, with 25 days as time forecast.
The guilty nightly was 20161205.
I have never seen anything like this...

This has solved it for me - I installed LG Bridge and flashed the factory firmware using the tool. Now it seems I'm back on stock but at least it's working.

got mine working. I had to install LGUP and flash stock ROM. Once flashed I installed CM14 and I am back up and running again.

I tried LGUP but it could not recognize the device while this was looping.....a bad experience......

I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. I did a cyanogenmod update from within cyanogenmod, which just booted into twrp, then I manually installed the update zip that cyanogenmod had downloaded, then it always boots into twrp. I wonder if initiating the update from within cyanogenmod was the cause. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?

Well. Mine got stuck in bootloop for the second time today. What is going on? In between the two bootloops I had one good update with CM. Using TWRP 3.0.2.1. Steps to reproduce failure: updating CM from within CM, it autoreboots into TWRP and after that nothing happends, no autoinstall. Then after a manual install of the new CM the bootloop starts.
Resolve the problem:
* Install LGUP 8994 DLL Ver 0 0 3 23, Install LGUP Install Ver 1 14, get the latest KDZ
* Get the phone into download mode with usb cable and after that in firmware update mode
* Startup LGUP and choose refurbish and select the kdz file.
* After that you can boot into your stock LG firmware again, reinstall TWRP an CM. If you want so.

Read that it is advised to manual update cm from within TWRP. TWRP will get an update in the future to solve this bootloop problem.

iankelling said:
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. After a cyanogenmod update, it always boots into twrp. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Click to expand...
Click to collapse
I second that. Same issue and neither LG Up nor LG Bridge will recognize my device. Looking in device manager there are no serial interfaces. Do I need a special driver that provides a com port for a phone in recovery or fastboot mode?
---Edith 2016-12-12: Found a solution for my issue:
The phone has to be in _download_ mode, not in recovery or fastboot. After realizing that I have to boot the phone in a different manner, it will be recognized by LG UP.
Here is how to boot the pone in download-mode:
- Power off your LG device.
- Press and hold Volume Up button.
- Connect your device to PC with a USB cable while holding the Volume Up button.
- You’ll boot into download mode with “Firmware Update” written on top of the screen.
Now everything is fine again.

croclacrimae said:
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
Click to expand...
Click to collapse
I was able to get out of that by also wiping by-name/misc. Don't do that, though, because then your wifi mac address will get messed up and you'll spend all day looking for a permanent fix for that.
I suggest reflashing a stock KDZ using LGUP, as others have said. You can get the usb drivers from LG Bridge.

I will release a fix for that soon. Check the twrp thread for updates on this.

Hi
I also have this problem
I installed cm-14.1-20161201-NIGHTLY-h815 successfully and was running it for almost 2 weeks without issues, today I updated to cm-14.1-20161213-NIGHTLY-h815 from cmupdater and I have been ending up in recovery every time I rebooted.
I tried flashing the latest cm recovery and reflashing the rom, with full wipes but no luck.
Full steps of recovering would be appreciated (for example, there are comments about flashing the latest stock rom, but a link to this rom would be helpful)
Thanks

Good news regarding this:
http://forum.xda-developers.com/showpost.php?p=70082901&postcount=213
The above will fix TWRP bootloop issues as well and I also released a first h811 version which should allow installing CM etc as it should.
Keep in mind that this is a BETA and not an official TWRP release.
Please report back in the above thread!
.

Does your twrp beta really fix the boot loop even it is already happening. What do I have to wipe? I have not managed to get out of the boot loop despite intalling it.
Is using using LG Up to flash to the stock rom really the only option?
Edited 2017-01-25 2:45 pm:
Well, sometimes you just have to be patient. Powered down the phone and when th H815 restarted CM did boot. Great. :good:

Hey, I just want to share a small detail, possibly a fluke that helped me overcome the bootloop.
So...I started with a fresh, stock H815, I don't quite remember the firmware version..it was something like version "20g"..
OK, I looked up several guides and tried to get the newest stable versions of each tool. I went through with the official bootloader unlock, then moved on to rooting: Kingroot didn't work for me so I went on installing twrp in fastboot mode so I could afterwards install supersu and root.
I got there eventually but first I was stuck in bootloop - kept ending up in twrp interface. I found the 2 dd commands but those didn't work for me as the msm_sdcc folder did not exist, but instead there was a "f9824900.sdhci". Tried to overwrite this one ...but as others have stated as well, it didn't work.
At that point, I had nothing to lose, I was starting to accept that I had soft-bricked my precious G4 so..I went on installing the DU 10.6 7.1.1 rom and the stock gapps, wiped dalvik, rebooted and held my breath...not literally
About 12 minutes later, after an endless red, spinning logo, my shiny ping pong paddle showed me a different screen, a fresh start welcome screen .
Almost 24h / 10-12 reboots (twrp included) / 70+ apps installed and removed later, the new OS holds around 2G ram average, a bit better battery life, smoother transitions, flawless navigation, flush streaming over both 3G/LTE & 2.4/5 G wifi.
FYI the reboots were intended, wanted to see consistency in boots - we're in the green . Now testing long term stability with moderate/high usage.
There is 1 aspect I noticed, there are a couple of contexts when the interface burps (several menus, various situations, never in apps) and resets back to homescreen...but I think that's more of a launcher topic than an OS one.
Other than that, so far I'm happy with the mod.
Hope my experience helps others that might be in the same spot I was or at lest boosts their confidence to try out a decent idea they might be pondering.

Unable to restore backup a3

Hi all, i recently flashed lineage os 16 on my a3 2017 ( A320FL). Before that i obviusly create a backup file with twrp, you know just in case. Now i'm trying to restore the orignal rom but phone get stucked.
I made a total wipe with twrp and then installed the backup (it is on sd), evertything goes fine i reboot first logo appears (galaxy a3 samsung powered by android) second logo appears (the flashing samsung) but then it get stucked. I waited like 30mins but nothig happened. When stucked in this logo i'm unable to power it off, i must enter the "odin mode" then rapidly shut off odin mode and enter recovery mode (if i'm not quick enough it just reboots and get stucked again in samsung logo). Backup is fine, it passed without any problem the checksum. Any suggestion?
Quick update:
I was able to install Lineage os 15, so i don't think is a custom recovery's problem. Still cannot install the stock one from my backup.

cholas_ni said:
Hi all, i recently flashed lineage os 16 on my a3 2017 ( A320FL). Before that i obviusly create a backup file with twrp, you know just in case. Now i'm trying to restore the orignal rom but phone get stucked.
I made a total wipe with twrp and then installed the backup (it is on sd), evertything goes fine i reboot first logo appears (galaxy a3 samsung powered by android) second logo appears (the flashing samsung) but then it get stucked. I waited like 30mins but nothig happened. When stucked in this logo i'm unable to power it off, i must enter the "odin mode" then rapidly shut off odin mode and enter recovery mode (if i'm not quick enough it just reboots and get stucked again in samsung logo). Backup is fine, it passed without any problem the checksum. Any suggestion?
Quick update:
I was able to install Lineage os 15, so i don't think is a custom recovery's problem. Still cannot install the stock one from my backup.
Click to expand...
Click to collapse
Does it work if you just restore system and boot?

iloveoreos said:
Does it work if you just restore system and boot?
Click to expand...
Click to collapse
Hi, sorry for the delay i was busy in these days, thanks for your answer. However I just tried but nothing. Still stucked on the Samsung screen and unable to shutdwon.

cholas_ni said:
Hi, sorry for the delay i was busy in these days, thanks for your answer. However I just tried but nothing. Still stucked on the Samsung screen and unable to shutdwon.
Click to expand...
Click to collapse
Does it work to hold power and volume down for it to shut off?

iloveoreos said:
Does it work to hold power and volume down for it to shut off?
Click to expand...
Click to collapse
Thanks again for your answer. However yes, it worked but it immediatly rebooted itself as i mentioned at the beginning of the thread. However, if anyone will ever meet a similar problem here's how i solved it:
I downloaded the last stock firmware and flashed it with odin, overwriting everything (custom recovery too, you can re-flash it in the future if you want). If unsure of the firmware version and you have a (unusable) backup like me check the folder where is saved: by default last digits correspond to your firmware version (mine for example was 320FLXXS3CRK3).

cholas_ni said:
Thanks again for your answer. However yes, it worked but it immediatly rebooted itself as i mentioned at the beginning of the thread. However, if anyone will ever meet a similar problem here's how i solved it:
I downloaded the last stock firmware and flashed it with odin, overwriting everything (custom recovery too, you can re-flash it in the future if you want). If unsure of the firmware version and you have a (unusable) backup like me check the folder where is saved: by default last digits correspond to your firmware version (mine for example was 320FLXXS3CRK3).
Click to expand...
Click to collapse
Awesome! Is everything working good now?

iloveoreos said:
Awesome! Is everything working good now?
Click to expand...
Click to collapse
Yes, almost 10 hours now and 0 problems. Just like a normal phone after factory reset.