I've unlocked my Australian Telstra XT905 (finally!) but I can't seem to flash twrp.
S:\Dropbox\android\fastboot>fastboot flash recovery twrp-recovery-scorpion_mini.
img
sending 'recovery' (7346 KB)...
OKAY [ 0.554s]
writing 'recovery'...
OKAY [ 1.602s]
finished. total time: 2.155s
But every time I boot into recovery, I see the stock android with chest open image.... what gives???
wintermute000 said:
I've unlocked my Australian Telstra XT905 (finally!) but I can't seem to flash twrp.
S:\Dropbox\android\fastboot>fastboot flash recovery twrp-recovery-scorpion_mini.
img
sending 'recovery' (7346 KB)...
OKAY [ 0.554s]
writing 'recovery'...
OKAY [ 1.602s]
finished. total time: 2.155s
But every time I boot into recovery, I see the stock android with chest open image.... what gives???
Click to expand...
Click to collapse
Works fine for me. Since I'm a new user, I can't post links but if you google "rooting your dev razr m droid rzr", it's the very first link that was posted 05 January 2013.
If you follow the steps from that page, it should work perfectly as that's the steps I followed...
figured it out, you need to get into TWRP via booting with power button + up
If you boot back into menu and select recovery, I get the stock droid recovery.
I need a recovery that to suit my Australian XT905. I have done a bit of a hunt around and connot find one that works. Can someone please point me to a suitable TWRP, CWM etc that will work for me. The ones I have found so far keep reporting invalid partition size when I run fastboot.
Actually my Bad. Had not in fact unlocked my bootloader. Once I went to the moto site and did that I was able to install CWM. All good.
Related
So I just flash the factory image through fastboot, and the boot?
Flashing latest TWRP after that, which method is best to root afterwards? Thanks.
binaryfalcon said:
So I just flash the factory image through fastboot, and the boot?
Flashing latest TWRP after that, which method is best to root afterwards? Thanks.
Click to expand...
Click to collapse
You flash the images, then you flash TWRP, then you do a factory reset in TWRP, and install SuperSU (http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip), and then boot. You'll now have 4.4 Rooted.
binaryfalcon said:
So I just flash the factory image through fastboot, and the boot?
Flashing latest TWRP after that, which method is best to root afterwards? Thanks.
Click to expand...
Click to collapse
How long does it take to flash the image-occam-krt16o.zip? I have been waiting for 20 minutes now. This is my output from the command window
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.076s]
writing 'bootloader'...
OKAY [ 0.298s]
finished. total time: 0.375s
wickdc said:
How long does it take to flash the image-occam-krt16o.zip? I have been waiting for 20 minutes now. This is my output from the command window
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.076s]
writing 'bootloader'...
OKAY [ 0.298s]
finished. total time: 0.375s
Click to expand...
Click to collapse
You can run the flash all command, or you flash everything separately. Go to efrant's guide on how to do that here on xda. You have now flashed the bootloader succesfully, now you will have to flash the other images as well.
Sent from my Nexus 4 using xda app-developers app
why don't you install cwm/twrp first? it's a lot easier to flash in my opinion (not if you want to install the image from your computer)
but normally it just takes a few moments/minutes
Everytime I install TWRP and boot into it. It shows Zero internal storage and when I reboot it outlines there isnt an OS installed.
The system OS isnt wiped (although I thought that the first 50 times). When I enter fastboot again TWRP inst installed.
No idea what going on... tried latest and previous TWRP files.
thanks in advance
Heres the Log
-------------
Z:\NewNexus7Root\platform-tools>adb reboot bootloader
Z:\NewNexus7Root\platform-tools>fastboot flash recovery twrp-2.8.7.0-flo.img
sending 'recovery' (8956 KB)...
OKAY [ 0.291s]
writing 'recovery'...
OKAY [ 0.271s]
finished. total time: 0.564s
Z:\NewNexus7Root\platform-tools>adb reboot recovery
error: device not found
error: device not found
Got it working after I found the MultiRom fix on this site.
Seems I had one of those unique "locked down" Nexus's 2013; mines from Amazon.
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Your command is wrong, The command to use is: fastboot flash recovery twrp.the name of your file.img
Just like @jawmail said, you're flashing twrp on the bootloader """slot""
-fastboot flash recovery ***TWPR***.img
-fastboot reboot-bootloader
When your phone reboots, using your volume keys, search for "recovery" and using the power button, confirm it.
PROFIT
bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.
Haha. Thanks. Yeah I am really lucky. My phone is working now thanks. Just coming from the S6 Edge. Very different rooting method from that, so yeah I should be way more careful. Thanks for the awesome guide, btw Heisenberg. Running PureNexus with ExperimentalX kernel. Such an amazing combo.
Heisenberg said:
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.
Click to expand...
Click to collapse
Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?
Puck24 said:
Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?
Click to expand...
Click to collapse
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P
Heisenberg said:
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P
Click to expand...
Click to collapse
guess it's a corrupted file?
Actually, I just tried flashing it one more time, rebooted to the bootloader with the phone, not with the command. Then I also used the phone to enter into recovery, not by issuing commands. And it works
Sent from my Nexus 6P using XDA Free mobile app
So i have been trying to flash TWRP 3.0.0.1 onto my phone using the guide, http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928, and at first when i got to step 2 and tried to flash TWRP file, it would say "error: cannot load twrp.img"
and that went away and i was finally able to flash it after installing universal adb driver.
When i flash it i get this:
C:\SDK\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 494927872 bytes
sending 'recovery' (16904 KB)...
OKAY [ 0.415s]
writing 'recovery'...
OKAY [ 0.244s]
finished. total time: 0.665s
and when i try to reboot to the bootloader, it shows up the standard stock recovery. What am i doing wrong?
please help
Also, when i do adb devices, it wont show my device. But i saw on the forum that adb doesnt even matter.
NEVERMIND i got it to work. But now im having trouble flashing the lastest march update. It says error 7 and something about my SD card.
LifeOfNexus said:
So i have been trying to flash TWRP 3.0.0.1 onto my phone using the guide, http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928, and at first when i got to step 2 and tried to flash TWRP file, it would say "error: cannot load twrp.img"
and that went away and i was finally able to flash it after installing universal adb driver.
When i flash it i get this:
C:\SDK\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 494927872 bytes
sending 'recovery' (16904 KB)...
OKAY [ 0.415s]
writing 'recovery'...
OKAY [ 0.244s]
finished. total time: 0.665s
and when i try to reboot to the bootloader, it shows up the standard stock recovery. What am i doing wrong?
please help
Also, when i do adb devices, it wont show my device. But i saw on the forum that adb doesnt even matter.
NEVERMIND i got it to work. But now im having trouble flashing the lastest march update. It says error 7 and something about my SD card.
Click to expand...
Click to collapse
I flashed twrp 5 times.. before it "stick" and shows up twrp recovery.
So I tried to flash a custom recovery and got this
C:\Users\kevin>fastboot flash recovery twrp.img
sending 'recovery' (13134 KB)...
OKAY [ 0.432s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.453s]
finished. total time: 0.886s
Was curious if it flashed or not?
EDIT: I got the SU from here and it's still not giving me root after flashing SU to the device.
KevinDel said:
So I tried to flash a custom recovery and got this
C:\Users\kevin>fastboot flash recovery twrp.img
sending 'recovery' (13134 KB)...
OKAY [ 0.432s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.453s]
finished. total time: 0.886s
Was curious if it flashed or not?
EDIT: I got the SU from and it's still not giving me root after flashing SU to the device.
Click to expand...
Click to collapse
From what I've seen so far, you may be trying to flash a custom recovery that is not made for your device, which variant are you using? (ex: XT1760, XT1764, you can see them as SKU in fastboot mode)
Also, from where did you download the twrp?
Moderi said:
From what I've seen so far, you may be trying to flash a custom recovery that is not made for your device, which variant are you using? (ex: XT1760, XT1764, you can see them as SKU in fastboot mode)
Also, from where did you download the twrp?
Click to expand...
Click to collapse
I got the TWRP to actually work now, now it's trying to get SU to work. I got TWRP from here I can't get majisk or SU to run at all though now.
Moderi said:
From what I've seen so far, you may be trying to flash a custom recovery that is not made for your device, which variant are you using? (ex: XT1760, XT1764, you can see them as SKU in fastboot mode)
Also, from where did you download the twrp?
Click to expand...
Click to collapse
Also it's the XT1768 model.
Try installing magisk the new way (without a custom recovery). There are instructions in the main magisk thread.