Related
I've found only one instance of this so far in the development forum by user malickie but they seem to have just returned the phone and I don't believe it's unfixable.
It all started by my trying to update while retaining root without flashing a stock 2.3.5. I tried the "three lines of code method", editing from within the phone using either FX or ES explorer (one initially wouldn't paste back into /system/bin after I made a backup on the sd card).
When I tried to update it got as far as the recovery image, the android with the folder and arrow, and eventually crashed telling me I had invalid this and that; CDROM, SYSTEM, WEBTOP. Sorry, I don't remember the specifics. I shut it down and it bootlooped as far as the AT&T logo droplet thing.
I launched into forum scrounging mode, got RSD Lite 5.6, the FXZ, the update.zip, and flashed back to 2.3.5. The first time I shut down after this it bootlooped again. So I flashed it again, so far so good, so I figured I'd go ahead and update to 2.3.6. More bad luck as it tells me "insufficient memory please factory reset". I try this, and it goes into fastboot telling me "Invalid CG (cg: recovery)".
So, I've been scrounging all day trying to figure out if this issue has been solved to no avail Does anyone have any suggestions?
ri4naire said:
I've found only one instance of this so far in the development forum by user malickie but they seem to have just returned the phone and I don't believe it's unfixable.
It all started by my trying to update while retaining root without flashing a stock 2.3.5. I tried the "three lines of code method", editing from within the phone using either FX or ES explorer (one initially wouldn't paste back into /system/bin after I made a backup on the sd card).
When I tried to update it got as far as the recovery image, the android with the folder and arrow, and eventually crashed telling me I had invalid this and that; CDROM, SYSTEM, WEBTOP. Sorry, I don't remember the specifics. I shut it down and it bootlooped as far as the AT&T logo droplet thing.
I launched into forum scrounging mode, got RSD Lite 5.6, the FXZ, the update.zip, and flashed back to 2.3.5. The first time I shut down after this it bootlooped again. So I flashed it again, so far so good, so I figured I'd go ahead and update to 2.3.6. More bad luck as it tells me "insufficient memory please factory reset". I try this, and it goes into fastboot telling me "Invalid CG (cg: recovery)".
So, I've been scrounging all day trying to figure out if this issue has been solved to no avail Does anyone have any suggestions?
Click to expand...
Click to collapse
I hate to say it, but it sounds like you might have a bad phone.
But you can try using the beginner thread and use the directions there to flash the fxz, but try unzipping the fxz and then go into RSD lite and click on the "..." button, and then select the xml file and start flashing.
If that does not work, there is another way, but you have to be VERY careful, because this can hard-brick your phone.
Last ditch, but ONLY if the others don't work, do this:
Make sure your have the android sdk installed:
http://developer.android.com/sdk/index.html
Then go grab this, and put in the same directory as the SDK installed to, under platform-tools:
http://forum.xda-developers.com/attachment.php?attachmentid=890596
Then open a command line in the directory that you saved and unzipped the fxz in, then;
put your phone in fastboot mode, connect the USB cable, and:
Code:
[FONT=monospace]
[/FONT]fastboot erase userdata
fastboot erase cache
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash preinstall preinstall.img
fastboot reboot
No guarantees this will work
The first two work fine, returning "OKAY". However, if I try any type of flashing from the cmd prompt I get a "FAILED".
Code:
C:\*\InlineFlashing_etc>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.355s]
finished. total time: 0.356s
C:***>fastboot erase cache
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.020s
C:***>fastboot flash system system.img
sending 'system' (491264 KB)...
OKAY [ 17.982s]
writing 'system'...
(bootloader) Preflash validation failure
FAILED (remote: )
finished. total time: 18.212s
I realize we have a locked bootloader so is there a step I might have missed? I flashed back the updated fxz (that's now 18 steps instead of 20, and PS. this renders me with a functional phone, just not one that can update) and luckily I can seem to get back to at least this state consistently.
Ok, so I tried rooting in this state and used the ADB method from the Beginners' Guide to attempt to retain root through the update. This time there was nothing about insufficient memory, it just downloaded the update and then tried to reboot for the install but instead of going to unzip the package it goes straight back to fastboot flash mode with another failure.
Code:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.65
Battery OK
OK to Program
Connect USB
Data Cable
On the bright side it's not taunting me with invalid partitions but then again it won't boot normally either. I'm stuck on this screen.
Try pulling the battery and then booting into boot selection mode. (Press+hold volume buttons, then power button) and select "normal boot".
If that doesn't work then flash the fxz... again.
Did you do manual or one-click root?
Sent from my MB865 using Tapatalk
Ok, I had to plug it in overnight, making sure not to press the power button because it would go into "AP Fastboot", because my battery ran low. I'm flashing the updated FXZ again right now.
I've only ever done the One-Click Root. The first time I tried to retain root, what started all this, was using only the phone. This last time I used the ADB method and it didn't demand I factory reset.
Interestingly, when I tried that factory reset that's when it told me my recovery image wasn't good. I've noticed that the FXZ doesn't flash recovery.img but it does flash system, boot, and preinstall. So, is it possible I could manipulate that file to perform the steps you, Jim, suggested? I should just need to create an MD5 sum and follow the template of the rest of the time, right?
Hello!
So, this is my first post here at XDA, so bear with me if my question has already been answered somewhere else. If so, pretty please point me to it and I'd be forever grateful, 'cause I really have searched for it without really getting somewhere. Of course, that might because I'm a real beginner at this and just cannot patch the bits and pieces of info together properly.
Background to problem
I have a TF300TG. I have unlocked the bootloader via official channels, and flashed CWM 5.5.0.4. Then I flashed CM9 stable, and got stuck in a bootloop. This was solved by a wiping of cache/dalvik and maybe a factory reset (don't really remember). Anyway, i managed to boot is, and realized that i could no use the 3G functions. Stupid i know, should have read more about it, but I finally realized that there are almost no custom ROMs for the 3G version of this transformer. So, what I now wanted to do was flash to something that would work.
I've read that it's only stock or the Hydroponic roms that are available for the TG-version, so I chose to try the Hydro. However, I read somewhere that I should use TWRP instead of CWM to flash, due to some kernel update-thingies, that CWM would not be able to do. If I understand it correctly, I needed to update the kernel back to the stock kernel, since I came from a cyanogenmod with a different kernel (?).
Flashing TWRP via fastboot was easy, and then I flashed the hydro TG rom from TWRP, which gave me bootloops again. Now I could not solve the bootloops via wiping cache or factory resets, nothing solved them. I tried reflashing several times, and also tried flashing after reverting to CWM again. This flash also worked, but I still got the bootloops.
Where I'm at at the moment
I have tried to flash the stock ROMs from Asus, both 9.4.4.40 and 9.4.4.28. However, they do not flash at all from recovery. I get a Status 7 error no matter if I use CWM or TWRP. And yes, i have extracted the downloaded .zip once, before flashing.
I have tried the fastboot -i 0x0b05 update update.zip command, but only get this:
Code:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Extracting the blob from the .zip and using fastboot -i 0x0b05 flash system blob does not work either, and outputs the following in the cmd prompt
Code:
D:\Mobil\Android\TF300TG\roms>fastboot -i 0x0b05 flash system blob
sending 'system' (796653 KB)...
OKAY [140.798s]
writing 'system'...
FAILED (remote: ()
finished. total time: 141.204s
and the following on the tab
Code:
[COLOR="Red"]Failed to process command flash: system error(0x170003)[/COLOR]
I have wiped system, cache, data etc from fastboot, so the pad is pretty much clean from everything except recovery partition. Maybe there's somehing wrong with the partitions, 'cause when I try to format them - system for example - i get the following:
Code:
D:\Mobil\Android\TF300TG\roms>fastboot -i 0x0b05 format system
formatting 'system' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.005s
My questions are these:
How do I flash back to stock, with a stock kernel, if the above things have not worked? Is there a way to flash via ADB that could work, instead of recovery or fastboot?
What's the deal with sometimes flashing the .zip files, sometimes .blob files, and sometimes .img files? I'm confused.
What does the status 7 error mean? Don't really get it from what I've found in my searches.
Can i somehow use the /staging partition to install? If so, how do I push the file there, and which file exacly should I use?
If anyone has any suggestions, I'd be forever grateful. And remember, I'm not an experienced android tinkerer, I have only a Desire HD with CWM and CM7 since before, which was done pretty much by following step-by-step guides and not much understanding from my side. ;P
If you need more info, just let me know.
Cheers!
Niklas
Update:
I managed to flash the hydro rom via CWM. It is still stuck on the Nexus 7-like bootanimation, though. Can't understand why it does not boot all the way into the OS. Ideas?
Update 2
I followed the tip here., and it seems to work. I managed to flash the non-3G version of the hydro rom, and could boot into the OS. Then id somehow worked to flash the 3G version, without any wipes. This time it said "updating android" and then booted! It does not recognize the SIM card, though, but I'm getting more confident that I will be able to fix this now.
So, I have been able to update to the Hydro rom, and can use the tablet, but since 3G is not working in those ROMs, I want to revertto stock ICS. However, I still get the Status 7 error when trying to flash the stock zip from Asus siste. Have tried .40 and .28 WW SKU, none of which is working. Cannot flash the roms in either TWRP, CWM or via fastboot.
Does anyone know what the problem could be? Can it be that the files are not really base roms, but only meant as updates to previous installs? If so, where can I get a base stock ROM?
Nah the work as full recoveries. What boot loader version do u have?
You can reflash stock kernel, by flashing stock ROM through fast boot.
naelme said:
Nah the work as full recoveries. What boot loader version do u have?
You can reflash stock kernel, by flashing stock ROM through fast boot.
Click to expand...
Click to collapse
Hey, thanks for answering. Where do I see the bootloader version? Kernel version is 2.6.39.4-00003-gafee6c5 [email protected] #1
I tried flashing the stock rom via fastboot, using the blob inside the update package
Code:
fastboot -i 0x0b05 flash system blob
I've also tried flashing the ZIP in CWM and TWRP, and I have unzipped the downloaded zip one time as the instructions say.
When you load in recovery mode it tells you boot loader 9.1 or 10.4
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Ah, OK. It says bootloader (2.10 e) released by "WW-epad-9.4.4.40-20120704" A03.
I would try to load jb..
Just visiting the threads with the custom Roms for this device makes my device brick...
I'm sure you can bring it back, another thing you can do is let the battery in the unit fully die then try.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
naelme said:
I would try to load jb..
Just visiting the threads with the custom Roms for this device makes my device brick...
I'm sure you can bring it back, another thing you can do is let the battery in the unit fully die then try.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
OK, then I just have to wait patiently for Asus to release JB for the TG-version. Had hoped to be able to solve it beforehand, but hopefully that will finally solve it for good.
Thank you for your time.
hello
after this
Extracting the blob from the .zip and using fastboot -i 0x0b05 flash system blob does not work either, and outputs the following in the cmd prompt
Code:
D:\Mobil\Android\TF300TG\roms>fastboot -i 0x0b05 flash system blob
sending 'system' (796653 KB)...
OKAY [140.798s]
writing 'system'...
FAILED (remote: ()
finished. total time: 141.204s
and the following on the tab
Code:
Failed to process command flash: system error(0x170003)
=> that the error arrive sometime ... try to do one again and that pass, i have the same error and on the second test i have the success
see link here => http://forum.xda-developers.com/showthread.php?t=1750861
that ok if you dont have go on JB update before ....
hakkukakt said:
hello
after this
Extracting the blob from the .zip and using fastboot -i 0x0b05 flash system blob does not work either, and outputs the following in the cmd prompt
Code:
D:\Mobil\Android\TF300TG\roms>fastboot -i 0x0b05 flash system blob
sending 'system' (796653 KB)...
OKAY [140.798s]
writing 'system'...
FAILED (remote: ()
finished. total time: 141.204s
and the following on the tab
Code:
Failed to process command flash: system error(0x170003)
=> that the error arrive sometime ... try to do one again and that pass, i have the same error and on the second test i have the success
see link here => http://forum.xda-developers.com/showthread.php?t=1750861
that ok if you dont have go on JB update before ....
Click to expand...
Click to collapse
too many details, none of which I was looking for
but here's my questions/recommendations
1. Are you on ICS? If yes what version of TWRP did you install there's 1 for ICS and 1 for JB
I recommend making sure you've installed TWRP for ICS and use TWRP to flash the official ICS firmware from the asus website
once everything is confirmed working then install Hydro for ICS TF300TG
2. If you're on JB. Unfortunately there is currently no going back to ICS. Also the Hydro JB Rom to my knowledge currently does not suport TF300TG, and I'm not aware of any ROM for TF300TG that is running JB
I recommend making sure the correct version of TWRP is install then, use it to flash the official ASUS ROM
hello
yes i'm on ICS
1. i use CWM
hum that's not me that have problem
i answered on the last post ...
sorry for my bad english, i speak normaly in french
Hi nikwid,
thanks for the detailed description!
Here's my story: my TF300TG is on stock 9.4.4.22, and I can't update to stock 9.4.4.28 nor 9.4.4.40. It's working normally, except the ugly screen flicker in the left lower corner and WIFI reconnect delays. The latest ASUS update promises to fix these issues, that's why I really would love to flash it.
History
Unlocked device
Flashed Root + CWM
Everything went flawless up to this point. The TF300TG is still on stock ASUS system.
Current situation
When flashing with CWM and TWRP I get:
Code:
Finding update package...
Opening update package...
Installing update...
script aborted (no error message)E:Error in /sdcard/WW_epad-user-9.4.4.40.zip
(Status 7)
Installation aborted.
fastboot outputs (no matter if flashing to system or staging):
Code:
writing 'system'...
FAILED (remote: ()
finished. total time: 142.102s
I don't dare to try `format` with fastboot, as I don't want to brick the Transformer.
I would be happy for any hint how to successfully update from stock to stock?
See you,
Berny
I seem to be stuck in the same situation.
I cannot install "WW_epad-user-9.4.4.40.zip" from within TWRP2 (2.6, 2.5 and 2.4 tried) and I cannot do "fastboot" as I get the same error messages as the others reported here.
This thread is old, but maybe today someone knows the answers?
I successfully installed WW_epad-user-10.4.3.9.zip by editing META-INF/com/google/android/updater-script in the zip and removing everything except the line
Code:
assert(package_extract_file("blob", "/tmp/blob"), write_raw_image("/tmp/blob", "staging"),delete("/tmp/blob"));
Later on I installed the other two packages (SAM_6260_ALL.fls and TF300TL_AMSS.MRP) one by one.
After this I successfully installed WW_epad-user-10.6.2.3.zip by just removing all "show_progress" and "set_progress" lines in the updater-script.
Finally the original WW_epad-user-10.6.2.6.zip installed without editing it (TWRP 2.5.0.0).
Now I can even check for new updates using the tablet, this didn't work since installing root and CWM
HTH!
Berny
gaga-man said:
I successfully installed WW_epad-user-10.4.3.9.zip by editing META-INF/com/google/android/updater-script in the zip and removing everything except the line
Code:
assert(package_extract_file("blob", "/tmp/blob"), write_raw_image("/tmp/blob", "staging"),delete("/tmp/blob"));
Later on I installed the other two packages (SAM_6260_ALL.fls and TF300TL_AMSS.MRP) one by one.
After this I successfully installed WW_epad-user-10.6.2.3.zip by just removing all "show_progress" and "set_progress" lines in the updater-script.
Finally the original WW_epad-user-10.6.2.6.zip installed without editing it (TWRP 2.5.0.0).
Now I can even check for new updates using the tablet, this didn't work since installing root and CWM
HTH!
Berny
Click to expand...
Click to collapse
By the way, I think that deleting all lines in "META-INF/com/google/android/updater-script" except the following one
Code:
assert(package_extract_file("blob", "/tmp/blob"), write_raw_image("/tmp/blob", "staging"),delete("/tmp/blob"));
will do the same as extracting the "blob" file and flashing it with
Code:
fastboot flash staging blob
---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------
forcemaker said:
I seem to be stuck in the same situation.
I cannot install "WW_epad-user-9.4.4.40.zip" from within TWRP2 (2.6, 2.5 and 2.4 tried) and I cannot do "fastboot" as I get the same error messages as the others reported here.
This thread is old, but maybe today someone knows the answers?
Click to expand...
Click to collapse
Current status: I can install an Asus Stock ROM by extracting the blob file and flashing that with
Code:
fastboot flash staging blob
The fastboot command never reports finishing (in this situation), so I stop it by pressing Ctrl+C in the console window, but only after giving it enough time, e.g. 10 minutes, to finish.
Code:
sending 'staging' (800933 KB)...
OKAY [135.726s]
[COLOR=Red]writing 'staging'...[/COLOR] [I](here it stays forever)[/I]
From this moment on no fastboot commands (e.g. "fastboot --reboot") are accepted until I manually reboot by pressing the "Power" button for 10-11 seconds . During reboot there will be a progress bar underneath the ASUS logo, which moves to completion within 10 minutes. After that the system reboots and the clean Stock ROM is installed.
I tried this on my TF300TG by
resetting it by "full wipe",
then via nvflash to an Android 4.0 Bootloader (if you are on a 4.0 Bootloader, go here: http://forum.xda-developers.com/showthread.php?t=1894867 !!!)
and with the latest Asus Stock ROM
4.0.3 (TF300TG: WW_epad-user-9.4.4.40.zip) and
4.2.1 (TF300TG: WW_epad-user-10.6.2.6.zip).
for TF300T (without 3G) there are different Asus ROM version numbers, you can find them here: http://forum.xda-developers.com/showthread.php?t=1697227
Remember, going to Asus Stock ROM 10.6.*.* will give you Bootloader for Android 4.1 and 4.2 which are not downgradeble to 4.0 unless you already have the nvflash backup files created with 4.0.
I figured it out! =D I ran around searching and found an SBF for the 4G LTE. It is 4.0.4 and worked like a beauty. I have re-uploaded the SBF with RSDlite in the file as well. You can find that here.
To revert to stock just...
1. install RSDlite
2. Flash the file provided in the zip
3. Reboot into fastboot mode and re-unlock (I don't know if that is mandatory, did it anyway)
4. Reboot into fasboot mode and re-flash recovery (Again, I don't know if that is mandatory, did it anyway)
5. Reboot and it should boot Stock ICS just fine!
So, i have noted a increased number of threads about people who have soft-bricked their phones downgrading from 4.4.4 GPE after recieving the OTA, since it includes a new partition table and there's no firmware image yet.
Worry not, i have found a solution for your problem. This method only let's you use custom ROMs (sadly), but it's meant to be a temporal solution while we wait for a 4.4.4 GPE image anyways.
So, without further ado, here's my fix:
You will need:
-The good ol' Android SDK
http://developer.android.com/sdk/index.html#download
-Motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
-A custom recovery. I recommend TWRP, since is the only one i have tested.
Official TWRP Images for Moto G: http://techerrata.com/file/twrp2/xt1032/openrecovery-twrp-2.7.1.1-xt1032.img
-The gpt.bin from 4.4.4 (this is the partition table)
I extracted it from the OTA file and uploaded to my Dropbox: https://dl.dropboxusercontent.com/u/82658555/gpt.bin
-A custom ROM of your choice (obligatory) + GApps (optional)
What to do:
Once you have the Android SDK, decompress the folder sdk/platform-tools in a place of your choice.
Inside this folder, put gpt.bin, the custom recovery image and the ROM and GApps zip's.
Start your phone on fastboot. Connect it.
Inside your decompressed platform-tools folder, hold shift and right click inside the folder. Select "Open command window here".
Make sure your phone is properly connected by typing "fastboot devices" (without the quotation marks). The command prompt should show your phone serial number.
Now we start the real deal. Fist of all, flash gpt.bin using this command:
fastboot flash partition gpt.bin
Make sure it ends on "OKAY"
Now, flash the recovery
fastboot flash recovery nameoftherecoveryfile.img
Once this is done, enter recovery using the fastboot menu on your phone (use Vol- to highlight "Recovery", and then press Vol+)
Now your phone should boot on recovery mode. If you recieve an error like "Can't mount /system/", don't worry, this is normal (there's no system partiton yet, after all). Now you can use ADB command with your PC. Once again, to be sure everything is connected properly,tyipe on the console:
adb devices
Once that is done, it's time to give your phone the custom ROM, so you can flash it. Type (or copy/paste)
adb push NameoftheROMfile.zip /sdcard/ NameoftheROMfile.zip
If you have GApps, do the same for those
adb push GApps.zip /sdcard/ GApps.zip
Now you can finally disconnect your phone from the PC! You are almost done, select "Install" in your recovery, and flash your ROM zip, then the GApps if you have them.
Once it's done, you can reboot to system.
And you will have a working Moto G again!!
Enjoy it, and don't brick it again
the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file
maurocds said:
the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file
Click to expand...
Click to collapse
From my experience, you don't have to enter sideload mode in recovery to push a file, sideload mode is for pushing OTAs. And remember, the ADB push command requires you to put the exact name of the file to transfer twice, that could have failed for you.
You can't use fastboot devices on recovery because you can only use ADB commands in recovery, you were supposed to use "adb devices".
Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.
masa86 said:
Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.
Click to expand...
Click to collapse
Not many people do NAND backups these days.
Sad, because they're really useful, and there wouldn't be as many "HALP BRICKED PHONE" threads.
It Doesn't work only say failed xD
Fresroqir said:
It Doesn't work only say failed xD
Click to expand...
Click to collapse
Care to explain what failed?
tatazeuz said:
Care to explain what failed?
Click to expand...
Click to collapse
The install for the custom rom and gapps
Fresroqir said:
The install for the custom rom and gapps
Click to expand...
Click to collapse
What error did you receive? Did you flashed gpt.bin correctly?
tatazeuz said:
What error did you receive? Did you flashed gpt.bin correctly?
Click to expand...
Click to collapse
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)
Fresroqir said:
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)
Click to expand...
Click to collapse
got.bin is the partition table of the Moto G. Its the file that indicates to the phone the size, name and number of partitions it should have.
So, I know TWRP said in red letters Failed, but I'm interested what is the specific error, what did it said on the command prompt of TWRP.
Error flashing zip sdcard pa falconzip
and then there comes this updating partitution details and do i need to put the rom twice in the cmd?
and do i need a cutom rom with 4.4.4????????
yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading
Fresroqir said:
and do i need a cutom rom with 4.4.4????????
Click to expand...
Click to collapse
maurocds said:
yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading
Click to expand...
Click to collapse
I used the latest version of PA + Stock GApps
Thanks!
Edit: Nope... Still same problem. Looks like the gpt file flashed but everything else is the same.
It still doesn't work for me i got th whole time failed and i don't know what i need to do ;(
It says: Z:\New folder\Android>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.025s]
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.372s]
finished. total time: 0.399s
is that good?
EDIT:it looks that sideload works and not that push command
EDIT: nvm i am stuck at bootanimation
EDIT: this wont work it says failed all the time at twrp
I'm kind of confused. Why couldn't people downgrade and go back to stock by reflashing all of the files from an older stock image, including the motoboot and gpt? I would think this would work...although with people saying that they are unable to downgrade I'm not willing to try upgrading to 4.4.4 myself.
What errors are people seeing if they try to flash gpt and motoboot from, say, 4.4.2 stock or 4.4.2 GPE?
-- Nathan
not work for me..
every recovery stay on black screen and return vibration on touch screen
:/
help > http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
i think this fix doesn't work because i can only sideload my roms and gapps xD
Hey guys,
I was using a NXT-TL00 with Android 7.0 and EMUI 5.0 and I wanted to change to a international ROM with Nougat and EMUI 5.
My current situation:
I unlocked the bootloader.
I can boot into fastboot and flash twrp-3.0.2-0-next.img
I can boot into that TWRP and flash MATE8-TL00-EMUI5.0_B577.zip. (Thanks again, paulcl!)
I can boot into that ROM and use it.
I changed my oeminfo and custom.bin from TL00 to L29 via SRKToolHuawei. Afterwards I had to unlock the bootloader again.
I tried to:
extract various update.zip (update.app inside of the zip) via HuaweiUpdateExtractor_0.9.9.5.
flash the extracted boot.img, recovery.img, system.img via fastboot manually and SRKToolHuawei.
wipe and format data, dalvik, cache, system in- and excluding reboots in every possible variation.
use different TWRP versions.
However:
I can't boot into stock recovery (even after flashing it).
I can't boot into eRecovery.
I can't flash any update.zip oder other ROM besides the one above. Why?
Using eRecovery or stock recovery won't work since I can't boot into it.
TWRP would print this error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
mountencrypt: failed to mount /data: No such file or directory
Removing unneeded files...
Patching system files...
Removing empty directorys...
Unpacking new files...
add link typ file...
write radio image...
check_write_data_to_partition, write data error
E:unknown command [errno]
update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NXT-TL00C01B575/update.zip'
I can't flash any system.img via fastboot. I would get this error:
fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (452422 KB)...
OKAY [ 13.007s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 13.045s
What I want:
A fully working TWRP so I can simple flash an update.zip
A working (stock?) L29 ROM with Android 7 or 6 and Emui 5 or 4 and preinstalled GAPPS.
A working stock recovery and erecovery
OTA support
the possibility to lock bootloader when everything else is working
What might help:
A ROM which won't touch the data partition so I can install it trough TWRP.
Maybe there is a way to put the system.img into a flashable zip-file so I can flash the partition via TWRP so there won't be the error message from fastboot. Unfortunately, I have no idea how to do that. An TWRP doesn't allow to flash system.img directly.
BTW:
My current model number is: NXT-L29
My current build number is: "NRD90M test keys"
EMUI-Version 5.0, Android Version 7.0
Thanks for reading through my text. It would be great if there is someone to help me out here!
hello i have the EXACT same problem except i was on a l29C at the beginning..
i m stuck here 2 days now
if somebody have a solution i greatly appreciated
Install stock kernel and the use hisuite
asphaltkiller said:
hello i have the EXACT same problem except i was on a l29C at the beginning..
i m stuck here 2 days now
if somebody have a solution i greatly appreciated
Click to expand...
Click to collapse
I already found a solution which is not perfect yet. First, I tried to follow the instructions from
How to install NXT-L29C432B560 (Official) Stock Firmware. (Guide with download links) by sillanwali.
Very helpful for me was post #49. I recommend to read through the first post and then coming back and follow the instructions below.
First, you need:
TWRP 3.0.3 (...3 is for Nougat)
this update.zip
MATE8-TL00-EMUI5.0_B577.zip
The procedure might be too long with redundant steps, but it worked for me. So give it a try:
Unlock bootloader
Flash twrp via fastboot(3.0.3 is for Nougat)
fastboot flash recovery twrp-3.03.img
fastboot reboot
Boot into TWRP
Copy update.zip and MATE8-TL00-EMUI5.0_B577.zip to SD.
Wipe>format Data>yes
Wipe>Advance wipe >data, dalvik, cache, system
Install this update.zip linked above.
Try to reboot into system. Mine didn't boot into system, but stock recovery and erecovery are now installed. Go on!
Flash TWRP again (since it's overwritten by stock recovery. No worries - you now can now easily flash back stock recovery).
Boot into TWRP.
Copy MATE8-TL00-EMUI5.0_B577.zip to SD Card.
Again, do a full wipe.
Install MATE8-TL00-EMUI5.0_B577.zip.
Reboot into system. It now should work, however it's the Chinese version.
Extract the update.zip and copy update.app to a new created DLOAD folder on the SD Card.
Do a factory reset.
Flash the stock recovery via fastboot (or TWRP). You will get the image by extracting recovery.img of update.app with HuaweiUpdateExtractor.
Reboot into recovery to install the update.app (automatically).
Now you should be on NXT-L29C432B560.
If you want to use the update_data_full_hw_eu.zip or SuperSu follow the instructions in the How-to-install guide.
To be clear, I still have a few problems:
erecovery would boot but when I am trying to restore via wifi I will get the error: "getting package info failed"
Bluetooth and NFC are not working.
Maybe someone has a solution for that?
sebastjon said:
Bluetooth and NFC are not working.
Click to expand...
Click to collapse
Make the installation again!