I solved my issue, you can close this thread
rooting xoom wifi 3.2
please i need your help.
im stuck at "fastboot flash boot rootboot.img"
after unlocking, im supposed to put that code into cmd but it gives error: cannot load 'rootboot.img'.
you look like u successfully rooted yors, please help. i've been trying for hours with no luck. please tell me what i'm missing...thanks in advance.
dirtysexyrodney said:
please i need your help.
im stuck at "fastboot flash boot rootboot.img"
after unlocking, im supposed to put that code into cmd but it gives error: cannot load 'rootboot.img'.
you look like u successfully rooted yors, please help. i've been trying for hours with no luck. please tell me what i'm missing...thanks in advance.
Click to expand...
Click to collapse
Do you have the rootboot.img file in the same directory as you are running the adb commands?
Typically this is C:\android-sdk-windows\platform-tools
Related
myxoom wont boot and it stuck at the boot logo! help pls!
Walk back into the store, walk up to customer service and say "It won't turn on"
That's about your only solution when someone loads a 3g kernel.
You might be able to try to Power Off, power on Press and hole Volume up and power when you see the moto logo.
i tried but failed! sad thing is i m staying malaysia n i ordered it via online!!!
pls! help me!
pls! i m gonna cry
Can you get into fastboot? You might want to try reflashing your boot and system partitions. I believe it was BeagleBoy that grabbed them off of a stock Xoom Wi-Fi. You're already unlocked I imagine. Should let you flash those right back in and start fresh.
This guy got out of a semi-brick by doing something similar.
http://forum.xda-developers.com/showthread.php?t=973355
Scourge1024 said:
Can you get into fastboot? You might want to try reflashing your boot and system partitions. I believe it was BeagleBoy that grabbed them off of a stock Xoom Wi-Fi. You're already unlocked I imagine. Should let you flash those right back in and start fresh.
Click to expand...
Click to collapse
If you can get into fastboot, you should be fine. Don't panic just yet.
Try reflashing the stock boot.img and system.img files through fastboot. I did it a few days ago http://forum.xda-developers.com/showpost.php?p=12832155&postcount=33
You can find boot.img and system.img for stock wifi xoom on the OP of that thread.
Failing that try the semi bricked solution.
I hope you solve your problem.
how do i enter fastboot?
sad is, now my machine stucks in boot screen (moto logo) .. n my com have no respond with it at all. any suggestion pls
omnia1994 said:
how do i enter fastboot?
sad is, now my machine stucks in boot screen (moto logo) .. n my com have no respond with it at all. any suggestion pls
Click to expand...
Click to collapse
Power off the device.
Then hold Volume Down and hold Power on at the same time.
it shows "Starting Fastboot protocol support" and stopped there. what this mean? =(
that means you should be able to get it running again.
follow the first message in this thread:
http://forum.xda-developers.com/showthread.php?t=1010568
probably from the stuck at 'dual core technology' bit...
but I think this is what you should follow:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push vold.fstab /system/etc/vold.fstab
adb reboot
you might also want to pick up the stock wifi images:
http://forum.xda-developers.com/showthread.php?t=1017398
and flash them using:
fastboot flash system system.img
fastboot flash recovery recovery.img
(you've already flashed boot.img above).
omnia1994 said:
it shows "Starting Fastboot protocol support" and stopped there. what this mean? =(
Click to expand...
Click to collapse
If you're lucky, your computer will connect and typing in "fastboot devices" will show an entry for your Xoom. You do not need to start with ADB if you're already in fastboot mode.
From there, flash the boot.img for the proper Xoom version you have. You may also want to flash the system.img as well.
From there, simply try to reboot using "fastboot reboot". Make sure your Xoom starts up. If it does, you're pretty much good to go. I'd root from there manually.
omnia1994 said:
it shows "Starting Fastboot protocol support" and stopped there. what this mean? =(
Click to expand...
Click to collapse
That means you are in fastboot.
You can now try to follow this http:// http://forum.xda-developers.com/showthread.php?t=1010568 skipping the unlock section. Or as scourge recommended, fastboot flash the stock .img files. You can find them here http://forum.xda-developers.com/showthread.php?t=1017398 and the instructions around post #26 in that thread.
but my com cant sense my device =(
n it stucks at boot screen with the words "Starting fastboot protocol support" but just stuck there, this works?
qubit76 said:
That means you are in fastboot.
You can now try to follow this http:// http://forum.xda-developers.com/showthread.php?t=1010568 skipping the unlock section. Or as scourge recommended, fastboot flash the stock .img files. You can find them here http://forum.xda-developers.com/showthread.php?t=1017398 and the instructions around post #26 in that thread.
Click to expand...
Click to collapse
That's not necessarily true. My PC can no longer detect my Xoom in any way whether or not it says "Starting Fastboot protocol support" or "Starting RSD mode 2". I can't get it to say anything else.
I used to be able to get into fastboot. That's how I bricked my Xoom... By trying to oem lock it with what I was hoping to be clean boot, system and recovery image files for the wifi.
Now, I can't even get back in to oem unlock or flash. RSD lite doesn't pick it up in RSD mode 2, but does pick up my old RAZR phone.
omnia1994 said:
but my com cant sense my device =(
n it stucks at boot screen with the words "Starting fastboot protocol support" but just stuck there, this works?
Click to expand...
Click to collapse
What sort of computer do you have? Can you copy and paste what you see when you type "fastboot devices"?
Copy and paste from your command prompt (or Linux terminal) and let's see what you've got.
ok. will report once tried. thx very much =)
Okay. If you can get into fastboot (check by "fastboot devices"), all you should need to do are these two commands if you're connected:
Code:
fastboot flash boot boot.img
fastboot flash boot system.img
fastboot reboot
That should get you close to stock first.
wth, i cant install the android SDK, it said it needs java to be installed. i ve installed that but still cant install the android sdk. =(
omnia1994 said:
wth, i cant install the android SDK, it said it needs java to be installed. i ve installed that but still cant install the android sdk. =(
Click to expand...
Click to collapse
Where error messages are you getting? Are you running 64bit?
HOX+
4.2.2 sense 5
Unlocked with HTCdev
I have followed ALL the steps from 'Lucky Thirteen', http://forum.xda-developers.com/showthread.php?t=2213910, but can`t get TWRP to install.
Everything goes fine until I use ``fastboot flash recovery TWRPrecovery.img`` command.
The laptop finds the phone because I`ve got ``fastboot usb`` showing on phone screen.
When I type the above fastboot command the message I get is ``error: cannot load ``TWRPrecovery.img`` : unknown error
I`ve spent hours on here trying to find solution... I´ve tried running command in the ``platform tools`` folder where the file is, tried downloading the TWRP file again, tried renaming without .img as suggested, EVERY suggestion I can find. Still won`t install.
Please help, phone still works OK, just can`t get a recovery installed.
Thanks
10rdan said:
HOX+
4.2.2 sense 5
Unlocked with HTCdev
I have followed ALL the steps from 'Lucky Thirteen', http://forum.xda-developers.com/showthread.php?t=2213910, but can`t get TWRP to install.
Everything goes fine until I use ``fastboot flash recovery TWRPrecovery.img`` command.
The laptop finds the phone because I`ve got ``fastboot usb`` showing on phone screen.
When I type the above fastboot command the message I get is ``error: cannot load ``TWRPrecovery.img`` : unknown error
I`ve spent hours on here trying to find solution... I´ve tried running command in the ``platform tools`` folder where the file is, tried downloading the TWRP file again, tried renaming without .img as suggested, EVERY suggestion I can find. Still won`t install.
Please help, phone still works OK, just can`t get a recovery installed.
Thanks
Click to expand...
Click to collapse
Further to my OP I`ve since been able to install TWRP through Hasoon2000`s ``all in one tool```.
Could the problem be something to do with ´´fastboot commands`` ?
If so, am I likely to have problems when I try to flash a boot.img with commands ?
Thanks
I was rooting my shield with the thread of shimp208 and when i flash insecure boot img and put the command "adb shell" the console was closed
im stuck on nvidia logo and it was there 10 hours and nothing happens
i was thinking if I let the battery runs out and turn on in fastboot i can acces to recovery and install the original rom
please somebody give me an answer or the original rom
I know this thread is in incorrect section but i cant post on shield development section
Please help me
Only one step
Yes! I entered in fastboot mode!
i only need to flash the original boot.img or the stock rom with recovery
Please can someone give me that? Please, I will be very grateful
Thanks
I am trying to flash the 5.0 official image to my N5 and it is now stuck on "waiting for device". See attached image.
I was able to see my device in adb, i booted to fastboot mode and adb fastboot listed my device. It sent/wrote the bootloader to the phone, but now is just waiting.
Can i safely kill the flash process and start again? I am a little worried that it is just stuck.
reynolds10g said:
I am trying to flash the 5.0 official image to my N5 and it is now stuck on "waiting for device". See attached image.
I was able to see my device in adb, i booted to fastboot mode and adb fastboot listed my device. It sent/wrote the bootloader to the phone, but now is just waiting.
Can i safely kill the flash process and start again? I am a little worried that it is just stuck.
Click to expand...
Click to collapse
im not going to answer, but you should read threads in other n5 xda sections(general. hint hint..)
simms22 said:
im not going to answer, but you should read threads in other n5 xda sections(general. hint hint..)
Click to expand...
Click to collapse
That's right ya'll wanna flash but don't wanna read :silly:
Thanks guys. Much appreciated.
Hello everyone. I am trying to root and flash my TF300T for the first time, and I am running into some problems.
I downloaded the unlocking tool from asus and that seemingly worked fine.
Now however when I try to boot into recovery mode, the android just falls down and gives me an error message. I am able to boot into the standard android mode without an issue. I tried to root with kingo which seemed to work as I can access the SuperSM.
I downloaded Minimal ADB and Fastboot to try and flash a ROM but I cant see the device in flashboot but I can in adb. (Saw on a different thread that I need to be in recovery mode to see this?)
I downloaded the naked universal drivers and put on everything that said asus but that didnt help at all.
My main goal is to get lollipop on my tablet but I cant seem to make any headway. Can someone help point me in the right direction on what I am doing wrong or what I should do next? Any help would be appreciated. Thanks.
Terry_Tsang said:
Hello everyone. I am trying to root and flash my TF300T for the first time, and I am running into some problems.
I downloaded the unlocking tool from asus and that seemingly worked fine.
Now however when I try to boot into recovery mode, the android just falls down and gives me an error message. I am able to boot into the standard android mode without an issue. I tried to root with kingo which seemed to work as I can access the SuperSM.
I downloaded Minimal ADB and Fastboot to try and flash a ROM but I cant see the device in flashboot but I can in adb. (Saw on a different thread that I need to be in recovery mode to see this?)
I downloaded the naked universal drivers and put on everything that said asus but that didnt help at all.
My main goal is to get lollipop on my tablet but I cant seem to make any headway. Can someone help point me in the right direction on what I am doing wrong or what I should do next? Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Ok I was dumb and figured out the first half of my problem. I thought it had to boot into recovery mode to get the fast loader to work. Anyways now it lists my device when I type fastload device but when I try to flash twrp it gives me an error saying
Sending 'Recovery" <6800 KB> ...
Failed (command write failed(No such device or address))
Can someone please help? thanks
I guess you forgot "-i 0x0b05" in the command
it should look like this:
fastboot -i 0x0b05 flash recovery twrp.blob
if fastboot devices detects tablet then this should work.
AFAIK Asus is the only one brand that needs "-i [hex_ID]" even when it is the only fastboot device detected by "fastboot devices" command
Sent from my TF300T using XDA Free mobile app
th3cr0w said:
I guess you forgot "-i 0x0b05" in the command
it should look like this:
fastboot -i 0x0b05 flash recovery twrp.blob
if fastboot devices detects tablet then this should work.
AFAIK Asus is the only one brand that needs "-i [hex_ID]" even when it is the only fastboot device detected by "fastboot devices" command
Sent from my TF300T using XDA Free mobile app
Click to expand...
Click to collapse
That id string is a vendor code and all android vendors have one ....
It is not need to flash from fastboot, it is only for safety that you need to use the vendor id ....
Thx Josh
I remembered reading about that while performing nvflash backup - https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
and then I remembered it didn't work for me without that vendor ID specified manually,
later on I rooted my cousin's Sony phone and that one did fastboot without -i option, so I concluded it must be asus specific "issue" - not to detect ID automatically or sth ....
Anyway @Terry_Tsang - If you have not tried like that, it is always worth a shot ;]
I have tried it with and without the -i tag and get the same error. I have a feeling my recovery file is corrupt as I get an error when I try to boot into that mode. I also now have a new error instead of unable to write, it says invalid argument.
Since I was able to root it with kingo, I tried the TWRP app but it also crashes when I try to do an install of TWRP through the app. I have no idea how to proceed.
I have tried, rooting with kingo and the commands. I have tried unrooting it. I have tried rooting then using ROM Manager and TWRP apps. I have no idea how to continue. I definately think something is wrong tho lol.
th3cr0w said:
I remembered reading about that while performing nvflash backup - https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
and then I remembered it didn't work for me without that vendor ID specified manually,
later on I rooted my cousin's Sony phone and that one did fastboot without -i option, so I concluded it must be asus specific "issue" - not to detect ID automatically or sth ....
Anyway @Terry_Tsang - If you have not tried like that, it is always worth a shot ;]
Click to expand...
Click to collapse
Well its all good not a point of being right a point in giving good info ...
Here are the most use vendor codes not just an Asus thing ?
https://gist.github.com/lj50036/3b30ecc420b5838646be
Thx Josh
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
Terry_Tsang said:
Hello everyone. I am trying to root and flash my TF300T for the first time, and I am running into some problems.
I downloaded the unlocking tool from asus and that seemingly worked fine.
Now however when I try to boot into recovery mode, the android just falls down and gives me an error message. I am able to boot into the standard android mode without an issue. I tried to root with kingo which seemed to work as I can access the SuperSM.
I downloaded Minimal ADB and Fastboot to try and flash a ROM but I cant see the device in flashboot but I can in adb. (Saw on a different thread that I need to be in recovery mode to see this?)
I downloaded the naked universal drivers and put on everything that said asus but that didnt help at all.
My main goal is to get lollipop on my tablet but I cant seem to make any headway. Can someone help point me in the right direction on what I am doing wrong or what I should do next? Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
You do not have to root to flash a recovery anyway ...
If you would like to look into this more shoot me an email at [email protected]
Thx Josh
Terry_Tsang said:
I have a feeling my recovery file is corrupt as I get an error when I try to boot into that mode. I also now have a new error instead of unable to write, it says invalid argument.
Click to expand...
Click to collapse
You did check the checksum of your download right?