Related
I believe I'm bricked, and when I installed the moto stock .img and tried to flash them, I get an <unknown error> in command prompt. Please help me! can anyone give me some step by step instructions for a fix? thanks!
This may be a dumb question but I need to ask, are you using adb and can you get into fastboot?
Sent from my Xoom using Tapatalk
This is how I unbricked my xoom it will take you back to stock 3.0, then you will have to wait for the over the air updates before you can root again. Any questions, please ask. I have bricked my xoom a few times. Lol.
tabletroms.com/forums/xoom-general-discussion/1268-how-unbrick-your-moto-xoom.html
Sent from my Xoom using Tapatalk
johnny0911 said:
This may be a dumb question but I need to ask, are you using adb and can you get into fastboot?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Yes I'm using adb, and yes, I'm in fastboot.
you must be in bootloader for fastboot commands(adb reboot bootloader)
put 4 stock .img files in platform-tools or tools(from where you are running fastboot)
that should do it.
needless to say your your bootloader must be unlocked for fastboot commands.
.................
the commands are given at motodev website.
rohit3192 said:
you must be in bootloader for fastboot commands(adb reboot bootloader)
put 4 stock .img files in platform-tools or tools(from where you are running fastboot)
that should do it.
needless to say your your bootloader must be unlocked for fastboot commands.
.................
the commands are given at motodev website.
Click to expand...
Click to collapse
I am in Fastboot protocol support. I try flashing the 4 stock .img in platform-tools, and I get errors.
C:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.253s
C:\AndroidSDK\platform-tools>fastboot flash system system.img
sending 'system' (262144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
See, it isn't working. any advice! I really hope I didn't pay $700 for a paper weight!!
I also get the OK, then it fails and says this...
C:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 0.727s]
writing 'boot'...
FAILED (status read failed (Too many links))
finished. total time: 1.319s
C:\AndroidSDK\platform-tools>fastboot flash system system.img
sending 'system' (262144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
C:\AndroidSDK\platform-tools>fastboot flash userdata userdata.img
I expect that you have copied all contents of "tools" folder to platform-tools folder.
Your bootloader must be unlocked to accept commands.
check the result of fastboot oem unlock.
Second : when xoom is not in bootloader mode type adb devices and check whether serial no of xoom is displayed.
Also recheck that you have java dev kit.
You may uninstall and then reinstall android sdk.
More than that I can not think of problem.
May be someone else.
rohit3192 said:
I expect that you have copied all contents of "tools" folder to platform-tools folder.
Your bootloader must be unlocked to accept commands.
check the result of fastboot oem unlock.
Second : when xoom is not in bootloader mode type adb devices and check whether serial no of xoom is displayed.
Also recheck that you have java dev kit.
You may uninstall and then reinstall android sdk.
More than that I can not think of problem.
May be someone else.
Click to expand...
Click to collapse
I have copied all of "tools" into platform tools. However, I cannot check adb devices, because I cannot leave the "Dual Core technology" screen. It's stuck on that. I cannot even enter recovery mode! I will attempt to reinstal java dev kit, and android SDK. And I will post my reply on how that works. Thanks for your patience with me. I'm just quite frustrated nothing has worked so far...
V0nice said:
I have copied all of "tools" into platform tools. However, I cannot check adb devices, because I cannot leave the "Dual Core technology" screen. It's stuck on that. I cannot even enter recovery mode! I will attempt to reinstal java dev kit, and android SDK. And I will post my reply on how that works. Thanks for your patience with me. I'm just quite frustrated nothing has worked so far...
Click to expand...
Click to collapse
I'm in the same boat as you, and with no good help. I'm getting the same answers, although my errors are a bit different than yours. If you somehow find an answer, PLEASE let me know.
hocplyr98 said:
I'm in the same boat as you, and with no good help. I'm getting the same answers, although my errors are a bit different than yours. If you somehow find an answer, PLEASE let me know.
Click to expand...
Click to collapse
Got it to work. I Google'd my issue, and I came up with a few possible issues. 1 being the usb cable, and the other being the usb port. Mine was a stock cable, so that wasn't the issue. But when I plugged the usb cable into the back of my pc (directly to the motherboards usb's) it worked, and I did not encounter the "command write failed"! successfully flashed the boot and system... ect img. and now my xoom is working!
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.
I executed fastboot -i 0x2A96 oem unlock before flashing. I also checked fastboot getvar unlocked so result is following.
>fastboot getvar unlocked
unlocked:
finished. total time: 0.002s*
And one more thing when I flashed cache , userdata , recovery , boot. It is all fine, there is no error. But this error occurs only when i tried to flash system. My Phone was stopped working due some decryption error and internal memory is showing as 0Mb in TWRP. I had followed my threads but no luck.
>fastboot -i 0x2A96 flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.018s]
sending sparse 'system' 1/4 (261218 KB)...
OKAY [ 8.737s]
writing 'system' 1/4...
**FAILED (remote: flash write failure)**
finished. total time: 9.167s
Might be Because Of Corrupted Data Partion.
atulsam said:
I executed fastboot -i 0x2A96 oem unlock before flashing. I also checked fastboot getvar unlocked so result is following.
>fastboot getvar unlocked
unlocked:
finished. total time: 0.002s*
And one more thing when I flashed cache , userdata , recovery , boot. It is all fine, there is no error. But this error occurs only when i tried to flash system. My Phone was stopped working due some decryption error and internal memory is showing as 0Mb in TWRP. I had followed my threads but no luck.
>fastboot -i 0x2A96 flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.018s]
sending sparse 'system' 1/4 (261218 KB)...
OKAY [ 8.737s]
writing 'system' 1/4...
**FAILED (remote: flash write failure)**
finished. total time: 9.167s
Click to expand...
Click to collapse
It Might Possible That Your Data Partition Has Been Corrupted. Download The Official Cynogen OS Zip. Extract it. In That Look For Data. And In same Folder, Press Shift&Right Click in empty Sapce And Open Command window Here. Connect Your Device In Fasboot Mode. Flash That Data Using command. And then Flash System.img by Normal Method. Hope It will Worked For Yu.
Please see the image attached.
Animdk said:
It Might Possible That Your Data Partition Has Been Corrupted. Download The Official Cynogen OS Zip. Extract it. In That Look For Data. And In same Folder, Press Shift&Right Click in empty Sapce And Open Command window Here. Connect Your Device In Fasboot Mode. Flash That Data Using command. And then Flash System.img by Normal Method. Hope It will Worked For Yu.
Click to expand...
Click to collapse
Please see the following image attached which is shared on drive.
Code:
https://drive.google.com/file/d/0B8Dudx72Yu9iamFLUzZOY1Y1TjQ/view?usp=sharing
atulsam said:
Please see the following image attached which is shared on drive.
Code:
https://drive.google.com/file/d/0B8Dudx72Yu9iamFLUzZOY1Y1TjQ/view?usp=sharing
Click to expand...
Click to collapse
Try Out My Method It Should Be Work.
And rather than Using Original USB Cabel, Use Good Original cabel. Sometimes Original USB Become Loose.
It may not be USB problem.
Animdk said:
Try Out My Method It Should Be Work.
And rather than Using Original USB Cabel, Use Good Original cabel. Sometimes Original USB Become Loose.
Click to expand...
Click to collapse
I am using amazon basics cable , this is not usb problem because data is flashing properly but system is not. And Internal memory showing as 0 Mb in TWRP, but SdCard is showing as it is.
I downloaded official tool kit and OS . I tried with two different img but result is same for both.
atulsam said:
I am using amazon basics cable , this is not usb problem because data is flashing properly but system is not. And Internal memory showing as 0 Mb in TWRP, but SdCard is showing as it is.
I downloaded official tool kit and OS . I tried with two different img but result is same for both.
Click to expand...
Click to collapse
Do Yu Tried For The Flasing Of Only Data Partition, It Might Fix Your Problem.....Otherwise, Sorry Bro....I don't Have Any Further Knowledge About This....
Animdk said:
Do Yu Tried For The Flasing Of Only Data Partition, It Might Fix Your Problem.....Otherwise, Sorry Bro....I don't Have Any Further Knowledge About This....
Click to expand...
Click to collapse
Yes I have tried that , data is flashing successfully. Since there is no system flashing so cant start my phone.
I am having the exact same problem
how did you resolve the issue
BOTDeveloper said:
I am having the exact same problem
how did you resolve the issue
Click to expand...
Click to collapse
Sorry, I did not solve yet.
How did it happened?? I'm scared if i overcome this. Cuz recently i unbricked my device from dead hardbrick
exact same issue
atulsam said:
Sorry, I did not solve yet.
Click to expand...
Click to collapse
exact same problem here please update here if you abe to fix it.
Same problem.............. Is there no one from this group to help us........... :'(
Same Probelm
Please someone help , if you have resolved the same . TIA
Guys ..ur problem solved ? Post reply
@ Heartstoler1991 - Not yet .. Please help someone ..
Same problem. Please share the solution if anyone solved it.
I found a pretty easy method but it doesn't let me post the link so send a mail to [email protected] and I give you the link!
Edit: it finally let me post it: https://forum.xda-developers.com/yu-yuphoria/help/bricked-t3174710
Good luck mates
Razor10707 said:
I found a pretty easy method but it doesn't let me post the link so send a mail to [email protected] and I give you the link!
Edit: it finally let me post it: https://forum.xda-developers.com/yu-yuphoria/help/bricked-t3174710
Good luck mates
Click to expand...
Click to collapse
Tried this method already.
Doesn't work, it gives the same exact error.
I have same problem
help me any body any solution
Can some one helps me with this:
I think i have unlocked bootloader, i tried to flash twrp but got something wrong:
C:\Users\Lucia\Desktop\Nova pasta>fastboot flash recovery "C:\Users\Lucia\Desktop\Nova pasta\RECOVERY-TWRP-2.8.7.0-D230X_D240X-UPDATED-THEME.img"
sending 'recovery' (12932 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.427s
i am just a biginner, please help me...
Manolovini2000 said:
Can some one helps me with this:
I think i have unlocked bootloader, i tried to flash twrp but got something wrong:
C:\Users\Lucia\Desktop\Nova pasta>fastboot flash recovery "C:\Users\Lucia\Desktop\Nova pasta\RECOVERY-TWRP-2.8.7.0-D230X_D240X-UPDATED-THEME.img"
sending 'recovery' (12932 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.427s
i am just a biginner, please help me...
Click to expand...
Click to collapse
Ok, first be sure that your Bootloader is unlocked, on dialer type:
*#*#7378423#*#* -> Service info -> Configuration -> Rooting status :
Bootloader unlock done
Then download TWRP form here:
https://www.androidfilehost.com/?fid=457095661767112082
To boot into fastboot mode, you should turn the M2 off and connect it to your computer using a USB cable while holding down the Volume Up button with the other end of the USB cable already connected to the computer, the led light should turn into blue.
Flash the TWRP recovery running:
fastboot flash recovery /path/to/the/twrp.img
Thanks bro! But I had already fix this problem. It was some problems with flashtool....
Manolovini2000 said:
Thanks bro! But I had already fix this problem. It was some problems with flashtool....
Click to expand...
Click to collapse
Nice to read that you"ve solved the problem.
Enjoy your M2 !
Manolovini2000 said:
Thanks bro! But I had already fix this problem. It was some problems with flashtool....
Click to expand...
Click to collapse
What problems do you had with Flashtool? because I have the same problem and I don't know how to resolve them
Kelzett said:
What problems do you had with Flashtool? because I have the same problem and I don't know how to resolve them
Click to expand...
Click to collapse
My problem with flashtool was that I couldn't unlock my bootloader, It was some folders and files that made me unable to do it. Try to find on YouTube "Fix bootloader on Flashtool", something like that, probably you will find... It's simple to fix. Hope I have helped.... Sorry about my English!
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