Boot Loop SPG611 Need help to root my tablet please

Hello,

I got the Z3tc SPG611 on lollipop firwmare .200
No matter what I tried I keep on getting bootloop

I have followed instructions: developer option, unknown source, install driver for flashtool successfully on win10...
I flashed the old firmware without any exception, and then the D6603 exploit system only.
When I try to restart the tablet it keeps on bootlooping at the blue animation thing.

the only thing i am not confident about is the MTP mode, i can't find the option to turn it off (not in storage like on nexus devices).

any help would be appreciated. thanks

Need help with unbricking Samsung Galaxy S6 [G920F] - stuck on boot loop

I'm completely hopeless, and all I can count on are good people from XDA to help me.

I bought a new Samsung Galaxy S6, T-Mobile version [G920F], running Android 5.1.
I used this tutorial:
http://www.droidviews.com/root-samsu...ry-all-models/

I enabled USB Debugging, downloaded latest Samsung USB drivers.

First I successfully installed TWRP 2.8.7.1, and meanwhile copied the SuperSU.zip to my device.
I had successfully entered TWRP, went to Install, and selected teh SuperSU file. It said it was done, so I went ahead and restarted my device.

Immediately, I noticed that the device was stuck on the boot logo (Galaxy S6 + Powered by Android screen).

And for some reason, when I connect the device with USB to mc PC, Windows says it's "damaged or undetected", something of that sort.
Luckily, I can still detect it in ODIN.

I might mention that I can still enter TWRP & Download Mode from the Bootloop.

I'll give any more information I can, just tell me if there is any hope for me.
Thank you so much.

Help!! Note 4 not booting up. Boot loop on samsung logo

I have a problem with my note 4 and hoping someone can help me. It is currently in a bootloop and won't go past the Samsung logo. Every time it gets to Samsung logo it just go off, vibrate twice and then restarts again over and over. I can't go into recovery mode as well and when I flash twrp or cmw I get 'recovery is not seandroid enforcing set warrenty bit'. Below is what I have tried so far:

Flash 3 different stock firmware, all flashed successfully but still boot loop
Flash bootloader
Flashed stock recovery, cmw and twrp
Flash pit file

I don't know what else to try. ANYBODY ABLE TO HELP? THANKS

Solved Boot Loop After Factory Flash Build mdb08i in fastboot on my Nexus 5X

Hi guys,

I was getting boot loop every time I tried to factory flash mdb08i from https://developers.google.com/androi...s/images?hl=en on my Nexus 5X. I flashed this build more than 5 times and let the device run 20+ minutes during boot animation.

I generally used method 2 from Nexus 5 tutorial since that was the tutorial I used on my Nexus 5:

Code:

---

fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
(Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img
fastboot erase cache
fastboot flash cache C:\androidimage\cache.img

---

However, the missing piece that solved my boot loop was to also run this command at the very end

Code:

---

fastboot flash vendor vendor.img

---

I normally have a batch script that runs all the commands for me.

How I found out about flashing vendor.img:
I found this issue only after I factory flashed mdb08i that I accidentally immediately flashed chainfire's modified mdb08i boot image for enabling root. After flashing chainfire's modified mdb08i, my Nexus 5X passed the boot animation but gave "Internal device error". So I looked up the error and found this thread: http://forum.xda-developers.com/nexu...xus-9-t3112827

I also tried other methods as mentioned in this thread but no luck with it on my end but perhaps will help others: http://forum.xda-developers.com/nexu...image-t2527382

Hope this help others who are also stuck on boot loop after flashing mdb08i on their Nexus 5X.

"Welcome to Hangouts" loop

I see some people are having Hangouts problems. This is mine -- the "Welcome to Hangouts" window never goes away, even after I click "GOT IT". I've tried erasing app data and even a factory reset (when I did my bootloader unlock). It still happens.

Anyone else?

Moto X (1st Gen.) XT1049 Stuck in boot loop. Need Help.

My stock, unrooted Republic Wireless Moto X decided that it no longer wanted to boot into android after I powered it down to charge. I can get into fastboot but none of the options work except "Barcodes". "Recovery" gives me the error "Boot up failed." and the other options just cause the phone to restart. Please help.

[GAME][+4.0] The impossible geometry loop

The impossible geometry loop is simple, relaxing, an endless game ( infinite game ). Guess the hieroglyph with geometric figures. Free puzzle dash game available on Google Play Store. Hours of fun and brain training.

Complete levels forming geometric figures, unites all the figures . The game of geometry controls are simple and only have to click on each shift parts for watching it spinning, and on and on until all the elements forming a geometric figures in which no protrusion is loose and everything is connected in dash . The impossible geometry loop has easy control !!

This game of logic and geometry will make you keep your mind active and will make you think to complete the infinite levels of play. Open your mind !!

S3 i8190l stuck in loop after flashing CM12.1

Hey everyone,

I'm having a problem after trying to flash CM12.1 on a i8190l.

The instructions I basically followed are the ones mentioned here: novafusion.pl/tutorials/installation-guide-golden/ and I used the rom Lollipop 5.0.2 (CyanogenMod 12.0) 20150428 stable with the Odin app to install it.

All went well up to the point 12. Click on Wipe, then use slider on the bottom to let process begin.

At this point I received a FAILED message with an error message saying below that /data couldn't be mounted. After that, I rebooted the phone, and it started loading the first android screen apparently. After a few minutes, Android threw up an error saying that it couldn't encrypt the data and had to reboot. After that reboot, the system won't stop going over a loop boot that flashes TeamWin over and over again.

I can still get to the download mode, what is the recommended step to take from here? Is it possible to recover the OS? Do I have to worry about the battery running out, or does it charge up while on download mode/other mode?

Thanks for your help

S3 i8190l stuck in loop after flashing CM12.1

Hey everyone,

I'm having a problem after trying to flash CM12.1 on a i8190l.

The instructions I basically followed are the ones mentioned here: novafusion.pl/tutorials/installation-guide-golden/ and I used the rom Lollipop 5.0.2 (CyanogenMod 12.0) 20150428 stable with the Odin app to install it.

All went well up to the point 12. Click on Wipe, then use slider on the bottom to let process begin.

At this point I received a FAILED message with an error message saying below that /data couldn't be mounted. After that, I rebooted the phone, and it started loading the first android screen apparently. After a few minutes, Android threw up an error saying that it couldn't encrypt the data and had to reboot. After that reboot, the system won't stop going over a loop boot that flashes TeamWin over and over again.

I can still get to the download mode, what is the recommended step to take from here? Is it possible to recover the OS? Do I have to worry about the battery running out, or does it charge up while on download mode/other mode?

Thanks for your help

HTC Rezund recovery not load after installed and OS boot loop. HELP!!!!

Hi, i need your HELP with this problem, i have look around this forum looking for a solution about similar ISSUE and i haved done STEP by STEP the procedure and when done my HTC wont load THE RECOVERY. I have been reading solutions about 4 days ago..

THIS WHAT HAPPEND:I
I replaced the LCD Screen Display correctly and when i turn it on it went directly to the BOOTLODER, since then my Rezound its been booting with the white "HTC" screen for fews seconds then LOOP again. no recovery boot and niether OS

THIS WHAT I DID:
Hi, i need your HELP with this problem, i have look around this forum looking for a solution about similar ISSUE and i have done STEP by STEP the procedure and when done my HTC wont load THE RECOVERY. I have been reading solutions about 4 days ago...

THIS WHAT HAPPEND:
I replaced the LCD Screen Display correctly and when i turn it on it went directly to the BOOTLODER, since then my Rezound it’s been booting with the white "HTC" screen for few seconds then LOOP again. No recovery boot and neither OS

THIS WHAT I DID:
I download ruu, rom, and all recovery versions lists above and installed them correctly according the ADB SCREEN, but when I try to enter to recovery it stock in white screen logo HCT

MY REZOUND INFO:

TAMPERED
UNLOCKED
VIGOR PUT SHIP S-OM RL
HBOOT.2.28
RADIO 2.23.10.123R/2.23.10.0124R

INFOversion: 0.5
INFOversion-bootloader: 2.
INFOversion-baseband: 2.23
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.05.605
INFOserialno: HT1BJS214553
INFOimei: 990000339159446
INFOproduct: vigor
INFOplatform: HBOOT-8260
INFOmodelid: PH9810000
INFOcidnum: VZW__001
INFObattery-status: good
INFObattery-voltage: 3651m
INFOpartition-layout: Gene
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: c
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!

RECOVERY INSTALLED AND NOT WORKED:
CWM-6.0.4.4-recovery
openrecovery-twrp-2.8.0.1F-vigor
recovery-clockwork-touch-6.0.3.1-vigor
recovery-ra-vigor-3.15-gnm
twrp-2.4.3.0-vigor
twrp-2.4.4.0-vigor
twrp-2.5.0.0-vigor
twrp-2.6.0.0-vigor ECT...
recovery-ra-vigor-3.14-gnm

I been doing this several times and different method as: rename recovery to PH98IMG.zip and installed from SD CARD, I been used ADB command "fastboot fast recovery recovery.img ect... all succeed but when calling the recovery partition it stuck.

ANY HELP about these issues i will appreciate it.

Boot Loop On standard Firmware

I have been on CM12 for a while now and decided to go back to stock firmware, but after downloading the h3g and btu firmware i get stuck in a boot loop with both after either the 3 splash screen or the Samsung splash screen, any ideas why this is?

e: partition problem and boot loop issue. How do I fix it?

Hello. I have a kindle fire HD 8.9 32gb that I'm trying to fix for a friend. When I received it the tablet would boot to a screen that gives you the option to reboot or to try to reset to factory default. Neither option resolves the issue. I downloaded a bunch of programs and followed recovery guides and nothing works.

I can get it into fastboot and I got it to say it was flashing a new recovery, bootloader, and rom image, but when they were done, it now boots to scrolling text stating that it has an issue with the e: partition. Something similar to it can't access that partition. I don't see any mention of partitions in any recovery guides or software. Any ideas? Thanks!

Nexus 6 - Google splash screen boot loop after flash of 6.0 factory image (unlocked)

Hi,

I'm hoping for some suggestions regarding my boot looping Nexus 6. Here's the details:

- Brand new device.
- First boot & setup. OK.
- Unlocked bootoader. OK.
- Reboot back into 5.0. OK.
- Tried to flash 6.0, initially using flash-all.bat from shamu-mra58k-factory-5b07088c.tgz. Failed.
- Extracted zip inside shamu-mra58k-factory-5b07088c.tgz and flashed all .IMG manually.
- Phone now stuck in boot loop. Google logo appears, sits there for 5-10 seconds then reboots.

I so far have tried:

- Multiple reflashes of 6.0 factory image. Boot loop remains.
- Multiple flashes of 5.1.1 factory image. Boot loop remains.
- Tried flashing Cyanogenmod cm-12.1-20151021-NIGHTLY-shamu.zip via recovery. Flash successful. Boot loop remains.
- Flashing gpt.bin and reflash 6.0 images. Boot loop remains.

This is the first time I've encountered issues. I've successfully flashed factory images to my Nexus 4 many times over the
last couple of years.

Does anyone have any suggestions re a fix, if at all possible? Any tips/suggestions would be greatly appreciated!

If i need to return it, should I flash to 6.0 and lock? Will they be able to tell that the bootloader has
been unlocked previously?

Thanks!!

Boot loop after flashing CWM recovery

Hi guys!

I flashed DooMLoRD's CWM-Based Recovery 6.0.4.6 Touch Recovery so I could get CM 11 on my z1c. Once I flashed the boot image, I booted my phone normally and went into the recovery menu to make sure things were working, which they were. After confirming I got a prompt saying that I didn't have root access and was asked if I wanted to root my phone, once I accepted the prompt things broke.

My phone is now in a boot loop which doesn't make it past the Sony logo, going into the recovery will give me the recovery screen with only the CWM logo and a black background and no options, then turn off and reboot again after a couple of seconds. I tried re-flashing the boot image and since that didn't work I tried with the ftf file as well (14.2.A.1.114) and got an error.

21/036/2015 21:36:40 - INFO - Selected Bundle for Sony Xperia Z1 Compact (D5503). FW release : 14.2.A.1.114. Customization : Customized_FR
21/036/2015 21:36:40 - INFO - Preparing files for flashing
21/037/2015 21:37:21 - INFO - Device disconnected
21/037/2015 21:37:25 - INFO - Please connect your device into flashmode.
21/037/2015 21:37:47 - INFO - Device connected in flash mode
21/037/2015 21:37:47 - INFO - Opening device for R/W
21/037/2015 21:37:48 - INFO - Reading device information
21/037/2015 21:37:48 - INFO - Phone ready for flashmode operations.
21/037/2015 21:37:48 - INFO - Opening TA partition 2
21/037/2015 21:37:48 - INFO - Current device : Unknown: Dec 17 2013/18:59:18 - CB5A1ZE653 - Unknown: Dec 17 2013/18:59:18 - Unknown: Dec 17 2013/18:59:18 - Unknown: Dec 17 2013/18:59:18
21/037/2015 21:37:48 - INFO - Closing TA partition
21/037/2015 21:37:48 - INFO - Start Flashing
21/037/2015 21:37:48 - INFO - Processing loader.sin
21/037/2015 21:37:48 - INFO - Checking header
21/037/2015 21:37:48 - INFO - Flashing data
21/037/2015 21:37:48 - INFO - Loader : S1_Root_6732 - Version : MSM8974_23 / Boot version : S1_Boot_MSM8974_LA1.04_15 / Bootloader status : ROOTED
21/037/2015 21:37:48 - INFO - Max packet size set to 512K
21/037/2015 21:37:54 - INFO - Making a TA backup
21/037/2015 21:37:54 - INFO - Opening TA partition 1
21/037/2015 21:37:54 - INFO - Start Dumping TA partition 1
21/037/2015 21:37:54 - INFO - Finished Dumping TA partition 1
21/037/2015 21:37:54 - INFO - TA partition 1 saved to C:\Users\####\.flashTool\registeredDevices\CB5A1ZE 653\s1ta15-10-21_09-37-54.ta
21/037/2015 21:37:54 - INFO - Closing TA partition
21/037/2015 21:37:54 - INFO - Opening TA partition 2
21/037/2015 21:37:54 - INFO - Start Dumping TA partition 2
21/037/2015 21:37:55 - INFO - Finished Dumping TA partition 2
21/037/2015 21:37:55 - INFO - TA partition 2 saved to C:\Users\####\.flashTool\registeredDevices\CB5A1ZE 653\s1ta15-10-21_09-37-54.ta
21/037/2015 21:37:55 - INFO - Closing TA partition
21/037/2015 21:37:55 - INFO - Parsing boot delivery
21/037/2015 21:37:55 - INFO - Ending flash session
21/037/2015 21:37:55 - ERROR -
21/037/2015 21:37:55 - ERROR - Error flashing. Aborted
21/037/2015 21:37:55 - INFO - Device connected in flash mode
21/037/2015 21:37:56 - INFO - Device disconnected
21/037/2015 21:37:59 - INFO - Device connected in flash mode
21/038/2015 21:38:59 - INFO - Device disconnected
21/040/2015 21:40:41 - INFO - Device connected with USB debugging off
21/040/2015 21:40:41 - INFO - For 2011 devices line, be sure you are not in MTP mode

I was rooted before flashing CWM and had bl unlocked as well, USB debugging (of course) was also enabled and when I connect to flashtool now it says that its no longer active which I think is causing the above error but idk.

What I can still do is connect my phone in either flash or fastboot mode, but I have no recovery or access to android OS.

Any help would really be appreciated as I'm out of ideas on what to do, if you need more info I will try to provide as much as I can!

Thanks for any help in advance!

Weird boot loop issue after flashing CM 12.1 nightlies

I have a D801, nothing terribly unusual about my setup. But every time I flash a CM 12.1 nightly it gets stuck on the CM boot anim on the subsequent boot. I'm using @blastagator's TWRP 2.8.7.1 and I make sure to wipe cache & dalvik every time. A reboot doesn't help but reflashing SuperSU via TWRP seems to fix it. Anyone have any ideas?