Database Info

Stock Recovery zip

Hi, am looking for the stock recovery file/zip p[ease.

The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.

_that said:
The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.
Click to expand...
Click to collapse
Thanks.

_that said:
The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.
Click to expand...
Click to collapse
I got the firmware and extracted the blob, but I only have fastboot, how do I flash it to get stock recovery back?
I tried this:
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 flash system blob
but nothing works, except I lost /system partition now (I was able to boot Android before). Any help appreciated.

3c said:
I got the firmware and extracted the blob, but I only have fastboot, how do I flash it to get stock recovery back?
I tried this:
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 flash system blob
but nothing works, except I lost /system partition now (I was able to boot Android before). Any help appreciated.
Click to expand...
Click to collapse
Sorry, if that doesn't work I have no more idea how to fix your locked tablet, if you don't have the blob for wheelie and nvflash.

_that said:
Sorry, if that doesn't work I have no more idea how to fix your locked tablet, if you don't have the blob for wheelie and nvflash.
Click to expand...
Click to collapse
Thanks anyway for helping. All I could figure out is that the blob doesn't actually get written to any partition. I've seen some users be successful doing that (what you suggested), so I'll keep trying, maybe reverting the driver. Wondering if using naked driver works well for such method.
In any case, thanks, and I'll post a reply if I can make it work.

3c said:
Thanks anyway for helping. All I could figure out is that the blob doesn't actually get written to any partition. I've seen some users be successful doing that (what you suggested), so I'll keep trying, maybe reverting the driver. Wondering if using naked driver works well for such method.
In any case, thanks, and I'll post a reply if I can make it work.
Click to expand...
Click to collapse
Try this, download stock recovery here http://www.mediafire.com/download.php?pdipp4h2qyqka63
then execute this:
fastboot -i 0x0B05 flash recovery recovery.blob
boot directly into recovery and see if you have recovery back.

buhohitr said:
Try this, download stock recovery here http://www.mediafire.com/download.php?pdipp4h2qyqka63
then execute this:
fastboot -i 0x0B05 flash recovery recovery.blob
boot directly into recovery and see if you have recovery back.
Click to expand...
Click to collapse
Big progress: blob flashed without a glitch. I was happy until I tried to reboot with fastboot: tablet frozen! Reboot, still no recovery
I guess this is it. Got a nice folding brick now! Will try RMA, but from Cambodia not sure it's worth it. Maybe next month when I'm in France.
Can't believe this happened while tablet is locked! Now I hate Asus for this.

3c said:
Big progress: blob flashed without a glitch. I was happy until I tried to reboot with fastboot: tablet frozen! Reboot, still no recovery
I guess this is it. Got a nice folding brick now! Will try RMA, but from Cambodia not sure it's worth it. Maybe next month when I'm in France.
Can't believe this happened while tablet is locked! Now I hate Asus for this.
Click to expand...
Click to collapse
I have asked you to flash the recovery zip, but once done you should boot directly into the recovery, don't boot up. Let me know if you still can fastboot the recovery to your device, but once done, hold the power until device turn off, then right away hold both power button and volume down button to boot into recovery. If you could do this we still have hope. Once in recovery let me know we can proceed to next step.

buhohitr said:
I have asked you to flash the recovery zip, but once done you should boot directly into the recovery, don't boot up. Let me know if you still can fastboot the recovery to your device, but once done, hold the power until device turn off, then right away hold both power button and volume down button to boot into recovery. If you could do this we still have hope. Once in recovery let me know we can proceed to next step.
Click to expand...
Click to collapse
I cannot actually do anything past flashing a blob. the tablet is "frozen" from the moment it enters fastboot, then after flashing any blobs, any further fastboot command are "non-responsive", here is the actual output. At the end the reboot command succeeds but nothing actually happened on the tablet. Still showing the 4 icons (RCK/Android/USB/WIPE) and the top white text. Tried with original Asus driver, with Google driver and now naked driver. no difference, can only be the tablet ;(
C:\Android\android-sdk\platform-tools>fastboot devices
015d2a5088641a08 fastboot
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery.blob
sending 'recovery' (6260 KB)...
OKAY [ 1.862s]
writing 'recovery'...
OKAY [ 2.432s]
finished. total time: 4.297s
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.642s
C:\Android\android-sdk\platform-tools>fastboot continue
resuming boot...
FAILED (command write failed (Unknown error))
finished. total time: 0.569s
C:\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
EDIT: Kinda lame I'm sure, but desperate as I am, I tried that too:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 boot recovery.blob
creating boot image...
creating boot image - 6414336 bytes
downloading 'boot.img'...
OKAY [ 1.857s]
booting...
FAILED (remote: ()
finished. total time: 1.861s
I suppose I need a kernel blob... But I couldn't find any stock to flash? Would you also happen to have that handy too?

3c said:
I cannot actually do anything past flashing a blob. the tablet is "frozen" from the moment it enters fastboot, then after flashing any blobs, any further fastboot command are "non-responsive", here is the actual output. At the end the reboot command succeeds but nothing actually happened on the tablet. Still showing the 4 icons (RCK/Android/USB/WIPE) and the top white text. Tried with original Asus driver, with Google driver and now naked driver. no difference, can only be the tablet ;(
C:\Android\android-sdk\platform-tools>fastboot devices
015d2a5088641a08 fastboot
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery.blob
sending 'recovery' (6260 KB)...
OKAY [ 1.862s]
writing 'recovery'...
OKAY [ 2.432s]
finished. total time: 4.297s
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.642s
C:\Android\android-sdk\platform-tools>fastboot continue
resuming boot...
FAILED (command write failed (Unknown error))
finished. total time: 0.569s
C:\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
EDIT: Kinda lame I'm sure, but desperate as I am, I tried that too:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 boot recovery.blob
creating boot image...
creating boot image - 6414336 bytes
downloading 'boot.img'...
OKAY [ 1.857s]
booting...
FAILED (remote: ()
finished. total time: 1.861s
I suppose I need a kernel blob... But I couldn't find any stock to flash? Would you also happen to have that handy too?
Click to expand...
Click to collapse
Seems like when you flashed the blob file it wipe out everything. But I tried to boot into recovery so it's a good sign that your tablet is not brick ....yet!!
Here is the stock kernel I created for you http://www.mediafire.com/download.php?16fji3z1nghr6th
fastboot -i 0x0B05 flash boot boot.blob
Possible we may need the bootloader too, but will see.

buhohitr said:
Seems like when you flashed the blob file it wipe out everything. But I tried to boot into recovery so it's a good sign that your tablet is not brick ....yet!!
Here is the stock kernel I created for you http://www.mediafire.com/download.php?16fji3z1nghr6th
fastboot -i 0x0B05 flash boot boot.blob
Possible we may need the bootloader too, but will see.
Click to expand...
Click to collapse
I guess I'm ready for bootloader flashing. Either it bricks it for good or it works or else
Nothing has changed. Just to give you more info, booting RCK, results in booting failed - unrecoverable bootloader error (0x000..).
Booting android: cold-booting linux - signature match. Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
So I tried flashing boot.blob and recovery.blob and the JB update blob to system again, but it hangs at the end, still have to reboot manually. It's like fastboot is not actually flashing anything, writing in below output is abnormally low or could it be that fast!?: It's the same time for boot, recovery of a 800Mb system file!?
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.329s]
sending 'system' (800199 KB)...
OKAY [141.653s]
writing 'system'...
OKAY [ 2.932s]
finished. total time: 146.920s
But the behavior of the bootloader seems quite strange, all this hanging at end of flashing, could this be a corrupted bootloader or worse a corrupted partition table?

3c said:
I guess I'm ready for bootloader flashing. Either it bricks it for good or it works or else
Nothing has changed. Just to give you more info, booting RCK, results in booting failed - unrecoverable bootloader error (0x000..).
Booting android: cold-booting linux - signature match. Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
So I tried flashing boot.blob and recovery.blob and the JB update blob to system again, but it hangs at the end, still have to reboot manually. It's like fastboot is not actually flashing anything, writing in below output is abnormally low or could it be that fast!?: It's the same time for boot, recovery of a 800Mb system file!?
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.329s]
sending 'system' (800199 KB)...
OKAY [141.653s]
writing 'system'...
OKAY [ 2.932s]
finished. total time: 146.920s
But the behavior of the bootloader seems quite strange, all this hanging at end of flashing, could this be a corrupted bootloader or worse a corrupted partition table?
Click to expand...
Click to collapse
Let try the bootloader http://www.mediafire.com/download.php?u6bwnaao6khcdaf

3c said:
Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
Click to expand...
Click to collapse
Define "Windows recognizes the tablet". If you have ADB access, you should be able to recover.

buhohitr said:
Let try the bootloader http://www.mediafire.com/download.php?u6bwnaao6khcdaf
Click to expand...
Click to collapse
Actually how do you flash bootloader? I did this: fastboot -i 0x0B05 flash bootloader loader.blob ?
But anyway, I just read fastboot doesn't flash anything when device is locked! So this piece of s**t doesn't flash but will erase any partition you wish! How's that for a crappy software! I wish I never tried to update to JB!
_that said:
Define "Windows recognizes the tablet". If you have ADB access, you should be able to recover.
Click to expand...
Click to collapse
No ADB, just the name of the tablet appears in Device Manager, sort of the SD card access, but no actual access. I updated the driver manually and was proposed some MTP device. No adb or fastboot when this is available.
Here is the input from another thread: I copy it because I believe the information is very important and identify another way to brick the TF700:
Pretoriano80 said:
ICS bootloader had the fastboot option disabled if the device's bootloader was still locked and the USB icon wasn't showing at all.
With the JB bootloader Asus made the USB icon available even if the device was locked so you can access fastboot mode but you can't flash anything (yes,it doesn't make sense, but this is Asus).
Anyway, if you are able to boot in recovery you should be able to restore you device easily,just follow my guide from the general forum.
Click to expand...
Click to collapse
That's exactly what's happening! I can go in fastboot, but it doesn't flash anything! Though it erase any partition you wish! How smart is that? So I have one thing to say to locked owner: never go in fastboot, ever, it's useless and can actually brick your tablet!!!
I bricked the tablet on my own sure enough, but without this ridiculous fastboot I wouldn't have been able to mess up the tablet in the first place! Sorry for those who love their tablet and Asus, but I find their strategy ridiculous. Except if it's main goal is to make money on RMA.
Thanks Asus for this nice brick!

3c said:
But anyway, I just read fastboot doesn't flash anything when device is locked! So this piece of s**t doesn't flash but will erase any partition you wish!
Click to expand...
Click to collapse
I'd still expect the locked bootloader to flash correctly signed blobs. But who knows what Asus were thinking...
One more idea you can try: Get the 10.4.4.23 dlpkgfile and extract the blob from there.
This blob contains the 10.4.4.23 bootloader, stock recovery and stock kernel, and an orignal Asus signature. My WW version is 13573093 bytes, so it is much smaller than the full firmware blob - try to flash that via fastboot, maybe you are lucky and it works.

_that said:
I'd still expect the locked bootloader to flash correctly signed blobs. But who knows what Asus were thinking...
One more idea you can try: Get the 10.4.4.23 dlpkgfile and extract the blob from there.
This blob contains the 10.4.4.23 bootloader, stock recovery and stock kernel, and an orignal Asus signature. My WW version is 13573093 bytes, so it is much smaller than the full firmware blob - try to flash that via fastboot, maybe you are lucky and it works.
Click to expand...
Click to collapse
Will do, thanks. How would you flash such blob? Onto "staging" or "system"? I've seen users flash the JB update blob to system and be successful. Also seen some posts mentioning staging?

3c said:
Will do, thanks. How would you flash such blob? Onto "staging" or "system"? I've seen users flash the JB update blob to system and be successful. Also seen some posts mentioning staging?
Click to expand...
Click to collapse
I don't really know - all I know is:
- TF700's fastboot implementation only supports blobs, no raw partition images
- blobs are usually always written to the staging partition first, then the contained partition images are flashed to the correct partition(s) by the bootloader
I've seen both variants of the fastboot command, so maybe the target partition doesn't matter when sending blobs. I'd try staging first.

RSD completes but I still have CM10 no matter what I do.

RSD completes but I still have CM10 no matter what I do.
I am having problems with my phone so I was gonna go back to stock but I realized RSD completes but the phone still boots into CM10 and factory reset/wipe does nothing in recovery.
What can I try?

Flash another rom?
sent from my thumbs

Firstly there is a dedicated CM10 Q&A thread so you could have avoided a new thread & be getting more responses. Now you can post in there with more details of your phone original stock firmware to the steps you worked up to CM10 & finally what fxz are you flashing to go back to stock so that some one may be able to help you.

sounreal said:
RSD completes but I still have CM10 no matter what I do.
I am having problems with my phone so I was gonna go back to stock but I realized RSD completes but the phone still boots into CM10 and factory reset/wipe does nothing in recovery.
What can I try?
Click to expand...
Click to collapse
Open the XML file using a text editor and check if there is a line containing system.
As a solution, you may open a command prompt in that folder using shift+right click. Put your phone in fastboot mode. Type and hit enter.
Code:
fastboot flash system system.img
Sent from my ME865 using Tapatalk 2

RAD7 said:
Firstly there is a dedicated CM10 Q&A thread so you could have avoided a new thread & be getting more responses.
Click to expand...
Click to collapse
Excuse you but I know you are pretty helpful around here I'm removing cm 10 and going back to stock. I know what I'm doing yet its not working something is physically wrong with the phone I guess. Cm10 worked perfectly fine for about 6 months on the phone. im using whatever att fxz ICS file that is posted. At one point in time I had 3 atrix 2s all on cm10 and I removed them all by rsd to ICS. I have tried every version I could fine of rsd and att fxz file.

Ravikirancg said:
Open the XML file using a text editor and check if there is a line containing system.
As a solution, you may open a command prompt in that folder using shift+right click. Put your phone in fastboot mode. Type and hit enter.
Code:
fastboot flash system system.img
Sent from my ME865 using Tapatalk 2
Click to expand...
Click to collapse
I'm super late... but I flashed everything. Including boot.img preinstall.img radio.img recovery.img fromInlineFlashing_Edison_67.21.125_CFC_P3_APBP and they all say something like
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot flash system system.img
target reported max download size of 1056964608 bytes
sending 'system' (491264 KB)...
OKAY [ 23.743s]
writing 'system'...
OKAY [ 14.976s]
finished. total time: 38.719s
I never get a error message. I reboot and CM10 is still on the phone. I how I delete the partitions and then reformat them?
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot format system
formatting 'system' partition...
FAILED (remote: protocol error)
FAILED (remote: protocol error)
finished. total time: -0.000s
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot erase system
erasing 'system'...
(bootloader) Command restricted
FAILED (remote: )
finished. total time: 0.016s

sounreal said:
I'm super late... but I flashed everything. Including boot.img preinstall.img radio.img recovery.img fromInlineFlashing_Edison_67.21.125_CFC_P3_APBP and they all say something like
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot flash system system.img
target reported max download size of 1056964608 bytes
sending 'system' (491264 KB)...
OKAY [ 23.743s]
writing 'system'...
OKAY [ 14.976s]
finished. total time: 38.719s
I never get a error message. I reboot and CM10 is still on the phone. I how I delete the partitions and then reformat them?
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot format system
formatting 'system' partition...
FAILED (remote: protocol error)
FAILED (remote: protocol error)
finished. total time: -0.000s
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot erase system
erasing 'system'...
(bootloader) Command restricted
FAILED (remote: )
finished. total time: 0.016s
Click to expand...
Click to collapse
You are like a year late lol
alright,
could you tell me what was your stock version?
and the version name?
and what version of RSD are you using?

Uzayr said:
You are like a year late lol
alright,
could you tell me what was your stock version?
and the version name?
and what version of RSD are you using?
Click to expand...
Click to collapse
4.0.4... I don't remember... A year ago I tried every RSD I could find. After I could not get it to format using fastboot I tried to brick it with RSD using the wrong Asia firmware. They did not do anything.

sounreal said:
4.0.4... I don't remember... A year ago I tried every RSD I could find. After I could not get it to format using fastboot I tried to brick it with RSD using the wrong Asia firmware. They did not do anything.
Click to expand...
Click to collapse
i had similar problems using an older version of rsd/
so i suggest you try RSD Lite 6 and up and see if it works for you.
Alright, could you tell if you A2 is at&t or retail?
i'll try my best to salvage the right fxz for you.

I'm sure I have RSD 6 lite but just so we are on the same page... Can you give me a link to the correct RSD 6 LITE? Oh yeah and its a ATT Atrix 2

sounreal said:
I'm sure I have RSD 6 lite but just so we are on the same page... Can you give me a link to the correct RSD 6 LITE? Oh yeah and its a ATT Atrix 2
Click to expand...
Click to collapse
Link for RSD Lite 6.1.4
http://forum.xda-developers.com/showthread.php?t=2637338
And also for the fxz file..i suggest you try the third link in this page
http://sbf.droid-developers.org/phone.php?device=17
if you were already on 4.0.4 before you flashed cm

I had RSD 6.1.4 installed but I tried 6.1.6 and the same thing happened. Once RSD completed the phone rebooted to the stock android recovery. I Hit the volume keys to bring up the menu and hit reboot... Still have CM 10...

sounreal said:
I had RSD 6.1.4 installed but I tried 6.1.6 and the same thing happened. Once RSD completed the phone rebooted to the stock android recovery. I Hit the volume keys to bring up the menu and hit reboot... Still have CM 10...
Click to expand...
Click to collapse
wait a minute...you don't need to hit the volume keys in recovery.
after fxz the phone should reboot to recovery and complete the other half of the setup.

I read if it and did not touch it once it got to the stock recovery... After about 2 mins it rebooted and I still had CM 10.

Hi, I am fairly new here but I have been around (just leeching, LOL) since my SE X10 Mini.
You could try using RSDLite 5.3.1.
I used it just this morning when I got black screen after flashing things after AOSB.
Just make sure you have the latest Moto Drivers.
Good luck! :good:
Cheers,
Rae

Raeshabu said:
Hi, I am fairly new here but I have been around (just leeching, LOL) since my SE X10 Mini.
You could try using RSDLite 5.3.1.
I used it just this morning when I got black screen after flashing things after AOSB.
Just make sure you have the latest Moto Drivers.
Good luck! :good:
Cheers,
Rae
Click to expand...
Click to collapse
Nope that did not help I still have cm10.

[Q] Flashed the LPX13D image and now my recovery is gone.

Hi Guys,
Hoping you can help me with this.
I was originally running Slimkat 4.4.4 and had the latest TWRP installed.
I downloaded the file for LPX13D and extracted all of the files right down to the Flash-all.bat and the images for bootloader, radio, and the system.
I ran the Flash-all.bat, and it installed everything successfully. The device booted, and voila, I am on 5.0 now.
The problem now, is that when I reboot into recovery, I am instead met with the little android guy laying on his back, with a red triange/exclamation point in his chest.
No problem, I say to myself. I'll just flash TWRP manually.
So I go to the bootloader, and try the command fastboot flash recovery recovery.img (renamed to make it faster to type.)
It goes through the motions, and says it was successful.
But when I go to recovery, it's the same red triange guy still.
I tried pressing volume up, power+volume up, etc. No dice. After about 30 seconds, it reboots on it's own back to system.
When I connect it to the Nexus Root Toolkit, and click on Flash recovery, and then choose TWRP latest, I get a window that pops up that tells me :
______
File Dependency Download
Status: Stock Kernel: Not Present - Need to download (this is in red)
Then a button that says "Download + Update All File Dependencies"
So what's my best option here? Should I let the NRT update the dependencies?

Try to flash cwm and tell me what happens

Isus <3 said:
Try to flash cwm and tell me what happens
Click to expand...
Click to collapse
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.

deleted

Stupendousman2012 said:
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
Click to expand...
Click to collapse
Twrp is not optimized yet well like cwm is for andorid l

Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Lethargy said:
I flashed the new developer preview for 5 minutes or so then went to revert. Recovery wouldn't boot not matter what I flashed, until I flashed a KK userdata.img. So it seems like the new developer preview changes the internal storage/data partition more then the old one.
Click to expand...
Click to collapse
Don't try getting around it. Nothing to do with anything else.
Isus <3 said:
Twrp is not optimized yet well like cwm is for andorid l
Click to expand...
Click to collapse
What? CWM is outdated.

Lethargy said:
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Don't try getting around it. Nothing to do with anything else.
What? CWM is outdated.
Click to expand...
Click to collapse
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
I also flashed the boot.img and the supersu update to get root working, and it seems to be going well now.
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.

Stupendousman2012 said:
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
Click to expand...
Click to collapse
Flash userdata.img and your TWRP will work properly.
Stupendousman2012 said:
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
Click to expand...
Click to collapse
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
Stupendousman2012 said:
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Click to expand...
Click to collapse
It says that because CWM is outdated.

Lethargy said:
Flash userdata.img and your TWRP will work properly.
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
It says that because CWM is outdated.
Click to expand...
Click to collapse
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?

Stupendousman2012 said:
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Click to expand...
Click to collapse
Yeah. Don't need to boot into recovery and wipe data since flashing a .img with fastboot while in bootloader erases it first then flashes. Just make sure you backup your stuff, including internal storage, off to a PC first if you have anything important.

Until L is officially released, we're using the below thread
http://forum.xda-developers.com/show....php?t=2796217
Android "L" Developer Preview Help, Troubleshooting, Q&A
Sent from my Nexus 5 using Tapatalk

[Q] Problem flashing CWM - MT7-L09

I've got a Mate7 (MT7-L09) that I bought used, from the look of it, it's been previously unlocked (which is good, since I've been unable to get an unlock code from Huawei for it), and is running the latest L09 factory rom (See attached screen shot, yep, says unlocked.)
Unfortunately, when I try to flash CWM, I get the following:
[email protected]:~/android-sdk-linux/platform-tools$ sudo ./fastboot flash recovery recovery_h60.img
target reported max download size of 471859200 bytes
sending 'recovery' (9386 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Attempting to flash the stock recovery works just fine. I've downloaded a couple of different copies of CWM and they all fail with the same error. I've also tried under Windows with the same error.
I've also tried flashing the factory image from the SD card to return the phone to 'stock' before again trying to flash CWM, this also did not fix the problem.
Any ideas?
Thanks!
Justin

Turbo4V said:
I've got a Mate7 (MT7-L09) that I bought used, from the look of it, it's been previously unlocked (which is good, since I've been unable to get an unlock code from Huawei for it), and is running the latest L09 factory rom (See attached screen shot, yep, says unlocked.)
Unfortunately, when I try to flash CWM, I get the following:
[email protected]:~/android-sdk-linux/platform-tools$ sudo ./fastboot flash recovery recovery_h60.img
target reported max download size of 471859200 bytes
sending 'recovery' (9386 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Attempting to flash the stock recovery works just fine. I've downloaded a couple of different copies of CWM and they all fail with the same error. I've also tried under Windows with the same error.
I've also tried flashing the factory image from the SD card to return the phone to 'stock' before again trying to flash CWM, this also did not fix the problem.
Any ideas?
Thanks!
Justin
Click to expand...
Click to collapse
man who told u flash that crap cwm which is not even for mate 7 ???
where did u get that crap.. thats for honor 6 or p7..
check mate 7 forum (general) and ull find PROPER recovery cwm for mate 7 !
i think i gave u lots of clues..
And if u tried to flash other CWMs ten u have old flash adb fastboot files..
u need latest ones supports higher sizes

Simona Simmy said:
man who told u flash that crap cwm which is not even for mate 7 ???
where did u get that crap.. thats for honor 6 or p7..
check mate 7 forum (general) and ull find PROPER recovery cwm for recovery_h60.imgmate 7 !
i think i gave u lots of clues..
And if u tried to flash other CWMs ten u have old flash adb fastboot files..
u need latest ones supports higher sizes
Click to expand...
Click to collapse
This is actually a recovery for the HAM7, not the Honor6/P7. Recovery_h60.img is just what the recovery was initially called (check the thread http://forum.xda-developers.com/mat...custom-recovery-tool-mt7-l10-l10-mt7-t3022424). I got the CWM file from that thread.
I've also tried the updated version posted in the same thread (MT7_CWM_CN_EN.img) with the same results.
sudo ./fastboot flash recovery MT7_CWM_CN_EN.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.800s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.805s
Finally, I have the latest adb/fastboot from the latest android SDK (for linux). As I mentioned, I also tried it under Windows with the included adb/fastboot with no differences.
Thanks for you help!

Turbo4V said:
This is actually a recovery for the HAM7, not the Honor6/P7. Recovery_h60.img is just what the recovery was initially called (check the thread http://forum.xda-developers.com/mat...custom-recovery-tool-mt7-l10-l10-mt7-t3022424). I got the CWM file from that thread.
I've also tried the updated version posted in the same thread (MT7_CWM_CN_EN.img) with the same results.
sudo ./fastboot flash recovery MT7_CWM_CN_EN.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.800s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.805s
Finally, I have the latest adb/fastboot from the latest android SDK (for linux). As I mentioned, I also tried it under Windows with the included adb/fastboot with no differences.
Thanks for you help!
Click to expand...
Click to collapse
jeezz
download thiiis alright ? and REPORT success ! To ME
https://www.sendspace.com/file/u5jkys

Simona Simmy said:
jeezz
download thiiis alright ? and REPORT success ! To ME
https://www.sendspace.com/file/u5jkys
Click to expand...
Click to collapse
I just tried flashing your file, and get the same result:
sudo ./fastboot flash recovery MATE7_CWM.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Just for grins, I compared your file to the one that I was flashing before, and they are identical.
diff -s MATE7_CWM.img MT7_CWM_CN_EN.img
Files MATE7_CWM.img and MT7_CWM_CN_EN.img are identical
Any more ideas?
Thanks!
Jsutin

Turbo4V said:
I just tried flashing your file, and get the same result:
sudo ./fastboot flash recovery MATE7_CWM.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Just for grins, I compared your file to the one that I was flashing before, and they are identical.
diff -s MATE7_CWM.img MT7_CWM_CN_EN.img
Files MATE7_CWM.img and MT7_CWM_CN_EN.img are identical
Any more ideas?
Thanks!
Jsutin
Click to expand...
Click to collapse
U still want idea ?? u have NOT get it already?? where did u purchased it from ?? and u already thinking WHY someone got rid of it ??
Does the phone normally working ???
Did u install huawei latest drivers?

Simona Simmy said:
U still want idea ?? u have NOT get it already?? where did u purchased it from ?? and u already thinking WHY someone got rid of it ??
Does the phone normally working ???
Did u install huawei latest drivers?
Click to expand...
Click to collapse
Purchased from Swappa, device works perfectly besides not being able to flash recovery.
I've been able to put the stock Huawei firmware on an SD card and flash that. (127)
I suppose you could be correct, maybe there's something wrong with the device, but that seems unlikely given that everything else works. One thing I'm thinking is that the phone is not actually unlocked (even though it says it is on the recovery screen). Wish I could get an unlock code for this thing to try re-locking and unlocking it.
Thanks for your help.

Turbo4V said:
Purchased from Swappa, device works perfectly besides not being able to flash recovery.
I've been able to put the stock Huawei firmware on an SD card and flash that. (127)
I suppose you could be correct, maybe there's something wrong with the device, but that seems unlikely given that everything else works. One thing I'm thinking is that the phone is not actually unlocked (even though it says it is on the recovery screen). Wish I could get an unlock code for this thing to try re-locking and unlocking it.
Thanks for your help.
Click to expand...
Click to collapse
I posted already procedure how to unlock phone..
U need tools for it ..
But now am going to bed.. so check out mine threads or posts .. it is here..

Simona Simmy said:
I posted already procedure how to unlock phone..
U need tools for it ..
But now am going to bed.. so check out mine threads or posts .. it is here..
Click to expand...
Click to collapse
Thanks, I've tried using the tools, and the code generated ends up not working on the Huawei web site. (See attached). Additionally, I've tried requesting the code from Huawei, and they say that unlocking is not available for the L09
From Huawei:
Huawei Dear user:
Hello, Thank you for using Huawei's products. MT7-L09 is currently not supported by the application unlock code if you want to brush Root or third-party systems, you can go online to search to see if there is a corresponding method. After the phone Root, though not affect the warranty, but if it is due to appear Root performance was a result of failure or system problems may affect your warranty love machine, specifically whether the warranty is to be detected by the service network, then you careful consideration! THX!
Huawei Customer Service Center
Thanks again for your help, just wanted others to see the process incase they were encountering similar problems.
Justin

Turbo4V said:
Thanks, I've tried using the tools, and the code generated ends up not working on the Huawei web site. (See attached). Additionally, I've tried requesting the code from Huawei, and they say that unlocking is not available for
Click to expand...
Click to collapse
You can try Y300-100 or something like or try to relock

Simona Simmy said:
You can try Y300-100 or something like or try to relock
Click to expand...
Click to collapse
Tried that one too (and a few other models), same message.
Thanks,
Justin

Turbo4V said:
Tried that one too (and a few other models), same message.
Thanks,
Justin
Click to expand...
Click to collapse
only one thing ..
get vroot : http://forum.xda-developers.com/showthread.php?t=2434453
root it ...
download flashy : https://play.google.com/store/apps/details?id=com.cgollner.flashify
flash super su (first copy it into your sc card)
delete vroot ..
download install su :https://play.google.com/store/apps/details?id=eu.chainfire.supersu

Simona Simmy said:
You can try Y300-100 or something like or try to relock
Click to expand...
Click to collapse
Thanks again for the ideas, but that root method looks a bit sketchy (malware etc). I guess I'll just leave things 'as-is' for now, hopefully I'll be able to figure out the whole lock/relock thing one day!
Justin

Turbo4V said:
Thanks again for the ideas, but that root method looks a bit sketchy (malware etc). I guess I'll just leave things 'as-is' for now, hopefully I'll be able to figure out the whole lock/relock thing one day!
Justin
Click to expand...
Click to collapse
doont worry .. just root it .. i had it and all was ok . .u will have it just for 5-10 mins.. by that time nothing will happen.
forgot to mention.. after installing flashy flash recovery (CWM) that flashy provides download and flash..
then after installing CWM go there and flash super su

Have the same problem and my Mate7 TL7-09 also has unlocked bootloader (verified with fastboot oem getinfo-bootloader) just cannot get CWM to flash.

djpharoah said:
Have the same problem and my Mate7 TL7-09 also has unlocked bootloader (verified with fastboot oem getinfo-bootloader) just cannot get CWM to flash.
Click to expand...
Click to collapse
Here.... the same problem

Use FLASHIFY that's how I bounce back and forth with recoveries.

Turbo4V said:
I just tried flashing your file, and get the same result:
sudo ./fastboot flash recovery MATE7_CWM.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Just for grins, I compared your file to the one that I was flashing before, and they are identical.
diff -s MATE7_CWM.img MT7_CWM_CN_EN.img
Files MATE7_CWM.img and MT7_CWM_CN_EN.img are identical
Any more ideas?
Thanks!
Jsutin
Click to expand...
Click to collapse
Sounds like your boot loader is still locked or has be relocked again. That's the error you get when boot loader is locked and fast boot can't flash to the partition. Hence the "remote failure" error you're getting.
---------- Post added at 01:38 PM ---------- Previous post was at 01:34 PM ----------
Simona Simmy said:
doont worry .. just root it .. i had it and all was ok . .u will have it just for 5-10 mins.. by that time nothing will happen.
forgot to mention.. after installing flashy flash recovery (CWM) that flashy provides download and flash..
then after installing CWM go there and flash super su
Click to expand...
Click to collapse
Regardless how long you think you may have "vroot" on tour device , there's no telling what type of malware will remain hidden on it. Or what its communicating back to where ever

OnePlus 6 No OS No TWRP, stuck on fastboot screen

Hello,
I'm a young user of a OP6, I did root it well, installed TWRP but everything ****ed up when I did erase everything w/ TWRP.
My situation now: No OS, no TWRP, stuck on fastboot mode.
What I've tried:
1- Flashing TWRP.img again, getting this error code :
C:\WINDOWS\system32>fastboot flash recovery "D:\Users\Documents\Rooter\twrp-3.2.3-1-enchilada.img"
target reported max download size of 536870912 bytes
sending 'recovery' (28728 KB)...
OKAY [ 0.618s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.624s
2- Tried to write it on boot_b (fastboot flash boot_b twrp-3.2.3-1-enchilada.img)
Works but while booting getting :
C:\WINDOWS\system32>fastboot boot "D:\Users\Documents\Rooter\twrp-3.2.3-1-enchilada.img"
downloading 'boot.img'...
OKAY [ 0.620s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.641s
3- Same steps with OP6 OS, same problems
I'm stuck and begging for help (french/english) and not a simple redirect.
I can't access to adb devices and neither to /sdcard/ .
Thanks a lot for your advices to save my phone
Reyz

Reyzhia said:
Hello, I'm a young user of a OP6,.........
Click to expand...
Click to collapse
I don't have this device but, I believe that one or more of the following threads should be helpful for what you are looking for that's specific to your device. Don't be afraid to ask for some member guidance within one of them too.
https://forum.xda-developers.com/showthread.php?t=3851802
https://forum.xda-developers.com/showthread.php?t=3828416
https://forum.xda-developers.com/showthread.php?t=3792643
https://forum.xda-developers.com/showthread.php?t=3796051
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.

Ibuprophen said:
I don't have this device but, I believe that one ..
Click to expand...
Click to collapse
Thanks you much for your reply, I did set my slot on A and i m now trying to reboot normally (it s taking long but wil wait 1/2 h), I dont really know if I should flash TWRP..
Reyzz

Reyzhia said:
Thanks you much for your reply, I did set my slot on A and i m now trying to reboot normally (it s taking long but wil wait 1/2 h), I dont really know if I should flash TWRP..
Reyzz
Click to expand...
Click to collapse
Closing thread, my phone is alright now
Thanks for helping <3
Reyz

Reyzhia said:
Closing thread, my phone is alright now
Thanks for helping <3
Reyz
Click to expand...
Click to collapse
Hey how do u solve it? i have the same problem as you,
Thanks,
Best Regards,
Haikal Rahman

xxhyekal said:
Hey how do u solve it? i have the same problem as you,
Thanks,
Best Regards,
Haikal Rahman
Click to expand...
Click to collapse
I hope you've solved the problem by now, but if not, you can use fastboot to load twrp directly by typing
fastboot boot twrp.img
(replace twrp.img with the actual filename).
Once twrp loads, you can sideload or use adb push to transfer the twrp.img file to the phone and install it from twrp.

You don't flash the twrp.img file ... instead boot twrp.img temporarily .... 'fasboot boot twrp.img' ... then you can flash the zip file in TWRP

Go to this post to unbrick your device
https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Good luck