Bought a replacement z3c as my former camera broke, WOW I do not remember this much pain in rooting the phone the first time.
I went through the dilligence of backing up the DRM keys - first time flashing down to 4.4.4 was somewhat painless, although in the .ftf i was using (I think it was an unbranded CE), i was getting CONSTANT process errors.
I've since flashed it back and forth (mistakenly flashed a forward .ftf build - 6.01 experiental) and now when I try to flash back to 4.4.4 (successful flash), upon boot, it attempts to put me through the language selection prompt, but I get a "google partner setup has stopped" that appears to freeze the device, and it reboots. constant boot loop - no ability to root as i don't have any system stability.
I'm trying to try different 4.4.4 versions in attempt to workaround this, but if anyone has insight it would be GREATLY appreciated.
*tear*
thanks in advance!
EDIT: RESOLVED - in flashtool, I checked the boxes to wipe data and user data when flashing new FTFs and that resolved the consistent crashing issues.
Related
I've had my N1 rooted pretty much since day one. Installing Froyo (at the time) wasn't as smooth as I have come to except of Google products, since the OTA updates wouldn't install and I needed to use repackaged versions. Recently my phone started nagging me to install 2.2.1. I got fed up and finally re-flashed the stock recovery image (I didn't restore anything else).
Ever since, I haven't been promoted to install the the update. Additionally, trying to update manually (using the original file) resulted in an android guy and an exclamation mark - but nothing further.
From my understanding, as long as you have the stock recovery, you should be able to flash original packages. Am I mistaking?
UPDATE: So the update was pushed to my phone again. After clicking install, the phone rebooted and the update started installing. At some point however, it froze with the android guy and an exclamation point development. I had to remove the battery to reboot.
Was re-flashing the recover image not enough?
I believe you have to be on stock recovery and stock rom.
I believe I'm on both. I cant get a checkin to indicate that there is an update. Is that normal?
I'm in the same boat but can't even reflash the original rom through vol- power.
In on this!
I searched and found nothing exactly like what I was experiencing and nothing I hadn't already tried. Hopefully someone has seen this before. I HAD a nice rooted stock SM-G900A 4.4.4 and now I have a flashy gold brick (soft). I rooted by downgrading the kernel to use towelroot then flashed stock kernel back. Everything worked fine for about a week or so. I'm not sure at what point I started having issues exactly so I'm not sure if an app or mild mod could have caused my issues. The only thing I had done was use SuperSU to block Knox and change the terrible TW stock sounds to standard ogg clicks and what not. The trouble started with the camera. I opened my camera and the screen would flash green then I would have red ghost images in a pattern on the screen. The pictures I took had the same effect when viewed in the gallery. If I switched modes the problem would go away with the camera until I closed then opened the camera app again so I assumed it was a software rather than hardware problem. I couldn't find any info on a fix so I did a factory reset. The problem persisted. I decided finally to flash back to stock. That's when it really got bad. After flashing to stock the phone will boot to the Samsung animation with the swoosh, freeze there for a few seconds without completing the boot animation then the screen shuts off and the phone becomes unresponsive. The only signs of life is the blue LED is constant lit. I have to do a battery pull to start over. I have flashed just the PDA and I have flashed the whole shootin match (except for BL) and I get the same results. I have tried stock tar files from a couple different sources. It will go into download mode as well as stock recovery where I tried a factory reset after flashing. PLEASE HELP!
So I flashed OA1 stock kernel and got it to boot. Of course now I get the Update interrupted message when I try for the OTA to anything newer than the 4.4.2 it's running. And after 8 hours of messing with this gem the camera issue persists.
Acer904 said:
So I flashed OA1 stock kernel and got it to boot. Of course now I get the Update interrupted message when I try for the OTA to anything newer than the 4.4.2 it's running. And after 8 hours of messing with this gem the camera issue persists.
Click to expand...
Click to collapse
Go here and flash back to NCE. Then take the OTAs.
http://forum.xda-developers.com/showthread.php?p=60012961
Sent from my SAMSUNG-SM-G900A
That is what I ended up doing just an hour before your reply and all is well again. I suppose my first attempt to go back to NCE didn't work because I didn't use the downgrade flash, just a regular 4.4.2 stock. There must be a difference between the two. The OTAs still wouldn't work so I ended up installing the updates from external sd. The lollipop OTA is downloading fine though. Thanks for confirming I FINALLY went the right route. This root screw up wasn't as bad as my last (efs S3 debacle) but it still took too many hours to fix.
Acer904 said:
That is what I ended up doing just an hour before your reply and all is well again. I suppose my first attempt to go back to NCE didn't work because I didn't use the downgrade flash, just a regular 4.4.2 stock. There must be a difference between the two. The OTAs still wouldn't work so I ended up installing the updates from external sd. The lollipop OTA is downloading fine though. Thanks for confirming I FINALLY went the right route. This root screw up wasn't as bad as my last (efs S3 debacle) but it still took too many hours to fix.
Click to expand...
Click to collapse
If you take the 5.0 ota you won't be able to root. Just FYI. There is no root for it yet. There is a pay however in the general section on how to upgrade to 5.0 and keep root.
So I was running a 4.4.x ROM and it was working great...then my company bought me a wifi-only tablet and that's pretty much useless for me without some tethering, and for whatever reason FoxFi didn't work with my ROM. I searched Google for days, tried mods and all sorts of Xposed stuff, but nothing worked. So I gave up and figured I'd try a new ROM. No reason not to switch to Lollipop, while I was at it - especially because the ROMs currently supported are all 5.0. So I flash a stock 5.0 firmware and tried a ROM - tethering didn't work. Tried another. Same deal. So fine - if i'm going to have no tethering capabilities, I'd rather have it with my old ROM and Nandroid backup.
Using Odin, I flashed the stock firmware that I've been flashing for a year now. It has worked every time in the past. But this time, Odin worked, and passed, and everything looked great - but when I booted up the phone, it starts to boot up, gives me the unlocked lock picture screen, then starts to load the Samsung image, stops mid-way through, and ... NOTHING. Screen goes blank and it hangs forever. I re-flashed with Odin a dozen times...nothing. Wiped data, wiped cache...nothing. I'm out of ideas and apparently Google hasn't seen this before, as far as I can find.
The image is where it stops loading the Samsung logo and then it just goes black.
Please. Help.
isellmidgets said:
So I was running a 4.4.x ROM and it was working great...then my company bought me a wifi-only tablet and that's pretty much useless for me without some tethering, and for whatever reason FoxFi didn't work with my ROM. I searched Google for days, tried mods and all sorts of Xposed stuff, but nothing worked. So I gave up and figured I'd try a new ROM. No reason not to switch to Lollipop, while I was at it - especially because the ROMs currently supported are all 5.0. So I flash a stock 5.0 firmware and tried a ROM - tethering didn't work. Tried another. Same deal. So fine - if i'm going to have no tethering capabilities, I'd rather have it with my old ROM and Nandroid backup.
Using Odin, I flashed the stock firmware that I've been flashing for a year now. It has worked every time in the past. But this time, Odin worked, and passed, and everything looked great - but when I booted up the phone, it starts to boot up, gives me the unlocked lock picture screen, then starts to load the Samsung image, stops mid-way through, and ... NOTHING. Screen goes blank and it hangs forever. I re-flashed with Odin a dozen times...nothing. Wiped data, wiped cache...nothing. I'm out of ideas and apparently Google hasn't seen this before, as far as I can find.
The image is where it stops loading the Samsung logo and then it just goes black.
Please. Help.
Click to expand...
Click to collapse
I'm not saying you file that you are using is messed up but I've been using the NCE downgrade file in this thread
http://forum.xda-developers.com/showthread.php?t=3076803. It's in the OP, step 5 in the notes section. Worth a shot.
Hello all. Generally I've been able to troubleshoot all my Android issues on my own. Most of the time someone has had the same problem (amirite?!). However, I'm stumped and could use a little help from the community.
I've been going along on Marshmallow with FK as my kernel. Generally, waiting a bit to take an update til SuperSU was confirmed all working correctly and that there wasn't any surprises. I had been putting off the MMB29V update for a bit just because everything was running fine and I had no real reason to upgrade. Well, one day I started getting a few FCs and things seemed a bit off performance wise so I decided that I'd go and move on to the next release.
Now, since I've had my N6 I really haven't had the need to run a custom ROM which is completely unlike my old habits on the S3. I decided that it's been a while since I've checked out AOSP so I flashed MMB29V using the batch file with no issues and then DU and their recommended GApps. Here's the first hint of an issue. When I loaded up the OS for the first time I got acore and phone FC's constantly. I instantly thought that I didn't wipe something or that I had a bad zip. I re-downloaded everything and checked MD5s. Everything looked good and after the flash I was able to get through the setup wizard without any issues. As I was sitting there checking out the tweaks and options available I started getting FCs again. It seemed related to Google apps. I did the whole process a second time and still had the same issues. Basically it seemed like at some random point in time the FCs would come and then shortly after the device would be highly unstable. I'd get random reboots, etc. Looking at the stack traces the errors seemed like odd NPEs and native errors.
I decided that AOSP wasn't going to cut it right now if I was going to have a relatively unstable phone and went to flash completely back to stock. Much to my surprise I still got the same errors! Apps like Feedly would never even be able to open. They would just FC on launch. The device hot reboots. The phone process seems to crash during most calls. I triple checked my MD5 on the download from Google. Made sure I wasn't doing something super stupid. I even tried doing the factory flash, booting to the welcome screen, then powering down, going to stock recovery, and factory resetting before continuing. All the same errors.
I've flashed back to complete stock a few times before without any issues. I've been able to flash system.img without any issues. Now it seems like the phone is completely unstable no matter what I do. I get the "Your device is corrupt. It can't be trusted and may not work properly." (red) message when doing a cold boot.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?
I've burned through two backup cards of Google 2-Step backup codes! I'd really like to figure this one out!
mikejr83 said:
.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?!
Click to expand...
Click to collapse
You could read the OP of the following thread and flash a debloated and prerooted ROM.
http://forum.xda-developers.com/showthread.php?t=3059493
I guess I'll try that. I'm still scratching my head why a flash from the factory image is still suffering from FC's and general instability. It also concerns me that I get the corrupted message at boot. It would be one thing if I flashed factory, then put a recovery, kernel, and rooted, but I haven't done that.
Hopefully I'll get a chance to try that this evening. Thanks for the link to that image. It's pretty much what I run when I take an update.
N, n, ne, necromancy!
I brought this thread back to life because I've never been able to solve the instability issues since my last post back in March.
Having some free time lately I decided to nuke my device and start again. I first grabbed the latest stock image and flashed stock. Then I downloaded the latest TWRP and Dirty Unicorns and decided that I'd give it a whirl again. I had FC issues right after the first go at it. I decided to try another GAPPs and do it again. I was able to get through setup. It took a few hours but the FCs started again.
I decided that I would try factory resetting the device and then starting a setup. I remembered that on my previous devices that I sometimes would have to do an immediate factory reset after flashing.
Well that did crap. FCs are random. The device is stuck booting now after a hot reboot.
How can I debug this? What do I need to grab from a logcat? Is there a way to run something like memtest to see if there is a bad section of RAM and something against storage to see if there is a bad sector?
This is frustrating as hell!
Hi all, I was running a CM ROM on my Droid Turbo and recently flashed back to stock using a backup I created with TWRP, because I was tired of not having GPS capabilities.
Now that I’m running stock (still rooted), I’ve been getting a notification to do an OTA update. When I allow the update to install, it restarts my phone and sends me straight to the TWRP recovery and does nothing else. Rebooting gets me stuck in a loop where it keeps sending me to recovery. Clearing out my cache got me out of the loop but after a day or so, the annoying install message comes back.
I noticed an error message when I looked at the log screen in TWRP. As best I can transcribe it, it says:
Package expects build fingerprint of motorola/quark_verizon/quark:5.1/SU4TL-44/44:user/release-keys or Motorola/quark…. ; this device has Motorola/omni_quark/quark:5.1.1/LYZ28E/1:eng/test-keys
Does anyone have any idea what’s going on with my phone – why I can’t take the OTA? Any advice on how to fix the problem or get this stupid upgrade notification to go away? The notification takes over the device every time you unlock the screen so it’s driving me crazy.
Thanks in advance for any help!
I think you need stock recovery and bootloader.
GPS issues have long been solved, using the "clear modem" file. You sent back to stock for nothing.
If you really want SUTL-49 there's plenty of downloads to manually flash it. You don't need the OTA.
Thanks for the replies. I think I'm going to stick with stock now. Have been enjoying the Motorola features like the hands-free driving thing and I wasn't seeing any advantage running CM anymore. Can I flash SUTL-49 using TWRP or do I have to hook to a PC and use ADB?
shinydiamond said:
Thanks for the replies. I think I'm going to stick with stock now. Have been enjoying the Motorola features like the hands-free driving thing and I wasn't seeing any advantage running CM anymore. Can I flash SUTL-49 using TWRP or do I have to hook to a PC and use ADB?
Click to expand...
Click to collapse
You can flash it with TWRP from here:
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
Thank you!