Database Info

Help with wifi!!! I beg u guys!!!

myxoom wont boot and it stuck at the boot logo! help pls!

Walk back into the store, walk up to customer service and say "It won't turn on"
That's about your only solution when someone loads a 3g kernel.
You might be able to try to Power Off, power on Press and hole Volume up and power when you see the moto logo.

i tried but failed! sad thing is i m staying malaysia n i ordered it via online!!!
pls! help me!

pls! i m gonna cry

Can you get into fastboot? You might want to try reflashing your boot and system partitions. I believe it was BeagleBoy that grabbed them off of a stock Xoom Wi-Fi. You're already unlocked I imagine. Should let you flash those right back in and start fresh.

This guy got out of a semi-brick by doing something similar.
http://forum.xda-developers.com/showthread.php?t=973355

Scourge1024 said:
Can you get into fastboot? You might want to try reflashing your boot and system partitions. I believe it was BeagleBoy that grabbed them off of a stock Xoom Wi-Fi. You're already unlocked I imagine. Should let you flash those right back in and start fresh.
Click to expand...
Click to collapse
If you can get into fastboot, you should be fine. Don't panic just yet.
Try reflashing the stock boot.img and system.img files through fastboot. I did it a few days ago http://forum.xda-developers.com/showpost.php?p=12832155&postcount=33
You can find boot.img and system.img for stock wifi xoom on the OP of that thread.
Failing that try the semi bricked solution.
I hope you solve your problem.

how do i enter fastboot?
sad is, now my machine stucks in boot screen (moto logo) .. n my com have no respond with it at all. any suggestion pls

omnia1994 said:
how do i enter fastboot?
sad is, now my machine stucks in boot screen (moto logo) .. n my com have no respond with it at all. any suggestion pls
Click to expand...
Click to collapse
Power off the device.
Then hold Volume Down and hold Power on at the same time.

it shows "Starting Fastboot protocol support" and stopped there. what this mean? =(

that means you should be able to get it running again.
follow the first message in this thread:
http://forum.xda-developers.com/showthread.php?t=1010568
probably from the stuck at 'dual core technology' bit...
but I think this is what you should follow:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push vold.fstab /system/etc/vold.fstab
adb reboot
you might also want to pick up the stock wifi images:
http://forum.xda-developers.com/showthread.php?t=1017398
and flash them using:
fastboot flash system system.img
fastboot flash recovery recovery.img
(you've already flashed boot.img above).

omnia1994 said:
it shows "Starting Fastboot protocol support" and stopped there. what this mean? =(
Click to expand...
Click to collapse
If you're lucky, your computer will connect and typing in "fastboot devices" will show an entry for your Xoom. You do not need to start with ADB if you're already in fastboot mode.
From there, flash the boot.img for the proper Xoom version you have. You may also want to flash the system.img as well.
From there, simply try to reboot using "fastboot reboot". Make sure your Xoom starts up. If it does, you're pretty much good to go. I'd root from there manually.

omnia1994 said:
it shows "Starting Fastboot protocol support" and stopped there. what this mean? =(
Click to expand...
Click to collapse
That means you are in fastboot.
You can now try to follow this http:// http://forum.xda-developers.com/showthread.php?t=1010568 skipping the unlock section. Or as scourge recommended, fastboot flash the stock .img files. You can find them here http://forum.xda-developers.com/showthread.php?t=1017398 and the instructions around post #26 in that thread.

but my com cant sense my device =(
n it stucks at boot screen with the words "Starting fastboot protocol support" but just stuck there, this works?

qubit76 said:
That means you are in fastboot.
You can now try to follow this http:// http://forum.xda-developers.com/showthread.php?t=1010568 skipping the unlock section. Or as scourge recommended, fastboot flash the stock .img files. You can find them here http://forum.xda-developers.com/showthread.php?t=1017398 and the instructions around post #26 in that thread.
Click to expand...
Click to collapse
That's not necessarily true. My PC can no longer detect my Xoom in any way whether or not it says "Starting Fastboot protocol support" or "Starting RSD mode 2". I can't get it to say anything else.
I used to be able to get into fastboot. That's how I bricked my Xoom... By trying to oem lock it with what I was hoping to be clean boot, system and recovery image files for the wifi.
Now, I can't even get back in to oem unlock or flash. RSD lite doesn't pick it up in RSD mode 2, but does pick up my old RAZR phone.

omnia1994 said:
but my com cant sense my device =(
n it stucks at boot screen with the words "Starting fastboot protocol support" but just stuck there, this works?
Click to expand...
Click to collapse
What sort of computer do you have? Can you copy and paste what you see when you type "fastboot devices"?
Copy and paste from your command prompt (or Linux terminal) and let's see what you've got.

ok. will report once tried. thx very much =)

Okay. If you can get into fastboot (check by "fastboot devices"), all you should need to do are these two commands if you're connected:
Code:
fastboot flash boot boot.img
fastboot flash boot system.img
fastboot reboot
That should get you close to stock first.

wth, i cant install the android SDK, it said it needs java to be installed. i ve installed that but still cant install the android sdk. =(

omnia1994 said:
wth, i cant install the android SDK, it said it needs java to be installed. i ve installed that but still cant install the android sdk. =(
Click to expand...
Click to collapse
Where error messages are you getting? Are you running 64bit?

[Q] Brickety Brick

I couldn't leave well enough alone and I f'd up somehow trying to flash my pad to 4.2 stock from Cyanogen with TWRP. Now booting thru vol- and power brings up TWRP only. It asks me for a password, which it never has before. I hit cancel and it puts me into home screen. Only ray of hope I see is that ADB still recognizes it and interacts with it. I've tried pushing every ROM I can get my mitts on to the pad. When I try and install it fails after a few seconds. Then the files I just pushed are no longer on /sdcard. I don't have a clue.
Anyone, anyone? Bueller, Bueller...

dedalus2k said:
I couldn't leave well enough alone and I f'd up somehow trying to flash my pad to 4.2 stock from Cyanogen with TWRP. Now booting thru vol- and power brings up TWRP only. It asks me for a password, which it never has before. I hit cancel and it puts me into home screen. Only ray of hope I see is that ADB still recognizes it and interacts with it. I've tried pushing every ROM I can get my mitts on to the pad. When I try and install it fails after a few seconds. Then the files I just pushed are no longer on /sdcard. I don't have a clue.
Anyone, anyone? Bueller, Bueller...
Click to expand...
Click to collapse
Make sure you have flashed the correct version of TWRP. as there are three different versions on their website. If you are confident you have flashed correct TWRP version then you may need to downgrade to the previous version of TWRP. I had a similar issue I downgraded to 2.4.4.0 JB build. Hope this helps

"...you may need to downgrade to the previous version of TWRP."
I can't get into fastboot to install an earlier version. I think I'm screwed.
Theoretically I could use TWRP to totally wipe the pad and then ADB to push the system files back on, but... I don't have that kind of tech knowledge and I doubt anyone who doesn't work for ASUS does.
Edit: My mistake. You can use ADB to install TWRP. I'll give it a shot, though I'm pretty damn sure it's a long one.

dedalus2k said:
"...you may need to downgrade to the previous version of TWRP."
I can't get into fastboot to install an earlier version. I think I'm screwed.
Theoretically I could use TWRP to totally wipe the pad and then ADB to push the system files back on, but... I don't have that kind of tech knowledge and I doubt anyone who doesn't work for ASUS does.
Edit: My mistake. You can use ADB to install TWRP. I'll give it a shot, though I'm pretty damn sure it's a long one.
Click to expand...
Click to collapse
Hey dude just thought I make it easier to understand if you have 3 icons then you will pre load into fastboot if you have four icons then you will have to load fastboot. Lemme know if you run into problems. Happy to help mate.

anaschillin said:
Hey dude just thought I make it easier to understand if you have 3 icons then you will pre load into fastboot if you have four icons then you will have to load fastboot. Lemme know if you run into problems. Happy to help mate.
Click to expand...
Click to collapse
I don't get three or four icons. It boots directly into TWRP. ADB still recognizes the pad and I can still push files to /sdcard. I tried reflashing the ROM but it fails after just a couple seconds, shuts down and boots back into TWRP.
I'm going to get a flashcard reader today and format my external card FAT32 and see if I can't install a new ROM from that.

im in a different situation
i did a erase system in fastboot
now i can only go to fastboot with preload on it
or
apx
is there any wait i can fix it and bring it back to live

Update: Bought a card reader at local Discount Electronics. Plugged it into my PC and it promptly froze my computer and destroyed my $80 64G sd card. Can't catch a break here. So I need to get another card and reader before I can attempt to install rom from external card.
The card reader is by a company called Zeikos. http://www.amazon.com/electronics/dp/B001T9N0R6 You have been warned.

Sheena0220 said:
im in a different situation
i did a erase system in fastboot
now i can only go to fastboot with preload on it
or
apx
is there any wait i can fix it and bring it back to live
Click to expand...
Click to collapse
Can you flash a recovery...
if you manage to flash a recovery run the command: fastboot reboot recovery.

dedalus2k said:
I don't get three or four icons. It boots directly into TWRP. ADB still recognizes the pad and I can still push files to /sdcard. I tried reflashing the ROM but it fails after just a couple seconds, shuts down and boots back into TWRP.
I'm going to get a flashcard reader today and format my external card FAT32 and see if I can't install a new ROM from that.
Click to expand...
Click to collapse
adb reboot bootloader
or
fastboot -i 0x0B05 reboot-bootloader
or
from android terminal - you must be rooted for this to work
su
reboot bootloader

tobdaryl said:
adb reboot bootloader
or
fastboot -i 0x0B05 reboot-bootloader
or
from android terminal - you must be rooted for this to work
su
reboot bootloader
Click to expand...
Click to collapse
I'll give the first one a shot. I can't get into fastboot mode and the su command comes up an error even though I am rooted or was. I really can't figure out where it all went haywire.

YES! I'm in!
tobdaryl said:
adb reboot bootloader
or
fastboot -i 0x0B05 reboot-bootloader
or
from android terminal - you must be rooted for this to work
su
reboot bootloader
Click to expand...
Click to collapse
You are a god amongst men! Thank you sooooo much. If you don't mind...now what?
I get the following messages:
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00e> released by "WW_epad-10.6.1.15.3-20130416" A03
Starting Fastboot USB download protocol
and then the three icons, RCK android and Wipe Data.
After this mishap I don't trust myself to weed through the mountains of info here again. I'm trying to reinstall 4.2.1 and keep it rooted. I'm assuming reinstall 4.2.1 and then reroot, yes? Would you mind terribly pointing me to a reliable post I can follow.
Thank You so much!!!

dedalus2k said:
You are a god amongst men! Thank you sooooo much. If you don't mind...now what?
I get the following messages:
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00e> released by "WW_epad-10.6.1.15.3-20130416" A03
Starting Fastboot USB download protocol
and then the three icons, RCK android and Wipe Data.
After this mishap I don't trust myself to weed through the mountains of info here again. I'm trying to reinstall 4.2.1 and keep it rooted. I'm assuming reinstall 4.2.1 and then reroot, yes? Would you mind terribly pointing me to a reliable post I can follow.
Thank You so much!!!
Click to expand...
Click to collapse
You will have to reroot but with motochopper that is minor.
Unzip 10.6.1.15.3 till you have a blob file. Place the blob in the directory with fastboot.
Reboot into bootloader and wait for fastboot to start. (watch the upper left of the screen)
fastboot -i 0x0B05 flash system blob - wait for the flash to finish then
fastboot -i 0x0B05 reboot
Good Luck!

tobdaryl said:
You will have to reroot but with motochopper that is minor.
Unzip 10.6.1.15.3 till you have a blob file. Place the blob in the directory with fastboot.
Reboot into bootloader and wait for fastboot to start. (watch the upper left of the screen)
fastboot -i 0x0B05 flash system blob - wait for the flash to finish then
fastboot -i 0x0B05 reboot
Good Luck!
Click to expand...
Click to collapse
Grazie Mille! Gonna give it a go right now.
Should I bother with TWRP? I tried to update it before and that's the point it went to hell last time.

tobdaryl said:
You will have to reroot but with motochopper that is minor.
Unzip 10.6.1.15.3 till you have a blob file. Place the blob in the directory with fastboot.
Reboot into bootloader and wait for fastboot to start. (watch the upper left of the screen)
fastboot -i 0x0B05 flash system blob - wait for the flash to finish then
fastboot -i 0x0B05 reboot
Good Luck!
Click to expand...
Click to collapse
Okay. I did it. No joy.
erasing 'system'...
OKAY [2.544s]
sending 'system' <800927 KB>
OKAY [136.994s]
writing 'system'...
OKAY [3.151s]
finished. total time 142.707s
fire off the reboot command
rebooting...
finished. total time 0.551s
But the tab doesn't reboot. And that short "writing 'system'" time to me sounds mighty suspicious
Any ideas? I'm afraid to force reboot it.

dedalus2k said:
Okay. I did it. No joy.
erasing 'system'...
OKAY [2.544s]
sending 'system' <800927 KB>
OKAY [136.994s]
writing 'system'...
OKAY [3.151s]
finished. total time 142.707s
fire off the reboot command
rebooting...
finished. total time 0.551s
But the tab doesn't reboot. And that short "writing 'system'" time to me sounds mighty suspicious
Any ideas? I'm afraid to force reboot it.
Click to expand...
Click to collapse
Reboot into the bootloader. If you get into the bootloader cold boot - volume down on the first icon.
If your tablet fails to boot into android go back to the bootloader and reboot into recovery.
I'll wait for your response.

tobdaryl said:
Reboot into the bootloader. If you get into the bootloader cold boot - volume down on the first icon.
If your tablet fails to boot into android go back to the bootloader and reboot into recovery.
I'll wait for your response.
Click to expand...
Click to collapse
Done and no luck

dedalus2k said:
Done and no luck
Click to expand...
Click to collapse
No recovery either?
What happens in both cases - please explain.

tobdaryl said:
No recovery either?
What happens in both cases - please explain.
Click to expand...
Click to collapse
From off state it always boots into TWRP. I stupidly installed an older version on accident. 2.2.2
With your help I was able to boot into fastboot with the adb command. I've run installs of both the ROM and tried an update to TWRP. According to the console everything went fine but when I give it the reboot command nothing happens. Somewhere in there it looses connections with the tablet it seems.

dedalus2k said:
From off state it always boots into TWRP. I stupidly installed an older version on accident. 2.2.2
With your help I was able to boot into fastboot with the adb command. I've run installs of both the ROM and tried an update to TWRP. According to the console everything went fine but when I give it the reboot command nothing happens. Somewhere in there it looses connections with the tablet it seems.
Click to expand...
Click to collapse
Please explain what happens now. Can you get into the bootloader, recovery, etc?
If you get into the bootloader what happens when you cold boot?
When you boot now without any intervention does it still boot twrp?

tobdaryl said:
Please explain what happens now. Can you get into the bootloader, recovery, etc?
If you get into the bootloader what happens when you cold boot?
When you boot now without any intervention does it still boot twrp?
Click to expand...
Click to collapse
Excuse my noobishness.
I can get into bootloader with the adb reboot bootloader command you gave me
When I go to recovery, RCK right?, it freezes up.
From cold boot it goes directly into TWRP, which asks for a password which it hasn't ever before this mishap.
If I go to android from bootloader and it goes to TWRP as well

[Q] help to get back to stock

tf300t unroot with android 4.2.1
running in 10.6.1.15.3
system always boot to cwm
from pc using cmd using adb reboot-bootloader
in the fastboot mode
with no usb icon
unable to flash with anything
not even able to cold boot
just only able to boot to cwm v6.0.2.3
each time need to cmd to boot to fastboot but no usb icon
any idea
question is this mean im in brick

Sheena0220 said:
tf300t unroot with android 4.2.1
running in 10.6.1.15.3
system always boot to cwm
from pc using cmd using adb reboot-bootloader
in the fastboot mode
with no usb icon
unable to flash with anything
not even able to cold boot
just only able to boot to cwm v6.0.2.3
each time need to cmd to boot to fastboot but no usb icon
any idea
question is this mean im in brick
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=42011887#post42011887 - read this post and let me know if you have any questions.

it doesnt work for me
i did exactly how you say
place the unzip file to sdcard
place the sd card to the side of the mmsd slot
reboot the tablet
nothing happen
even try to reboot in the fastboot mode and press the up button at he rck mode
still no go
i just have no idea how i got to the point that the bootloader fail went i in the fastboot->rck
show that fail bootloader with (0x000000000)
i can only get to APX mode and Fastboot using pc (but i cant do nothing to it) it doesnt show the usb icon
i can read the tablet
but i cant write anything to it
im still waiting for something happen
hope one of this master
have a software and about to bring back to live

Sheena0220 said:
it doesnt work for me
i did exactly how you say
place the unzip file to sdcard
place the sd card to the side of the mmsd slot
reboot the tablet
nothing happen
even try to reboot in the fastboot mode and press the up button at he rck mode
still no go
i just have no idea how i got to the point that the bootloader fail went i in the fastboot->rck
show that fail bootloader with (0x000000000)
i can only get to APX mode and Fastboot using pc (but i cant do nothing to it) it doesnt show the usb icon
i can read the tablet
but i cant write anything to it
im still waiting for something happen
hope one of this master
have a software and about to bring back to live
Click to expand...
Click to collapse
The previous link you were provided only works with stock recovery not cwm or twrp.
The 4.2 bootloader (10.6.?.?.?) does not have a usb icon. When you get to the bootloader press no buttons and wait for notification in the upper left - entering fastboot.

Sheena0220 said:
it doesnt work for me
i did exactly how you say
place the unzip file to sdcard
place the sd card to the side of the mmsd slot
reboot the tablet
nothing happen
even try to reboot in the fastboot mode and press the up button at he rck mode
still no go
i just have no idea how i got to the point that the bootloader fail went i in the fastboot->rck
show that fail bootloader with (0x000000000)
i can only get to APX mode and Fastboot using pc (but i cant do nothing to it) it doesnt show the usb icon
i can read the tablet
but i cant write anything to it
im still waiting for something happen
hope one of this master
have a software and about to bring back to live
Click to expand...
Click to collapse
http://www.androidauthority.com/transformer-pad-tf300t-restore-stock-firmware-108016/ = try this method. this is the fastboot method. FYI, as sheena said, you dont need to see the usb icon. immediately u boot into the bootloader, the tablet enters fastboot mode. if you need more detailed instructios, add me on skype or facebook. i'll be glad to help.

crazynitro said:
http://www.androidauthority.com/transformer-pad-tf300t-restore-stock-firmware-108016/ = try this method. this is the fastboot method. FYI, as sheena said, you dont need to see the usb icon. immediately u boot into the bootloader, the tablet enters fastboot mode. if you need more detailed instructios, add me on skype or facebook. i'll be glad to help.
Click to expand...
Click to collapse
thx for the instruction
i will try it tonight
i think i see somewhere before and try it before with the code in the cmd
at fastboot
while the tablet still flashing with the 3 icon (rck, android, and wipe data)
in pc i type this code as follow
fastboot device
come out the sn #
fastboot -i 0x0b05 flash system blob
then the tablet freeze but the cmd is say success
but i try only one or two time
at this moment i only able to boot in to fastboot by hard reset and the APX
in APX mode the pc didnt recognize the driver
also i try couple at fastboot mode in tablet i hit the upper vol at RCK
it return message as follow
bootloader fail
code is 0X 00000000
i know it is not in brick
the system has no os to boot too
and the tablet has no wait to write anything into it
but i will try the method you have instruct tonight at see any chance
hope no need to send back to the shop to fix it

Sheena0220 said:
thx for the instruction
i will try it tonight
i think i see somewhere before and try it before with the code in the cmd
at fastboot
while the tablet still flashing with the 3 icon (rck, android, and wipe data)
in pc i type this code as follow
fastboot device
come out the sn #
fastboot -i 0x0b05 flash system blob
then the tablet freeze but the cmd is say success
but i try only one or two time
at this moment i only able to boot in to fastboot by hard reset and the APX
in APX mode the pc didnt recognize the driver
also i try couple at fastboot mode in tablet i hit the upper vol at RCK
it return message as follow
bootloader fail
code is 0X 00000000
i know it is not in brick
the system has no os to boot too
and the tablet has no wait to write anything into it
but i will try the method you have instruct tonight at see any chance
hope no need to send back to the shop to fix it
Click to expand...
Click to collapse
i had try the method
tablet freeze as soon as i start the code of
fastboot -i 0x0B05 flash system blob
i do see in cmd say finish and ok
i try code of fastboot -i 0x0B05 reboot
tablet didnt response
try fastboot devices
come back will
??????????????????? list
i just dont know what to do
it freeze all the time as i write something into tablet

Sheena0220 said:
i had try the method
tablet freeze as soon as i start the code of
fastboot -i 0x0B05 flash system blob
i do see in cmd say finish and ok
i try code of fastboot -i 0x0B05 reboot
tablet didnt response
try fastboot devices
come back will
??????????????????? list
i just dont know what to do
it freeze all the time as i write something into tablet
Click to expand...
Click to collapse
which firmware did you download? have you tried flashing a recovery img like twrp?

crazynitro said:
which firmware did you download? have you tried flashing a recovery img like twrp?
Click to expand...
Click to collapse
i use us one and get the blob out
i think i got what you mean now
i have to have the right blob before i can get the flash work if not i will freeze it
the problem is i cant even boot to android
so i have no clue on will firmware i using
all i can see from now is at the fastboot that only is us ...10.6....
is that the firmware i have to flash if do so i will try
i cant even flash the twrp into the tablet
i try blob and img
it wont work
i try the version is the 2.5......4.2.blob or img
it just got no luck at all
thx thx thx

Sounds like you flashed the incorrect twrp for your bootloader, flashing a non-4.2 twrp on a 4.2 bootloader can cause a fastboot flash brick.
Here's a little info about the changes from a 4.1 to a 4.2 bootloader as there have been quite a few bricks here over the last few months.
Still not sure of the exact issue here but seems there was a change in some or all of the partition tables with the 4.2 bootloaders for both 10.6.1.8 & 10.6.1.15.3 and as a result after updating to 4.2 and then flashing TWRP (non-4.2 version) or CWM recovery would give the following outcome when you boot to recovery.
TWRP would ask for a password on boot, you can hit cancel but are left not being able to mount any partition including external apart from possible system.
CWM was the same, unable to mount any partition.
The device will now also likely boot strait to recovery, and if you have not wiped system you will now have to cold boot andriod from now on.
Now the bad part - In about 90% of cases flashing TWRP (non-4.2 version) or CWM would also result in a fastboot flash brick, meaning that some other fastboot commands will work ok, however any fastboot flash command will look to go ok on the command prompt but you will no longer get the blue progress bar on the tablet and nothing will flash to the tablet. So your either stuck with the current os and have to cold boot or if you wiped your system your just stuck.
Only solution so far to this issue is to replace your motherboard. Here's a thread on the issue http://forum.xda-developers.com/show....php?t=2179874
And thus the -4.2 versions of TWRP were made for the 4.2 bootloaders
JB 4.2 bootloaders require the -4.2 versions of twrp
- JB 4.2.1 - 10.6.1.8 = twrp 2.4.4.0-4.2
- JB 4.2.1 - 10.6.1.15.3 = twrp 2.5.0.0-4.2
So if you do not get the blue progress bar on tablet when running a fastboot flash command then sorry to say you have the fastboot flash brick.
There are many many threads/posts on this issue with the above info but still people are not reading, bricking there tablets and creating duplicate upon duplicate threads on this issue, so please look through the threads first, read, read and read some more and if still not sure ask as many questions as you need.
Hope this helps explain what has happened and why the fastboot flash command freezes your tablet.

ok thx for everyone that give a great advice
i just change a new motherbooard
and now the tablet is in a unroot and unlock
i just want a instruction on how to do the unlock and root correctly
i read so many post
i just confuse
im in a android 4.2.1
and us 10.6.1.15.3
any suggestion before i got mess up

Moto G bricked?

Hey guys this is my first thread, I hope it's in the right section
Here's my problem:
Yesterday my Moto G 2013 with CM12.1 just froze (I could turn the screen on and off but that was it)
I tried opening the reboot menu, which worked, but it got stuck on "rebooting", so I just holded the power key until it turned off.
After that I got to the boot logo, but nothing happened from there, not even the boot animation showing up.
Next I tried to boot into TWRP, but it only got to the TWRP boot logo and nothing happened after that, so I flashed CWM, which I could access, but when trying to flash something it just doesn't progress. When I press "reboot to bootloader" on CWM it just freezes there aswell.
In another thread I read that flashing the gpt.bin should fix everything but it didn't help.
I don't really want to perform a factory reset, because of the data loss, but I think this would be my only option.
My question is:
How can I fix my phone (preferably without a factory reset), for example by getting TWRP to work again, because I have a Backup of my system and a zip of CM12.1 on it?
Btw another thing to mention is that when being in Recovery/System USB doesn't really work, but if my phone is turned off or in bootloader it works just fine.

Try "fastboot boot twrp.img" (or whatever the exact name of your TWRP image is). If it gets at least to the curtain screen, run "adb pull /tmp/recovery.log".

_that said:
Try "fastboot boot twrp.img" (or whatever the exact name of your TWRP image is). If it gets at least to the curtain screen, run "adb pull /tmp/recovery.log".
Click to expand...
Click to collapse
When I try "fastboot boot twrp.img" it reboots and get's stuck at the boot logo of android (Motorola logo) and I can hear the "Device disconnected" sound of windows.
But I flashed TWRP into recovery and it get's to the curtain screen. But it doesn't recognize my phone which might have to do with that as soon as it boots into a system USB just won't work

The following command will get TWRP working: fastboot erase userdata

lost101 said:
The following command will get TWRP working: fastboot erase userdata
Click to expand...
Click to collapse
But this will delete everything like my pictures folder, right? Isn't there a way to backup these files ?

@Ju43
adb pull /sdcard/ c:/motog_backup/​

lost101 said:
@Ju43
adb pull /sdcard/ c:/motog_backup/​
Click to expand...
Click to collapse
But adb only works in recovery mode in android, which I can't access right now without deleting everything, right ? And if I delete userdata, will my TWRP backup be deleted, too ? (It's just a backup of my system)
(sorry for asking so many questions, but I really don't wan't to lose all my photos and stuff)

Ju43 said:
But adb only works in recovery mode in android, which I can't access right now without deleting everything, right ? And if I delete userdata, will my TWRP backup be deleted, too ? (It's just a backup of my system)
(sorry for asking so many questions, but I really don't wan't to lose all my photos and stuff)
Click to expand...
Click to collapse
Yes, you do need at least access to recovery mode for adb to work. Try testing TWRP even if it is only partially loading. Also try CWM.
Everything will get erased on internal storage, photos, TWRP backup etc. Unfortunately, you may be left with no alternative.

lost101 said:
Yes, you do need at least access to recovery mode for adb to work. Try testing TWRP even if it is only partially loading. Also try CWM.
Everything will get erased on internal storage, photos, TWRP backup etc. Unfortunately, you may be left with no alternative.
Click to expand...
Click to collapse
Okay, thanks for your answer, but as I mentioned before, as soon as I boot into something like recovery or android, USB doesn't really work anymore (though it seemed to work again in android). Will erasing user data fix this (as it seems to be a software problem) or even better fixing it before erasing userdata, so I can backup my files? And if I erase user data and TWRP/CWM/whatever works, but USB won't then I can't really put a system on it, can I ?

Ju43 said:
Okay, thanks for your answer, but as I mentioned before, as soon as I boot into something like recovery or android, USB doesn't really work anymore (though it seemed to work again in android). Will erasing user data fix this (as it seems to be a software problem) or even better fixing it before erasing userdata, so I can backup my files? And if I erase user data and TWRP/CWM/whatever works, but USB won't then I can't really put a system on it, can I ?
Click to expand...
Click to collapse
Recovery mode ADB can take some effort to make work depending on the version of Windows. Since you obviously want to backup your files, you can try booting into Linux (a livecd will work) and installing adb. Linux adb works without the need for drivers so it may give you access.
If using Ubuntu, the command to install adb/fastboot is:
sudo apt-get install android-tools-adb android-tools-fastboot​

lost101 said:
Recovery mode ADB can take some effort to make work depending on the version of Windows. Since you obviously want to backup your files, you can try booting into Linux (a livecd will work) and installing adb. Linux adb works without the need for drivers so it may give you access.
If using Ubuntu, the command to install adb/fastboot is:
sudo apt-get install android-tools-adb android-tools-fastboot​
Click to expand...
Click to collapse
I see what you mean but I got adb to work most times when android was still working (just not in recovery) but I also had problems with charging when the phone was turned on, so I assume it's a problem with android, but I'll search for a Ubuntu Live CD that should be layng around somewhere here (lol) and I'll try it

@lost101
Ok, I installed adb and fastboot, but now it doesn't even find my phone in bootloader...

Ju43 said:
@lost101
Ok, I installed adb and fastboot, but now it doesn't even find my phone in bootloader...
Click to expand...
Click to collapse
Use: sudo fastboot devices

lost101 said:
Use: sudo fastboot devices
Click to expand...
Click to collapse
Thanks, I didn't think abut that :highfive: fastboot works now, but adb doesn't (again when using fastboot boot TWRP.img the terminal shows that it worked but the phone just reboots and is stuck on the Motorola logo and if I flash TWRP it doesn't work either). Maybe I should mention, that I have that screen flickering and like scanline thingy going on when I boot into recovery.

Ju43 said:
Thanks, I didn't think abut that :highfive: fastboot works now, but adb doesn't (again when using fastboot boot TWRP.img the terminal shows that it worked but the phone just reboots and is stuck on the Motorola logo and if I flash TWRP it doesn't work either). Maybe I should mention, that I have that screen flickering and like scanline thingy going on when I boot into recovery.
Click to expand...
Click to collapse
Can you fastboot boot TWRP.img, then adb pull /sdcard/ ?

lost101 said:
Can you fastboot boot TWRP.img, then adb pull /sdcard/ ?
Click to expand...
Click to collapse
Nope, because as I mentioned it doesn't get to the TWRP logo at all

Ju43 said:
Nope, because as I mentioned it doesn't get to the TWRP logo at all
Click to expand...
Click to collapse
Try CWM.

lost101 said:
Try CWM.
Click to expand...
Click to collapse
Same thing except it started vibratng and didn't stop until restarting after a few seconds 0.o

Ju43 said:
Same thing except it started vibratng and didn't stop until restarting after a few seconds 0.o
Click to expand...
Click to collapse
Maybe you can get the phone booting into Android by fastboot flashing the system.sparsechunks from the Factory Firmware Image for your phone.

lost101 said:
Maybe you can get the phone booting into Android by fastboot flashing the system.sparsechunks from the Factory Firmware Image for your phone.
Click to expand...
Click to collapse
Downloading it right now, could you please exactly tell me what to flash with which command ?

Bootloop when starting android or RCK

I tried to flash a custom rom (KatKiss), and it seems that I did something wrong along the way because the tablet is stuck in a bootloop.
So I rebooted my tablet and access the bootloader ("fastboot devices" recognize my device) and try to go to the recovery (with the TWRP splash screen, "adb devices" recognize my device). Unfortunately after 20 seconds on the splash screen, the tablet reboots (tries to load my katkiss android but bootloop everytime).
Bootloader : 10.6.1.14.10
TWRP : 3.1.1.0
Since the fastboot recognize my device while in bootloader, I think that I should try to flash twrp since it seems to be corrupted somehow.
Every time I flashed a rom nothing went wrong but now that I have a problem I don't want to worsen it and would like some help on the issue.

Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Sent from my Nexus 5X using Tapatalk

Thank you for the fast reply!
I did flash the rom with my current TWRP and only downloaded the rom version for the TF700. Below is what I tried from your suggestion:
I check that my device is recognized:
fastboot device
So I tried flashing TWRP:
fastboot flash recovery twrp-3.1.1-0-tf700t
After it succeeded, I reboot the tablet:
fastboot reboot
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.

That is very strange indeed. Yes, try a 3.0.2 version of TWRP and see if that works.
If not, I would flash the Asus stock blob in fastboot and start from scratch....
Sent from my TF700T using Tapatalk

Kromlech said:
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
Click to expand...
Click to collapse
Not sure if this will help but I had a reboot problem with trying to load into TWRP. I posted my solution into a different thread but will toss it out here..
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basically the same.
https://forum.xda-developers.com/tra...prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessary .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)

I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?

double post

Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
Unidave's link would only help you if you generated your device specific nvflash blobs when the tablet was still functioning. Did you:
flash a specifically modded recovery - flash the moddded bootloader, use wheelie to generate and save your blobs, return everything to factory specs?
I highly doubt it since you would have mentioned...
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/my/support/Download/28/1/0/11/29/8/
Extract the zip twice until you see a blob and a meta-inf file.
Move the blob into your fastboot folder, discard the rest of the file
Issue these commands one by one, letting each one finish before starting the next. Some will finish quick, others may take up to 3 minutes:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
The first boot will take a while, but that should put you back on a stock JB 4.2 system.
Trash all the files you used in your last attempt and redownload the rom, gapps and supersu
Fastboot flash TWRP
Reboot
Format /data in TWRP (this will take up to 1 hour - let it finish!!), then convert /data to f2fs
Flash the rom, gapps, supersu
If you flash Nougatella remember that you have to turn on wifi right after the language selection during setup or Google framework will crash.

Spend the end of the day doing it, but it worked flawlessly! Thanks a lot @berndblb, now I can use my tablet again!

Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
My apologies for the problem with my link, looks like you resolved it, but wanted to post a correct working link to take someone else into the full conversation and context...
https://forum.xda-developers.com/showpost.php?p=71150385

berndblb said:
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Click to expand...
Click to collapse
Broken link ? that post isn't very old, either. ??

berndblb said:
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Click to expand...
Click to collapse
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks

ketulharini said:
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
Click to expand...
Click to collapse
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!

monogwai said:
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
Click to expand...
Click to collapse
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks

ketulharini said:
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
Click to expand...
Click to collapse
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/forum/transformer-pad-infinity-tf700-tegra-3-development/46302-guide-help-my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.

monogwai said:
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
Click to expand...
Click to collapse
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks

ketulharini said:
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
Click to expand...
Click to collapse
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.

monogwai said:
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
Click to expand...
Click to collapse
You mean a batch file with the adb commands right? Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8). Depending on what situation he came from before, it might be a good idea to start all fresh...
The tricky thing are the adb push bootit.ko and the insmod command. Those have to be timed just right to get executed, so a batch file might come in handy. Both commands only take a second or two to execute, so your window of 5 seconds could work. Maybe not in the same session, but they should work.
If the insmod command does not kick the tablet into the bootloader, there are 2 possible reasoons:
adb push bootit.ko did not work
the insmod command did not work
To find out if the file push worked you could add a simple list command for the contents of /sdcard/. Again - tricky, I know since you still are working with the 5 sec window, but that's what you got to work with...
That would look something like in the attached picture. So after pushing bootit.ko you issue:
Code:
adb shell ls /sdcard/
Try it with the batch file, try it with single commands... Don't give up. As long as you have any kind of adb access you should be able to solve it.
Good luck!

berndblb said:
You mean a batch file with the adb commands right?
Click to expand...
Click to collapse
Yeah.
berndblb said:
Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8).
Click to expand...
Click to collapse
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.

monogwai said:
Yeah.
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
Click to expand...
Click to collapse
Care to share the batch file?