Hola,
looks as I am the only one having problems with that
-http://forum.xda-developers.com/showpost.php?p=14813252&postcount=52 guide.
Well, I think I went through that above procedure quite acurately but as the download link of the 'recovery zip (solarnz-R3-240511-1908)' in
-http://forum.xda-developers.com/show....php?t=1093818 never worked for me I googled for and dl anywhere else. The problem now is the tf does not start into any UI instead revolvingly reboots (screen looks scambled after some time later reboots).
As I found out now (string is displayed after booting into recovery mode) I obviously installed 'solarnz-R3-230511-1908' even though the downbload file was named ...240511... but arent OS for the UI and the one for the recovery mode two different things? Or may be the problem is I have been on the official 3.2.1 before walking the procedure above?
So my questions are what is the current state of the transformer now and what can I do to make it working?
It currently seems not to be possible to access the device via adb (POWER button and volume plus). My PC makes the USB sound but the 'adb devices' command delivers an empty list. But the transformer can be started into recovery mode (POWER button and volume minus, volume plus after).
Just from my poor understanding I would now try to flash another CWM for example the one mentioned in
-http://forum.xda-developers.com/showthread.php?t=1213723
The thing which bothers me is I cant check any versions (postings seem to make differences among different version of ROM).
--
Regards Michael
following are the specifications before I flashed solarnz file mentioned above:
Transformer TF101
Android version 3.2.1 [email protected]#1
Kernel version 2.6.36.3
Build number HTK75CN_epad-8.6.5.19-20111107
Flash back to stock
tabletromsDOTcom/forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html
Cant post links so the DOT is obviously .
thanx Detection
edit: the problem simply is the adb does not recognize the transformer even though the pc makes the characteristical USB sound after pushing VOLUME UP and POWER button. I did already dig myself all the way through -http://forum.xda-developers.com/showthread.php?t=1071584 ... no chance
Further on I think I lack some basic understanding:
Is it right an android ROM contains the android OS (what version ever) and a whatever set of applications? A manufacturer localized version of a ROM for a specific gadget may NOT fit that specific gadget distributed anywhere else in this world? (for example the US version of a transformer ROM may not fit the transformer distributed in japan)? Does it additionally depend on the kernel?
And finally CWMs do replace some files of those ROM and may do some changes of the configuration?
If my understanding of the above would be right I think I would not necessarily have to go back to stock (which I currently cant as adb does not connect) but find a 3.2.1 suitalbe CWM to make the necessary changes on files and configurations (which would be easy as it may be flashed from the microSD).
Please let me know!
<forget that>but what to do after going back to stock as original OS is not where I want to be in the end. The CN version of most android devices can mostly dl only chinese apps from chinese app markets and thats not what I am interested in at all...</forget that>
--
Regards Michael
Ok, obviously it does not need the ADB but those procedure above finally break my device which means now even the xreen does not switch on anymore
did that happen due to the specifications (certainly build 8.6.5.19) before I flashed solarnz? Is there still any chance?
Transformer TF101
Android version 3.2.1 [email protected]#1
Kernel version 2.6.36.3
Build number HTK75CN_epad-8.6.5.19-20111107
--
Cheers
I didn't check out all the links you posted, but I have a hunch that you are getting bootloops because you have a CN boot.img/bootloader, but are trying to load a rom with a US or WW boot.img. This is just a hunch. I suspect you'll need to get everything to match or at least match the region.
So, just to be clear, you can get into recovery, but not boot into the regular system? When you boot into recovery, there is some white text at the top- what does it say there?
Edit: please fix your links
Hola Gee one,
no, I cant get anywhere anymore. The screen remains black no matter how long I push power and volume up or down
This thread pretty much aggregates everything I did. First this have been my specifations:
Transformer TF101
Android version 3.2.1 [email protected]#1
Kernel version 2.6.36.3
Build number HTK75CN_epad-8.6.5.19-20111107
then I followed on this guide:
-http://forum.xda-developers.com/showpost.php?p=14813252&postcount=52 guide
due to the boot up loop after I then followed on
-tabletromsDOTcom/forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html
and since then the screen remains black. Is there still any chance?
--
Regards
[email protected] said:
Hola Gee one,
no, I cant get anywhere anymore. The screen remains black no matter how long I push power and volume up or down
This thread pretty much aggregates everything I did. First this have been my specifations:
Transformer TF101
Android version 3.2.1 [email protected]#1
Kernel version 2.6.36.3
Build number HTK75CN_epad-8.6.5.19-20111107
then I followed on this guide:
-http://forum.xda-developers.com/showpost.php?p=14813252&postcount=52 guide
due to the boot up loop after I then followed on
-tabletromsDOTcom/forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html
and since then the screen remains black. Is there still any chance?
--
Regards
Click to expand...
Click to collapse
What is your serial number? Look under the tablet near the charging port, there's a sticker with your s/n and should start with a BxOxxx
ie. B60, B70, B80 ect....
Its starting with B60... sorry I forgot to state before
Perhaps you are stuck in APX mode? The screen will be black until you send an nvflash command. There isn't a lot of info in one place about nvflash, but the tools are out there. Try flashing a full rom via nvflash.
sent from my cyanogen(mod) vision
hold power button for 30 seconds, release and power on as normal
no reaction. Seems a clear message
If you are on a linux/unix system, plug in your tf and type "lsusb" Post the output.
If you are on windows, sorry.
Perhaps your power button is broken?
wow thats quick responses now. I just plugged in my tf to the USB port of my PC and when I pushed the power button for a while there was at least the typical sound but its not itemized in the WIN7 device manager
If there is a chance to get it back working on a linux system I can get one I guess
but
its late here now ...11pm. So would be great U could gimme some advice for tomorrow to work on
--
Mic
could I possibly run those command from a linux live CD (I remember some like KNOPIX but dont know if its internationally well known)?
Yeah, it should work. Type it in from a terminal or command line.
Sent from my Transformer TF101 using Tapatalk
well I dont have any clue about LINUX, so I should explain.
I started the UltimateBoot CD 5.1.1 within the vmware player.
For me unexpectedly I got just a screen like DOS in old times.
The window itself states to push CTR+G in order to type in comands and when I do so and type in 'Isusb' I can not read what I type?
Is that what I am supposed to do? Should the tf (obviously it has to be connected) tried to be switched on? POWER and volume up or down?
--
Thanx for any further help
Michael
the command is lsusb (LSUSB, but in lower case) First letter is L as in laptop.
plug in your transformer and it will show you what mode your are in, if any. It might show the Asus transformer (normal) or nvidia (apx mode).
When I conncect the Tf, pus POWER and volume even the VM will show me a message a device NVIDIA (APX) can be connected but then I dont think I am doing right. No matter I am typing 'Isusb' or lsusb'
the outcome always alternates between:
!BIOS V3.20
BIOS V1.35.0
CMOSPWD V5.0
KEYDisk
WipeCMOS V1.2
and
BIOS
CPU
HDD
Memory
Others
Peripherals
System
Parted Magic V6.6...
UBCD Free DOS R1.44
User-defined
Boot next device
Reboot
GRUB4DOS
Edit: i am off for a few hours now
try typing "uname -a"
What comes out?
Edit:
alternatively I tried KNOPPIX and chose Shell there. Typing lsusb' the outcome is:
Bus 001 Device 002: ID 0955:7820 NVidia Corp
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and more
the outcome for 'uname -a' is:
Linux Microknoppix 2.6.39.3 #21 SMP PREEMPT Sat...
:Edit
while I type 'una...' the list stated above (starting with BIOS) alters and there is only one line 'configfile /ubcd/menus/grub4dos/bios.lst'
I think as soon as I push (no matter what I tpyed before) the [ENTER] key that is about to happen but not the command U want.
As the list above very much looks like some kind of menu, I chose the grub4dos option. If then I type 'c' for command line and then type 'uname -a' the outcome is: No such command: uname
Additionally at the VM windows menu 'Virtual machine' under removable devices have one entry 'nvidia apx' and it can be successfully connected
Related
Here I am again...
This time I have written a shell script (linux only) and made a live-cd (for all windows/linux users) to automatically root the stock firmware on the TF101. Every stock firmware.
Today in Europe Asus rolled out the 3.2 upgrade. If you are on stock and you have alredy upgraded then download attached tar file and do as follows:
NOTE: Unfortunately, this script won't work with the latest revision of TF101 (3G version, B80 and some B70)
NOTE2: As someone pointed out (thank you Pieter) you need to be root on your linux box in order to make it work.
Code:
tar -xvf universal.tar
cd universal
./universal.sh
In Ubuntu the last command would be:
Code:
sudo ./universal.sh
Follow the instructions and you're done.
If you have a stock US/DE/TW/JP/TB firmware you can do the same.
If you are running an older version of Honeycomb the process is the same.
When ASUS will pull out another upgrade... same commands as above.
So this probably is the closest thing to one-click-root for the Transformer.
This won't install custom rom/CWM/strange other things (V2 version added the support for CWM); it's only root.
I've tested this morning after the 3.2 upgrade and it worked like a charm.
However this is in testing stage so, as always, if you brick/ruin/burn/crash something don't blame on me.
This package includes the Bootunpack tool, courtesy of Rayman84
LIVE CD INSTRUCTIONS
It's based on slitaz (http://www.slitaz.org/).
Burn the image into a cd or if you want it on a thumb usb drive follow this (http://doc.slitaz.org/en:guides:liveusb).
Put the cd/usb in your pc and reboot.
Follow the indication on screen (for setting locale and keymap).
When the desktop shows up, double click on "Universal Root for ASUS TF101".
Again follow the indication and you'll be ok.
For a guide on how to boot from cd/usb try this: http://www.passwordunlocker.com/knowledge/change-bios-settings.html
or search with google.
The option to install a stock boot/recovery (added on V3) is working even if not fully tested.
The program has correctly rebuilt a stock recovery on my WW version.
From version V4 root checker correctly says that the rom is not rooted after you do an unroot.
If you like the work i did take a look at that funny button under my name with the "donate to me" caption
Seriously, I appreciate even only a "Thanks".
FAQ
[Q] I'm running on Windows, how can I burn the live-cd?
[A] Try with cdburnerxp (it's the easiest way).
You can download one installer frome here:
http://cdburnerxp.se/en/download
or the portable package if you don't want to install other software:
http://download.cdburnerxp.se/portable/CDBurnerXP-4.3.8.2568.zip
Start the program (for the portable version the file is cdbxpp.exe) and click on "Burn iso image". Then select the .iso file you have downloaded and click "burn disk". All Done.
[Q] How can I reboot in APX/recovery mode?
[A] Do as follows:
VOL UP + POWER BUTTON for ~5sec = boot in APX mode. The screen will stay black as if it is turned off. This mode is used only when you use nvflash to flash boot/recovery/data partition (this is the first step in my script).
VOL DOWN + POWER BUTTON ~5sec = will appear a screen where it says to press vol down again to wipe all data (obviously you don't want to do it now), or press up to enter RCK (recovery mode). If you installed CWM you will see the main menu navigable with vol up / vol down / power button.
If you have the stock recovery you will see a green android with a esclamation mark on a yellow triangle.
[Q] Help! I can't reboot in recovery mode!
[A] I think the main problem here is that it is a bit tricky to get into CWM recovery, once you see the small text come up don't try to read anything, just hit volume up.
Hold volume down plus power until the text in upper left shows,if you let go too early it just boots up and you never see the text. If you wait too long you don't get the option to boot into recovery. Hope that helps..
Thx to ckuke4 for this answer http://forum.xda-developers.com/showpost.php?p=16306342&postcount=60
[Q] The live-cd gave me this error: "connection failed NvError 0x8" what is it?
[A] This means that either you are not in APX mode (read above), or that you have one of the latest revision of the tf101 (B7O) which have an unknown (for now) sbk.
For what i know, there's no knew method for rooting your device.
Maybe someone will find a way, but for now you have to be patient.
[Q] I'm running your scripts from my linux box, but it keep me saying "Permission Denied". Why?
[A] You need the root privileges on your local machine.
If you are running Ubuntu:
Code:
sudo ./universal.sh
[I](it will asks for your password)[/I]
If you are running another linux distro:
Code:
su
[I](it will asks for your password)[/I]
./universal.sh
[Q] I have rooted my tablet with this method, but I can't find the superuser app and Titanium Backup says that I am not rooted.
[A] The root script will asks you to reboot your tablet, make sure that usb debugging is turned on and then press any key.
You have to wait until you see a little bee on the bottom right of your tablet's screen, near the clock. Then press any key.
[Q] I've installed CWM but every time i try to do a backup, it says it can't find sdcard. But my microsd card work fine with root explorer!
[A] Don't get me wrong but, are you sure?
In root explorer you see a sdcard folder but it's not your microsd, it's the internal memory (it's weird, i know). In root explorer the microsd card is mounted under the "/removable/microsd" folder. You should also see a little sd card icon in the bottom right, near the clock.
Also you need to make sure the card is formatted correctly. Try reformat it with this: https://www.sdcard.org/consumers/formatter_3/
Thanks to skeeterpro for the link (http://forum.xda-developers.com/showpost.php?p=16385872&postcount=6)
[Q] The live cd stops at the command prompt, I can't see the desktop.
[A]The live cd doesn't include every driver for every video card, mouse, keyboard, etc.. (keep in mind that the original slitaz livecd is only 30MB).
You can do all the process in the text console, it's not much more difficult.
If it asks for a login insert "tux" (without quotes).
At the command line enter the following:
Code:
cd
cd universal
./universal.sh
Then the magic will start. The unroot script is called ./unroot.sh
CHANGELOG:
V4:
- Corrected some text
- Added a link on the Desktop to this thread
- Added stock ramdisk for all SKU (though JP, CN and DE are not the latest versions) (thanks to kovla for the latest TB recovery)
- Added a script on the Desktop to increase the font size on the fly for those who are using a very high dpi monitor/tv.
- Changed compression algoritm. Now the iso is ~10MB smaller.
- Maybe I have found the way to make everyone read the faq...
V3:
- [BETA] added a second script to come back to stock.
V2:
- added the option to install CWM (thanks Roach!)
- more error check
V1:
First version
=====> DOWNLOAD LIVE-CD V4 - (Mirror)<=====
DOWNLOAD LIVE-CD V3 (previous version)
DOWNLOAD LIVE-CD V2
As always, keep your eyes open and
Have Fun!
Hey, how about an equivalent windows script for those who prefer msft's os. Ok?
awesome -one root to rule them all!
ondoy1943 said:
Hey, how about an equivalent windows script for those who prefer msft's os. Ok?
Click to expand...
Click to collapse
In linux there's no need for drivers to work with tf101.
Windows seems to be problematic with driver (for someone seems to be way too difficult install the right ones).
As i stated above, adding this to a live linux cd will be the final one-click-root (put a live cd/usb-memory on your computer, reboot, follow the easy instructions and you're rooted).
Sincerely I don't know how to modify a livecd to add these scripts and programs.
If anyone wants to try, he is welcome.
Anyway I don't plan to do a windows port of this.
Disappointed! No windows support!
Will probably be trying this method from my PCLOS partition, if I can hold off the OTA update which has just begun pestering me.
Got to find out whether the modded adhoc wpa_supplicant works with 3.2 first, thanks for the effort HF
Excellent, glad to avoid having to dig out my old Windows box to root the TF Would advise people to drop it, new Mint/Ubuntu is much nicer visually than Win7 and my startup times are fantastic, not to mention the slick media support.
Does you script give also install CWM?
Will give this a go later and see how it works.
belrik said:
Excellent, glad to avoid having to dig out my old Windows box to root the TF Would advise people to drop it, new Mint/Ubuntu is much nicer visually than Win7 and my startup times are fantastic, not to mention the slick media support.
Does you script give also install CWM?
Will give this a go later and see how it works.
Click to expand...
Click to collapse
I was thinking on it, but perhaps it's better no.
Installing cwm means no more ota, since the update relies on the stock recovery.
This script was meant to leave all as stock as possible.
For all the windows folks:
I have added to the first post a live-cd with all the necessary tools.
Just run it and you'll be fine. (anyway, you are always in time to switch to linux)
Hallo and thanks!!!
what about mac's Users?
Can you explain a bit about what it does? So we can all learn.
Thank you,
Hi !
Will it work under wmware or virtual pc ?
Sorry if this is a dumb questions, but would this work in Terminal in OS X?
RayYung said:
Can you explain a bit about what it does? So we can all learn.
Thank you,
Click to expand...
Click to collapse
So you wanna learn? Good!
First i learned how to root the stock firmware from here: http://forum.xda-developers.com/showthread.php?t=1125714 .
Essentially the steps are:
1 - download a modified boot image into the tablet
2 - install the su and superuser packages.
My scripts do these 2 steps. I wrote a small howto that explains how to modify a boot image (http://forum.xda-developers.com/showthread.php?t=1193737)
Caramel said:
Hi !
Will it work under wmware or virtual pc ?
Click to expand...
Click to collapse
scirio said:
Sorry if this is a dumb questions, but would this work in Terminal in OS X?
Click to expand...
Click to collapse
I really would like to have an answer to these questions...
The Mac should have a layer of compatibility with linux (can't tell you more), but i really don't know the mac world.
*Maybe* the live cd will work under virtual machine; there should be some options to enable the usb feature. In Virtual Box there's an option to enable the usb controller and an option to filter what device will be accessible to the guest os; don't know vmware and virtual pc.
I don't know if an Intel based Macintosh is able to boot from a x86 live-cd, you could try.
I'm sorry i can't help you much more.
scirio said:
Sorry if this is a dumb questions, but would this work in Terminal in OS X?
Click to expand...
Click to collapse
Oops- no- there is no Nvflash for Mac. Sorry.
Created a live usb, booted via windows, and voila i am looking at a linux desktop, which i have not seen for a long time. Started going to its paces to root my tf, but did not push thru to the end, in as much as my tf is already rooted beforehand. But i can sense that barring any unforeseen miscues by the |op|, this almost one-click rooting procedure should produce its desired result. Highly recommended; good job |op|.
Looks like this calls for an "unrooting" routine to complement the rooting process. How about it?
Nice script! I just completed one of my own for unrooting the TF
One thing: why not just use adb reboot recovery instead of telling them how to do it manually?
brando56894 said:
Nice script! I just completed one of my own for unrooting the TF
One thing: why not just use adb reboot recovery instead of telling them how to do it manually?
Click to expand...
Click to collapse
I have already tried this, but seems it doesn't work.
if i write "adb reboot recovery" or "adb reboot bootloader" my tablet reboot in normal mode.
It's more reliable do it manually.
how can install ClockworkMod recovery
i rooted my transformer with your one click tool from live cd.
if i want install ClockworkMod recovery how can do ?
zulu99 said:
i rooted my transformer with your one click tool from live cd.
if i want install ClockworkMod recovery how can do ?
Click to expand...
Click to collapse
For now if you are running on windows, you can use one of these methods:
http://forum.xda-developers.com/showthread.php?t=1125714
http://forum.xda-developers.com/showthread.php?t=1185104
you are already rooted, so just need the cwm.
Since i had many requests on adding cwm, i am going to update the scripts and live-cd for adding this feature.
I'll keep you updated.
Hi all,
I had a nice, long, detailed post typed out but then my browser at work crashed, so here is the revised edition:
I recently (three days ago) bought a TF300T tablet. Absolutely love it. As any android fan does, I immediately wanted to root it to get the full benefit of the device. I followed the step-by-step guide on the cyanogenmod wiki and have been successful (after a few hours of figuring things out) in unlocking the device. I am aware at this point that my device is unlocked and my Asus warranty is voided. I am also aware I may have to follow different steps to root it, and am willing to do so accordingly.
I'm not set on using cyanogenmod, but that seems to be the most popular and well-known one so I'd like to use one that is established.
So, up until now I have followed that guide but I am having an issue with flashboot. When I go to do the 'fastboot devices' command, I get nothing. It just jumps to the next line, as if I sent a blank command. When I type 'adb devices' it works fine and shows some letters&numbers so I know my device is recognized.
With all that being said, can anyone advise me on which step I'm doing wrong, if any?
Also, I'm -really- cautious about potentially bricking this thing. I still have 30 days at Best Buy but I'm also an employee there and my co-workers know I'm trying to root so if I brick it, it may not be as easy to return it as with a normal customer. I also have the Accidental Damage & Handling plan so if I DO brick it, I can smash it and get a new one without too much incident, if it comes down to it (which obviously is a LAST resort)
My device is as following:
Asus Transformer Pad TF300T unlocked, firmware .29.
I' have about 15 tabs open in Google Chrome right now after SEARCHing the forums, specifically the TF300 forum, and I'm filtering through all the posts right now. If I find a solution I will post asking for this thread to be deleted.
I'm very tech-savvy, but completely new to android. I don't own a smartphone, and this is my first android device, so this is an incredible learning experience. If anyone feels so kind, could you please explain the different terminiologies used in the rooting scene? I hear stuff about blobs, .build files, DE, WW, US stuff. What's what? And what does it all mean?
Thanks so much, and here's to hoping my computer doesn't crash as soon as I press "post"!!
-Opethfan89
*edit* Forgot to add that when I use the command
fastboot flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
the command prompt just stays stuck on "waiting for device", while my device is stuck on "Starting fastboot USB download protocol"
Slight resolution
So I am just posting with a slight update to what I've been trying to get this working. I uninstalled the ADK, all drivers, and started over from scratch. I installed ADB using the method listed on the CyanogenMod wiki, and it works fine (I can use all ADB commands from command prompt and it lists my device when I use the 'adb devices' command.
So I'm continuing to follow the steps on the CyanogenMod wiki page and I get back to the part about Fastboot. I boot into fastboot mode, plug the device in, and the new development is that my computer DOES recognize fastboot only in device manager. I do have a yellow exclamation mark near it meaning I don't have the proper driver installed.
So now my newest question is, how do I install the driver for -just- fastboot, or where can I find the .inf file so I'm able to install it myself?
I'm SO close to rooting this device I can just taste it!! Any device is very much appreciated
Thanks!
Opethfan89
Are you following this guide?
http://forum.xda-developers.com/showthread.php?t=1668173
Pretty easy to follow and the easiest way to install recovery and root device.
Yes I have followed that guide and like I said I get to the step where fastboot SHOULD be recognized by my computer but it isn't. It shows up in my device manager with a yellow exclamation point so I literally just need the driver to make things work and I should be rooted.
This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.
Have you tried to see the index on tf300t development?
Hope you have all you need and all process.
For Fastboot : [GUIDE] Help for flash more faster when you use Fastboot Line Command
And for Drivers:
ASUS Android USB Drivers.zip - 2012/04/13 - MD5 Sum: 43af8f39ed421caabecd6c4a2de17212 - Size: 8.28 MB (8687221 bytes)
ASUS Pad PC Suite (PC version V1.0.41) - MD5 Sum: 02d7661affefeb0ae05f577b6b24b37a - Size: 145.09 KB (148570 bytes)
ASUS Sync V1.0.82 - MD5 Sum: a7d229ee2f2678819e6a99711d1f572d - Size: 62.18 MB (65195236 bytes)
You will find all you need for your TF300t in this index
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop
philos64 said:
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop
Click to expand...
Click to collapse
I think you do need to install android sdk because of the fastboot files are in there and need it to use fastboot that could be the reason why his computer does not recognize the tablet when he is in fastboot mode. If you look at your android manager you will see a file under android tools that fastboot files are installed.
you need to specify device id
fastboot -i 0x0b05 flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
try that op
IT WORKED!!!!
EndlessDissent said:
This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.
Click to expand...
Click to collapse
See, I think that's where I messed up. None of the guides say to download ASUS' drivers, and in my anxiousness to root I must have overlooked that step. I will try this today and post my results accordingly!! Also, no offense taken by the linux comment, and I've used linux in the past, but I've had quite a few times where it doesn't "just work" (Like using a broadcom wireless card on my old laptop. I had to learn how to use ndiswrapper and whatnot, not a pleasant experience for a linux newb at that time!!)
I recently removed my Linux partition (was using ubuntu 10.10 because I hate unity!!) and can re-install it if it will make my rooting process easier?
vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
Yea I didn't download the asus pad suite drivers, and I think that is what is causing my issue. I wish I could post links to the guides I am following but none of them specify that. They just say to download the android SDK and all drivers are included.
FlyingPoo said:
you need to specify device id
try that op
Click to expand...
Click to collapse
I did do that, flyingpoo. At one point my cmd line showed "Sending file recovery.img (5***kb)" but the tablet never picked it up, so I know there is just some miscommunication between the tablet and the PC. When I typed adb devices in cmd line, I see the device listed, but when I type fastboot devices in cmd line, it just goes to a blank line.
I will try the above listed solutions and hope that something works. Thank you all so much for your help!
*edit* This guy, right here? Yea, he's freakin ecstatic! I installed the drivers from EndlessDissents' post, and it worked!! As soon as I booted into fastboot mode, my computer recognized the device. I then used the command that FlyingPoo used (which I tried in the past), and it showed:
Code:
c:\recovery1>fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' <5306 KB>...
OKAY [2.417s]
writing 'recovery'...
OKAY [2.053s]
finished. total time: 4.473s
So now I'm following the next few steps to root it. I've backed up my apps using Astro as well as the ASUS backup suite, and I'm using CWM for a backup of my entire system at the moment.
Thank you again to everyone who responded. I always get hung up on the simplest step, but once that is overcome everything else is a smooth ride downhill
One last noobish question to ask, and then I think I'll be done:
I've downloaded the root-signed.zip file, as well as the latest CyanogenMod file I could find (The official wiki didn't have one listed for any asus products, for some reason?) as well as a google apps for cyanogenmod. I put the files on my SD card but nothing on there is detected within CWM. So the noobish question is which directory do I need to put the files in for CWM to detect it?
That being said, I'm also wanting to backup my system to my external SD card and I selected the option in CWM to backup but it said no sd\ext was detected. Any thoughts?
Thanks again everyone for your responses.
*EDIT* For anyone following this thread, I did figure it out. Another guide I referenced specifies that you copy the files to the INTERNAL SD card (which is kind of confusing, as SD card explicitly refers to an external memory card) and then choose it from CWM. So for me, I downloaded the files on my computer, copied them to my SD card, put the SD card in my tablet, and copied the files to the root directory of the internal storage on my tablet.
Thanks again everyone, I now have root (at least, I'm pretty sure I do?)
Mod, please feel free to close this thread as necessary.
Since there is a terrible lack of information on this RockChip tablet, I've decided to compile what is known about this tablet into one thread. I'll modify this as more info becomes available to me.
Double Power TD-1010 10.1" Tablet
Tablet architecture: this tablet is a Rockchip RK3066 based tablet.
Rooting the TD-1010: The method that I have tried and successfully rooted my tablet involves using the drivers from PDAnet and AndroidRoot. A tutorial exists on YouTube for this. Having that out of the way, we can begin on more technical information.
Backing up the ROM: As the tablet is a rockchip device, you can use the RkFlashTool for linux here in order to copy/write to the tablet. I've modified the source of RkFlashTool in order to detect the tablet, and attached it below.
1.compile it using the included instructions, and throw it in your /usr/bin folder.
2.To put the tablet into flash mode, hold the VOL+ button while plugging in the usb cable to the tablet.
3.Wait 2-3 seconds before letting go of the Vol+ button after plugging it in. your screen should be black at this point.
4.You are now in flash mode, and can be detected by the rkflashtool.
5.Download the Linux tools.7z, and run MAKE on the tools dir.
6.Copy the resulting mkkrnlimg executable to your /usr/bin directory.
7.make sure the simpledump has permissions to execute, and run
Code:
./simpledump.sh
8.Make sure your tablet is in flash mode, then hit enter to begin.
Recovery/Unbricking:
Dillmiester at TabletRepublic has made a stock backup of the TD-1010 after it returned from RMA, and can be located Here. Note, remove the external SD card, and you may have to retry the flashing of system.img multiple times if it fails.NOTE 2: THIS UPGRADES YOUR TABLET TO JELLYBEAN, AND GIVES YOU 1.8 GB of APP SPACE.
Flashing: ROMS, such as the stock one linked above, can be flashed using Windows 7 and the RKAndroidTool I have attached to this post. This includes the drivers for using the program as well. The tablet will need to be in Flash mode in order for the program to write to it.
Booting into recovery:Yes, this tablet does have a recovery. to get to it:
hold power and vol+ at the same time
screen should boot to android character with a red ! sign over his body
press vol+ and Back(the normal touchscreen location for it)
If done at the same time, you should be at the recovery menu.
great job thank you. i don't have a Linux machine so i guess all i can do is root?
you can root and flash existing ROMS on windows, but you cannot dump your own tablet on windows.
DOPO td-1010 romdump procedure
ase1590 said:
you can root and flash existing ROMS on windows, but you cannot dump your own tablet on windows.
Click to expand...
Click to collapse
Just an FYI for those interested. I've found a working romdump procedure for this tab, that's independent of any OS. Unfortunately, I can't post the link, but would be more than happy to supply it some other way. I can confirm it works and is safe. It's on vondroid.com for those interested. The rest of the link is /threads/updated-27-08-2012-how-to-dump-current-rom.322/ hope it helps those using windows.
Just for clarification purposes. 'The extracted file is what you need to copy to your SD, not the zip. And when you change the permissions all you need to do is add execute to the user. Oh, and in term emulator after su you need to enter /data/local/romdump and NOT just /data/romdump because it won't work.
ase1590 said:
Since there is a terrible lack of information on this RockChip tablet, I've decided to compile what is known about this tablet into one thread. I'll modify this as more info becomes available to me.
Double Power TD-1010 10.1" Tablet
Tablet architecture: this tablet is a Rockchip RK3066 based tablet.
Rooting the TD-1010: The method that I have tried and successfully rooted my tablet involves using the drivers from PDAnet and AndroidRoot. A tutorial exists on YouTube for this. Having that out of the way, we can begin on more technical information.
Backing up the ROM: As the tablet is a rockchip device, you can use the RkFlashTool for linux here in order to copy/write to the tablet. I've modified the source of RkFlashTool in order to detect the tablet, and attached it below.
1.compile it using the included instructions, and throw it in your /usr/bin folder.
2.To put the tablet into flash mode, hold the VOL+ button while plugging in the usb cable to the tablet.
3.Wait 2-3 seconds before letting go of the Vol+ button after plugging it in. your screen should be black at this point.
4.You are now in flash mode, and can be detected by the rkflashtool.
5.Download the Linux tools.7z, and run MAKE on the tools dir.
6.Copy the resulting mkkrnlimg executable to your /usr/bin directory.
7.make sure the simpledump has permissions to execute, and run
Code:
./simpledump.sh
8.Make sure your tablet is in flash mode, then hit enter to begin.
Recovery/Unbricking:
Dillmiester at TabletRepublic has made a stock backup of the TD-1010 after it returned from RMA, and can be located Here. Note, remove the external SD card, and you may have to retry the flashing of system.img multiple times if it fails.NOTE 2: THIS UPGRADES YOUR TABLET TO JELLYBEAN, AND GIVES YOU 1.8 GB of APP SPACE.
Flashing: ROMS, such as the stock one linked above, can be flashed using Windows 7 and the RKAndroidTool I have attached to this post. This includes the drivers for using the program as well. The tablet will need to be in Flash mode in order for the program to write to it.
Booting into recovery:Yes, this tablet does have a recovery. to get to it:
hold power and vol+ at the same time
screen should boot to android character with a red ! sign over his body
press vol+ and Back(the normal touchscreen location for it)
If done at the same time, you should be at the recovery menu.
Click to expand...
Click to collapse
Thank you sooooo much for the work you have compiled into one location. Is there any way that you could provide a detailed description for Windows PC's for loading the ROM that increases the App storage file size to 2GB and also how to load CWM as the permanent recovery? I just received my tablet back from DOPO and it is loaded with Android 4.1.1 firmware and 1GB of app storage space. The original root process (android root unlocker) does not work anymore. I ended up using (root rk29) to obtain root access (just in case anyone needs the info). Thank you in advance for your support with this tablet, it is greatly appreciated.
Hi.
It's been some time since i tried fixing my Asus Transformer...
The problem is : If it has battery life. It boot's and gets stuck on the first screen.
With the logo "eee pad" .
If i turn it off, it automaticly reboots and gets stuck in the same screen.
If i try to get into recovery mode.
Vol down, Powerup... and the vol up , i can see the few line's of code , saying it will boot into recovery mode.
but while trying to start recovery mode the icon changes to a fallen android and an "! triangle above it
I've been looking around forums evrywhere but i cant find a solution for my exact problem.
can anyone help?
Quickly, with the info you provided, I would think your firmware or storage may be damaged.
Can you access ADB? Sometimes you can while it boots, even if it doesn't fully boot. That would allow you to check logs and back up data.
Can you access APX? It has nothing to do with Android, it's a part of the device made by Asus to allow you to "inject" a firmware inside the device while it's in "brick" state.
If you can access ADB, you can "pull" the files you want from the device to your computer. You can see information on ADB here. Basically you install the package from google and connect the device to your computer, then run a set of commands.
If you can access APX (chances are you can unless there's hardware damage), then EasyFlasher can push a stock firmware back to the device. This will wipe your device 100% back to stock and you will lose all your files.
Lethe6 said:
Quickly, with the info you provided, I would think your firmware or storage may be damaged.
Can you access ADB? Sometimes you can while it boots, even if it doesn't fully boot. That would allow you to check logs and back up data.
Can you access APX? It has nothing to do with Android, it's a part of the device made by Asus to allow you to "inject" a firmware inside the device while it's in "brick" state.
If you can access ADB, you can "pull" the files you want from the device to your computer. You can see information on ADB here. Basically you install the package from google and connect the device to your computer, then run a set of commands.
If you can access APX (chances are you can unless there's hardware damage), then EasyFlasher can push a stock firmware back to the device. This will wipe your device 100% back to stock and you will lose all your files.
Click to expand...
Click to collapse
With my Ubuntu, if i do the command ./adb device
Then i can see a number. So the device is connected i think.
I am not sure if i can access APX, i do not yet how to test tis yet.
Is there an easy way to see / test this in ubuntu ?
DarkCloud98 said:
With my Ubuntu, if i do the command ./adb device
Then i can see a number. So the device is connected i think.
I am not sure if i can access APX, i do not yet how to test tis yet.
Is there an easy way to see / test this in ubuntu ?
Click to expand...
Click to collapse
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
What serial number is your TF ?
NVFlash is the quickest way to get back to 100% working stock
http://www.xdafileserver.nl/Files/A...OMS/ICS .27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z
*Detection* said:
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
What serial number is your TF ?
NVFlash is the quickest way to get back to 100% working stock
Click to expand...
Click to collapse
I tried the "hold volume up & power" when connected to my Windows PC.
I did see the "usb connection" and heard the sound.
But it says the installation failed.
my serial number of my TF is B60KAS032926
DarkCloud98 said:
I tried the "hold volume up & power" when connected to my Windows PC.
I did see the "usb connection" and heard the sound.
But it says the installation failed.
my serial number of my TF is B60KAS032926
Click to expand...
Click to collapse
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin
*Detection* said:
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Click to expand...
Click to collapse
Ok, i'l try that right now.
The APX driver is installed now.
i'l try NVFlash
DarkCloud98 said:
Ok, i'l try that right now.
The APX driver is installed now.
i'l try NVFlash
Click to expand...
Click to collapse
I edited my post with quick instructions
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin
*Detection* said:
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin
Click to expand...
Click to collapse
When do i know if it's done. And is there any other thing required?
I used the NVFLASH_ICS_9.2.1.27_WW_NOROOT
and running download.bat with admin its starts a terminal.
after this is done, i see 2 lines of information on my Asus transformer. only chip Uid and Nv3P server
DarkCloud98 said:
When do i know if it's done. And is there any other thing required?
I used the NVFLASH_ICS_9.2.1.27_WW_NOROOT
and running download.bat with admin its starts a terminal.
after this is done, i see 2 lines of information on my Asus transformer. only chip Uid and Nv3P server
Click to expand...
Click to collapse
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
*Detection* said:
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
Click to expand...
Click to collapse
ok sweet, thx !
i hope it'l boot soon
after that...i'l need to root it again i think. ...but thats for later.
Now it would be awsome to let it work again.
thx again for the help
DarkCloud98 said:
ok sweet, thx !
i hope it'l boot soon
after that...i'l need to root it again i think. ...but thats for later.
Now it would be awsome to let it work again.
thx again for the help
Click to expand...
Click to collapse
You could flash the pre-rooted versions too although I think it's easy enough to root yourself these days
This is the XDA Fileserver for different ROMs if you need them
http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)
I was just reading someone else who had the same display stuck on their TF while trying to use NVFlash and they said re-downloading the ROM and trying it again fixed it
So if this fails for some reason, try another NVFlash ROM from the XDA Server
*Detection* said:
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
Click to expand...
Click to collapse
seems to still do nothing more.
sure i'm not missing the something i should add to the NVFLASH ?
DarkCloud98 said:
seems to still do nothing more.
sure i'm not missing the something i should add to the NVFLASH ?
Click to expand...
Click to collapse
NVFlash contains everything you need, ROM and NVFlash tools to install it to the TF, I've used that exact same download on mine so it should be working
Did you have any progress showing in command prompt ?
It should say something like
Deleting partition
1
2
3
4
5 etc
Then creating partiton
1
2
3
4
5etc
Then sending boot.img
sending system.img <<<<< This one takes a while
Try it a few times until you start seeing progress in CMD, if you don't see it after a few minute, cancel it again try again
There is also a Linux version of NVFlash you could try
http://forum.xda-developers.com/showthread.php?t=1123429
*Detection* said:
NVFlash contains everything you need, ROM and NVFlash tools to install it to the TF, I've used that exact same download on mine so it should be working
Did you have any progress showing in command prompt ?
It should say something like
Deleting partition
1
2
3
4
5 etc
Then creating partiton
1
2
3
4
5etc
Then sending boot.img
sending system.img <<<<< This one takes a while
Try it a few times until you start seeing progress in CMD, if you don't see it after a few minute, cancel it again try again
There is also a Linux version of NVFlash you could try
Click to expand...
Click to collapse
i see =
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
/ 786432/1454712 bytes sent
and when it's done , the cmd closes and thats about it.
so'l best try it a few times?
DarkCloud98 said:
i see =
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
/ 786432/1454712 bytes sent
and when it's done , the cmd closes and thats about it.
so'l best try it a few times?
Click to expand...
Click to collapse
Did the TF not reboot on its own ?
Have you tried booting it manually by holding power for 30 seconds then powering on normally ?
That all looks like its working fine, sending the files across
EDIT - I`ll upload an older version that I have saved, it has a different file structure and uses .img instead of .blob
EDIT - Try this NVFlash
http://www.portableandroid.co.uk/androidDL/new Windows.zip
*Detection* said:
Did the TF not reboot on its own ?
Have you tried booting it manually by holding power for 30 seconds then powering on normally ?
That all looks like its working fine, sending the files across
EDIT - I`ll upload an older version that I have saved, it has a different file structure and uses .img instead of .blob
EDIT - Try this NVFlash
Click to expand...
Click to collapse
I Just Tried the linux NvFlash.
and the boodloader sending = send succesfully
but the next step it says : "File not found: recovery.img"
Failed executing command .... NvError 0x4
Command failure: create failed.
I'm nog going to try the last NVversion you linked with my Windows PC
EDIT: And the other NvFlash version you linked me, does the same...after it being sent, the CMD closes and thats it
DarkCloud98 said:
I Just Tried the linux NvFlash.
and the boodloader sending = send succesfully
but the next step it says : "File not found: recovery.img"
Failed executing command .... NvError 0x4
Command failure: create failed.
I'm nog going to try the last NVversion you linked with my Windows PC
Click to expand...
Click to collapse
I think maybe the linux version is the older .img version, and the files are .blob so it can't find anything
The one I linked you is the .img windows version, hopefully you'll have more luck with that
If not, put all the .img files into the linux folder and try it that way
*Detection* said:
I think maybe the linux version is the older .img version, and the files are .blob so it can't find anything
The one I linked you is the .img windows version, hopefully you'll have more luck with that
If not, put all the .img files into the linux folder and try it that way
Click to expand...
Click to collapse
It worked !!!
By using the linux download.sh but by adding all the files in the from the windows folder that were missing.
Thank you very much !!!
DarkCloud98 said:
It worked !!!
By using the linux download.sh but by adding all the files in the from the windows folder that were missing.
Thank you very much !!!
Click to expand...
Click to collapse
Great news! Linux vs Linux did the trick
How long have you been without your TF until now? It'll be like having a new toy again I would imagine
ALARM: the device could be bricked if something will go wrong.
Actually should work for 10' and 13' as well
Introduction
The Yoga Tab 2 devices are built on the Intel Baytrail SOC, which makes them not very different from cheap Intel Atom laptops and idea to make them run something more serious than Android is too tempting to resist. Even more interesting, the Windows version of the devices do exist, so running of the full desktop OS is definitely possible.
Beginning
The easiest method to boot Linux on the Yoga is to unlock bootloader and replace standard EFI loader with GRUB. To do it, use the set of files, available here.. Unzip the file, put the tablet into fastboot mode, connect to PC and use script hack.cmd to flash the ESP with GRUB. Now, the system will be booting the GRUB, which will normally boot Android (if no buttons is pressed). The volume buttons are configured as hotkeys in grub.cfg, so it is possible to load arbitrary system, supported by GRUB.
To modify the grub.cfg from Android, mount the ESP partition:
Code:
su
mkdir /esp
busybox mount /dev/block/by-name/ESP /esp
vi /esp/boot/grub.cfg
Kernel
The device is able to boot mainline Linux kernel in the described way, but due to erroneous ACPI tables majority of hardware won't work. I did my best to repair the tables to make system usable. Still, not everything is working, mainly screen brightness control and sound. The kernel development info is available at https://github.com/Trel725/yoga2linux
System
I've chosen Manjaro Linux as a distro to work with because of my own taste. It shouldn't be a problem to run any other distro with modified kernel, but I provide rootfs only for Manjaro.
How to get it working
1. Flash the modified ESP as desribed above.
2. Download the archive, create folder /factory/manjaro (folder /factory should be already present in the tablet) and unzip archive to that folder. It is necessary because GRUB can't access the external SD, so kernel need to be loaded from internal memory and then find SD card. /factory is just a partition, used for storing tablet configuration, and as it is usually empty for 90-99 % it is convenient to use it to store the kernel and initramfs.
3. Find a good SD card, format it to the ext3 or ext4 FS and unzip RootFS to the SD card. Insert card to the tablet.
4. Reboot and press Volume+ to boot Linux.
Some ideas
1. After tablet has booted Linux and USB is initialized, it keep it's state on reboot. This means that following trick is possible:
boot linux -> reboot -> get to GRUB (by pressing Volume-) -> USB keyboard should work as it was initialized -> go to the GRUB command line (press c) -> type exit, press enter -> should get to BIOS with working keyboard -> if USB flash disk was inserted before entering the BIOS (usb hub is needed as device has only one port) it is possible to boot from it.
2. TODO
Hello, do you have any Linux tutorials installed here?
Wordowg's post failed
Thanks for this, @Trel725.
No problem with 5.2 kernel? isn't it too new for such an old device?
Also -- maybe some stuff from here is relevant? e.g., WM5102.
NaEpoch said:
Hello, do you have any Linux tutorials installed here?
Wordowg's post failed
Click to expand...
Click to collapse
Which tutorials do you mean? Linux usage in general?
raenye said:
Thanks for this, @Trel725.
No problem with 5.2 kernel? isn't it too new for such an old device?
Click to expand...
Click to collapse
Linux is very good in backward compatibility, even support for 80386 (released in 1985) was discontinued only in kernel 3.8. Moreover, I am particularly interested in mainline kernel without need to support ancient code (like for majority of android devices).
raenye said:
Also -- maybe some stuff from here is relevant? e.g., WM5102.
Click to expand...
Click to collapse
Thank you for the suggestion. I didn't try the patch for WM5102 from github, hopefully it will work for mainline kernel. I will try to find some time for it in the future.
sorry,my bad
i mean install linux for yoga tablet2 ' tutorials.
The tutorials in the forums all failed.
If you are free, can you teach me how to install it?
Thanks very much.
Unfortunately I don't have time for complete guidance, but if you have any questions I will readily answer them. The more details you provide the easier to help you.
alright, Thank you all the same.
But if you have time, please help.
My E-mail is [email protected]
Just a simple tutorial.
thank you
I can get Manjaro to boot but it can't load LightDM. I'm on 1050L.
I cant get this to work... All i get is a shell command line. no dual boot. Doesnt default into Android if nothing is imputed.
I tried connecting a keyboard. And cant type anything in.
I feel some steps have been skipped.
Tried this and now can't do anything but sit in empty shell. Can't type, volume buttons do nothing