Related
I have confirmed that I have root access and that my bootloader is unlocked
I have tried flashing CWM recovery via rom manager and various img files found throughout this site and others.
Despite this, when I boot into cwm I get the android guy with the yellow ball
If I hit vol up and down I get only a few options:
Bgackup and restore, reboot, apply update, whipe data factory reset, whipe cache partition.
No advanced (this is one I've seen mentioned but didn't see on my device)
But as long as I got that far, I went through the steps to install CM9.
I whiped data then cache
Applied the CM9 zip
then rebooted
When my phone came back on I still have moto gingerbread and it just wants me to relogin to blur and sign in to google.
Also tried Another SD card with the same results. CWM couldn't see any zips on the cards after reentering cwm after a reboot. Reformatting the cards and trying again produced the same results.
What am I missing here? I've followed and refollowed letter by letter with all the guides I've been seen.
Thanks for any help and I apologize for any newb stuff as this is my first attempt at android roms.
Well it looks like this is magically solved now.
After TWRP failed earlier I decided to go back into fastboot and did a erase recovery, reboot, then reflash twrp
Then tried booting into it and it worked!
So I went back into fastboot and flashed cwm instead since I'd prefer the non touch recovery.
Thanks for all the tips
Please remember to post questions in the Q&A forum.
I honestly don't know what's wrong. It looks like your doing everything properly.
seem like you're not with CWM installed on your device..
try to put another one like TWRP and see what happens
You are certain your bootloader is unlocked? (you see "unlocked" on the Moto splash screen)
First, try to fix permissions from Rom Manager.
If that doesn't work fastboot flash the most recent recovery. Go here and get the latest version.
I would advise against using ROM manager. It's been known to cause many issues.
ravilov said:
I would advise against using ROM manager. It's been known to cause many issues.
Click to expand...
Click to collapse
Oh ravilov, you and your crazy stories. I've been using Rom Manager since the day I rooted my phone. Never had one problem (well, except for the way koush does the premium license).
Make sure you're choosing "install zip from SD card" not "install update from SD card".
LÄvLab / HostileSlothRecords
ravilov said:
I would advise against using ROM manager. It's been known to cause many issues.
Click to expand...
Click to collapse
ROM Manager is perfectly fine for fixing permissions.
upndwn4par said:
Oh ravilov, you and your crazy stories. I've been using Rom Manager since the day I rooted my phone. Never had one problem (well, except for the way koush does the premium license).
Click to expand...
Click to collapse
It was reportedly the culprit of randomly appearing ".nomedia" files on some ROMs. After that I don't think I'd want to trust it.
Some people also had problems installing stuff through it, no matter what they tried. Once they switched to cmd/fastboot/manual install, everything worked fine.
So I'm not exactly pulling stuff out of my butt here.
I also don't really like it personally, I always remove it if it comes bundled with a ROM. But that's just me. To each their own. If it's working fine for you, by all means keep using it.
ravilov said:
It was reportedly the culprit of randomly appearing ".nomedia" files on some ROMs. After that I don't think I'd want to trust it.
Some people also had problems installing stuff through it, no matter what they tried. Once they switched to cmd/fastboot/manual install, everything worked fine.
So I'm not exactly pulling stuff out of my butt here.
I also don't really like it personally, I always remove it if it comes bundled with a ROM. But that's just me. To each their own. If it's working fine for you, by all means keep using it.
Click to expand...
Click to collapse
If I remember correctly, that was for epinter's and joker's CM10 ROMs. And it was never even close to proven that CWM was the culprit. Doesn't make sense that CWM is to blame for suddenly doing random stuff. Especially since both of those ROMs have had serious media issues since day one.
Anyway, I'm not saying that CWM is perfect - it's not. But RomRacers recovery is unsupported, and I try to never use unsupported software. TWRP is nice, but I don't like touch recoveries and old CWM backups are useless. Anyway, to each his own.
upndwn4par said:
If I remember correctly, that was for epinter's and joker's CM10 ROMs. And it was never even close to proven that CWM was the culprit. Doesn't make sense that CWM is to blame for suddenly doing random stuff. Especially since both of those ROMs have had serious media issues since day one.
Anyway, I'm not saying that CWM is perfect - it's not. But RomRacers recovery is unsupported, and I try to never use unsupported software. TWRP is nice, but I don't like touch recoveries and old CWM backups are useless. Anyway, to each his own.
Click to expand...
Click to collapse
Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.
But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.
Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:
ravilov said:
Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.
But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.
Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:
Click to expand...
Click to collapse
Yeah, you know what I meant. :cyclops:
I still think it is more likely that the ROM made RM go wacky than the other way around. Especially with the history of JB ROM media issues.
ravilov said:
Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.
But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.
Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:
Click to expand...
Click to collapse
I remember this happening when rom manager updated. Then a few days later they put another update distinctly saying "fixed problem of rom manager adding .nomedia to internal and external sd" so yes rav is right that rom manager was the culprit THEN. However that being said, I had tried a jb rom (can't remember which) that added those .nomedia files to my internal and external so you both could be correct in your assumptions.
EDIT: in the changelog for ROM manger here https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager it shows that it did place those .nomedia files.
Yes, I am certain that my phone is unlocked or at least I think I am since it says "unlocked" in the corner when I turn it on
I didn't want to sign back into everything quite yet so I haven't been able to try the rom manager fix permissions thing yet.
I flashed the TWRP recovery instead of the CWM one and got the same result when booting into the recovery so I assume that neither CWM or TWRP was successfully installed.
Shouldn't flashing these with fastboot get them in there? (technically tried installing from rom manager once too)
drsatan316 said:
Yes, I am certain that my phone is unlocked or at least I think I am since it says "unlocked" in the corner when I turn it on
I didn't want to sign back into everything quite yet so I haven't been able to try the rom manager fix permissions thing yet.
I flashed the TWRP recovery instead of the CWM one and got the same result when booting into the recovery so I assume that neither CWM or TWRP was successfully installed.
Shouldn't flashing these with fastboot get them in there? (technically tried installing from rom manager once too)
Click to expand...
Click to collapse
Yes, fastboot should be installing recovery properly.
I see three possibilities:
1) Something happened during the unlock process, so despite seeing "unlocked" you are not fully unlocked.
2) Fastboot is not writing recovery recursively
3) You have a hardware problem
I would try the following first:
1) Check to make sure you have the correct drivers installed on your PC and you have the most recent version of fastboot
2) Erase recovery with fastboot
3) Re-flash recovery with fastboot
Next I would try unlocking your bootloader again
Did you ever solve your problem?
Yes I got it working now.
TWRP booted after I did a fastboot erase and reflashed the recovery.
So I then reflashed CWM and that booted.
When I actually went to install a ROM a few days later it didn't boot again so I reflashed and ran the recovery on the next reboot OK again.
I was able to successfully get Joker's CM10 flahsed and running.
Not sure why I'd have to reflash every time I want to run the recovery but I think that that isn't a big deal for me anymore as this was just a test and this is no longer my primary device.
Thank you all for the help
You've probably heard this song and dance before, but my phone only charges if I hold the connector a little to the left of the port of the phone. This is a phone issue, I've tried like 5 cables. I am rooted so I'm worried att will just turn me away if I go to a repair place. I am s-on. I'm hoping maybe this is something I can fix myself. Any ideas?
Secondly, today I noticed that my mobile data only works for browsing google. Only google's web results show up. If I click on a link from there, it won't work. Any other app does not work. I've tried a soft reset and rebooting several times, and no I don't have any proxies enabled. If anyone has the stock lollipop build.prop, I'd really appreciate that. Very strange issue that I've never heard of. Running elementalx kernel and stock rom.
siren_shadows said:
my phone only charges if I hold the connector a little to the left of the port of the phone. This is a phone issue, I've tried like 5 cables. I am rooted so I'm worried att will just turn me away if I go to a repair place. I am s-on. I'm hoping maybe this is something I can fix myself. Any ideas?
Click to expand...
Click to collapse
If you purchased the phone from AT&T, they will not deny warranty due to root, unlocked bootloader, etc. Folks here have had good success with warranty claims on modified phones with AT&T. If you look at AT&T's warranty terms, you will see that they changed a year or 2 ago. Modifying the software is no longer mentioned under the items that void the warranty. Only physical damage and water damage are now listed.
siren_shadows said:
Secondly, today I noticed that my mobile data only works for browsing google. Only google's web results show up. If I click on a link from there, it won't work. Any other app does not work. I've tried a soft reset and rebooting several times, and no I don't have any proxies enabled. If anyone has the stock lollipop build.prop, I'd really appreciate that. Very strange issue that I've never heard of. Running elementalx kernel and stock rom.
Click to expand...
Click to collapse
What happens if you just type in a URL, without going through Google search results?
redpoint73 said:
If you purchased the phone from AT&T, they will not deny warranty due to root, unlocked bootloader, etc. Folks here have had good success with warranty claims on modified phones with AT&T. If you look at AT&T's warranty terms, you will see that they changed a year or 2 ago. Modifying the software is no longer mentioned under the items that void the warranty. Only physical damage and water damage are now listed.
What happens if you just type in a URL, without going through Google search results?
Click to expand...
Click to collapse
ah, thanks. if I type in a URL, I get the same dns lookup error. seems YouTube, Instagram, and Google are the only things that work. play store does not work.
siren_shadows said:
ah, thanks. if I type in a URL, I get the same dns lookup error. seems YouTube, Instagram, and Google are the only things that work. play store does not work.
Click to expand...
Click to collapse
Did you make any recent changes that may have caused this, such as flashing the custom kernel?
redpoint73 said:
Did you make any recent changes that may have caused this, such as flashing the custom kernel?
Click to expand...
Click to collapse
yeah, I reinstalled elementalx. I'd love a stock build.prop and an insecure stock kernel if that's possible.
siren_shadows said:
yeah, I reinstalled elementalx. I'd love a stock build.prop and an insecure stock kernel if that's possible.
Click to expand...
Click to collapse
Did you modify build.prop?
redpoint73 said:
Did you modify build.prop?
Click to expand...
Click to collapse
yeah, but I deleted the values. I'm worried I may have deleted something I wasn't meaning to, though.
siren_shadows said:
yeah, but I deleted the values. I'm worried I may have deleted something I wasn't meaning to, though.
Click to expand...
Click to collapse
WNC just posted the 4.28.502 version of his ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
I assume the build.prop is stock; and kernel is insecure.
unfortunately, I am s-on.
siren_shadows said:
unfortunately, I am s-on.
Click to expand...
Click to collapse
s-off is only needed to flash firmware (and it sounds like you already have Lollipop firmware).
You can pull boot.img from the ROM.zip without even actually flashing the whole ROM.
build.prop, not sure if there is a similar way to do that (extract without flashing he whole ROM). Otherwise, flash the ROM, and extract/copy the build.prop for use on the fully stock ROM.
Or just flash the ROM and use it, WNC's work is always good. Its basically the stock ROM, just cleaned up.
redpoint73 said:
s-off is only needed to flash firmware (and it sounds like you already have Lollipop firmware).
You can pull boot.img from the ROM.zip without even actually flashing the whole ROM.
build.prop, not sure if there is a similar way to do that (extract without flashing he whole ROM). Otherwise, flash the ROM, and extract/copy the build.prop for use on the fully stock ROM.
Or just flash the ROM and use it, WNC's work is always good. Its basically the stock ROM, just cleaned up.
Click to expand...
Click to collapse
I'm not averse to using the ROM, I just don't want to lose my data or have any long boots/incompatibility issues. I used the latest OTA from the official att update.
siren_shadows said:
I'm not averse to using the ROM, I just don't want to lose my data or have any long boots/incompatibility issues. I used the latest OTA from the official att update.
Click to expand...
Click to collapse
You shouldn't have any long boot or imcompatibility issues. The ROM I linked is based on the same ROM you are on (AT&T Lollipop update) just with bloat removed and some performance enhancements. What you can do, if you want to keep the current stock ROM:
1) Download the ROM I linked
2) Unzip on your computer
3) Find boot.img, copy it to your fastboot folder. This should be the stock, insecure kernel
4) Connect phone to computer in fastboot mode
5) Flash boot.img with command: fastboot flash boot boot.img
Reboot the phone, and see if the data is working again. If not, you can try to restore the build.prop. I don't personally know of a way to pull this from the ROM similar to above for the kernel. So this may be a little convoluted, but just a thought:
6) Make a nandroid of the current setup
7) Flash the ROM by WNC
8) Use a file explorer to copy build.prop file to internal storage or the removable SD
9) Restore your nandroid (back to stock AT&T) that you just made in Step 6 above
10) Copy the build.prop from WNC's ROM to overwrite the one that you modified
11) If it doesn't work, you are no worse off since you have a nandroid snapshot of your current setup (won't lose any user data)
redpoint73 said:
You shouldn't have any long boot or imcompatibility issues. The ROM I linked is based on the same ROM you are on (AT&T Lollipop update) just with bloat removed and some performance enhancements. What you can do, if you want to keep the current stock ROM:
1) Download the ROM I linked
2) Unzip on your computer
3) Find boot.img, copy it to your fastboot folder. This should be the stock, insecure kernel
4) Connect phone to computer in fastboot mode
5) Flash boot.img with command: fastboot flash boot boot.img
Reboot the phone, and see if the data is working again. If not, you can try to restore the build.prop. I don't personally know of a way to pull this from the ROM similar to above for the kernel. So this may be a little convoluted, but just a thought:
6) Make a nandroid of the current setup
7) Flash the ROM by WNC
8) Use a file explorer to copy build.prop file to internal storage or the removable SD
9) Restore your nandroid (back to stock AT&T) that you just made in Step 6 above
10) Copy the build.prop from WNC's ROM to overwrite the one that you modified
11) If it doesn't work, you are no worse off since you have a nandroid snapshot of your current setup (won't lose any user data)
Click to expand...
Click to collapse
I've got some very bad news. I tried replacing the build prop with the one in the zip that you linked, and now my phone won't boot up. at all. can't even get into recovery.
siren_shadows said:
I've got some very bad news. I tried replacing the build prop with the one in the zip that you linked, and now my phone won't boot up. at all. can't even get into recovery.
Click to expand...
Click to collapse
Can you still get into bootloader?
sigh. was able to get into recovery. gonna restore. don't think i had a modified build.prop at that time either... hopefully my cable won't mess up before i copy the backup back onto my phone
redpoint73 said:
Do you mean you can't get into bootloader?
If so, that doesn't actually make any sense, bootloader is write protected with s-on. So there is no way this can be corrupted or over-written.
This seems scary. But just take a breath, as I don't think this is as bad as it looks.
What happened after you copied the file?
Does the screen come on at all?
Click to expand...
Click to collapse
i got a black screen after a reboot. but holding power and volume up did the hard reset and i had to really quickly press volume down. like a split second window
siren_shadows said:
sigh. was able to get into recovery. gonna restore. don't think i had a modified build.prop at that time either... hopefully my cable won't mess up before i copy the backup back onto my phone
Click to expand...
Click to collapse
You didn't need to move the backup off the phone.
Its not a bad idea to make a copy of the backup (in the event the one on internal storage gets wiped) to your computer.
But its also good to keep a backup either on internal storage or on the removable SD.
redpoint73 said:
You didn't need to move the backup off the phone.
Its not a bad idea to make a copy of the backup (in the event the one on internal storage gets wiped) to your computer.
But its also good to keep a backup either on internal storage or on the removable SD.
Click to expand...
Click to collapse
I was a genius and decided I would save space by moving onto my computer. However, I am restoring now. That'll fix my black screen issue, right?
siren_shadows said:
I am restoring now. That'll fix my black screen issue, right?
Click to expand...
Click to collapse
Yes, build.prop is part of the ROM, so the TWRP backup will put you back to where you were before trying to replace the build.prop file.
Odd, I wouldn't think that replacing the build.prop with the one for a nearly stock ROM (and same LP base) would render the phone unbootable into OS.
redpoint73 said:
Yes, build.prop is part of the ROM, so the TWRP backup will put you back to where you were before trying to replace the build.prop file.
Odd, I wouldn't think that replacing the build.prop with the one for a nearly stock ROM (and same LP base) would render the phone unbootable into OS.
Click to expand...
Click to collapse
who knows. My issue isn't fixed regarding mobile data, either. At least I have a usable phone tho!
I think I'm screwed here. My tablet locked up and I force-powered it down. When it restarted, it went into a soft bootloop and won't load the OS. I'm able to get to my custom recovery and attempted to restore a backup I made in TWRP, but every time I try to restore it displays the screen shown in attached Pic 1, gets to 20% and reboots the tablet. I tried installing a custom ROM and got pretty much the same error (see Pic 2). I can't even wipe the device for some odd reason. All it does is reboot the system. I can get to the screen shown in Pic 3, but I'm not quite sure what my options are. Do I need to factory reset, or do I have a paperweight. I'll sideload if I have to, but I'm not sure of the best way to do this. I'm throwing myself on everyone's mercy here! AAAAAAAGH!
When all else fails, flashing the factory image with fastboot usually will solve the problems.
Sent from my SM-T820 using XDA-Developers Legacy app
jd1639 said:
When all else fails, flashing the factory image with fastboot usually will solve the problems.
Sent from my SM-T820 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I tried flashing the factory image and it appears to have crapped out. See attached image. I think I got a real problem here .
Joe_6pak said:
I tried flashing the factory image and it appears to have crapped out. See attached image. I think I got a real problem here .
Click to expand...
Click to collapse
Think this is a better screencap.
Interesting that bootloader and recovery flash but then nothing else. Try downloading the factory image again. I have seen downloads being corrupted before.
jd1639 said:
Interesting that bootloader and recovery flash but then nothing else. Try downloading the factory image again. I have seen downloads being corrupted before.
Click to expand...
Click to collapse
Think I should stick with Nougat or download the original factory image (5.0, LRX21Q) that it shipped with? I've also heard rumors that it may be a faulty USP port or cable. Thoughts?
It should not matter which version of the factory image. It possibly could be a bad cable. Also, use the usb ports in the back of the computer, not the front, if you're using a pc. I haven't seen this being a problem with nexus devices but it has been on some samsung devices and odin.
jd1639 said:
It should not matter which version of the factory image. It possibly could be a bad cable. Also, use the usb ports in the back of the computer, not the front, if you're using a pc. I haven't seen this being a problem with nexus devices but it has been on some samsung devices and odin.
Click to expand...
Click to collapse
Okay. I used the back USB port and a different cable and I tried flashing the latest Nougat image. Went through without a hitch and it started up but hung on the splash screen and kept rebooting. Flashed the original image and the tablet started up but I got the dreaded "Enter your password" screen. Had NO idea what my password was, so I entered the first PIN that I thought I may have used. Well, that wasn't it, so it took me to a Factory Reset screen because it said I had corrupt data. After a lengthy "erasing" screen, the tablet fired up and I'm back where I started on Day 1. I have no idea if I am still rooted or if my custom recovery survived, but I'm kinda glad the thing at least got started again. My bootloader is still unlocked, and I made sure the "Enable OEM Unlock" box was checked in developer options. Since I just use this for games, email, video watching and an occasional Facebook glance, I'm really not concerned if I'm rooted or not. Obviously I'd like to be, but I'd rather make sure the tabled is updated by a download from Google first. I think my use of Flashfire is what screwed me up in the first place.
Long story short, I'm back up and running, but its 2014 all over again. Will I be able to take the factory update from Google with an unlocked bootloader, and will it be to the latest version of Android? Do you think my custom recovery survived, and is it worth the bother to root and flash it for a (mostly) gaming device? The only thing I can think of that I would want root for is Stickmount (to transfer files) and to get Google Assistant (which I'm pretty sure that I could back-door through Nova Launcher). Oh, yeah, and the adblocking. Let me know what you think. I TRULY appreciate the help, and I'm glad this resource is out there for noobs like me to make it through the Google menagerie.
By the way, does anyone think that going from system to systemless root is what may have caused this?
I'm glad you're up and running. System or systemless should not have made a difference. I'm sure you no longer have a custom recovery or are rooted. I'm guessing you will get an OTA update from Google
jd1639 said:
I'm glad you're up and running. System or systemless should not have made a difference. I'm sure you no longer have a custom recovery or are rooted. I'm guessing you will get an OTA update from Google
Click to expand...
Click to collapse
It took the update just fine. No Google Assistant, but I'll keep trying. Thanks a bunch. REALLY couldn't have done it without your help!
Joe_6pak said:
It took the update just fine. No Google Assistant, but I'll keep trying. Thanks a bunch. REALLY couldn't have done it without your help!
Click to expand...
Click to collapse
Google removed Assistant support from tablets
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
TwinShadow said:
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
Click to expand...
Click to collapse
Downgrade to twrp 3.1.1-0 and try again...
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
TwinShadow said:
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
Click to expand...
Click to collapse
What is your exact model - what's written on the box and what is the model shown in Settings on your stock firmware (if you remember).
I have a sneaking suspicion that it may not be the exactly same device as ours - E5823, creating a conflict somewhere between Firmware/Recovery. Generally, it should get the device data from prop files but you never know I guess...
Here is what you can try: Install latest firmware for E5823 from XperiFirm in Flashtool and wipe everything. If you don't wipe old files are still going to stay! Also, make a backup of all your stuff so you don't lose it. There are guides how to do it here and what things to not wipe in any case.
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
The last 2 nightlys don't work properly!! I have clean installed, wiped everything and gone back to stock and tried and tried again and again!! 20180318 is the one that is true!! Try flashing that build!!
TwinShadow said:
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
Click to expand...
Click to collapse
The thing is some partitions get updated only in that way - like baseband for example. Ensuring everything is the latest version and on a clean slate will remove the chance of weird bugs that nobody knows about or can help you with.
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
TwinShadow said:
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
Click to expand...
Click to collapse
Lol. I have never had that :d and that is from years and years of use and multiple Sony devices...
My guess is a bad flash. That happens rly rarely but maybe u have a bad PC or cable that makes an unreliable connection...
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
TwinShadow said:
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
Click to expand...
Click to collapse
You might wanna ensure you have the latest fastboot drivers installed under 'Disable driver verification' mode.
Hi!
Finally I got stuck in a boot loop on my Pixel 6 running QPR2.
It's looping after the G animation (vibrates a few times at that point when attached to a PC).
Reflashing the latest QPR factory image (without -w) by using SDK 33.0.3 does not solve the issue.
The ROM was running fine before, but it rebooted due to a faulty custom kernel version and now I'm stuck.
My theory is, that the launcher (nova) can't load and therefore it reboots.
Anything I could do using fastboot?
Never flash a custom kernel on a stock ROM, If not suggested by the dev.
I understand that you flash without wipe?
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If the kernel broke your actually ROM, nope. You could backup the file stored locally via adb in the recovery, but not anything more.
Wipe all is the best, better than have to handle with an hard brick.
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If I were you I'd maybe get some logs and go through them and see if you can find anything that way. Maybe add logs to your op here.
There aren't many ways to backup things nowadays for pixel 6 but what I have used to backup apps + app data that works well when restoring is Neo app from Fdroid store. As far as backing up goes, at this time I've used nothing that is/has been as solid as Neo. I miss the days of just being able to boot one of a few various custom recoveries, making a nandroid backup to a USB thumb drive with my OTG cable and restore it whenever it was needed but things change. Sounds like maybe something was left behind from your kernel install. If you really dislike formatting I'd stay away from whatever you installed here to get in this loop but definitely backup using Neo once you get going again and put your backups on thumb drive or you PC or somewhere other than your device so you can restore them when you need to. I don't flash nowhere near as much as I used to but I used to flash my device(s) many times a day , everyday for many years but I remember years ago on another device I looped and wiped my cache and system and reflashed rom and ended up booting up. But that was another device years ago. Maybe try adb sideloading instead of factory image flash without wiping data. Try that and after it's done installing reboot to others slot and sideload it again... These things probably won't work but you never know until you try. Did you have magisk installed before and not now? Maybe flash stock kernel patched with magisk to both slots if so. Hate to say it but you will probably end up having to format data but idk because I don't know exactly how you installed the kernel "in detail" or exactly what kernel it is or if anything else was changed from before you looped ... No logs...
I've been using Android since the beginning (G1) and I've been tinkering with my devices since back in the Nexus S days on a regular basis and I've found that the best way for to get the help I need is to try like hell to figure whatever it is out myself by searching for the problem I'm having, I mean like really searching, sometimes for hours , sometimes maybe searching for things related to the problem I'm having that show up in my searches, sometimes the answer can be in another devices forum, piecing together bits of info from various places to try and solve whatever it is... etc ... etc... But the best way to get help is do research on it, take some notes, try various things to fix it, then if I still can't figure it out make a post about it here and in op attach every log I can possibly gather from said device, include all the things I tried to fix it with myself "in detail..." My exact installation process, you know like: reboot bootloader, was on slot A, executed ./flash-all.sh for factory image xxxxx, rebooted system ... The more details you provide the more accurate people will be when answering and the more people you will get to reply.. I'm not trying to sound like some asshole or anything at all. Im just speaking what works best here to get answers. Sometimes you just don't get any answers even if you post 18 paragraphs with a chart and a line graph, things you tried, what all you tried it with and links to it all. But anyone here who does this will most definitely stand a much better chance at getting some replies on whatever it is. I sometimes read over on Reddit and Tele groups , sometimes answers can be found that way. Sometimes people just give you the silent treatment.. Even if you do your homework. That's just a thing with anything related to development that happens. I always used to think when I would get no replies that the other guys and gals who know the answer are thinking to themselves, "oh look at this idiot here!" "He clearly didn't graduate from Harvard top of his class with a PhD like we did. " " Such an imbecile!!! " But what could have been going on and more than likely was/is is life , kids, bills, sleep, relationships, covid19, and tons of other things..
Some of this development stuff is a real beech to get and everyone works hard to get it and many aren't too fond of just giving random people answers that took them many sleepless nights to get. But if and when a dev sees someone with a detailed post , things tried.... etc ... etc .. Theyre much more likely to throw some knowledge your way. That's been my experience anyway.
@flash713
Wow, thx for thw write up, appreciate!
I was on latest QPR2.1 with Radioctive Kernel, Magisk installed.
Since the device got stuck in the boot animation, I tried a lot and flashed different factory images using the flash-all method. w/o success.
Also tried the Flash tool in the google website, also w/o success.
When the device boots while it's connected to the PC, it beeps/vibrates 3 times and the reboots.
My guess is that it has problems to load the launcher, Nova was set as standart.
I'm using android since years, tinkering a lot, but I'm not a pro in doing so.
Meanwhile i set up my new Pixel 7 and restored it via Google backup and a few apps by using a SWIFT backup.
Fotos were restored by Google, but all whatsapp pictures are messed up ow, cause the date of restore.
How do I gather proper logs?
Did a last attempt and sideloaded the OTA to both slots...same outcome...
Doesn't magisk have a remove all modules.zip? I mean oriole doesn't have TWRP available yet.
I presume that when it's bootlooping you don't have any ADB?
You did have ADB enabled, right?
Depending on system and setup you may have ADB started by init or started by Android.
Your problem could be as simple as a bad Launcher.
I don't know if the P6 has a UART console. Does it?
Hi Renate,
thx for your reply.
Yes, that is what i thought. The Pixel boots up into the G-animation and then loops 3 times (beeping/vibrating if connected to PC) and than reboots in total.
I think I had something like that in the past when I accidently deleted the launcher apk (don't ask )
Anyway, Nova launcher was set as standart, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Sui77 said:
Anyway, Nova launcher was set as standard, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Click to expand...
Click to collapse
I'm still not clear if you have ADB ever available.
If you do you could:
Code:
adb uninstall com.nova.whatever.launcher
If the /data/data that Nova is using is corrupt or missing it could cause failure.
Android will switch to whatever else belongs to android.intent.category.HOME automatically.
If there is nothing there you can install another launcher.
Have adb (after booting into recovery mode), will report back asap
I habe adbd device connected via recovery/rescue mode, but that's not working.
In bootloader, I can't use adb, no device connected.
Hw can I use adb while the device is not booted up?
Can you mount data in recovery (and it's unecrypted)?
Feeling a bit dumb, but I can only boot into fastboot or into the boot loop, don't know how to mount data in recovery mode (the one with the andoird robot)
When you're in the boot loop you don't get adb even for a few seconds?
This are the last lines of the recovery.log
2 new items by TheMrSui
photos.app.goo.gl
Checked that by opening a cmd and using "adb devices", but nothing showed up
When you're viewing that log, don't you have ADB working then? It says that it is.
I had this weird issue on Raven, first try using android flash tool through a chrome based browser. If that still loops then wipe, and flash an older image. For some reason I had to flash an image from the previous month and that would boot.