G4 stuck in bootloop !

Hello,

I'm having a really bad situation with my G4 (H815L),
My new UNROOTED device just decided to enter a bootloop, I tried to make a factory wipe but it got back into bootloop,
I tried to flash a stock firmware with the flash tool but again it got back into the loop.
Tried to find a TOT files for this version but I couldn't find one. :(
Does anybody have a solution for this ?

Thanks.

Stuck in a bootloop

Before I start, I wanted to inform you that I am a newbie so please be patient because I'm in dire need of help.

You can view my other thread here to get more backstory:
http://forum.xda-developers.com/spri...3#post63109703

As of right now I am in a very annoying bootloop. After trying to unroot my phone by flashing a stock 5.1.1 ROM and failing, I decided to try and manually unroot my phone. I deleted the files /system/xbin/su and /system/apps/Superuser . I have looked around for hours looking for answer and I can't seem to find a working one. Please help me! Thanks.

Lollipop Bootloop, Huh?

Totally my fault as I know not to use kernel cleaning scripts but...

While playing with a new in box N7'13 I went to switch between Glitch and ElementalX while contemplating Timur's.
I flashed a kernel cleaning script After reading the update script and seeing nothing that I thought would create problems.

I've flashed the lollipop factory image and it will not boot. I flashed the Kit Kat factory image and it boots fine, Going back to Lollpop, bootloop. It's been given plenty of time on each occasion for lollipop to boot.

Ideas?

Thanks...

Xperia Z1S Bootloop Help please!!!!

Hi please help me
I have got an Xperia Z1s running on lollipop Rooted
i tried to change the LCD Density followiong the steps in this tutorial : http://forum.xda-developers.com/show....php?t=1428830
but ones i clicked on Reboot my phon is only showing me the sony logo then a black screen then it reboot again and again and again.......
i tried to flash the phone with flashtool using the same ftf file (lollipop ftf 14.5.B.0.236)
but it's saying that the flash is aborted

i also wanted to tell you that my bootloader is unlocked :

First boot problem, stuck in bootloop

Hello, a friend of mine bought a moto x play black today, he buy it online, but the phone keep restarting itself after a few seconds of use and go in bootloop. We turn it off, turn it on again, it work for 20-30 sec and it restart again and go in bootloop. We made a few tries but we always get the same problem. There is a chance to fix it or we must give it back and ask for a refund?

Thanks a lot in advance

Stuck into TWRP bootloop

Folks,

I tried to reboot the phone today (completely working and functional, running Euphoria), but instead of rebooting, it booted into recovery; and stays there no matter what. I restored my nandroid backup, did factory reset, fixed permissions... none of them works. even when choosing power off or bootloader in TWRP, it again reboots into recovery.

This is the first time I see this, I searched a bit, but couldn't find an answer, any help is appreciated.

P.S. I found this on another device thread, but even this didn't work for me on OPO:

" Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER "

sudden bootloop

Hey guys I've got a problem.
I installed a navigation app and downloaded the map data for a country ( 700Mb).
During the process my phone crashed.
I didn't think much of it so I gave it another go. Now my phone is stuck in a boot loop.
Also can't go into recovery.

My phone is unlocked rooted , but i'm running the stock firmware (4.4.4).
I recently wanted to restore the phone to it's stock config. but had a problem with a file "E:Unable to stat.....".

EDIT: I can now go into the recovery boot screen (phone is recognised via adb) but then it reboots again.
Any solutions?
All help would be very appreciated.
Daniel

XT1032 Bootloop after recovering backup

Hi everyone,

I was gonna update to a new version of CM12.1 (was originally using the 27/08 version, and i was gonna update to 30/09 version). So I made a backup, then I tried to restore it, because last time I updated, the update failed and the backup was bad too. So, I restored it, and then the phone went into a bootloop. When I tried to boot into Recovery (Fastboot -> Recovery), it would reboot and get stuck, then reboot again.

The things I did in order:
Try to get into bootloader a couple of times
Reflash TWRP in fastboot (fastboot flash recovery twrp.img, was version 2.8.6.0)
cmd: fastboot erase recovery
cmd: fastboot erase cache
Flash TWRP again
cmd: fastboot erase system
Flash CyanogenMod Recovery
I can boot into that now
Try to flash CM12.1 nightly 30/09
Factory Reset (Recovery crashes before it is completed)
cmd: fastboot erase data (I get this error in the cmd:
erasing 'data' . . .
(bootloader) Invalid partition name data
FAILED (remote failure)
finished. total time: 0.016s

I just get 'cmd: erase:data' with no error in the fastboot.)

So I think the problem is in the data partition, but I don't know how to fix this.

Thanks in advance!

Bootloop and Bad Partition Table? PIT File Please?

Hello!

I got a Galaxy Note 2 second hand and there is something wanky going around.

So the current status of the phone:

The phone will not go into twrp or odin mode without the charger in. However, I check the battery voltage and it was at full charge, 3.4v? ish?

When just pressed power button alone, it goes into a bootloop. So far, it glitches into the galaxy note 2 logo then back to battery with screen. Or other times, it goes into bootloop with only battery screen then on and black screen, which this further repeats.

There are no partitions mounted when observed inside twrp. 0mb so I am assuming that the previous owner tried to flash a custom rom and may have failed at or something.

So my current conclusion of the phone after researching and experimenting with a little knowledge about anything:

The phone has its partition table messed up (ugghghghgh) and there is no platform for the OS or Android to be flashed on to when I was trying to using odin for couple past days.

Any ideas? Anyone have a PIT file that I can test this with? I got some pit file online that I assume that is for Sprint Galaxy Note 2, but re-partitioning with that PIT doesn't seem to do anything.

Any ideas how to approach this?

P.S. it also says that it can't mount /data. Assuming because it doesn't have any partition within the phone itself but could there be any different reason?

Got stuck on bootloop Plzz help guys coz i love my phone!!

As i was trying to install PHILZ recovery my mobile got stuck on boot screen and unfortunately the bootloop begin . As in my mobile to enter recovery mode i have to connect my mobile to charger then press volume up + power button but its not helping it still keeps booting.Help me guys what to do now as i have not much knowledge about adb.

If you're getting a "select language" bootloop when installing Cyanogenmod 12.1

Hello everyone!

I'm opening this post because even though it does say so in the Wilson's ROM, there are suggestions to the contrary on other ROM threads. This might only be necessary for the 32gig version

I was desperately trying to get CM12.1 flashed onto my 32gig mi4i which comes stock with MIUI 5.9.15, and nothing was working. Wiped everything, formatted, tried different sets of GAPPS, tried different ROMS... no cigar. It would flash, optimize apps, reboot, go onto language selection screen, get stuck for a few seconds, and reboot. and reboot. and reboot. you get the idea.

You ABSOLUTELY need to flash MIUI 6.6.10 first. No other version of MIUI will work. I tried a couple of others first since 6.6.10 was taking forever to download to no avail. I put the patience in, downloaded 6.1.10, flashed the UBER ROM and voila! works first try.

I've only been toying with it for an hour or so but i'm really, REALLY loving it. I'm not a fan of MIUI but I could have gotten used to it, however the ****ty recent apps drawer and the useless lockscreen were deal-breakers for me. I'm a lot happier with my Mi4i purchase now!

Thanks a lot to everyone putting in the effort to port and compile these ROMs so noobs such as myself just have to hit a few buttons to get them working.

Samsung Galaxy Ace 5830i bootloop

Hello Guys, i need some help My samsung galaxy ace i is on bootloop and the volume down button doesn't work, how can i do a hard reset without it? or even flash it in download mode? I didn't try to root it or something, it just become that way.

Phone stuck in bootloop

Good morning everybody.
I have a rooted Galaxy xcover 2 with link2sd installed in order to solve the classic memory issue problem. The program gave me troubles in moving apps to the sdcard, so i read on the internet that i should format the sdcard properly in order to use it.
Afer followind the procedure of the tool, my phone got stuck in boot.
I can still use download mode and odin works, but
-If i flash the stock rom, i cannot anymore access cwm recovery
-if i flash cwm recovery, the boot sequence let me access ONLY the recovery (like there is no rom inside).
when i try to wipe from cwm, it says it can access to cache and data partitions.

I think that the tool damaged somehow the partitions of my phone. How can i fix that?
I've been oversecure while flashing and i didn't make any nandroid of my phone. Can anyone give me one?

your help is veery appreciated,
Thank you!

PS: if you need to looki inside the tool code, there is a file called "dos.sh", but i didn't find anything particular

Bootloop on Lollipop Stock

So, yesterday i tried to install Euphoria OS on my phone, but in all of a sudden, the /cache partition corrupted, i was dumb enough and deleted it via TWRP, making my phone fall into the QPST status.

After fixing it, i proceeded and reflashed KitKat, but the phone only shows 8GB instead of 16GB, so i tried to fix this by flashing TWRP, everything went well, until i upgraded to Lollipop again.

It always bootloops no matter what i do, i really need my phone with my 16GB of storage back, it isn't a Hardware failure since the QPST diagnosis didn't say anything about mobo failures.

I can mount all the partitions, i can wipe it all, i can boot into bootloader and recovery, i can do basically everything but booting the system.

Any light on this? it either happens after i flash TWRP or after i try to root it.

Im running Android 5.1.1 stock.

Flashtool don't flash boot delivery - stuck in a bootloop

Help please, my flashtool don't flash the boot delivery ( bootbundle ), it says "no bootdelivery to send" , so now i stuck in a bootloop, please help :crying:

Help! Bootloop after editing Build Prop.

I tried to fix the memory leak issue by editing the build prop. But after I inserted it and rebooted my phone kept boot looping. I was OE2 Rooted, can I flash OE2 in Odin and then re root or what is the best course of action?

Thanks

IDENTIFIED: cause of Xposed bootloop on Z3+

I've identified the cause of bootloops on Z3+ with Xposed.

When looking at a logcat after the bootloop it can be seen that the cause is com.google.android.gms, crashing after some intervention by Xposed libart.so

Code:

---

--------- beginning of crash

F/libc    ( 8226): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x4 in tid 8241 (Signal Catcher)

I/ThermalEngine(  620): ACTION: BACKLIGHT - Setting max LCD brightness to 52

I/ThermalEngine(  620): Mitigation:BACKLIGHT:52

D/illumination-service(  626): 'thermal': Color 00343434, BrMode 0, OnMS 0, OffMS 0, Mode 0

D/clmlib  (  608): Got activities:0x0000000E

I/Process ( 1674): Sending signal. PID: 1674 SIG: 3

I/art    ( 1674): Thread[9,tid=1687,WaitingInMainSignalCatcherLoop,Thread*=0x7f85521800,peer=0x12c02080,"Signal Catcher"]: reacting to signal 3

W/art    ( 1674): Suspending all threads took: 18.026ms

I/DEBUG  (  608): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

I/DEBUG  (  608): UUID: b0341a53-b861-4217-bce5-8fe4798b8faf

I/DEBUG  (  608): Build fingerprint: 'Sony/E6553/E6553:5.0.2/28.0.A.8.251/1150652000:user/release-keys'

I/DEBUG  (  608): Revision: '0'

I/DEBUG  (  608): ABI: 'arm64'

I/DEBUG  (  608): pid: 8226, tid: 8241, name: Signal Catcher  >>> com.google.android.gms <<<

I/DEBUG  (  608): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4

W/dex2oat ( 8299): Compilation of com.google.protobuf.nano.k com.google.c.g.c.a.n.mergeFrom(com.google.protobuf.nano.a) took 108.714ms

I/DEBUG  (  608):    x0  0000000000000028  x1  0000000000000004  x2  000034746961770a  x3  0000000000000070

I/DEBUG  (  608):    x4  0000007f956ffa00  x5  0000007f956ff998  x6  0000000000000000  x7  0000000000001002

I/DEBUG  (  608):    x8  0000007f956ff760  x9  0000000000001002  x10  00000000000000b0  x11  0000007f85512407

I/DEBUG  (  608):    x12  0000000000000020  x13  88c5a592539be2de  x14  88c5a592539be2de  x15  0000007f956ff1dc

I/DEBUG  (  608):    x16  0000007f967fafd8  x17  0000007f9644e9c8  x18  0000000000000028  x19  0000007f956ff760

I/DEBUG  (  608):    x20  0000007f8d584048  x21  0000007f956ff990  x22  0000007f90ae24c0  x23  00000000702bd430

I/DEBUG  (  608):    x24  0000007f96770020  x25  0000007f956ff990  x26  0000007f9675d238  x27  0000007f96774628

I/DEBUG  (  608):    x28  0000007f96748000  x29  0000007f956ff6f0  x30  0000007f966b07f4

I/DEBUG  (  608):    sp  0000007f956ff6f0  pc  0000007f966b06b4  pstate 0000000060000000

I/DEBUG  (  608):

I/DEBUG  (  608): backtrace:

I/DEBUG  (  608):    #00 pc 000000000032a6b4  /system/lib64/libart.so (art::DumpNativeStack(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, int, char const*, art::mirror::ArtMethod*)+300)

I/DEBUG  (  608):    #01 pc 00000000002fd718  /system/lib64/libart.so (art::Thread::DumpStack(std::__1::basic_ostream<char, std::__1::char_traits<char> >&) const+260)

I/DEBUG  (  608):    #02 pc 00000000003087dc  /system/lib64/libart.so (art::ThreadList::DumpForSigQuit(std::__1::basic_ostream<char, std::__1::char_traits<char> >&)+172)

I/DEBUG  (  608):    #03 pc 00000000002e9958  /system/lib64/libart.so (art::Runtime::DumpForSigQuit(std::__1::basic_ostream<char, std::__1::char_traits<char> >&)+96)

I/DEBUG  (  608):    #04 pc 00000000002f21b4  /system/lib64/libart.so (art::SignalCatcher::HandleSigQuit()+1104)

I/DEBUG  (  608):    #05 pc 00000000002f2dc8  /system/lib64/libart.so (art::SignalCatcher::Run(void*)+456)

I/DEBUG  (  608):    #06 pc 000000000001ba00  /system/lib64/libc.so (__pthread_start(void*)+52)

I/DEBUG  (  608):    #07 pc 0000000000017cf0  /system/lib64/libc.so (__start_thread+16)

---

An examination of the filesystem showed that com.google.android.gms (Google Play Services) installs an apk and an odex file in /data/data/com.google.android.gms/app_chimera/chimera-module-root/module-b4902ed544a9b2fc3415a9fb64fb048759fc2157. The long hashed folder name changes, as you can imagine with a name like "chimera".

Since I've previously had problems with un-odexed files and Xposed, I figured I try to manually de-odex it and then install xposed to see what happens. Previously, I'd been getting repeated boot loops no matter what I did.

What do you know, it worked. On first boot, I had a crash. When the device came up again it was stable and able to run Xposed and various modules. What did appear to have happened, however, is that after the first boot the hash filename had changed to a different hash and a new odex file and apk was in it's place.

With this knowledge in mind I did a more targeted search on Xposed and com.google.android.gms and come across this discussion on Github. Copy/pasting from the discussions

Quote:

Originally Posted by rovo69 GMS correctly detects that the odex file is outdated and opens a DexClassLoader to recompile it. This finally ends up in ClassLinker::GenerateOatFile(), where one of the changes for Xposed finds the odex file and uses it for the --dex-file option instead of the APK. Normally, this works fine, but due to compiler-filter=interpret-only, the previous version of the odex has been optimized with more invoke-quick calls, which now fail to resolve with the new boot image. So the odex-instead-of-APK mechanism has to be restricted to apply only for certain odex files.

There appear to be some commits to the Xposed repo to fix this problem, 18 days ago, which is post- the latest v74 of Xposed and so not available in any official release. I need to sync the latest AOSP 5.0.2 sources in order to build Xposed from the sources, so I'll get around to making an updated unofficial version of Xposed that hopefully should work on Z3+.

However in the meantime if you're impatient, you could use the temporary approach I used by manually deodexing the MapsModule.odex and replacing the apk/odex before installing. When I did this, I first did a reboot to TWRP, wiped cache and dalvik, then rebooted, ran Play Store. I verified that Play services worked ok, then rebooted to TWRP again and installed Xposed. I've attached the deodexed apk - when installing it don't forget to chmod it it 644.

On the first boot post installation of Xposed I got a crash. The second boot worked fine. Looking at the chimera module folder, I saw that the hashed folder name had changed and I speculate that the odex had been regenerated, I presume this time to one that was updated and so the Xposed crash didn't occur because of an attempted recompilation. Unfortunately I omitted to do a logcat on first boot and so I can't assert this for sure. I just know the workaround was successful, if a little clumsy...

Attached Files

MapsModule.zip - [Click for QR Code] (981.3 KB)

What to do if you bootloop?

Title says it all. For people like myslef that sometimes play with fire and try de-bloating too much or maybe flash a bad Xposed module what can we do if we get stuck in a bootloop.

I've seen people say you should keep the stock and rooted versions of whatever version firmware your on the External SDcard.

So lets say you bootloop and you have the stock and rooted images on your phone...what then? Will we still be able to get into download mode by plugging in the USB cable and volume up? Whoever, knows for a fact please advise the steps to get the phone working again.

Appreciate any and all feedback

Bootloop Problem

hi im using Samsung galaxy note 2 and my phone got softbricked. It just shows Samsung galaxy note 2 booting screen I have tried clearing davlik cache,factory reset,wipe cache but there is no change. all I did was to install rom it booted and got struck on the note 2 screen.please fix this.. Thanks in advance

Bootloop

Hey guys,

I'm on the newest 10N TMO rom. Everything's stock - no root, stable 3rd party apps, no debloat..

So I'm on the plane, playing around with the gogo inflight texting thing, which I tried with four phones and it's still never worked... My phone stopped responding and attempted to reboot - except it never finishes booting because it keeps on showing the black LG - LIFE IS GOOD screen. I attempted to master reset with the down and power button, but even after the reset, it throws me back into the loop. I've tried booting it on with or without the SD card and SIM, but it doesn't make a difference. TMO is sending out a replacement unit, but I know it's going to be a refurb. I've had the worst luck with TMO replacements since they just end up sending me someone else's broken device... The phone doesn't react to vol up + power to enter download mode either.

Any other ideas?