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] XT925 partition error?

My Xt925 has "Encrytion Unsuccessful" when I boot up. I have tried to flash a recovery img but all I get is this message.
C:\Documents and Settings\Admin\Desktop\Fastbootxt925\Fastboot>fastboot flash re covery twrp-hdrecovery.img
sending 'recovery' (6678 KB)... OKAY [ 0.844s]
writing 'recovery'...
INFOFailed to erase partition INFOFailed to flash partition recovery
FAILED (remote failure) finished. total time: 1.000s
Click to expand...
Click to collapse
Motorola XT925
Android 4.2
AF Fastboot flasmode (s)
10.9B (Sha-5b608bc, 2012-12-20 16:55:20)
eMMC info: size 16gb
Device is unlocked, status code: 3
Its Bricked isn't it?
I have tried getting some help so I hope someone reads this..

"Partition signed?"
is0lde said:
My Xt925 has "Encrytion Unsuccessful" when I boot up. I have tried to flash a recovery img but all I get is this message.
Motorola XT925
Android 4.2
AF Fastboot flasmode (s)
10.9B (Sha-5b608bc, 2012-12-20 16:55:20)
eMMC info: size 16gb
Device is unlocked, status code: 3
Its Bricked isn't it?
I have tried getting some help so I hope someone reads this..
Click to expand...
Click to collapse
I have also tried reflashing rom using RSD Lite, and get a the Following error
Failed flashing process. 2/22 Flash parition "partition signed" -> Phone returned FAIL.
Click to expand...
Click to collapse

is0lde said:
I have also tried reflashing rom using RSD Lite, and get a the Following error
Click to expand...
Click to collapse
Delete the partition signed line from the Xml and try flashing again!!!!
Al the best!!!!
Sent from my C6802 using Tapatalk

Same problem
Hey man, having the same problem, excluded the line (actually many), and it installed 14. Now the reboot is in process and nothing happens.
kumeipark said:
Delete the partition signed line from the Xml and try flashing again!!!!
Al the best!!!!
Sent from my C6802 using Tapatalk
Click to expand...
Click to collapse

mari18cf said:
Hey man, having the same problem, excluded the line (actually many), and it installed 14. Now the reboot is in process and nothing happens.
Click to expand...
Click to collapse
flash the partition file with "Mfastboot", then re-flash the stock file with only the partition, tz, and getvar(you may not have this) removed.

[Q] Can't flash recovery - FAILED (remote: image update error)

When I try flash a recovery image using the command prompt I receive the following error:
fastboot flash recovery recovery.img
sending 'recovery' (8956 KB)...
OKAY [ 1.105s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.355s
How to resolve error?

Akio8 said:
When I try flash a recovery image using the command prompt I receive the following error:
fastboot flash recovery recovery.img
sending 'recovery' (8956 KB)...
OKAY [ 1.105s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.355s
How to resolve error?
Click to expand...
Click to collapse
Have you successfully unlocked the bootloader ?
Which recovery image are you trying to flash ?

htc_one_mini_m4 said:
Have you successfully unlocked the bootloader ?
Which recovery image are you trying to flash ?
Click to expand...
Click to collapse
Yes the bootloader is unlocked. I'm trying to flash philz-touch-6.26.1-m4.img

Akio8 said:
Yes the bootloader is unlocked. I'm trying to flash philz-touch-6.26.1-m4.img
Click to expand...
Click to collapse
Can you try flashing TWRP 2.7.1.1 instead ? ( Just to see if it's a general issue or something related to your image file )

htc_one_mini_m4 said:
Can you try flashing TWRP 2.7.1.1 instead ? ( Just to see if it's a general issue or something related to your image file )
Click to expand...
Click to collapse
It's a general issue it doesn't matter what image I try to flash

Akio8 said:
It's a general issue it doesn't matter what image I try to flash
Click to expand...
Click to collapse
So, you're stuck with the stock recovery or with a custom one ?
I'd try to install an unsecured kernel + ROM like Jmz's and try flashing a new recovery after that.
Not sure if it would work, just my thoughts and gut says that it might

Root: Stuck at "Your device is booting now"

Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!

if you have the boot backup then restore it.

venugopalu007 said:
if you have the boot backup then restore it.
Click to expand...
Click to collapse
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.

if you cannot find the boot.img
just do a rollback bro
here is the link
first dload this
http://download-c.huawei.com/download/downloadCenter?downloadId=94070&version=376169&siteCode=de-h
and this now
if your device is BLN-L21C432B151 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v84712/f1/full/update.zip
or BLN-L21C185B131 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v75593/f1/full/update.zip

I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img

Stinks said:
I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img
Click to expand...
Click to collapse
The guide from "cyberkey.in/how-to-root-honor-6x-100-working/" is simply wrong when it comes to flashing the twrp recovery. If you really followed this guide completely then you flashed the recovery to the boot partition.
Use "fastboot flash recovery twrp.img" to flash the recovery.
You will still have to flash the boot image to your boot partition then (fastboot flash boot boot.img).

Stinks said:
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.
Click to expand...
Click to collapse
Use fastboot flash recovery twrpname.img to flash the recovery

Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.

V
Stinks said:
Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.
Click to expand...
Click to collapse
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.

venugopalu007 said:
V
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.
Click to expand...
Click to collapse
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?

Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
Bro y this ,just do a rollback .

Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
I recommend you to download firmware files only from the official honor website or by using the huawei firmware finder(https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146)
In this case try to use huawei firmware finder to get the right stock version for your phone. Download these two files: e.g. update.zip & update_full_BLN-L21_hw_eu.zip.
Export the following image files: recovery, system, boot and cust.
The try to flash them:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
If flashing a partition via fastboot fails then it is usually because it's the wrong image or just not made for your phone.

Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.

Stinks said:
Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.
Click to expand...
Click to collapse
Glad you revived your phone

question
​
Stinks said:
Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!
Click to expand...
Click to collapse
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.

[email protected] said:
question
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.
Click to expand...
Click to collapse
did you solve your issue.....I have same problem now

nokiasatyam said:
did you solve your issue.....I have same problem now
Click to expand...
Click to collapse
Hello, could you be more specific about your problem? I'll be able to help you.
Brief Explanation:
From the screen on which you're stuck, press and hold power button for about 10 seconds to forcibly restart your device. when you see the same screen again, immediately press and hold volume up button(for about 3 seconds) to boot to eRecovery.
> Choose shut down option on eRecovery. press and hold vol down button and insert the charging cable to boot to fastboot.
> Press and hold power and volume up button to boot to recovery. (You could do this even from fastboot screen and the screen you're stuck at).