Develop Bugs

[RECOVERY] CWM 5.5.0.4 For Acer A100

DISCLAIMER
Thank you to all the DEV'S who have made this possible.
waydownsouth,
gh123man,
hbwelch,
randomblame,
shchers,
Koush
I am in no way responsible for any damage done to your tablet. Follow the instructions!
-----------------------------------------------------------------------------
Here it is guys, Stock CWM Recovery for the ACER A100.
Before anything make sure you have the latest ICS leak C/O Vache, Root, and Unlocked Bootloader.
Official ICS Leak c/o Vache:
http://forum.xda-developers.com/showthread.php?t=1510706
Root Instructions here:
http://forum.xda-developers.com/showthread.php?t=1531646
Unlock your bootloader for fastboot, follow here:
http://forum.xda-developers.com/showthread.php?t=1557445
once you have done all of the above, you should be ready to flash this recovery. Make sure you have ADB up and working properly. And place the recovery.img in your working folder (see below)
1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
This recovery has been tested by myself, and is the first in a series of goodies coming please be patient, dont ask for ETA's as the DEV's are EXTREMELY hard at work and don't even have this device themselves. Big THANKS to all of them!
Now keep in mind most mistakes are made in the location of where you opened the command prompt, just be sure the recovery.img is in the folder you are working in with the command prompt. If it isn't, well, it wont flash anything.
Download CWM Recovery 5.5.0.4 for A100: http://www.mediafire.com/?sgkiz31lg2jd19v
Download A100 ICS Gapps: http://www.mediafire.com/?db2rl0z6v8xc2a8
Follow A100 CM9 progress...Original thread here ---> http://forum.xda-developers.com/showthread.php?t=1597102
Please Hit thanks button of everyone involved, this couldn't be possible without this great community.

First . Testing right now.
Edit: Looking good . One thing... I messed up step 2. I got excited before connecting the device .

Theonew said:
First . Testing right now.
Edit: Looking good . One thing... I messed up step 2. I got excited before connecting the device .
Click to expand...
Click to collapse
lol :-D haha right on man glad my instructions are good. always hard to do a step by step of something you do daily lol. thanks for the feedback! be sure to thank our devs as well.
Sent from my SGH-I897 using xda premium

Well couldn't test much, but everything seems honky dory
One question, should we expect the recovery to be touch enabled later on? .. yeah I know we have buttons, but the touch enabled recoveries are simply cooler anyways, thanks a bunch guys.

ptesmoke said:
thanks for the feedback!
Click to expand...
Click to collapse
The backup is far larger than the ones of the first recovery provided.

Theonew said:
The backup is far larger than the ones of the first recovery provided.
Click to expand...
Click to collapse
could be backing up more data. I think the old Thor recovery had some partitions missing. I will look into it though. pretty sure the old one didn't backup /flexrom which I think the new one does..but I'm not using a flexrom ATM.
Sent from my SGH-I897 using xda premium

Works great thank you very much

ptesmoke said:
could be backing up more data. I think the old Thor recovery had some partitions missing. I will look into it though. pretty sure the old one didn't backup /flexrom which I think the new one does..but I'm not using a flexrom ATM.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
That must be why. The previous recovery made backup sizes of approx. 1.1Gb; This makes backups of well over 2Gb (Bar didn't even reach half way as yet when it hit the 2Gb mark ).

Working great.
Just in case anyone is wondering, flashed fine running flex-100-reaper and crossix SD swap mod.

illego said:
Working great.
Just in case anyone is wondering, flashed fine running flex-100-reaper and crossix SD swap mod.
Click to expand...
Click to collapse
yes i forgot to add. if you are on flexreaper it will work..as you should already have root and unlocked bootloader to get there :-D thanks for verifying though!
i don't want anyone to think they need to reflash the leak and root and unlock again to do this. as long as your on the ics bootloaders and unlocked then your good...no matter what rom you have loaded.
Sent from my SGH-I897 using xda premium

Theonew said:
That must be why. The previous recovery made backup sizes of approx. 1.1Gb; This makes backups of well over 2Gb (Bar didn't even reach half way as yet when it hit the 2Gb mark ).
Click to expand...
Click to collapse
Just ran the whole backup.
Old backup: 1.4Gb
New backup: 4.0Gb

illego said:
Just ran the whole backup.
Old backup: 1.4Gb
New backup: 4.0Gb
Click to expand...
Click to collapse
looking into it..may not be .tar
Sent from my SGH-I897 using xda premium

ptesmoke said:
looking into it..may not be .tar
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
It is ".tar".

Theonew said:
It is ".tar".
Click to expand...
Click to collapse
k so my backup is 300mb...
but I'm not on a flex rom. do me a favour do a backup and once done do an " adb logcat > logcat.txt " and pm me the txt file..plz
Sent from my SGH-I897 using xda premium

ptesmoke said:
k so my backup is 300mb...
but I'm not on a flex rom. do me a favour do a backup and once done do an " adb logcat > logcat.txt " and pm me the txt file..plz
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
A full backup or just /data?

Theonew said:
A full backup or just /data?
Click to expand...
Click to collapse
My guess would be repeat the process that netted you a 4 gb backup
Sent from my Kindle Fire using Tapatalk 2

jamminjon82 said:
My guess would be repeat the process that netted you a 4 gb backup
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Wasn't me. Anyways, that would be a full backup.

anyone on a flex rom. so anyone :-D and yes full backup plz.
Sent from my SGH-I897 using xda premium
edit: nvm dont need log. looks like its backing up the /data/media partition
stay tuned.....workin on it. I didnt notice as i wiped all my partitions...hence my low backup size.

ptesmoke said:
anyone on a flex rom. so anyone :-D and yes full backup plz.
Sent from my SGH-I897 using xda premium
edit: nvm dont need log. looks like its backing up the /data/media partition
stay tuned.....workin on it. I didnt notice as i wiped all my partitions...hence my low backup size.
Click to expand...
Click to collapse
I was going to say my backup was the right size on Flexrom A100, but it would make sense because I use the Micro SD card swap mod. So my /data/media is empty while in CWM.

Gibson.Dubs said:
I was going to say my backup was the right size on Flexrom A100, but it would make sense because I use the Micro SD card swap mod. So my /data/media is empty while in CWM.
Click to expand...
Click to collapse
your 100% correct :-D . working on a fix right now. any other bugs? can everyone mount USB in recovery? mine doesn't work but I'm having mtp driver issues last few days
Sent from my SGH-I897 using xda premium

How to factory reset my gs2 using adb

Im selling it but it has a crack screen dat i cant see wat are the commands for adb to delete everything so wen they fix it n turn it on it gives rhem a wwlcome screen?
Sent from my SGH-T989 using XDA

Just go to menu- settings- privacy- factory reset. Bam done.
Sent from my SGH-T989 using xda premium

Madblaster6 said:
Just go to menu- settings- privacy- factory reset. Bam done.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I cant do it or else i would of done that my screen is pitch black plus the digitizer doesnt work
Sent from my SGH-T989 using XDA

Bump
Sent from my SGH-T989 using XDA

A wild stickied thread appears! http://forum.xda-developers.com/showthread.php?t=1513359
Sent from the darkside of my Galaxy S III.

danielblakes said:
A wild stickied thread appears! http://forum.xda-developers.com/showthread.php?t=1513359
Sent from the darkside of my Galaxy S III.
Click to expand...
Click to collapse
Im trying to leave it rooted as i stated it to the potential sbuyers i just want my data n everything wipe n since i cant see the screen n the digitizer doesnt work my best bet was to use adb but im sure if the command for adb is
Adb shell
Format data
Format cache
Trying to see this is it because i dont want it to boot loop orcanything cuz i did somerhing wrong
Sent from my SGH-T989 using XDA

hazy4days said:
Im selling it but it has a crack screen dat i cant see wat are the commands for adb to delete everything so wen they fix it n turn it on it gives rhem a wwlcome screen?
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Yo, run ddms from where you android-sdk is. Go to Tools and DDMS will be right there. On the top right you have options to portrait the screen. You may use that.

alphadog32 said:
Yo, run ddms from where you android-sdk is. Go to Tools and DDMS will be right there. On the top right you have options to portrait the screen. You may use that.
Click to expand...
Click to collapse
Thanks
Sent from my SGH-T989 using XDA

Interesting.
alphadog32 said:
Yo, run ddms from where you android-sdk is. Go to Tools and DDMS will be right there. On the top right you have options to portrait the screen. You may use that.
Click to expand...
Click to collapse
Well, this is good to know. I have never used this and can see how it could be useful in a bad screen situation. very cool.

hazy4days said:
Im trying to leave it rooted as i stated it to the potential sbuyers i just want my data n everything wipe n since i cant see the screen n the digitizer doesnt work my best bet was to use adb but im sure if the command for adb is
Adb shell
Format data
Format cache
Trying to see this is it because i dont want it to boot loop orcanything cuz i did somerhing wrong
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Its
adb shell
wipe data
wipe cache
reboot
its done

[Q] Help to fix my phone

I used a video to unroot my phone and now it will not come out of boot mode, I turn it on it acts like it is booting up but never does just stays in the same position. and when I try to go into fastboot mode I get an error, it shows an android laying down and a red triangle over him how do I fix this? PLEASE HELP

follow this exactly as its written: http://forum.xda-developers.com/showthread.php?t=1626895

I will try this, but I am not sure that the computer is reading the phone, I can get odin to work but it is not helping I tried putting stock files using odin but same thing. when i tried cmd and fastboot devices it brings up nothing

when I plug my phone in my computer does not recognize it, now what do I do?

Zepius said:
follow this exactly as its written: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
did everthing step by step, I am able to see the device in my device manager, but when I get to the part where I put it in bootloader and and type fastboot devices it does not recognize it. any suggestions?

pamelak38 said:
did everthing step by step, I am able to see the device in my device manager, but when I get to the part where I put it in bootloader and and type fastboot devices it does not recognize it. any suggestions?
Click to expand...
Click to collapse
You need to install the fastboot driver.
Sent from my Galaxy Nexus using Tapatalk 2

Petrovski80 said:
You need to install the fastboot driver.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I cannot turn my phone on to put it on usb debugging, could this be my problem? and how do I install fastboot driver I thought I had it with sdk tools

pamelak38 said:
I cannot turn my phone on to put it on usb debugging, could this be my problem? and how do I install fastboot driver I thought I had it with sdk tools
Click to expand...
Click to collapse
When you are booted into bootloader but a "fastboot devices" does not list your device, it's almost always caused by having installed either no driver at all or the wrong one. Use the naked driver, follow the link in my signature to find it.
Sent from my Galaxy Nexus using Tapatalk 2

Petrovski80 said:
When you are booted into bootloader but a "fastboot devices" does not list your device, it's almost always caused by having installed either no driver at all or the wrong one. Use the naked driver, follow the link in my signature to find it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ok I got it up and running! My only concern is I did every step but the radio step failed every time, is this a problem?????
THANK YOU SO MUCH, I HAVE LEARNED A LOT FROM THIS!!

pamelak38 said:
Ok I got it up and running! My only concern is I did every step but the radio step failed every time, is this a problem?????
THANK YOU SO MUCH, I HAVE LEARNED A LOT FROM THIS!!
Click to expand...
Click to collapse
Lte radio? Anyway if your connection is ok I'd say it's not an issue.
Good you figured it out.
Sent from my Galaxy Nexus using Tapatalk 2

still cant get into recovery mode
can anyone help, I got the phone back to where I can get into it, but if I try to go into recovery mode I still get the dead android with the red triangle and can anyone tell me where to find a lte radio

pamelak38 said:
can anyone help, I got the phone back to where I can get into it, but if I try to go into recovery mode I still get the dead android with the red triangle and can anyone tell me where to find a lte radio
Click to expand...
Click to collapse
What you see is the stock recovery. Android will flash it back automatically even after you've flashed a custom recovery. To prevent this, you must either rename/delete /etc/install-recovery.sh OR rename/delete /system/recovery-from-boot.p.
LTE radios are in the factory images. Read this: http://forum.xda-developers.com/showthread.php?t=1626895

Petrovski80 said:
What you see is the stock recovery. Android will flash it back automatically even after you've flashed a custom recovery. To prevent this, you must either rename/delete /etc/install-recovery.sh OR rename/delete /system/recovery-from-boot.p.
LTE radios are in the factory images. Read this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Ok, I have never had to rename/delete,ect before, can you help walk me thru that, I know I am asking a lot but I would sure appreciate it

pamelak38 said:
Ok, I have never had to rename/delete,ect before, can you help walk me thru that, I know I am asking a lot but I would sure appreciate it
Click to expand...
Click to collapse
Do you have root? In that case it's a matter of launching your file manager.
Sent from my Galaxy Nexus using Tapatalk 2

Petrovski80 said:
Do you have root? In that case it's a matter of launching your file manager.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes I have root, now what do I need to do?

pamelak38 said:
Yes I have root, now what do I need to do?
Click to expand...
Click to collapse
Navigate to the folder /etc with a file manager. Remount with RW rights (root explorer has a convenient button for this) and rename the file install-recovery.sh to install-recovery.sh.bak.
Then reflash a custom recovery. This time it will stick.
Sent from my Galaxy Nexus using Tapatalk 2

Petrovski80 said:
Navigate to the folder /etc with a file manager. Remount with RW rights (root explorer has a convenient button for this) and rename the file install-recovery.sh to install-recovery.sh.bak.
Then reflash a custom recovery. This time it will stick.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I got it back to stock and locked, THANK YOU so much you are awesome!!!!

[HOWTO]Recover From a Bad Flash - Now automated

Ok so you accidentally tried to Odin or CWM the wrong file to your phone. Well the good news is that if you can get into CWM with access to the sdcard(s) or access ADB we can fix it. If the phone won't power on at all, you can't access cwm with sdcard(s), ADB or Odin you are unfortunately out of luck. You will need to get it repaired by Sprint or send it off for a jtag repair.
Disclaimer: I am not responsible for anything that happens to your phone. You do this at your own risk.
If you don't own the E4GT do not use this guide because if your partitions are not the same as ours you will brick your phone.
If by chance you can get into Odin mode and your computer can see the phone go buy a lottery ticket J/K. All you have to do is download a full tar and Odin it back on. I won't go into details for that as it is well documented. Or you can still use this zip if you prefer.
I have automated the process of the restore. What this zip will do is flash the Agat 0.5.4 source kernel so you have cwm. It will flash the FH13 boot.bin, hidden.img, param.lfs and Sbl.bin. It will wipe Cache and Dalvik also.
This will not flash the modem, wipe data or replace system. So after you use this zip if your modem is also hosed flash a modem zip from CWM. Once you have recovered the phone you can flash whatever you want back on the phone.
Download CWM Odin Restore To FH13: http://d-h.st/3yZ
Copy the zip file to your phone and flash in custom recovery.
If you don't have access to the sdcard(s) but do have access to ADB proceed to the second post.
If you need some direct assistance you can PM me and I will work with you when possible.

You only have ADB access
For this method you will need CWM, ADB, Root and the image files to restore.
If you don't have ADB installed I have attached it to this post. I have also provided a link to the FH13 image files.
If you don't have ADB, extract the ADB directory to the root of C:. So you should see C:\ADB
You need to know where your ADB directory is located. If you used step 1 ADB it is C:\ADB. If you installed it on your own you should know where to find it.
Extract the images.zip into the ADB directory. You should now have the Images folder in the ADB folder.
Boot into CWM and attach your phone to the computer.
Open a command prompt and change directory to the ADB directory cd C:\ADB (or wherever your directory is).
Type adb push Images /tmp and hit enter.
You should see something like 6 files pushed. 0 files skipped.8465 KB/s (19271020 bytes in 2.223s).
Type adb shell and hit enter.
This part is critical. Make sure it is typed exactly or you can/will destroy your phone.
Copy and paste or type the following commands. If you copy and paste make sure you don't copy any leading or trailing spaces. Hit enter after each command.
You can skip any of the following commands if you know you don't need them. For example, if you know you only installed the Sbl.bin then you only need to enter that command. I have provided them all to cover all of the needs. If you are not sure just do them all.
dd if=/tmp/boot.bin of=/dev/block/mmcblk0p0
dd if=/tmp/hidden.img of=/dev/block/mmcblk0p12
dd if=/tmp/param.lfs of=/dev/block/mmcblk0p4
dd if=/tmp/Sbl.bin of=/dev/block/mmcblk0p2
dd if=/tmp/zImage of=/dev/block/mmcblk0p5
dd if=/tmp/zImage of=/dev/block/mmcblk0p6
You should see something like 2560+0 records in, 2560+0 records out, 1310720 bytes (1.3MB) copied, 0.265521 seconds, 4.7MB/s after each command.
Reboot your phone and it should boot up.
If it still doesn't boot something didn't take and we will need to work one on one.
Download the Images.zip: http://d-h.st/8gY

The bootloader restore has been proven to work on one phone so far. Thanks to pjkingphd for testing and confirming that it works.

great share!thanks for the tutorial.

crawrj said:
Please sticky this thread.
Click to expand...
Click to collapse
Hopefully this will be done.
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2

Crawrj my man.
Tappin' Typin'

md5 sums might be nice. Don't want bricked phones due to bad downloads.
Sent from my Galaxy Nexus using xda app-developers app

times_infinity said:
md5 sums might be nice. Don't want bricked phones due to bad downloads.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
But then we wouldn't have anyone to test this... would we..
Great tutorial crawrj
Sent from my SPH-D710 using Xparent Blue Tapatalk 2

Very nice. Thank you.

times_infinity said:
md5 sums might be nice. Don't want bricked phones due to bad downloads.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If the md5 is not right it will say so when you try to restore in cwm. It won't restore if they don't match. But I can throw up md5 for the sbl.
Sent from my SPH-D710 using xda premium

MD5 added. Sticky this please.

I have now automated the restore process in a zip file. You must be able to copy the zip file to the phone for it to work. I have flashed it about a dozen times but I would like to get a few brave testers to try it on your phone for me. Make sure you do a backup first! I have moved the manual commands to post two and revamped the instructions.

+1
Sticky or move to original development.
Sent from my piece of crap Zio until i get my E4GT back from Samsung, using XDA Premium app

Thread stuck. Thank you for helping out the community. :highfive:

jayharper08 said:
Thread stuck. Thank you for helping out the community. :highfive:
Click to expand...
Click to collapse
Thank you sir :highfive:

Sooo... uhm ,,, say I know a certain someone who botched their custom boot logo and has been lazy..... and has the draw failure start up...
This would restore that to stock without any other ramifications except for a kernel swap, correct??
Edit: Guess after a day Ill just assume yes and hope it cant brake anything....

PhAkEer said:
Sooo... uhm ,,, say I know a certain someone who botched their custom boot logo and has been lazy..... and has the draw failure start up...
This would restore that to stock without any other ramifications except for a kernel swap, correct??
Edit: Guess after a day Ill just assume yes and hope it cant brake anything....
Click to expand...
Click to collapse
Yeah this will fix you up. Once you get recovered you can flash whatever you want back on. Since you are an advanced user if you have a particular setup that you want to restore, just pull those files from the tar and place them in the Images folder of the zip.

You never can be too sure.. Lol I just always expect the one time I make an assumption will be regretted.
Good idea btw... And thanks.
And Ive actually been meaning to flash a param.lfs..... I have like 4 OCs it just they are all the way on my backup backup card ...(see my level of sloth ?!?!?!)

PhAkEer said:
You never can be too sure.. Lol I just always expect the one time I make an assumption will be regretted.
Good idea btw... And thanks.
And Ive actually been meaning to flash a param.lfs..... I have like 4 OCs it just they are all the way on my backup backup card ...(see my level of sloth ?!?!?!)
Click to expand...
Click to collapse
LOL nice. Let me know how it turns out.

crawrj said:
LOL nice. Let me know how it turns out.
Click to expand...
Click to collapse
Good as gold, as expected. I did end up only using the param.lfs but Im sure the rest will work great when I need it =)
Thanks again.... Itd been a long time since I last saw that sweet , sweeet gaudi_bootimage.jpg
Sent from my SPH-D710 using xda premium

[Q] Accidentally deleted OS/System?

I accidentally wiped my rom off my Maguro Galaxy Nexus.
Now its stuck on the bootscreen and I need help on how to push a ROM zip file to the phone because i dont have one on it.

Boot in your recovery and push a ROM with adb
Sent from my Nexus 7 using xda app-developers app

is this possible using the nexus toolkit

Use Toolkit and flash stock rom it'll definetly work.
Sent from my Galaxy Nexus using xda app-developers app

Mertowski said:
Use Toolkit and flash stock rom it'll definetly work.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yes it would work, but he just has to push a ROM with adb.
Its just one f***ing command.
I told him what to do, but he's too lazy too Google it and I won't spoon feed him with a step by step guide. There are enough out there.

Mertowski said:
Use Toolkit and flash stock rom it'll definetly work.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Thanks man. Solved it by flashing a factory image with the toolkit
c.m.b said:
Yes it would work, but he just has to push a ROM with adb.
Its just one f***ing command.
I told him what to do, but he's too lazy too Google it and I won't spoon feed him with a step by step guide. There are enough out there.
Click to expand...
Click to collapse
Sorry dude. I tried the adb method but it didn't recognise the command. Probably because I didn't have the driver or something. Thanks anyways.

neevian said:
Thanks man. Solved it by flashing a factory image with the toolkit
Sorry dude. I tried the adb method but it didn't recognise the command. Probably because I didn't have the driver or something. Thanks anyways.
Click to expand...
Click to collapse
Lol, it didnt recognize the command because you didnt have adb binary in your PATH variable.
Sent from my i9250

neevian said:
is this possible using the nexus toolkit
Click to expand...
Click to collapse
Stop using toolkits. I almost guarantee that's how you "accidentally" wiped your system.

Some people don't have the time to annoy them with all the adb or fastboot stuff
Sent from my Galaxy Nexus using xda premium

Man_u said:
Some people don't have the time to annoy them with all the adb or fastboot stuff
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Then those people shouldn't be messing with their phone
Sent from my Galaxy Nexus using Tapatalk 2

Zepius said:
Then those people shouldn't be messing with their phone
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Then you are saying everyone who doesnt want to learn command lines shouldnt have access to rooting and flashing new roms to their phone. Toolkits are easy and fast when you are in trouble and need to get back to stock. There isnt anything wrong with using them just because you dont have to put a command line in.

MartianCeo said:
Then you are saying everyone who doesnt want to learn command lines shouldnt have access to rooting and flashing new roms to their phone. Toolkits are easy and fast when you are in trouble and need to get back to stock. There isnt anything wrong with using them just because you dont have to put a command line in.
Click to expand...
Click to collapse
Do you read these forums? So many people could fix their problems with a couple commands, but they have no idea how to do anything because of these toolkits. They make the user lazy and ignorant.
Sent from my Galaxy Nexus using Tapatalk 2

Zepius said:
Do you read these forums? So many people could fix their problems with a couple commands, but they have no idea how to do anything because of these toolkits. They make the user lazy and ignorant.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Anyone coming into the android rooting, flashing roms, ect are kind of ignorant because they dont know everything. If we stay in the days of only using command lines and not coming up with faster ways to help our devices then that is being ignorant. There is just more than one way to do something. Just because someone uses a faster way it doesnt make then lazy but makes them open to new ways of doing things...

MartianCeo said:
Anyone coming into the android rooting, flashing roms, ect are kind of ignorant because they dont know everything. If we stay in the days of only using command lines and not coming up with faster ways to help our devices then that is being ignorant. There is just more than one way to do something. Just because someone uses a faster way it doesnt make then lazy but makes them open to new ways of doing things...
Click to expand...
Click to collapse
Using a toolkit is what is ignorant. With adb it is virtually impossible to "accidentally" do anything. Anybody who believes toolkits to be superior is either an idiot or too lazy to learn adb.

i would say that i have always tried to learn here, thats my goal , i dont know about other people and i dont criticize them , but it really frustrates me if i dont know whats going on when i am doing something. still TOO MUCH to learn:good:

Toolkit is only faster if you don't know how to use adb/ fastboot. Its only faster because you don't know what you're doing it takes me the same amount of time typing commands than using a toolkit basically I'm just waiting for the files to flash and move on to the next step. It isn't like when you're using a toolkit it can magically type and execute all the commands at the same time there is still a process being done.
Sent from my Galaxy Nexus using xda premium

You could use GNex toolkit that works realy good
Send from my Galaxy Nexus running the latest version of PA using xda premium