Been on the site for a few years modding my phones, just found out that phones are a lot easier, the download of the room got corrupted and my own complacency from changing rooms on my phone so many times left my scooping to do a nandroid, dumb i know. So my tab sits at the splash screen, its unlocked and rooted, i was able to get into CMD but that no longer works after trying a one click brick fix, i can use Vol - and pow to get to that menu which recently list one potion as well, it now only has fast boot and wipe data, and with Vol + and power the screen goes black and the computer asks for vtx(?) drivers. Any help on where to go from here would be greatly appreciated, thanks
Sent from my SGH-T769 using xda app-developers app
flash cmw using fastboot and adb push your desired rom to your tablet's internal memory and flash with cmw?
Sent from my ASUS Transformer Pad TF300T
was working on that on my laptop but it's so cluttered with roms/mods/drivers from the phone, just switched to a nice clean comp going to work on it from here, hopefully it'll help, also not very experienced with adb, but there's enough tut's and advice on here so it shouldn't be to hard, thanks for replying
ok, I flashed CMW with fastboot, pushed the rom I wanted onm and flashed that with cmw, it installed and it didn't help, still sit's at the splash screen, I'm stumped
go into CWM
and use following ADB commands:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
Enter
Wen this is ready the next one
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
Enter
That should be it
ok, ran those commands and nothing happened, don't know if this shows anything of signifigence:
~ # dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
1+0 records in
1+0 records out
100 bytes (100B) copied, 0.005003 seconds, 19.5KB/s
~ # dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
1+0 records in
1+0 records out
16 bytes (16B) copied, 0.004434 seconds, 3.5KB/s
also tried installing the rom again, I looked through the folders with adb quick push, not sure if it shows files or just folders, but all I see is folders, no files at all in any of them
you can try this unbrick tool
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
This will flash the ww.30 Version.
sadly no luck again, this is the one I tried before that removed my cold boot option from the vol - power menu, and removed cwm as well, this is frustrating, thanks for helping out though, I'd love to get this back up and running
Have you tried flashing a stock rom through CWM?
tried a stock deodexed rom, nothing, but I did find something that may be causing problems, I noticed errors on the unbricking app, then on ADB Quick Push I checked the last tab and saw this
"Devices found:
0123456789ABCDEF
Failed to mount as R/W"
if I don't have r/w access it's probably blocking the unbricking from writing the files needed, I tried using adb to change rights and it comes up with this:
"~ # mount -o remount,rw /system
mount -o remount,rw /system
mount: can't find /system in /proc/mounts
~ #"
I'm fastbooting in the cwm + root so I should be able to change it, and it was indeed rooted before the issues, or am I way of track with this r/w thing?
I'm starting to think there's something bigger going on behind the scene's here, the tab isn't retaining anything I do, all memory is gone, every restart it forgets where the clockwork mod folder is until I go into cwm and go into the folder then it shows up, when I fix the permissions under advanced in cwm, it keeps them until it reboots, and now I recall when it started doing all this I took it out of the leather case and the corner of the screen had come out of the casing, perhaps something jogged loose, I'll pop it open and give it a look I guess
thanks to everyone who helped me work on this issue, the problem has been solved, the onefix tool wasn't pushing through and erroring, another user had same problems and resolved issues through fastboot, using his steps it fixed my issues as well, thanks again everyone, post that fixed my tab http://forum.xda-developers.com/showthread.php?p=29142627#post29142627
Related
Right,
I've got this Q-Ware 9.7" tablet which has the Allwinner A10 / Mali setup.
Yesterday I tried to install CM9 on this tablet, but since I'm writing this post it did not work out as intended.
I know there was an issue with the Touchpad not working - which I encountered myself as well. I then installed the "fix" and some compatibility package which was supposed to fix that, but it didn't.
A guy on another forum pointed me towards another compatibility fix that I might have to install as well (was for momo8), but after installing that one the tablet just is not showing anything anymore ........ at all.
It does seem to work as I can connect to it with ADB and DroidExplorer, but that is where it ends.
What I've tried so far is:
- Fix_permissions (it says that it is not allowed to fix permissions in the /system/ folders;
- Clear Dalvik_Cache and /data/;
- Tried to reinstall CWM via ADB;
- Tried to run this command someone else gave me:
adb shell "echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot"
Returns this:
[email protected]:/ $ echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1
conv=sync; sync; reboot
x dd of=/dev/block/nandf count=1 conv=sync; sync; reboot <
0+1 records in
1+0 records out
512 bytes (512B) copied, 0.001510 seconds, 331.1KB/s
reboot: Operation not permitted
Click to expand...
Click to collapse
- I also created a logfile with logcat, please see here: pastebin suffix: dWWXGnPA (cannot post links yet).
- Tried wiping the 'system' folder, does not work as it gives these errors:
unlink() error on '/system/xbin/uudecode' 'Read-only file system'
- It has enough battery (100%) according to the /capacity command in ADB;
- I am able to push/pull things over via ADB or with external SDcard;
Also I noticed the daemon connection seems to drop very often, it just kicks me out on a regular basis.
DroidExplorer works and finds the tablet, but is not showing any folders. I also see the 'boot' folder for example is 0bytes (not sure whether this can also we caused by rights?).
Any help would be appreciated a lot
Before I forget to add ... it is only giving me a blank/black screen. Occasionally I see the backlight change a bit in power, but that's it.
Ive been trying to get TWRP loaded on to my TF300T on 4.2.1 using this guide but on the fastboot its stuck on waiting for device. The device is recognised in the Terminal but have no luck flashing the recovery. Is there any other methods for flashing a recovery I can use on linux or advice.
Im running Xubuntu 13.04
mackay508 said:
Ive been trying to get TWRP loaded on to my TF300T on 4.2.1 using this guide but on the fastboot its stuck on waiting for device. The device is recognised in the Terminal but have no luck flashing the recovery. Is there any other methods for flashing a recovery I can use on linux or advice.
Im running Xubuntu 13.04
Click to expand...
Click to collapse
Is your OS 32 or 64-bit? If it's 64, you may need to have both ia32-libs and ia32-libs-dev installed for fastboot to work properly. Also, did you get the android-tools packages from the repos? I'm not sure about the *buntus, but on Debian, they're in the unstable repos. Make sure you have the newest versions (trust me; it matters).
If you want to do it via ADB, you could do this:
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
Make sure the recovery image is on your internal storage if you do it that way.
I recommend trying to get fastboot working, and use ADB as a last resort.
Its 32-bit, I used fastboot for my N4 so unsure why its not working just now. I tried the method you said but think i may ahve done it wrong it completed the operation but got the Android on its back with the red triangle :/
First time i got :-
1|[email protected]:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
12896+0 records in
12896+0 records out
6602752 bytes transferred in 5.185 secs (1273433 bytes/sec)
Then after that i got :-
127|[email protected]:/ $ dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
ry.img’: No such file or directory <
/system/bin/sh: dd:: not found
127|[email protected]:/ $ dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
1|[email protected]:/ $
mackay508 said:
Its 32-bit, I used fastboot for my N4 so unsure why its not working just now. I tried the method you said but think i may ahve done it wrong it completed the operation but got the Android on its back with the red triangle :/
First time i got :-
1|[email protected]:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
12896+0 records in
12896+0 records out
6602752 bytes transferred in 5.185 secs (1273433 bytes/sec)
Then after that i got :-
127|[email protected]:/ $ dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
ry.img’: No such file or directory <
/system/bin/sh: dd:: not found
127|[email protected]:/ $ dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
1|[email protected]:/ $
Click to expand...
Click to collapse
Stupid question probably, but is your tablet unlocked?
Also, for the second one, you weren't logged in as root. You need to be root to write the image.
Linux 101:
- If you see a dollar sign ($) in the terminal, you're a normal, unprivileged user
- If it's a pound sign (#), you're root.
Also, like I said before, the version of Fastboot matters. Way back in August, I soft-bricked my tablet, and fastboot gave me the same problem it's giving you, even though I had used fastboot on my tablet before that. Months later, I found the fastboot in the Debian repos. I'm not sure what the difference was between the versions, but the new one from the repos worked perfectly, and I was able to get my tablet working again.
EndlessDissent said:
Stupid question probably, but is your tablet unlocked?
Also, for the second one, you weren't logged in as root. You need to be root to write the image.
Linux 101:
- If you see a dollar sign ($) in the terminal, you're a normal, unprivileged user
- If it's a pound sign (#), you're root.
Also, like I said before, the version of Fastboot matters. Way back in August, I soft-bricked my tablet, and fastboot gave me the same problem it's giving you, even though I had used fastboot on my tablet before that. Months later, I found the fastboot in the Debian repos. I'm not sure what the difference was between the versions, but the new one from the repos worked perfectly, and I was able to get my tablet working again.
Click to expand...
Click to collapse
Yeah I unlocked it using the unlocker app and have the this device is unlocked at the boot screen. Forgot the su part :/ what i get for using the up button haha. Yeah it came up with grant superuser access on my tablet, I deleted and reinstalled fastboot the other day to see if it would help but it didnt. Might have to wait until i can access a Windows laptop :/
Sorry I couldn't help. Those are the most common problems/solutions I've seen and personally experienced. And I have no idea why dd didn't work in ADB Shell. I would check the recovery image and try again. Check out adb --help to see if there are any other options available. I'm not overly familiar with ADB.
You could also flash the recovery while booted into Android using Terminal Emulator. That's how I usually flash recoveries. Just use the dd method from the ADB Shell instructions. Just skip the first command, starting ADB Shell, and start at su.
Oh, and I completely missed it earlier, but make sure that the recovery you're using ends in -42.img or - 42.blob. If you use one with -JB, you could brick your tablet. I don't know why the guy giving instructions in your link said to use -JB, but there have literally been dozens of bricked tablet threads here because people flashed a -JB recovery on a 4.2 bootloader. -JB recoveries should only be used with the 4.1 bootloader.
EndlessDissent said:
Sorry I couldn't help. Those are the most common problems/solutions I've seen and personally experienced. And I have no idea why dd didn't work in ADB Shell. I would check the recovery image and try again. Check out adb --help to see if there are any other options available. I'm not overly familiar with ADB.
You could also flash the recovery while booted into Android using Terminal Emulator. That's how I usually flash recoveries. Just use the dd method from the ADB Shell instructions. Just skip the first command, starting ADB Shell, and start at su.
Oh, and I completely missed it earlier, but make sure that the recovery you're using ends in -42.img or - 42.blob. If you use one with -JB, you could brick your tablet. I don't know why the guy giving instructions in your link said to use -JB, but there have literally been dozens of bricked tablet threads here because people flashed a -JB recovery on a 4.2 bootloader. -JB recoveries should only be used with the 4.1 bootloader.
Click to expand...
Click to collapse
Thanks for the help anyway, yeah just glad i read up on the recoveries before hand incase it worked and i got bricked. Ill try using the terminal and see if that works
Hello,
I have nerve-breaking issue with CWM Recovery wich loads up every time i turn on my tablet. So if i wish to restart or to go to CWM i have to hold volume down button to get to bootloader and then select Android to get back to CWM.
So my first question is how do i resolve this problem with constant booting into CWM Recovery? so it would go to recovery only when i select reboot to recovery option in CWM
My next issue is that i have tried to install Ubuntu Touch for TF101 (from ubuntu touch wiki). And in installation guide it says you have to download cm-10.1-20130404-UNOFFICIAL-tf101.zip, and then quantal-preinstalled-phablet-armhf.zip. The fist zip i got successfully but the second link did not exist, so i checked their repository and found similar zip named saucy-preinstalled-phablet-armhf.zip (i tought it's a newer version) well, then i made data wipe and installed both as stated in guide, i also deleted cache and now when i try to boot my tablet i get to blue spinning CWM logo and it stays there for eternity.
So my second question is how to put some other rom on SD card so i can install another rom? or what i have to do to make Ubuntu Touch work?
My third thing that i noticed (for me it seems wrong) is that with every data wipe it makes new 0/ folder and it keeps everything before wipe in it. I made couple of data wipes and now my data structure looks something like this:
Code:
0/
0/
0/
0/
ASUS/
Alarms/
Albums/
AndroZip/
...other folders (apps and data from stock rom)
Alarms/
Android/
Autodesk/
DCIM/
...other folders (probably from first wipe)
Alarms/
Android/
DCIM/
Downloads/
...other folders (probably from second or third wipe)
legacy/
obb/
obb/
So my third question is if this is the correct data structure because it seems wrong for me? And how to resolve that issue?
My un-educated guess is that all three problems are connected, but my android experience and knowdlege is far to small to have a clue how to begin resolving this twisted problem.
I did some researching and as far it goes with second question i think i have soft-bricked tablet (maybe there is still hope?). So i would like to make it back to original rom or 4.2 jelly bean as i had till now without CWM Recovery issue, if possible of course
(Using ClockworkMod Recovery v5.8.3.4 now, and i think at beginning there was ROM Manager used, i bought used tablet)
Please help, thx
The issues are somewhat intertwined, and run back to using CWM 5.8.X.X
The first thing you MUST do is stop the CWM bootloop or you will not be able to install any other ROM or recovery.
If you can boot to a ROM, run a terminal window with SU permissions. If you cannot boot to a ROM, you will need to run from an ADB Shell from a computer when booted to recovery:
Code:
echo boot | dd of/dev/block/mmcblk0p3 bs=1 seek=0
Then reboot normally and your bootloop to CWM should be fixed.
Next, I HIGHLY HIGHLY recommend upgrading to TWRP 2.3.2.3 or higher. The /0/0/0/0 issue has to do with the new directory structure of Android 4.2 for multi-users. CWM 5.8.X.X cannot handle multi-users properly.
TWRP 2.3.2.3 can be updated using the GooManager app (tap the menu key in the top right and choose Install OpenRecovery Script).
IMO, TWRP is far superior to CWM as it has a file manager and terminal emulator.
I am running SidneyK's TWRP 2.6.3.0. He has a zip that can be flashed from CWM to update, however you have to have the boot loop issue resolved or it will not flash.
Ok, as you said i cannot boot to ROM so i tried with ADB Shell but it says
error: device not found
I have device connected on keyboard dock and cable from dock to pc
Any advices how to reslove that issue? Am i missing some drivers?
In device manager i can see that there is a Transformer device with yellow exclamation. I tried to install drivers from asus webpage but it wont install.
Should i get copy of live linux and try from there?
EDIT:
I got the connection working with ADB Shell but i got this response from code you provided
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee image there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?
boonz said:
Maybe i should type?
Code:
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
Click to expand...
Click to collapse
Damn, yeah, it should be ...of=dev/block/...
D'OH!
I made few more edits on previous post as i was trying diffrent things. So currently i'm at this position:
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee logo there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt or should i push some basic ROM from asus webpage to tablet and replace it with Ubuntu Touch in order to proceed with your instructions?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?
Thx
boonz said:
I made few more edits on previous post as i was trying diffrent things. So currently i'm at this position:
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee logo there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt or should i push some basic ROM from asus webpage to tablet and replace it with Ubuntu Touch in order to proceed with your instructions?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?
Thx
Click to expand...
Click to collapse
There are a few ways.
You can use ADB to push the TWRP.zip from sidneyk's thread in the dev section, install that from the internal storage.
If you have a TF101 (non 3G) you can use one of my repacked EasyFlasher in APX mode to push TWRP: http://forum.xda-developers.com/showpost.php?p=43986513
Another option is to use the .blob file (extracted from the zip) and use adb to install when in CWM recovery.
Push the blob file to the /sdcard/ (called twrp.blob for this example)
Use adb shell and execute:
Code:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (you need to see the progress indicator complete before rebooting to recovery). What I do is just hold the power button for 10 seconds, once the progress bar completes and it flashes black, hold VOL DOWN until you see the RCK message then tap VOL UP to boot to recovery. With any luck you will see TWRP.
Now i downloaded TWRP 2.6 for TF101 from teamw.in page and i got that twrp.blob file.
Then i executed adb push and it says it successfully copied file
But when i check in adb shell it says i cannot go or look into sdcard.
Am i missing some sort of permissions? or would live linux still be better option and using it with su might help?
Or is it ok and i should just run dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4?
Code:
C:\Program Files\Android\sdk\platform-tools>adb push C:\Users\BoonZ\Downloads\twrp.blob sdcard
1322 KB/s (4984908 bytes in 3.682s)
C:\Program Files\Android\sdk\platform-tools>adb shell
~ # cd sdcard
cd sdcard
/sbin/sh: cd: can't cd to sdcard
boonz said:
Now i downloaded TWRP 2.6 for TF101 from teamw.in page and i got that twrp.blob file.
Then i executed adb push and it says it successfully copied file
But when i check in adb shell it says i cannot go or look into sdcard.
Am i missing some sort of permissions? or would live linux still be better option and using it with su might help?
Or is it ok and i should just run dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4?
Code:
C:\Program Files\Android\sdk\platform-tools>adb push C:\Users\BoonZ\Downloads\twrp.blob sdcard
1322 KB/s (4984908 bytes in 3.682s)
C:\Program Files\Android\sdk\platform-tools>adb shell
~ # cd sdcard
cd sdcard
/sbin/sh: cd: can't cd to sdcard
Click to expand...
Click to collapse
Try doing cd /sdcard/
If that does not work, you can also just push the twrp.blob to the / directory and push it from there too.
frederuco said:
Try doing cd /sdcard/
If that does not work, you can also just push the twrp.blob to the / directory and push it from there too.
Click to expand...
Click to collapse
Ok superb, i have TWRP it says v2.3.2.3
How do i perform something like format or delete everything (so there will be no 0/0/0/ folders or whatsoever) and make my tablet usefull again. I would like to run jellybean again because i'm pretty used to it and delete that Ubunto Touch mess i made. Maybe little help here, so i don't mess anything up?
Thx
Go to the Wipe section.
Wipe the system, davlik and also the cache.
Choose the FORMAT DATA option to completely wipe the /data/ partition (this deletes everything in the /data/media/ aka /sdcard/ directory)
Then I would reboot back to recovery (suggested after a format data) and then install your ROM, applicable GAPPS and kernel if necessary.
I have had this on the tablet for a while. It is very laggy and too slow to be useful. I tried to install the TWRP recovery (from CWM) and it does not take. I always come back to CWM. I tried using dd to write the TWRP recovery (copy to root of SD card, dd if=/dev/zero of=/dev/block/mmcblk0p3 then dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 (after I had extracted the twrp.blob to the sd cadr)) no luck. So, I wiped it and tried to install KattKiss. It gets stuck booting. I get the 4 dots that go round and round and the logo, but it never boots. So, I went back through the CM10 instructions (http://wiki.cyanogenmod.org/w/Install_CM_for_tf101) and I have 'joy' (definition: it boots and runs), but am wondering what is 'wrong' that I cannot load another ROM image. This is an old machine and there are a lot of meandering threads on XDA and none seem to work for me. I am not averse to 'starting over', but would like some guidance. I have rooted and rom-ed an atrix 4g, sgs2 and sgs3, but this is a bit different. I read that there is a bootloader unlocker for some tf101s, but those links are dead. I see lots of references to goo manager to assist with recoveries and such, but those links are dead as well.
Any help appreciated.
Keith
so I finally figured out how to stop it from recovery looping.
Cold booted it then 1) changed to su (sudo su), I'm running Linux 2) adbshell, 3) echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0 4)
reboot and voila, it will reboot to cm10.
Code:
sudo su
adb shell
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
Now to get kitkat installed. Is there anything else I am doing wrong before I try it again?
Keith
I have a tf101. Tried flashing the newest twrp, and it failed. Here are the details.
Current bootloader: US_epad-9.2.1.27-20120615
Flashed from this recovery: ClockworkMod Recovery v5.8.3.4
Flashed this new recovery: signed_twrp-2.8.1.1_tf101.zip
Installation was reported as successful. I rebooted into Android as instructed. After it had completely booted, I rebooted again and tried to go into recovery, but the device just sat there at the EeePad logo screen. I was able to cold boot into Android using the power-downVolume combination. Instructions on this forum at showpost.php?p=46806749&postcount=187
said to first enter a terminal and type this:su
dd if=/dev/zero of=/dev/block/mmcblk0p3
My result was: /dev/block/mmcblk0p3: write error: No space left on device
4097+0 records in
4096+0 records out
2097152 bytes transferred in 0.455 secs (4609125 bytes/sec)
In spite of the error, I went on. The page said to download twrp.blob and install like this:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
However, that link was no good (404 error).
So I went to the TeamWin Project page for this device at:
twrp2/109
They gave this link to download the latest .blob file:
twrp2/tf101
Which took me to a page listing five versions of openrecovery-twrp, the latest of which was:
openrecovery-twrp-2.3.2.3-tf101.blob
Instructions:
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (NOT to recovery) to complete installation.
I did all this and it still have the same result. So I examined the file signed_twrp-2.8.1.1_tf101.zip and found that it contained a file called twrp.blob. I copied this to /sdcard of the device and tried the same above instructions to flash that.
This didn't work either.
I'm still stuck at the logo, unless I use the key combination to boot into Android.
My bootloader, when I press power-downVolume, gives me the option to "wipe data". I have not done this out of concern I might not be able to boot into Android afterward.
However that seems to be my only next step unless I can find some ideas here.
Somewhere in the middle of all this, I did manage to get out of the loop, and the device now boots directly into Android (I'm running a CyanogenMod v10nightly). But it reboots itself all the time-- not very stable, and I'm looking forward to installing the 4.4.4 KatKiss rom, which is what got me started trying to install twrp.
Can you guys offer any help? Thanks.
Does it reboot immediately or do you have time to open the terminal and enter
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot