----
No solution found yet.
Possibly hard brick,since you flashed a rom that uses ext4 filesystem on a device that uses f2fs.
Sent from my Moto G using Tapatalk
---------- Post added at 02:11 AM ---------- Previous post was at 02:10 AM ----------
DeHuMaNiZeD said:
Possibly hard brick,since you flashed a rom that uses ext4 filesystem on a device that uses f2fs.
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
But,i dont know,maybie you could find a stock rom zip,and try to flash it from recovery?
Sent from my Moto G using Tapatalk
DeHuMaNiZeD said:
Possibly hard brick,since you flashed a rom that uses ext4 filesystem on a device that uses f2fs.
Sent from my Moto G using Tapatalk
---------- Post added at 02:11 AM ---------- Previous post was at 02:10 AM ----------
But,i dont know,maybie you could find a stock rom zip,and try to flash it from recovery?
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
I flashed stock recovery but I'm getting an android with a red exclamation point when I get to it... Any proper files to use?
Try flashing CWM and then try to flash
Sent from my Moto G using Tapatalk
DeHuMaNiZeD said:
Try flashing CWM and then try to flash
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
I tried that with no luck.
Basically the issue is http://forum.xda-developers.com/moto-g/help/recover-4-4-4-downgrade-brick-temporal-t2801946
And it seems that everyone who is trying to downgrade from 4.4.4 after a failed flash is experiencing it.
No resolution at the moment.
Our phones are bricked
Related
Hi,
Current Configuration:
Bootloader Unlocked,
Rooted
HBOOT 1.14
Rom: CleanRom 5.1
Since I"m on HBOOT 1.14, I understand I have to manually flash boot for each rom I flash; however, I can't seem to get any non-sense roms to work. The rom flashes with no issues, I flash boot of the new rom, boot, but once I get to the launcher, none of the of the apps seem to work. Please advise this NOOB. Much Appreciated!
http://forum.xda-developers.com/showthread.php?p=33303798
Sounds like adb might be having an issue? Check out the walkthrough.
There is another thread out there about flashing kernel via an apk. I'll see if I can locate for you
Sent from my One X using xda premium
---------- Post added at 09:43 AM ---------- Previous post was at 09:27 AM ----------
http://forum.xda-developers.com/showthread.php?p=33463262
Try this out.
Sent from my One X using xda premium
subarudroid said:
http://forum.xda-developers.com/showthread.php?p=33303798
Sounds like adb might be having an issue? Check out the walkthrough.
There is another thread out there about flashing kernel via an apk. I'll see if I can locate for you
Sent from my One X using xda premium
---------- Post added at 09:43 AM ---------- Previous post was at 09:27 AM ----------
http://forum.xda-developers.com/showthread.php?p=33463262
Try this out.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Thanks for the reply, after trying the steps once more, I'm still having same issues. Once I boot to CM10, I get a barrage of "Unfortunately, "Insert App Name" has stopped".... :crying:
ChummyDays said:
Try to wipe everything before flashing
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
this ^^
make sure that before flashing you wipe (at least) the cache and dalvik cache. if you are changing from sense to aosp or vice versa you will probably want to do a factory reset in twrp (not in the bootloader - this corrupts the sdcard).
Every rom ive tried, it stucks into bootlogo. How can i solve it? Thanks in advance.
It happened to me too. The only solution is to revert to stock JB, reinstall custom recovery, re-root and install custom rom.
Many moto g users had this problem...
Sent from my Desire S using xda app-developers app
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
And, just for curiosity, how did you solve your bootloop problem without using the VolDown key?
Sent from my Desire S using xda app-developers app
skorpionvenom said:
It happened to me too. The only solution is to revert to stock JB, reinstall custom recovery, re-root and install custom rom.
Many moto g users had this problem...
Sent from my Desire S using xda app-developers app
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
And, just for curiosity, how did you solve your bootloop problem without using the VolDown key?
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
thank you, I already flashed aosb =)
.....
lol, i didnt without... i just went to get fixed it after my last post in the other thread... this guy on the place i went only took him like 40mins to replace/fix it.
DualDark said:
thank you, I already flashed aosb =)
.....
lol, i didnt without... i just went to get fixed it after my last post in the other thread... this guy on the place i went only took him like 40mins to replace/fix it.
Click to expand...
Click to collapse
Did you flash recovery in JB? I have your problem right now, and I have reflashed stock JB, updated to KK, re-rooted, installed CWM and... bootloops again . Can it be the problem? Should I flash recovery in JB directly? And which recovery should I flash in stock JB, CWM for 4.3 bootloader? Thanks in advance
Im having the same problem, after I installed GPe. Gonna try going back to JB.
Enviado desde mi XT1032 mediante Tapatalk
Feyerabend said:
Did you flash recovery in JB? I have your problem right now, and I have reflashed stock JB, updated to KK, re-rooted, installed CWM and... bootloops again . Can it be the problem? Should I flash recovery in JB directly? And which recovery should I flash in stock JB, CWM for 4.3 bootloader? Thanks in advance
Click to expand...
Click to collapse
I don't have an idea what is exactly the problem. Regardless if I'm on JB or KK, I always flash recovery using the moto tool application. In order to install any aosp rom, I must to be in JB stock.
Enviado desde mi XT1032 mediante Tapatalk
Hey,
i own a german XT1032, updated to 4.4.2 the day i bought it.
I unlocked the bootloader, installed Philz Touch recovery ( CWM based) and rooted it.
But no matter which ROM i flash, it just stays at the bootanimation until i restore my backup.
I already tried different recoverys, including TWRP, different methods of wiping... all to no avail.
so... what am i missing ?
Any help would be appreciated.
After installing ROM try for clear the cache and data
Sent from my XT1033 using Tapatalk
---------- Post added at 03:32 AM ---------- Previous post was at 03:31 AM ----------
ajeetone said:
After installing ROM try for clear the cache and data in recovery
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Sent from my XT1033 using Tapatalk
Hey there,
I'm new here and really hope that people from this community would help me in my dilemma.
So I own a MTK6589 phone that runs JB 4.2. I've been waiting but it seems the manufacturer and others are not interested in making a 4.4 Kitkat ROM for my phone. So I tried to port a 4.4 ROM from other manufacturer's phone that has same specifications as mine and failed. After some reading I found out that you can't port a ROM if the OS installed in your phone is not same as the one you're porting, right?
So I want to ask if there's any way for me to get a 4.4.4 ROM in my phone which is running a 4.2 ROM?
Thanks
If the phone is rooted, you can flash CWM recovery or TWRP. And then try to flash this ROM.
http://click.xda-developers.com/api...oo.im/devs/chrmhoffmann/wiko...FBUGS-0.15.zip
Sent from my Moto G using XDA Premium 4 mobile app
DillonFixDroids said:
If the phone is rooted, you can flash CWM recovery or TWRP. And then try to flash this ROM.
http://click.xda-developers.com/api...oo.im/devs/chrmhoffmann/wiko...FBUGS-0.15.zip
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My phone's rooted and I tried this ROM modified for a clone device as mine, but it stuck at boot logo. Is it really true that you can't port a 4.4.4 ROM if your device is running a lower android like 4.2?
You should be able to flash whatever ROM that was made for your device. There may be some stock firmware you could flash to it. Do you know if it is a fastboot supported phone?
Sent from my Moto G running Carbon ROM 4.4.4
---------- Post added at 01:28 AM ---------- Previous post was at 01:07 AM ----------
And you said that CM11 Doesn't Work? If it was stuck at boot animation, go to CWM recovery and go to mounts and storage and wipe "/data" "/none" /cache" and then reboot. It worked for me.
Sent from my Moto G running Carbon ROM 4.4.4
DillonFixDroids said:
If the phone is rooted, you can flash CWM recovery or TWRP. And then try to flash this ROM.
http://click.xda-developers.com/api...oo.im/devs/chrmhoffmann/wiko...FBUGS-0.15.zip
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
DillonFixDroids said:
You should be able to flash whatever ROM that was made for your device. There may be some stock firmware you could flash to it. Do you know if it is a fastboot supported phone?
Sent from my Moto G running Carbon ROM 4.4.4
---------- Post added at 01:28 AM ---------- Previous post was at 01:07 AM ----------
And you said that CM11 Doesn't Work? If it was stuck at boot animation, go to CWM recovery and go to mounts and storage and wipe "/data" "/none" /cache" and then reboot. It worked for me.
Sent from my Moto G running Carbon ROM 4.4.4
Click to expand...
Click to collapse
Actually this ROM isn't made for device, its made for a device that has exact specs as mine but its from a different manufacturer. Yes is supports fastboot. And the new ROM is stuck at boot logo and not at boot animation. But I'll try what you suggested and post the results here. Thanks
What manufacture was your phone made by?
Sent from my Moto G running Carbon ROM 4.4.4
DillonFixDroids said:
What manufacture was your phone made by?
Sent from my Moto G running Carbon ROM 4.4.4
Click to expand...
Click to collapse
Celkon A119Q running on MT6589 1.2 Ghz
Did you try the steps? I didnt see any stock firmware for the divice.
Sent from my Moto G running Carbon ROM 4.4.4
---------- Post added at 03:37 AM ---------- Previous post was at 03:29 AM ----------
I have the link to download firmware for the device now.
https://drive.google.com/uc?export=download&confirm=yRuX&id=0Bw_oNhE1hof7QnN3TXJfOEtyNkU
I think that is the right firmware for your device.
Sent from my Moto G running Carbon ROM 4.4.4
DillonFixDroids said:
Did you try the steps? I didnt see any stock firmware for the divice.
Sent from my Moto G running Carbon ROM 4.4.4
---------- Post added at 03:37 AM ---------- Previous post was at 03:29 AM ----------
I have the link to download firmware for the device now.
https://drive.google.com/uc?export=download&confirm=yRuX&id=0Bw_oNhE1hof7QnN3TXJfOEtyNkU
I think that is the right firmware for your device.
Sent from my Moto G running Carbon ROM 4.4.4
Click to expand...
Click to collapse
Yes I tried what you suggested but unfortunately it didn't work. Trying the firmware you posted. Do you know how could I find mount points in my phone with root explorer? I kind of mixed the ones that I already had.
Sorry, I don't know.
Sent from my Moto G running Carbon ROM 4.4.4
DillonFixDroids said:
Sorry, I don't know.
Sent from my Moto G running Carbon ROM 4.4.4
Click to expand...
Click to collapse
K thanks anyway. I'll check the firmware and post back here.
Is their a recent guide how to root and flash a custom recovery on t-mobile lg g2 running lollipop so far all I seen are old tutorials any help would be appreciated thanks in advance
Bump... Would really love to see one
Sent from my LG-D801 using Tapatalk
---------- Post added 06-08-2015 at 12:12 AM ---------- Previous post was 05-08-2015 at 11:59 PM ----------
I would like someone to confirm, but from reading bits and pieces over XDA I think I understand how to root and install cm12.. So I'm on the updated stock lollipop. I understand that you can root with the one click program and install twrp through something like flashify. Once in recovery I need to flash the 20g bootstack and the JB bootloader, then I can proceed to flash cm12 and gapps...if that's right, someone please let me know.
Sent from my LG-D801 using Tapatalk