Database Info

CWM flashing not possible

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;

[Q] bricked? not sure

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.

Bricked shield Tablet, fastboot only works.

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

Soft Bricked my Phone(Stuck in bootloop, fastboot flash fails)

Hi,
I recently flashed a custom ROM(Lineage OS 15.1) using this tutorial. Didn't like it so decided to switch back to stock. Trouble is I didn't have Stock ROM. Found one here and flashed it. It worked, sorta. My IMEI numbers were cleared. I have them on my box but no .bak file. Read somewhere that some apps can write IMEI but needed root and Xposed Framework.
Rooted my device using this tutorial and tried to install Xposed using this tutorial.
However,this caused my phone to get stuck in a bootloop.
Tried reset from stock recovery. Even though it says reset success, still stuck in bootloop. Also cleared Cache.
Tried flashing stock ROM and Lineage OS using fastboot flash system ***.img,
Code:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/7 (456507 KB)...
OKAY [ 19.324s]
writing 'system' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 19.402s
I can't seem to flash recovery or system.
Have I bricked it? Please help me out.

HarryPotterWannabe said:
Hi,
I recently flashed a custom ROM(Lineage OS 15.1) using this tutorial. Didn't like it so decided to switch back to stock. Trouble is I didn't have Stock ROM. Found one here and flashed it. It worked, sorta. My IMEI numbers were cleared. I have them on my box but no .bak file. Read somewhere that some apps can write IMEI but needed root and Xposed Framework.
Rooted my device using this tutorial and tried to install Xposed using this tutorial.
Now,
My phone is stuck in a bootloop.
Fastboot opens, but FRP is locked. (PHONE Unlocked).
all fastboot commands FAILED (remote: Command not allowed), except
fastboot devices, which shows my device.
I can't flash recovery or system.
Have I bricked it? Please help me out.
Click to expand...
Click to collapse
Can you still go into erecovery?
Sent from my HUAWEI BKL-L09 using XDA Labs

youtuber123 said:
Can you still go into erecovery?
Sent from my HUAWEI BKL-L09 using XDA Labs
Click to expand...
Click to collapse
Yes. attempted factory reset and cache. succeeds both, still stuck in boot loop

HarryPotterWannabe said:
Yes. attempted factory reset and cache. succeeds both, still stuck in boot loop
Click to expand...
Click to collapse
I'm not asking for the recovery but the Erecovery
The one who should help you in this situation
Sent from my HUAWEI BKL-L09 using XDA Labs

youtuber123 said:
I'm not asking for the recovery but the Erecovery
The one who should help you in this situation
Sent from my HUAWEI BKL-L09 using XDA Labs
Click to expand...
Click to collapse
Yes, it boots into erecovery. I don't have twrp, and can't seem to flash one because if command not allowed error.

Can't flash t.w.r.p / root on global fastboot 10.3.7 rom.

I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.

toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
What's the message that appears in ADB when you flash it?

toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
Did u unlocked the bootloader?
Sent from my Redmi Note 7 Pro using XDA Labs

Naveenthemi said:
What's the message that appears in ADB when you flash it?
Click to expand...
Click to collapse
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!

toyspeed said:
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!
Click to expand...
Click to collapse
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?

Naveenthemi said:
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?
Click to expand...
Click to collapse
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.

toyspeed said:
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.
Click to expand...
Click to collapse
Did it work?

Naveenthemi said:
Did it work?
Click to expand...
Click to collapse
I actually decided to flash Superior OS instead, loving it so far!