Hi Everyone,
First I apologize if this isn't the right place to post this, please move it to the correct forum if it's not.
I have a Asus TF700 (running the latest Asus firmware) the, warranty just ran out so I figured it was time to unlock and play with some custom roms.
I got it unlocked using the Asus bootloader tool, I went to install CWM using fastboot and it seemed to go OK but then when I went to reboot the bootloader it failed giving me a write failure. Now when I try to boot up recovery it briefly shows the android guy in working mode then goes to the error with the android laying on his back.
Here is my commands with fastboot:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (6688 KB)...
OKAY [ 2.483s]
writing 'recovery'...
OKAY [ 2.409s]
finished. total time: 4.893s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\adb>adb reboot bootloader
error: device not found
And that's it, I'm a bit stumped not sure how to fix it so I can move onto installing the roms, any help would be greatly appreciated.
Anyone?
DId you install the Google USB driver?
If don't,please install the Android SDK and install all.
packyy said:
DId you install the Google USB driver?
If don't,please install the Android SDK and install all.
Click to expand...
Click to collapse
Yes, if I hadn't then I wouldnt have been able to use fastboot or install CWM.
No one? I thought this was the android super stars forum.
Can someone at lease suggest another forum with people willing to help?
Not a single person willing to help me out? Wow, thanks.
Yesterday afternoon I upgraded my C6802/Z Ultra to 14.4.A.0.108 aka 4.4.4 and to persuade the Sony PC Companion program on windows to download the update, I used flashtool to lock my bootloader.
I've used the phone happily all day but I want to root it so I can use Titanium Backup Root/Pro, and hack the platform.xml file so as to allow full use of the microSDHC card.
I went to the service menu with the *#*#7378423#*#* and it says my bootloader is unlockable. I then put the phone into fastboot mode and ran the unlock sequence, but it failed the first time and reported device already unlocked.
I am using the tools from the full Android SDK
Code:
$ ./fastboot -i 0x0fce getvar version
< waiting for device >
version: 0.5
finished. total time: 0.003s
$ ./fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXXXX
...
FAILED (remote: Command did not succeed)
finished. total time: 0.018s
$ ./fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXXXX
...
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
$ ./fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXXXX
...
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
So then I tried to flash Jackie's 108 Dual Recovery kernel and it failed; I tried again as root just to make sure:
Code:
# ./fastboot flash boot ~/download/android/sony/xperia_z_ultra/C68xx_kernel_108_DualRec_Jackie099.bin
sending 'boot' (17728 KB)...
OKAY [ 0.557s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.560s
I get the same result if I use FlashTool's built-in tools. I have tweaked the phone's configuration to allow/disallow USB ADB debugging, allow/disallow side-loading, verification of apps etc etc, makes no difference.
I suspect that the phone is falsely reporting its bootloader is already unlocked, but where do I go from here?
thanks for any ideas
Paul
first off you may have lost your DRM keys by not doing a TA backup before unlocking the bootloader.
try and flash doomkernel's boot.img and see if that works? (unpack the zip)
I think I can remember someone not beinf able to flash jackie's .bin but doomlord's boot.img worked?
blueether said:
first off you may have lost your DRM keys by not doing a TA backup before unlocking the bootloader.
try and flash doomkernel's boot.img and see if that works? (unpack the zip)
I think I can remember someone not beinf able to flash jackie's .bin but doomlord's boot.img worked?
Click to expand...
Click to collapse
thanks, I'll give the doomkernel a go.
I lost my DRM keys the same day I received my XZU.. what you've never used you don't miss
Looks like the problem that I had:
http://forum.xda-developers.com/xperia-z-ultra/help/reunlocking-bootloader-error-t2808395
Hello all!
In an effort to try and help Boost Mobile users out, I have put together a stock restore guide for the Moto E 2015. There are other versions of a stock firmware guide, but those are for GSM and others not using CDMA. Here you will find steps to restore your Boost Mobile Moto E!
First off, I am NOT responsible for damaging your phone or any user error. USE THIS GUIDE AT YOUR OWN RISK!
If you are here reading this guide, you have either bricked your device or just want to go back to the stock firmware. If you are using a custom recovery such as TWRP, any saved nandroid backups will be lost if saved on internal storage. This will factory load 5.0.2 Lollipop fresh out of the box the day you got your phone!
Firstly, you will need ABD and Fastboot and Motorola Device Manager. You can download Motorola Device Manager directly from here.
I have attached ABD and Fastboot to this post for download.
To use ABD and Fastboot, you will need to make a new folder and extract the zip to the new folder and name it fastboot. From there, you will need to launch a command window from that folder. The easiest way to do this is to to have that folder selected and Shift/right click and "Open command window here". From there, if you have done this right, you will have a command prompt window ready to go!
After you have setup your new folder with ABD and Fastboot, you are ready to load the stock firmware to your Moto E! Download link is here
After you have downloaded your stock firmware, double check to make sure you have XT1526_Updated_SURNIA_BOOST_5.0.2_LXI22.50-14.6_cid9_subsidy-DEFAULT_CFC.xml.zip
Extract the contents of the file you downloaded to the folder where you put your ABD and Fastboot in.
Once you have everything ready to go, power down your phone and put it in bootloader mode. Hold power and volume down for a few seconds and you are there. Attach your USB cable from your PC to the phone and be ready to load several lines of code. Flash these codes in order. Copy and paste if you like in to your command prompt, one line at a time!
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem config carrier
fastboot oem fb_mode_clear
Once you have done this, restart your phone and wait a few minutes for the boot sequence to start. If you have done this right, your phone will be factory fresh with the stock firmware on it!
If I was able to help out, hit thanks! :good:
This is my first guide and I had to look everywhere to find out how to do this for Boost variants, and hopefully it is ok for everyone to use!
EDIT: I updated the download link. Sorry about that.
Will this relock bootloader?
crazynapkinman said:
Will this relock bootloader?
Click to expand...
Click to collapse
No. There are certain steps to relock the bootloader, but it does no good now. You can still OTA with an unlocked bootloader, but as far as factory warranty goes, its void as soon as you unlock it. The only reason you would ever want to relock it is if you were giving the phone to someone who didn't know anything about rooting our phones.... it just doesn't do any good.
Thanks. I may try this, but not until after I flash cyanogen 12. That won't be until they get LTE working on CDMA Boost Mobile variant.
Also, why do you need to have Motorola Device Manager?
crazynapkinman said:
Thanks. I may try this, but not until after I flash cyanogen 12. That won't be until they get LTE working on CDMA Boost Mobile variant.
Also, why do you need to have Motorola Device Manager?
Click to expand...
Click to collapse
Motorola Device Manager installs all the drivers you need for the phone.
Thank you
imprint89 said:
Motorola Device Manager installs all the drivers you need for the phone.
Click to expand...
Click to collapse
Thank you I finally got my Moto e back to stock with twrp and root with SuperSu which Borks my cameras. LOL. The only thing I had to do different I had to use MFastboot and there is a 1 click installer to do it with.
I really appreciate you looking out.
Joe
joex55 said:
Thank you I finally got my Moto e back to stock with twrp and root with SuperSu which Borks my cameras. LOL. The only thing I had to do different I had to use MFastboot and there is a 1 click installer to do it with.
I really appreciate you looking out.
Joe
Click to expand...
Click to collapse
Glad I could help out!
Hey, this forum looks really helpful, but unfortunately the stock firmware zip link isn't working for me. Is there any other place that you might suggest getting it from? I do have two of the same phone if it's possible to retrieve the firmware from another one, but I wiped my first one which is why I'm here in the first place. Thanks!
*EDIT: Hey, no worries, I found another file of the same type, but I can't post the link yet. (Follow the Moto E 2015 thread to general to "| Read Before You Flash | Unlock | Restore | Stock Firmware |," follow the link there, and find the other, newer, XT1526 file.) I just installed the drivers, got the minimal adb/fastboot zip, and followed the commands given above. Thanks for your help, everything is fixed now, even my service is back!
Will you provide the link when you can?
I could use a link as well :|
Sitting ducks until i can flash stock back on.
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
NateAC said:
Hey, this forum looks really helpful, but unfortunately the stock firmware zip link isn't working for me. Is there any other place that you might suggest getting it from? I do have two of the same phone if it's possible to retrieve the firmware from another one, but I wiped my first one which is why I'm here in the first place. Thanks!
*EDIT: Hey, no worries, I found another file of the same type, but I can't post the link yet. (Follow the Moto E 2015 thread to general to "| Read Before You Flash | Unlock | Restore | Stock Firmware |," follow the link there, and find the other, newer, XT1526 file.) I just installed the drivers, got the minimal adb/fastboot zip, and followed the commands given above. Thanks for your help, everything is fixed now, even my service is back!
Click to expand...
Click to collapse
is there any way you could pm me a link to a working xt1526 rom?
Download link is updated.
Does this remove account information and installed apps? Do you have to activate phone with Boost again or no?
Nevermind. I just went for it and the answer is Yes, it removes accounts and installed apps.
And No, you do not have to re-register with Boost Mobile. Full system restore.
Confirm working for Boost Mobile XT1526 CDMA LTE.
Thanks so much for this thread. You're going to save SO many devices!
After flashing this my stock recovery gives me a dead android (on it's back with red triangle) How can I get stock recovery back? Can I flash stick recovery via adb?
Edit: So after further Googling, my understanding is that the red triangle android is supposed to be there... but I've tried all the suggested button presses to get the actual menu to appear. I'm trying to get the menu on the Moto E 2015 CDMA LTE Boost Mobile.
Can someone tell me the actual button combination to get the stock recovery menu to appear?
Edit: OMFG! People are so stupid... I'm going to make my own youtube video and post it for our phones.... All of the guides were wrong!
To enter recovery menu (after android with red triangle is displayed) press and hold power for 3 seconds, then tap the volume up once.
I will post a video on how to do this for moto e 2015 CDMA XT1526. Hope this helps anyone else who was confused/concerned about their stock recovery partition not working after flashing back to pure stock.
Edit: Here's the video of how to access the contextual menu of Recovery on the Moto E 2015 4G LTE CDMA Boost Mobile variant (XT1526)
http://youtu.be/gffx5CN9wF4
Help with Fastboot Errors
There are errors when running some of these commands on my phone the rest of the commands seem to run fine. Hope to resolve or confirm they are simply to be ignored. I would like to confirm all partitions are re-written factory for troubleshooting purposes. Thanks.. These are the only errors...
Windows 8.1
Fastboot download from this post.
Driver Motorola ADB interface v2.0.2.0 - If in question please confirm this or post directly to drivers that I can manually install to know I'm running. The MOTO software install hides everything so I'm just not sure what it's doing exactly.
D:\ADB>fastboot erase D:\ADB\XT1526\modemst1
erasing 'D:\ADB\XT1526\modemst1'...
(bootloader) Invalid partition name D:\ADB\XT1526\modemst1
FAILED (remote failure)
finished. total time: 0.016s
D:\ADB>fastboot erase D:\ADB\XT1526\modemst2
erasing 'D:\ADB\XT1526\modemst2'...
(bootloader) Invalid partition name D:\ADB\XT1526\modemst2
FAILED (remote failure)
finished. total time: 0.000s
D:\ADB>fastboot erase D:\ADB\XT1526\cache
erasing 'D:\ADB\XT1526\cache'...
(bootloader) Invalid partition name D:\ADB\XT1526\cache
FAILED (remote failure)
finished. total time: 0.000s
D:\ADB>fastboot erase D:\ADB\XT1526\userdata
erasing 'D:\ADB\XT1526\userdata'...
(bootloader) Invalid partition name D:\ADB\XT1526\userdata
FAILED (remote failure)
finished. total time: 0.000s
D:\ADB>fastboot oem config D:\ADB\XT1526\carrier
...
(bootloader) Not allowed command
FAILED (remote failure)
finished. total time: 0.016s
Hmmm. I followed this exact guide and it worked flawlessly
deansouth8 said:
There are errors when running some of these commands on my phone the rest of the commands seem to run fine. Hope to resolve or confirm they are simply to be ignored. I would like to confirm all partitions are re-written factory for troubleshooting purposes. Thanks.. These are the only errors...
Windows 8.1
Fastboot download from this post.
Driver Motorola ADB interface v2.0.2.0 - If in question please confirm this or post directly to drivers that I can manually install to know I'm running. The MOTO software install hides everything so I'm just not sure what it's doing exactly.
D:\ADB>fastboot erase D:\ADB\XT1526\modemst1
erasing 'D:\ADB\XT1526\modemst1'...
(bootloader) Invalid partition name D:\ADB\XT1526\modemst1
FAILED (remote failure)
finished. total time: 0.016s
D:\ADB>fastboot erase D:\ADB\XT1526\modemst2
erasing 'D:\ADB\XT1526\modemst2'...
(bootloader) Invalid partition name D:\ADB\XT1526\modemst2
FAILED (remote failure)
finished. total time: 0.000s
D:\ADB>fastboot erase D:\ADB\XT1526\cache
erasing 'D:\ADB\XT1526\cache'...
(bootloader) Invalid partition name D:\ADB\XT1526\cache
FAILED (remote failure)
finished. total time: 0.000s
D:\ADB>fastboot erase D:\ADB\XT1526\userdata
erasing 'D:\ADB\XT1526\userdata'...
(bootloader) Invalid partition name D:\ADB\XT1526\userdata
FAILED (remote failure)
finished. total time: 0.000s
D:\ADB>fastboot oem config D:\ADB\XT1526\carrier
...
(bootloader) Not allowed command
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
You're entering the commands incorrectly. For example, the first command in your example should be "fastboot erase modemst1", not "fastboot erase D:\ADB\XT1526\modemst1". Enter the commands as shown in the first post of this thread.
Brainfart bigtime. Thanks for the catch. I'm going to get the tire pump for a refill.
If you do this after updating to 5.1 ota will the phone still work correctly?
Meaning you will be back to stock recovery, stock system, stock firmware, and Android 5.1 OS?
Question?
imprint89 said:
No. There are certain steps to relock the bootloader, but it does no good now. You can still OTA with an unlocked bootloader, but as far as factory warranty goes, its void as soon as you unlock it. The only reason you would ever want to relock it is if you were giving the phone to someone who didn't know anything about rooting our phones.... it just doesn't do any good.
Click to expand...
Click to collapse
Can i just put the lock bootloader command first,then put the rest of the commands or is this not digitally signed
Help: XT1511 bricked
Hello, my XT1511 has been bricked, had installed CM12.1 and TWRP but the error information to be going to an external hard drive via a laptop with ubuntu mate is present. My terminal only presents the logo of the brand and enter fastboot, have tried to follow the steps but I get errors that you can not write to the device, the debug options and OEM you were disabled so the OEM unlock does not work how I can get my device?
Regards.
Long story short, I tried to flash new rom on my Mt2-L02 mate2 and failed and its bootlooping (at Huawei Ascend screen and keep rebooting) now. using the SDcard udload to load new rom don't work either. I cannot go into recovery, or boot into system.
My phone is bootloader unlocked, so I tried to flash (extract from a rom) boot.img, recovery.img and is ok but when flashing system.img, it stucked in writing 'system'... for long time.... so I tried fastboot erase system -w and get FAILED (remote: Command not allowed)... why is it so? my phone is already unlocked. I tried unlock again and flash the system.img, same problem.
So... I'm screwed?
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
kimtyson said:
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
Click to expand...
Click to collapse
Only have 1 pc, yes, I'm flashing MT2-L02 ROM, tried alot of version but discovered only these version rom (b408, b603, b606, b607) able to write the system.img, original out of box android version for my phone is 4.4.2. but still bootlooping after flashing boot.img, recovery.img and system.img. I think only custom recovery can save now, but there is none for this model... or maybe there is no hope for my phone? Maybe my phone got some system modified lock so that I'm not able to erase using flashboot?
C:\adb>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
C:\adb>fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
If I'm able to erase those, I'm might solved the bootlooping problem..
Try using this thread as reference, http://forum.xda-developers.com/asc...to-fix-soft-bricked-phone-using-twrp-t2886630. It's for a different model so just use your stock ROM in place of the L03 ROM. I'm not sure how to help beyond that. There has to be a way to return to stock on the L02.
Maybe this message is late, pls try following
http://pan.baidu.com/s/1dDpc4eP
http://www.huaweirom.com/rom/mate2/2619.html
usb flash instructions:
http://www.huaweirom.com/guide/2621.html
You may need to use google translate since all the info is in Chinese
Basically they are saying you should use B117 if B4xx not working.
Current status of my phone:
I unlocked my bootloader via @huaweihax method (SLOCK). I couldn't install the 4pda zip thingy that unlocks your bootloader permanently and prevents EMUI 9 from locking your bootloader. Is there any alternatives for that?
I want to install Android 11 on my phone.
My phone is ANE-LX1 (vendor: hw, region: eu).
How can I install LineageOS 18 without losing my unlocked bootloader and my root?
Currently I have EMUI 8 installed with May 2018 security patch.
I have Magisk installed (that app gives me root access).
With the help of ROM Manager I booted into 3.2.1-0 Catuva21 TWRP recovery and finally, I could flash that 4pda zip file! ROM Manager is not neeeded but it makes things easier.
Hmmm, apperantly it was supposed to factory reset my device but I think I selected the wrong thing on my device. I guess what you choose is highlighted in white and not red. Here's the output of fastboot:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock TishSerg_For4pda
...
(bootloader) The device will reboot and do factory reset...
FAILED (status read failed (Unknown error))
finished. total time: 38.370s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock TishSerg_For4pda
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.027s
Should I be worried about this?
If you have flashed theTishSerg_For4pda zip you should be able to do
fastboot oem unlock TishSerg_For4pda
which should give you the warning screen with the red and white yes/no options.
I upgraded from stock 8.0 to stock 9.1 (dload method) and was able to unlock my bootloader again using the same command. I could then flash LOS 17.
Edit: if I remember correctly, I flashed the zip with a TWRP-oreo-smart.img recovery.
An3skmbi said:
If you have flashed theTishSerg_For4pda zip you should be able to do
fastboot oem unlock TishSerg_For4pda
which should give you the warning screen with the red and white yes/no options.
I upgraded from stock 8.0 to stock 9.1 (dload method) and was able to unlock my bootloader again using the same command. I could then flash LOS 17.
Edit: if I remember correctly, I flashed the zip with a TWRP-oreo-smart.img recovery.
Click to expand...
Click to collapse
Thanks!
Yap, I figured this out eventually. If anyone else is looking to do this, follow this!