What do you guys think?
Sent from my Galaxy Nexus using xda app-developers app
dead ? as dead as me I should say :laugh:
There's root, CWM and Cyanogen so it doesn't seem very dead to me!
Just not highly active, but not dead at all.
I don't believe its going to be heavily developed for truthfully, although some are trying.
The real action will be with the Asus Infinity, and the Nexus 7 (which is one of the reasons I bought one)...
I may sell the Acer once the next gen Samsung tablet comes out.
Yes im seeing the same with the asus' i really like my a700 since im not getting all those issues.
The only funny thing is that dead trigger is kind of slow, but shadow gun runs nicely as well as real racing runs really smooth.
I haven't tried root and so on yet because i heard of bricked devices?
Sent from my A700 using XDA
Not so much the root portion as the recovery options.
The newest CWM recovery seems to have the issues fixed, but now we need to have ROMs developed.
And the ones doing all this are getting their tablets fixed at the moment, which is why its slooooow here.
Yeah, no issues here expect some mild heat during heavy gaming which isn't even that bad with the newer updates.
Although now I game on the Nexus 7 (better size) and use the Acer to surf the web, watch movies and listen to music.
It is a great tablet just very overlooked at the moment.
I do hope they stick around and do some development for it to unlock its potential.
Yeah that's right I love the device I had the prime and the new iPad but this is my favorite ! Ah okay I didn't know that there where other developers around.
Sent from my Galaxy Nexus using xda app-developers app
actually the A510 is really dead compare with A700. just root and testing CWM.
my bricked A510 have no way to rescue.:crying:
Oh dang sorry to hear that did u try to send it back ? Yeah its bad that these devices are so overlooked..... somehow everyone is on the Asus hipe....
Sent from my Galaxy Nexus using xda app-developers app
Tawitp is developing a rom but he has bricked his tab - so untill he has got it back there is his alpha rom atm which - despite the portrait mode bug - is my daily driver (due to my tf300t still broken).
its a nice rom and everything works sans portrait mode
so i hope he gets its tab back soon so we will have a nice cm10 rom growing here
I was thinking on putting the rom on my a700 also but i have some unanswered question. First can i flash back to stock without an issue? Its a german device? And second is the rom much more smooth than stock? I have the galaxy nexus with jelly bean and there are worlds between the both but the a700 issn't laging at for example homescreen?
Sent from my A700 using xda app-developers app
MACBLACK91 said:
I was thinking on putting the rom on my a700 also but i have some unanswered question. First can i flash back to stock without an issue? Its a german device? And second is the rom much more smooth than stock? I have the galaxy nexus with jelly bean and there are worlds between the both but the a700 issn't laging at for example homescreen?
Sent from my A700 using xda app-developers app
Click to expand...
Click to collapse
Smoother yes. So far only the portrait issue. Like i said its my daily driver for now. Some games work in portrait mode. Flipboard google now and spotify dont for example.
Since i dont wana go back to stock i did not try but there are some stock images here so you probably can go back if you want
Cheers
Sent from my A700 using xda app-developers app
Buster99 said:
Smoother yes. So far only the portrait issue. Like i said its my daily driver for now. Some games work in portrait mode. Flipboard google now and spotify dont for example.
Since i dont wana go back to stock i did not try but there are some stock images here so you probably can go back if you want
Cheers
Sent from my A700 using xda app-developers app
Click to expand...
Click to collapse
Okay I will give it a try, but can someone help me with the bootunlocker or let me say it like this to flash the custom rom i need to unlock the boot loader than root? and than install cwm? and where can I download the android sdk?
MACBLACK91 said:
Okay I will give it a try, but can someone help me with the bootunlocker or let me say it like this to flash the custom rom i need to unlock the boot loader than root? and than install cwm? and where can I download the android sdk?
Click to expand...
Click to collapse
Sdk from google(android.com)cwm and the rom from pawitp threat (read carefully) unlocking theres a thread as well all in the dev section
Unlock, install cwm, make nandroid, flash rom and gapps, reboot and have fun
Cheers
Sent from my A700 using xda app-developers app
I'll try in short terms .
Download and install Android SDK: http://developer.android.com/sdk/index.html
After install open it as administrator and let it update the main packages in "Tools". Choose in section "Extras" "Google USB Drivers" (not sure if really needed). You don't need the rest (i hope I have it cause I'd start developing apps). You may need to reopen Android SDK for further updates (it will tell you).
If not done in the past, install the Acer A700 USB driver (you can access the internal sdcard without them, so don't be fooled by windows).
Activate "usb debugging" under settings -> developeroptions and connect your A700 via usb to your computer
Open a console on windows and type "adb devices" [enter]. It should list something like this
Code:
C:\Users\Mechkilla\adb devices
List of devices attached
22212345678 device
if not ... search or ask .
Unlook bootloader: http://forum.xda-developers.com/showthread.php?t=1710755
Install CWM: http://forum.xda-developers.com/showthread.php?t=1791165
Hope it helps, mechkilla
thanks u both!!! but I have one stupid question the terminal, do u mean the one from windows? because it keeps telling me that the command is wrong?! adb devices
Yes windows. Ok, forgot about that ... if you not put the path in your environment variables from windows you have to go to:
C:\Program Files x86\Android\android-sdk\plattform-tools
There you can find the commands adb and fastboot.
somehow mine is here C:\Users\MACBLACK\AppData\Local\Android\android-sdk\platform-tools and if I click on adb or fastboot it just opens and closes real fast... im probably getting on your nerves
okay i reinstalled it and now its in the right path
those are console commands not for clickediclick .
Mechkilla said:
I'll try in short terms .
Download and install Android SDK: http://developer.android.com/sdk/index.html
After install open it as administrator and let it update the main packages in "Tools". Choose in section "Extras" "Google USB Drivers" (not sure if really needed). You don't need the rest (i hope I have it cause I'd start developing apps). You may need to reopen Android SDK for further updates (it will tell you).
If not done in the past, install the Acer A700 USB driver (you can access the internal sdcard without them, so don't be fooled by windows).
Activate "usb debugging" under settings -> developeroptions and connect your A700 via usb to your computer
Open a console on windows and type "adb devices" [enter]. It should list something like this
Code:
C:\Users\Mechkilla\adb devices
List of devices attached
22212345678 device
if not ... search or ask .
Unlook bootloader: http://forum.xda-developers.com/showthread.php?t=1710755
Install CWM: http://forum.xda-developers.com/showthread.php?t=1791165
Hope it helps, mechkilla
Click to expand...
Click to collapse
Use the cwm in pawitp alpha rom thread.. thats the only one that has been tested anduses rm instead of format to not destroy the /data partition.
I used that and no probs here - just as a warning since he said himself that one of his cwms did not work properly
Cheers
Sent from my A700 using xda app-developers app
hey guys thanks very much for the help I made it i got one question is it normal that the alpha is using ~550mb ram? without any app open?
Related
Hi, last night i decided to flash a new kernal after the feature became available via Rom Manager. I tried to flash the kernal to which i was prompted with "insufficiant storage space, please reboot" so i did as asked and now im stuck in fastboot,bootloader? I can't access CWM to reflash and i have no idea to push a new recovery.img using a Mac 10.4.
I can get access to a windows PC, could anyone help me out with sorting this out. quite worried im now the owner of an expensive paper weight
Cheer
When you rooted the device you fastboot the recovery the first time then used recovery to flash the su. Just do that same method again. If not just look in the sticky of the development section for the many guides.
ok cheers will try that
When plugging in the device on the bottom of the nexus s screen it says "USB control init" "USB control init end" what does this mean as currently all that shows up in device manager is "Android 1.0" shouldn't it say Nexus S? Btw I used team wins' kernal app which obviously is a piece of ****. Never had a problem flashing within CWM
Sent from my Nexus One using XDA App
Ok pdanet solved that problem
Sent from my Nexus One using XDA App
It's also kernel not a kernal
Sent from my Nexus S using XDA Premium App
zephiK said:
It's also kernel not a kernal
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I don't think a mis-spelling of kernel contributes to the issue. Is this forum populated by pedagogues?
I just unbricked your phone
Here you go.
Yeah **** you grammar troll!!!
Nice one dude you are the best! Ill pop around tomorrow to collect
Sent from my Nexus One using XDA App
There was no way to move the recovery img to the phone by fastboot; this was completely shot. Fortunately there's a separate download mode hack you can use by plugging the phone into USB and holding vol up AND down simultaneously. This opens up a separate Samsung Composite Device which allows you to flash with Odin - Samsung's own flashing/debricking software This failed the first few times but after a few device driver reinstalls it flashed the bootloader, PDA and CSC files and booted quite happily.
leoni1980 said:
I don't think a mis-spelling of kernel contributes to the issue. Is this forum populated by pedagogues?
Click to expand...
Click to collapse
Mis-spelling? Kernal and Kernel are actually two different things:
http://en.wikipedia.org/wiki/KERNAL
The KERNAL is Commodore's name for the ROM-resident operating system core in its 8-bit home computers; from the original PET of 1977, followed by the extended but strongly related versions used in its successors; the VIC-20, Commodore 64, Plus/4, C16, and C128.
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Linux_kernel
The Linux kernel is an operating system kernel used by the Linux family of Unix-like operating systems.[6] It is one of the most prominent examples of free and open source software.[7]
Click to expand...
Click to collapse
And I'm no where close to being a "grammar troll." In fact, I wasn't even judging about your grammar. You were talking about a kernal when its a kernel. They're two different things. And I've helped many people in regards to the topic of fastboot and recovery. I was simply just clarifying on "kernel." I only posted it to to help you out by knowing its a 'kernel' not a 'kernal.' Sorry if that insulted you
That's just being pedantic.
Hi,
As most of you probably already know by now, I have released a fully functional nvflash for Transformer yesterday
More information is available at http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
UPDATE 15-06-2011:Bumble-Bee (Apache14) is just as much to thank for this as me! Both of us (from AndroidRoot.Mobi) have worked hard on making this happen! Thanks to Roach for providing the nvflash-ready Prime 1.4 ROM!
UPDATE: The Prime 1.4 linked is European (WW) build! Roach will release 1.5 soon probably and there'll be both WW and US available. I'm planning to write a quick guide on how to root when running stock 3.1 already (it's pretty easy!)! E.g. to stay on full stock and *just* have root
Windows nvflash
Linux nvflash
Quick guide to unbricking:
Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
(Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
Run download.sh (linux) or download.bat (windows)
???
Profit
Awesome! Thanks a lot!!
rayman84 said:
Hi,
As most of you probably already know by now, I have released a fully functional nvflash for Transformer yesterday
More information is available at http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
Windows nvflash
Linux nvflash
Quick guide to unbricking:
Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
(Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
Run download.sh (linux) or download.bat (windows)
???
Profit
Click to expand...
Click to collapse
WOW, It's "just like that"? Really that's all what you have to do to unbrick a device? I guess times when flashing roms was dangerous have passed
Great job
Very thanks and keep up the good work!!!
unbrick tool came before root tool. lol
but it's a very useful program for all of us.
thanks for this!
i have a question though, my Samsung Vibrant was HARDWARE LOCKED, which makes button combinations to enter recovery/download modes impossible.
Is there any possibility that my TF has a hardware lock too which will prevent me from accessing the USB when it gets bricked?
i have experience in rooting and/or jailbreaking but i havent rooted my TF yet, coz the only way to root right now is kind of "not layman friendly". and i hate the terms BLOBS. lol
thank you.
So I'm rooted running prime 1.4 could some one explain in laymans terms what difference this makes to me and what if anything I need to do to benefit to my TF
DESIRE HD using leedroid. ASUS TRANSFORMER using prime
atlaswingpasaway said:
unbrick tool came before root tool. lol
but it's a very useful program for all of us.
thanks for this!
i have a question though, my Samsung Vibrant was HARDWARE LOCKED, which makes button combinations to enter recovery/download modes impossible.
Is there any possibility that my TF has a hardware lock too which will prevent me from accessing the USB when it gets bricked?
i have experience in rooting and/or jailbreaking but i havent rooted my TF yet, coz the only way to root right now is kind of "not layman friendly". and i hate the terms BLOBS. lol
thank you.
Click to expand...
Click to collapse
Either you didn't read the post or you might be dyslexic. If you unbrick your device you're pushing a custom ROM which means you automatically get root.
combat goofwing said:
So I'm rooted running prime 1.4 could some one explain in laymans terms what difference this makes to me and what if anything I need to do to benefit to my TF
DESIRE HD using leedroid. ASUS TRANSFORMER using prime
Click to expand...
Click to collapse
You don't need this your already rooted. This is a easy way to root and it can also revive bricks, custom flash different partitions and who knows what other functions can be done with nvflash.
Sent from my HTC Vision using XDA Premium App
Will this wipe your data partition if using this to get a rooted custom rom on?
seshmaru said:
Either you didn't read the post or you might be dyslexic. If you unbrick your device you're pushing a custom ROM which means you automatically get root.
Click to expand...
Click to collapse
it might be both! lol sorry my bad.
im new to tablet/honeycomb rooting so i dont know much about this.
so... im on stock 3.1 right now (i guess the build number wont matter anymore?)
and no root. should i just follow the OP instructions or what?
Canadoc said:
Will this wipe your data partition if using this to get a rooted custom rom on?
Click to expand...
Click to collapse
Using the script included it will wipe all user data. But it may be tweaked later.
Sent from my HTC Vision using XDA Premium App
atlaswingpasaway said:
it might be both! lol sorry my bad.
im new to tablet/honeycomb rooting so i dont know much about this.
so... im on stock 3.1 right now (i guess the build number wont matter anymore?)
and no root. should i just follow the OP instructions or what?
Click to expand...
Click to collapse
Yes if u want a custom rom with root. No more downgrading firmwares anymore like before
Cannot mount SD card in clockwork mod?
EDIT: Nevermind. I tried a different microsd card and it worked fine. False alarm... Move along... nothing to see here
I used the NVFlash utility to flash Prime 1.4 without a hitch but now that I'm trying to deploy the overclock kernel clockwork mod is not playing nice. I get an error E: Can't mount /sdcard when trying to choose a zip file. My understanding is that /sdcard is not the microsd anyway. How do I resolve this? I already tried reformatting the microsd card on my pc but that didn't solve the issue.
Thanks!
-Matt
I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App
david279 said:
I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
/Removable/MicroSD/ is the MicroSD card slot on the TF104
/SDCard is the 30gigs on the 32gb NAND
Also check the CWM installed. If it's the old one it erases your sd card and internal card on data wipes. You don't want that.
Sent from my HTC Vision using XDA Premium App
david279 said:
I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
It's /Removable/MicroSD
But I think the key thing here is that /sdcard is whatever the booting process mounts as /sdcard. This is why CWM has no problem listing the zip files for ROMs, etc. as being from the sdcard. It has accessed it through the actual block device which doesn't change. The whole internal sdcard that we see is some trickery that allows us to have access to all the space on our internal memory, but CWM doesn't know or care about that.
Sent from my Transformer TF101 using XDA Premium App
So...
No rooting, and no CWM..
Just use the tools and profit?
It flashes CWM for future flashing fun.
Sent from my HTC Vision using XDA Premium App
i just dont seem to get it.. . so does this give my stock 3.1 root?
Guys so i wanted to root my phone and
1) i just didnt have to patience to do all the work
2) i didnt get some stuff
3) and i wanted to do this quickly and effectively
i found this youtube video after like an hour of searching and it worked GREAT. [Video and end of post]
-----------------------------------------------------------------------------
pretty much the instructions are to:
Download the drivers first *NECESARRY*******IMPORTANT. this is one of the ke things cause without this is wont work in the beginning
*JUST A MENTION*
i tried doing this on my 64 bit system and it wasnt as easy when i did it on my 32 bit.
so it could have just been my comp.
just a heads up.
64 bit driver:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
32 bit.
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
After that you're going to download this file:
http://tinyurl.com/Sidekick4GALLinOne
this is the file/folder whatever that will root your sidekick and add the CWM.
^^^^^^^^^^^^^^^^^^^REQUIRES WINRAR^^^^^^^^^^^^^^^^^
-----------------------------------------------------------------------------
Ok so to start rooting and the CWM
1) You're going to install the the driver that you download...64 bit or 32 bit etc.
2) after that you're going to set your phone to "USB DEBUGGING" when connect and ofcourse
connect your phone
after that your open up the folder thats called "sk4g root with good recovery"
3) ignore everything you see and just go straight to run.bat
4) click it and then wait, "Press any key to continue" press anything
5) let the thing run and you should be set at the end.
ENJOY
-----------------------------------------------------------------------------
your phone will reboot during the process and that is ok
-----------------------------------------------------------------------------
if your doing this to install a new rom i recommend ayoteddy's GingerCloneV2. if great and has barly any glitches
-----------------------------------------------------------------------------
SOURCE AND VIDEO:
http://www.youtube.com/watch?v=wYC8XRqM-no&feature=channel_video_title
(this is not my video)
ENJOY YOUR SIDEKICK!
this has been covered already in the dev section and has been sticked
Sent from my SGH-T839 using XDA App
Aw man. I got all hyped cause I couldn't find any other post like it....oh well.
Sent from my SGH-T959 using XDA App
Ok, i ran the bat file, it did its thing, waited till it reboot, i didnt get a chance to get rom manager till later today, so ive rebooted the phone couple times since then. But now i got rom manager and flashed CW and...... hit reboot into recovery and........ stock recovery pops up.
Reinstall. Packages
PM FOR PSN NEED THE RUN PSN
BAleR said:
Ok, i ran the bat file, it did its thing, waited till it reboot, i didnt get a chance to get rom manager till later today, so ive rebooted the phone couple times since then. But now i got rom manager and flashed CW and...... hit reboot into recovery and........ stock recovery pops up.
Click to expand...
Click to collapse
You cqnt just flash cwm from rom manager, you have to trick the phone into booting into a cwm "clone" there is a thread on how to do his, I am in class now, but when I get out I will post the link, or you may be able to find it.
Edit here u go http://forum.xda-developers.com/showthread.php?t=
Remember to hit thanks!
Sent from my SGH-T839 using XDA App
help plz
AFAinHD said:
You cqnt just flash cwm from rom manager, you have to trick the phone into booting into a cwm "clone" there is a thread on how to do his, I am in class now, but when I get out I will post the link, or you may be able to find it.
Edit here u go http://forum.xda-developers.com/showthread.php?t=
Remember to hit thanks!
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
that link its not longer working ... never mind i have it its true just go to reinstall packages and done thanks
Beware! Softpedia installs malware on your computer.
The file 'C:\Users\\Sk4g_root_with_good_recovery\Sk4g root with good recovery\rageagainstthecage-arm5.bin'
contained a virus or unwanted program 'EXP/Agent.5392' [exploit]
Action(s) taken:
The file was moved to the quarantine directory under the name '4a696fda.qua'.
Just sayin'.
Lol that is from the super click website it root phone
Sent from my SGH-T839 using XDA App
For everyone that reads this thread, i no longer have a sidekick, i recently just got my android phone after it was stolen (hence no replies from me or anything) sorry. But on to the point, this thread is old and i do not have anymore knowledge of this phone. So if theyre are problems in the future from this thread, i wont be able to help you much. Sorry.
Sent from my LG-P769 using xda app-developers app
mksin11 said:
For everyone that reads this thread, i no longer have a sidekick, i recently just got my android phone after it was stolen (hence no replies from me or anything) sorry. But on to the point, this thread is old and i do not have anymore knowledge of this phone. So if theyre are problems in the future from this thread, i wont be able to help you much. Sorry.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
This phone doesn't have much of a life left anymore anyway. Most people have already left. The phone was a great idea, just needed to have better specs and have a more open source. Right now its just on it's last breath. Kinda makes me sad, the keyboard was amazing. The doubleplays keyboard doesn't even compare. But I couldn't handle how slow a single core CPU is. As with most people.
Sent from my LG-C729 using xda app-developers app
Dead Link
mksin11 said:
After that you're going to download this file:
http://tinyurl.com/Sidekick4GALLinOne
!
Click to expand...
Click to collapse
The link is dead. Could you possibly reupload it, or direct me to where I can find it?
Thanks!!!
i recently tried to install jellybean but the rom did not work on nexus s, i stupidly removed the only working rom from my 'sd' card and now my phone only boots into a black screen, i have tried to put a known working rom on my phone but every pc i try to connect my phone to says the device has malfunctioned and windows cannot install software. i have tried to use adb but that also cannot find my device. am i looking at getting another nexus with a broken screen and using my working screen to gain a decent phone back or am i missing a vital programme that will fix my utter cockup? thanks in advance
Are you familiar with adb? Because unless you have the right drivers, you phone won't be recognized. Also, usually your computer won't notify you when you're connected and able to use adb, you have to start the interaction through cmd.exe. this being said, try adb again to move a rom or backup into your device.
Also, can you boot into fastboot? If so, is there a warning message or anything?
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
Are you familiar with adb? Because unless you have the right drivers, you phone won't be recognized. Also, usually your computer won't notify you when you're connected and able to use adb, you have to start the interaction through cmd.exe. this being said, try adb again to move a rom or backup into your device.
Also, can you boot into fastboot? If so, is there a warning message or anything?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i am only famililar with adb to the point of rooting, i have tried to download the drivers but only can see .dll files in the driver folders no option to install said drivers. i can get into power and vol up if that is fastboot?? the problem been is i installed a rom which was meant for the nexus s and i didnt read all comments and later found out it does not work with the nexus. i now cannot access the sd storage to put a working rom onto it . when i open cmd and type adb shell it says device not found. brains ready to explode right now. any help on adb is greatly appriciated
Fast boot is when you phone is off, you turn it on by pressing volume up+power at the same time. Let me know if there is a warning text in red at the top.
Do you know how to flash factory images? Because you may be able to do that to get a stock os on your phone. It would wipe everything, however. Flashing a factory image doesn't require you to open SD storage. I'd link you to the thread with the tutorial, but I'm on mobile :/ ill post it if i get a chance, i know its floating around in the nexus s android forums
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
Fast boot is when you phone is off, you turn it on by pressing volume up+power at the same time. Let me know if there is a warning text in red at the top.
Do you know how to flash factory images? Because you may be able to do that to get a stock os on your phone. It would wipe everything, however. Flashing a factory image doesn't require you to open SD storage. I'd link you to the thread with the tutorial, but I'm on mobile :/ ill post it if i get a chance, i know its floating around in the nexus s android forums
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i do not know how to flash factory images, im am very much a noob to rooted phones and playing with software.
i can get into fastboot and at the bottom it says
usb control init
usb control init end
top says fastboot mode
product name herring
hw version rev 11
bootloader version i9020xxka3
baseband version i9020xxkd1
carier info eur
ser 33304eb5103500ec
lock state unlocked
my laptop does not recognise the phone so i dont know how to flash a factory image. this is the cmd sequence i get
adb shell
error device not found
tried mounting sd card and data but no joy
also tried mounting usb storage.
all i get is device has malfunctioned and will not run
tried downloading google usb drivers and samsung drivers all to no avail.
fingers crossed you can tell me something i dont know as i really cant afford to buy a new phone
Well it seems you sdcard isn't dead, which is good! When mine was, fastboot gave me an error.
Now IMO, you should be able to flash a stock recovery image. This will clear everything you have on ur phone, but it should get it back to working condition.
Ill post a tutorial on how to do it tomorrow, that's the soonest i can get on a computer. It is not that hard, and it helps when you're already somewhat familiar with adb. I used to be a noob too, now I'm slightly less noobish!
So as i said, i think i have a solution, ill post how tomorrow, when i have a PC (in on mobile right now).
Cheers, i hope i can fix your phone!
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
Well it seems you sdcard isn't dead, which is good! When mine was, fastboot gave me an error.
Now IMO, you should be able to flash a stock recovery image. This will clear everything you have on ur phone, but it should get it back to working condition.
Ill post a tutorial on how to do it tomorrow, that's the soonest i can get on a computer. It is not that hard, and it helps when you're already somewhat familiar with adb. I used to be a noob too, now I'm slightly less noobish!
So as i said, i think i have a solution, ill post how tomorrow, when i have a PC (in on mobile right now).
Cheers, i hope i can fix your phone!
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
much appriciated and i hope you can too. thank you thank you thanks you
Alright, so this is the guide to install a factory image: http://forum.xda-developers.com/showthread.php?t=1572307
What a factory image will do, is restore your phone completely to a new like state. That being said, you will lose anything you have on the phone (picture, music, etc..). I don't know of any other way to help, so if you're willing to lose everything, but get your phone working, continue reading.
-First, you have to determine what model on Nexus S you have. If you're on AT&T or Rogers, you have an I9020A, and you have to download the "sojua" factory image. If you're on T-mobile, or have the version with an S-LCD display (as opposed to the normal AMOLED), you have to flash the "soju" factory image. If you're not sure what version you have, let me know what carrier you're with.
-Second, download the Factory image corresponding to your phone from the link I posted, as for version, that's up to you, but I recommend 4.1.2 (JB).
-Third, Make sure you have all the right drivers, and the android-sdk installed. You should already have this, since you've use adb before.
-Fourth, follow steps 1,2,3 and 4A in the link I posted above.
Follow these instruction, and if you do not understand them before doing the procedure, just ask a question here! good luck!
FirePoncho86 said:
Alright, so this is the guide to install a factory image: http://forum.xda-developers.com/showthread.php?t=1572307
What a factory image will do, is restore your phone completely to a new like state. That being said, you will lose anything you have on the phone (picture, music, etc..). I don't know of any other way to help, so if you're willing to lose everything, but get your phone working, continue reading.
-First, you have to determine what model on Nexus S you have. If you're on AT&T or Rogers, you have an I9020A, and you have to download the "sojua" factory image. If you're on T-mobile, or have the version with an S-LCD display (as opposed to the normal AMOLED), you have to flash the "soju" factory image. If you're not sure what version you have, let me know what carrier you're with.
-Second, download the Factory image corresponding to your phone from the link I posted, as for version, that's up to you, but I recommend 4.1.2 (JB).
-Third, Make sure you have all the right drivers, and the android-sdk installed. You should already have this, since you've use adb before.
-Fourth, follow steps 1,2,3 and 4A in the link I posted above.
Follow these instruction, and if you do not understand them before doing the procedure, just ask a question here! good luck!
Click to expand...
Click to collapse
still adb cannot find device.......... any links for known drivers for nexus s on win 7 64 bit?
You might need to reinstall the android SDK and drivers, there should be a link in the link i sent you to show how to do that.. If adb still doesn't recognise, your main board might be fried
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
You might need to reinstall the android SDK and drivers, there should be a link in the link i sent you to show how to do that.. If adb still doesn't recognise, your main board might be fried
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
reinsalled sdk tools, still phone not recognised by laptop. gonna try get a cheaper android and flog this one on ebay as someone else might know how to repair it. thank you for your time and help but it appears its all in vain......... damn stupid phone!
[deleted]
Rodya234 said:
the phone is probably fine if you can get into fast boot.
Click to expand...
Click to collapse
What I'm saying! You can get it to boot, but just not into anything..
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
What I'm saying! You can get it to boot, but just not into anything..
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i wish someone could just see this, pdanet asks me to connect my phone to finnish installing the drivers, problem is the phone is NOT RECOGNISED i know exactly what you are all saying to do but my phone will not connect at all. more than happy to post it to one of you guys on here to fix but like i said ive tried everything and have pulled nearly all my hair out in the process
Samsung repair? I know what you're talking about, it happened to me, I was completely bricked, all I could so was send it to Samsung repair..
Sent from my Nexus S using xda app-developers app
Damn, if only you could get it recognized you'd probably be able to flash custom recovery through fastboot and I guess you'd be able to install from sd without data loss.
Sent from my Nexus S
ok so i installed the asus 4.2 no problem. bootloader is unlocked. i then flashed twrp 4.2, then realized i needed to do push 4.4 twrp instead. so i did that. i was able to boot to the asus rom no problem. i then rebooted into twrp, and it starts asking me for a password, all i could do was hit cancel. Nothing will mount, no sdcards no external, no internal memory. so i did a bit of reading and someone said a factory reset from the bootloader screen would fix twrp. that was a big nope.
so, now the tablet will only boot into twrp, but not read anything, and i cant even get to the fastboot menu so that i can push anything. when i reset it says install super user??/ but it also says no os installed. i have a rom on my sd card i could load if i can get twrp to read it, but i tried mounting, and unmounting, and pretty much every option in every menu.
anyone have any insite?
Thank you
Mike
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
bythewayr said:
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
Click to expand...
Click to collapse
Did you use twrp from their site.or the modded one here on the forums
Sent from magical jelly bean.
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's your issue.you need the modded one
Sent from magical jelly bean.
kaos420 said:
That's your issue.you need the modded one
Sent from magical jelly bean.
Click to expand...
Click to collapse
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
Not sure why I stayed on 4.1 boot loader with 4.2.2 cm10.1 just not worth it to me until a o.c kernel appears
Sent from magical jelly bean.
bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
You might want to dig through the forums. I believe I did read about a trick using the little reset hole (About an inch below the microSD).
From there it might be possible to flash the modded TWRP. From there you should be able to get back into your JB.
I'd be very careful with flashing ROMs, I still don't see anything that confirms we can use one safely on our newest model/version.
I would be totally fine. Just installing stock Asus jellybean for now. Just so I works. I found the thread on the reset hole. I'm going to try it this afternoon.
Sent from my Galaxy Nexus using xda app-developers app
As long as fastboot still works you're not bricked. If you can't boot to download mode try adb in recovery mode and send
Adb reboot download
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Check if ADB still works, it should since you have TRWP!
and try:
adb reboot bootloader
klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's why I said to execute adb from recovery.
Code:
adb reboot download
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
ok so the adb reboot bootloader worked. and i was finally able to reboot into the os. turns out it was still on there even though twrp said it was not. so now, i suppose im going to reboot into fastboot, and push the new modded twrp from fastboot. and we should be good? Im going to try it. ill report back. now that i know my adb works correctly, im not so scared of getting stuck. back in a few. thank you guys for the help. and direction. i only hope this helps someone else not get as stuck as i was.
edit:
yeah so that is no good. downloaded the modded one from the thread. though it appears that its the same as the one from twrp site. except the link in the cromi 4.0 first post points to an androidfiledownload site. i pushed it via fastboot. except when executing the reboot command, it simply booted back to the twrp screen with it still asking for a password. so now i guess im looking at reflashing the asus stock rom and letting rewrite the recovery? and starting fresh? can i do that via adb? im still learning adb and fastboot stuff. Thanks.
Can't check this adb command solution till next Thursday but I sure hope it'll work for me, too.
As far as I understand this whole TWRP problem is that it doesn't have permission to do anything which thankfully should keep the original OS safe.
Keep us posted klownin5643. At this point I'm also mostly concerned with getting back the original recovery program.
Same issue here! Happened to me a few weeks back:
http://forum.xda-developers.com/showthread.php?t=2197895
Only when mine booted directly into TWRP connecting it to the PC didnt yeaild me any results, even after I was able to get the PC to install the naked drivers. The PC would error and say, unable to start device so ADB would not work for me either and trying 'adb devices' didnt return any results. The ONLY thing that worked for me was booting into ADX but that did me no good as I had not installed NVFLASH prior to the brick.
The resolution for me was to replace the mainboard. I got it off of eBay for 88 dollars shipped. I replaced it the same day it came in and Im up and running on the new stock 4.2.1 ASUS release. Paying the 88 dollars was better than shopping for a new tablet
Good luck with your troubleshooting OP! :good:
I'm wondering at this point, can I even flash a new recovery? Or even reflash a new ROM thru fast boot? Someone else said they tried thru adb but the files just disappeared. Or was that cause he was just pushing it to the memory card? I had the os running but I got a freeze and reboot. And it went right back to the direct loading of twrp. I don't wanna have to do that every time I restart. What would be the ASB command or fast boot to flash a new rom.?
Sent from my Galaxy Nexus using xda app-developers app
I know I'm not the only one with this problem. But has anyone flashed the stock blob over top and got everything back to normal?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Refering to your question about pushing files with ADB. I pushed them to internal memory, but that was in recovery mode with locked twrp. If you can get out of recovery with "adb reboot bootloader" then it wouldn't be directly applicable.
If you really have functional fastboot commands ( i.e. commands working instead of "waiting for device" ) then flashing a new ROM or recovery should be, more or less, straightforward. One thing I'm not sure about myself is whether new recovery can be named whatever or should it be called "twrp.blob" again. Technically, yoou're giving a "flash recovery" command so it should replace the current one, whatever it is but I'd rather not brick my device for good with a bad flash. Either way, like I mentioned, I have to wait till thursday to try anything.
I have to read more about fastboot to help with the right commands but there's a lot of guides out there.
I can give the flash recovery command and it will be fine. When I give the reboot command it freezes.
Sent from my Galaxy Nexus using xda app-developers app