Related
I wanted to post this as a reply to some peoples problems in this thread but the posting rules dont allow me access to development forums.......
I was trying to use fastboot but it kept hanging saying it was waiting for the device.
> ./fastboot flash recover recovery-Tiamat-R4c-100611-1150-cwm.img
< waiting for device >
Click to expand...
Click to collapse
using "fastboot devices" gave me the clue
> ./fastboot devices
no permissions fastboot
Click to expand...
Click to collapse
TO FIX IT: I ran the command as root.
> su
> ./fastboot devices
028841444160c3d7 fastboot
Click to expand...
Click to collapse
and then my device showed up and as root I could continue flashing my Xoom.
Hope this helps someone else.
And completely as a side note, does it take anyone else 20 tries to pass every damn captcha on this site?
had same problem, used same fix.
thak you for posting an update, most of the user put just solved, without thinking that other people may need the same solution
thx,
but how can use i fastboot without root ?
rabiny said:
thx,
but how can use i fastboot without root ?
Click to expand...
Click to collapse
You can use udev rules to make fastboot accessible for normal users.
dreamcwli said:
You can use udev rules to make fastboot accessible for normal users.
Click to expand...
Click to collapse
Could you please post a link of this "udev" software? My friend's Xoom updated to 4.0.3 via OTA and he can't get any USB connection recognised by the computer. We've tried everything. It's not rooted and fastboot doesn't work because his bootloader is still locked.
Could you please post a link of this "udev" software? My friend's Xoom updated to 4.0.3 via OTA and he can't get any USB connection recognised by the computer. We've tried everything. It's not rooted and fastboot doesn't work because his bootloader is still locked.
Click to expand...
Click to collapse
udev is not a software (it is but not like you think)
in this context is just bunch of lines you need to add to file (under linux OS)
see: http://developer.android.com/tools/device.html
and here: http://wiki.cyanogenmod.org/wiki/udev
I love you
I have spent 4 hours trying to fix this whole lack of rom on my device thing. You rock.
You are a legend! This solved my problem straight away!
????????
when i use root (sudo) it just sends me back a reply with like a ton of ?
I type in sudo fastboot devices and i get
????????????????? fastboot
what do i do
You're great guys ever in the milkyway. Kiss kiss
fastboot flash recovery /usr/bin/twrp.img
< waiting for any device >
fastboot waiting error arch linux manjaro
twrp installation error
How to flash TWRP Recovery with Linux
This command "028841444160c3d7 fastboot" simply doesn't work anyway. I did it as root. Of course, I did this command with my device number but catching it from adb command
I've been looking around for way to remove it but no avails. Can this be done or reversible? Please help.
newshook said:
I've been looking around for way to remove it but no avails. Can this be done or reversible? Please help.
Click to expand...
Click to collapse
This belongs in Q & A but just flash the firmware from Asus and it will get rid of recovery and root.
Yup what ^ said. And this does belong in Q&A.
Sent from my Transformer Pad TF300T using XDA Premium HD app
duuude!!
newshook said:
I've been looking around for way to remove it but no avails. Can this be done or reversible? Please help.
Click to expand...
Click to collapse
i'm still lost for the answer to this EXACT question ... and this is the only searchable thread that come up with anything near like what I want.
I want to remove TWRP because it doesn't work .. i can't factory reset ... i can't do anything that involves mounting ... so how do i REFLASH over TWRP and go back NOT unlocked ...
interslicer said:
i'm still lost for the answer to this EXACT question ... and this is the only searchable thread that come up with anything near like what I want.
I want to remove TWRP because it doesn't work .. i can't factory reset ... i can't do anything that involves mounting ... so how do i REFLASH over TWRP and go back NOT unlocked ...
Click to expand...
Click to collapse
In Android Terminal, type
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
The "recovery.blob should be the blob of the new recovery u want to install.
Also you can't go back from "unlocked" A lot have people have tried and failed.
If you are more comfortable with fastboot, then maybe try using the fastboot command lines:
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase cache <------not sure if optional or not, but doesn't hurt
fastboot -i 0x0b05 flash recovery <filename>.blob
Or, last but not least, flash the stock rom. It will overwrite the recovery, and you must reroot. Not advising you to do this as a first resort, but just throwing the option out there.
Sounds like you semi bricked the device to me if you can't mount anything in recovery. Search for and follow Buster's guide to fix that issue.
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
Dear all,
If you haven't updated it, don't do it.
My situation now is:
1. It stucks at the red dual core logo; (I think it shouldn't be called a boot loop)
2. It can't be powered down; (even I press and hold the power button forever!)
3. If I reboot it, I can still press the -vol button to choose between modes, but there are only 3: NvFlash; RSD; and fastboot. No "android recovery" option.
As of now, I put it into Nvflash mode so that the screen will not keep shining with the red logo.
May anyone suggest how I could unbrick it, or the worst case, reinstall everthing to stock?
Thanks very much for your help!
204 and 205 don't work...
If you had read a few posts back on the thread you would know this.
203 however is great...just clear caches and flash...all will be fine.
ionSeven said:
204 and 205 don't work...
If you had read a few posts back on the thread you would know this.
203 however is great...just clear caches and flash...all will be fine.
Click to expand...
Click to collapse
I have known that already, didn't u notice?
I know 203 is great, too.
My problem now is I am stocked, and couldns't get into the recovery. Any suggestion to fix it?
I have tried some brick fixing method in the forum, but a strange thing is even though I can control and even flash files to my xoom, but if I typed "adb devices", it shows that the xoom is actually not connected. And thus, the work I have done didn't help at all.
Waiting for someone who is Almighty to help me!
Hi, I think you can try flashing the recovery again with the fastboot. Do the following:
Plug your Xoom to your PC
Open a cmd (if you're on Linux tell me)
Go to your fastboot folder with it
Download a recovery and rename it to recovery.img
Type:
Code:
fastboot flash recovery recovery.img
It may do the work, if it doesn't work, please quote this post and I'll tell you how to factory reset .
great fix, back working
XxLordxX said:
Hi, I think you can try flashing the recovery again with the fastboot. Do the following:
Plug your Xoom to your PC
Open a cmd (if you're on Linux tell me)
Go to your fastboot folder with it
Download a recovery and rename it to recovery.img
Type:
Code:
fastboot flash recovery recovery.img
It may do the work, if it doesn't work, please quote this post and I'll tell you how to factory reset .
Click to expand...
Click to collapse
I am a long time reader but this is my first time writing a comment.
the most recent update locked up my xoom but this brillient reply saved me, I flashed twrp and recovered to a older rom flash i still had in goo manager. Thank you very much.
diamondvsn said:
I am a long time reader but this is my first time writing a comment.
the most recent update locked up my xoom but this brillient reply saved me, I flashed twrp and recovered to a older rom flash i still had in goo manager. Thank you very much.[/QUOT
Congrats! U r so lucky.
As of me, I tried, no luck. I flash the recovery, the computer told me it's successful, and the tab showed the same. But when I reboot it, I still got only 3 options: nvflash,RSD and fastboot.
And I think one of the important point is, when I connected it in the fastboot mode, I type "adb devices", my devices didn't show up. However,I can still flash the recovery with fastboot commands. Strange.
Click to expand...
Click to collapse
XxLordxX said:
Hi, I think you can try flashing the recovery again with the fastboot. Do the following:
Plug your Xoom to your PC
Open a cmd (if you're on Linux tell me)
Go to your fastboot folder with it
Download a recovery and rename it to recovery.img
Type:
Code:
fastboot flash recovery recovery.img
It may do the work, if it doesn't work, please quote this post and I'll tell you how to factory reset .
Click to expand...
Click to collapse
Thanks so much for your help. I tried this. But still no luck. I have mentioned the situation in the above post. Pls give suggestions. Thanks.
tech.arthur said:
Thanks so much for your help. I tried this. But still no luck. I have mentioned the situation in the above post. Pls give suggestions. Thanks.
Click to expand...
Click to collapse
Okay, so your case seems worse than I expected... Somehow it seems your recovery partition for screwed . I will think a little, if I don't come off with anything I will send you a guide on how to restore to stock (unless you want it now I can send it). Gimme some time and I hope to find an answer for you
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
tech.arthur said:
Thanks so much for your help. I tried this. But still no luck. I have mentioned the situation in the above post. Pls give suggestions. Thanks.
Click to expand...
Click to collapse
So, I did a little research and it seems that NVFlash is a thing back from HC LOL! I dunno how you got there, but I'll help you getting out! Remember the following will completely wipe your device, if you want to take some more time I can see if I can find a way to get you out without wiping. So here we go:
Download the Stock ROM from here: http://forum.xda-developers.com/showpost.php?p=13178555&postcount=2
Extract it to a folder which cointains fastboot protocol
Boot your tablet in fastboot and plug it to your PC
Open a cmd and go to the fastboot folder
Type:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Hope this saves your device .
Dear friend,
I am so glad there is a person who cares so much to others.
I would like to wait for u, for a way that needn’t wipe everything. For there are some photos in the internal memory.
Or a way that I could back up everything first. Wait for your good news.
Thanks in advance!
QUOTE=XxLordxX;43575614]So, I did a little research and it seems that NVFlash is a thing back from HC LOL! I dunno how you got there, but I'll help you getting out! Remember the following will completely wipe your device, if you want to take some more time I can see if I can find a way to get you out without wiping. So here we go:
Download the Stock ROM from here: http://forum.xda-developers.com/showpost.php?p=13178555&postcount=2
Extract it to a folder which cointains fastboot protocol
Boot your tablet in fastboot and plug it to your PC
Open a cmd and go to the fastboot folder
Type:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Hope this saves your device .[/QUOTE]
tech.arthur said:
Dear friend,
I am so glad there is a person who cares so much to others.
I would like to wait for u, for a way that needn’t wipe everything. For there are some photos in the internal memory.
Or a way that I could back up everything first. Wait for your good news.
Thanks in advance!
XxLordxX said:
So, I did a little research and it seems that NVFlash is a thing back from HC LOL! I dunno how you got there, but I'll help you getting out! Remember the following will completely wipe your device, if you want to take some more time I can see if I can find a way to get you out without wiping. So here we go:
Download the Stock ROM from here: http://forum.xda-developers.com/showpost.php?p=13178555&postcount=2
Extract it to a folder which cointains fastboot protocol
Boot your tablet in fastboot and plug it to your PC
Open a cmd and go to the fastboot folder
Type:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Hope this saves your device .
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I don't think this wipes internal memory. Just application data.
ChillyChan said:
I don't think this wipes internal memory. Just application data.
Click to expand...
Click to collapse
Yes, it will wipe your internal data, when I first did the command I thought the same as you, resulted in a loss of 13-14GB of storage . So now you know and will never do this without warning . About the case now, can someone make me and the OP a favor?
Get the stable EOS 4 ROM, install it, go to adb shell and type:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/recovery of=/sdcard/recovery.img
Then upload those three files
So the OP will be able to fastboot flash the files and it will probably boot, as it's the same ROM he was using before, prolly it will require only a 'fastboot erase cache' command.
Hope you can help with it .
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
XxLordxX said:
Yes, it will wipe your internal data, when I first did the command I thought the same as you, resulted in a loss of 13-14GB of storage . So now you know and will never do this without warning . About the case now, can someone make me and the OP a favor?
Get the stable EOS 4 ROM, install it, go to adb shell and type:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/recovery of=/sdcard/recovery.img
Then upload those three files
So the OP will be able to fastboot flash the files and it will probably boot, as it's the same ROM he was using before, prolly it will require only a 'fastboot erase cache' command.
Hope you can help with it .
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
Click to expand...
Click to collapse
So let me see if I get it right:
The method u suggest now, is useable even I can only control the device in fastboot mode?
I need to boot it in fastboot mode, and then type the commands u posted.
Now, could I just download a 203 zip and unzip it to do so?
XxLordxX said:
Yes, it will wipe your internal data, when I first did the command I thought the same as you, resulted in a loss of 13-14GB of storage . So now you know and will never do this without warning . About the case now, can someone make me and the OP a favor?
Get the stable EOS 4 ROM, install it, go to adb shell and type:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/recovery of=/sdcard/recovery.img
Then upload those three files
So the OP will be able to fastboot flash the files and it will probably boot, as it's the same ROM he was using before, prolly it will require only a 'fastboot erase cache' command.
Hope you can help with it .
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
Click to expand...
Click to collapse
I learned it the hard way ha ha. Followed your directions and I was able to boot the tab (my brother's) to stock but all data is gone like you said. Too bad I didn't check the thread before that.
Now it's running EOS 203 with no problems. I'd help you upload the images but my upload speeds are terrible so if you/he can wait till tomorrow, I can upload it overnight.
Btw, can he just flash the stable EOS 203 zip using "fastboot flash zip"? I could do it on HTC One X so I'm just wondering if Xoom supports it too. The recovery is just CWM Touch from clockworkmod.com and the boot.img is in the ROM zip.
tech.arthur said:
So let me see if I get it right:
The method u suggest now, is useable even I can only control the device in fastboot mode?
I need to boot it in fastboot mode, and then type the commands u posted.
Now, could I just download a 203 zip and unzip it to do so?
Click to expand...
Click to collapse
ChillyChan said:
I learned it the hard way ha ha. Followed your directions and I was able to boot the tab (my brother's) to stock but all data is gone like you said. Too bad I didn't check the thread before that.
Now it's running EOS 203 with no problems. I'd help you upload the images but my upload speeds are terrible so if you/he can wait till tomorrow, I can upload it overnight.
Btw, can he just flash the stable EOS 203 zip using "fastboot flash zip"? I could do it on HTC One X so I'm just wondering if Xoom supports it too. The recovery is just CWM Touch from clockworkmod.com and the boot.img is in the ROM zip.
Click to expand...
Click to collapse
Hehe, the hard is way is the worse (but at least you never forget lol). About the update.zip, what happens is the following:
When you do an update.zip file, you write something like a "install script", which the recovery reads and apply, that's what the update.zip does while the fastboot simply flashes the partition itself. That's the difference, what I think you used on your HTC One X is adb sideload, which I used some times already, which basically sends the zip to a tmp folder and install it. The thing is, fastboot is very different from adb, so you can't simply do it. On new devices (with unlockable bootloaders) the fastboot has already some new cool features, I tried to use on my Xoom to see of worked, but no luck, the command was "fastboot boot recovery.img" which could prolly work on OP case, however Xoom's bootloader is old and doesn't support this command. I don't mind waiting and am very grateful for your help . Hope we cab fix Arthur's tablet soon !
~Lord
PS.: regarding your other question @tech.arthur, that command should be used by someone with a Xoom booting, so we can get the EOS4 system.img and boot.img, this way you can boot your tablet after flashing the new imgs with fastboot .
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
XxLordxX said:
Hehe, the hard is way is the worse (but at least you never forget lol). About the update.zip, what happens is the following:
When you do an update.zip file, you write something like a "install script", which the recovery reads and apply, that's what the update.zip does while the fastboot simply flashes the partition itself. That's the difference, what I think you used on your HTC One X is adb sideload, which I used some times already, which basically sends the zip to a tmp folder and install it. The thing is, fastboot is very different from adb, so you can't simply do it. On new devices (with unlockable bootloaders) the fastboot has already some new cool features, I tried to use on my Xoom to see of worked, but no luck, the command was "fastboot boot recovery.img" which could prolly work on OP case, however Xoom's bootloader is old and doesn't support this command. I don't mind waiting and am very grateful for your help . Hope we cab fix Arthur's tablet soon !
~Lord
PS.: regarding your other question @tech.arthur, that command should be used by someone with a Xoom booting, so we can get the EOS4 system.img and boot.img, this way you can boot your tablet after flashing the new imgs with fastboot .
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
Click to expand...
Click to collapse
So, I can't download the 203 nightilies .zip to unzip it to use those .img files?
I have to wait for the uploads, right?
A bit confuse to me. Sorry.
tech.arthur said:
So, I can't download the 203 nightilies .zip to unzip it to use those .img files?
I have to wait for the uploads, right?
A bit confuse to me. Sorry.
Click to expand...
Click to collapse
Unfortunately yes you'll have to wait, the zip has no imgs.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
Oh, I re-read everything, I understand now.
So dear friend ChillyChan, I will wait for your upload, and I am pretty sure you will get a lot of thanks Cox I believe a lot of noobs like me out there is stucked too! Haha!
XxLordxX said:
Unfortunately yes you'll have to wait, the zip has no imgs.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
Click to expand...
Click to collapse
Yes, I will wait patiently.
You guys are awesome! Thanks thanks thanks!
XxLordxX said:
Unfortunately yes you'll have to wait, the zip has no imgs.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
Click to expand...
Click to collapse
Wanna clarify: if I leung wait for the.img files, I wouldn't need to wipe my tab to save it, right?
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?