Database Info

Looping at boot screen, due to the last firmware update?

Hi folks, it seems that I may use some help right now. Searched around, but so far no luck is found. My rooted TF700 runs with the latest firmware and not unlocked (stock). Today she went nowhere but showing the ASUS logo and circling dots.
First, as usual, I tried to have a cold boot. Still, she didn't go further. Then I decided to wait patiently, and I think one hour is a reason to try helping her out of there. Next step, as some of you may already had in mind: RCK. Picked it up, the green robot showed up, but only few seconds before it went to sleep accompanied by that... yes, that red triangle.
Not so long afterwards, I downloaded the firmware ZIP file from ASUS's website. Extracted it once, renamed it the "usual" way, put the file at a MicroSD root and got the TF700 installing it. Installation was complete, the robot wasn't shown sleeping, and then it rebooted. At this moment I took the MicroSD from the slot so it doesn't interrupt the process.
But then what? Still the same old eight dots making the runabout form under ASUS logo. Tried cold boot once again, no luck. Then, I borrowed my children's A100 to type this help request.
I have no idea what to do. Still have the warranty valid but I want to try another thing before sending it out. It might be due to the new firmware (25 I think, I'm not memorizing firmware numbers) but it seems that I'm the only one suffering it so far. The last thing I remembered was the TF700 went sudden reboot when I click the bluetooth icon to activate it, while I'm trying to connect to a portable speaker.
I never flash any custom ROMs, it has been always the stock. Random reboots, yes, I think I'm not the only one. But now I'm getting suspicious since this happens one day after the last firmware update. The looping at boot screen.
In case anyone has suggestions or thoughts, please kindly share that here. Thanks in advance.
Sent from my A100 using XDA Premium HD app

Maybe your data partition is corrupted. Did you try "wipe data" in the bootloader menu?

_that said:
Maybe your data partition is corrupted. Did you try "wipe data" in the bootloader menu?
Click to expand...
Click to collapse
Hi, thanks. Doesn't install a fresh firmware do further? I mean, it also removes the data, right? Or am I wrong here?
Sent from my A100 using XDA Premium HD app

suroboyo said:
Hi, thanks. Doesn't install a fresh firmware do further? I mean, it also removes the data, right? Or am I wrong here?
Click to expand...
Click to collapse
"Wipe data" deletes your data, right. I never did it myself, so I can't say what exactly will be deleted. Installing a firmware only replaces the firmware, not your data.
Alternatively you can try if you can connect via adb shell while the boot screen dots are spinning.

_that said:
"Wipe data" deletes your data, right. I never did it myself, so I can't say what exactly will be deleted. Installing a firmware only replaces the firmware, not your data.
Alternatively you can try if you can connect via adb shell while the boot screen dots are spinning.
Click to expand...
Click to collapse
Wipe data is factory reset. If you reset your device from setting-> factory reset, it will boot into "wipe data" mode and wipe all your apps, bring everything back to factory default. At this point if you don't have a backup, I see you only have one option which is wipe data.

OK guys, thanks a lot. If you read my footer now, you know I already have access to my TF700.
I did it as you suggested, chose "Wipe Data" after several times failing with firmware recovery. Losing data in SD is not a very big deal since I always keep my "real data" in an external MicroSD, anticipating such things exactly like I just "suffered". I also backed up my most of apps and their data to the MicroSD using Titanium Backup, so it's very close to the previous state... only snappier.
So I wiped the data and got into the stock of everything, without root. Then I rolled back to ICS firmware (30), rooted it using Debugfs, installed OTA Rootkeeper, protected a copy of the root access, updated the firmware, restored root, installed TB, restore all apps and data. Then it's the matter of replacing some widgets and little "here-and-there" settings. No more than two hours overall, could be way less if the number of apps are smaller.
What was really missing is just a few downloads and some "not really important" winter photos. Movies and maps kept in the internal storage, well, I have the backup. I wouldn't say this was caused by the new firmware, but somehow I feel like I should have a suspicion at it.
Thanks again!
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

baseband unknown :((

So i must have messed up my phone while using the all in one root unlocker and so on. Im not sure what i did, but i finally got my phone to boot, and now i get no service. Im on tmobile and it says i have no sim card. When i go into about phone it shows baseband unknown.
I really have no idea what to do. Ive never been stuck in this situation. Maybe someone more experienced can point me in the right direction?
any help would be appreciated!

aamzalag said:
So i must have messed up my phone while using the all in one root unlocker and so on. Im not sure what i did, but i finally got my phone to boot, and now i get no service. Im on tmobile and it says i have no sim card. When i go into about phone it shows baseband unknown.
I really have no idea what to do. Ive never been stuck in this situation. Maybe someone more experienced can point me in the right direction?
any help would be appreciated!
Click to expand...
Click to collapse
so furthermore, it looks like i have no data partition anymore, i can go on my chromebrowser on the phone and browse the web but when i try to install anything it says no sdcard. I also cant move anything to the phone via windows, it just freezes even tho i can see the phone and go into the internal storage.
Im really screwed here. Ive also used the fastboot files to flash back to google stock, but for some reason continue to find everything borked.
HELP PLZ!!! ahah

Also, finding that i cant mount any partition, cache, data, anything liek that. It seems like my partitions have been messed up . Not sure how to resolve that

Well it looks like your the first one to brick the nexus 5. If your imei is missing your screwed.
P.S.A DON'T USE TOOLKITS
Sent from my NEXUS 5

Might be helpful to others to explain exactly what you did to your phone.

lafester said:
Might be helpful to others to explain exactly what you did to your phone.
Click to expand...
Click to collapse
He used a tool kit. Who knows what it did to his phone
Sent from my NEXUS 5

I realize that maybe using the toolkit may not have been a good choice but considering im already here. Constructive advice might be a little more helpful... I know that with my old verizon GS3 if i lost my imei/ similar info, i could nv flash myself and get it back in certain cases. Does a similar thing not exist for the nexus 5? Id imagine that a truly unlocked device like this one should have a method to get back from anything?

aamzalag said:
I realize that maybe using the toolkit may not have been a good choice but considering im already here. Constructive advice might be a little more helpful... I know that with my old verizon GS3 if i lost my imei/ similar info, i could nv flash myself and get it back in certain cases. Does a similar thing not exist for the nexus 5? Id imagine that a truly unlocked device like this one should have a method to get back from anything?
Click to expand...
Click to collapse
If you've flashed the stick images and it hasn't fixed it then you might be out of luck. With the n4 there is a thread on how to restore the phone with LG nv flash in download mode. I don't think the tools or files are available yet for the n5 tho
Sent from my NEXUS 5

i dont know what i did, but i restored the factory image one more time, then booted to stock recovery and wiped all partitions. The phone booted and my imei and baseband are back. Working 100% now. Gonna sit out the rooting and so on for now. time to relax for a bit

So you can't fastboot flash anything? Can you fast boot flash twrp recovery from the android SDK on a PC?
Sent from my Nexus 7

aamzalag said:
i dont know what i did, but i restored the factory image one more time, then booted to stock recovery and wiped all partitions. The phone booted and my imei and baseband are back. Working 100% now. Gonna sit out the rooting and so on for now. time to relax for a bit
Click to expand...
Click to collapse
That's how I fixed my N4. I flashed the factory images 3 times.

Glad it's working finally
Sent from my Nexus 7

Ya, fastboot continued to work, and iw as able to flash the factory images.At first those werent fixing anything. the final time i flashed it right before it worked again, i let the phone sit and run the boot screen for about 30 minutes before i went to stock recovery and wiped. Then it booted perfectly.
The previous times i had flashed twrp and wiped which i believe was the cause in the first place.
Thanks all its working perfect now. The device is amazing,!

aamzalag said:
The previous times i had flashed twrp and wiped which i believe was the cause in the first place.,!
Click to expand...
Click to collapse
Sames just happened to me, but I didnt use a toolkit, i did it all manually.
Quick flash of the factory image sorted it. :victory:
UPDATE: Flashed TWRP again....All ok this time.

You guys unlocked the bootloader first right?
Sent from my SGH-I747

This has just happened to me. I have installed the stock images 2 times now.
Is there anything you guys did differently to make it work?

My N5 decided to wipe the baseband and IMEI when I went to wipe the cache through recovery. Tried to reflash factory images 5 times and each time, when the phone boots up, hangouts, camera and gallery apps force close and I still have no network signal or IMEI/baseband.
Worst bit is all I did was wipe the cache partition, done that a million times and never had this problem
Anyone know what i can do?
I've relocked the bootloader for now but I can't call Google because my only phone is the Nexus 5 so that's out of the question.
Edit:
Managed to fix it by using a slightly different set of fastboot commands.
Here's what I did:
adb reboot bootloader
fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.17.img
fastboot reboot-bootloader
fastboot -w update image-hammerhead-krt16m.zip
fastboot reboot-bootloader
That worked for me

WRAITH07 said:
My N5 decided to wipe the baseband and IMEI when I went to wipe the cache through recovery. Tried to reflash factory images 5 times and each time, when the phone boots up, hangouts, camera and gallery apps force close and I still have no network signal or IMEI/baseband.
Worst bit is all I did was wipe the cache partition, done that a million times and never had this problem
Anyone know what i can do?
I've relocked the bootloader for now but I can't call Google because my only phone is the Nexus 5 so that's out of the question.
Click to expand...
Click to collapse
After you flash the factory image, boot into recovery and do a factory reset.

You mentioned a cache wipe. Was this in CWM or TWRP? My N5 hung trying to do a cache wipe in CWM. After rebooting the sdcard was inaccessible. The solution was to flash TWRP from fastboot, and do an advanced wipe of only the cache, and give it TIME. Like 5-10 minutes. After another reboot I had the sdcard and radio back, but some write permission issues. One more reboot and everything was ok again.
Sent from my Nexus 5 using Tapatalk

cmstlist said:
You mentioned a cache wipe. Was this in CWM or TWRP? My N5 hung trying to do a cache wipe in CWM. After rebooting the sdcard was inaccessible. The solution was to flash TWRP from fastboot, and do an advanced wipe of only the cache, and give it TIME. Like 5-10 minutes. After another reboot I had the sdcard and radio back, but some write permission issues. One more reboot and everything was ok again.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I had this issue while wiping cache in TWRP 2.6.3.0
Sent from my Nexus 5 using Tapatalk

[Q] Flashing no longer possible: Flash successful but system does not change

Hello!
I can no longer flash anything to my GT-P5110, even factory reset has no effect. The internal storage seems to be read-only.
I think this is a longer story: About one year ago the stock firmware became incredibly slow, to the point that processes started to force close, then my user data was lost, and after factory reset the tablet went into endless boot loop.
So I decided to give CM10 a try and it worked flawlessly. The tablet was fast again. I even could upgrade to CM11 later. But around 2 month ago, only sometimes processes started to force-close or the tablet randomly rebooted itself - mostly during charging. I left it that way in the charger for some days because I had no time to bother with that issue. Then, I tried to factory reset my device only to find out that this has absolutely no effect. Installing app updates: No effect. Changing system settings: No effect. And apps start to force-close at an insane rate short after boot. The device is unusable. My could only shut down and reboot into recovery. I left the tablet lying around, turned off, out of charger, for 2 months. Now I tried to investigate:
When I "adb shell" into recovery and call dmesg, I see lots of these lines:
Code:
mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
I think something is really broken with the internal storage. I tried to flash a newer recovery but it has no effect, even when done from download mode.
Factory reset sometimes fails with an error. Reinstalling CM fails with an error. Wiping cache seemingly succeeds but I'm sure it has no effect. I tried installing SlimRom instead which seemingly succeeds, too - but after reboot I'm greeted with the CM boot logo again.
I tried to flash stock firmware with Odin. It is very very slow, runs for about 15 minutes, then fails at around 50%. Of course: That "half flashed firmware" does in no way affect the device: It still boots CM11 "without problems", then a few seconds after finishing boot (showing home screen), force-closes start to pop-up.
What should I do? I suppose the device is out of warranty for a few weeks or months, now. And even when not: It has been flashed with CM, the triangle counter is not zero. I suppose that combination of problems (read-only/failing storage, non-stock firmware) voids warranty in a way that Samsung will deny any repair. If at least I could return the device to stock firmware things would be different maybe.
Any ideas what I could try? Is it possible that the internal storage is simply fried? fsck'ing the partitions shows no errors, just the data partition is unclean with unwritten journal data but all data is readable. So the internal storage has probably not died. It just sticks to read-only mode for whatever reason.
I've found some posts with similar problems but those seem to be about older Galaxy Tab 1 devices built 2011 or before.

Just reading over this and it sounds very similar to what I'm currently facing, which is doubly annoying as no one else has chipped in a solution
I had reboot issues with my Tab2 10.1 (GT-P5110) on stock so after realizing I'd need to factory reset bite the bullet and rooted so I could use CM10.
Had occasional reboots but nothing I couldn't live with however from yesterday evening the tablet is seemingly stuck in a boot loop. It comes on, some apps fire up and an update starts. Sometimes apps force close then BOOM I get the boot splash screen.
I've tried factory reset in recovery (CWM 6.0.2.7) to no avail and wiping just about everything which also had no noticeable effect as all my settings and the rom are still the same when I get back in (albeit briefly!).
I've tried flashing new recovery via ODIN which reported a success however that also didn't appear to take. I'm beginning to think it some serious file system or storage corruption ;(

Same problem here...
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.

bigg fella said:
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.
Click to expand...
Click to collapse
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).

hurikhan77 said:
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).
Click to expand...
Click to collapse
exactly, can't even uninstall an app. It's as if it boots from a permanent back up because even deleting pictures or files isn't permanently successful. You can uninstall and delete to your hearts content, get false hope, and get crushed after it reboots and everything is unchanged

Not looking very optimistic for this I was getting a similar inkling that it's gone into a permanent RO mode as not even the wipes from recovery have an effect. I'd also tried un-installing apps as I noticed one updating and thought it was crashing it however even when it did fire up and I disabled WLAN to stop Play Store auto-updating and removed the app on the next reboot cycle the app was back:crying::crying:
I fear I may have a big white paperweight....

Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app

shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Would this method be any different to the way it attempts to reformat the internal partitions when you select to format the various mounts from CWM? If so I'm more then willing to give it a go as I really have nothing to lose as the damn thing is useless atm!

shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Good call......Smart move?

help!!
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?

PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app

im also having this issue with my galaxy tab2 7".. help is badly needed

Well, the proposed fix I had didn't help. Was worth a shot...
Sent from my Nexus 4 using XDA Premium HD app

hope someone finds a solution for this.

No Access to ADB
shakatu said:
PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Hi Shakatu,thanks for the PM, however, my device in ADB is unauthorised, so wont let me get into shell. Is there a way around this please?

sunnytimes said:
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?
Click to expand...
Click to collapse
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread

same problem please help me... :crying:

seagman said:
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread
Click to expand...
Click to collapse
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..

sunnytimes said:
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..
Click to expand...
Click to collapse
same here too, i have same issue.. unable to flash or do anything to my phone....

Probably this is the end for our tab. As off now the tab is useless.
Sent from my GT-N7000 using XDA Free mobile app

[HUGE BUG] Partitions disappeared!

Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!

Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock

I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.

CafeKampuchia said:
I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.
Click to expand...
Click to collapse
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
dreamerguy00 said:
Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock
Click to expand...
Click to collapse
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!

blackbird5308 said:
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!
Click to expand...
Click to collapse
Sorry wrong thread
Sent from E.P.D.Center

I had the same weird problem last night.....
Except my recovery was also reverted to stock.
it happened after i got notifed about an update available couple days in a row which i canceled.
I even have Droidwall and everything but a few apps are blocked from data usage.
What i would suggest is to freeze the ""system update" system app.
I kinda have a feeling the OTA updates have something to do with it.
This happend to me 1 other time a while back with an HTC One X device. Same pattern, System update notifications then couple days of ignoring .... then pooffff...
blackbird5308 said:
Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!
Click to expand...
Click to collapse

Cyanogenmod 12.1 Upgrade from Slimkat 4.4.4 - Bootloop after optimization

So I've been trying to go from Slimkat (Slim-4.4.4.build.7.0-Official-5979) to Cyanogenmod 12.1 (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw) for a few weeks now. I've tried like 4 different guides, which were all pretty similar, but every time I get to the same point. I'm able to get to my recovery (CWM), clear all my cache, etc, install CM12.1 and Gapp5.11, reboot, it optimizes all my apps, finishes the boot, and then goes into what seems like a boot loop. I've let it sit there and reboot for like 5-10 minutes before and it just keeps rebooting. I even redid the flashing of the aboot and bootloader as shown in the official CM install guide to get the recovery on there and also tried the latest TWRP recovery with the same results. Also, once it enters this bootloop, from the time I turn it on, it shows the Samsung logo with the blue Android man below it, then goes to the screen with the pulsing Android head, it vibrates then goes do a dark screen with a blue pulsing indicator light and then starts the sequence over after a few seconds.
I tried to remove my MicroSD card and boot without that with no success. Is it possible I need to format my internal storage as well? The guides usually don't mention what you're coming from, so I have no idea what starting point they expect me to be at.
Files used:
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw
gapps-511-base-20151205-1-signed
I did NOT use the below CM Recovery, however. I was afraid to do that and lose my ability to recover my old image.
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw-recovery
I'm able to recover back to my original ROM, but any help to upgrade is greatly appreciated. I'm tired of messing with this....

hypercoyote said:
So I've been trying to go from Slimkat (Slim-4.4.4.build.7.0-Official-5979) to Cyanogenmod 12.1 (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw) for a few weeks now. I've tried like 4 different guides, which were all pretty similar, but every time I get to the same point. I'm able to get to my recovery (CWM), clear all my cache, etc, install CM12.1 and Gapp5.11, reboot, it optimizes all my apps, finishes the boot, and then goes into what seems like a boot loop. I've let it sit there and reboot for like 5-10 minutes before and it just keeps rebooting. I even redid the flashing of the aboot and bootloader as shown in the official CM install guide to get the recovery on there and also tried the latest TWRP recovery with the same results. Also, once it enters this bootloop, from the time I turn it on, it shows the Samsung logo with the blue Android man below it, then goes to the screen with the pulsing Android head, it vibrates then goes do a dark screen with a blue pulsing indicator light and then starts the sequence over after a few seconds.
I tried to remove my MicroSD card and boot without that with no success. Is it possible I need to format my internal storage as well? The guides usually don't mention what you're coming from, so I have no idea what starting point they expect me to be at.
Files used:
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw
gapps-511-base-20151205-1-signed
I did NOT use the below CM Recovery, however. I was afraid to do that and lose my ability to recover my old image.
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw-recovery
I'm able to recover back to my original ROM, but any help to upgrade is greatly appreciated. I'm tired of messing with this....
Click to expand...
Click to collapse
I'd suggest maybe switching your recovery. I'm also running the same version of slimkat on my old S3.
Nexus 6 via SSHD/Cataclysm

ShapesBlue said:
I'd suggest maybe switching your recovery. I'm also running the same version of slimkat on my old S3.
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
yea, I tried using Clockwork Mod recovery as well. CM12.1 includes a recovery as well, but I'm hesitant to use it....
Also, how did you patch the Stagefright exploit on that?

hypercoyote said:
yea, I tried using Clockwork Mod recovery as well. CM12.1 includes a recovery as well, but I'm hesitant to use it....
Also, how did you patch the Stagefright exploit on that?
Click to expand...
Click to collapse
I mean change the recovery to something else like twrp. Honestly I didn't. I personally think the stagefright exploit wasn't anything to worry about
Nexus 6 via SSHD/Cataclysm

ShapesBlue said:
I mean change the recovery to something else like twrp. Honestly I didn't. I personally think the stagefright exploit wasn't anything to worry about
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
Yea, you might've missed that part or I worded it weird, but I tried both TWRP and ClockworkMod and they both produced the same result.

hypercoyote said:
Yea, you might've missed that part or I worded it weird, but I tried both TWRP and ClockworkMod and they both produced the same result.
Click to expand...
Click to collapse
That's weird. I've been using twrp on nearly all my devices and the only issue I've ever had is to update it
Nexus 6 via SSHD/Cataclysm

ShapesBlue said:
That's weird. I've been using twrp on nearly all my devices and the only issue I've ever had is to update it
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
Well, I don't think it's a recovery issue. My guess is it's got something to do with the Bootloader, some files on my phone. I really don't know. Doing the whole custom ROM thing isn't really that hard or complicated once you know what you're doing, but I've run out of things to check on. I don't recall doing anything odd before when I upgraded to Slimkat, but even if I did, it should've been undone in the install process of CM12.1.

hypercoyote said:
Well, I don't think it's a recovery issue. My guess is it's got something to do with the Bootloader, some files on my phone. I really don't know. Doing the whole custom ROM thing isn't really that hard or complicated once you know what you're doing, but I've run out of things to check on. I don't recall doing anything odd before when I upgraded to Slimkat, but even if I did, it should've been undone in the install process of CM12.1.
Click to expand...
Click to collapse
Very possible. I wish I knew what to do or how to help with this issue
Nexus 6 via SSHD/Cataclysm

ShapesBlue said:
Very possible. I wish I knew what to do or how to help with this issue
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
Me too! lol

Hehehe