I have recently been interested in wanting to install a ubuntu onto my tablet, so i am installing twrp first, i have downloaded the android SDK files and have extracted them with adb and fastboot into my c: drive, i have also unlocked my device by using the Asus unlock tool, i then when into the i believe its called bootmenu where you can choose between usb,rck,coldboot,ect and downloaded the fastboot driver into my usb 3.0 after that i flashed twrp using "fastboot -i 0x0b05 flash recovery twrp.blob" in cmd everything went well the blue bar loaded, the cmd said it finished.
Now this is where the problem starts when i enter RCK (recovery mode) it just freezes there like the fastboot, the icon stops flashing and text appears saying "booting recovery image kernel" but nothing happens. To my knowledge and the guide i am following it should boot to twrp if im not mistaken.
I am using windows 7 for my pc and have updated my tablet to 4.1.1, i have also check the Md5 codes. I am also following this guide (http://forum.xda-developers.com/show....php?t=2038464).
If anyone could help out someone trying to get into roms for andriod that would be awesome thank you.
Related
I cannot get fastboot to find my TF201. I ran the unlock tool tonight on my stock .21 prime. I have booted into fastboot usb download mode with the Power + Vol Down, wait for RCK to pass, then Vol Down to select fastboot then Vol Up to confirm.
I have tried under my native Ubuntu 11.10 x64 install and Windows 7 x64. Under windows, I removed my already installed SGS2 drives and replaced them with the Naked 0.61 Drivers as found here: [ADB/FB/APX Driver] Universal Naked Driver Beta 0.6.1. I rebooted Windows and tried again to no luck:
Code:
./fastboot devices
or
Code:
fastboot.exe devices
as per respective OS.
Each command just echos an empty line, any tips?
EDIT:
I just went for it anyway and it apparently flashed the recovery
Code:
fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img
but now I am sitting with a completed blue progress bar and am scared to reboot the device.
EDIT 2:
I took a leap and power cycled the device, looks like recovery is in and good to go. Looks like since we need to specify the vendor_id for our devices, the devices command, or anything else for that matter fails to work properly (fastboot reboot, fastboot devices, etc.).
Hope this will help anyone else having issues.
Thanks.
SOLVED fastboot does not find device
Would like to expand your answer!
i am working with asus transformer prime TF201
i had a problem (SOLVED) where fastboot would not find device.
Code:
<waiting for device>
i fixed it by specifying asus vendor id (in this instance i was flashing a new recovery)
Code:
./fastboot -i 0x0b05 flash recovery recovery.img
Hope this helps it took me 2 days to figure that out
PEACE!
Thanks!
I ran into the same issue where the TF201 was not shown as a device.
You saved me from hours of pain!
how ot change vendor id
I'm having the same problem; need to install twrp via fastboot, but windows does not recognize the device. I have 'waiting for device'.
Can anyone explain how to change/specify the vendor id?
EDIT: nevermind, the 0x0b05 is the vendor ID, I already did that but the problem remained. In the end I switched computers and this solved it.
I'm having a somewhat similar problem except I connect my Prime and I see a serial, but it's not the serial of my Prime. I run the command:
fastboot -i 0x050b flash recovery flatline_tf201.img
and I get the message that it copied successfully, but I don't see any blue progress line and when I boot into recovery, I get the triangle; presumably because there is no recovery image.
I've tried it from three different windows systems (2 64bit and 1 32bit) with the same results. I am also unable to connect via ADB.
Any suggestions?
My phone is HTC Desire. Using to enter fastboot to install 4EXT recovery but failed
I can use adb command form cmd.
E:\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT0ARPL02347 device
But When I restart my phone and enter to FASTBOOT is shows FASTBOOT USB in the screen but nothing happen when I issue command "fastboot devices"
E:\sdk\platform-tools>fastboot devices
E:\sdk\platform-tools>
Hello Everyone, this is one of my first posts so go easy on me.
I used the method in this thread to flash JB onto my TF201, and now i cannot boot to recovery (get the android on his back/side with the red exclamation) and fastboot shows up as a device in device manager in windows, but when i run the "fastboot devices" command with the up to date SDK nothing is listed. ADB works, but for osme reason superuser was installed as a system process and will not uninstall, and will not issue any sort of root command to anything, including ADB. any ideas?
hi
i have a issue similar to this thread http://forum.xda-developers.com/forumdisplay.php?f=1465, but just want to confirm
i have a CWM and CM10.1 installed previously but no nvflash,
but during a recently flash i accidently formatted the "system" partition.
I now can no longer boot past the asus logo unfortunately,
and tried the following
1) i can boot into CWM but it only allow flashing from /mnt/sdcard and i dont have any rom in /mnt/sdcard (wiped)
2) i can boot into fastboot (PWR+DWN) and i installed the naked driver v0.72 and it show in device manager -- however "fastboot.exe devices" show nothing
3) if i normal boot (ie stuck on "Eee Pad logo) and install some form of "ADB interface" driver, then i can "adb.exe devices" into it -- but i can push anything onto /mnt/sdard (permission denied)
4) "adb shell" wont work bc of missing "system/bin/sh" hence i cant re-root
5) i can go into APX mode (PWR+UP), but it is not nvflashed sadly
6) i have tried 2 usb cables already, so hopefully not it
Is there anything i can do ... or it is bricked and have to send back to asus for service ?
thanks in advance !
jojo665 said:
hi
i have a issue similar to this thread http://forum.xda-developers.com/forumdisplay.php?f=1465, but just want to confirm
i have a CWM and CM10.1 installed previously but no nvflash,
but during a recently flash i accidently formatted the "system" partition.
I now can no longer boot past the asus logo unfortunately,
and tried the following
1) i can boot into CWM but it only allow flashing from /mnt/sdcard and i dont have any rom in /mnt/sdcard (wiped)
2) i can boot into fastboot (PWR+DWN) and i installed the naked driver v0.72 and it show in device manager -- however "fastboot.exe devices" show nothing
3) if i normal boot (ie stuck on "Eee Pad logo) and install some form of "ADB interface" driver, then i can "adb.exe devices" into it -- but i can push anything onto /mnt/sdard (permission denied)
4) "adb shell" wont work bc of missing "system/bin/sh" hence i cant re-root
5) i can go into APX mode (PWR+UP), but it is not nvflashed sadly
6) i have tried 2 usb cables already, so hopefully not it
Is there anything i can do ... or it is bricked and have to send back to asus for service ?
thanks in advance !
Click to expand...
Click to collapse
First of all try adb push Name_of_Rom.zip /sdcard/
If that does not work try adb push Name_of_Rom.zip /system/media/
If that still does not work then download the correct TWRP blob file from the following link for your bootloader. http://www.teamw.in/project/twrp2/93
The fact that you are on CWM and was using CM 10 makes me believe that you are still on the ICS bootloader but to make 100 percent sure when you first power on the device look at where the "NVIDIA" logo is. If it is bottom center it is ICS, if it is bottom right it is Jellybean. (MAKE SURE YOU GET THE CORRECT TWRP VERSION FOR YOUR BOOTLOADER)
Now rename the blob file you downloaded to twrp.blob. Go into fastboot and type the following.
fastboot -i 0x0b05 flash recovery twrp.blob
This should install TWRP which will allow you to install a rom off an external micro sd.
turn out it is windows problem -- fastboot device driver (Naked 7.1) is installed but wont connect to the tablet. I ended up installing Ubuntu in order to get fastboot to work.
Once fastboot is working, i able to follow above advice and get my tablet back to functional state.... thanks!
ps: now time for nvflash :laugh:
jojo665 said:
turn out it is windows problem -- fastboot device driver (Naked 7.1) is installed but wont connect to the tablet. I ended up installing Ubuntu in order to get fastboot to work.
Once fastboot is working, i able to follow above advice and get my tablet back to functional state.... thanks!
ps: now time for nvflash :laugh:
Click to expand...
Click to collapse
What exactly did you do? I'm trying to extinguish all avenues before I have to RMA my tablet. Thanks for the help!
Hello guys,
i have a bricked rooted oneplus x
I had issues with the rooted rom so i flashed the newest stock rom via twrp
The phone boots up and showed the usual otimizing apps message. After the proccess is done it just the usual "let me helpt set up your phone page" and then restarts
I cant acces twrp anymore and when i try to acces the stock recovery it just shows a oneplus logo
I do have access to fastboot though (i hope that leaves some hope)
I have tried the MegaUnbrickGuide here in the forum but i wasn't able to install the drivers i need for that method
One more thing whenever i try
Code:
fastboot boot recovery.img
i get the "remote dtb not found" message
Does that have to do with developer options not being unlocked?
Any ideas on how to just get some form of working os installed on the device
(i dont care wheter rooted or not at this point have been trying stuff for hours now)
regards
Jan
First download Minimal ADB and Fastboot and install it.
Go into fastboot mode.
1. Re-unlock your bootloader using the command - fastboot oem unlock
2. After doing that, download the latest version of TWRP(which at the time of writing this is 3.1.0) and rename it to 'recovery.img'
3. Open a command window in the place you have downloaded the recovery by pressing the shift key and right clicking and then choosing the option Open Command WIndow Here... Flash the recovery using the command fastboot flash recovery recovery.img
4. Boot into it using the command fastboot boot recovery.img
5. If it still gives 'remote dtb not found' then follow this guide: https://forum.xda-developers.com/oneplus-x/help/opx-remote-dtb-solution-t3480274
6. If it boots into recovery, your phone is now fine and go ahead and flash whatever ROM you want.
Cheers!
Hi
I have a Redmi note 10, i unlocked the bootloader and tried to install the custom recovery Orange fox, i posted this question on the main Orange fox trhead but as i read its no longer being mantained, so i made a separate thread.
what i did is follow a tutorial in which i was instructed to dowload bot the Adb exe, and using the commands to flash the recovery img.
what i did step by step is the following:
1. Unlock bootloader
2. Start fast boot and connect my device to my PC using the original usb cable
3. Download Platform tools and Orange fox recovery
4. Copy the recovery image into the Platform tools folder
5. Type CMD to start the commands screen
6. Used the "fastboot devices" command to find my connected device
7. my device is a A/B type of device, so i typed the following command "fastboot flash boot_b recovery.img"
8. then i typed the command "fastboot reboot recovery"
up until this point it was working, then i was supposed to add the zip file into my phone so i could install it using orange fox
9. i typed "adb push "orange fox file location"/sdcard" and got the following string as an answer: adb.exe: push requires <source> and <destination> arguments
no matter how i tried to string the command i always got back this answer so i tried to manually move the zip file into the Fox folder and it allowed me to install it.
the problem is that im now stuck on recovery mode, cant leave that screen, cant even turn off my phone, i tried rebooting to fastboot, to recovery again, to system and it will always end on the recovery screen, attempted doing a factory reset but im still stuck on the recovery loop, i attempted to flash an stock rom but i was unable to do it, did i brick my phone? is there some way to solve it? would flashing a different custom recovery solve my issue?
Please any help would be appreciated.
if its of any help my device is a redmi note 10, MIUI was 12.5.5.0, global mojito, i ussed the latest version of orange fox when i attempted this