I installed the KitKat update recently, tried to rsd back to jellybean, and the modem firmware downgraded. Now the phone won't activate because KitKat can't read the earlier firmware. I have the the soak ota downloaded, I just need a method to get the modem firmware back the the soak ota version.
Also, I tried to install the KitKat ota and I get errors about amazon_kindle.apk having unexpected contents since I disabled it
Sent from my XT907
i have to assume you are unlocked because rsd should have failed long before it got to the modems if you were locked.
that being true, you should be able to grab the 9.30.1 fxz from sbf droid devs and use this modified xml file http://www.mediafire.com/view/p217akcxwmijcr7/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC_DOWN.xml to go back to jb and all should be fixed.
if some how im wrong and you are locked do not do what i posted above!!
I am locked, the problem is I don't know how to flash the files in fastboot to get the modem working again, that's my only problem, I know the commands but don't know what specific order the files should be flashed and what partitions / files need to be erased. I may have to wait until the firmware is released on the sbf droid developers site. Also,
we really need the modem file from the kk sbf to ensure its done right. it may be possible to do it now but im not going to guess as to the proper sequence. there are about 2 dozen files in the modem folder. after we get the sbf they will be compressed into one file thats easy to flash.
sorry i cant be of more help.
on a side note, its very odd that rsd only flashed the modems and didnt bork your phone from the files it would have flashed before that. your phone should be bricked right now from trying, you are very lucky indeed.
Your phone is borked at this point from what is currently known after applying the KK OTA to a locked phone.
If you have already applied the OTA and you're locked, you CANNOT downgrade at all. Attempting to do so will result in what you are seeing I believe.
You will now have to wait for the official KK FXZ full image to come out so you can flash that back to your phone and get it back to operational standards. That could be weeks or months. No one knows for sure, but in the past, it usually takes a few weeks after the official OTA is released.
If, however, your phone's bootloader were unlocked, then you could have gone here and gotten yourself back in operation:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
bweN diorD said:
we really need the modem file from the kk sbf to ensure its done right. it may be possible to do it now but im not going to guess as to the proper sequence. there are about 2 dozen files in the modem folder. after we get the sbf they will be compressed into one file thats easy to flash.
sorry i cant be of more help.
on a side note, its very odd that rsd only flashed the modems and didnt bork your phone from the files it would have flashed before that. your phone should be bricked right now from trying, you are very lucky indeed.
Click to expand...
Click to collapse
The sequence is in the updater-script in the 9.30.1.XT926.Verizon.en.US.zip, I just don't know how to apply that specific part of it. I was just looking over it a few minutes ago. and yes, I'm very thankful my phone isn't a paperweight right now, I thought most soak ota's allow you to downgrade, but I was very wrong. Now I can't run the ota again because it fails due to disabled apps returning errors. I guess I'll just have to wait on the firmware which is weeks away. Sigh. At least I have an Razr M running kitkat, so I'm not missing out on much right now.
I think I know of a method, but it requires me erasing the system completely and re-applying it. Does anyone know the fastboot command to erase the OS off my Maxx HD so I can re-install it? I'm missing an argument when I try to erase the system.
Playb3yond said:
I think I know of a method, but it requires me erasing the system completely and re-applying it. Does anyone know the fastboot command to erase the OS off my Maxx HD so I can re-install it? I'm missing an argument when I try to erase the system.
Click to expand...
Click to collapse
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
Also, I can't seem the get the Motorola device manager from my HD to install, when my computer is connected to the internet, it won't run. But when it isn't, it opens. Has anyone else had this issue?
I checked the file version of the setup file and it seems to be moto device helper 4.0.0.0. I was thinking this would help me fix my phone if I could only get it to install
Sent from my XT907 using XDA Free mobile app
Here's the updated version of it https://www.dropbox.com/s/56jrbm1x0rqzkpd/Motorola Device Manager 4.0.0.0.zip
Sent from my XT907 using XDA Free mobile app
I tried flashing the modem manually and it still won't activate. No one could help me get this back in a usable state?
Sent from my XT907 using XDA Free mobile app
Related
I am running CM10.1, and wanted to upgrade to the new nightlies, Upon trying to get into recovery, I cannot use goo manager to installed recovery nor reboot to recovery. I did then try to push TWRP to my device using fastboot, that did not seem to work as any time i rebooted to recovery it would do a normal reboot. I can access fastboot, however when I volume up on "RCK" the following error comes up
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB Download protocol
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000).
I do not know if I have everything loaded into my PC correct, drivers, etc. Anyone who can help would be greatly appreciated.
As i am now I can run CM 10.1 just fine, booting and everything, I just cannot get into recovery to upgrade or change roms.
ffalzone23 said:
I am running CM10.1, and wanted to upgrade to the new nightlies, Upon trying to get into recovery, I cannot use goo manager to installed recovery nor reboot to recovery. I did then try to push TWRP to my device using fastboot, that did not seem to work as any time i rebooted to recovery it would do a normal reboot. I can access fastboot, however when I volume up on "RCK" the following error comes up
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB Download protocol
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000).
I do not know if I have everything loaded into my PC correct, drivers, etc. Anyone who can help would be greatly appreciated.
As i am now I can run CM 10.1 just fine, booting and everything, I just cannot get into recovery to upgrade or change roms.
Click to expand...
Click to collapse
I don't know if this method will work on CM. You can give it a shot and report back.
1. Download the Asus firmware from Asus website and extract it once because there is anotherr zip in it.
2. Copy the second zip file to your root directory on your internal sd and reboot
3. If it works, you should see the notification on the lower right corner and click on it. You just follow the instruction to put your device back to the factory bootloader.
Before you use this method, you need to move all your stuff to your computer as a back up because it will wipe everything that you have on your device..
There is another method that you could try if it does not work.. Good luck..:fingers-crossed:
I tried to download the US Firmware from the ASUS site, put it on the root of the internal, then rebooted. Did not see any notification
What is this other method you speak of....
This isn't a huge deal, if I'm stuck on a RC of CM 10.1 I can deal with it. I just like to be up to date and like to reconfigure my tablets and phones from time to time.
On a side note, isn't rom/recovery etc tasks with this tablet very difficult when compared to other tablets/phones?
ffalzone23 said:
I tried to download the US Firmware from the ASUS site, put it on the root of the internal, then rebooted. Did not see any notification
What is this other method you speak of....
This isn't a huge deal, if I'm stuck on a RC of CM 10.1 I can deal with it. I just like to be up to date and like to reconfigure my tablets and phones from time to time.
On a side note, isn't rom/recovery etc tasks with this tablet very difficult when compared to other tablets/phones?
Click to expand...
Click to collapse
Did you unzip it once? You need to have a different firmware version than the one on your system... I will find the other method and link for you..
Thanks Man. I appreciate the help!
ffalzone23 said:
Thanks Man. I appreciate the help!
Click to expand...
Click to collapse
I am still looking for the link. I forgot what it is called... I will post the link here when I find it..
LetMeKnow, Thanks for the update.
Myp hone is a Droid Razr HD, and I know with that phone its possible through the bootloader to flash stock firmwear, is this possible at all with the Transformer tf700t? It would be great to have a simple tool to aid us in getting back to stock to start from square one!
ffalzone23 said:
LetMeKnow, Thanks for the update.
Myp hone is a Droid Razr HD, and I know with that phone its possible through the bootloader to flash stock firmwear, is this possible at all with the Transformer tf700t? It would be great to have a simple tool to aid us in getting back to stock to start from square one!
Click to expand...
Click to collapse
By reading your post again, let me summarize it here. You know how to use fastboot, can't boot to your custom recovery (TWRP), want to flash stock recovery to fix your problem, and have try a few methods to put the stock back but it did not work. You still can get to your bootloader menu. Can you try to use this command to see if you can access to your custom recovery: fastboot boot-recovery
Good luck and get back to you on the link...
this is what came up in command prompt....
C:\android-sdk\platform-tools>fastboot boot-recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
I then did try below. but when I went to reboot, it just stayed in fastboot, so that leads me to believe there is some error there, either my bootloader is screwy or something related. I appreciate your help. At this point if anything can get me back to stock as bought, I dont care if its older versions of the firmware/bootloader/stock recovery, I'll take it from there.
C:\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery-jb.img
sending 'recovery' (7746 KB)...
OKAY [ 3.606s]
writing 'recovery'...
OKAY [ 2.414s]
finished. total time: 6.022s
C:\android-sdk\platform-tools>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.548s
C:\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
ffalzone23 said:
I then did try below. but when I went to reboot, it just stayed in fastboot, so that leads me to believe there is some error there, either my bootloader is screwy or something related. I appreciate your help. At this point if anything can get me back to stock as bought, I dont care if its older versions of the firmware/bootloader/stock recovery, I'll take it from there.
C:\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery-jb.img
sending 'recovery' (7746 KB)...
OKAY [ 3.606s]
writing 'recovery'...
OKAY [ 2.414s]
finished. total time: 6.022s
C:\android-sdk\platform-tools>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.548s
C:\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
Click to expand...
Click to collapse
I have not seen that before, so I don't know what to say...
When I did fastboot TWRP recovery, I used blob file instead of img file. Do you want to download the blob file and try again?
Edit: What version of TWRP did you fastboot? V2.6.3.0 is larger than our partition on the tf700. Therefore, you can not use it..
The .IMG was cwm recovery. I tried that after trying twrp most recent version. 2.6.3.1 I think.
Sent from my XT926 using xda app-developers app
On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts?
At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try.
ffalzone23 said:
On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts?
At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try.
Click to expand...
Click to collapse
If fastboot doesn't work for you but you have a rooted Android, you can try installing a recovery using the dd method:
Code:
cd wherever/you/downloaded/twrp
su
dd if=openrecovery-twrp-2.6.3.1-tf700t.blob of=/dev/block/mmcblk0p4
then reboot - the bootloader should flash your new recovery with a blue progress bar and reboot again. On the second reboot, hold down volume-down to get to the bootloader menu and try entering RCK again.
ffalzone23 said:
On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts?
At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try.
Click to expand...
Click to collapse
You can try _that method. He always have good advices and know what he is talking about.....:good:
Good luck....
_that. What screen do I have my tablet on when I run the dd command prompt ?
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
ffalzone23 said:
_that. What screen do I have my tablet on when I run the dd command prompt ?
Click to expand...
Click to collapse
You mean the expected output? Something similar to:
Code:
15836+1 records in
15836+1 records out
8108136 bytes (8.1 MB) copied, 0.152395 s, 53.2 MB/s
(the above is from my PC - the TF700 is slower)
Or do you mean where you enter those commands? Either via your PC in an adb shell (in this case you must first transfer the file to the TF700 with adb push or other means), or directly on your tablet with a terminal app under Android (I recommend the one from jackpal, search the Play Store)
I was able to get the same output, however when I rebooted after running the last dd code, it did not do anything, just rebooted as normal.
ffalzone23 said:
I was able to get the same output, however when I rebooted after running the last dd code, it did not do anything, just rebooted as normal.
Click to expand...
Click to collapse
What is the response when you use power and volume down buttons?
It takes me into fastboot or boot loader screen w the rck, android cold boot, and wipe data icons
Phone: Moto X / KitKat 4.4
Carrier: AT&T (XT1058)
Problem: Mysteriously stopped booting.
Good News: Fastboot is recognized.
Bad News: (bootloader) Flash write failure
Taking this guide as my playbook - http://forum.xda-developers.com/moto-x/moto-x-qa/kitkat-update-crashed-moto-x-t2535150 I tried to flash on a stock OS. Here's the main spot from the thread I'm working from-
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
The mission objective is simple: retrieve files off of sdcard and factory reset.
So with my mfastboot (not the android one), I'm trying to flash my stock OS back on so I can get a drive in windows and retrieve sdcard files. Actually, ANY OS back on at this stage of the game will be nice.
Things I have NOT done:
1. rooted the phone, or
2. unlocked the boot loader
If doing these will help, let me know.
So I get my download from sbf.droid-developers.org for 4.4.2 & ATT carrier and unpack the files.
flashing for 'partition' in gpt.bin actually works (yay), but I get the above error ("Flash write failure") for system.img and recovery.img
uh-oh
It seems others with this problem changed cables and USB ports, so I tried that. No dice.
Someone said something about permissions, so I started my command window with administrator privileges, also no luck.
Unless, of course, they meant permissions on the phone side of things? Would that actually help?
So at this juncture if my SDCard died I can go for warranty because I never did any unlocking.
However, if the SDCard can be saved, I am willing to void the warranty and unlock. The data on it is valueable to me and yes a lesson I learned here is I should start using dropbox or equivalent service. Noted.
Should I unlock the phone and try mfastboot flash system system.img, or am I already dead?
Factory reset doesn't even work, I get "no valid piv block in sp for system"
I just ran mfastboot erase cache and at the command prompt I get:
(bootloader) Failed to erase partition
FAILED: Remote failure
The phone screen says, 'Failed to erase partition cache'
This doesn't sound good.... Is there anyway can get this thing booted?
Ah, nevermind, it just keeps getting errors flashing everything. Something with the phone itself is seriously wrong.
I've decided to return it. I think my data is lost.
After a full days of Bootloops, Errors and Stress.. I have finally figured it out!
First i tried Resoring my Moto G back to Retail UK 4.4.2, in order to flash this in the hope i would recive OTA's and 4.4.4. ( i was wrong ).
So, i went ahead a tried restoring back to Retail. using this
I kept getting Errors with System and a few others..
NOTICE: When using the fastboot method to restore/flash firmware, makesure the commands you are typing are correct to the files inside the folder, for instance the final firmware i flash using fastboot what got the captured ota to work was this offical imagewhat can be found HERE
was telling me to use the following command.. "fastboot flash system system.img" but in the firmware folder it was split into 3 sparse chunk parts so you have to type the following 1-3: (i used mfastboot v2) fastboot wouldnt work for me.
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
(I did get a few errors stating 2&3 parts has issues with signitures. Its OKAY)
Also there is no "fastboot flash fsg fsg_gpe.img" in the Offical Firmware (if your outside the US) So just use the one already flashed, it should be okay, the new update has a new one i think because it isn't showing as 3G no more it is showing as H & H+ .
Once you have typed all the commands needed, you should have a working OFFICAL GPE ROM.
HERES WHERE THE UPDATE/SIDELOAD COMES IN!
Note, i didn't find this out myself... credits go to someone else i just noticed it and though hey ill try that, if your that guy Thanks!
Okay when your phone successfully boots. TURN IT OFF BEFORE GOING THROUGH ANY OF THE SETUP... DO NOT EVEN SELECT A LANGUAGE!
Use minimal adb & fasboot, and move the 4.4.4 GPE captured OTA to the folder, It will be located... C:/Program Files/ Minimal adb & fastboot
You need to boot into STOCK recovery it should be installed since you have just flashed stock firmware, enter fastboot and select recovery. you will see a dead droid.. just hold-in both Vol + & - and power for a few secound and release.. it will get you into the menus and select install update via adb
now open the cmd window at the minmal and fastboot where the update had been moved.. and type
adb devices (to see if your phone is working in adb)
adb sideload KOT49H.M004_5-KTU84P.M003_18.zip
it should start sideloading and ... BOOM you have 4.4.4
Now hold Right sift on the folder and right click and select to start cmd window here
Sent from my XT1032 using XDA Free mobile app
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
My tf 700t is stop in a restarting loop until the battery is finished.... i have tried booting into recovery but the logo of the recovery TwRP apear and the tablet restarts itself to that point ,until the battery is dead.
Any sugestions?
the tablet is rooted and i was on KatKiss rom on the moment of the crash for about 5 months.
Try this:
http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my Nexus 5X using Tapatalk
I'm having the exact same issue.
I can occasionally get into the bootloader, but when I try to get into TWRP it will show the logo page and will immediately restarts.
Following the link you sent, I tried the adb devices prompt, but it showed up blank. Do I need to be in TWRP for adb to work? When I try to get into TWRP it just restarts.
Not sure what my options are when the only screen I can get into is the fastboot.
wldtravel26 said:
I'm having the exact same issue.
I can occasionally get into the bootloader, but when I try to get into TWRP it will show the logo page and will immediately restarts.
Following the link you sent, I tried the adb devices prompt, but it showed up blank. Do I need to be in TWRP for adb to work? When I try to get into TWRP it just restarts.
Not sure what my options are when the only screen I can get into is the fastboot.
Click to expand...
Click to collapse
If you can get into fastboot yours is a very different situation. But let me answer your questions first.
The linked method works if you have adb access in TWRP - however briely. Even if TWRP loops you should have adb access at some point (open Device Manager and watch for changes).
If TWRP is just bootlooping very quickly you may be out of luck but I have seen cases where a little window of adb access and careful timing of the commands let people push the file to internal and insmod it. But that depends on the nature of the bootloop, the skill of the user and persistence.
Now, if you have fastboot access you don't need any of that. In fastboot you have a pretty powerful tool to wipe and format partitions, flash the Asus blob if all fails, but you quite a few options....
If you can get "only occasionally" into the bootloader I would not wait much longer but perform a full wipe of the major partitions and flash the Asus system blob, returning the tablet to stock basically and giving you a fresh start.
We call it a @Buster99
Download the latest Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95u/8/
Extract it twice and copy the blob into your fastboot directory.
Issue these commands in fastboot one by one:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Good luck!
Thanks Berndblb. I downloaded the Asus firmware and was able to get the blob file.
But I'm fine with totally starting over and trying Buster99, but I'm still unable to get the ADB to see the device.
I've gone through the beginners guide to root and flashing a custom rom again, but I still can't see the device when I type in "fastboot devices".
If you have any advice or a guide on what I need to do get where I can use ADB to erase everything and start over again.
i cant do anything the tablet starts - shows asus logo-go to TWRP logo screen - restarts (all in 32 seconds). Any other sugestion? if i dismantle the tablet ? or anithing else?
Thank You
wldtravel26 said:
Thanks Berndblb. I downloaded the Asus firmware and was able to get the blob file.
But I'm fine with totally starting over and trying Buster99, but I'm still unable to get the ADB to see the device.
I've gone through the beginners guide to root and flashing a custom rom again, but I still can't see the device when I type in "fastboot devices".
If you have any advice or a guide on what I need to do get where I can use ADB to erase everything and start over again.
Click to expand...
Click to collapse
Either you do not have the correct driver installed or your usb cable is not original but a cheap "charge only" knockoff or try a different usb port or you are not open the cmd prompt from the fastboot directory or your usb port is busted.....
I don't know how to troubleshoot that from here....
Please search the TF700 forum or google "fastboot driver problems". That problem is so common, I really do not know what to add to advice that's out there a hundred times over....
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
mallasorte2000 said:
i cant do anything the tablet starts - shows asus logo-go to TWRP logo screen - restarts (all in 32 seconds). Any other sugestion? if i dismantle the tablet ? or anithing else?
Thank You
Click to expand...
Click to collapse
You can always install a new r used mainboard, but that's the only reason to open it up....
Sorry man, if you do not have adb while the recovery is looping or starting up and you cannot get into fastboot, there's nothing you can do.....
Except for the really crazy and desperate "throw away reason" stuff of course. Like stuffing the tablet into the freezer in an airtight bag for 30 min, then try to boot it......
Thanks Berndblb, I was able to get through the Buster 99 instructions above.
Per the last step I would have expected the tablet to reboot, but that did not happen.
When I restarted it I got the following error when I tried to load Andriod "unrecoverable bootloader error".
I used the following file from the Asus website US_epaduser10_6_1_14_10_UpdateLauncher, based on the fact that my bootloader shows the tablet as "US_epad-10.6.1.14.10-20130801". Hopefully I used the right file for the blob file.
I've attached what I have from adb for the system flash blob and reboot. I tried to screen shoot it in a better format, but that didn't work.
Hopefully someone will be able to take a look and direct me in the right way to get this working again.
C:\adb>fastboot devices
015d2a5086641a19 fastboot
C:\adb>fastboot - i 0x0B05 flash system blob
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\adb>fastboot - i 0x0b05 reboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
wldtravel26 said:
Thanks Berndblb, I was able to get through the Buster 99 instructions above.
Per the last step I would have expected the tablet to reboot, but that did not happen.
When I restarted it I got the following error when I tried to load Andriod "unrecoverable bootloader error".
I used the following file from the Asus website US_epaduser10_6_1_14_10_UpdateLauncher, based on the fact that my bootloader shows the tablet as "US_epad-10.6.1.14.10-20130801". Hopefully I used the right file for the blob file.
I've attached what I have from adb for the system flash blob and reboot. I tried to screen shoot it in a better format, but that didn't work.
Hopefully someone will be able to take a look and direct me in the right way to get this working again.
Click to expand...
Click to collapse
You used the correct file but I see a mistake in your command.
You put a space between the dash and the "i" in your command: fastboot - i 0x0B05 which is a command fastboot does not understand so it shows you the help file so to speak.
It is supposed to be fastboot -i 0x0B05.
See the difference?
Try it again and welcome to the world of the command line
A thousand thanks Berndblb. I was able to get it flashed and it back to the original firmware. Thought for a while, it was a total loss, so your advise was a big help.
On another note, I was having this issue with multiple custom roms, which leads me to believe it a hardware issue.
If I press on the screen too hard or lift it in a different angle, it will freeze up and try to reboot.
I was just able to get past the initial setup, but once I lifted the tablet up again, it did the same thing and froze.
I had basically been stuck, just using the tablet for strictly steaming purposes and leaving in on a table.
If anyone has had similar issues or has any insight let me know.
My wife is asking for a new Ipad if we can't get it to work properly, I'm still trying to convince her to stick with Android but this tablet isn't helping my case.
wldtravel26 said:
A thousand thanks Berndblb. I was able to get it flashed and it back to the original firmware. Thought for a while, it was a total loss, so your advise was a big help.
On another note, I was having this issue with multiple custom roms, which leads me to believe it a hardware issue.
If I press on the screen too hard or lift it in a different angle, it will freeze up and try to reboot.
I was just able to get past the initial setup, but once I lifted the tablet up again, it did the same thing and froze.
I had basically been stuck, just using the tablet for strictly steaming purposes and leaving in on a table.
If anyone has had similar issues or has any insight let me know.
My wife is asking for a new Ipad if we can't get it to work properly, I'm still trying to convince her to stick with Android but this tablet isn't helping my case.
Click to expand...
Click to collapse
damn i feel so used
grats on getting it to work again.
in regard to the troubles you are still having: is it in the Keydock or without, also a possibility that the display has an issue with the digitizer and shortens out.
cheers
Buster
I typically use it without the dock. Haven't put it in the dock in a while. Yea I was thinking the same thing where maybe something is loose inside.
Short of changing out the whole digitizer, do you know of any trouble shooting I can do if I open it up? If it keeps doing this, the tablet itself isn't worth using often. I did have a gumdrop case on it most of the time. I've got a toddler, so wanted maximum protection for it. Maybe it overheated or something?
Check out some tear down videos on YouTube and iFixit, then open it up and check all connectors you can get your hands or tools on. It does sound as if you gave a connection shorting out.
Sent from my Nexus 5X using Tapatalk
berndblb said:
If you can get into fastboot yours is a very different situation. But let me answer your questions first.
The linked method works if you have adb access in TWRP - however briely. Even if TWRP loops you should have adb access at some point (open Device Manager and watch for changes).
If TWRP is just bootlooping very quickly you may be out of luck but I have seen cases where a little window of adb access and careful timing of the commands let people push the file to internal and insmod it. But that depends on the nature of the bootloop, the skill of the user and persistence.
Now, if you have fastboot access you don't need any of that. In fastboot you have a pretty powerful tool to wipe and format partitions, flash the Asus blob if all fails, but you quite a few options....
If you can get "only occasionally" into the bootloader I would not wait much longer but perform a full wipe of the major partitions and flash the Asus system blob, returning the tablet to stock basically and giving you a fresh start.
We call it a @Buster99
Download the latest Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95u/8/
Extract it twice and copy the blob into your fastboot directory.
Issue these commands in fastboot one by one:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Good luck!
Click to expand...
Click to collapse
I also got into a bootloop situation and was unable to connect via adb (adb usb gave me "error: device not found") but fastboot was ok. So I tried the @Buster99 rescue. Unfortunately it failed at the flash system blob step. It gave "FAILED (data transfer failure (unknown error))...".
It's been too long since I used adb and fastboot. Lately my TF700T had become erratic, unstable and experiencing sudden reboots so I wanted to format data and do clean re-install of KatshMallow #29. I also had discovered that the digitizer had developed a blind-spot, actually more of a whole blind column of about a quarter inch wide, giving me problems swiping a TWRP button to unlock the screen. So, I went to change TWRP's screen timeout setting (TWRP 2.8.4.0 Kang) to max when suddenly it rebooted into a system bootloop. Going to TWRP would go to bootloop again at the TWRP splash screen.
Alas, I must have forgotten to set the USB debug mode after the last flashing as I am now locked out of adb. That's how I got into this unfortunate situation.
Any ideas, short of replacing TF700T's mb? Looks like this is the end of a long journey with my TF700T! :crying:
Kraka said:
I also got into a bootloop situation and was unable to connect via adb (adb usb gave me "error: device not found") but fastboot was ok. So I tried the @Buster99 rescue. Unfortunately it failed at the flash system blob step. It gave "FAILED (data transfer failure (unknown error))...".
It's been too long since I used adb and fastboot. Lately my TF700T had become erratic, unstable and experiencing sudden reboots so I wanted to format data and do clean re-install of KatshMallow #29. I also had discovered that the digitizer had developed a blind-spot, actually more of a whole blind column of about a quarter inch wide, giving me problems swiping a TWRP button to unlock the screen. So, I went to change TWRP's screen timeout setting (TWRP 2.8.4.0 Kang) to max when suddenly it rebooted into a system bootloop. Going to TWRP would go to bootloop again at the TWRP splash screen.
Alas, I must have forgotten to set the USB debug mode after the last flashing as I am now locked out of adb. That's how I got into this unfortunate situation.
Any ideas, short of replacing TF700T's mb? Looks like this is the end of a long journey with my TF700T! :crying:
Click to expand...
Click to collapse
Did you ever get it fixed? I'm in the same situation. Can't enter recovery or fastboot. Well, I entered fastboot once, chose recovery, now it boot loops straight to recovery. This sucks. Tablet worked fine for months.
If you can't boot into fastboot and you do not have adb access when in recovery, you're done. Nothing left to do.
You did not mention if you are unlocked. With a locked bootloader you can't do anything even if you have adb in recovery or if you could boot to fastboot. Sorry
It is unlocked and rooted. I see something showing up in Device Manager, only it says Google Nexus ADB interface. I can also enter the other mode with Power and Vol Up. This mode holds, however, not sure if I can do much from there.
Now I got TWRP screen stuck, so at least it's not looping. But adb commands don't produce any effect.
xxhaimbondxx said:
It is unlocked and rooted. I see something showing up in Device Manager, only it says Google Nexus ADB interface. I can also enter the other mode with Power and Vol Up. This mode holds, however, not sure if I can do much from there.
Click to expand...
Click to collapse
What do you mean? APX? No, that does not help you
xxhaimbondxx said:
Now I got TWRP screen stuck, so at least it's not looping. But adb commands don't produce any effect.
Click to expand...
Click to collapse
With TWRP booted, do you see the adb recovery interface in device manager and what do you get with "adb devices"? Do you have the drivers installed?
berndblb said:
With TWRP booted, do you see the adb recovery interface in device manager and what do you get with "adb devices"? Do you have the drivers installed?
Click to expand...
Click to collapse
This is the only thing I see in Device Manager: Google Nexus ADB interface. I installed the Universal Drivers.
When I type adb devices, I get nothing.
Well, this one time I got this:
adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *