Database Info

NOOBZ: The EASY guide to rooting your Aria and Installing Attn1's ROM (Win XP/Vista)

Like some of you, i'm an absolute newbie to Android. But after a week of reading and scrolling through many webpages and forums. i finally got the nerve to Root my Aria and install Attn1's ROM because i was tired of the auto-start of ATT's bloatware and random restarting of those apps that i had to constantly check and kill with Advanced Task Killer (ATK..in the Market).
and yes i've actually seen a slight increase in my batter life after. (on at 6am..average txting, heavy web surfing, and minimal Market browsing...69% by 2pm)
so here's the step by step guide without having to go through the many pages of the forums...
** To Root your Aria and Clockwork Mod
1. go to http://unrevoked.com, choose your Aria phone, and click the download file. save and extract into a easy to remember directory on your computer.
2. go to http://www.unrevoked.com/rootwiki/doku.php?id=public:windows_hboot_driver_install and follow the instructions to install HBOOT
3. go to HTC's website and download and install HTC Sync. Yes it's been said it messes up the process. slightly not true. you're only gonna install it so that the proper ADB drivers are installed that Unrevoked Rooting tool needs to access your phone. as soon as it installs...uninstall it. it will leave the proper ADB required drivers behind. (it took me hours and finally wading through 6 pages worth of forum posts to find this out..so i'm saving you the trouble)
4. now on your phone..click Menu > Settings > Connect to PC > Default Connection Type > and select Charge Only
5. go back to Settings > Applications > Development > and check USB Debugging
6. now start UnRevoked (c:\directory you chose\reflash.exe)
7. gray wide window with UnRevoked's logo and a "waiting for device" type message under it. now plug in your Aria via USB to the computer. sit back and watch the magic. 5mins (or less) later and you will have a Rooted phone with Clockwork mod.
**now that your Aria is rooted you can install Attn1's ATT bloatware free Rom.
1. go to Menu > Settings > Connect to PC > Default Connection Type > and select Disk Drive
2. go to http://forum.xda-developers.com/showthread.php?t=708434 and decide which beta version you want to use. I chose B003 since it's the one folks have the least issues with and the cleanest one that hasn't changed too much about the stock rom. download and save the file to your SD Card. i chose the Download folder to make it easy to find.
3. now turn off your phone. hold down the Volume Down button and press the Power button. you should see the standard Fastboot menu with the lil droid guys on skateboards on the bottom. press the volume down button until "recovery" is highlighted. hit the Power button to select it. you'll see the HTC logo as if it's booting and the clockwork mod screen (black background with green text) that you were left at with the Unrevoked tool.
4. using the volume down button select Nandroid > Backup. i'm not quite sure but i think this backups all your settings of the current stock Rom. *advanced users correct me if i'm wrong*. all i know is you NEED to do this. it was stressed in most forums.
give it a couple minutes and the process should finish.
5. now select Install Zip from SD Card. Use the volume buttons and Power button (select) and navigate to Attn1's Rom zip file. select it. don't let the warning scare you too much. his Rom is LEGIT and 110% working select yes and watch the quick install process.
few minutes later you should be up and running just fine.
6. if it reboots and you hear some pleasant chimes/dings and no ATT 3G boot up or loud WOOSH animation..you've installed his Rom just fine and all your previous settings as if nothing's changed yes the HTC Quietly Brilliant will be on your screen for a little while since there is no secondary boot animation. don't worry.
credits go to attn1 and quickness to get this clean rom up
***EDIT: July 26, 2010 ***
just wanted to thank everyone for the compliments and glad this was able to help ease the pain of rooting your Aria and installing a custom ROM.
many thanks for the compliments

Whoa! Just what I needed. Many have come before you and remained silent so thanks for putting this together. I have been reading for a week now in preparation of purchasing an Aria and it just shipped from Amazon today. Now, I'm psyched!

this is amazing, i had literally just done the unrevoked thing and had no idea what to do next, and then all of the sudden this thread pops up and helped A LOT
perfect timing

glad to help
the experienced users were right that's it's simple if you KNOW what you're doing. just the answers/instructions were vague on exactly how.

ok, now how do i access clockwork? do i have to restart while holding the volume and power buttons or is there something im missing?
also, is there a way to move the apps to the sd card?

unteagle said:
ok, now how do i access clockwork? do i have to restart while holding the volume and power buttons or is there something im missing?
also, is there a way to move the apps to the sd card?
Click to expand...
Click to collapse
Power down your phone, than hold down the volume down button and power button. In the fastboot menu push volume down till Recovery is highlighted and push the power button to select. 5 seconds later it'll load into clockwork
And I have yet to try the SD card app method

thanks, hopefully someone will find out how to install apps to the sd card soon, it would save a lot of space

I certainly appreciate your help here. I am now running the liberated 005 on my Aria. Still want to make the jump to 2.2

Not to be rude, but we really shouldn't keep posting new instruction threads, they generally confuse people, and attn1 already mentioned this method.

new here. thanks for the step by step!
all was running fine up till the point where the program was rebooting my phone... but after the phone reboot and is running fine... it still say it's "waiting for reboot..." so... i try to start over and now it says that it's "waiting for device"...
but i've already installed and uninstalled the HTC sync for aria. please help!

andoh said:
Not to be rude, but we really shouldn't keep posting new instruction threads, they generally confuse people, and attn1 already mentioned this method.
Click to expand...
Click to collapse
yeah, but it took me over an hour and going through pages of forum posts before realizing i needed to install HTC Sync and uninstall it so that i could have all the drivers i needed and no issues of programs trying to access the USB port. this saves some newbs a lil headache. that's all i'm trying to do.

uhhhyeahhh said:
new here. thanks for the step by step!
all was running fine up till the point where the program was rebooting my phone... but after the phone reboot and is running fine... it still say it's "waiting for reboot..." so... i try to start over and now it says that it's "waiting for device"...
but i've already installed and uninstalled the HTC sync for aria. please help!
Click to expand...
Click to collapse
just plug the phone back in and let it run the Unrevoked again. i ran into the same issue and thought i might have rebooted too soon through clockwork.

Thank you for this. I tried to root my phone the other way and could never get my phone to be seen by my comp.

can anyone tell me why the link to unrevoked.com/#aria wont load. all i get is the the home page where you select your phone. down at the bottom of the screen it says errors on page.... so frustrating

It's working for me. Try http://unrevoked.com/recovery/

this is exactly what i needed! i have read and read (and tried) other methods, which may be the same in a sence, but i have never got it to work. i am in the process of installing the liberated rom as we speak. much props to you asiancuta for putting out a great step by step guide. and as always props to attn1 for making this possible.
edit: keep getting error at line 7 and installation aborted. phone is pretty much screwed. i can keep getting back into clockwork but dont know what to do from there. phone wont boot up either

beazie0885 said:
this is exactly what i needed! i have read and read (and tried) other methods, which may be the same in a sence, but i have never got it to work. i am in the process of installing the liberated rom as we speak. much props to you asiancuta for putting out a great step by step guide. and as always props to attn1 for making this possible.
edit: keep getting error at line 7 and installation aborted. phone is pretty much screwed. i can keep getting back into clockwork but dont know what to do from there. phone wont boot up either
Click to expand...
Click to collapse
Odd. Never had that happen. In the install zip from SD card menu try selecting Signature Verification method is off and try that.
Also make sure you reboot the phone after rooting just in case.

beazie0885 said:
this is exactly what i needed! i have read and read (and tried) other methods, which may be the same in a sence, but i have never got it to work. i am in the process of installing the liberated rom as we speak. much props to you asiancuta for putting out a great step by step guide. and as always props to attn1 for making this possible.
edit: keep getting error at line 7 and installation aborted. phone is pretty much screwed. i can keep getting back into clockwork but dont know what to do from there. phone wont boot up either
Click to expand...
Click to collapse
If you followed the instructions, you can use ClockworkMod to restore your 'nandroid' backup.

Found out what the problem was. At least I think. When I formatted my SD card(trying other methods), I lost all the default folders. So I created a "downloads" folder and put the liberated Rom in it. Therefore I was getting an error message. I nand restored, moved the Rom out of the dl folder, and just put the zip file on the SD card. Not in a folder. Then proceeded with the instructions and worked just fine. Thx everyone. Now I'm rooted and flashed my first Rom (at least on android)
Sent from my HTC Liberty using XDA App

This helped me so much! Thank you!

CognitionV2.2Beta6 (noob guide)

**Please note that following these steps will completely erase your phone**
**Back up any important information before starting(contacts, photos, etc)**
**This guide is for Windows users**
Flashing Cog 2.2 Beta6 (From 2.1 Eclair or 2.2 Frozen Yogurt)
Things to download before you start:
Odin 1 click stock - http://www.thevod.org/misc/captivate/I897UCJF6-final-OCD-REV0.rar
one click root - http://forum.xda-developers.com/showthread.php?t=739304
cognition beta 6 - http://www.ponack.net/designgears/index.html
On your phone - go to Settings, Security, restore factory data.
Reboot your phone.
Enable USB debugging.
Start Odin (you downloaded earlier).
Plug your phone into your computer via USB.
Odin should recognize your phone at this point.
Click "Master Clear".
Once finished, close Odin. Your phone should be rebooting.
Once phone has rebooted, make sure usb debugging is still enabled.
Remove usb plug from phone and then power down the phone.
Remove battery, remove sim, (remove external SDCard).
Insert battery.
Open Odin.
Hold vol up and vol down.
While holding vol buttons, insert USB.
The phone should show a triangle with android digging (or sweeping?)
odin should recognize the phone at this point
Click "Start".
You should see a progress bar on your device display, and within Odin.
The phone will reboot when finished.
Close Odin.
Go back to your phone an re-enable usb debugging.
Run "One-Click Root"
Click "one click root"
Your phone will boot into recovery mode.
Use the volume buttons to highlight "reinstall packages".
Hit the power button to select.
Your phone will apply the update then reboot itself.
Go into app drawer and verify that "superuser permission" icon is visible.
Close one click root.
Power off your phone.
Re-insert your sim card.
Power phone on.
Allow your phone time to read the internal SD card.
Connect your phone to your computer via USB.
From your phone - select mount usb.
using windows, copy Cognitionv2.2beta6.zip onto your SD card.
Sign into Market.
Find ROM Manager, download, and install it.
On your phone, open ROM Manager.
Click "Flash clockwork mod recovery"
Select "Galaxy S Captivate".
Observe the green progress bar at the top of your phone's display.
When complete, clockwork will ask for superuser permissions - allow it.
Choose install rom from SD Card.
Navigate to your SD card and select the cognition zip.
Click OK.
Click OK.
Your phone will either install and reboot automatically, or it may hang at the recovery screen waiting for your input. If this happens, select reinstall packages.
From within this menu select install rom from .zip.
Navigate to the cognition rom and select it.
Confirm that you actually want to do this.
Your phone will reboot to menu again.
Select "reboot system" and sit back.
Your phone should boot into the Android OS.
Almost done...
Go here, https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_LG.gif:NonHosted and buy DesignGears some beverages

It seems that this is already well documented in the Cognition wiki, no?
http://cognition.theidiotshideout.net/mw/index.php?title=Main_Page
You may also catch some flack as this has nothing to do with actual android development.

Cog 2.2 Beta 6 should be rooted already when you flash it, unless something changed. I dont see the need to use one click root.

z28james said:
It seems that this is already well documented in the Cognition wiki, no?
http://cognition.theidiotshideout.net/mw/index.php?title=Main_Page
You may also catch some flack as this has nothing to do with actual android development.
Click to expand...
Click to collapse
+1
Plus this list may be a bit confusing to a real noob.

Jimmy thanks for this, simple but very precise. The wiki seems to be written for somebody that already knows all the details. It's also not very clear as to whether or not you can go straight from eclair to cog2.2, you cleared it up for me so now I don't have to start a "sorry about the noobness" thread/post. I'm running cog 2.1.5 so I have done it before, even used odin once. Thanks again

Or you could just use his pre-made Odin flash and skip all of those steps.
Delete.

kakwvu said:
Or you could just use his pre-made Odin flash and skip all of those steps.
Delete.
Click to expand...
Click to collapse
+1
Sent from my SAMSUNG-SGH-I897 using XDA App

kakwvu said:
Or you could just use his pre-made Odin flash and skip all of those steps.
Delete.
Click to expand...
Click to collapse
That's an answer that belongs in some sort of guide for noobs haha

I appreciate the detailed instructions. A few details to be added. Odin is Windows only, and one click root does not copy the zip file successfully for me (on a Mac). I had to view the package contents of the program and drag the file over and rename it myself, then used the program to reboot into recovery (3 button didn't work for me either).

kakwvu said:
Or you could just use his pre-made Odin flash and skip all of those steps.
Delete.
Click to expand...
Click to collapse
And this is +3.
Sent from my SAMSUNG-SGH-I897 using XDA App

For everyone that gripes about battery life after a flash, try this first after every new ROM:
http://forum.xda-developers.com/showthread.php?t=765656

joeybear23 said:
For everyone that gripes about battery life after a flash, try this first after every new ROM:
http://forum.xda-developers.com/showthread.php?t=765656
Click to expand...
Click to collapse
If you gonna take this there, I'd suggest this one instead.
http://forum.xda-developers.com/showthread.php?t=806211

So does this mean I cant go from stock eclair to froyo with only Rom Manager and no use of ODIN (my phone never recognizes ODIN )

Actually, I think this is a good idea, might keep some of the junk out of the regular Cog thread, that thing is Frickin HUGE...

ozy944 said:
So does this mean I cant go from stock eclair to froyo with only Rom Manager and no use of ODIN (my phone never recognizes ODIN )
Click to expand...
Click to collapse
yes you go from stock eclair to froyo with only Rom Manage...
i did it on sunday night and today i see new cog 6 beta released!!!!
copy cog file to your sd card; install rom manager and continue from there, it will fail the first time (mostly) start phone again and reinstall package..done.

There's also one more thing the op didn't mention. If this is targeted at noobs, it really should be mentioned that if you follow these instructions, you are essentially wiping your entire phone clean (by the odin one click stock). If your that paranoid, go for it.
To me though, I just use titanium backup first, and back everything up. Then after upgrading to cog from eclair (directly without reverting to stock) you can restore your THIRD PARTY apps plus their data. (avoid restoring core apps as thats a bad idea) Not to mention no need to back up and restore any of the media you might have on the internal sd card. (not sure if odin one click stock touches that stuff or not)
I've had no problems in any of my ROM upgrades, and I've moved from 2.1 to cog 2.2 beta 2, then again today to cog 2.2 beta 6. All of that without a restore to stock. You really should only restore to stock if you are having problems AFTER upgrading. Why do extra work and wipe the whole thing clean if it's not necessary? Just adds steps, and possible frustration from people not expecting a wiped phone.

thank u man! rly!

Please verify that you are able to get into download mode using only button combinations before you start any flashing process.
Sent from my SAMSUNG-SGH-I897 using XDA App

orlandoxpolice said:
Cog 2.2 Beta 6 should be rooted already when you flash it, unless something changed. I dont see the need to use one click root.
Click to expand...
Click to collapse
You have to root to be able to flash it in the first place.

Do you mean that Odin won't recognize your phone? WHat happens when you try?

Relock US Xoom Tiamat 1.4.4 resulted in hanging at Motorola logo

Hey guys I was having some problems with my xoom's wifi on Tiamat's 1.4.4 so i decided to relock the device and use stock.
It's a US model and had build HMJ37 but i decided to follow this thread
http://www.xoomforums.com/forum/mot...4600-thinking-about-unrooting-read-first.html
I downloaded img build HRI66 and followed all the steps and it was ok. Then, i rebooted and now my device is at the motorola logo's dual core screen. Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo. It just keeps rebooting and getting stuck at the motorola logo. I then unlocked again, and performed the same process with the HRI39 img and still got the same problem
So im stuck. Please help me out guys, i'm in serious ****.

So you have gone as far as the "fastboot erase cache" and "fastboot oem lock" right? This is kind of funny because I tried to install Tiamat 1.1 ROM tonight and ended up going through this HUGE loop of problems.
Here's the problem I had: some time ago I installed ROMManager from the market. I thought it would be easier. It SHOULD be easier. I let it update my recovery to its own version 4.something. It allowed me to SORT OF install the ROM, but I wound up with some persistent system files that weren't getting wiped and a bcm4329.ko version mismatch.
This stumped me for a long time because all I could see was an "Error" message where I was supposed to be able to toggle the wifi on and off. I tried rolling back to my previous ROM. No go. And the culprit the whole time was ROMManager's CWM.
I tried rolling back my recovery.img file to the Tiamat version recommended in this forum. I kept getting all of these crazy "could not mount" errors for pretty much EVERYTHING. I thought my recovery partition was effed. So I rolled back to stock. Followed pretty much the same instructions you linked to.
From there I was able to boot into the stock OS. WiFi worked. I breathed deeply for a minute or two then dove right back in.
If I was in your position I would (and I did, though not from a boot loop) boot into fastboot and unlock the bootloader again. You can do it by holding the Vol down key as the device boots. When fastboot loads type "fastboot oem unlock". Press the Vol down key then the Vol up key. Do that again. Your device is unlocked now! Hooray!
Now you need to install a recovery.img. (I just did this too.) Get the .img file here: http://forum.xda-developers.com/showthread.php?t=1074979
Boot into fastboot again. Put the recovery img file you downloaded into the same directory as your adb and fastboot executables (if you haven't already linked to them in your PATH). Type "fastboot flash recovery recovery-lotsofstuffhere.img". Type "fastboot reboot". 2 seconds after the Motorola logo pops up press the Vol Down key. Then press the Vol Up key to enter recovery.
Ok, here's where I found out what a dumbass I was. I got all of the stupid "can't mount anything" errors again. I thought, HOLY ****. I just did all of that work, spent hours troubleshooting and reformatting and bringing it back to stock and flashing the custom recovery all over again just to run into the SAME error. I really thought I was screwed. Then I found some forum where a guy was complaining about the same error. He realized he was getting it because his sd card was half-way out. I thought - "SD CARD?!?" Some guys told me I needed one earlier too, but the ROMManager CWM didn't require it. It just screwed up my system files. So I popped one in and rebooted. Voila. Everything's kosher. If YOU have the same problem, make sure you've got an SD card in.
Ok, so now you're in recovery. You'll need to flash an OS of course. If you haven't already got it, get Tiamat 1.1 rom. Put it on the sd card. Wipe data/factory reset. Install zip from sd card. You're golden. At least I was. 5 hours later.
-Mike

Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.

DUDE YOU'RE MY ****ING HERO!!!! I got it running can't say if everything is 100% just yet but the fac tthat im back in is enough to thank you so very much Mike!!! What a guy!

It worked? Great that's excellent news. Just out of curiosity - did you get there because you had ROMManager's ClockWorkMod? Or maybe you didn't do a full wipe before flashing a new rom? Or maybe you restored some WiFi settings with Titanium Backup after a new flash? How did you wind up with tthe problem in the first place - you know, for posterity.

well to be honest i am not 100% sure. I think the source of the problem msut have come from my previous installation of tiamat's 1.4.4 rom, it was always actin up on me and i don't believe i wiped the mod before i updated it and that may have done it. I wish i could give you more than just a pseudo answer.

DeeJayCruiser said:
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
Click to expand...
Click to collapse
This is why they say to make sure you're plugged in when doing this important stuff, lol.

okantomi said:
This is why they say to make sure you're plugged in when doing this important stuff, lol.
Click to expand...
Click to collapse
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
DeeJayCruiser said:
Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo.
Click to expand...
Click to collapse

farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You are right...I had forgotten that from the OP. Very strange indeed.

Yeah I dunno why, my xoom was just acting up. It's fantastic now, albeit the wifi still has a couple kinks but android market issues have been resolved, i get much better streams and with tiamat 1.1 everything is already built in and with a quickboot option =)
Xda...where would i be without you!

farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You should be able to reboot the device using vol up + power, then holding vol down and vol up until it says "Cold booting Linux.....".
This should do the same as letting the battery drain, plugging it in and turning it on.

DeeJay - dunno if you've done this already, but if you haven't you should go back to the Tiamat 1.1 thread and find the Modpack. It fixes the Market update issue and gives you built-in screenshot capabilities and an option to reboot into recovery from the power off menu. It's in there - you just have to scroll down a bit before you find it.
Also - what issues are you having with WiFi?

Thanks for that important tidbit, solarnz. I'm going to file it away for future use.

OMG!!!! Dude you just saved my life! I thought my baby was out the window. I had the exact same problem as you did. I was trying everything from every thread that had anything to do with this problem. I just finished installing and it booted. WHEWWW!!!
Thank u thank u thank u!!

Glad it helped. I'm seeing all kinds of posts in here about the ROMManager CWM. Not good.
Sent from my Xoom using Tapatalk

my lg o1 stuck at lg logo, need help

Hi
I tried to install cm11
on The device
And the middle of the installation I registered it was canceled
So I had to install cm7
from the Memory card
I installed it
When I run the device
He got stuck LG logo
What to do?
And I used this guide: http://forum.xda-developers.com/showthread.php?t=2589303
And I followed - Upgrading from another CM10.2 or Older ROM
Sorry for the english, I'm from Israel
And I used google translate

eran32 said:
Hi
I tried to install cm11
on The device
And the middle of the installation I registered it was canceled
So I had to install cm7
from the Memory card
I installed it
When I run the device
He got stuck LG logo
What to do?
And I used this guide: http://forum.xda-developers.com/showthread.php?t=2589303
And I followed - Upgrading from another CM10.2 or Older ROM
Sorry for the english, I'm from Israel
And I used google translate
Click to expand...
Click to collapse
Boot back in to your recovery and wipe cache and dalvik cache. Format system and then install your ROM. There are major differences between CM11 and CM7. When making big jumps like that it's always best to format system before installing a ROM.

shinobisoft said:
Boot back in to your recovery and wipe cache and dalvik cache. Format system and then install your ROM. There are major differences between CM11 and CM7. When making big jumps like that it's always best to format system before installing a ROM.
Click to expand...
Click to collapse
I just did factory reset via cwm
And still have a problem
So do just what you say and do
system format?
You mean that you are going to have a system folder in the mount and stroage given formatting?

eran32 said:
I just did factory reset via cwm
And still have a problem
So do just what you say and do
system format?
You mean that you are going to have a system folder in the mount and stroage given formatting?
Click to expand...
Click to collapse
In CWM select Wipe data/factory reset. This will wipe the cache, dalvik cache and a couple other partitions. Then go to Mounts and Storage and select Format System. That will format the system partition.
Now go back to CWM home screen and install your ROM.

shinobisoft said:
In CWM select Wipe data/factory reset. This will wipe the cache, dalvik cache and a couple other partitions. Then go to Mounts and Storage and select Format System. That will format the system partition.
Now go back to CWM home screen and install your ROM.
Click to expand...
Click to collapse
thanks man, now my lg o1 works

Glad to help
Sent from my LG-P769 using Tapatalk

Hi,
May I ask for help here (instead of creating a new thread) ? I have the same problem: The device is booting loop at the LG screen. Bricked it when I wanted to save the ROM with ROM Manager.
I have no access to recovery mode, but Emergency mode does work (With and without battery).
I've followed multiple guides, including this one:
Most of you are stuck on a yellow screen with”Emergency mode!!” or the phone is not responding at all. You guys wanted a custom rom like Optimus Prime-v2 and let me tell you, this time it will work. Optimus One P500 comes with stock android 2.2 – V10a, V10b … and android 2.2.1 – V10n. They might be done for different regions depending upon the phone release and its popularity and definitely bug fixes and enhancements. To have Prime-v2 on your handset you will require V10a or V10b on your handset. Reason, V10n stock cannot be rooted easily. Rooting the handset is must if Prime-v2 is required on the device. Steps to install V10a, V10b series. I am using Windows 7 32-bit, 3 GB RAM laptop:
1. Clean your system first; get rid of LG PC suite and other stuff shown in Uninstall Program with vendor name as LG. Remove MSXML builts from the handset. Remove Nokia and other drivers if they are on system like Ovi suite etc. I also removed a lot of Microsoft runtime environments. Not sure about the reason but it worked for me.
2. LG usb device drivers, download the application B2CAppSetup.exe http://csmg.lgmobile.com:9002/client/app/B2CAppSetup.exe .
3. In the Menu Bar, click "Options & Help", and click "Country & Language". Select the appropriate Country & Language. I used India and select P500 from the list that popup after you change the country and region. It will download, install and save the drivers somewhere in C:\LGP500\USB_Driver, it will prompt to open the rar files, just click and install the exes seen in them.
4. Reboot the system.
5. Right click on Computer -> Properties -> Device Manager and see for three drivers – LG android usb modem, LGE serial usb port and LG composite USB device. Disable the modem driver and reboot once again.
6. Switch off the phone and press volume up + BACK button + POWER button. Phone should turn yellow with text “Emergency Mode!!” To switch it off you have to remove the battery (I know it hurts, but that’s the only way out here). Switch off and let’s continue with the setup.
7. To do the KDZ of system you will require the KDZ software updater, links keep going off and on internet. Try searching for “KDZ_FW_UPD_EN” or “KDZ_FW_UPD_EN.7z” in Google and download the software. It should be somewhere around 2.3 MB. To use it you will required some good version of WinZip or winrar again Google it and install the 7z archive utility.
8. Install msxml.msi as the manual or readme.txt says to do so.
9. To get the V10x Official ROM, you need to first determine the ROM of your choice. List of all firmware available for LG Optimus One P500 (list of codes) http://csmg.lgmobile.com:9002/csmg/b2c/client/ezlooks_model_list.jsp?model=LGP500 , search for your country (use IE it looks sexy in it), I looked out for IND/INDIA. Download link to the ROM is http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/XXXXX/V10a_00/V10A_00.kdz where XXXX is code from list of codes. In my case it was: AINDBK. Save the file.
10. Prepare the handset by removing the SD card and boot it to emergency mode (some are already stuck on it so reading this post…: D) using the key combination stated above.
11. Connect to the PC and it should say, installing drivers’ blah… blah … your device is ready to use now.
12. Run the KDZ updater downloaded in step 7. Select 3GQCT in Type, DIAG in PhoneMode, and browse for ROM V10a in KDZ file and hit Launch Software update. Wait for somewhere around 5-10 minutes. It should say ===FINISHED=== in the log window of updater.
13. Handset will reboot, if not wait for another 5 minutes. Unplug from USB and try to switch it on.
Click to expand...
Click to collapse
My problem is that KDZ still doesn't find my phone after all these attempts - I uninstalled the device driver, then reinstalled it succesfully (B2CAppSetup.exe). I reboot, install msxml.msi, and start KDZ.
Next, I power my phone in Emergency phone, plug it, and it is detected for the first time by the computer. I do have LGE Android Platform Composite USB Device, listed in the Device Manager, as well as LGE Android Platform USB Modem.
Using KDZ, I select the "3GQCT" type, phone mode "DIAG", with the correct KDZ file I've downloaded earlier. Once I launch the software update, phone is not found.
I've tried several times, including desactivating the LG Modem from the Device Manager; unfortunately, when I disable it I need to reboot - I do reboot, but then the LGE Android Platform Composite USB Device is absent from the device manager, and isn't detected by Windows at all, until I fully reinstall the driver (...).
I really don't know what I'm doing wrong - note that I use a laptop with Windows 7 x64; I know laptops handle USB port in a different way than desktops.
Can you help please?
I must be SO close... =(
Thanks, I really appreciate it!

GameX2 said:
Hi,
May I ask for help here (instead of creating a new thread) ? I have the same problem: The device is booting loop at the LG screen. Bricked it when I wanted to save the ROM with ROM Manager.
I have no access to recovery mode, but Emergency mode does work (With and without battery).
I've followed multiple guides, including this one:
My problem is that KDZ still doesn't find my phone after all these attempts - I uninstalled the device driver, then reinstalled it succesfully (B2CAppSetup.exe). I reboot, install msxml.msi, and start KDZ.
Next, I power my phone in Emergency phone, plug it, and it is detected for the first time by the computer. I do have LGE Android Platform Composite USB Device, listed in the Device Manager, as well as LGE Android Platform USB Modem.
Using KDZ, I select the "3GQCT" type, phone mode "DIAG", with the correct KDZ file I've downloaded earlier. Once I launch the software update, phone is not found.
I've tried several times, including desactivating the LG Modem from the Device Manager; unfortunately, when I disable it I need to reboot - I do reboot, but then the LGE Android Platform Composite USB Device is absent from the device manager, and isn't detected by Windows at all, until I fully reinstall the driver (...).
I really don't know what I'm doing wrong - note that I use a laptop with Windows 7 x64; I know laptops handle USB port in a different way than desktops.
Can you help please?
I must be SO close... =(
Thanks, I really appreciate it!
Click to expand...
Click to collapse
First, serious word of advice. Stay away from ROM Manager. It does not handle this device correctly.
It sounds to me like you are not entering Emergency Mode correctly. Yes, the LG USB Modem must be disabled. Power off the device. Press the "Back + Volume Up + Power" buttons together until the device boots to Emergency Mode. Now connect device to you PC/laptop. This can also be done with the battery removed and the device off. Same method except no power button involved. Press the "Volume Up + Back" buttons while attaching your device to your data cable, assuming it's already attached to your PC/laptop.
The attachment I've posted is a stripped down version of the KDZ Updater. All you need to supply is the correct KDZ file for your phone. This one does not require any of LG's other crap software either.
Download to your PC. Extract to a folder of your choosing. Read the ReadMe.txt carefully and follow it's directions to the letter. I just used this to revive two ( 2 ) bricked P506's.
If you can boot to fastboot mode, there is a tool in my signature, Android Flash Recovery, that is designed to flash a recovery to a device with fastboot. So you have two options to restore, revive your device.

shinobisoft said:
First, serious word of advice. Stay away from ROM Manager. It does not handle this device correctly.
It sounds to me like you are not entering Emergency Mode correctly. Yes, the LG USB Modem must be disabled. Power off the device. Press the "Back + Volume Up + Power" buttons together until the device boots to Emergency Mode. Now connect device to you PC/laptop. This can also be done with the battery removed and the device off. Same method except no power button involved. Press the "Volume Up + Back" buttons while attaching your device to your data cable, assuming it's already attached to your PC/laptop.
The attachment I've posted is a stripped down version of the KDZ Updater. All you need to supply is the correct KDZ file for your phone. This one does not require any of LG's other crap software either.
Download to your PC. Extract to a folder of your choosing. Read the ReadMe.txt carefully and follow it's directions to the letter. I just used this to revive two ( 2 ) bricked P506's.
If you can boot to fastboot mode, there is a tool in my signature, Android Flash Recovery, that is designed to flash a recovery to a device with fastboot. So you have two options to restore, revive your device.
Click to expand...
Click to collapse
Hey, cheers !!
That was all I needed to do with this simple version, the update got applied properly, and I saw the FINISHED message.
My phone "rebooted". Well, what I see now if the Android logo with a big " ! ", which is normal according to what I've read.
I will do more ressearch to make sure what I do if correct now: is this safe to power off/reboot at this screen? I believe it's the last step.

GameX2 said:
Hey, cheers !!
That was all I needed to do with this simple version, the update got applied properly, and I saw the FINISHED message.
My phone "rebooted". Well, what I see now if the Android logo with a big " ! ", which is normal according to what I've read.
I will do more ressearch to make sure what I do if correct now: is this safe to power off/reboot at this screen? I believe it's the last step.
Click to expand...
Click to collapse
Yep. Sounds like you're good to go

shinobisoft said:
Yep. Sounds like you're good to go
Click to expand...
Click to collapse
Thanks
Holding the power button does not shut it down - pull the battery, right (It won't screw the thing right before the end ? XD ) ?
Look.. correct:
12 - Start the phone again. If you get stuck in a screen with an Android and an exclamation mark ("!") in a triangle, just unplug the USB cable and the battery. Plug the battery again and start the phone. It will take 2 to 5 minutes to reboot for the first time and the boot animation will be the stock LG (your carrier's stock animation is lost for good), but chances are your phone is intact, with all it's apps and configurations working the same as before the incident. When the boot finishes, turn off the phone again and put back the SD Card you took off on the first step.
Click to expand...
Click to collapse
I really don't want to mess anything at this point.

GameX2 said:
Thanks
Holding the power button does not shut it down - pull the battery, right (It won't screw the thing right before the end ? XD ) ?
Look.. correct:
I really don't want to mess anything at this point.
Click to expand...
Click to collapse
If KDZ Updater says it's done and your device has rebooted to recovery, then yes you can pull the battery to shut it down. You may still need to do the key presses for a factory reset, but the key combo has slipped my mind for the moment. Old age...

shinobisoft said:
If KDZ Updater says it's done and your device has rebooted to recovery, then yes you can pull the battery to shut it down. You may still need to do the key presses for a factory reset, but the key combo has slipped my mind for the moment. Old age...
Click to expand...
Click to collapse
Really nice, I have the Android logo !!
I will wait - people says it can take up to 5-15 minutes or even more - I won't shutdown on the logo.
Letting you know as soon as it's done.
***
After a while, the device booted, and I had a few messages saying it was restoring all the settings!
No data loss! Nothing (I had backed up my contacts and apps on my SD Card already - I was unsure if I would have loose my SMSs, I didn't) is lost !
Dude, seriously, thanks A BUNCH - this is ridiculous, I screwed the phone up at like 10PM yesterday, and did not went to sleep until 2AM because I couldn't fix the thing (I had access to FastBoot at first. I did a process to restore it from Fastboot, it should have worked properly, but then I only had access to the LG logo. Man, I thought I was toasted, and had to spend 50$ for a new phone, just because of a stupid mistake. Never would I thought that SAVING the ROM of my SD card would have screwed up the ROM!)...
I spent like 6 hours today trying to fix it, reinstalling the drivers over and over again... Installing a fresh new Windows XP on a machine, just so I could install everything on a new operating system to figure out the problem...
That was just plain crazy, seriously.
****BONUS****
The first thing I've noticed when I booted my phone was the BLACK notification bar
I really love black, and I once did ressearch a while ago to see if I could turn my white bar into black (I have Android 2.2.1), but no success.
I just realised I got it updated "accidentally" to Android 2.3, and so I was on Android 2.2. since 2011 (when I bought it) !
Well, nice addition, it is sexier with black
I belive it's because of the KDZ file I've used... I had a really hard time to find one, all the links were broken, from 2010, it's a old phone. I found the KDZ from Koodo, Canadian French, exactly my own.
Guess I "accidentally" upgraded to Android 2.3 then Nice addition !
I have no experience at all with fixing Android devices / ROM stuff - I'm used with Windows/Linux and others, but Android (although Android is a version of Linux) is another thing for me.
THANKS - seriously, I wouldn't have made it without your help.
YAY

GameX2 said:
Really nice, I have the Android logo !!
I will wait - people says it can take up to 5-15 minutes or even more - I won't shutdown on the logo.
Letting you know as soon as it's done.
***
After a while, the device booted, and I had a few messages saying it was restoring all the settings!
No data loss! Nothing (I had backed up my contacts and apps on my SD Card already - I was unsure if I would have loose my SMSs, I didn't) is lost !
Dude, seriously, thanks A BUNCH - this is ridiculous, I screwed the phone up at like 10PM yesterday, and did not went to sleep until 2AM because I couldn't fix the thing (I had access to FastBoot at first. I did a process to restore it from Fastboot, it should have worked properly, but then I only had access to the LG logo. Man, I thought I was toasted, and had to spend 50$ for a new phone, just because of a stupid mistake. Never would I thought that SAVING the ROM of my SD card would have screwed up the ROM!)...
I spent like 6 hours today trying to fix it, reinstalling the drivers over and over again... Installing a fresh new Windows XP on a machine, just so I could install everything on a new operating system to figure out the problem...
That was just plain crazy, seriously.
****BONUS****
The first thing I've noticed when I booted my phone was the BLACK notification bar
I really love black, and I once did ressearch a while ago to see if I could turn my white bar into black (I have Android 2.2.1), but no success.
I just realised I got it updated "accidentally" to Android 2.3, and so I was on Android 2.2. since 2011 (when I bought it) !
Well, nice addition, it is sexier with black
I belive it's because of the KDZ file I've used... I had a really hard time to find one, all the links were broken, from 2010, it's a old phone. I found the KDZ from Koodo, Canadian French, exactly my own.
Guess I "accidentally" upgraded to Android 2.3 then Nice addition !
I have no experience at all with fixing Android devices / ROM stuff - I'm used with Windows/Linux and others, but Android (although Android is a version of Linux) is another thing for me.
THANKS - seriously, I wouldn't have made it without your help.
YAY
Click to expand...
Click to collapse
Glad things worked out for ya And helping is what I'm here for

shinobisoft
shinobisoft said:
Yep. Sounds like you're good to go
Click to expand...
Click to collapse
Thanks for helping NOOBS, i appreciate that!

[Q] HKC P776A Android tablet stuck in twrp/cwm bootloop

Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic

parkourgamer said:
Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic
Click to expand...
Click to collapse
Super old I know but my kids tablet is doing this now. Did you ever find a fix?

KilluminatiStyle said:
Super old I know but my kids tablet is doing this now. Did you ever find a fix?
Click to expand...
Click to collapse
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it

janekmuric said:
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it
Click to expand...
Click to collapse
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.

parkourgamer said:
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.
Click to expand...
Click to collapse
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.

janekmuric said:
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.
Click to expand...
Click to collapse
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.

parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
here is the video

parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if

janekmuric said:
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if
Click to expand...
Click to collapse
this is what happens to the .bat fikle when i open it

parkourgamer said:
this is what happens to the .bat fikle when i open it
Click to expand...
Click to collapse
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?

parkourgamer said:
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?
Click to expand...
Click to collapse
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.

janekmuric said:
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.
Click to expand...
Click to collapse
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS

parkourgamer said:
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS
Click to expand...
Click to collapse
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.

janekmuric said:
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.
Click to expand...
Click to collapse
ok will try