I flashed aerokernel and it worked great.
Today i wake up and the phone was off due it ran out of battery, now im charging it and it wount pass first motorola logo, shows it and then it vanish from pink to black.. screen backlight is noticiable, but i cannot do anything.
any ideas?
Antieco said:
I flashed aerokernel and it worked great.
Today i wake up and the phone was off due it ran out of battery, now im charging it and it wount pass first motorola logo, shows it and then it vanish from pink to black.. screen backlight is noticiable, but i cannot do anything.
any ideas?
Click to expand...
Click to collapse
How long have you been charging?
You need a couple of hours before thinking there is a problem.
alresave said:
How long have you been charging?
You need a couple of hours before thinking there is a problem.
Click to expand...
Click to collapse
It goes into recovery without problem, it just wont go further the logo... the funny thing is this pink vanishing screen.
its charging now for about 20 minutes and its on 45%...
i tried flashing stock kernel, radio & modules without success.
Im on stock KK 4.4.3 US retail / Philz recovery
Antieco said:
It goes into recovery without problem, it just wont go further the logo... the funny thing is this pink vanishing screen.
its charging now for about 20 minutes and its on 45%...
i tried flashing stock kernel, radio & modules without success.
Im on stock KK 4.4.3 US retail / Philz recovery
Click to expand...
Click to collapse
I'm not sure flashing stock kernel would help or make things worse. AeroKernel renames or deletes a library when it's flashed.
If it is charging then your device is working somehow. Maybe you'll need to re-flash 4.4.3 ROM using mfastboot to recover the phone.
Did you try to undervolt or overclock AeroKernel?
Have you tried pressing power button for about 5 minutes?
alresave said:
I'm not sure flashing stock kernel would help or make things worse. AeroKernel renames or deletes a library when it's flashed.
If it is charging then your device is working somehow. Maybe you'll need to re-flash 4.4.3 ROM using mfastboot to recover the phone.
Did you try to undervolt or overclock AeroKernel?
Have you tried pressing power button for about 5 minutes?
Click to expand...
Click to collapse
Thanks! will restoring with mfastboot delete my data partition?
Antieco said:
Thanks! will restoring with mfastboot delete my data partition?
Click to expand...
Click to collapse
Yes it will delete your data partition.
Did you make a nandroid backup before flashing AeroKernel?
alresave said:
Yes it will delete your data partition.
Did you make a nandroid backup before flashing AeroKernel?
Click to expand...
Click to collapse
No i didnt.. cant just flash it over it? as a zip?
Antieco said:
No i didnt.. cant just flash it over it? as a zip?
Click to expand...
Click to collapse
Yes, but it has to be done prior to flashing something that can potentially break your system.
The nandroid backup creates full images of your partitions with all the data on them. So if your device has an error the nandroid backup will restore it as it was before. It is recommended to make a nandroid before flashing a new kernel or rom, so you can revert to a previous state if anything goes wrong.
alresave said:
Yes, but it has to be done prior to flashing something that can potentially break your system.
The nandroid backup creates full images of your partitions with all the data on them. So if your device has an error the nandroid backup will restore it as it was before. It is recommended to make a nandroid before flashing a new kernel or rom, so you can revert to a previous state if anything goes wrong.
Click to expand...
Click to collapse
I know its a good practice, but as mine just got 5gb free its quite hard to have a full nandroid... im going to try installing the kk4.4.3 zip version.. hope find it around... that should keep my data partition untouched innit?
Antieco said:
I know its a good practice, but as mine just got 5gb free its quite hard to have a full nandroid... im going to try installing the kk4.4.3 zip version.. hope find it around... that should keep my data partition untouched innit?
Click to expand...
Click to collapse
If it is a normal flashable zip and you dirty flash it, it should work. Just don't make the factory reset.
Antieco said:
I know its a good practice, but as mine just got 5gb free its quite hard to have a full nandroid... im going to try installing the kk4.4.3 zip version.. hope find it around... that should keep my data partition untouched innit?
Click to expand...
Click to collapse
If you mean the tar.zip file or something like that, then you have to use mfastboot. Just don't do mfastboot erase userdata and you can keep your apps
Related
my one s recently developed a strange issue, where if i try to run a nandroid backup, it will mostly finish, then reboot itself without fully completing the process, leaving me with a bunk backup and stuck on one rom for now. also, and the more important of my 2 concerns, is that i don't know if it will do this during a rom flash, nor do i want to find out, seeing as i have no current working backup. doe's anyone have any ideas as to how i could fix this?
mercenaryhmster said:
my one s recently developed a strange issue, where if i try to run a nandroid backup, it will mostly finish, then reboot itself without fully completing the process, leaving me with a bunk backup and stuck on one rom for now. also, and the more important of my 2 concerns, is that i don't know if it will do this during a rom flash, nor do i want to find out, seeing as i have no current working backup. doe's anyone have any ideas as to how i could fix this?
Click to expand...
Click to collapse
At a guess you got a high Hboot so that means when you restore its not restoring the boot.img. You need to flash that in fastboot.
Darknites said:
At a guess you got a high Hboot so that means when you restore its not restoring the boot.img. You need to flash that in fastboot.
Click to expand...
Click to collapse
nope, i have hboot 1.06, and either way that wouldn't, and shouldn't, cause a nandroid to fail during backup, nor for the phone to reboot by itself.
mercenaryhmster said:
nope, i have hboot 1.06, and either way that wouldn't, and shouldn't, cause a nandroid to fail during backup, nor for the phone to reboot by itself.
Click to expand...
Click to collapse
Oh if you mean you cant make a backup try a newer recovery or if its already up to date try an old one.
Edit, just to add I use TWRP 2.2.2.0 and it works fine.
Darknites said:
Oh if you mean you cant make a backup try a newer recovery or if its already up to date try an old one.
Edit, just to add I use TWRP 2.2.2.0 and it works fine.
Click to expand...
Click to collapse
tried using twrp 2.3, 2.2, cwm touch, regular cwm, does it on all of them.
mercenaryhmster said:
tried using twrp 2.3, 2.2, cwm touch, regular cwm, does it on all of them.
Click to expand...
Click to collapse
Not sure then sorry.
Do you have enough free space on your sdcard partition?
You can also try (un?)mounting /data and /system before you start the backup.
Just as an update, I solved my problem. It seems that there were some corrupted files on my data partition, and they were causing nandroid to fail and reboot randomly. So, since I was planning on wiping anyway, I wiped and set up viper again, and successfully made a nandroid after.
Well, me being me, screwed up rooting this thing by putting the wrong system.img.gz version into my B1-710. Is there a way to fix this bootlooping or not?
Shark0727 said:
Well, me being me, screwed up rooting this thing by putting the wrong system.img.gz version into my B1-710. Is there a way to fix this bootlooping or not?
Click to expand...
Click to collapse
80% not ...
on the other side if you replace files from your stock system.img to the one which you just flashed, and than flash it again after replacing files..
You may be able to save your data and boot.
Else you can save your data by taking a CWM backup, and again flashing your ROM and from advance restore, Restore data only.
droid-devz said:
80% not ...
on the other side if you replace files from your stock system.img to the one which you just flashed, and than flash it again after replacing files..
You may be able to save your data and boot.
Else you can save your data by taking a CWM backup, and again flashing your ROM and from advance restore, Restore data only.
Click to expand...
Click to collapse
I see but, I didn't take a CWM backup or get my stock system.img. As well, I havent found the clockwork recovery for the B1-710. I do have a sd-card for it. But all I require is the firmware for it. Anything on that?
I have a friend who has the Skyrocket.
He is rooted and has TWRP installed, but he is still running the stock rom and kernel.
Today his phone randomly rebooted and now it is stuck on the samsung logo. We have been able to take out the battery and boot into TWRP no problem.
We do have a backup from a while back and he is also considering trying a new rom at this point, but we'd like to be able to get this to boot.
Anyone have any ideas on how to get this thing to boot? What could have caused this?
Any help is greatly appreciated.
If the backup is a nandroid backup made in twrp restore that in twrp
jd1639 said:
If the backup is a nandroid backup made in twrp restore that in twrp
Click to expand...
Click to collapse
We do have a twrp backup and can restore it, but we're hoping to find something that will fix the boot issue.
Do you think it could possible fix the problem if we flashed a new kernel and then tried to boot? Can't hurt, right?
iLuvMudkips said:
We do have a twrp backup and can restore it, but we're hoping to find something that will fix the boot issue.
Do you think it could possible fix the problem if we flashed a new kernel and then tried to boot? Can't hurt, right?
Click to expand...
Click to collapse
You could try the kernel our you could also try wiping just cache and dalvik. I assume you're trying to save the data.
jd1639 said:
You could try the kernel our you could also try wiping just cache and dalvik. I assume you're trying to save the data.
Click to expand...
Click to collapse
We aren't trying to save the data. We already have a backup. We're trying to get this thing to boot without flashing a new rom or reverting to a backup.
iLuvMudkips said:
We aren't trying to save the data. We already have a backup. We're trying to get this thing to boot without flashing a new rom or reverting to a backup.
Click to expand...
Click to collapse
read the stickys, this one is right above your post, short answer wipe caches and if still a no go then do a factory reset, still a no go then restore, still a no go then read the sticky
Hi guys, can somebody help me? I received the stagefright update this morning and after downloading it and rebooting, the phone stopped working. It shows the logo animation for a few seconds then the screen goes black. It's a rooted and unlocked phone so i don't know if thats the cause. Also, i can access the recovery mode pressing power and down. Other than that nothing.
If you were rooted and updated ya..the rooting may be the reason
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Jaydeep123 said:
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Click to expand...
Click to collapse
I always forget how peacefull people with knowledge can be. Thanks mate, will do that.
But, just for curiosity: rooted phones tends to have problems after updates?
Yes It may get error or Somthing Else Thats Why I prefer if a update is avaiable flash back to stock and then proceed
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
reinaldojr said:
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
Click to expand...
Click to collapse
Mod will move or merge.
Sent from my MotoG3 using XDA Free mobile app
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
hp420 said:
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
Click to expand...
Click to collapse
Hello HP429; reflashin full factory image would effectively wipe phone
sunandoghosh said:
Hello HP429; reflashin full factory image would effectively wipe phone
Click to expand...
Click to collapse
Not if you only flash the system, boot and recovery image files
Recover the factory
I did the update and as mentioned previously on the thread stales after the logo. (bootloader is unlocked)
I can not find my oem backup. I tried twrp on recovery and was able to backup other stuff. Is there a way to generate the OEM so that i can flash or any other roms that are compatible with Moto G 3rd generation?
Try wiping cache, dalvik cache and data with TWRP. Don't use stock recovery for the data wipe or you will lose all the files stored on your internal partition, as well.
Edited the build.prop file by adding 1 line, restarted phone and now I keep getting System UI has stopped message.
Any way I can edit the file to fix my phone?
Have you tried to clear the cache in recovery? If that doesn't work, try a full factory reset.
If the phone is running a stock rom, try flashing just the system.img file in fastboot.
Before doing any of this, make sure you backup your data.
audit13 said:
Have you tried to clear the cache in recovery? If that doesn't work, try a full factory reset.
If the phone is running a stock rom, try flashing just the system.img file in fastboot.
Before doing any of this, make sure you backup your data.
Click to expand...
Click to collapse
Thank you, I ended up backing up the data and cache via USB, then did a flash of Cataclysm ROM. I'll let you know if it works.
Can I just restore the data ASAP after installation or do I need Google to finish restoring my backup first?
Edit: Well, restored data, stuck with the boot screen loop again, then goes to Android is upgrading... and shows it optimizing 10 apps, and back to the boot logo.
Did the phone boot without restoring data?
audit13 said:
Did the phone boot without restoring data?
Click to expand...
Click to collapse
No, I made sure it was completed.
Now Play Store keeps quitting when I try to install apps. I can only install specific ones.
I recommend flashing a stock rom to make sure there isn't a hardware problem. Don't restore anything until you are sure the phone works.
audit13 said:
I recommend flashing a stock rom to make sure there isn't a hardware problem. Don't restore anything until you are sure the phone works.
Click to expand...
Click to collapse
Alright, I was able to get all my apps installed besides United Airlines and can't update Chrome.
So the stock rom works fine?
audit13 said:
So the stock rom works fine?
Click to expand...
Click to collapse
Yes, thank you.
I don't think I want to do another custom ROM for now.
The stock rom is the best with the bloat taken out .I think the kernel can be improved though. I use EX