Related
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
Today I felt ambitious and tried to install a new JB rom (AOSPA 4.2.2). The instructions said that if I had 3 icons I would be on JB bootloader and that I would need to upgrade to the latest TWRP 2.5.0.0 (I was on 2.4.4.0). Well, what I missed is the fact that there were two different versions of 2.5.0.0 (one specifically for JB 4.2) and of course I flashed to wrong one.
Now when the tablet boots it goes straight to recovery and asks for a PW (I don't know the password and never set one). I can select cancel which lets me into the main menu but none of the functions actually have write access. Nothing mounts or lets me gain access to the internal memory. When I try to reboot it immediately goes back to recovery, never letting me get back into fastboot to install the correct version.
Reading some forums and doing some other google search I don't find anyone with exactly the same problem, but it seems that I cannot get out of this mess. I know that nvflash is out of question since that is not working on JB yet.
If anyone has encountered a similar issue or knows how I could potentially get fastboot to trigger again so I can flash the correct version of recovery, that would be a great start.
Thanks !!
Have a look here
http://forum.xda-developers.com/showpost.php?p=42254642&postcount=10
pjc21 said:
Have a look here
http://forum.xda-developers.com/showpost.php?p=42254642&postcount=10
Click to expand...
Click to collapse
Great, That is exactly what happened. Looks like I'll be looking for a new tablet.
I am wondering if the Google Nexus 10 would have a similar risk of bricking. Guess it's time to do some research.
Thanks.
anosis said:
Great, That is exactly what happened. Looks like I'll be looking for a new tablet.
I am wondering if the Google Nexus 10 would have a similar risk of bricking. Guess it's time to do some research.
Thanks.
Click to expand...
Click to collapse
You may want to check & confirm that fastboot will not flash (you don't get the blue bar on tab when flashing) before looking for a new tab, although this "fastboot flash brick" issue results about 90% of the time you may be lucky and be in that 10% that does not.
You should be able to access fastboot using the "adb reboot-bootloader" command while in recovery, if pc does not pick-up device for adb in recovery have a look here and follow on from the device manager part.
When you get to the bootloader menu have a look at the text in the top left and confirm which 4.2 bootloader version your on, either 10.6.1.8 or 10.6.1.15.3 - then download the correct twrp version for that bootloader and see if you can flash it via fastboot.
If that does not work, which will most likely not would you like to try something for me? which may or may not work, just an idea.
Download this file, unzip it & copy the bootloader.bin file in your android-sdk/platform-tools folder.
Boot back to fastboot using the adb reboot-bootloader command and try
Code:
fastboot -i 0x0b05 flash bootloader bootloader.bin
If this works and does not freeze the tab then
Code:
fastboot reboot-bootloader
If the tab does reboot to this command then check the bootloader version here in the bootloader menu and if it has worked it should say 10.4.2.20 in the text in the top left of the screen.
If by chance this has worked then you should also now have 4 icons in the bootloader as you will now be back on a 4.1 bootloader.
If this does work at all let me know for next steps.
pjc21 said:
You may want to check & confirm that fastboot will not flash (you don't get the blue bar on tab when flashing) before looking for a new tab, although this "fastboot flash brick" issue results about 90% of the time you may be lucky and be in that 10% that does not.
You should be able to access fastboot using the "adb reboot-bootloader" command while in recovery, if pc does not pick-up device for adb in recovery have a look here and follow on from the device manager part.
When you get to the bootloader menu have a look at the text in the top left and confirm which 4.2 bootloader version your on, either 10.6.1.8 or 10.6.1.15.3 - then download the correct twrp version for that bootloader and see if you can flash it via fastboot.
If that does not work, which will most likely not would you like to try something for me? which may or may not work, just an idea.
Download this file, unzip it & copy the bootloader.bin file in your android-sdk/platform-tools folder.
Boot back to fastboot using the adb reboot-bootloader command and try
Code:
fastboot -i 0x0b05 flash bootloader bootloader.bin
If this works and does not freeze the tab then
Code:
fastboot reboot-bootloader
If the tab does reboot to this command then check the bootloader version here in the bootloader menu and if it has worked it should say 10.4.2.20 in the text in the top left of the screen.
If by chance this has worked then you should also now have 4 icons in the bootloader as you will now be back on a 4.1 bootloader.
If this does work at all let me know for next steps.
Click to expand...
Click to collapse
Followed your google usb instructions to make ADB work. Executed the bootloader command and was greeted with the three icons (4.2 bootloader I believe). Then flashed the correct TWRP 2.5 4.2 (no blue progress bar) and waited for the command prompt to show successful write. Rebooted and when recovery started up, showed nothing was different. Still requires me to enter a PW and none of the mounts work.
Then followed your bootloader update instructions and while it said it was successful I only get three icons when in fastboot.
Should I try the older TWRP that I had on there before (2.4.4.0) to see if that at least lets me back in?
anosis said:
Followed your google usb instructions to make ADB work. Executed the bootloader command and was greeted with the three icons (4.2 bootloader I believe). Then flashed the correct TWRP 2.5 4.2 (no blue progress bar) and waited for the command prompt to show successful write. Rebooted and when recovery started up, showed nothing was different. Still requires me to enter a PW and none of the mounts work.
Then followed your bootloader update instructions and while it said it was successful I only get three icons when in fastboot.
Should I try the older TWRP that I had on there before (2.4.4.0) to see if that at least lets me back in?
Click to expand...
Click to collapse
Miraculously the tablet will allow me now to cold boot into the previous rom. That at least makes it usable again, but it probably means that I am stuck on this. Also strange is that the tablet now no longer is recognized as a USB device. I cannot access the internal ram??
Under 'About Tablet' my build # shows 10.6.1.14.4/US DEODEX. Not sure if this might help in fixing the recovery issue?
Anyway I am glad I don't have to spend money to get a replacement, but sure hope I can fix the existing recovery image issue.
So tried to flash back the previous version of TWRP and it will not. Even though the fastboot command prompt shows a successful flash nothing appears to be changed, which refers to the original issue that states that I am stuck on whatever rom is on this tablet.
Is the reason I cannot flash back an older or correct version because there is a permission issue? Is there something I can do directly from within the rom after it boots up, like the shell emulator?
I have 2 Xoom tablets, in Germany, and I took the SD Card from one of them to put it on a new phone, the Tablet kept working fine until last week that I forgot to plug it and the battery ran out. When I charged it and started it, it didn´t work again, I got the Encryption message, nothing happens when I click the Reset Tablet either, I tried putting the SD card from my other Xoom but still nothing. I enter the Recovery mode and did a Factory Reset and the tablet was OK.
Battery run out again yesterday and got the same problem once again, but now factory reset is not working, tablet stays stuck at the "M" logo after doing it, I have repeat the operation a zillion times and nothing, it stays on the M. Plus I can´t turn it off either.
The model is the MZ604 and Android Version 4.0.4
I connected the xoom to the computer after installing the drives but it won´t recognize it. I got to do the fastboot and flashed motorolas images but nothing. I can´t do the adb reboot bootloader command because ADB won´t work, because I don´t have USB Debbuging checked, but I can´t check it now because I can´t get to settings (
What can I do to recover the tablet?
Anyone, is driving me crazy, no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either
I tried RDS too and after the reboot stays the same in the M logo, nothing changes. What can I do?
No ideas? :crying:
I want to save the tablet if possible.
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
alecbond said:
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
Click to expand...
Click to collapse
Yes I mean stock images, and yes, it always stays on Xoom default, it never changes no matter which Recovery image I flash.
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
alecbond said:
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
Click to expand...
Click to collapse
Thanks for the info, sadly I have done almost all that, I can´t use adb commands because I never allowed the tablet to do USB Debbuging, since I wasn´t doing anything that needed that and never thought I would need it. I think I didn´t kept the tablet connected to the PC, so I will try again and let you know if it works.
Like I said before, I'm unsure whether it'll work as I'm not an expert.
However, you may find this helps:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
I believe ClockworkMod Recovery enables USB debugging anyway, through modifying default.prop
I'd recommend trying the above, and/or if that fails for any reason download Motorola USB Drivers here.
Thanks again but nothing works, I tried rebooting being connected to the PC and the same thing happens, the default recovery from the Xoom stays there, fastboot shows on the command Prompt and in the tablet that everything went ok and the new image was flashed but the rebooting kills it, and I can´t use any ADB commands because of the stupid USB Debugging, if something like this can happen, Motorola should have left it open from default or at least have a fail safe in case something like this could happen. RDS also flashes an image but when it rebbots the whole thing goes to hell, it stays on the damn logo with the same images. I think I can throw the tablet to the trash :crying:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
alecbond said:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
Click to expand...
Click to collapse
Thanks, but I have done everything, what is the good thing of a successful flash when the tablet returns to it´s previous state as soon as it reboots?
Plus I can´t use one of the most important things, adb, because of the usb debugging, I can´t get into the tablet to activated it, and even if there are recoveries which bypass this thing, I can´t flash them into the tablet, well I can, they just aren´t there after the reboot. And all this because the tablet run out of battery :crying:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Click to expand...
Click to collapse
alecbond said:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Click to expand...
Click to collapse
The problem lies with the recovery, I only have the default recovery from the xoom, it doesn´t matter how many times I flash it and everything seems to work correctly, when I restart the tablet I get the default recovery. I don´t understand why this happens, command prompt and the tablet in fastboot mode tell me the recovery has been flashed, but to use it I have to reboot and when I do I always find the same good for nothing recovery.
recovery
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
pots22 said:
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
Click to expand...
Click to collapse
Here is what happens, I flash new recovery, I restart the xoom with power and volume up, when the logo appears, after 3 seconds, I push volume down, recovery option shows, I press volume up and the default recovery is still there, not the new one I just flashed.
Is really no one out there that can help? :crying:
There's nowhere stated that, however I believe you already have unlocked your bootloader, didn't you? Because it's REALLY weird that it can't flash the recovery, I mean, you left the battery run out, then after charging you wasn't able to boot normally again.
I'll think a little, but give a check if your bootloader is really unlocked, the device should have installed the recovery, and as you didn't restart it entirely (let it go after the dual core logo), the recovery should be there...
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
I have done the fastboot oem unlock command, should I do it everytime? I can´t use adb, because like I said, I never check the USB Debugging, which I have done in my other tablet now, don´t want the same thing to happen twice.
is it dead?
hgokuh said:
is it dead?
Click to expand...
Click to collapse
I unfortunately believe that yes, however I'm still thinking about it! So don't give up! As soon as I have another answer I shall post something
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Hi. I'm trying to flash my TF300T to the latest stock ROM. I'm currently on 4.2.1 and bootloader 10.6.1.15.3. Reason being i can't flash TWRP 2.8+ to install lollipop because i get splitscreen issue, so i'm trying to get the latest bootloader by getting the official one...
Ok, now to the problem. Fastboot is setup and working properly. ADB commands work, fastboot commands work.
Problem is, when i try and flash using this command "fastboot -i 0x0B05 flash system blob" (i have placed the blob file in the fastboot directory), it renders my computer practically useless, in other words everything is super slow. In CMD after entering the command nothing happens. It's almost like it's working insanely hard, yet nothing is happening. The first time i let it go on for about 30 mins because i didn't want to interrupt it if it was flashing, but i decided to hard shutdown my computer. Nothing had been done and the tablet turned back on as normal
Any help would be great...
grimsonfart said:
Hi. I'm trying to flash my TF300T to the latest stock ROM. I'm currently on 4.2.1 and bootloader 10.6.1.15.3. Reason being i can't flash TWRP 2.8+ to install lollipop because i get splitscreen issue, so i'm trying to get the latest bootloader by getting the official one...
Ok, now to the problem. Fastboot is setup and working properly. ADB commands work, fastboot commands work.
Problem is, when i try and flash using this command "fastboot -i 0x0B05 flash system blob" (i have placed the blob file in the fastboot directory), it renders my computer practically useless, in other words everything is super slow. In CMD after entering the command nothing happens. It's almost like it's working insanely hard, yet nothing is happening. The first time i let it go on for about 30 mins because i didn't want to interrupt it if it was flashing, but i decided to hard shutdown my computer. Nothing had been done and the tablet turned back on as normal
Any help would be great...
Click to expand...
Click to collapse
Wrong command!
You can't flash whole ROM blob on 'system' (i.e. OS) partition because ROM blob contains bootloader, partition table, recovery, kernel, system and userdata, which are to be flashed to other partitions.
Therefore our Transformers have a 'ramp-up' partition called 'staging'. On reboot bootloader flashes the 'sub'-blobs of blob (blob.EBT, blob.SOS, blob.LNX, blob.PT, blob.USR) to their respective partition.
Use:
Code:
fastboot -i 0x0b05 flash [b]staging[/b] blob[enter]
fastboot -i 0x0b05 reboot [enter]
Really?? you see, i have been following a few tutroials on doing this on this tablet, and all of them gave me that command. Thanks a lot anyways, will try
grimsonfart said:
Really?? you see, i have been following a few tutroials on doing this on this tablet, and all of them gave me that command. Thanks a lot anyways, will try
Click to expand...
Click to collapse
This should work! However it will last along time. When tab reboots, you will see a blue progression bar, which sometimes seems to freeze. Let tab restart by itself.
If you don't succed, you might have a corrupt blob, either by downloading or by unzipping with an outdated winrar (suffered that myself).
Well, no luck first time. Exactly the same thing happened when using that command in CMD. Not sure if it's a problem with my PC or what... Going to re-download the files from ASUS.
Not sure what you mean with that blue progression bar? (really long time since i have messed around with my tablet) You mean on the tablet? When i'm in fastboot and trying to flash nothing happens, i see the same rck, android, whipe data and all the writings on top left is the same.
I am doing this one a really old computer though (no access to mine atm). It's windows XP SP3, 1gb ram and intel celeron 1.8ghz i think. Not sure if it has anything to do with this but anyways.
grimsonfart said:
Not sure what you mean with that blue progression bar? (really long time since i have messed around with my tablet) You mean on the tablet? When i'm in fastboot and trying to flash nothing happens, i see the same rck, android, whipe data and all the writings on top left is the same.
Click to expand...
Click to collapse
When you flash to staging, bootloader copies blobs to their partitions after reboot, while this happens, a blue progression bar is visible on ASUS Screen not on bootloader screen.
As you report it, you are probably not in fastboot mode.
Try to follow:
1. Press power + vol down -> bootloader screen appears with icon RCK blinking. Now you are in fasboot mode.
2. Connect tb to pc; tab should show up in Win's device manager as ASUS fastboot device(o.s.). If warning sign appears or 'unknown device' label, install proper drivers.
3. Open terminal window with admin permissions in fastboot folder.
4. Type
Code:
fastboot devices [enter]
-> device should be shown; if not: type
Code:
fastboot -i 0x0b05 reboot [enter]
tab should now reboot into OS; if not, fastboot doesn't work.
5. Try procedures 1. to 4. with every single USB port available. If no success try different pc (normally WINXP is no deal breaker, Win 8.1 sometimes might be).
6. Report.
It worked now . I just had to wait for about 20 minutes then it started sending "staging". Aftr that it all went fine. I guess it was just the computer being a ****.
Succesfully booted into android too. Everything working fine. +1 for your help anyways man. Cheers
grimsonfart said:
It worked now . I just had to wait for about 20 minutes then it started sending "staging". Aftr that it all went fine. I guess it was just the computer being a ****.
Succesfully booted into android too. Everything working fine. +1 for your help anyways man. Cheers
Click to expand...
Click to collapse
Glad to be of any help.
You might add to your OP tag [Solved]
First I'll give credit where it is due. From two threads on this site is where I got help with this issue:
I followed THIS guys steps for manually erasing and got the recovery images and lots of other useful information from HERE. Thank you guys very much!
OK, so, hopefully I can help someone with my little story as well. I was having issues with apps and programs crashing on me with lollipop and the new marshmallow update. The tablet just wasn't working properly and moving slow. I even had the SD card holding all my apps and larger files so I didn't overload the internal storage. So, I decided I wanted to flash back to factory/stock recovery and go from there. I did this using THIS method. I flashed via the "flash-all.bat" file (the command in fastboot is the same as the file name). I should note that there was one instance that failed during the install (I did try it again and got the same failure). Said something about “did you mean you wanted to flash this partition” or something, then showed it failed. After flashing I hit continue on the bootloader screen of the tablet and it said it was "cold booting." After about 5 minutes or so it started to boot but never made it past the NVidia screen. I tried wiping the phone with factory reset, wiping the cache, etc. and then re-flashing the recovery (again with the .bat file). I tried flashing TWRP but it didn't install apparently, because it still went to factory recovery. I even re-locked and then unlocked my bootloader to see if that would set everything straight. Nothing seemed to work. I knew I would eventually find a solution though so I kept looking. Stumbled on some other people that had the same issues but no solution (hope those people got it figured out). So here's what I did after some more research:
First, if you're in this situation and you did factory reset to try and resolve the problem, you may feel like you can no longer communicate with the device via fastboot/adb, but as long as you have the usb drive and your SDK tools installed (I used CodeWorks for Android all-in-one program) that shouldn't be a problem. You'll just have to be in the bootloader on the tablet.
-If for some reason you deleted or uninstalled your drivers and tools you'll have to download them again and then, the computer should still be able to communicate with the tablet. In the device manager under portable devices it will still show up as Module something or other. So the computer still sees the device but doesn't fully recognize it yet. Don't worry, this should still work! Just make sure you that fastboot is seeing the device by inputting "fastboot devices" in the command window and a 14 digit serial number should pop up. If it just says "list of devices" or there's nothing then you wont be communicating with the tablet.
Your device should be connected to your computer and started in bootloader mode. On your computer you should have the command prompt for adb/fastboot open. I just go to the folder where the .exe files are located and hold shift and right click in the white space of the folder, then select "open command window here."
From here follow the erase steps: stolen from manigault! :highfive:
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
Then flash your recovery MANUALLY:
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
You can download whatever recovery version you wish. I downloaded 2.2.2 because that's what my device came with out of the box on Christmas 2014. It will more then likely be a .zip file. To make this whole process a little easier simply extract the files in the .zip file where the adb.exe and fastboot.exe files are located (folder should be named platform-tools) and you can completely eliminate typing the whole directory before the file name. ***After your done flashing everything you can go back and delete those files if you want. Just double check that you're deleting the right files by looking at the original zip file. Not sure if it makes a difference but I deleted them anyway.
For example the commands in fastboot will look like this exactly :
(after extracting recovery files into platform-tools folder)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Note: Do NOT use the flash-all.bat command as this doesn't seem to work for this situation. Do it manually like shown above. And let each individual process complete before attempting to input another command.
After this step I didn't select continue on the bootloader. You can either select reboot or simply input "fastboot reboot" into the command window. It may take about 5 minutes to start installing everything but just be patient, it should start. Sometimes with these things you have to do things twice before it works. If for some reason it doesn't work the first time then start from the beginning and try it again. It took two times for me, but that's because I installed system.img twice and was getting double screen. Newb error... and I was a bit inebriated last night when I did this.
Hope this helps someone!
Thanks again to manigault and MidgetMob!
NVIDIA download files HERE!
i think i done the same thing
but the problem i now have is i cnt get tablet into fastboot on pc. i can load fastboot on tablet with power and volume down , but the tablet only shows as MTP device in device manager. i have downloaded drivers from nvidia and no matter what i try i cant install them i have been through all instructions but scince it went to mtp device i cant get device showing in adb. The only way i can get device showing in adb on pc ist to select apply update from adb ! but none of these commands listed in your post will work because its in sideload. is there anyway i cn reset , flash custom rom ect bu using commands while device is in adb sideload.
all i get is now send the package you want to apply to the device with "adb sideload <filename>".....
if you could shed any light on this it would be much appreciated , thanks , lester
did you update official android 6.0 before? then, not working stock recovery, stock boot...
If you can enter bootloader mode, download unofficial twrp 3.0.0.0 (here http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117) and flash it.
i have a working boot.img file on marshmallow if you want.. please reply.
Sorry for the late response! I have no clue how you got into sideload??? Are you talking about through the recovery on your device? You're not able to get adb/ fastboot to recognize the device, right? It doesn't matter how you get the tablet into the bootloader. Whenever you have the phone in the bootloader then you'll use the fastboot command to "talk to" the device; i.e. "fastboot devices" without the quotes. That command should show your device if it shows as an MTP device whenever you open your "device manager" in windows. That's the same exact situation I was in. Download the codeworks from nvidia like I linked above. Hopefully then you should be able to recognize your device through the bootloader. If not DM me and I'll try to help you.
I'm having the exact problem as Lester. Tablet boots into bootloader but won't connect to computer. So I go into recovery mode and nothing works except apply update from adb. Which brings up the side load message that Lester quoted. And bootloader is showing "device=locked". I am attempting to fix this tablet for a friend that messed it up trying to flash a custom rom. Problem is he had no idea what he was doing and I'm not exactly sure what he did. I do however have a lot of experience with rooted android devices and flashing so any help would be GREATLY APPRECIATED!
---------- Post added at 05:59 PM ---------- Previous post was at 05:55 PM ----------
Also, I've already tried flashing stock rom back onto the tablet by applying update from sd card function in the recovery but when I try to do that the tablet for some reason can't mount the sd card.
rom fiend said:
Tablet boots into bootloader but won't connect to computer.
Click to expand...
Click to collapse
If you've got the device in bootloader then you need to use fastboot, not adb. Try the command 'fastboot devices' and see if the device id is listed. If so then grab a factory image, unzip it and use fastboot to flash the .img files using the commands 'fastboot flash system system.img'. Just make sure to match the partition names to the files.
Hello i have similar issue except when i try flash something i get this error ''remote: file write failed''
and i have to reboot into fastboot to get it flashing fully
but even though i managed to flash everything by rebooting when i boot system nothing shows up, i can just see the back light coming on and turning off after a while
Please help