Q&A for I flashed LCA43.
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for I flashed LCA43.. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Visegrad said:
Yeah, it's weird. It's like I've lost recovery. I have flashed back to stock, locked the bootloader and try to go to recovery, dead android. unlocked bootloader, try to go to recovery from bootloader... dead android. I have used the restore tool to push recovery image on, everything says it went fine, try any method to get to recovery...dead android. I was able to flash the Mysterious Magic rom back on via his script with no issues, so not sure where the disconnect is, but for now I will stick with the rom since the battery life is great with that.
Click to expand...
Click to collapse
Once you have the OTA zip downloaded, reboot your watch into its recovery. To do this, run the command “adb reboot recovery”. Once you see the green Android with the red warning symbol, tap the screen. A menu will appear on the screen from which you can select an item by swiping up or down on the touchscreen. Swipe right when you’ve highlighted “apply update from ADB.”
When I first got to the screen with the green Android and the red warning symbol, tapping the screen did nothing. So I held down the reset the button on the back of the watch until the watch turned off (about 10 seconds). I then placed the watch on the charger to wake it up, once on the LG start screen tap the upper left and lower right corner to get into the bootloader menu. Select boot recovery and now you should be able to see the menu when you tap the screen with the green Android and red warning symbol.
I've tried everything with no luck, LCA43 doesn't want to be installed on my watch.
I got the OTA, but when I press install it start installing until more or less the middle of the progress bar and then I get a dead android. I downloaded the OTA to do a sideload but it gets aborted at 61%. I formatted all the partitions and flashed the official images of LDZ22D, then tried both methods, with the same result.
Does anyone have the link to the official img? Because the OTA doesn't seem to work for me.
Sent from my Nexus 4 using XDA Free mobile app
JanusDC said:
I've tried everything with no luck, LCA43 doesn't want to be installed on my watch.
I got the OTA, but when I press install it start installing until more or less the middle of the progress bar and then I get a dead android. I downloaded the OTA to do a sideload but it gets aborted at 61%. I formatted all the partitions and flashed the official images of LDZ22D, then tried both methods, with the same result.
Does anyone have the link to the official img? Because the OTA doesn't seem to work for me.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Getting exact same error.
edit:
Got it past 61%
I used the images in
http://rootjunkysdl.com/?device=LG G Watch&folder=G Watch Script Tool
instead
Related
I reflashed my gtablet with NVflash, the three birds comes up then the tap n tap animation comes up then disappears and it does this about 10 times then goes black. I did the volume + & power button, I get a triangle.
after looking through the forums I came to the conclusion the I needed to install CWM. I installed CWM3028.1.2micro it and the triangle was replaced with a unpacking box. It rebooted and the on and off of the Tap Ntap screen started again (this time only 4 times)
I am at a loss of what to try next, any suggestions?
Thanks
Search the forums before posting next time. Your answer is here about 100 times.
Google search "G Tablet for Dummies" and READ, READ, READ
go to the start here section. I believe that you are a code red, if memory serves me right.
Why were you NVFlashing? Were you already in a soft brick? Read the page on NVFlashing, read the page on CWM, READ, READ, READ....then post
Shadowrunner63 said:
I reflashed my gtablet with NVflash, the three birds comes up then the tap n tap animation comes up then disappears and it does this about 10 times then goes black. I did the volume + & power button, I get a triangle.
after looking through the forums I came to the conclusion the I needed to install CWM. I installed CWM3028.1.2micro it and the triangle was replaced with a unpacking box. It rebooted and the on and off of the Tap Ntap screen started again (this time only 4 times)
I am at a loss of what to try next, any suggestions?
Thanks
Click to expand...
Click to collapse
My signature. Go to start here page. You're a code red.
What you did was you didn't erase data from the previous rom. The left over data is interfering with your boot up process. What's worse, you might have installed the wrong branch of development.
try at your own risk
Shadowrunner63 said:
I reflashed my gtablet with NVflash, the three birds comes up then the tap n tap animation comes up then disappears and it does this about 10 times then goes black. I did the volume + & power button, I get a triangle.
after looking through the forums I came to the conclusion the I needed to install CWM. I installed CWM3028.1.2micro it and the triangle was replaced with a unpacking box. It rebooted and the on and off of the Tap Ntap screen started again (this time only 4 times)
I am at a loss of what to try next, any suggestions?
Thanks
Click to expand...
Click to collapse
(I am from medico line i donot have any IT knowledge, what all i have learnt is from this forum from the awesome DEVs here. If I make any mistake in my instructions then please rectify it, and I am sorry about it in advance. These instructions are according to my experience so please use at your own risk, for any doubt read, read,read the forum)
I was in same scenario after my gtab started to bootloop suddenly one day. i was using bos alpha 6. Its an awesome ROM, i think some of my apps backed up by titanium messed up......... how i sorted out this problem is as follows.
As i said i was on bos i.e 1.2 rom so when i nvflashed (to the initial 3588 stock rom) i went to 1.1 with lot of data from previous rom still there in the memory interfering with the booting process. So i used the the compatible CMW i.e the old one bekits version (CMW v08). I booted in to CMW and did my all factory reset and wipes. (Donot use the newer cmw the one meant for 1.2 bootloaders.) After all wipes i rebooted and was stuck in gtab logo. Since i have cleared all the data, so i Nvflashed again and every thing went fine from there. Now if you want to again use 1.2 loader roms then install 4349 stock rom to get bootloader 1.2 on your gtab.
hope it helps thankyou
Hello.
Yesterday ATT finally rolled out the new update, but for me it freezes with screen where android with explanation mark in triangle.
A day before I did successfully install [PUDDING] International House of Pudding! (Unlock/root thread) Updated July 23 2011 v2.3.4 and also [Unlocked Only][Release]CWM Recovery Mod for Atrix 4G 2011-06-30 updated again!
After that I reverted to stock v1.2.6 and gradually upgraded to v1.8.3
On top of that the android recovery doesn't work either with vol down on reboot, same explanation mark in a triangle...
Any ideas what could be wrong?
Thank you.
PS. sorry
[email protected] said:
Hello.
Yesterday ATT finally rolled out the new update, but for me it freezes with screen where android with explanation mark in triangle.
A day before I did successfully install [PUDDING] International House of Pudding! (Unlock/root thread) Updated July 23 2011 v2.3.4 and also [Unlocked Only][Release]CWM Recovery Mod for Atrix 4G 2011-06-30 updated again!
After that I reverted to stock v1.2.6 and gradually upgraded to v1.8.3
On top of that the android recovery doesn't work either with vol down on reboot, same explanation mark in a triangle...
Any ideas what could be wrong?
Thank you.
PS. sorry
Click to expand...
Click to collapse
Hey [email protected],
There is no problem with your recovery menu. When you see the Android with the exclamation mark, you are in recovery mode. just touch the screen right above the Search button, which turns out to be the "Hide" function, and you'll see everything show up! Neat-o, right? =] Too bad CWM isn't touchscreen-capable =[
What probably happened for you is that you failed the pre-test. When they install an OTA update, it looks to make sure that certain apps are still there and makes sure no illegal mods are added to your Atrix. If you remove bloatware using Titanium or have root or you modded system files, you'll run into an error trying to update because you failed the pre-test. The best way around that problem AND the solution to upgrading without deleting anything is here. Use the Automated Update for PC Users, which will bypass this check. This was made for the sole purpose of those who don't want to lose their data, however, you'll be more likely to encounter strange bugs if you do upgrade this way. I suggest backing up your SD card before you do anything, perform this update, and then do a factory wipe. I know it's annoying because you have to re-input all of your info and stuff, but this is pretty much the only guaranteed way that about 95% of it will function as it should.
Hope that helped =D
~jojojohnson7410~
jojojohnson7410 said:
Hey [email protected],
There is no problem with your recovery menu. When you see the Android with the exclamation mark, you are in recovery mode. just touch the screen right above the Search button, which turns out to be the "Hide" function, and you'll see everything show up! Neat-o, right? =] Too bad CWM isn't touchscreen-capable =[
What probably happened for you is that you failed the pre-test. When they install an OTA update, it looks to make sure that certain apps are still there and makes sure no illegal mods are added to your Atrix. If you remove bloatware using Titanium or have root or you modded system files, you'll run into an error trying to update because you failed the pre-test. The best way around that problem AND the solution to upgrading without deleting anything is Use the Automated Update for PC Users, which will bypass this check. This was made for the sole purpose of those who don't want to lose their data, however, you'll be more likely to encounter strange bugs if you do upgrade this way. I suggest backing up your SD card before you do anything, perform this update, and then do a factory wipe. I know it's annoying because you have to re-input all of your info and stuff, but this is pretty much the only guaranteed way that about 95% of it will function as it should.
Hope that helped =D
~jojojohnson7410~
Click to expand...
Click to collapse
When I touched the screen above the search button, I see the source of the error is "/system/app/swype.apk
so I imagine it is due to updating swype cuple of times and as far as I remember, in the first update i had to remove 2 system files to make it work.
This will help fix your issue.
1. Download the Motorola Drivers HERE if you haven't already, and install. (Link is to the 4.9.0 version, there is a newer one, but someone has said it has issues) If you would like to try the latest version, you can obtain them directly from Motorola Here.
2. Download RSDlite 5.3.1 HERE and install
3. Download the AT&T/Motorola 4.1.83 FULL SBF from this thread, unzip it and place it in a folder at C:\AtrixSBF\ (or something similar, short folder name, in the C:\ directory)
4. Plug your phone into a Rear USB port on your PC, using the OEM supplied USB cable. Set your USB option from the pull down Notification bar to None. ***For those that can't boot, power down, hold Volume Up while powering on. You should end up in Starting RSD protocol. Then continue. ***
5. Open RSDlite, wait until it recognizes you phone is attached.
6. Click on the "..." button and navigate to the SBF file you downloaded and select it.
7. Click the Start button and wait. It's good to stick around to make sure there are no errors, but it's going to take a good 20-40 minutes. DO NOT DISCONNECT anything until you see PASS next to the process you're running in the far right hand column.
Eddie Bombay said:
This will help fix your issue.
1. Download the Motorola Drivers HERE if you haven't already, and install. (Link is to the 4.9.0 version, there is a newer one, but someone has said it has issues) If you would like to try the latest version, you can obtain them directly from Motorola Here.
2. Download RSDlite 5.3.1 HERE and install
3. Download the AT&T/Motorola 4.1.83 FULL SBF from this thread, unzip it and place it in a folder at C:\AtrixSBF\ (or something similar, short folder name, in the C:\ directory)
4. Plug your phone into a Rear USB port on your PC, using the OEM supplied USB cable. Set your USB option from the pull down Notification bar to None. ***For those that can't boot, power down, hold Volume Up while powering on. You should end up in Starting RSD protocol. Then continue. ***
5. Open RSDlite, wait until it recognizes you phone is attached.
6. Click on the "..." button and navigate to the SBF file you downloaded and select it.
7. Click the Start button and wait. It's good to stick around to make sure there are no errors, but it's going to take a good 20-40 minutes. DO NOT DISCONNECT anything until you see PASS next to the process you're running in the far right hand column.
Click to expand...
Click to collapse
This did it for me. Left the SD card update on my SD card and as soon as it rebooted to clean 183 it found the update and installed it!
Thanks
Hi guys, newbie here. I've been an Android user for a while now, but never needed to post because I didn't feel like I could contribute with my very limited knowledge. It's unfortunate that my first post has to be a plea for help, but I've no other choice. :crying:
I was trying to revert my unlocked TF201 back to an official Asus ROM from the current Cyanogenmod ROM, and successfully flashed it using TWRP. (Went into TWRP > Install > Selected the ROM > Success! > Reboot). My TF201 tablet now gets past the initial boot phase (where it says device is unlocked on the top left and Powered by Nvidia on the bottom right), but once it gets to the next screen with the Asus logo and the YouTube loading sign (the spinning circular thing), it halts. The YouTube loading sign-looking thing is spinning, but it doesn't really go anywhere.
If it's of any help, I am able to power it off and restart the tablet.
androidbrownie said:
Hi guys, newbie here. I've been an Android user for a while now, but never needed to post because I didn't feel like I could contribute with my very limited knowledge. It's unfortunate that my first post has to be a plea for help, but I've no other choice. :crying:
I was trying to revert my unlocked TF201 back to an official Asus ROM from the current Cyanogenmod ROM, and successfully flashed it using TWRP. (Went into TWRP > Install > Selected the ROM > Success! > Reboot). My TF201 tablet now gets past the initial boot phase (where it says device is unlocked on the top left and Powered by Nvidia on the bottom right), but once it gets to the next screen with the Asus logo and the YouTube loading sign (the spinning circular thing), it halts. The YouTube loading sign-looking thing is spinning, but it doesn't really go anywhere.
If it's of any help, I am able to power it off and restart the tablet.
Click to expand...
Click to collapse
what version of twrp?
whycali said:
what version of twrp?
Click to expand...
Click to collapse
I wish I could tell you, but I don't know. I received this tablet a few days ago as part of a trade. TWRP is no longer on there anymore, and the RCP(?) thing, the recovery kernel, has an Android w/ an exclamation mark whenever I select it.
androidbrownie said:
I wish I could tell you, but I don't know. I received this tablet a few days ago as part of a trade. TWRP is no longer on there anymore, and the RCP(?) thing, the recovery kernel, has an Android w/ an exclamation mark whenever I select it.
Click to expand...
Click to collapse
Hold down power and volume down the same time until the machine restarts. Keep holding them down until you get the icons on screen (rck, wipe, usb etc). Look up the top left and there is a load of writing. At the end of the long line with bootloader in it is a number that's starts with either 9 or 10. What is it?
I managed to get it to boot into the Asus official ROM somehow. I selected something from the pwr+vol down option and it booted up fine. It was originally in Chinese though, but fortunately I knew my way around Android well enough to change the language.
Case closed, thanks for all the help!
Q&A for Cubot GT99 general thread
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Cubot GT99 general thread. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hey guys, please help,
For 2 days now, i've been having some problems with my cubot GT99. A month ago there were times when i found the phone black and needed to press power button 10 sec to turn it back on.
One day it decided to die on me, just went black. I couldn't turn it on, no matter what i tried. I decided reflashed the stock rom using the Flash Tool method. I installed the rom without the SIM card in the phone. After turning it on the first time and checking everything is fine, i turned it off to insert the sim card and sadly it wouldn't turn back on. Took out the sim card and still nothing. I reflashed again but this time decided to let the phone charge over night, so after the first boot i left it charging and went to sleep.
In the morning the blue front led was on indicating charging status but the phone was dead black screen, locked. Held power button 10 seconds. Battery did not charge. Plugged usb out then back in. The phone restarted the moment i plugged the USB cord back. It bricked the phone, stuck at cubot loading screen.
I'm out of ideas....maybe i have an IMEI NVRAM problem?
Inverted boot logo and animations
For anyone who dislikes the white boot logo and boot and shutdown animations i inverted the logo and animations. So now the background is black and the text is white. I did change:
logo.bin
boot_logo
bootanimation.zip
shutanimation.zip
All in a convenient flashable zip file. Please hit THANKS if you use these.
Click to expand...
Click to collapse
Hi brillemans,
thank you for the boot logos, better than default ones. Could I use they in my custom rom?
GT99 Amazon App login issue
Noticed this issue was posted a while back but no one appeared to reply with the same experience.
Well I have the same experience and don't seem to be able to overcome it.
The only way I have found to use the full Amazon experience is to access the Amazon site via Chrome and then request the desktop site, I can then login and access my cart, wish list etc.
Nothing else gives me access to my account.
colossus s5 rom soft button vibrates
hello,
now that i have changed my rom to collossus 5 most things work great.
but i do not like vibrating when i touch the home or back button.
how can i fix that?
greetings
I flashed LCA43 with adb sideload eefea3292b364b67db746dc4131713605b8e8f76.signed-platina-LCA43-from-LDZ22D.eefea329.zip and everything wents very well.
Now I am in tests and tomorrow I leave a feed-back of the new version.
Thanks.
I download Bits Watch Face from Play Store and I am testing with the new Android Wear LCA43.
For first impression Bits Watch Face is awsome, I like it, very cool.
What was your flash-process?
Unlocked/locked Bootloader? Stock Firmware?
My adb sideload command always breaks things at 61% with an "Installation Aborted" (Error 7) when it is verifying the Image.
Thanks for your help
My flash process is adb sideload eefea3292b364b67db746dc4131713605b8e8f76.signed-platina-LCA43-from-LDZ22D.eefea329.zip
Previously I am in pure stock with locked bootloader, and I flash the new LCA43 with windows 10.
When I flashed it stops two or three minutes in 61% than I continues to 100% without any breaks.
I think you must wait at 61% until process continues.
Try flashing it with another usb port for example.
FYI
The old technique of forcing an ota update still works for a stock watch: Make sure you have the latest android wear app.
1. Reset the watch from settings
2. On the phone, erase the data from the android wear app.
3. Connect the watch to the app
After the watch syncs, it will ask if you want to update.
I have tried, flashing stock and sideloading, no dice, reflashing stock and locking bootloader then sideloading, again no dice, unlocking flashong stock once more relocking and trying ota, nothing flashes when ota tries to flash the lint gets to 15-25% theb flips to the dead Android for around 30-60 seconds before rebooting.
i tried multiple cables, pcs and operating systems (win7-10 linux Ubuntu and debian) and multiple downloads from seperate sources, nothing seems to want to give me this update..
Any help would be appreciated
freshlysqueezed said:
FYI
The old technique of forcing an ota update still works for a stock watch: Make sure you have the latest android wear app.
1. Reset the watch from settings
2. On the phone, erase the data from the android wear app.
3. Connect the watch to the app
After the watch syncs, it will ask if you want to update.
Click to expand...
Click to collapse
Thank you,it works
I have the new Android Wear 1.3 flashed at 28 hours ago and for now i am loving the new faces, and i like the battery optimization, in my case it consumes only 0.89% battery in one hour.
I have the screen off and micro off with an application.
LG G Watch have a new stable upgrade in my opinion.
Hi. What do you mean by micro off ?
Do you also keep fit off ?
Sent from my LG-D852 using XDA Free mobile app
ruben46_ said:
Thank you,it works
Click to expand...
Click to collapse
Tried this twice, stock with bootloader locked and both times it comes up with the dead android and reboots. Not sure what's wrong.
Sent from my Hitchhikers Guide to the Galaxy
Visegrad said:
Tried this twice, stock with bootloader locked and both times it comes up with the dead android and reboots. Not sure what's wrong.
Sent from my Hitchhikers Guide to the Galaxy
Click to expand...
Click to collapse
Did for me right now too. Maybe try to boot into recovery mode and flash it via ADB sideload.
For the user that ask me I mute the mic with an apk "mute wear mic" that I download, I think that is free.
I upgrade my to 1.3 with adb sideload command and it work at the first shoot.
I have also ended up with the dead android and tried both sideloading and the regular installing from watch. Tried with restoring the watch to stock and locked the bootloader but I am still ending up with a dead Android image then reboot..
steso90 said:
I have also ended up with the dead android and tried both sideloading and the regular installing from watch. Tried with restoring the watch to stock and locked the bootloader but I am still ending up with a dead Android image then reboot..
Click to expand...
Click to collapse
Yeah, it's weird. It's like I've lost recovery. I have flashed back to stock, locked the bootloader and try to go to recovery, dead android. unlocked bootloader, try to go to recovery from bootloader... dead android. I have used the restore tool to push recovery image on, everything says it went fine, try any method to get to recovery...dead android. I was able to flash the Mysterious Magic rom back on via his script with no issues, so not sure where the disconnect is, but for now I will stick with the rom since the battery life is great with that.
I've tried everything with no luck, LCA43 doesn't want to be installed on my watch.
I got the OTA, but when I press install it start installing until more or less the middle of the progress bar and then I get a dead android. I downloaded the OTA to do a sideload but it gets aborted at 61%. I formatted all the partitions and flashed the official images of LDZ22D, then tried both methods, with the same result.
Does anyone have the link to the official img? Because the OTA doesn't seem to work for me.
Sent from my Nexus 4 using XDA Free mobile app
JanusDC said:
I've tried everything with no luck, LCA43 doesn't want to be installed on my watch.
I got the OTA, but when I press install it start installing until more or less the middle of the progress bar and then I get a dead android. I downloaded the OTA to do a sideload but it gets aborted at 61%. I formatted all the partitions and flashed the official images of LDZ22D, then tried both methods, with the same result.
Does anyone have the link to the official img? Because the OTA doesn't seem to work for me.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
It's not "aborted" at 61% (or does it say Aborted?), only takes a long freaking time till it hits 100% from then on. Just wait 5 minutes or so once you see 61% on your CMD window.
Also I posted the update in a separate thread here, I think under General.
EpicLPer said:
It's not "aborted" at 61% (or does it say Aborted?), only takes a long freaking time till it hits 100% from then on. Just wait 5 minutes or so once you see 61% on your CMD window.
Also I posted the update in a separate thread here, I think under General.
Click to expand...
Click to collapse
If I boot into recovery, I get the dead android, and ADB can't see my device when this happens, so I can't sideload your update file, so I tried installing TWRP recovery and installing that file from there, but it fails straight away from TWRP.
How did you get ADB to see you device when you have the dead android showing?
Thank you =)
Is there any way to make the ota flashable through twrp?
hugoprh said:
If I boot into recovery, I get the dead android, and ADB can't see my device when this happens, so I can't sideload your update file, so I tried installing TWRP recovery and installing that file from there, but it fails straight away from TWRP.
How did you get ADB to see you device when you have the dead android showing?
Thank you =)
Click to expand...
Click to collapse
Boot into bootloader, select recovery there, once the screen turns to the LG logo instantly swipe from left upper to right lower corner as fast and often as you can, after a few seconds you should see a menu on the stock recovery screen. Then select the adb sideload option and send it from your PC via "adb sideload zipnamegoeshere.zip"
EpicLPer said:
Boot into bootloader, select recovery there, once the screen turns to the LG logo instantly swipe from left upper to right lower corner as fast and often as you can, after a few seconds you should see a menu on the stock recovery screen. Then select the adb sideload option and send it from your PC via "adb sideload zipnamegoeshere.zip"
Click to expand...
Click to collapse
No luck, tried it, booted into the bootloader, selected recovery and once the screen turned to the LG logo, I swipe from left upper to right lower corner as fast and often as I could, went again into the dead android screen and ADB still unable to see the device.
Isn't the swipe from upper left to lower right, to boot into the bootloader? I can do that, but whilst booting into recovery, from the bootloader, it just goes to the dead android.
Also tried to do a factory reset to the watch, cleared the data of the Android App on the phone, connected the watch and update fails when the progress bar is at about 20%
if any one could get their hands into the full ROM file, that would be awesome.
Any other ideas are welcome =)
And thank you for your help