Hi,
I rooted my mojo and then i installed twrp, then i installed cyanogenmod 12 and i tryed to reboot but when i pressed reboot TWRP asked "Your device isnt rooted want to root? but i presed no accidentaly (one of the worst mistakes of my life) and it stucked on bootloop and i tryed to reboot it on recovery mode to fix it using fastboot but it stucks on rebooting... (on the screen of terminal on my laptop) and i waited for a long long time, but nothing happened.
Please help!
Did you use towelroot, or the USB-USB cable?
If towelroot, then you may not be able to recover the device without using a USB-USB cable. The fastboot prevents the MOJO from being bricked, because you can always re-flash it using the USB-USB method, even if the OS installed isn't working.
If you have a USB-USB cable, you need to use that to boot from TWRP again (or re-flash it to the fastboot if it won't work) and then re-wipe the MOJO and re-install CM12 + the Gapps, then re-boot the system as per the instructions. If you have any questions regarding clarification of the procedure, feel free to ask.
I used towelroot to root it and i tried fastboot to reboot it but on windows 10 don't detect it and on mac os X el capitan stucks on rebooting.....
The Windows driver should be in the same folder as fastboot. I was using Windows 7 and it didn't detect either, but the driver makes it detect correctly.
http://i.imgur.com/8O5FDgB.jpg
Windows 10 cant, but i will try with an windows 7 old (not so old) laptop
https://drive.google.com/file/d/0B3gWeKqMPK8HcjE2ZC1hOU0yUDA/view?usp=sharing
hi again, i tried with the windows 7 laptop but now fastboot dont detect it,i installed the drivers succesfully but fastboot dont detects it
https://drive.google.com/file/d/0B3gWeKqMPK8HajBUNlMyZEcxV1k/view?usp=sharing
SOLVED: the reason it didnt detected it its because on windows you needed to turn on testdriversigning and install the .inf file included on the MoDaCo mod zip on the windows.drivers and after that you needed to write "fastboot -i 0x0738 <command> , "0x0738" is the mojo´s usb vendor so it sended the commands directly to the mojo.
The problem was that the data and system partitions were corrupted so i reformated them with "fastboot -i 0x0738 erase system -w", the -w is for erase userdata. After that i booted the twrp recovery by "fastboot -i 0x738 boot <recovery.img path>" and from twrp i reinstalled android and it worked!
Related
I rooted my Nexus 7 months ago, but today I decide I wanted to try a new ROM and was wiping by data and system partitions for a fresh install of CM10, and I accidentally chose format all data. So my device is wiped except for TWRP.
Im in TWRP and when I run "adb devices" from my pc I get the following...015d2994a62bf403 sideload
but when I tried to use adb sideload, but i get the error "failed to write data 'protocol fault <no status>'
I'm screwed here...
You are not screwed, you still have a working bootloader (which I presume to be unlocked).
If the recovery keeps coming up in sideload mode after re-starting it, try soft-booting a recovery instead of booting it off the (previously flashed) recovery stored on the device
(with fastboot/bootloader showing on the N7)
Code:
fastboot boot recovery-image-file.img
This will certainly let you use a newer recovery as well if you want.
If that works and your drivers are correctly set up, you can push a file
(with soft-booted recovery running)
Code:
adb push My-Favorite-ROM.zip /sdcard/My-Favorite-ROM.zip
and then if that completes successfully, flash that ROM.
good luck
Edit : the problem is the usb cable itself.. Tried with HTC USB cable and its working flawlessly..!! Though it (original asus USB cable ) still works good for both charging, data sync and file transfers but not working for adb and fastboot..
Previously installed stock factory image (KTU84P) using fastboot (in boot loader)
then flashed twrp 2.7.1.1
rooted
rebooted and everything working fine.
to install a ROM through adb sideload
i formatted all partitions in recovery
started adb sideload but its in terminal adb is not detecting my device..
So i rebooted to boot loader (fastboot mode) to flash factory image but here fastboot not detecting my Nexus 7
is the problem with my nexus 7 or linux..??
i tried using windows but with no luck..
NOW My Nexus 7 doesnt have operating system dont know how to install one without using fastboot and adb sideload..
Did you try to use fastboot in Root privilege, I mean sudo in Linux?
Hello All
I've rooted and installed TWRP recovery. And accidently wiped all partitions (system, data, caches...). Currently no OS installed.
Tried installing Cyanogen mods and also default ROMs via TWRP but getting error saying
====
Unknown command "screenshot"
E: Unable to mount /spare
====
Also tried flashing default ROMs...same error . No luck.
Tried wiping all partitions again.
connected to my linux lap
Device is connected and listed while running command "lsusb". (USB data connection working)
But not detecting under adb devices also not shown under fastboot mode. (So no luck to flash via PC).
All forums saying "check usb debugging" to show under adb devices. How can I ..if there is no ROM
Also TWRP is restarting after some time.
-------------------*******helppp******************************
Hi,
I have the same problem, few post below.
During my searching I found this post, but I get error during
fastboot erase spare
It hard to say what wrong is with this partition.
Maybe you will be have more luck
Elokwentnyemu said:
Hi,
I have the same problem, few post below.
During my searching I found this post, but I get error during
fastboot erase spare
It hard to say what wrong is with this partition.
Maybe you will be have more luck
Click to expand...
Click to collapse
In my case, the phone is not listed under fastboot devices But it's connected to computer in fastboot mode and we can see the device is listed when command lsusb is executed.
antoponline said:
In my case, the phone is not listed under fastboot devices But it's connected to computer in fastboot mode and we can see the device is listed when command lsusb is executed.
Click to expand...
Click to collapse
I checked on Manjaro and my phone is present under fastboot. Try reinstall drivers or use other PC to connect by fastboot.
so sad for both of you guys i've already encountered this before try this any of these.
- use adb sideload via TWRP using stock firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip
- if you have a back up restore it, then boot to fastboot and flash the fastboot, boot and recovery of this firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip then boot to recovery and side again using this firmware.
- try this link if it's work http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
sorry guys i forgot how i managed to solve this i will update this thread. just always remember use always this firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip and back your current rom even if it's stock or custom this is most important. if you can access bootloader just do the flashing fastboot, boot and recovery this would be easy if you can access bootloader.
Hi
I would like to ask for some advice.
I've recently soft bricked my MI2S. I can boot to recovery (TWRP 2.8.1) and fastboot. The phone isn't recognised by Windows or Ubuntu, so I can't flash anything with fastboot. Actually, fastboot, adb or MiFlash don't detect the phone. I've tried to use a USB stick with an OTG cable, but TWRP doesn't detect the USB stick. If I boot to system, it stays on the MI logo (I can wait a full night, it won't change).
My question is, do I have a problem with my USB port? I'm equipped to solder a new one, if necessary. Or is my connection problem due to another reason? I wouldn't want to go through soldering if it is for nothing. Especially, when I started to mess up with the phone, it was locked with a different MI account (it was my wife's account, but it took me a few days to connect the dots together), and I couldn't connect with MiFlash, adb or fastboot either.
The steps I did to get it soft bricked:
Flashed TWRP 2.8.1 with fastboot
Rebooted to recovery
Rebooted to MIUI (a few times)
Attempted to flash TWRP 3.5.0 (my memory fails a bit there, I think I did it via fastboot)
The last didn't work because I'm still on TWRP 2.8.1
And I can't add any more zip file to flash via recovery, nor can I use adb sideload or flash with fastboot.
Any advice or comments are more than welcome. You may just have an idea that I didn't think of.
Regards
Matt
Quick update:
I don't know if you would agree, but I can't see my issue to be a software one (the device not being recognised)
I've ordered a USB port directly from China and I'll see if I can unbrick the phone from that point.
It's great that you can still access to recovery and fastboot.
First, I advice you to back up your data.
If you cannot use adb sideload or flash with fastboot.
Try in fastboot mode
- fastboot erase cache;
- fastboot erase system;
- fastboot erase userdata.
See if that can solve your issue.
I'm trying to flash Magisk custom boot.img using fastboot but it will never detect the device, tried everything in the first page of Google with different searches, nothing works. Tried downloading Samsung developer drivers from here, tried this tool while in fastboot and then while the device is booted normally, tried this 15 second ADB installer tool to install Google adb and fastboot drivers, tried Kies, tried uninstalling all the relevant devices and using the Windows default ones, tried another laptop, another USB cable, another USB port, many videos and articles but still nothing. When I run fastboot devices, it doesn't show me anything, adb devices works just fine and shows the device when booted normally, of course I run fastboot devices when I'm in fastload but nothing shows up.
My device is SM-N910C treltexx EGY EXynos5433, tried all this mainly on Windows 11 but also tried with the Samsung developer drivers on a Windows 10 device.
I have WSA installed with hyper-V and Virtual Machine Platform installed on 11, could this be a problem? Also I noticed that when I run adb reboot fastboot, the device just restarts, the same when I choose Run fastboot in recovery mode, the only way for me to get to fastboot is pressing power +home +volume down. Also Odin recognizes the device in fastboot just fine.
So how to solve this? Or is there a method to flash Magisk's boot.img without fastboot? Or an alternative that does its job?
With further research I managed to do it with Odin. Took the patched file and renamed it to boot.img, used 7z to make a tar archive out of it. Loaded it in Odin as an AP and it worked! I have been using Magisk 24.3 all along because there is an issue with 25.0 that makes it stuck on the logo screen on rooted Galaxy Note 4 devices.
Still, is there a way to use fastboot on this device?
samsung galaxy note 4 (snapdragon and exynos) won't have fastboot mode, sorry.