Hello, i previously recovered using xsball gingerbread guide, i thought id brave roms again and was using touch recovery that came with the guide. To help things a long i took backups and restored then when roms failed etc. this all went fine.
I thin thought, maybe its because im using touch that roms were failing so i installed non touch 5.0.2.0, took my backup and flashed my rom (CM10). This failed (bootloop) so i tried to restore my backup. CM repotred that the backup was successfull but now when i reboot im stuck at LG logo with all of the lights on and nothing happening.
I can get back into CWM can anyone suggest ANYTHING?
Maybe if someone could upload the same version of CWM touch that came with the GB guide i could flash that via CWM non-touch somehow?
can someone suggest ANYTHING to get my phoen to work again
Thanks (Desperate)
Related
I upgraded manually to 4.04 coming from 4.03 rooted, i flashed the update file and then flashed Superuser, everything is working fine.
Today i wanted to make a backup with the rommanager, but it seems that the Clockworkmodrecovery isnt there anymore, when i tried to flash clockworkmodrecoveryin standard recovery i get the Signature verification fail and then the android with the exclamation mark.
For the rest the phone works fine. i am confused now, what to do
i have backups of my olders system, from a few days ago, but can i use rommanger to set things back or does that not work anymore because the clockworkmod recovery is missing now.
How can i get back clockworkmod recovery
is this working for you: http://andwise.net/?p=268 ?
No it does not work .
what does not work exactly ??
there is an missing dll in your fastboot exe,
pulled the battery and flashed thru rommanager, then its ok, recovery is there but when i want to make a backup, clockworkmod recovery is gone again after reboot, not sticky i think
Rename "/system/etc/install-recovery.sh" to "/system/etc/install-recovery.sh.bak". All Stock ROMs replace the recovery on each Boot if it isn't the stock one. Renaming this script stops that. After you do this, flash CWM one more time and it'll stick.
Ok thanks, i am just back to 4.03 using a nandroid backup, when i am going back to 4.04 i will try your solution
I WENT TO FLASH PACMAN AND I FLASHED IT AND WENT AOK, BUT I FORGOT TO FLASH GAPPS I READ A FEW PLACES THAT YOU CANNOT FLASH GAPPS AFTER YOU FLASH THE ROM. SO I WENT TO RESTORE MY BACKUP. WEN IT RESTORED I WAS STUCK IN BOOT LOOP ON THE HTC ONE SCREEN. I READ A FEW OTHER PLACES AND I THEN TRIED TO FLASH
---CM10
SICK KERNELJB
AND GAPPS ]
AND THAT WAS STUCK IN BOOT LOOP TO. IVE ERASED EVERYTHING AND TRIED RESTORING AGAIN. I DONT KNOW WHAT ELSE TO DO. I CAN STILL BOOT INTO FASTBOOT, AND RECOVERY (USING TWERP 2.3 AS RECOVERY) PLEASE HELP ME what DO I DO
No need for all caps, bro, makes it harder for people to read.
Do you have a nandroid backup from before all this happened or something ?
Pennycake said:
No need for all caps, bro, makes it harder for people to read.
Do you have a nandroid backup from before all this happened or something ?
Click to expand...
Click to collapse
Ya i kno (bout the caps) the button was stuck where i was at. Yea i did hava a back up, but ended up figureing it out last night. i eneded up flashing (fastboot) CDMA STOCK Kernal and all was well. I have reflashed it and works fine. but got one more ? (im just learning the android side of developing but is flashing the kernel optional with new roms or with certain roms you have to flash it, and if i ened up resoting after i flash a kernel so i need to flash back to the kernel i was using before.
Hi there!
Few days back I had a problem of low internal memory. I posted the problem, got some responses, then followed cute prince's Nandroid restoring tutorial. Flashed the latest Cm9, all was working fine. Then again needed a change (I'm kinda flashaholic ), wiped / reset my phone thru TWRP recovery (whatever is the procedure) and was unable to flash any single rom onwards. Tried to flash stock rom, even tried to restore my 6 months old cwm recoveries, but nothing boots up. I also tried to flash boot.img thru fastboot and flash the rom consequently but it too didn't work.
Now, I have no rom on my explorer except getting to bootloader, fastboot, TWRP or Clockworkmod recoveries. I can't do the nandroid restore as told by cute prince, now.
So I would have to post again here in the forum for the above problem. Here, what I need is to find out about what went wrong actually and what is the solution to the problem!! I hope am not talking about bricking the phone or something.
An urgent reply is highly appreciated, please
Regards.
vikingmax said:
Hi there!
Few days back I had a problem of low internal memory. I posted the problem, got some responses, then followed cute prince's Nandroid restoring tutorial. Flashed the latest Cm9, all was working fine. Then again needed a change (I'm kinda flashaholic ), wiped / reset my phone thru TWRP recovery (whatever is the procedure) and was unable to flash any single rom onwards. Tried to flash stock rom, even tried to restore my 6 months old cwm recoveries, but nothing boots up. I also tried to flash boot.img thru fastboot and flash the rom consequently but it too didn't work.
Now, I have no rom on my explorer except getting to bootloader, fastboot, TWRP or Clockworkmod recoveries. I can't do the nandroid restore as told by cute prince, now.
So I would have to post again here in the forum for the above problem. Here, what I need is to find out about what went wrong actually and what is the solution to the problem!! I hope am not talking about bricking the phone or something.
An urgent reply is highly appreciated, please
Regards.
Click to expand...
Click to collapse
change TWRP to cwm and then flash your cwm recoveries...........search xda how to install cwm over twrp...........
Hit thanks if i help
i had the same problem too.....i was using the twrp because its touch...but i think its not as good as cwm.....install cwm and then yannou's recovery .....you can find it in index thread...yannou is best ...im using it for four months ...no problem till now....
Burnt Nand?
Come here
http://forum.xda-developers.com/showthread.php?t=2183130
Sent from my HTC Explorer A310e using xda premium
CWM 6.0.1.0. is installing roms fine, but I can't get it to backup and restore properly (making it extremely irritating to try new roms I may not like). So I installed TWRP via EZ Recovery recently, and for the life of me, I can not get it to install any rom, but it will backup and restore perfectly. What am I doing wrong? I've been flashing roms since the Droid X days and I'm stuck trying to wrap my head around this. Thanks for any help
rruready said:
CWM 6.0.1.0. is installing roms fine, but I can't get it to backup and restore properly (making it extremely irritating to try new roms I may not like). So I installed TWRP via EZ Recovery recently, and for the life of me, I can not get it to install any rom, but it will backup and restore perfectly. What am I doing wrong? I've been flashing roms since the Droid X days and I'm stuck trying to wrap my head around this. Thanks for any help
Click to expand...
Click to collapse
I would try to reinstall the twrp recovery using the goo.im app to make sure you get the latest version 2.5.0.0
I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk
A lot of users report issues not being able to flash rom's on 4.4.2 kitkat.
A fix is to downgrade to 4.3, then flash roms.
I dont know why. I bought my device upgraded to 4.4.2 already, and i can flash roms with no issues.
Search the forum for the topic and you will find the info you need.
Roshi69 said:
I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It wont backup saying what error?
Twrp just said 'failed' in red writing after the data backup I think. And philz touch said something along the lines of Not being able to write a file into the \clockworkmod folder.
I bought the device with 4.4.2 on it and followed the guides after reading up about the problems etc but TWRP 2.7.0.0 had a lot of reports that everything was working on it so went ahead with it
Sent from my Nexus 5 using Tapatalk
Ya that's strange because philz works great for me. Do you have a USB otg to try an external backup?
Sent from my XT1032 using Tapatalk
I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
Roshi69 said:
I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
Click to expand...
Click to collapse
Why dont you use Clockwork mod recovery for flashing Rom. I have flashed 10 Roms with that and all are backed up with out any problems. TWRP has no official support for moto g, and instead of all that why don't you try Cyanogenmod ?
(sorry if my english is not perfect)
Hello,
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
I never had such problems on my Nexus..
Please help me, I don't know what's going on
TheSkweed said:
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
Click to expand...
Click to collapse
Same here. It may be possible to downgrade to 4.3 (see here), but would it then be possible to flash a 4.4.2-based custom ROM ? I'm not sure.
Heres the steps I took.
*******Before device was stuck at bootloop*******
1. Bought phone (XT1032)
2. unlocked boot loader
3. Rooted
4. Flashed Philz Recovery (wouldn't backup rom)
5. Flashed TWRP and CWM with same issue.
6. Flashed 2 ROMs to try it (TweakyOne + C-Rom, Both wouldn't boot. and tried on all recoveries.
********Steps after being stuck at bootloop*******
1. Followed this amazing guide here (https://www.youtube.com/watch?v=laU6NQ0LxR0)
2. Set up the stock ROM again
3. Flashed TWRP 2.7.0.0 via Fastboot
4. Backup worked successfully
5. installed CM11 and setup successfully
6. installed Lego rom just to assure myself (currently running this ROM)
I know this is no solution at all but just wanted to share my steps to see what maybe fixed my phone. possibly the stock 4.2.2 rom I flashed was the solution. Maybe the original factory ROM that came on the phone was the issue?