Related
Hi all,
I have a friend's nexus 5, that I try to unbrick. Unfortunally, and after dragging all threads about unlocking via fastboot, I'm still unable to fix his device.
The fact is, I'm able to unlock (fastboot oem unlock) , then when I reboot the bootloader, it's back locked.
I've tried to flash stock bootloader (for both nexus 5 bootloaders (HHZ11k, HHZ10x) but without success
The device is locked on a bootloop Google screen, impossible to access to recovery mode (via fastboot or via vol up + power)
Anybody's got an idea ?
here is a sequence of trying to update bootloader, you can see that I must unlock for allmost each step
Code:
./fastboot oem unlock
...
OKAY [ 2.596s]
finished. total time: 2.596s
./fastboot erase boot
erasing 'boot'...
OKAY [ 0.217s]
finished. total time: 0.217s
./fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.215s]
finished. total time: 0.215s
./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.219s]
finished. total time: 0.219s
./fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.221s]
finished. total time: 0.221s
./fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.493s]
finished. total time: 0.493s
./fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
OKAY [ 0.404s]
finished. total time: 0.691s
./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
./fastboot oem unlock
...
OKAY [ 2.130s]
finished. total time: 2.130s
./fastboot oem unlock
...
OKAY [ 3.665s]
finished. total time: 3.665s
./fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
sending 'radio' (42049 KB)...
OKAY [ 1.514s]
writing 'radio'...
OKAY [ 2.850s]
finished. total time: 4.364s
./fastboot oem unlock
...
OKAY [ 2.999s]
finished. total time: 2.999s
./fastboot -w update image-hammerhead-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ10x
Baseband Version.....: M8974A-1.0.25.0.23
Serial Number........: 02ffc80f08e51d0d
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ10x'.
Update requires 'HHZ11k'.
finished. total time: 0.601s
You need to flash the right bootloader first before the rest can go through
yep, the fact is I can't find anywhere a bootloader to flash for my version (HHZ10x).
The only files I found are those from Google.
I've tried both for same result.
I've find updates from this thread but I can't boot in recovery mode (from fastboot mode or with fastboot boot recovery.img).
Maybe there is a way to flash those files (from above thread) but I've tried with files (like bootloader.aboot.img, bootloader.imgdata.img, bootloader.rpm.img, etc, ...) without success (FAILED (remote: invalid bootloader image))
benoit.bds said:
yep, the fact is I can't find anywhere a bootloader to flash for my version (HHZ10x).
The only files I found are those from Google.
I've tried both for same result.
I've find updates from this thread but I can't boot in recovery mode (from fastboot mode or with
Code:
fastboot boot recovery.img
).
Maybe there is a way to flash those files (from above thread) but I've tried with files (like bootloader.aboot.img, bootloader.imgdata.img, bootloader.rpm.img, etc, ...) without success (
Code:
FAILED (remote: invalid bootloader image)
)
Click to expand...
Click to collapse
Looks like you have corrupted memory and nothing is going to work. Time to rma.
jd1639 said:
Looks like you have corrupted memory and nothing is going to work. Time to rma.
Click to expand...
Click to collapse
i agree.
I don't want to come off as alarmist, but I'm starting to see a worrying trend here. If you look at other threads over the past few days, there have been quite a few people with dying flash chips (myself included). There are a few differences in some of the symptoms, but the most common being that 'fastboot oem unlock / lock' fails to stick. It's like the chip is left in some random state of corruption, and unable to be written to. If I were I betting man, I'd say we can expect to see a flood of these posts in coming days.
I would recommend to anyone with an unlocked bootloader, that you get it locked asap and reset the tamper flag too, just in case this same issue occurs with your phone in future, and you need to RMA it.
To the OP, can you confirm whether the device has been previously unlocked, and whether anything was done to the device leading up to the issue? I'm hoping that if this issue is happening to both locked and unlocked devices that Google / LG will have to take the issue seriously should it become an epidemic.
:crying:
My friend has admitted that his n5 had fallen into water...
He gave it for deoxidation + battery replace, but they didn't manage to boot it more than fastboot mode, so I proposed him to give it a try.
To reply to sir_earl, the device was early bought, stock rom and official OTAs.
Anyway, thank you all for your responses !
Regards
device: VZW motorola droid razr hd xt926 - completely stock, no customizing at all, every update that came to the phone I installed without problem.
About a month ago (~dec 16, 2014 I believe) the phone was lagging and unresponsive so I powered down, restarted, and that is when the problem began. Upon restart the phone got to the red motorola logo and would hang there. holding the power button would power down for a second, then restart.. so I soft reset it to the boot menu where it atleast wasnt heating up drastically. I left it plugged in because there was no way to power down. From there I began researching the xt926 and seeing other people's problems about the phone hanging at boot logo.
I scoured these forums (and numerous others) for problems similar to mine. Since I was able to get into the boot options menu I've tried everything I could find.. rsd lite, rsd flasher, motorola device manager, house of motorola, droid razr utility...
I tried for about 5 days straight and gave up, took it to a local cell repair place and asked what they would do to repair it. They mentioned a few of the things I tried and said that I had went further than they would go. Out of pity (I believe) they gave me an old BB curve which I've been using the last month. I've been shopping around lately for new phones and wanted to give the razr hd one last crack before relenting and getting a new phone (either S5 or HTC one M8).
First question I guess is, is the phone unusable and beyond repair? upon power up, the phone gets to the red motorola logo for about 2 seconds then goes to this presumed fail boot screen.
it lists:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-07-29 03:17:13)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode: USB Connected
Load kernel (boot) failed
Fastboot Reason: Boot Failure
I can restart the phone from here by clicking the power button, it restarts, hits logo screen, then right back here.
I can get to the boot selection screen by holding the volume up button when its restarting.. it'll get to the boot menu and then restart after about 3 seconds of idle time if I dont pick something quickly.. the 5 options at the boot selection are:
Normal Powerup
Recovery
AP Fastboot
Factory
BP Tools
Normal Powerup, Factory, and BP Tools do nothing.. the phone restarts and hits logo screen then boot failure.
AP Fastboot restarts phone and goes to the same boot screen, but instead of the load kernel boot failure stuff it says: Fastboot Reason: Key Pressed. This is the same result as during powerup/restart holding the volume down key.
Recovery restarts, gets to logo screen, then after about 5 seconds gets to the droid dude with the red exclamation triangle over his open chest. From here I can get it into the recovery mode with 5 selections..
reboot system now
apply update from sdcard
apply update from ADB
wipe data/factory reset
wipe cache partition
All of that being said.. do I have any options to get this phone functional?
Your time and effort is greatly appreciated.
Cheers
I'm assuming that you tried the wipe data from recovery option ? And then to be clear did you actually download and install a factory image using RSD?
i would try rsd lite again with all the latest version of the fxz/sbf in case you were using an old one. this thread from @SamuriHL http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083 is the latest for the xt926 make sure you have the moto drivers installed. if you need i can help with teamviwer or hangouts if you want just pm me for details.
as a side note i do not think that your phone is dead just soft bricked.
---------- Post added at 10:21 PM ---------- Previous post was at 10:14 PM ----------
randymancanstand said:
device: VZW motorola droid razr hd xt926 - completely stock, no customizing at all, every update that came to the phone I installed without problem.
Cheers
Click to expand...
Click to collapse
__
I appreciate the input, sorry for the delay in my response.
I'm assuming that you tried the wipe data from recovery option ? And then to be clear did you actually download and install a factory image using RSD?
Click to expand...
Click to collapse
yes, I factory wiped and using rsd lite, droid razr utility, rsd flasher I tried many different images.. through different iterations and combinations. When rsd lite had no effect installing the different images I had, I moved onto a different program. I wasnt exactly sure which image the system required.. I went through the following:
VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC.xml
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
VZW_XT926_4.4.2-KDA20.62-10_1FF.xml
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
I am unsure if they are 'factory' images
i would try rsd lite again with all the latest version of the fxz/sbf in case you were using an old one. this thread from @SamuriHL http://forum.xda-developers.com/droi...46-15-t2873083 is the latest for the xt926 make sure you have the moto drivers installed. if you need i can help with teamviwer or hangouts if you want just pm me for details.
as a side note i do not think that your phone is dead just soft bricked.
Click to expand...
Click to collapse
I am glad to hear that the phone may have a chance yet. I will look into the latest image. I have RSD Lite v6.2.4.. could someone remind me of the basic flash process?
connect the phone to my pc
put the phone into fastboot,
load up rsd lite
load up image in rsd lite
????
profit?
Again, thank you for your time.
edit: I also have motorola mobile driver 6.4.0 installed
RSD Lite v6.2.4
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
When i click start it fails and gives status:
Failed flashing process. 1/17 flash partition "gpt.bin" -> Phone returned FAIL.
Am currently trying house of moto..
randymancanstand said:
RSD Lite v6.2.4
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
When i click start it fails and gives status:
Failed flashing process. 1/17 flash partition "gpt.bin" -> Phone returned FAIL.
Am currently trying house of moto..
Click to expand...
Click to collapse
this may sound to simple but are you unziping the sbf/fxz?
billycar11 said:
this may sound to simple but are you unziping the sbf/fxz?
Click to expand...
Click to collapse
yes definitely
okay maybe your partitions are messed up then i have seen @bweN diorD help people with that before so he may be able to help.
randymancanstand said:
yes definitely
Click to expand...
Click to collapse
flash this in fastboot. use the data wipe batch file.
if the phone doesnt boot fully to the setup screen within 10min after flashing, its likely toast.
edit,
on second thought, dont close the prompt until you see if it boots up or not. if not, copy all the text from inside the prompt and post it here for me to look at.
thanks
The download is going incredibly slow, but when its done I will flash it and report back.
Thanks for the direction
randymancanstand said:
The download is going incredibly slow, but when its done I will flash it and report back.
Thanks for the direction
Click to expand...
Click to collapse
so the download is crawling along.. it has finished prematurely a couple times already. I'll open the .rar and it says its incomplete.
Is this for matt's droid utility? I have a copy of it I got on 12/17/14.. with an fxz labeled:
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_RSD
I'll keep trying the download from the link you provided in the mean time
randymancanstand said:
so the download is crawling along.. it has finished prematurely a couple times already. I'll open the .rar and it says its incomplete.
Is this for matt's droid utility? I have a copy of it I got on 12/17/14.. with an fxz labeled:
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_RSD
I'll keep trying the download from the link you provided in the mean time
Click to expand...
Click to collapse
You need to use the one I just provided.
Not sure what's up with the DL speeds, my account is paid, so that almost never happens.
bweN diorD said:
You need to use the one I just provided.
Not sure what's up with the DL speeds, my account is paid, so that almost never happens.
Click to expand...
Click to collapse
no dice...
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*] Maintained by bweN diorD
[*] Before continuing, ensure your device is in the
[*] "AP Fastboot" mode and connected via USB.
[*] Be VERY aware! This WILL wipe your userdata, including contacts, apps, etc.
[*] I am not responsible if this wipes your internal sdcard, and you should
[*] backup anything worth it to you to your external sdcard and computer before
[*] you choose to continue. You can exit now with the X button on this window.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] This script will also wipe your data (did i mention this will wipe your data
?).
[*] Press any key to continue.
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.340s
sending 'sbl1' (101 KB)...
OKAY [ 0.030s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.160s
sending 'sbl2' (127 KB)...
OKAY [ 0.030s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.160s
sending 'sbl3' (512 KB)...
OKAY [ 0.060s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.350s
sending 'rpm' (140 KB)...
OKAY [ 0.030s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.300s
sending 'tz' (210 KB)...
OKAY [ 0.030s]
writing 'tz'...
Failed to erase partition
Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.300s
sending 'aboot' (256 KB)...
OKAY [ 0.040s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.310s
sending 'modem' (30720 KB)...
OKAY [ 2.400s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.540s
sending 'fsg' (165 KB)...
OKAY [ 0.030s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.160s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.050s
sending 'logo' (854 KB)...
OKAY [ 0.090s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.220s
sending 'boot' (10240 KB)...
OKAY [ 0.810s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.550s
sending 'recovery' (10240 KB)...
OKAY [ 0.822s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.556s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
sending 'system' (30720 KB)...
OKAY [ 2.400s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 4.010s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.053s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.010s
Hit ENTER to return.
Sorry, but throw it in the trash and move on.
I have seen this exact scenario many times, its not fixable.
bweN diorD said:
Sorry, but throw it in the trash and move on.
I have seen this exact scenario many times, its not fixable.
Click to expand...
Click to collapse
I figured as much.. any idea what could bring this on?
Like I said, no modifications to the phone, it was lagging/hanging so I restarted it.. simply would not boot afterward..
Anyway, thanks for your time and effort. Atleast I know for sure it is done with.
Cheers
randymancanstand said:
I figured as much.. any idea what could bring this on?
Like I said, no modifications to the phone, it was lagging/hanging so I restarted it.. simply would not boot afterward..
Anyway, thanks for your time and effort. Atleast I know for sure it is done with.
Cheers
Click to expand...
Click to collapse
no one seems to know whats causing it. some have mods, some dont. the hole device just seems to become write protected for no reason.
I am a inexperienced user I am also slow and need step by step clear instructions.. I have not once ounce of a clue how to use CMD ... ok ..
I got a Moto G X1028 from a friend who said it wasn't booting up..
found out it does boot but only into Fastboot menu..
Normal power up, recovery, and factory all when clicked, make the screen go black,then a light on top of phone blinks 3 times..
Now I have gotten it to seem idk alive, when clicking the 3 choices above sometimes it randomly will ether blink 3 times or give a system failed to verify..
although sometimes when the recovery feature does go through there is a little green android laying down with a red triangle ...
I am trying to see if theres is some hope on restoring this phone through Fastboot..
The Pc recognizes the device as Fastboot falcon S but can't enter it at all ...
I am looking for a more detailed step by step on how, if possible to restore this device ..
I have attempted many tutorials all leaving me bewildered and confused ..
I have on my PC 2 roms I think thats what they are ...
philz_touch_6.57.9-falcon.img and cm-12-20150131-UNOFFICIAL-falcon.zip...
I have installed the minimal ADB and Fastboot software
and the Motorola drivers are installed and recognizes the device as 210.12.41.falcon_cdma.verizon.en.us
So I am hoping someone can help me, understand I am slow and on top of that a newb...
and bring hope that this phone can be restored to working order ..
Note: not sure if this could help it states the device is locked, Status code 0
on screen at the time of posting this is fastboot reason: volume down key pressed
usb connected, cmd: getvar:all
So:
Can this phone be restored?
Will it be a easy task?
Can it be restored if the device is locked?
Yumi Chi said:
I am a inexperienced user I am also slow and need step by step clear instructions.. I have not once ounce of a clue how to use CMD ... ok ..
I got a Moto G X1028 from a friend who said it wasn't booting up..
found out it does boot but only into Fastboot menu..
Normal power up, recovery, and factory all when clicked, make the screen go black,then a light on top of phone blinks 3 times..
Now I have gotten it to seem idk alive, when clicking the 3 choices above sometimes it randomly will ether blink 3 times or give a system failed to verify..
although sometimes when the recovery feature does go through there is a little green android laying down with a red triangle ...
I am trying to see if theres is some hope on restoring this phone through Fastboot..
The Pc recognizes the device as Fastboot falcon S but can't enter it at all ...
I am looking for a more detailed step by step on how, if possible to restore this device ..
I have attempted many tutorials all leaving me bewildered and confused ..
I have on my PC 2 roms I think thats what they are ...
philz_touch_6.57.9-falcon.img and cm-12-20150131-UNOFFICIAL-falcon.zip...
I have installed the minimal ADB and Fastboot software
and the Motorola drivers are installed and recognizes the device as 210.12.41.falcon_cdma.verizon.en.us
So I am hoping someone can help me, understand I am slow and on top of that a newb...
and bring hope that this phone can be restored to working order ..
Note: not sure if this could help it states the device is locked, Status code 0
on screen at the time of posting this is fastboot reason: volume down key pressed
usb connected, cmd: getvar:all
So:
Can this phone be restored?
Will it be a easy task?
Can it be restored if the device is locked?
Click to expand...
Click to collapse
If you have access to fastboot, it is entirely possible that you can manually restore the stock 4.4.4 ROM and recovery that way. I'll have some time in the morning where I can walk you through some steps in detail if you still need it.
a_gert said:
If you have access to fastboot, it is entirely possible that you can manually restore the stock 4.4.4 ROM and recovery that way. I'll have some time in the morning where I can walk you through some steps in detail if you still need it.
Click to expand...
Click to collapse
I would greatly appreciate that ^-^
Yumi Chi said:
I would greatly appreciate that ^-^
Click to expand...
Click to collapse
Alright, let's see what we can do for you! First things first, download the XT1028 4.4.4 stock ROM from here:
http://www.filefactory.com/file/5cg..._4.4.4_KXB21.14-L1.41_42_release-keys.xml.zip
It's big, filefactory is slow, and that's going to take a while, so you can sit back and get up to speed on the rest of things while that is in progress. The next thing you need to do is head over to the following thread and read through the first post. You will be following the process for firmware downloaded in xml.zip format: http://forum.xda-developers.com/showthread.php?t=2542219
It sounds to me like you have done at least a solid portion of the prerequisites for this, but you can run through the list to make sure. You might want to download and install the Motorola drivers (Prerequisite 'a') if you haven't already, and you'll want to get the mfastboot-v2.zip package (Prerequisite 'c'). Once you have everything downloaded and the drivers/adb/fastboot stuff installed, the basic idea here is that we are going to take the original stock firmware piece by piece and manually install it using the phone's fastboot mode. If it works correctly, it will completely replace whatever corrupted ROM and recovery files are on your device presently and may allow you to actually boot up the phone into Android 4.4.4 KitKat at a factory default condition.
Find and locate the place where you installed adb and fastboot. On my own system, I just installed it to "C:\adb" for simplicity. In the folder, you'll see adb.exe, fastboot.exe, etc. Take the mfastboot-v2.zip you downloaded above and extract the contents into the same folder -- you should now also have a "mfastboot.exe" file there, as well. Finally, take the stock firmware zip file you downloaded from the above link and extract this into the same folder (make sure all these files are actually in the same folder as the .exe's, not in some subfolder); it contains a good dozen or so files that we are going to flash onto your phone.
In Windows, if you're in the folder with the above files and you hold down the Shift key and right click somewhere in the folder, you'll have an option from the drop down menu to "Open command window here" which should get you a nice command prompt right where you need to be. Get your phone rebooted into fastboot mode, connect it to your PC, and then we can start running through the commands if everything is working correctly.
On the post I linked above, there is a series of mfastboot commands you will have to enter one by one and confirm that it returns an [OKAY] message afterward. The only variation you should have from the original post is that you need to enter an additional command for sparsechunk4 (make sure you scroll this whole list):
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash system system.img_sparsechunk4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
If everything went well, you should be rebooted into a stock Verizon 4.4.4 ROM. Take your time, let me know if you have any additional questions about the steps or you get stuck, and good luck!
a_gert said:
Alright, let's see what we can do for you! First things first, download the XT1028 4.4.4 stock ROM from here:
http://www.filefactory.com/file/5cg..._4.4.4_KXB21.14-L1.41_42_release-keys.xml.zip
It's big, filefactory is slow, and that's going to take a while, so you can sit back and get up to speed on the rest of things while that is in progress. The next thing you need to do is head over to the following thread and read through the first post. You will be following the process for firmware downloaded in xml.zip format: http://forum.xda-developers.com/showthread.php?t=2542219
It sounds to me like you have done at least a solid portion of the prerequisites for this, but you can run through the list to make sure. You might want to download and install the Motorola drivers (Prerequisite 'a') if you haven't already, and you'll want to get the mfastboot-v2.zip package (Prerequisite 'c'). Once you have everything downloaded and the drivers/adb/fastboot stuff installed, the basic idea here is that we are going to take the original stock firmware piece by piece and manually install it using the phone's fastboot mode. If it works correctly, it will completely replace whatever corrupted ROM and recovery files are on your device presently and may allow you to actually boot up the phone into Android 4.4.4 KitKat at a factory default condition.
Find and locate the place where you installed adb and fastboot. On my own system, I just installed it to "C:\adb" for simplicity. In the folder, you'll see adb.exe, fastboot.exe, etc. Take the mfastboot-v2.zip you downloaded above and extract the contents into the same folder -- you should now also have a "mfastboot.exe" file there, as well. Finally, take the stock firmware zip file you downloaded from the above link and extract this into the same folder (make sure all these files are actually in the same folder as the .exe's, not in some subfolder); it contains a good dozen or so files that we are going to flash onto your phone.
In Windows, if you're in the folder with the above files and you hold down the Shift key and right click somewhere in the folder, you'll have an option from the drop down menu to "Open command window here" which should get you a nice command prompt right where you need to be. Get your phone rebooted into fastboot mode, connect it to your PC, and then we can start running through the commands if everything is working correctly.
On the post I linked above, there is a series of mfastboot commands you will have to enter one by one and confirm that it returns an [OKAY] message afterward. The only variation you should have from the original post is that you need to enter an additional command for sparsechunk4 (make sure you scroll this whole list):
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash system system.img_sparsechunk4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
If everything went well, you should be rebooted into a stock Verizon 4.4.4 ROM. Take your time, let me know if you have any additional questions about the steps or you get stuck, and good luck!
Click to expand...
Click to collapse
This ^ is what I needed simple step by step you sir are amazing ! I have everything downloaded but the rom its still going atm so once that is done ill finish the rest of steps and come back here
Yumi Chi said:
This ^ is what I needed simple step by step you sir are amazing ! I have everything downloaded but the rom its still going atm so once that is done ill finish the rest of steps and come back here
Click to expand...
Click to collapse
Help ...failed
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bi
n
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.036s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.346s]
finished. total time: 0.382s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboo
t.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.156s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.094s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.109s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Yumi Chi said:
Help ...failed
Click to expand...
Click to collapse
Any idea as to the status of the phone before you got it? The bootloader status of 0 means it is still locked and it appears from the versioning you listed that it was on 4.4.4 already, so I'm not sure why you'd be having signature verification issues reflashing 4.4.4. At this point, I am honestly just guessing, but perhaps try reflashing the partition table again (the first command with gpt.bin), then reboot the phone back into fastboot mode and try to do the other commands on a second pass?
a_gert said:
Any idea as to the status of the phone before you got it? The bootloader status of 0 means it is still locked and it appears from the versioning you listed that it was on 4.4.4 already, so I'm not sure why you'd be having signature verification issues reflashing 4.4.4. At this point, I am honestly just guessing, but perhaps try reflashing the partition table again (the first command with gpt.bin), then reboot the phone back into fastboot mode and try to do the other commands on a second pass?
Click to expand...
Click to collapse
the phone has to be off??? it wont turn off while usb connected ok im confused now .....the phone once charged boot only in fast boot she said it did work but she thought the battery was just going no harm was done to the device .. atm the phone is stating hab check failed for system
failed to validate system image
a_gert said:
Any idea as to the status of the phone before you got it? The bootloader status of 0 means it is still locked and it appears from the versioning you listed that it was on 4.4.4 already, so I'm not sure why you'd be having signature verification issues reflashing 4.4.4. At this point, I am honestly just guessing, but perhaps try reflashing the partition table again (the first command with gpt.bin), then reboot the phone back into fastboot mode and try to do the other commands on a second pass?
Click to expand...
Click to collapse
Knowing my friend shes not one for updates she must have what ever update comes with this phone by default
Yumi Chi said:
the phone has to be off??? it wont turn off while usb connected ok im confused now .....the phone once charged boot only in fast boot she said it did work but she thought the battery was just going no harm was done to the device .. atm the phone is stating hab check failed for system
failed to validate system image
Click to expand...
Click to collapse
I was suggesting that after you do the mfastboot command to flash the gpt.bin file (which, from your log appeared to work corrrectly), you could then reboot the phone into fastboot mode (turn it off, turn it back on and get it back into fastboot mode) and then resume from step two. My only theory there was that it may need to actually reformat the partitions before you go back in and start flashing things and that might be why you have the error you do.
Question 30 at: http://forum.xda-developers.com/showthread.php?t=2537119 suggests that if you are failing to flash 4.4.4 at this point, you may be stuck, so I'm just trying to walk through the steps I would try myself in your scenario.
Yumi Chi said:
the phone has to be off??? it wont turn off while usb connected ok im confused now .....the phone once charged boot only in fast boot she said it did work but she thought the battery was just going no harm was done to the device .. atm the phone is stating hab check failed for system
failed to validate system image
Click to expand...
Click to collapse
Trying to find the default that comes with this phone is not my line knowledge ....
looking on a wiki this is some things i found
its a CDMA Version XT1028 for Verizon
I have a feeling it may be this default that comes with it
Operating system Android Jelly Bean 4.3[6] (Upgradable to Android 5.0 Lollipop[7])
my friend never updates her phones .... I think its a 4.3 jellybean any way to check that theory and find a stock rom ?
Yumi Chi said:
my friend never updates her phones .... I think its a 4.3 jellybean any way to check that theory and find a stock rom ?
Click to expand...
Click to collapse
The XT1028 originally shipped with 4.3 Jelly Bean, but it is no longer the stock ROM for this device. The part where you say it was recognized as "210.12.41.falcon_cdma.verizon.en.us" means that the device and bootloader have been updated to 4.4.4 KitKat, as that string would have been different were it still on 4.3 or 4.4.2.
a_gert said:
The XT1028 originally shipped with 4.3 Jelly Bean, but it is no longer the stock ROM for this device. The part where you say it was recognized as "210.12.41.falcon_cdma.verizon.en.us" means that the device and bootloader have been updated to 4.4.4 KitKat, as that string would have been different were it still on 4.3 or 4.4.2.
Click to expand...
Click to collapse
ok ill give it another shot and try reflashing
reformat the partitions how does one do this ?
Yumi Chi said:
ok ill give it another shot and try reflashing
Click to expand...
Click to collapse
Considering the phone in your hand is a Verizon model and the bootloader is locked, Best Buy has this model in stock for $30, just in case it comes to replacing it outright: http://www.bestbuy.com/site/verizon...lack/3041063.p?id=1219086346405&skuId=3041063
each time ive gotten after gpt step one: no valid gpt found
Yumi Chi said:
reformat the partitions how does one do this ?
Click to expand...
Click to collapse
You were doing this when you followed the first mfastboot command that flashed the gpt.bin. Do that again, reboot the phone and go back into fastboot mode, and then resume from the second command on the list. This may or may not work, but it's all I can think to suggest.
a_gert said:
You were doing this when you followed the first mfastboot command that flashed the gpt.bin. Do that again, reboot the phone and go back into fastboot mode, and then resume from the second command on the list. This may or may not work, but it's all I can think to suggest.
Click to expand...
Click to collapse
well the img went through the rest well failed ...
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bi
n
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.035s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.347s]
finished. total time: 0.385s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboo
t.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.123s]
finished. total time: 1.222s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.078s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.344s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.789s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 5.360s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.807s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (254591 KB)...
OKAY [ 13.213s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 27.487s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (245234 KB)...
OKAY [ 12.917s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.143s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (257606 KB)...
OKAY [ 13.315s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.682s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk4
target max-sparse-size: 256MB
sending 'system' (125353 KB)...
OKAY [ 9.052s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.917s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.b
in
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 6.532s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.557s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (712 KB)...
OKAY [ 5.072s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.098s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.983s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot
Yumi Chi said:
well the img went through the rest well failed ...
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bi
n
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.035s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.347s]
finished. total time: 0.385s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboo
t.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.123s]
finished. total time: 1.222s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.078s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.344s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.789s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 5.360s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.807s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (254591 KB)...
OKAY [ 13.213s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 27.487s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (245234 KB)...
OKAY [ 12.917s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.143s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (257606 KB)...
OKAY [ 13.315s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.682s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk4
target max-sparse-size: 256MB
sending 'system' (125353 KB)...
OKAY [ 9.052s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.917s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.b
in
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 6.532s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.557s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (712 KB)...
OKAY [ 5.072s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.098s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.983s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot
Click to expand...
Click to collapse
Whenever something indicates FAILED, you really don't need to keep on with the following steps. What I find odd is that you are succeeding with a couple and then the remaining ones are failing. You can try to reboot after each step that succeeds, perhaps, if that helps.
Hi guys,
I have my friend's Asus Transformer tablet which was never rooted nor modified in any way. One time it went dead and did not boot up. When it finally turned back on, screen was stuck on ASUS logo (please see attachment below).
These were the troubleshooting steps taken:
Reset through the small opening at the side (NO GOOD)
Click Wipe Data at Recovery (NO GOOD)
Tried to flash stock rom through fastboot (NO GOOD)
Firmware used was: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5 Only for JP SKU (Android 4.2)
And the error in fastboot was this:
Code:
C:\adb>fastboot devices
015d15b4f8041c04 fastboot
C:\adb>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.143s]
sending 'system' (800931 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 7.317s
Flashed using Windows 7 OS.
We'd like to know if there would be any chance to revive the tablet or is it time to bid goodbye.
Thank you and more power XDA!
rmcalingasan said:
Hi guys,
I have my friend's Asus Transformer tablet which was never rooted nor modified in any way. One time it went dead and did not boot up. When it finally turned back on, screen was stuck on ASUS logo (please see attachment below).
These were the troubleshooting steps taken:
Reset through the small opening at the side (NO GOOD)
Click Wipe Data at Recovery (NO GOOD)
Tried to flash stock rom through fastboot (NO GOOD)
Firmware used was: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5 Only for JP SKU (Android 4.2)
And the error in fastboot was this:
Code:
C:\adb>fastboot devices
015d15b4f8041c04 fastboot
C:\adb>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.143s]
sending 'system' (800931 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 7.317s
Flashed using Windows 7 OS.
We'd like to know if there would be any chance to revive the tablet or is it time to bid goodbye.
Thank you and more power XDA!
Click to expand...
Click to collapse
Had the same issue. Used Linuxmint and was able to flash image with no issues.
Also had this issue happen to me one day out of the blue, with the exception of not even being able to boot into recovery. I tried everything and ended up giving up as nothing worked. I'm currently waiting for a new motherboard to see if that fixes it.
rmcalingasan said:
Hi guys,
Firmware used was: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5 Only for JP SKU (Android 4.2)
Flashed using Windows 7 OS.
We'd like to know if there would be any chance to revive the tablet or is it time to bid goodbye.
Thank you and more power XDA!
Click to expand...
Click to collapse
...are you sure that the chosen firmware is the right one that fits to your tablet exactly? I suppose it's the wrong one, because I used to take Version WW_V10.6.1.27.5 and was successful to get a clean Stock Rom JB. I also may be wrong.
However I think it's worth to make a further attempt to flash that blob as follows:
Make a folder C:\Flash and copy the .blob from WW_V10.6.1.27.5 into the folder.
Open Minimal ADB and Fastboot and put in "fastboot devices". The device should appear as "xxx device".
Now type in step by step (wait after every step!):
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase misc
fastboot erase cache
After that open C:\Flash and put in "fastboot -i 0x0B05 flash system blob" without " " .
Now it takes a while "sending..." appears then "write..." and the load status will be shown.
If loading is finished put in "fastboot -i 0x0B05 reboot". It takes a while to start into a clean JB 4.2.2!
Please note, I cannot guarantee any success-everything you do is on your own risk. Good luck!
ebonit said:
...are you sure that the chosen firmware is the right one that fits to your tablet exactly? I suppose it's the wrong one, because I used to take Version WW_V10.6.1.27.5 and was successful to get a clean Stock Rom JB. I also may be wrong.
However I think it's worth to make a further attempt to flash that blob as follows:
Make a folder C:\Flash and copy the .blob from WW_V10.6.1.27.5 into the folder.
Open Minimal ADB and Fastboot and put in "fastboot devices". The device should appear as "xxx device".
Now type in step by step (wait after every step!):
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase misc
fastboot erase cache
After that open C:\Flash and put in "fastboot -i 0x0B05 flash system blob" without " " .
Now it takes a while "sending..." appears then "write..." and the load status will be shown.
If loading is finished put in "fastboot -i 0x0B05 reboot". It takes a while to start into a clean JB 4.2.2!
Please note, I cannot guarantee any success-everything you do is on your own risk. Good luck!
Click to expand...
Click to collapse
Thank you for your input. I'm currently trying it in Linux.
Here is the current status:
Code:
fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.074s]
sending 'system' (800931 KB)...
rmcalingasan said:
Thank you for your input. I'm currently trying it in Linux.
Here is the current status:
Code:
fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.074s]
sending 'system' (800931 KB)...
Click to expand...
Click to collapse
It's just stuck at sending 'system'.
I've tried using the sd card method but failed too.
aem2267 said:
Had the same issue. Used Linuxmint and was able to flash image with no issues.
Click to expand...
Click to collapse
Installed Linuxmint too. (Loving the interface!)
But still stuck at sending 'system' at terminal.
rmcalingasan said:
Thank you for your input. I'm currently trying it in Linux.
Here is the current status:
Code:
fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.074s]
sending 'system' (800931 KB)...
Click to expand...
Click to collapse
It's strange. As I wrote "sending..." takes a while then appears "write..." and the load status will be shown. Were you patient enough? Did you ever see the load status? Are you sure it's the right "blob"?
ebonit said:
It's strange. As I wrote "sending..." takes a while then appears "write..." and the load status will be shown. Were you patient enough? Did you ever see the load status? Are you sure it's the right "blob"?
Click to expand...
Click to collapse
Yes, I'm quite sure it's the correct blob. The JP_epad-10.6.1.27.5-20130902 shows at the top of the screen of the tablet.
One thing I noticed when erasing other parts was that it failes erasing other parts:
Code:
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot devices
015d15b4f8041c04 fastboot
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.055s]
finished. total time: 2.055s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.036s]
finished. total time: 0.036s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
FAILED (remote: (Unknown error code))
finished. total time: 0.382s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase boot
erasing 'boot'...
OKAY [ 0.036s]
finished. total time: 0.036s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase misc
erasing 'misc'...
FAILED (remote: (Unknown error code))
finished. total time: 0.038s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: (Unknown error code))
finished. total time: 0.043s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot -i 0x0B05 flash system bloberasing 'system'...
OKAY [ 0.010s]
sending 'system' (800931 KB)...
I'm currently trying to download an older version of JP blob.
rmcalingasan said:
Yes, I'm quite sure it's the correct blob. The JP_epad-10.6.1.27.5-20130902 shows at the top of the screen of the tablet.
One thing I noticed when erasing other parts was that it failes erasing other parts:
Code:
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot devices
015d15b4f8041c04 fastboot
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.055s]
finished. total time: 2.055s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.036s]
finished. total time: 0.036s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
FAILED (remote: (Unknown error code))
finished. total time: 0.382s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase boot
erasing 'boot'...
OKAY [ 0.036s]
finished. total time: 0.036s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase misc
erasing 'misc'...
FAILED (remote: (Unknown error code))
finished. total time: 0.038s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: (Unknown error code))
finished. total time: 0.043s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot -i 0x0B05 flash system bloberasing 'system'...
OKAY [ 0.010s]
sending 'system' (800931 KB)...
I'm currently trying to download an older version of JP blob.
Click to expand...
Click to collapse
Please try the version WW_V10.6.1.27.5. WW stands for world wide. That's what I used to take. http://www.asus.com/Tablets/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/
Once downloaded, you need to head to the path “Settings > About Tablet” where you will have to note down the Build number. If the build number starts with “WW”, your SKU is WW. Similarly, if your build number starts with “US”, you must download the firmware for the US SKU.
EDIT : THIS ERROR ONLY HAPPENS ON WINDOWS. GO TO THE TELEGRAM GROUP IN THE BOTTOM LINK AND INSTALL PIZZAG'S MINT LINUX. AS IT HAS ADB AND FASTBOOT DRIVERS BAKED IN. ROMS FLASH FLAWLESSLY ON LINUX. IF YOU HAVE ANY PROBLEMS CONTACT THE DEVS VIA TELEGRAM.
C\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot flash boot boot.img
1031shadow said:
Sending 'boot_a' (98304 KB) OKAY [ 3.350s]
Writing 'boot_a' OKAY [ 1.409s]
Finished. Total time: 4.808s
ADD HERE fastboot reboot fastboot then it should reboot to twrp fast boot then the super.img will flash correctly
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot flash super super.img
Sending sparse 'super' 1/5 (774340 KB) OKAY [ 26.719s]
Writing 'super' OKAY [ 0.049s]
Sending sparse 'super' 2/5 (784673 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot erase metadata
Erasing 'metadata' OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO
ECHO is on.
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO Device Flashing Should Be Finished
Device Flashing Should Be Finished
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO Device Should Be Rebooting To Android
Device Should Be Rebooting To Android
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO
ECHO is on.
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO PRESS ENTER TO EXIT
PRESS ENTER TO EXIT
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>PAUSE
IF ANYONE HAS AN ERROR LIKE THE ONE ABOVE . WHERE EVERYTHING FLASHES
BUT SUPER.IMG or system a.img
edit the script and make this change
RIGHT CLICK THE SCRIPT THEN EDIT GO TO THE LINE AFTER
FASTBOOT FLASH BOOT BOOT.IMG AND ADD THIS fastboot reboot fastboot IT SHOULD LOOK LIKE THIS:
fastboot flash boot_a boot.img
ECHO
ECHO
fastboot reboot fastboot
ECHO
ECHO
SLEEP 2
fastboot flash system_a system.img
this fixes super.img (no link FAILED (Write to device failed (no link))
and system A.img (FAILED (Write to device failed (no link))
ALSO YOU SHOULD INSTALL SYSTEM WIDE ADB AND DOWNLOAD GOOGLES PLATFORM
(ON WINDOWS AND LINUX IF NOT ALREADY INSTALLED)
TOOLS AFTER INSTALL. GO TO THE ROOT OF YOUR HARD DRIVE IN THE ADB FLODER AND REPLACE THE ALL THE FILES THERE FOR THE ONES IN THE PLATFORM TOOLS YOU DOWNLOADED FROM GOOGLE. IF YOU HAVE A RYZEN CPU DOWNLOAD AND INSTALL THE FIXES FOR FASTBOOT
for system wide adb https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
credit goes to
Snoop05 for system wide adb
The new telegram account has several moto devices unified in one group they also have a chat room where other users and the actual devs will respond to your inquiries or you can message them directly on telegram.
Another thing is windows is trash if you want the best compatibility with the ROM flasher he provides you can install his mint Linux with adb and fastboot installed also has dump and build tool for those who like his ROMs .
the above error only happens in Windows I've tested on Linux and it works without having to edit the script
all credit goes to
A-Team @pizzaG
https://t.me/A_Team_Digital_Solutions
Thank you. !
Much appreciated on the links and detailed info.
1031shadow said:
FOR ANYONE WHO HAS THIS ERROR GO TO THE BOTTOM OF THE PAGE FOR FIX
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot flash boot boot.img
Sending 'boot_a' (98304 KB) OKAY [ 3.350s]
Writing 'boot_a' OKAY [ 1.409s]
Finished. Total time: 4.808s
ADD HERE fastboot reboot fastboot then it should reboot to twrp fast boot then the super.img will flash correctly
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot flash super super.img
Sending sparse 'super' 1/5 (774340 KB) OKAY [ 26.719s]
Writing 'super' OKAY [ 0.049s]
Sending sparse 'super' 2/5 (784673 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot erase metadata
Erasing 'metadata' OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO
ECHO is on.
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO Device Flashing Should Be Finished
Device Flashing Should Be Finished
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO Device Should Be Rebooting To Android
Device Should Be Rebooting To Android
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO
ECHO is on.
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO PRESS ENTER TO EXIT
PRESS ENTER TO EXIT
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>PAUSE
IF ANYONE HAS AN ERROR LIKE THE ONE ABOVE . WHERE EVERYTHING FLASHES
BUT SUPER.IMG or system a.img
edit the script and make this change
RIGHT CLICK THE SCRIPT THEN EDIT GO TO THE LINE AFTER
FASTBOOT FLASH BOOT BOOT.IMG AND ADD THIS fastboot reboot fastboot IT SHOULD LOOK LIKE THIS:
fastboot flash boot_a boot.img
ECHO
ECHO
fastboot reboot fastboot
ECHO
ECHO
SLEEP 2
fastboot flash system_a system.img
this fixes super.img (no link FAILED (Write to device failed (no link))
and system A.img (FAILED (Write to device failed (no link))
i contacted the developer for a fix but no reply so i fixed it myself i love these roms but very little help from the comunity so i did it myself ive been rooting for 12 years now so not a noob but not a dev
ALSO YOU SHOULD INSTALL SYSTEM WIDE ADB AND DOWNLOAD GOOGLES PLATFORM TOOLS AFTER INSTALL. GO TO THE ROOT OF YOUR HARD DRIVE IN THE ADB FLODER AND REPLACE THE ALL THE FILES THERE FOR THE ONES IN THE PLATFORM TOOLS YOU DOWNLOADED FROM GOOGLE. IF YOU HAVE A RYZEN CPU DOWNLOAD AND INSTALL THE FIXES FOR FASTBOOT
for system wide adb https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
credit goes to
Snoop05 for system wide adb
i also wanted to add i really appreciate the developers for this rom for even taking time to develop roms and root for this device i will be posting the links for their telegram to download custom gsi and custom stock roms it was almost impossible to find as of writing
all credit goes to
A-Team @pizzaG https://t.me/ATeamReleases
Click to expand...
Click to collapse
ATeamReleases is not found on Telegram right now.
Your right I'ma edit with new links
403 forbidden
https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/