So hello, i've got a D806, and installed CloudyG3 1.3 ROM and it worked like a charm.
So i went further and started tweaking this ROM and adding stuff, and reached the point where i wanted to place the G3's Keyboard due to its resize function. I ended founding Cloudyfa's G3 Ported Keyboard and i supposed it would work perfectly (Being both ROM and Keyboard from same developer), Yet, i went for the APK installation and opened it.
1- Loads up and shows my model (D806) perfectly
2- Backup current
3- Install New & Reboot
When i rebooted, the home wouldnt stop crashing (And therefore not starting up), and i managed to open the recent-apps window, wich resulted in the systemui crashing, and rebooting the phone. It ended up breaking the ROM (The phone never booted totally, it just kept with the LG startup icon moving endlessly) and i had to go into TWRP and Re-flash the ROM to fix back up everything. (When i could load up again the keyboard screen sensor was not good and i couldnt touch the bottom keys, so i restored the backup i did and it worked great back again).
I wanted this keyboard and i certainly dont want to go back throught all the steps of re-customizing my ROM back, so how can i make this with no risks (or the least possible)?
Geetz
HyPeXeLeD said:
So hello, i've got a D806, and installed CloudyG3 1.3 ROM and it worked like a charm.
So i went further and started tweaking this ROM and adding stuff, and reached the point where i wanted to place the G3's Keyboard due to its resize function. I ended founding Cloudyfa's G3 Ported Keyboard and i supposed it would work perfectly (Being both ROM and Keyboard from same developer), Yet, i went for the APK installation and opened it.
1- Loads up and shows my model (D806) perfectly
2- Backup current
3- Install New & Reboot
When i rebooted, the home wouldnt stop crashing (And therefore not starting up), and i managed to open the recent-apps window, wich resulted in the systemui crashing, and rebooting the phone. It ended up breaking the ROM (The phone never booted totally, it just kept with the LG startup icon moving endlessly) and i had to go into TWRP and Re-flash the ROM to fix back up everything. (When i could load up again the keyboard screen sensor was not good and i couldnt touch the bottom keys, so i restored the backup i did and it worked great back again).
I wanted this keyboard and i certainly dont want to go back throught all the steps of re-customizing my ROM back, so how can i make this with no risks (or the least possible)?
Geetz
Click to expand...
Click to collapse
have you tried manually installing the files as suggested in the keyboard mod thread?
you have a backup so no harm in trying right?
Yeah ive got the backups.. i will try it when i feel ready to spend hours tweaking my phone again... (or i will backup 100% with twrp)
Yeah it's a pain when getting one thing to work means redoing everything else.
Best of luck.
Related
Hi all,
I'm having a little problem. I have researched but everything I've found leads me back to square one...
So I followed this guide to installing CM7 on my M2. Please note that I have in the past successfully rooted my phone, installed the Argenstone ROM and one other basic Great Britain Rom. So I'm not a total nub. However at this stage I have a phone that's is useless to me...
My phone is rooted. I have Droid2Bootstapper installed and I managed to get the CWM 3.X installed. I downloaded the all-in-one.zip file from the CM7 ROM thread (the zip is actually called EndlessCM7-110901-nightly_build.zip - hope that's not an issue?)
I booted into CWM and applied the EndlessCM7-110901-nightly_build.zip and after (without a reboot) wiped everything (I had backed it up previously).
I rebooted the phone and...well I get the Google logo with the Motorola M and the Cyanogen bot as the 2 'O' characters. Then after a while a 3D rotating 'square' and the android writing and logo 'shimmering' in and out but that just goes on forever. I left it for an hour at one point and just gave up.
Now I can't even get past the Google logo. I've tried restoring my previous back up but that won't work either. I can't boot into the OS to actually use RSD lite to flash a known working ROM over the top.
When the LED turns blue and I hit the volume key it displays "Android BootMenu <v1.0.3>" which is different to the CWM 3.X that I was getting prior to applying the EndlessCM7-110901-nightly_build.zip file.
From here I can select to recover the last 'latest recovery' which when done loads into CWM-based Recovery v4.0.1.6-defy.
Basically I'm at this point where I seem to be able to load just about every boot menu under the sun and do everything but actually launch the damn OS.
How can I get out of this hole? Preferably I'd like to get everything back to the stock ROM the phone came with so that I can start from scratch again.
Any bodies help would be more than appreciated.
Cheers,
- Matt
EDIT: I have even used CWM 4.X+ to try and restore the Argenstone ROM. it goes through the whole process of checking the MD5 sums, restoring the system and boot images etc and seems to work without any issues. I then wipe all data and reboot. Nothing - still the same cyanogen Google logo and the only thing I can do is boot into all the CWM menus.
*sigh*
Argh feel like a true idiot now. It took me about an hour of searching earlier but I've only just found/remembered how to get RSD lite to see my phone (pwr+volume+camera) and I'm wiping the whole thing to the factory (vodafone) ROM. Might take the opportunity to take it to Vodafone and tell them it never gets a damn 3G connection lol...provided this flash works (touch wood).
My wonderful wife gave me an Acer a500 for Christmas. Awesome gift. I had rooted it immediately with no problems, since all of my phones and families phone are rooted, it just seemed to be the natural thing to do.
As someone that "plays" with their android a lot I did all of the backups. Well, the time came to have my tablet "approved" for use at my company and also have the appropriate "encryption" software and keys added. Just as a precaution I decided to restore the original backup and unroot the tab.
All was going well until I received the update message. I went ahead and downloaded the update and ran it. During the install process it froze. I thought it was just busy so I left it for a good 20 minutes and finally realized it was frozen. I rebooted and it went through a couple of reboots and finally settled on the lock screen. But now I find the touch screen unresponsive.
I plugged in a mouse and keyboard in hopes that I could get back into it and start over, but, although, the mouse shows up, it is jumpy sluggish and will not grab the lock to slide open and eventually freezes.
I have tried all of the "update.zip" files I could find and they all fail at one point or another.
ADB allows me to explore in shell but since I unrooted, I cannot get su privileges.
Acer is of course, useless and the vendor it was purchased from is worthless.
I have been through every thread I could find and tried every trick I could come up with. Now I'm just stuck.
Any help is appreciated
I've had this a couple of times already. Usually just turning the screen off and on a couple of times does the job (the issue seems to be with the driver, also on various custom roms). Just try it after each off-on cycle, most of the time it takes no more than two or three tries, though there are exceptions.
Thanks, but it has been rebooted many many times since it's demise.
Decided to skip sleep tonight and keep plugging away.
I found an update.zip recovery file for an a501. Figured I can't do much worse so I went ahead and ran it.
It froze at about 95% but.........
Good News:
The tablet is responsive and touch panel works again.
Bad News:
It boots straight into system settings and although you can open the settings menu, nothing actually launches.
Decided to try all of the old update.zips and still everything fails.
No more ADB response.
When you originally unrooted your device did you revert back to the stock recovery or did you leave cwm on your device?? If you left cwm on your device that may be the problem with the update.zips and OTAs.
You are sooo right. I've never gone back to a stock rom before and I completely forgot about reverting to the stock recovery.
As a matter of fact, I was on Civato's Flexstriker 3.2.1 rom with the new CWM before I reverted back to the stock rom.
Well, at least we've determined my stupid mistake, but now the question lies: "How do I get back to any working rom?"
Here's an update. I did find an update.zip file that also begins to load but does not finish. It stops at 95% still.
I will attach the photos in case someone notices something otherwise I am at a loss. In addition to all of the above, I tried everything I could to get into APX mode but nothing. I am willing to try almost anything at this point, so all suggestions are appreciated.
Something I noticed was the recovery for the a501 was android with gears spinning in the body. The recovery I have now is a package with an arrow. The recoveries are different. The current update file is Acer_A500_1.145.05_COM_GEN1
So this brings me to a question: Can I put Thor's 1.6 CWM back on the a500 and at least work from there? I do have my original backups and thought I might be able to get somewhere that way.
Hi Guys!
Sorry, I couldnt find any problem similar to mine regarding note 3.
Device: N900W8 Canadian (Rogers)
TLDR: After flashing a rom a second time (First time was perfect) phone says its in factory mode and now stock lockscreen doesnt work at all no matter what settings. In factory mode wifi is one of the settings it says isnt suppose to work but it does work, and Im extra confused.
Steps leading to the problem:
- Rooted using cf auto root
- twrp to backup entire stock rooted rom
- flashed Darthstalker v6
- phone works flawlessly, except with gps issues which I suspected was not a rom issue
- decided to test it out anyways, tried to restore my stock rooted backup but for some reason failed (Honestly have no idea why)
- flashed Darthstalker v6 again, complete clean install to see if GPS fixes itself
Phone now boots up normally, but on first boot up it showed a short popup that disappears shortly saying something like this
"Factory mode is ON, in this mode some settings such as wifi may not work blah blah blah"
Thing is, it does work, so far the only difference that I see from this mode is that I cant have a lock screen no matter what setting I put on it. Right now forced to use an alternative lockscreen (Go locker).
Just flashed Jedi Elite v5 yesterday, same issue as above, but everything else is working fine...
Thanks for the help guys!
I suspect it is and EFS thing, but I dont know what that is.
I used root explorer to look in the folder and nothing seems to be inside (Even when selecting to view hidden files and folders)
Unfortunately since my original stock root backup did not work I have no way of restoring the original. If you think this is the issue can someone point me in the right direction to get my EFS folder proper? Currently I only see Backup/restore options. Not the full EFS folder that I think I might need.
Two more things I noticed
- 4 way reboot doesnt work, it just turns off the phone
- when playing youtube "An error occurred" appears for maybe 10 seconds and disappears. Video is playing in the background so its pretty annoying.
Download this file by firasusman and flash thru recovery. Don't know if the lockscreen will come back but if it doesn't reinstall whichever rom you have right now to fix the broken file.
So i got my g2 to get somehow the JB buttons back (im using cloudyG3 btw)
Did this with G2 Xposed.
But i could not edit the menu and back keys position, so i unistalled it. But buttons are still same and kitkat aint back... and app crashes when going into frontal buttons on settings...
So far tried to replace them again in the way i want, but gravitybox isnt doing anything either...
i want back button on the right and menu button on the left...( Samsung way)
Any help on fixing this buttons would be highly apreciated, as having them reverse is terribly annoying.
If anyone need any more details on my phone, please ask.
Greetz
PD: Got nandroid backup, tried restoring only system (dont wanna go 1 week back in stufd) but no results.
Hello. I sort of had this issue yesterday, and the reason why it happened for me, was that my phone didn't wipe EVERYTHING as it was supposed to do when I wiped data+system+cache+dalvik, it just counted CloudyG3 as an "upgrade". That unfortunately means that your CloudyG3 was dirty flashed and that's why it doesn't work.
What I would recommend you to do is to backup all your apps only, and return to stock. then towelroot+autorec and start all over again.
I did something else, but I wouldn't recommend it since my phone stuck at bootlogo and kept turning itself on. I formatted Data in TWRP (which means internal storage too, don't do this unless you REALLY can't get out), and tried pushing a ROM through ADB (which didn't work because my adb wasn't properly installed), but then restored to stock through download mode.
I bought an Lg G2 d802 from aliexpress, the phone came rooted and with Philz touch installed.
A few days ago i decided to install a custom Rom (liquidsmooth but i don't think it's relevant), after i did the steps to install the custom rom when i rebooted the phone , on the screen appeard that error (690) fastboot has started.
I couldn't do anything so i decided to restore stock firmware, i thought the first version i installed wasn't the right one because the touchscreen was not working properly so i tried different one but still the same behavior.
Everything else on the phone seems to work but i can't write. I can't select anything the normal way , but i found a pattern to do things.
Basically when i place my finger on o part of the screen it actually senses the touch on another part of the screen.
Any thoughts on how this can be fixed ?