So I have the issue where my CWM version is boot looping. I know how to fix it by flashing the CWM roach fix but my SD card directory is not visible either. It's only showing the internal sd card. I unfortunately can not get my transformer driver to install on my pc. The driver that is provided from the asus website isn't working. That and the driver should be showing "APX" i believe, and it's showing "Transformer".
I've done a lot of searching for help and all the recommendations are saying connect it to the computer and use adb to push the file or to create a micro sdcaard directory. Or use nvflash.
Suggestions are appreciated.
And for info, i've used a pc with windows xp, and 2 laptops one with windows 7 and one with windows 8. No luck with the drivers.
same problem, I can't ADB either.
Brand New said:
same problem, I can't ADB either.
Click to expand...
Click to collapse
I'm still actively looking for a fix. I'm trying to see if I boot in linux if I can get the tablet recognized. I'll report back. If you find a fix yourself please share.
I wonder if we flash a new update.zip and just return to complete stock if it'll work?
No, the recovery (if you have the same one I have) is that it is a bug in the recovery that continually boot loops. I have nand and tried to install fresh and it doesn't fix. If you can read your sdcard not your internal memory you can easily just install the fixed roach recovery that doesn't boot loop and that will fix it for you.
If you guys are able to cold boot into the OS, use Terminal Emulator to do what
ADB would do.
1 - Cold boot into the OS and move files needed to internal sd storage.
2 - Reboot into your bad 5.5.0.4 cwm , install the new cwm through : install zip from sdcard , choose zip from ...
3 - Once installation is done , don't press "reboot system now" , do a cold boot directly (Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot)
4 - Once you've booted your rom , run terminal emulator.
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : exit
type : reboot
NOTE: Someone say the above steps only work when they skipped the exit part so try it both way.
This helped. Step one was slightly pointless due to the fact that the CWM recovery doesn't read the SD card but the internal storage. But after doing the cold reboot, I loaded the new one, and then followed the steps 1-3 without the exit and it applied with no issue. I'm now on the new touch recovery with no boot loops. Thanks very much for your help.
Yeah I should have pointed out to cold boot first and put the files needed on the internal sd.
Edit above post to show that
How do you coldboot?
Brand New said:
How do you coldboot?
Click to expand...
Click to collapse
Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot
baseballfanz said:
Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot
Click to expand...
Click to collapse
Thanks buddy I owe you one.
Thank you guys
thanks
Hi guys, I just registered today, I have been using XDA for a while now, and hadn't created an account. I rooted my asus tf and Flashed CWM and ended up getting the recovery bootloop. Within 10 minutes I had found this post and used baseballfanz suggestion to use terminal emulator, and Flashed the touch Recovery and got out of the bootloop. Now running AOKP on my TF-101 and its smooth as butter. I felt i needed to make an account today just to thank baseballfanz. You guys rock, thanks again.
**EDIT** stryke504, i neglected to thank you as well in my earlier post.
This is what this place is all about. I created an account back in 2007 and just started posting last year for the same reason.
Sick!!!! It worked!!!
Hi guys I'm in trouble!! I have continuos bootloops in recovery. I tryed to flash a rom as usual but always bootlooping adn when I tryed to make a cold boot it remain in the same " colod booting linux ".. I can't restore my backup cause I move it on my memory card and cant restore it! Can I do something? I can't boot anymore... Any suggestions? I can only install the rom I have put in the internal memory..
same issue and nothing seems to work.....help
I was caught in a bootloop with CWM 3.2....something or other...couldnt adb. Couldn't cold boot...just clicked and stayed on screen...now I have lost the recovery I did have and feel like I am royally screwed....I am on tf101 b90....so nvflash doesn't work so I read....exactly how screwed am I?
What do you mean? You don't know what recovery you are using anymore?? Have you tried NVflash? Does your computer recognize the tablet?
Sent from my PG86100 using xda premium
thank you
helped fix my problem i was having but i was caught in the terminal and it kept denying root access the way i solved this was to
cold boot
re root using vipermod 4.5 and using option 1
http://bit.ly/Ac63pA
then following the steps with the terminal commands
fully working transformer
baseballfanz said:
If you guys are able to cold boot into the OS, use Terminal Emulator to do what
ADB would do.
1 - Cold boot into the OS and move files needed to internal sd storage.
2 - Reboot into your bad 5.5.0.4 cwm , install the new cwm through : install zip from sdcard , choose zip from ...
3 - Once installation is done , don't press "reboot system now" , do a cold boot directly (Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot)
4 - Once you've booted your rom , run terminal emulator.
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : exit
type : reboot
NOTE: Someone say the above steps only work when they skipped the exit part so try it both way.
Click to expand...
Click to collapse
hum, sorry, i don't mean to be slow but im not understanding how i can install from zip (sdcard) if my bad cwm can't read it.
i can cold boot, i can use terminal but how can i flash the files if i need to be in recovery to do it and that recovery won't read the sd?
is it possible to flash from terminal?
thanks,
Related
HSN Launches Coby Kyros Internet Tablet 7" Android OS 2.1, 800MHz with 1080p HDMI review by me (note just click on the image to get to the review)
Coby Kyros Internet Tablet MID7005-4G Work-in-Progress Review by me
(note just click on the image to get to the review)
hi
hi where did you buy this ive been looking for a while?
I got a 7105-4g at k-mart yesterday.
Hey, I have a Kyros MID 7005-4G too. Unfortunately, it's pretty screwed at the moment. I'm looking for a recovery image for the device. If anyone can get me a recovery image of one of these, I'd be very grateful. I've tried a recovery image MID 7015, but they don't seem to be similar enough to work. Anyone?
Edit: On second thought, the Framework.jar file from an MID 7005-4G would help too.
Market
Yea, I just bought the MID7005 and it's cool. The resistant touchscreen is a little difficult at times. I really want googles market on it though. Id love to know how? Anyone?
clockworkmod/cyanogenmod/market on 7005
If you're interested in modding your 7005, I bought a used one on ebay. It was locked and the password lost by the previous owner when I got it, and it seems like it's been dropped because the charger is pretty intermittent. I don't think my battery is charging...
Anyway, if you want google market on it you will need to root your device and install a custom recovery.
What you will need:
SD card 1gb <
computer with the Android SDK (you need to use the ADB)
z4root
dump-recovery-signed.zip
clockworkmod recovery for the X5A-G
Cyanogenmod 7 for X5A-G
GAPPS (Google Apps) flashable zip
NOTES
***if you're very brave you can try using terminal emulator, but I don't recommend it. This tablet doesn't have a lot of power and crashing or freezing at any time during this process will almost definitely brick it. Just use the ADB and don't take the risk!***
I can confirm that both Clockworkmod Recovery and the Cyanogenmod 7 ROM for the X5A-G work on Kyros 7005.
1. install z4root and permanenty root. reboot
2. link removed at owner's request
you can get into the recovery by either holding home and power at bootup, or by enabling USB debugging on the tablet and then issuing the command
Code:
adb reboot recovery
Once you are in the recovery, select update from .zip file. This will trick your tablet into thinking it is preforming a firmware update, when in fact it is running a script that is backing up the recovery to your SD card.
3. download the x5a-g clockworkmod recovery .zip. Renaming it as 'update.zip' and attempting to flash using stock recovery does not work. You will have to do this manually, either via the adb or terminal emulator. I strongly suggest using the adb.
4. extract the clockwork mod recovery .zip file and find the recovery.img file. Copy recovery.img to the root of your sd card (in other words just drag and drop the recovery.img into the sd card)
5. obtain a root shell. If you don't know what that means you REALLY should not continue with this tutorial!!! open up a terminal/cmd prompt and start the adb.
Code:
adb shell
Code:
su
The prompt should now change to # indicating that you have gained root access. a prompt screen may show up on your tablet asking you to allow "unknown" root access. Click allow and proceed to the next step.
6. Flash the recovery.img from the root of your SD card
Code:
flash_image recovery /sdcard/recover.img
* I think this should go without saying, but you do have to insert the sd card into tablet and allowing android to mount it...
7. reboot into your new recovery
8. make a backup of your system. This is a precautionary measure to ensure that you will have at the very least a working system to boot back into. Reboot.
9. before you flash the cyanogenmod rom, you will have to do a factory reset and format /system from recovery. Once you've done this, you can proceed to flashing Cyanogenmod 7 rom. After the flash completes, reboot the tablet. Don't be alarmed or think that you've bricked your device. The first boot takes a LONG time. After you boot up for the first time you should be prompted to calibrate the screen. if the tablet doesn't automatically prompt you to calibrate the screen, fire the adb shell back up and enter the command
Code:
am start -a android.intent.action.MAIN -n org.zeroxlab.util.tscal/.TSCalibration
** it has been my experience that after first calibration the screen will not operate properly until after a reboot. Don't be alarmed! Just reboot using the command
Code:
adb reboot
since you probably won't be able to get the tablet to do so from the screen/buttons.
10. Once you have booted back into your tablet which should take considerably less time than the first boot after flashing, you will now be looking at the Cyanogenmod 7 desktop for the first time! Now you need to gain access to the google market. reboot into recovery, which can easily be done now from the shutdown menu.
11. flash the gapps .zip file and reboot
12. Your tablet will go through the "New Phone Setup" process. you will be prompted to set up a bunch of things, but you can skip past a lot of it. once you get to the desktop, connect to your wifi, open the market and off you go!
I have installed the 5.5.0.4 recovery from Koush via Rom Manager. That recovery is broken and it will not let me flash another recovery. I am asking someone who knows how to push a different custom recovery ( like rogue recovery http://bit.ly/ADptUO ) to the device using ADB, to write a step by step guide with all the commands and necessary files to do so. This will help many people who are stuck in the same situation that I have found myself in. Any help will be appreciated, thank you.
This might get you part of the way there. There might be something in there about flashing a new recovery too.
http://forum.xda-developers.com/showthread.php?t=1530337
gee one said:
This might get you part of the way there. There might be something in there about flashing a new recovery too.
http://forum.xda-developers.com/showthread.php?t=1530337
Click to expand...
Click to collapse
It says to type the command though ADB while in CWR... my device does not show up in ADB while in recovery.
If you have access to the rom, you can copy your new recovery to the internal sdcard. You can also type the command in the rom with adb or terminal, but be careful since anything that you have in the staging partition will flash after you type the commands and then reboot. So, 1) copy rom to the internal sdcard, 2) reboot to recovery, 3) flash new recovery (nothing will happen yet) 4) reboot to the rom) 5) type commands in adb 6) reboot 7) then make a step by step guide for the next person.
sent from my cyanogen(mod) vision
hey guys im having an issue with my asus tablet i rooted it i tried to install a different rom but after i restarted it on recovery i cant access my sd also when i press reboot goes back to the recovery menu but if i press vol down and power the cold boot works but everytime i turn it off and back on it boots to recovery menu does anybody knows how to fix this? any help is aprecciated.
Hi all,
I have the same problem with him, is there anyway to uninstall CWM Recovery?
Thanks in advance!
I found this fix its really easy just follow the steps
If you guys are able to cold boot into the OS, use Terminal Emulator to do what ADB would do. 1 - Cold boot into the OS and move files needed to internal sd storage. 2 - Reboot into your bad 5.5.0.4 cwm , install the new cwm through : install zip from sdcard , choose zip from ...
3 - Once installation is done , don't press "reboot system now" , do a cold boot directly (Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot)
4 - Once you've booted your rom ,
run terminal emulator. type : su (if superuser appp ask to you , allow). will give you a # type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : exit
type : reboot
NOTE: Someone say the above steps only work when they skipped the exit part so try it both way.
Typing 'exit' is not necessary as that only ends superuser status. You should be fine going straight to 'reboot.'
Could someone please help me with this? I have posted a thread over on Android Forums with all the problems.
http://androidforums.com/asus-eee-p...restoring-device-big-problem-read-inside.html
Also, I have posted on here in the past about this, but I honestly am a giant noob at android and did not know what they were telling me to do.
Any help would be really great, thanks!
Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.
frederuco said:
Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.
Click to expand...
Click to collapse
I will try this out when I get home. Thank you. I will report back with what happens.
Edit: Also congratulations on 100 thanks.
format your micro SD and only put the ROM you want in it. Now install twrp as other guy said and reboot into twrp recovery in go to wipe and wipe (dalvik, cache, internal memory, system and everything else expect micro SD). Then do a clean installation of ROM and you should be good to go.. if that doesn't work then try easy flash
Sent from my Transformer using xda app-developers app
frederuco said:
Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.
Click to expand...
Click to collapse
This did not work, I still boot into cwm when the device restarts after downloading it.
Here is another thing to try:
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=TWRP.blob of=/dev/block/mmcblk0p4
reboot recovery
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes
frederuco said:
Here is another thing to try:
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=/TWRP.blob of=/dev/block/mmcblk0p4
reboot recovery
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes
Click to expand...
Click to collapse
I cannot connect the device to my computer at all. I have usb debugging enabled and everything. It freezes for a couple of seconds when I plug the device in, and then says that installing the drivers has failed in windows. I am trying to run adb and it says no devices are connected.
BloodyRory said:
I cannot connect the device to my computer at all. I have usb debugging enabled and everything. It freezes for a couple of seconds when I plug the device in, and then says that installing the drivers has failed in windows. I am trying to run adb and it says no devices are connected.
Click to expand...
Click to collapse
You don't need to do this on your PC, so long as you can boot you can do it on your tablet.
frederuco said:
You don't need to do this on your PC, so long as you can boot you can do it on your tablet.
Click to expand...
Click to collapse
Ah, sorry, long time since I've done this. Alright, well I've gotten into terminal emulator and I've typed that exactly, switching over my directory to my microsd though and changing the file name to the exact one. I'm getting a "cannot open for read: No such file or directory" error when I do this. I have also tried moving the file to /sdcard/ and I have named the file twrp.blob, and neither of these have helped.
Did you issue the su command and get a popup for root access?
frederuco said:
Did you issue the su command and get a popup for root access?
Click to expand...
Click to collapse
Yes, that was the first thing I did. I did exactly as you said. I've tried changing file names, changing directories and everything but for some odd reason I'm getting the same error.
Edit: and yes, I'm changing those when I enter them in terminal as well.
Strange.
I'll have to troubleshoot this in a bit. I'll let you know what I find.
frederuco said:
Strange.
I'll have to troubleshoot this in a bit. I'll let you know what I find.
Click to expand...
Click to collapse
Thank you. Here is an image of what I have typed in case it is an error on my part.
http://i.imgur.com/lyJU8MR.jpg
Nope, error is on my part. Remove the "/" after the if=
It should be
dd if=TWRP.blob of=/dev/block/mmcblk0p4
Will update the other posts above.
frederuco said:
Nope, error is on my part. Remove the "/" after the if=
It should be
dd if=TWRP.blob of=/dev/block/mmcblk0p4
Will update the other posts above.
Click to expand...
Click to collapse
And it appears that I am still in clockworkmod when the device boots up.
BloodyRory said:
And it appears that I am still in clockworkmod when the device boots up.
Click to expand...
Click to collapse
Try a normal reboot at the end instead of reboot recovery and see if that works.
If not, run through this and download one of the flashable .zip files (it is version 2.2.X.X) and see if that works. If so, then run through GooManager to get the 2.3.2.3.
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
djakolis said:
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
Click to expand...
Click to collapse
You can still enter RCK ??
Not that this helps your situation, so apologies.
Just started getting the screen flicker/lines randomly when handeling it. So my guess was just the loosining of something internally.
I`m also freecarding it. So that hadden`t crossed my mind.
Time for a tear down vid I guess.
Best of luck tho.
I'll make a quick video. Be right back to you...
Edit: I cannot post a video due to XDA rules, but you can search for it: TF700 no fastboot, recovery stuck (search for recent uploads, d jakolis is my username on YouTube) If you guys cannot find it, I can email the link to you.
As you can see in the video, there is not much left to do with the tablet.
However, when I selected Wipe Data on bootloader, did it wipe kernel too? I'm asking this cause I had installed data2sd.zip along with its corresponding kernel.
What would happen if someone else with the same device installed the custom ROM on MicroSD card and handed me his MicroSD card to pop in my tablet? Would it boot off it? Would I be able to enter Android and maybe somehow re-flash recovery and stock kernel along with stock ROM?
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
_that said:
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
Click to expand...
Click to collapse
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
djakolis said:
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
Looks like your /data partition is not formatted properly. Try this (don't type "#" and the following comment):
Code:
adb shell # connect to a shell on the device
killall -19 recovery # suspend the recovery so that it doesn't interfere with formatting
make_ext4fs /dev/block/mmcblk0p8 # format /data
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 # remove "wipe data" request
reboot
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
djakolis said:
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Click to expand...
Click to collapse
Maybe the "killall -19" stuff didn't work and the recovery was not suspended, so it may have somehow determined that the wipe was finished and initiated a reboot.
djakolis said:
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
Click to expand...
Click to collapse
What is installed? Whatever recovery, kernel and ROM you installed last. No other apps since you just formatted /data.
Since the nvflash (flatline) process saves only BCT, bootloader, partition table and unlock token (basically all the stuff you need to get fastboot working on a hard bricked tablet), you can do that now.
djakolis said:
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
Click to expand...
Click to collapse
Lots of reading here, lots of googling and more reading. Experience with Linux on PCs helps too.
where can i wirte this codes i dont know , can anyone help me??? i have same problem
i can not connect device also in adb mode pc didnt accept the drivers
y3akup said:
i can not connect device also in adb mode pc didnt accept the drivers
Click to expand...
Click to collapse
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
berndblb said:
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
Click to expand...
Click to collapse
i tried this tool before but still in the device manager page i have transformer device with yellow flag
y3akup said:
i tried this tool before but still in the device manager page i have transformer device with yellow flag
Click to expand...
Click to collapse
You need to install the drivers - right click on the yellow ? and choose install drivers
Use these ones here:
http://www.androidfilehost.com/?fid=23329332407571009
http://www.androidfilehost.com/?fid=2332933240
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
y3akup said:
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
Click to expand...
Click to collapse
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
sorry but it says dd is not inside or outsite command and bla bla i cant translate directly but like this
is not recognized as an internal or external command, operable program or batch file
berndblb said:
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
Click to expand...
Click to collapse
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
y3akup said:
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
Click to expand...
Click to collapse
Splendid!
Now - did you a full wipe in TWRP before installing the rom? Select the Wipe option and swipe the button. Then re-install the rom.
On the last page of the Aroma installer you have the option of saving the installation log. Do it.
Then back to TWRP, go to Advanced and also save the recovery log.
If the ROM still doesn't boot, post both of those logs.
Also try to capture a logcat of the boot process
Code:
adb logcat -v long > logcat.txt
Post that one too.