i'm trying to install vegacomb 3.2 built 8.1 last night and after went thru the moddedstock, start the vega in its original mode, selected the language and went all the way down on the agreement page.... but couldn't 'click' the 'Accept' button; the screen just not responding at all. helpppp anyone .
thanks
If you can get to it, run the screen calibration app. If you cant get to it flash the stock rom and try from there. When sorted try the modded stock again.
Good luck.
Related
Help please.
I purchased 2 thrive tablets from best buy on a recent holiday from uk to usa (one for myself and one for my father in law).
I recently installed the update on my own without a problem. However when my father in law installed it on his thrive it got into a boot loop when rebooting. It keeps booting with the words "booting recovery kernel image".
When i do the vol/power switch on and pick the box icon to reset the same boot loop happens. I can use the tablet by doing the vol/power switch on and choosing the android icon but dont want to do this everytime i use the tablet.
Since i live in the uk and bought the tab in the usa I dont know what my warranty rights are.
Any help would be greatly appreciated.
william40 said:
Help please.
I purchased 2 thrive tablets from best buy on a recent holiday from uk to usa (one for myself and one for my father in law).
I recently installed the update on my own without a problem. However when my father in law installed it on his thrive it got into a boot loop when rebooting. It keeps booting with the words "booting recovery kernel image".
When i do the vol/power switch on and pick the box icon to reset the same boot loop happens. I can use the tablet by doing the vol/power switch on and choosing the android icon but dont want to do this everytime i use the tablet.
Since i live in the uk and bought the tab in the usa I dont know what my warranty rights are.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
OK, let me get this right. Your Father-in-Law did the update and when it rebooted it got to "Booting recovery Kernel Image" and hung. If you shut it down and try to boot it, it still comes up and says the same thing.
If I have this right, it has not installed the update. It has hung up tryig to reboot into recovery to apply the update. You said you can go into recovery and select boot and it will boot fine. If this so, open the Service Station and see if you can select the update again. With any luck, you sould be able to get it to redownload and install it again and fix the issue.
You also said you did a reset and it still came up with the message. Did you do a full factory reset? If not, do that and it should boot up as it did the firat day it was turned on. Also, if you have done this, try clearing the cache and reboot to see if that fixes the issue.
Thanks for the reply
I did try the service update again from the service station but the tablet shuts down then reboots with the same problem i.e. the" booting recovery kernel image loop"
I also tried the full factory reset from the settings but same boot loop again.
I also tried the reset by clicking on the open box icon when you turn on the tablet with the vol up/power buttons but again i get the boot loop
william40 said:
Thanks for the reply
I did try the service update again from the service station but the tablet shuts down then reboots with the same problem i.e. the" booting recovery kernel image loop"
I also tried the full factory reset from the settings but same boot loop again.
I also tried the reset by clicking on the open box icon when you turn on the tablet with the vol up/power buttons but again i get the boot loop
Click to expand...
Click to collapse
Sounds like you covered all th normal stuff. The final option I can give you is to go here and download my Thrive Easy Flash Tool. Once you have it, follow the readme file to load the adb drivers on your PC. I am assuming you have a Windows PC, if not, let me know. Once you get the ADB drivers loaded and operational, flash the Clock=WorkMod recovery to the device. Once it is loaded, you can download AustereGrims Thrive 0029 Stock images or rooted images and load them. Since it is your Father-in-Laws Thrive, I would load the stock images. After that is done, the device should boot just fine and be updated to the latest load.
Let me know if you have any other problems.
Mod Edit: Offsite links requiring registration removed.
Thanks Paul.
Will give it a go.
william40 said:
Thanks Paul.
Will give it a go.
Click to expand...
Click to collapse
No problem. Try ThriveForums.org. Think you find a lot of good info and people.
Many thanks for your help Paul.
Tablet is now starting up as normal.
Only prob is I now have no wifi. I get a wifi error in the wireless settings and cant add any networks.
Afraid I'm a bit of a dummie when it comes to this rooting and flashing lark.
Thanks again
william40 said:
Many thanks for your help Paul.
Tablet is now starting up as normal.
Only prob is I now have no wifi. I get a wifi error in the wireless settings and cant add any networks.
Afraid I'm a bit of a dummie when it comes to this rooting and flashing lark.
Thanks again
Click to expand...
Click to collapse
I am glad you have it almost working. It looks like you have the wrong version of the boot image or wrong version of the system image. If all you did was my root tool, then you have a new boot image with the older system image. That is why the WiFi says error. What you now need to do is get the file from AustereGrim that I gave you a link to. If you used the stock image of his and have the WiFi error, then he did not update the stock image with the correct boot image. In that case, just use my tool to flash a stock boot image. If you need more assistance, send me your Email via PM and I will get back to you to help.
I just bought my A500 a couple days ago. I received a couple OTA updates but the last one froze up. After powering down my tablet and bringing it back up the touch is unresponsive.
I've found that if I unplug the power from it I am able to press the power button on and off and that seems to make the touch part work.
However, once I'm in the OS it constantly resets to a black home screen with "Android System" up in the top left corner. Next to that is an icon with a big gear and a small gear with a green belt around them.
The tablet is full stock and I can't enable USB debugging because settings always resets as soon as I get into that area.
I've tried flashing many ROMs using the Power/VOL + recovery mode but none of the ROMs work.
I am assuming that I will need an official ROM in order to actually restore the tablet.
Can anyone help me either track down a stock ROM, ie "update.zip" or help me figure out a way to restore this tablet another way?
Ok, when I plugged in my tablet just now it said USB Debugging was on.
What are my options with pushing an update to the tablet? Are there any methods that would work for me in this case?
Would I be able to root the device at this point and have more recovery options?
Same thing happened to a friend of mine. I followed the directions on this page to fix it:
http://www.androidtablets.net/forum...ding-yellow-triangle-exclamation-point-2.html
Basically you are just making it revert to a earlier version.
klaus9000 said:
Same thing happened to a friend of mine. I followed the directions on this page to fix it:
Basically you are just making it revert to a earlier version.
Click to expand...
Click to collapse
You are awesome! I've been looking and looking for an image that would work and the one at the bottom of that thread worked like a charm!
Thank you so much for your help!
This rom is not rooted correct? I need to go back to factory to return for warranty.
Hello everyone This is my first time posting so I hope this is in the correct spot.
I have a Transformer TF101.
I rooted it months ago and can not remember what method I used.
I installed CyanogenMod 10 and everything was fine.
I did an update to one of the nightly builds and now my Transformer is stuck in CWM.
When I plug it into my Windows 7 pc it comes up with a unknown device code 43. I have tried it on several other devices having vista and xp and the same thing happens.
For the heck of it I tried placing the stock FW on the SD card but the transformer does not see it.
I tried placing it in adb mode but the pc still comes up with unknown device.
I have factory reset, wiped cache, and delvik, it is just stuck on CWM.
Can anyone help me with this or did I just totally break the thing? Thank You.
what did you use to flash the rom?
Try doing a cold boot......volume down and power (like you would to boot into recover) but release the keys when the white writting comes up on screen and press nothing.
use v+ and v- to toggle and select the Android or let it kick in itself.
sounds like youve used rom manager
Broke my TF101
scottyf79 said:
what did you use to flash the rom?
Try doing a cold boot......volume down and power (like you would to boot into recover) but release the keys when the white writting comes up on screen and press nothing.
use v+ and v- to toggle and select the Android or let it kick in itself.
sounds like youve used rom manager [/QUOTE
Thank You Scotty: That did get me back so it boots up. None of my computers will see it. Wondering if maybe the cable took a dump. I did use rom Manager. At this point I would like to bring everything back to stock and start over. Any suggestions on how to bring back to stock with sync cable not working?
Click to expand...
Click to collapse
best just to get the sync cable and use one of the tools available to make sure it gets done right.
just dont use rom manager bud.....:good:
try this to see if you can fix the recovery loop
Recovery Loop fix with terminal emulator
Hello XDAers,
I am a real noob at rooting or android-related, and a true one voided of any knowledge regarding anything IT- related.
So dear veterans, please go easy on me.
Due to my prior success of rooting and flashing my Nexus 4 successfully a few months back with no issues, I decided to give it a try to flash a custom ROM for my dad's LG Optimus L7 - which seemed an easy task compared to configuring my Nexus 4 - since there was no need for inputting any command lines or any dealing with the abd (using the easy shortcut, that is).
So, I followed the guide here: http://forum.xda-developers.com/showthread.php?t=1906133 ...
I first factory resettled the phone because it was bloated, then applied the "RunMe.bat" from the "What you desire!" folder. (Everything was already backed-up beforehand.) But the process didn't success until I've retried again and again by re-plugging the USB in because the application/PC couldn't detect the phone. In the same time, I was running KDZ_FW_UPD.exe in the background, so unexpectedly for me the phone shut itself and pushed itself to a vividly green emergency screen, then in a few seconds switched back to a screen of purple-white-blue glitches. I had to close KDZ_FW_UPD.exe without knowing what quite happened since it seemed to be the cause and restarted the process with RunMe.bat.
I didn't manage to "Restore" it first due to the fact that the phone stopped responding due to a lag asking for an encryption key. It was lagging so hard and I had to close the cmd around 5 tries while it was processing, but succeeded later on.
And then, to verify whether I've actually suceeded in rooting L7, I installed Root Checker from the Play Store. And again, for the first few tries the program froze on screen for a long period of time due to "system performance", but after rebooting and restarting the app a few times again, the ROOTING proves to be a success. Just to be sure, around this time I've reloaded KDZ_FW_UPD.exe and it suceeded.
So I went to install CWM and ES. CWM for recovery boot and ES for removing pre-installed system apps as the phone was lagging so badly. I've downloaded the CWM restoring(something like ~6.0.28?) first and tried fastbooting immediately right after, but instead of getting the fastboot menu I got a screen emptied in black with these words:
[5020] "Secure booting error"
[5020] "Cause: boot certification verify"
No hard keys could do anything on the presumed "fastboot", and so I had to hard boot again. I thought that it might be due to the lack of memory(checked on ES later on that it was 310~MB/2GB), and so I've used ES to uninstall a lot of system apps which I deemed uneccessary. So I've Googled a bit and it became apparent to me that that I've didn't unlock the device properly, so lurked around and found a file called L7CWM that is supposedly to resolve my problem, but I presume that it's the CWM recovery image that I've installed. So in the end, I didn't bother with it but kept it on tab just in case.
I repeated the same process with CWM again, but this time, the screen was joined with all kinds of flowery glitches. Restarted the device, and it went only downhill: now the Home launcher stayed all pitch black and nothing appeared. I waited a few minutes, but nothing there until the notification bar appeared. The home screen is apparently dead, and so are the menu keys. Switched to Nova Launcher(installed it just in case Home Launcher fails), and still dead. I couldn't access using any of the menu keys and had unusable launchers.
Hopefully I could still access to the settings from my status bar, but when I did, it started crashing immediately.
I've repeated the attempt a few times after restarting the device a few times, but nothing helped. It only got worse that the when the launcher did SEEM to work. It only showed the wallpaper without showing any of the icons/apps. And crashes again.
I could still access to the App menu via the settings, but couldn't open any of them and when I tried to uninstall them, the screen frozes immediately right after I gain access to the page (white page though) and gain this message: "Unfortunately Package Uninstaller Stopped!"
Then I convinced myself that the only thing I could do at the time was to factory reset the phone and then everything would go alright since I've just had to restore the system apps.
But then the black screen of death came right along with it:
"Secure booting error"
It seems that I'm out of luck... ... But just to check if I'm still left with resorts, I've downloaded the L7CWM file online...
... ...but it still didn't help.
So now I'm being left with no other choices other than asking for help. I never really understand what KDZ_FW_UPD.exe does since I had the LG Driver already before installing it, which I presume was for updating the phone to a newer or older version. And too complex tech articles are kind of alien for me.
EDIT(1 hour later): Okay, now I figured out the reason why L7CWM didn't work was because I didn't extract it to the right folder (after double checked via notepad that I was supposed to directly put it into the C:\ drive). Now it worked(?), but then it didn't.
After launching Flash_Bootloader.bat:
This message now appeared on the L7:
"Sorry!"
"SuperSU is not responding.
Would you like to close it?"
"Wait - Report - Close"
and a few minutes later
"Sorry!"
"Unfortunately, SuperSU has stopped."
"Report - OK"
Now I think the bugs till now happened was due to the fact that I've deleted a file that was required for me to launch apps... Now I just need the right fix.
After 5 minutes of screen inactivity the phone restarted by itself, kind of creepy... ...
Flash_Recovery.bat did nothing.
Reboot2Recovery.bat made it reboot but still struck on the same menu.
Nothing seems to be effective via the phone anymore, seems like I have to rely on abd but then again I don't know how... ... My dad is also f*cking pissed off ^ ^;...
__________________________________
I think that I explained the logs pretty precisely in case I missed something... I'll be very very very very very very thankful if someone could tell me what has caused my phone to fail though.
For references, here are the phone's specifications:
Model Number: LG-P705g
Android version: 4.0.3 (Stock)
Rooted:Yes (root checker)
Baseband version: MSM7227A-1-AA
Kernel version: 3.0.8-perf
Build number: IML74K
Software version: V10e-AUG-10-2012
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
remove the battery for 10 seconds,put it back pres VOL+ and VOL - same time and than press the power button.when you feel a vibration press for many times the button wich is down in right,try for many times and maybe it will working :}
Cydes said:
Hello XDAers,
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
Click to expand...
Click to collapse
simple answer for your
just download your stock rom
go to emergency mode
and flash that stock rom
i just downloaded and installed the android 10 system update from the ASUS download centre and after installation completed the phone worked for a while and then it suddenly got locked and after a sec it started showing black screen and the navigation buttons and status bar are flashing (popping out and going in) and it occasionally also shows the lock screen for a brief moment. I have tried going into safe mode and this issue still happens. is there a way i can fix this without hard resetting the phone? i was editing the quick access menu options just before the phone got locked if that helps. please help. u can find a video of the phone in attachments or here
https://imgur.com/a/HBjwq0P
. (sorry for the bad english. its not my native language)
You able to reboot to bootloader?