Hey guys,
my bootloader is unlocked - so far, so good. however though, when I want to flash cwm, I'm getting this result:
C:\xyz>fastboot flash recovery cwmrecovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6632 KB)...
OKAY [ 0.558s]
writing 'recovery'...
OKAY [ 1.838s]
finished. total time: 2.397s
so it looks successful. But I still have the stock recovery. When I'm trying the rom manager from the playstore alternatively, I'm getting an error right aways after the cwm download (looks as if nothing happened in between). Error message is simply "An error occurred while flashing your recovery"
Any suggestions?
Thanks!
After you fastboot flash recovery, IMMEDIATELY reboot to recovery. Do not reboot to Android.
Take a backup. Then boot to Android... should stick.
Yeah, I learned that the hard way....
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Yeah, I learned that the hard way....
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Weird! I had the similar issue as described above. I'm able to successfully flash the CWM flash to the SPH-710 for me. However, can't boot INITIALLY to the CWM boot; It's able to successfully go into normal boot; But Volume-UP, Center button Power button, just blinks the custom boot screen once then the screen becomes blank for some time.
Can't get out of the Stock ROM boot up to CWM;
Related
I have an unlocked, rooted 300T with JB which I flashed to 10.4.2.13 using the existing installation of TWRP which has now disappeared when booting+Vol Down. I do not seem to be able to re-install TWRP using fast boot as I get this message.
Code:
C:\Users\Mike\Desktop\Fastboot>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)... OKAY [ 2.058s]
writing 'recovery'... FAILED (status read failed (Too many links))
finished. total time: 2.061s
I have searched extensively and cannot find a similar issue, but without TWRP I cannot then flash a custom ROM...:crying:
Seahorse said:
I have an unlocked, rooted 300T with JB which I flashed to 10.4.2.13 using the existing installation of TWRP which has now disappeared when booting+Vol Down. I do not seem to be able to re-install TWRP using fast boot as I get this message.
Code:
C:\Users\Mike\Desktop\Fastboot>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)... OKAY [ 2.058s]
writing 'recovery'... FAILED (status read failed (Too many links))
finished. total time: 2.061s
I have searched extensively and cannot find a similar issue, but without TWRP I cannot then flash a custom ROM...:crying:
Click to expand...
Click to collapse
Are you installing the jb compatible twrp? what happens when you try and boot recovery?
Sent from my SGH-I727 using xda app-developers app
I have downloaded the 2.2.2 jb blob from here. When I boot into recovery & select RCK I get an android on his back with an exclamation mark in his stomach.
Seahorse said:
I have downloaded the 2.2.2 jb blob from here. When I boot into recovery & select RCK I get an android on his back with an exclamation mark in his stomach.
Click to expand...
Click to collapse
When you used twrp to flash stock it includes recovery which overwrites twrp. Go back to the instructions to fastboot twrp, do so and you should be good.
Good Luck!
Try a new download of twrp!
Reboot your pc, only plugin your asus and no other device, retry fastboot.
Forgot, if on dock remove from dock reboot pc and asus and try again.
Clearing cache maybe? Just a shot in the dark, never seen this one. I can tell you I flashed ota v13 and it blew away my recovery but I was able to get it back easily.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
After following numerous google links - too many links fastboot, I found one resolution. Another device used on pc and usb drivers installed since last use of unit giving links error. Resolution was remove offending drivers, reboot pc and profit.
Good Luck!
I'm having a bit of a different problem. I have flashed twrp 2.2.2 several times and each time it says okay but it isn't updating it. I still have 2.2.1.5 installed.
Code I'm using...
adb reboot bootloader
fastboot -i 0x0B05 flash recovery tf300t-jb.blob
Click to expand...
Click to collapse
It goes through the install and says OKAY at the end yet it doesn't actually update the recovery blob.
Blew away cache, used fastboot again on twrp.blob and got same install fail error message. However, on power on + vol down RCK now works with TWRP, which is kind of odd, but there you go. Thanks for all the suggestions...
glad you got it fixed
SITH16 said:
I'm having a bit of a different problem. I have flashed twrp 2.2.2 several times and each time it says okay but it isn't updating it. I still have 2.2.1.5 installed.
Code I'm using...
Quote:
adb reboot bootloader
fastboot -i 0x0B05 flash recovery tf300t-jb.blob
It goes through the install and says OKAY at the end yet it doesn't actually update the recovery blob.
Click to expand...
Click to collapse
Three things come to mind.
1. Try to flash as twrp directions show; without adb reboot bootloader.
2. Verify you are trying to flash the proper version for your bootloader; ics or jb.
3. If the above two items fail redownload proper version for your boot loader and try again.
Note: The twrp page also shows how to flash with adb!
Good Luck!
Terminal Emulator is an easier way to flash TWRP imo. But hey.
babymatteo said:
Terminal Emulator is an easier way to flash TWRP imo. But hey.
Click to expand...
Click to collapse
Terminal method worked. Thanks everyone for helping me out.
TWRP Install Fail
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?
BadWolf428 said:
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?
Click to expand...
Click to collapse
this is the tf300t forum. Make sure you are installing a tf700t TWRP
cmendonc2 said:
this is the tf300t forum. Make sure you are installing a tf700t TWRP
Click to expand...
Click to collapse
I noticed that after I hit reply. I was using all of the correct TF700t TWRP and whatnot. I found this in a google search because it was similar to my issue. It turned out that even though I thought I had unlocked my device, it did not unlock. I fixed that and now I am all set.
BadWolf428 said:
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?
Click to expand...
Click to collapse
The warning invalid state normally applies to the bootloader being locked make sure your bootloader is unlocked.
Sent from my Nexus 5 using Tapatalk
Got a phone from a friend. Said it was bricked.
In bootloader:
*** unlocked ***
doubleshot pvt ship s-on rl
hboot-1.45.0013
microp-0353
emmc-boot
When click recovery, get 3 skateboarders and back to menu.
Tried to load a recovery:
C:\Android>fastboot flash recovery recovery-clockwork-5.0.2.7-doubleshot.img
sending 'recovery' (4754 KB)...
OKAY [ 0.888s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.348s
Received above error, should I perform another step first?
Somehow finally got cwm 5.0.2.7 into recovery.
Found this thread and did basically the same thing.
http://forum.xda-developers.com/showthread.php?t=2665472
Downloaded cm-9-1-(3-0-97)-r13.zip
Checked md5sum
Extract contents of ROM to PC(boot.img)
Put the full zip and gapps on SD card
Boot to recovery
Wipe data/factory reset, wipe cache partition
Flash ROM cm-9-1-(3-0-97)-r13.zip. Install successful.
Pulled battery, boot direct to bootloader
Flash kernel with fastboot <<<<< here I get the below error
fastboot flash boot boot.img
sending 'boot' (16384 KB)...
OKAY [ 2.624s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 4.085s
Any suggestions?
Try miktouch or another stock based ROM so you don't need to flash kernel
Sent from my Nexus 4 using XDA Premium 4 mobile app
Is there a particular miktouch I should try? Would the below link be good to try?(for some reason having hard time finding)
"cx.com/mycx/share/jzvMU-erEeGfjBICOBql1A/MikTouch-0.7-signed.zip"
And just follow the steps and flash it vs cm9, correct?
Any stock based ROM is easier to flash as you don't need to flash the kernel afterwards through fastboot. Also cm9 is one of the few Roms I have seen issues for people when trying to flash, granted it is one of the better Roms out there, but right now you are just trying to get this working again, so stick with easy.
And I would think that's a good link, but didn't check
Sent from my Nexus 7 using XDA Premium 4 mobile app
installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.
any suggestions on trying something else?
waynebattle said:
installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.
Click to expand...
Click to collapse
What ROM were you on before? If its non stock, I would try to fastboot flash the boot.img
Sent from my Nexus 4 using Tapatalk
unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?
waynebattle said:
unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?
Click to expand...
Click to collapse
On some of my Linux distros I would have to use fastboot flash with a ./ before it would work.
./fasboot flash boot boot.Img
I have no idea why it was like this but it helped me a fee times on the DS. If its anything else I'd have no idea, I haven't messed with this since I sent mine off to a XDA user here.
Sent from my Nexus 4 using Tapatalk
Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?
waynebattle said:
Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?
Click to expand...
Click to collapse
You said you are able to get into recovery? Try factory resetting there
Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.
abe5 said:
Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.
Click to expand...
Click to collapse
dont you need to be locked to do this? i've tried "fastboot oem lock" but it has an error about too many links and the phone shuts off and it shows that it is still unlocked. I tried the PG59IMG.zip anyway and it said parsing and went right back to hboot within a second.. Flashed miktouch rom. Restarted phone, still just stuck on logo screen.
What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.
abe5 said:
What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.
Click to expand...
Click to collapse
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?
waynebattle said:
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?
Click to expand...
Click to collapse
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6
abe5 said:
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6
Click to expand...
Click to collapse
No luck, (md5 check sum verified) get error when try to flash it:
C:\Android>fastboot flash recovery cwm.img
sending 'recovery' (6338 KB)...
OKAY [ 1.285s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.745s
Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When you say adb working from within recovery, I am able to mount usb storage within recovery and then on pc I can do 'adb devices' and I see the device, is that what you are referring to? Thanks.
got a bricked N5
tried to install stock from fastboot but after each reboot bootloader relocks
so wanted to install TWRP and go from there
Code:
C:\>adb2\fastboot flash recovery recovery-twrp-3.0.2.0-hammerhead.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14524 KB)...
OKAY [ 0.629s]
writing 'recovery'...
OKAY [ 1.104s]
finished. total time: 1.736s
but when i boot to recovery get stock 6.0.1 recovery
ideas?
iakovl said:
got a bricked N5
tried to install stock from fastboot but after each reboot bootloader relocks
so wanted to install TWRP and go from there
but when i boot to recovery get stock 6.0.1 recovery
ideas?
Click to expand...
Click to collapse
Since it's keep relocking bootloader, it's time to say goodbye, unfortunately. Memory chip is done.
Sent from my Nexus 5 using XDA Labs
Any hope left? Goes to boot menu. Goes to recovery but just stuck on bootloop
Sent from my SM-N920I using Tapatalk
iakovl said:
Any hope left? Goes to boot menu. Goes to recovery but just stuck on bootloop
Click to expand...
Click to collapse
As far as I've been reading about that exact problem, no hope. It was always the same answer, eMMC is damaged.
Sent from my Nexus 5 using XDA Labs
When unlocking the bootloader, it should take more than a few seconds to format and reset. If the process is done in a few seconds, this is also an indication the memory chip is defective.
Going through some of the threads here got me as far as being able to use fastboot on my bricked Shield.
I would like to ask if anyone can give me some pointers what to try next.
The previous owner tried to flash Lineage OS onto the Tablet using CWM but this failed and he probably wiped some needed partition.
I tried to flash new partitions and this works but I can not start the Shield and it won't boot into CWM. The strange thing is that I tried flashing TWRP and even though that started it did not boot through. And after a simple Shield reboot the CWM logo popped upmagain.....:confused
I was convinced I could fix this but I am beginning to think that this Tablet is a goner...
Any thoughts would ne appreciated.
What happens if you download an original recovery image from Nvidia for your model, and flashboot flash all 5 (recovery, boot, system, userdata, blob)? Do you get any fastboot errors? If the partition structure is corrupted, you'll see some sort of error message.
If the blob is messed up sometimes TWRP won't start. I suggest getting a factory image and trying again, then giving it a long time to boot. Once mine took 20 minutes at the Nvidia screen.
I did try flashing the original image from Nvidia including the other 4 images. One of the first things I tried. I woyld like to get it back to factory default. This went without issues an no errors. I might not have given it enough tine to but but still CWM seems to be on.
Will give it another try and post a screenshot.
Sent from my SM-G935F using Tapatalk
Here is a dump of the flash log. After flashing I reboot and the CWM logo pops up after a few minutes and gets stuck.
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.384s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.709s
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.394s]
booting...
OKAY [ 0.017s]
finished. total time: 0.417s
Think it is done for, after flashing TWRP numerous times it let me get to the start screen for TWRP it then hangs. When you reboot the Shield and want to go to the recovery again you get the dead android.
PS. I can sometimes get into TWRP but it fails on everything I do. Would there be a terminal solution for this? Like re-creating partitions?
Unlock your bootloader?
Sent from my ZTE A2017U using Tapatalk
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
sn0r said:
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Try to flash the attached file. Remember to unzip it first! Flash with:
"fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
sn0r said:
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
Click to expand...
Click to collapse
Then my guess would be some problems with the internal storage which may not be repairable.
Using fastboot try the following
Fastboot erase cache
Fastboot format cache
Fastboot format userdata
Make sure your tablet is in bootloader mode first though.
Sent from my pa_osprey using Tapatalk
Hello,
Edit: Don't know how or why, but after a couple of more tries I was able to boot the recovery directly and flash the rom. So everything is working fine right now. Admin/mod, would you like to close this thread? Thank you
For some reason I wanted to flash a new rom on my XT1039. In the process I screwed up and got it softbricked. I already had a look at the thread started by alfread56 and although the situation seems quite similar, the offered solutions didn't work out for me.
Right now my phone doens't have any rom installed. Flashing twrp with fastboot suggest everything works allright (using a linux system by the way):
fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (8314 KB)...
OKAY [ 0.295s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.598s
After the reboot and holding the buttons for recovery mode I still get the stock recovery screen. When I select recovery in this menu, the phone shuts down. Because I know holding the recovery buttons on reboot takes some timing, I have redone the procedure of flashing twrp and holding the buttons numerous times. But it never went to the twrp recovery.
Then I tried to boot the twrp image directly with
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.290s]
booting...
OKAY [ 0.230s]
finished. total time: 0.520s
Here I made a mistake: I have also flashed the boot partition with the twrp image with fastboot flash boot recovery.img (don't know how much of problem this is).
Booting up the TWRP image works fine. Then I've wiped dalvik, cache, data, internal storage and after several runs also deleted system by accident, and factory reset. When trying to flash the lineage zip everything works out fine for about 1 second, then the screen flashes en the phone is back in the TWRP screen. Too quick for me to see what the output is, but I do see there are not red marked lines (no errors)
I have tried it with several different ROMS (al checked), with several versions of TWRP and with fastboot and mfastboot. Does anybody know a solution on how to get twrp recovery working on my phone, or why I can't flash a rom when I boot twrp directly? Any help is appreciated!
Thank you in advance.
Regards,
weisa4564