my situation right now: installed jokersax atrix 4.4 but some issues came up about two weeks ago:
1. wifi broke suddenly, wont refresh
2. phone reboots and reboot and reboots sometimes within 30s other times after a few days... not sure why
3. somehow revert's to previous versions?? idk what happens but some times after reboot my wallpaper will return to the one i had a month ago
right now im having some issues with moto-fastboot... not sure what im doing wrong
what i have done so far:
using cwm to restore to previous states and flashing to new states with cwm nothing worked
currently:
DL'ed the system.img from the site and moved everything to a common folder
power on phone with vol down up etc. "starting fastboot protocol support shows up
> cd [path]
> moto-fastboot flash system system.img
connect phone via usb
*nothing*
but it seems to be stuck on "<waiting for device>"
downloaded the fastboot files from here:
http://forum.xda-developers.com/showthread.php?t=1138092
i appear to have done everything required...
-_-
James.UBC said:
my situation right now: installed jokersax atrix 4.4 but some issues came up about two weeks ago:
1. wifi broke suddenly, wont refresh
2. phone reboots and reboot and reboots sometimes within 30s other times after a few days... not sure why
3. somehow revert's to previous versions?? idk what happens but some times after reboot my wallpaper will return to the one i had a month ago
right now im having some issues with moto-fastboot... not sure what im doing wrong
what i have done so far:
using cwm to restore to previous states and flashing to new states with cwm nothing worked
currently:
DL'ed the system.img from the site and moved everything to a common folder
power on phone with vol down up etc. "starting fastboot protocol support shows up
> cd [path]
> moto-fastboot flash system system.img
connect phone via usb
*nothing*
but it seems to be stuck on "<waiting for device>"
downloaded the fastboot files from here:
http://forum.xda-developers.com/showthread.php?t=1138092
i appear to have done everything required...
-_-
Click to expand...
Click to collapse
Why don't you try using cwm method if your not familiar with fastboot
Sent from my MB860 running Jokersax's CM9
i did
restore/flashing with cwm did nothing. even flash 5.1 +wipe
every time i try to turn the wifi on it freezes then reboots...
i guess my question is this -- how do i fix the wifi issue?
when i flash it it's stable until i turn on wifi so i assume the boot loop is somehow caused by the wifi but flashing rom dosnt do anything to reset it
some times it also somteitmes takes a good while longer to boot up. ~1 min in the bootloader
James.UBC said:
i did
restore/flashing with cwm did nothing. even flash 5.1 +wipe
every time i try to turn the wifi on it freezes then reboots...
i guess my question is this -- how do i fix the wifi issue?
when i flash it it's stable until i turn on wifi so i assume the boot loop is somehow caused by the wifi but flashing rom dosnt do anything to reset it
some times it also somteitmes takes a good while longer to boot up. ~1 min in the bootloader
Click to expand...
Click to collapse
Have you tried turning on your bluetooth? if the same happens it could be a hardware issue.
<edit> well actually i just saw your post about your bluetooth also broken…i think its a hardware issue
well damn... what should i do then?
im pretty sure my warranty is up :/ and i'd have to go state side -_-
Related
First off id like to say thanks in advance to any replies and also apologize if this has been posted previously (i searched and could not find anything that was helpful) I lurked around these forums when i had my x1 and im hoping you guys can be as helpful for me as you are for everyone else. anyway onto the issue
I used the superboot method to root my ATT US Streak. My intentions were to update to 2.1 following the steps in the "eclair working on my u.s. unlocked streak!" thread (wont let me put a link since its my first post)
after using fastboot to root the phone will boot up and function fine but recovery and fastboot no longer work. i tried flashing Koush's custom recovery and other things that require fastboot and the terminal just says "sending..." nothing happens no errors or anything, the cmd prompt just sits there and i need to remove the battery to reboot the device.
i then downloaded the Rom Manager apk from the market and flashed the clockwork recovery from there (it said i did anyway). when i load the recovery from boot (volume keys + power and its the stock recovery) and chose option 2 to flash modaco custom rom or even the stock dell rom it just goes to a black screen and i once again need to remove the battery to reboot.
the phone itself is still functioning fine when it boots up and everything works the way it should other than the home, menu, and back button lights flash in random orders, thats just annoying though. again any help is appreciated
so what should i try next?
EDIT: woke up this morning and now the device will not turn on. i tried starting to fastboot and recovery but still nothing. plug it into my pc and i get the "found new hardware wizard" for a Qualcomm CDMA Technologies MSM.
first real brick? ha that would be my luck
EDIT 2: a kid just ran through my work, grabbed my phone and threw it on the ground. it screwed up the 30 pin connector on the phone and the charger. im going to hurt somebody. phone is booting again though... put sd card back in and still boots fine
SOLVED: Dont know the technical reasons behind it but i had to reinstall the drivers and switch usb ports for every fastboot and recovery procedure
removed SD card and its booting up normally. any thoughts?
Here's my situation, maybe someone will find it interesting or know what's going on. I was running the EOS Jelly Bean (EOS-tf201-20120728-31.zip). Everything was running pretty well for a few days, then yesterday the device simply powered off. When I rebooted it got to the splash screen then shut off before it could get any farther. I figured it was a power issue, so I plugged it in and charged it for a while but get the same response. Around this point I started to get suspicious and tried to boot into recovery. It got to "Booting Recovery Kernel Image" then powers off the same way.
So then I proceed to go into fastboot and fastboot works great no power offs. Through that I am able to flash openrecovery-twrp-2.2.1-tf201.blob and the virtuous packaged boot as per this thread http://forum.xda-developers.com/showthread.php?t=1773280 as well as factory reset. I also tried a few other boot/recovery combinations and was able to make it into recovery. In twrp recovery I was able to install the latest Virtuous rom which got me back to stock and I thought good case closed. I even made it all the way into the OS and was able to install apps, wifi worked great, run the apps etc. Eventually the screen went blank though and I was stuck back in the same shutdown on boot scenario as described above. Now I'm able to fairly consistently flash openrecovery-twrp-2.2.1-tf201.blob, reboot, get into teamwin recovery, but now even that appears to be randomly powering off.
So now I'm guessing that it may just be bricked and is probably a hardware issue since the reboots appear so random, the unit was refurbished. At the same time I'm still holding out some hope that it's simply some boot code somewhere that was corrupted and I can flash something and get things back to normal again since I can still access fastboot and occasionally ADB and recovery. I've flashed from fastboot system/recovery/boot, any other thoughts or potential combinations I could try? Also anything I can do with those tools to debug it further and get more data on what may be the root cause?
Hi all, so i´ts my first time here posting but I´ve been following this forums long ago and touching stuff with my phones.
Today (well today... i´m working on this since yesterday) I´ll need the help of the most veteran users since I can´t solve this on my own.
I Have an XT910 Razr Moto. Yesterday I charged it with it being off, but to my surprise when I powered it on, I got the Fastboot screen saying the device is locked. Here´s the complete error:
-----------
AP Fastboot Flash Mode (S)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery Ok
Ok to Program
Connect USB Data cable.
-----------
So, after getting this, obviously I thought, well, power off, or force power off, then power it on, and lets go... Well, nothing, I constantly get into Fastboot again.
What I figured out is that if I power it off, then hold vol down + vol up and power at the same time, I actually CAN get into boot menu but It will not let me select anything, it will just show it and boot in Safe Mode for me.... Tried factory reset also, so i could backup everything...
After going through all that I decided to give it a try and go for RSD with stock firmwares from sbf.droid-developers.org. I got like 4 and they all stucked at cdt.bin flashing part... Giving me an error about 6/18 process that can´t flash cdt.
So far I´ve tried LOTS LOTS of stuff like some .zip going around there to fix the CDT, with no luck...
THen I ran into this post
http://forum.xda-developers.com/showthread.php?t=1651596
Which was very usefull to have some progress, like completing the flash by erasing some lines in the xml about the cdt. system (cause it hung a lot there and gave error again)...
However, the error still persists, I boot up my damn phone and it goes into AP Fastboot. When i go into Safe Mode I see that everything has been wiped so its like a factory phone now, but still in safe and powering it off won´t make the difference.
I´m kinda desperate and about to throw this phone out of the window. Is there any pro savior out there who can give me more tips?
Thanks!!!!!!!!!
-Musashi- said:
Hi all, so i´ts my first time here posting but I´ve been following this forums long ago and touching stuff with my phones.
Today (well today... i´m working on this since yesterday) I´ll need the help of the most veteran users since I can´t solve this on my own.
I Have an XT910 Razr Moto. Yesterday I charged it with it being off, but to my surprise when I powered it on, I got the Fastboot screen saying the device is locked. Here´s the complete error:
-----------
AP Fastboot Flash Mode (S)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery Ok
Ok to Program
Connect USB Data cable.
-----------
So, after getting this, obviously I thought, well, power off, or force power off, then power it on, and lets go... Well, nothing, I constantly get into Fastboot again.
What I figured out is that if I power it off, then hold vol down + vol up and power at the same time, I actually CAN get into boot menu but It will not let me select anything, it will just show it and boot in Safe Mode for me.... Tried factory reset also, so i could backup everything...
After going through all that I decided to give it a try and go for RSD with stock firmwares from sbf.droid-developers.org. I got like 4 and they all stucked at cdt.bin flashing part... Giving me an error about 6/18 process that can´t flash cdt.
So far I´ve tried LOTS LOTS of stuff like some .zip going around there to fix the CDT, with no luck...
THen I ran into this post
http://forum.xda-developers.com/showthread.php?t=1651596
Which was very usefull to have some progress, like completing the flash by erasing some lines in the xml about the cdt. system (cause it hung a lot there and gave error again)...
However, the error still persists, I boot up my damn phone and it goes into AP Fastboot. When i go into Safe Mode I see that everything has been wiped so its like a factory phone now, but still in safe and powering it off won´t make the difference.
I´m kinda desperate and about to throw this phone out of the window. Is there any pro savior out there who can give me more tips?
Thanks!!!!!!!!!
Click to expand...
Click to collapse
What fastboot files did you tried to flash?Were you on ICS or JB before the brick?Where are you from?
Error 6 means that you are trying to flash wrong firmware,for example,you was on JB and now you want to flash ICS.
Here are JB Fastboot files http://forum.xda-developers.com/showthread.php?t=2231289,just flash one for your region.
welder73 said:
What fastboot files did you tried to flash?Were you on ICS or JB before the brick?Where are you from?
Error 6 means that you are trying to flash wrong firmware,for example,you was on JB and now you want to flash ICS.
Here are JB Fastboot files http://forum.xda-developers.com/showthread.php?t=2231289,just flash one for your region.
Click to expand...
Click to collapse
I´m from Argentina. And you are totally correct, I downloaded FB files for 4.0.4 , but now I tried running the phone in Safe Mode, went to sys info to take a look at it. And found I have 4.1.2
So question is, from that list you gave me, the "Retail Brazil" should do it? as well as UK retail or any other?? Which one should I chose
Thanks!!!!!!!! a lot
welder73 said:
What fastboot files did you tried to flash?Were you on ICS or JB before the brick?Where are you from?
Error 6 means that you are trying to flash wrong firmware,for example,you was on JB and now you want to flash ICS.
Here are JB Fastboot files http://forum.xda-developers.com/showthread.php?t=2231289,just flash one for your region.
Click to expand...
Click to collapse
Ok so I have made quite a progress here. I was able to get a Brazilian version which is from LATAM and RSD flashed straight like a charm. Now I have the clean new firmware.
And even I can read in the fastboot 0A.77 instead of 0A.74 version
HOWEVER: problem with the Fastboot still persists. Even the phone itself when it restarts goes into Fastboot and when I´m able to make a boot menu I can´t choose anything and it goes directly to Safe Mode.
Now that the system´s """""fixed"""" and I could flash it.... Any tips on taking this off? I cant start the phone in normal mode :S
I was on my phone when suddenly it just booted off for no reason, weird right? So now it just stays on the "LG" boot up screen and now do anything. I've tried everything and done everything right (as far as I know) before I get into that let me tell you what my device can do as of now:
Devices DOES have fastboot oem unlock done
Phone was rooted as well and working perfectly (or so I thought until this happened)
ADB doesn't seem to work, but fastboot when connected to the computer does.
Ex: ADB devices (blank)
but fastboot devices (shows phone connected)
I've tried rebooting into recovery (Power + down) doesn't do anything, however, {Power + down} then finger off power then {Power + down} again takes me to "factory reset" option, if done so the phone just hangs and removing battery on way to take it back to fastboot on pc, or bootloop again.
I've done the following steps using [LG-H901] Stock .img Files (Boot, System, and Recovery)
Code:
fastboot flash system system.img
then
fastboot flash boot boot.img
and finally
fastboot flash recovery recovery.img
I've tried booting the phone and still gets me stuck on bootloop, and doing the same {Power + down} gets to the same "factory reset" option only then freezes my phone if I agree to do so.
Is there something I've done wrong or incorrect? I will provide as much info as requested.
Thanks guys!
Update: Phone booted up to lockscreen after finishing "Android is starting..." procedures, then kept bootlooping and it is now doing "Android is starting.." procedures again. I'll keep it updated if it keeps doing so or anything of the sort.
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Double0EK said:
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Click to expand...
Click to collapse
This is the weirdest thing, phone worked for a bit then shuts off and does the same thing. all files and everyhing was in tact. ANy main reason behind this? I am desperate not to delete everything because i have important photos on there that were still there when it re-started again right now.
So to recap: At the moment doing the {factory reset} got me as far as using phone for like 2 minutes before ****ting out and sending me on a bootloop yet again.
Important Questions:
On all my other devices I am able to connect via usb and read devices, but on this phone I get the message when connecting to my computer "LGE Android MTP Device: Failed" whats this about?
Is there any way to save internal photo album images other than getting this to boot up and pray it stays on long enough to transfer data?
UPDATE 2: Phone has booted up and not froze (yet)? Testing to see if it will keep working so far so good. Unfortunately all my **** was deleted which bummed me out, would have honestly prefered to lose a $600 phone than all the family, friend, ext photos I had on my phone I made the huge mistake of saving to internal memory and never backing up. Smh.
Update 3: Phone is back at it again with the bootloop. I have no idea what is wrong, I've repeated the steps twice and phone doesn't seem to let up. It's fine until I hit that restart or shutdown button then it goes into bootloop heaven. I'm guessing this phone is done for? On an unrelated note it did fall on me, but worked fine afterwards, it was just sudden when it started doing this. Unless anyone has more suggestions I'd be glad to hear them. As of right now, this phone is toast.
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Double0EK said:
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Click to expand...
Click to collapse
I am thinking the warranty route. Is there anything specific I should do before doing so? I hear having "fastboot oem unlock" {Bootloader Unlocked} voids the warranty. Is this true that you might know of? Either way thanks I appreciate the information.
Sorry so late..
But you can try to fastboot oem lock it.
Hi Im new to the forum but I am finding it to be a massive resource for all things technical android. I am also new to rooting android but am technically savvy, (10 years in IT will do that). Initially it went just fine, even if a speed bump here or there. I got my Sony Z2 (starting BL unlocked w most recent Sony stock .291 firmware) rooted and flashed with TWRP and SuperSU (UPDATE-SuperSU-v2.76-20160630161323.zip) using rocker00's guide. I was then able to successfully flash ParanoidAndroid's latest (pa_sirius-6.0.3-20160809-signed.zip) and Gapps (A-GAPPS+6.0.1_14.05.2016_v5.2.zip) using TWRP recovery. I got a minor bootloop trying to get PA running, but re-flashing seemed to clear it up. It seemed to work fine although I couldn't figure out how to get the pie controls or the halo notifications to work. Without those things i couldn't see the point, so I decided to try Cyanogen (cm-12.1-20161016-NIGHTLY-sirius.zip). Apparently this uses a different recovery (CWM), I was a little worried but went for it anyway. It seemed to be fine after the first reboot. I rooted fine (same SuperSU as before) and started installing apps via Google restore. But after the next reboot, it started bootlooping. First it would cycle between the Sony screen and a blank screen, But after trying a bunch of things (I'll detail below), it just hangs at the Sony screen indefinitely.
So, what I've tried till now to fix it is:
1) First I tried to reinstall TWRP using the tool from rocker00's post with the phone in fastboot mode. The flash went without error, but did not fix the problem. I have not been able to get into recovery since the bootloop. In the process I also did a fastboot -w, which also seemed to have relatively no effect, although I would get the android robot with the blue progress once before it reboot into the bootloop.
2) With the phone in flashmode I tried flashtooling the kernel again with the same from rocker00's post (D6503_23.5.A.0.575_kernel.ftf). No effect. I also tried flashing recovery a few more times using the script from his post to no effect (i think the phone needs to be booted for this tool to work).
3) I've tried all the relevant commands from this page and this page, hoping to eradicate whatever errant code is screwing with my phone. Since fastboot seems to be the only way to interact with my phone. I tried:
Code:
fastboot flash recovery /path/to/twrp-3.0.2-0-sirius.img
fastboot -w
fastboot update /path/to/pa_sirius-6.0.3-20160809-signed.zip
the attempt to flash PA through fastboot errored with a message about not having "android-info.txt".
I also desperately tried:
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
the one about data errored. the others seemed fine, but didn't change the situation.
This guide was informative yet quite useless to me, since I definitely don't want to start scripting my phone 2 days after starting this stuff. I've also scoured this forum and others for similar situations, which I've found but they all seemed to get resolved by either doing stuff I've already tried or from having a completely irrelevant problem to my own..
I'm really scratching my head here because it is all stock TWRP and Android or should be by now. adb commands aren't connecting due to stock android not having USB debugging enabled, and without being able to boot into the settings I can do nothing to change that. So all I have is fastboot. I also have a TWRP backup image I made before installing PA but till now Ive seen no way to restore it without booting into recovery.
Any help please!!!! This can't be bricked!!
epeace said:
Hi Im new to the forum but I am finding it to be a massive resource for all things technical android. I am also new to rooting android but am technically savvy, (10 years in IT will do that). Initially it went just fine, even if a speed bump here or there. I got my Sony Z2 rooted and flashed with TWRP (twrp-3.0.2-0-sirius.img) and SuperSU (UPDATE-SuperSU-v2.76-20160630161323.zip) using this guide. I was then able to successfully flash ParanoidAndroid's latest (pa_sirius-6.0.3-20160809-signed.zip) using TWRP recovery. I got a minor bootloop trying to get PA running, but re-flashing seemed to clear it up. It seemed to work fine although I couldn't figure out how to get the pie controls or the halo notifications to work. Without those things i couldn't see the point, so I decided to try Cyanogen. Apparently this uses a different recovery (CWM), I was a little worried but went for it anyway. It seemed to be fine after the first reboot. I started installing apps, rooted fine. But after the next reboot, it started bootlooping. First it would cycle between the Sony screen and a blank screen, But after trying a bunch of things (I'll detail below), it just hangs at the Sony screen indefinitely.
So, what I've tried till now to fix it is:
1) First I tried to reinstall TWRP. The flash went without error, but did not fix the problem. I have not been able to get into recovery since the bootloop. In the process I also did a fastboot -w, which also seemed to have relatively no effect.
2) I tried flashtooling the kernel again with the same from rocker00's post (D6503_23.5.A.0.575_kernel.ftf). No effect. I also tried flashing recovery a few more times using the script from his post to no effect.
3) I've tried all the commands from this page and this page, hoping to eradicate whatever errant code is screwing with my phone. Since fastboot seems to be the only way to interact with my phone. I tried:
Code:
fastboot flash recovery /path/to/twrp-3.0.2-0-sirius.img
fastboot -w
fastboot update /path/to/pa_sirius-6.0.3-20160809-signed.zip
the attempt to flash PA through fastboot errored with a message about not having "android-info.txt".
I also desperately tried:
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
the one about data errored. the others seemed fine, but didn't change the situation.
This guide was informative yet quite useless to me, since I definitely don't want to start scripting my phone 2 days after starting this stuff. I've also scoured this forum and others for similar situations, which I've found but they all seemed to get resolved by either doing stuff I've already tried or from having a completely irrelevant problem to my own..
I'm really scratching my head here because it is all stock TWRP and Android or should be by now. adb commands aren't connecting due to stock android not having USB debugging enabled, and without being able to boot into the settings I can do nothing to change that. So all I have is fastboot. I also have a TWRP backup image I made before installing PA but till now Ive seen no way to restore it without booting into recovery.
Any help please!!!! This can't be bricked!!
Click to expand...
Click to collapse
Welcome to XDA!
May I know what fw version did you initially start with? .575 or .291 or any others?
iXaidyiu said:
Welcome to XDA!
May I know what fw version did you initially start with? .575 or .291 or any others?
Click to expand...
Click to collapse
Hi iXaidyiu,
I started with .291. i stopped going back to it after the first time as I noticed that the custom recovery stopped working in .291. I have had it at .575 since then. And of course now that I can't get into recovery .291 is not an option unless I find an ftf of it for flashtool.
Another observation I forgot to mention is that I cannot turn the thing off. I have to force quit it (vol up + power) and after a second it boots up again to get stuck at Sony screen. I have noticed that if I do the flash boot buttons (vol down + power) I get a different Sony screen (without the xperia logo). But it sticks just the same. I don't even know if the phone is charging at this point, although it was on the Sony screen all night so there must be some charging happening. How could this have gotten so screwed up? It was working fine and I was doing benign activities at the time it choked
epeace said:
Hi iXaidyiu,
I started with .291. i stopped going back to it after the first time as I noticed that the custom recovery stopped working in .291. I have had it at .575 since then. And of course now that I can't get into recovery .291 is not an option unless I find an ftf of it for flashtool.
Another observation I forgot to mention is that I cannot turn the thing off. I have to force quit it (vol up + power) and after a second it boots up again to get stuck at Sony screen. I have noticed that if I do the flash boot buttons (vol down + power) I get a different Sony screen (without the xperia logo). But it sticks just the same. I don't even know if the phone is charging at this point, although it was on the Sony screen all night so there must be some charging happening. How could this have gotten so screwed up? It was working fine and I was doing benign activities at the time it choked
Click to expand...
Click to collapse
Well if so, let's just start from scratch, because you seems to have screwed quite badly and complicated.
Firstly, flash .291 firmware with the three boxes under "Wipes:" ALL CHECKED, check also "AUTO_BOOT" on the right column. These steps will return your device into factory state.
After the flashing process has finished, if your device turned on automatically, turn it off, then unplug the device and replug it when pressing vol+ key, this will enter fastboot mode, you can have two ways to follow now:
(1) Select "Flash", "Fastboot Mode", "Select kernel to flash", navigate to the directory that contain the kernel downloaded (I personally recommand Elite Kernel and extracted), then flash the .IMG file;
(2) Open a cmd using shift+R mouse on the blank space in the directory that stores your twrp.IMG (you can download it here), and type in:
Code:
fastboot flash recovery <filename>.img
and press Enter.
In both method, after you have pressed Enter and see there are two "Okay" printed in the CLI, unplug your device and boot it.
During boot, you will see yellow or green LED light blinked, press vol+ button once and hurray, you will be booted into TWRP recovery!
Now you can load your zip onto your SD card and start flashing! Happy flashing!
P's1 When you tried to boot up your device with the vol- button pressed together, you will be booted into SAFE_MODE, in this mode all 3rd party applications will be disabled.
P's2 I personally DO NOT recommend you to flash zip or erase anything using fastboot commands, use TWRP instead
Thank you iXaidyiu. Option 1, although it fails to boot normally, was successful in getting me back into recovery! Now that I'm in recovery, I first tried to restore my back up. But this failed with errors:
Code:
Failed to mount '/system' (Invalid Argument)
Failed to mount '/data' (Invalid Argument)
Failed to mount '/cache' (Invalid Argument)
So then I tried to flash PA again (since that was the only rom I had on my sd card right now) which also failed with the same errors plus new ones:
Code:
Failed to mount '/data' (Invalid Argument)
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Download/pa_sirius-6.0.3-20160809-signed.zip'
It also said that "This package is for "sirius" devices; this is a "".". Apparently my Z2 is no longer identifying as 'sirius'. I checked the file system, and I can see that the /data, /cache, and /system folders are physically there. Why are they not mounting? Permissions? :s What to do from here?
UPDATE: This "Failed to mount /data error" seemed to be the root of all the problems till now. Others on the net with this error also see boot hanging at the mfr logo. However, I was able to solve it by formatting /data. I still couldn't flash PA due to the 'This package is for "sirius" devices' error, but I was able to restore my TWRP backup, which then solved the "sirius" ID issue, after which I could flash PA just fine! Thanks iXaidyiu for your help in getting me back into recovery! That was clutch to me finding the solution!
@epeace
If you ever face the device id issue again, unzip the ROM, navigate down /META-INF/com/Google/Android/updater-script and delete the following line:
Code:
getprop("ro.product.device") == "sirius" ||
abort("E3004: This package is for \"sirius\" devices; this is a \"" +
getprop("ro.product.device") + "\".");
(probably the first of the code till a semi-colon)
This disable the Device ID check when you flash the ROM.
P's May I know how's your phone charging status? I am curious cuz' I once tried flashing PA 6.0.3 and all working good EXCEPT the battery cannot be charged. It keeps draining itself even though it can sense the presence of the charger but it still cannot charge:crying:
Ok great tip, I'll make that edit for next time. Re: the charging, I think it's charging, but it's definitely charging very slow. But a number of things could be contributing to that, I'm constantly on it right now (setting it up), i'm charging off of my computer (usually slow to begin with), and this phone is a few years old so the battery is not what it used to be. I'll keep an eye on it the next days, and report back here and let you know what I've observed. Thanks again for your help!
iXaidyiu said:
@epeace
P's May I know how's your phone charging status? I am curious cuz' I once tried flashing PA 6.0.3 and all working good EXCEPT the battery cannot be charged. It keeps draining itself even though it can sense the presence of the charger but it still cannot charge:crying:
Click to expand...
Click to collapse
Hey @iXaidyiu,
I no longer have PA installed, but in the couple days with it I didn't notice any difference in battery performance compared to other ROMs. I think that shouldn't be a deterrent. At the moment I'm trying out GarvityBox on rcstar6696's vanilla MM/Nougat. So far it feels right, although rooting was a little tricky for some reason. We'll see how that goes!