Hello! My device stucks in the Kindle Fire logo and keeps looping. I know that a lot of people face this problem and i've read a lot of topics but i cant find the answer. I made a factory cable and on the screen it says "Fastboot kindle fire" in orange. But my computer recognizes it as Tate-PVT-08. Although in the device manager it shows Kindle Fire/Android ADB Interface. I used KFHD System.img Restore Tool and chose 4-th option, it shows:
"product: Tate-PVT-08
finished. total time: 0.003s
rebooting...
finished. total time: 0.002s
Please wait for your device to reboot fully, unlock the screen and make sure ADB
is enabled in settings, as well as install unknown applications.
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
- waiting for device -"
And then I ran the "restore-su only"option. the prog worked but nothing happened to my kindle.
What I have to do? Please help me, it's driving me mad!
Hey buddy, I actually went through something similar not too long ago so let me see if I can help. First off, download the tool from this link and make sure it's the proper OS version you were using before:
http://forum.xda-developers.com/showthread.php?p=39687961
The OS version might not matter, but to be safe you might want to pick the version you were using. I selected the first option to restore with a rooted OS, and a couple extra boot-loaders's and that way it came out nicely rooted for me with NOVA launcher (which is awesome).
The only hiccup I ran into was I was changing versions, so I had to erase user data (it's one of the menu options) and then I had to manually copy boot and recovery files. I lost my user data, but that just lost me some saved game files and everything else I could get from amazon.com. Good luck, and if I can help in any way let me know.
phanbach92 said:
Hello! My device stucks in the Kindle Fire logo and keeps looping. I know that a lot of people face this problem and i've read a lot of topics but i cant find the answer. I made a factory cable and on the screen it says "Fastboot kindle fire" in orange. But my computer recognizes it as Tate-PVT-08. Although in the device manager it shows Kindle Fire/Android ADB Interface. I used KFHD System.img Restore Tool and chose 4-th option, it shows:
"product: Tate-PVT-08
finished. total time: 0.003s
rebooting...
finished. total time: 0.002s
Please wait for your device to reboot fully, unlock the screen and make sure ADB
is enabled in settings, as well as install unknown applications.
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
- waiting for device -"
And then I ran the "restore-su only"option. the prog worked but nothing happened to my kindle.
What I have to do? Please help me, it's driving me mad!
Click to expand...
Click to collapse
boomtekd said:
Hey buddy, I actually went through something similar not too long ago so let me see if I can help. First off, download the tool from this link and make sure it's the proper OS version you were using before:
http://forum.xda-developers.com/showthread.php?p=39687961
The OS version might not matter, but to be safe you might want to pick the version you were using. I selected the first option to restore with a rooted OS, and a couple extra boot-loaders's and that way it came out nicely rooted for me with NOVA launcher (which is awesome).
The only hiccup I ran into was I was changing versions, so I had to erase user data (it's one of the menu options) and then I had to manually copy boot and recovery files. I lost my user data, but that just lost me some saved game files and everything else I could get from amazon.com. Good luck, and if I can help in any way let me know.
Click to expand...
Click to collapse
Thank you for your reply , but i wish it was that simple. My os version is 7.1.5 as i remember, i've tried the 1.0 version of that program. It worked but nothing happened, the problem still remains. Now i'm downloading the 1.2 version.Hope it works...
I think the problem is that my PC can't recognize my kindle. Although it shows Kindle Fire ADB driver in the Device Manager. Did your PC recognize your device as Kindle Fire? or something like "TATE-PVT-08"?
I just want to ask, is that normal if my device shows Tate-PVT-08?
phanbach92 said:
I just want to ask, is that normal if my device shows Tate-PVT-08?
Click to expand...
Click to collapse
That shows that your fastboot works. Thread in my signature, #6.
seokhun said:
That shows that your fastboot works. Thread in my signature, #6.
Click to expand...
Click to collapse
i plugged my device and checked for the adb status, it says device's not found. Then i tried "restore-su only" the program worked till finish, but my kindle is still bricked, like nothing's happened. One more thing, i use windows 8.
phanbach92 said:
i plugged my device and checked for the adb status, it says device's not found. Then i tried "restore-su only" the program worked till finish, but my kindle is still bricked, like nothing's happened. One more thing, i use windows 8.
Click to expand...
Click to collapse
Okay, back up. If your device is bricked, that means the bootloader is damaged. You have to overwrite the bootloader if you want it to boot at all, restoring su binaries won't do a thing.
seokhun said:
Okay, back up. If your device is bricked, that means the bootloader is damaged. You have to overwrite the bootloader if you want it to boot at all, restoring su binaries won't do a thing.
Click to expand...
Click to collapse
Is there any tutorial for that?
phanbach92 said:
Is there any tutorial for that?
Click to expand...
Click to collapse
/facepalm. I told you, thread in my signature, #6. You already have the factory cable, use it.
seokhun said:
/facepalm. I told you, thread in my signature, #6. You already have the factory cable, use it.
Click to expand...
Click to collapse
I mean how to overwrite the bootloader?
I tried this:
2. Download this file: Amazon OS 7.2.3. Once it finishes, place that file in the same folder as your fastboot.exe (this is found in the Android SDK folder, so if you haven't installed the Android SDK, do so) which should be the platform-tools folder. Rename the file to amazon723.bin for easier flashing (or rename it however you want, but use that name later on).
Now plug the device into the computer using the factory cable, and the device should reboot into fastboot mode (you'll see "fastboot" in orange on the device). From there, type this command and hit enter:
fastboot -i 0x1949 flash boot amazon723.bin
Now the OS will be flashed, and after it finishes, type:
fastboot -i 0x1949 reboot
After the reboot completes, you'll be back at the very start.
but when it flashes the OS it says FALED: <remote: image is too large for partition>
phanbach92 said:
I mean how to overwrite the bootloader?
I tried this:
2. Download this file: Amazon OS 7.2.3. Once it finishes, place that file in the same folder as your fastboot.exe (this is found in the Android SDK folder, so if you haven't installed the Android SDK, do so) which should be the platform-tools folder. Rename the file to amazon723.bin for easier flashing (or rename it however you want, but use that name later on).
Now plug the device into the computer using the factory cable, and the device should reboot into fastboot mode (you'll see "fastboot" in orange on the device). From there, type this command and hit enter:
fastboot -i 0x1949 flash boot amazon723.bin
Now the OS will be flashed, and after it finishes, type:
fastboot -i 0x1949 reboot
After the reboot completes, you'll be back at the very start.
but when it flashes the OS it says FALED: <remote: image is too large for partition>
Click to expand...
Click to collapse
Do you have factory cable ? Now you dowload KFHD_SRT_v1.3.5- 7.3.0 (seperate option for restoring factory recovery) .See here http://forum.xda-developers.com/showthread.php?t=1951254
Follow the instructions of your device will work again. Hope help you
phanbach92 said:
I mean how to overwrite the bootloader?
I tried this:
2. Download this file: Amazon OS 7.2.3. Once it finishes, place that file in the same folder as your fastboot.exe (this is found in the Android SDK folder, so if you haven't installed the Android SDK, do so) which should be the platform-tools folder. Rename the file to amazon723.bin for easier flashing (or rename it however you want, but use that name later on).
Now plug the device into the computer using the factory cable, and the device should reboot into fastboot mode (you'll see "fastboot" in orange on the device). From there, type this command and hit enter:
fastboot -i 0x1949 flash boot amazon723.bin
Now the OS will be flashed, and after it finishes, type:
fastboot -i 0x1949 reboot
After the reboot completes, you'll be back at the very start.
but when it flashes the OS it says FALED: <remote: image is too large for partition>
Click to expand...
Click to collapse
Use the KFHD System Restore tool. If you want to go that route, change "boot" to "system" and it should work.
quan_1986 said:
Do you have factory cable ? Now you dowload KFHD_SRT_v1.3.5- 7.3.0 (seperate option for restoring factory recovery) .See here http://forum.xda-developers.com/showthread.php?t=1951254
Follow the instructions of your device will work again. Hope help you
Click to expand...
Click to collapse
Cảm ơn bạn rất nhiều! Tôi làm theo cách của bạn và đã sửa được máy!!:good:
phanbach92 said:
Cảm ơn bạn rất nhiều! Tôi làm theo cách của bạn và đã sửa được máy!!:good:
Click to expand...
Click to collapse
:good: Group our https://www.facebook.com/groups/KFHDVN/
Related
Introducing: Kindle Fire 2nd-bootloader + TWRP 2.6.3.0 for the Kindle Fire 2nd GEN
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
*** READ CAREFULLY BEFORE DOING ANYTHING ***
*** Kindle Fire 1st-gen ROMs/KERNELS are *NOT* compatible with the Kindle Fire 2. Please only flash ROMs/KERNELS that are made for the Kindle Fire 2. ***
** IF YOU HAVE QUESTIONS, RE-READ THROUGH THE THREAD FOR ANSWERS. WHEN YOU'RE ABSOLUTELY SURE NO ONE HAS ASKED YOUR QUESTION, GO AHEAD AND RE-READ THE THREAD AGAIN AND USE THE SEARCH FEATURE. THEN POST YOUR QUESTION IF YOU STILL CAN'T FIND THE ANSWER **
** WHEN MOVING FROM AMAZON OS TO CM10.1 IN TWRP: "WIPE" -> "SYSTEM" AND "FACTORY RESET" TO CLEAR SYSTEM/DATA/CACHE. YOUR APPS FROM AMAZON ICS AREN'T COMPATIBLE. IF NOT YOU'LL LOOP ON THE CM10.1 BOOT ANIMATION **
[03/27] NEW support thread for OFFICIAL CM on the Otter2 (Kindle Fire 2):
http://forum.xda-developers.com/showthread.php?t=2209995
** YOU SHOULD HAVE A WORKING FASTBOOT CABLE + FASTBOOT DRIVERS/ACCESS ON YOUR PC. **
Q: How do I know if my fastboot works?
A: Plug the cable into your device and then the computer. Reboot the Kindle. It *SHOULD* show a Fastboot screen. Once at the screen use this command on your computer:
fastboot -i 0x1949 devices
You should see something like this:
0123456789ABCDEF
Here's 1 website you can purchase a FASTBOOT adapter from (works with your normal USB cable)
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
** I don't make any commission or fee from the sales of these devices, I just know they have them on stock most of the time and ship in a reasonable time frame unlike the Chinese variants found on ebay.
If you do NOT see this, then make sure you have the SDK installed correctly and you have the right setup for fastboot on your PC before proceeding.
*** BE SURE YOU HAVE A GOOD CHARGE ON THE DEVICE ***
INITIAL SETUP INSTRUCTIONS (1st TIME ONLY) FOR 2ND-BOOTLOADER + TeamWinRecoveryProject INSTALL:
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb pull /dev/block/mmcblk0boot0
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/boot
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/system # This will take a few minutes
Take those files and put them somewhere safe.
STEP 2: Download the files you will need to install 2nd-bootloader, TWRP and CM10.1:
Stack override file:
http://goo.im/devs/Hashcode/otter2/stack
[12/09] otter2-freedom-boot-10.4.6.img (USED ONLY THE FIRST TIME -- .zip files will have their own boot.img's from now on):
http://goo.im/devs/Hashcode/otter2/otter2-freedom-boot-10.4.6.img
md5sum: 80f9b9ba80910de361463560f86f315a
[09/03] TeamWin Recovery 2.6.3.0:
http://goo.im/devs/Hashcode/otter2/otter2-twrp-2.6.3.0-recovery.img
md5sum: a66a8cbab92fd5daaa85f6303e9cc0c3
older 10.2.4 bootloader file and flash to your device via fastboot:
http://goo.im/devs/Hashcode/otter2/otter2-u-boot-prod-10.2.4.bin
md5sum 5b03a7b428325de8d360ec201a745498
(You SHOULD check the MD5SUM before using fastboot -- downloads CAN be corrupted)
CM-10.1/CM-10.2 for the Kindle Fire 2 (choose the latest version from):
http://www.get.cm/?device=otter2
Google Apps from: http://goo.im/gapps (choose the version: CM10.1 or CM10.2)
Place the ROM and the gapps .zip on your device in the /sdcard area
STEP 3. Install the stack override in /system:
ADB commands entered while booted up into STOCK *rooted* Amazon Kindle OS -- May need to enable ADB debugging in Settings:
[2013-08-21] edited the location where stack is placed on device due to permissions changes
Code:
adb push stack /sdcard/
adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
[ Connect fastboot cable, and reboot the device so that "Fastboot" is showing ]
STEP 4.
Flash the OLD bootloader, new otter2-freedom-boot.img and TWRP recovery.[/B]
*DONT RE-FLASH FREEDOM-BOOT.IMG LATER AFTER FLASHING CM10.1 -- IT'S FOR STOCK AMAZON OS ONLY / FIRST INSTALL ONLY*
Code:
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.0-recovery.img
fastboot -i 0x1949 reboot
** If everything was done correctly you will at this point see the bootmenu with a BLUE logo during the reboot. **
TO ENTER RECOVERY:
During the blue logo screen press the power button to cycle through options and select "Recovery" to enter TWRP.
Once in TWRP you can Install" the CM-10.1/CM-10.2 by selecting "Install" and then browsing the device and selecting it, then "Add Zip" and select the Gapps .zip as well.
Use the slider to start the install.
FLASHING BACK TO STOCK:
** FIND THE FILES WE BACKED UP IN STEP #1 OR DOWNLOAD NEW ONES FROM THE RECOVERY THREAD HERE: **
http://forum.xda-developers.com/showthread.php?t=2035047
Once you have these files (we'll name them boot.img/recovery.img and system.img for the purpose of these instructions, but they could be different on your system).
Plug in your fastboot cable and reboot so that you see the fastboot screen and enter the following commands:
Code:
fastboot -i 0x1949 flash boot [B]boot.img[/B]
fastboot -i 0x1949 flash recovery [B]recovery.img[/B]
fastboot -i 0x1949 flash system [B]system.img[/B] # This one will take a few minutes
fastboot -i 0x1949 reboot
Enjoy
THANKS TO:
fattire for finding the original bootloader exploit
TESTERS: powerpoint45 and FMKilo
Changelog: updated 2013-07-08
freedom boot.img (for use w/ stock Amazon OS + 2nd-bootloader):
[07/08] Updated w/ kernel from 10.4.3 release
TeamWin Recovery (TWRP) 2.6.0.0
[07/08] USB Vendor ID / Product ID in recovery now matches stock Amazon OS
[07/08] Based on 10.4.3 stock kernel
[07/08] Fixed recovery bootloop issue
[07/08] TWRP 2.6.0.0 update
one more reserved space
no chance to flash without fastboot cable? cause when i do
su
reboot bootloader
the fire boots into fastboot...does this work too?
Hondologe said:
no chance to flash without fastboot cable? cause when i do
su
reboot bootloader
the fire boots into fastboot...does this work too?
Click to expand...
Click to collapse
Yes, this would work, however if something goes wrong (and it frequently can during early development) you will have NO WAY of recovering the device without a fastboot cable. So I don't recommend this method currently.
Also, these instructions are BRAND NEW, and I understand if you really want to get this setup, but please let some users w/ fastboot cables run through the instructions to make sure I didn't typo something, etc.
Good work man! Can't wait for my fastboot cable so I can try this out.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Good work man! Can't wait for my fastboot cable so I can try this out.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I`m gonna try it later WITHoUT FB cable . If it fails i just have to wait a couple of days, so its worth it if i get CM onto my kindle
BTW If it fails, im gonna blame it on you (Just kidding...)
Thanks hash code!!! Is this ROM the updated one so Apollo won't force close?
powerpoint45 said:
Thanks hash code!!! Is this ROM the updated one so Apollo won't force close?
Click to expand...
Click to collapse
I did make the /storage/usb0 changes in this ROM. No telling if it'll fix the Apollo FCs till we get it tested.
Hashcode said:
I did make the /storage/usb0 changes in this ROM. No telling if it'll fix the Apollo FCs till we get it tested.
Click to expand...
Click to collapse
OK cool! Looking forward to build custom ROM. Downloading latest ROM now... I think Darwin's upload failed ): not showing up as right file size on goo.im. will check md5 at home
Edit:no FC yet
i just ordered my factory cable... thanks hashcode and powerpoint45!
powerpoint45 said:
OK cool! Looking forward to build custom ROM. Downloading latest ROM now... I think Darwin's upload failed ): not showing up as right file size on goo.im. will check md5 at home
Edit:no FC yet
Click to expand...
Click to collapse
Goo doesn't always update the file size on the webpage during large uploads. Have him double-check the md5sum.
Hashcode said:
Goo doesn't always update the file size on the webpage during large uploads. Have him double-check the md5sum.
Click to expand...
Click to collapse
OK. I will when I get home so I can check md5. Any ideas to fix ducati?
powerpoint45 said:
OK. I will when I get home so I can check md5. Any ideas to fix ducati?
Click to expand...
Click to collapse
If someone has the time to do a video guide for this that would be great.
Congrats!
(that's all I got)
Congrats and thanks again to you and all involved!
Just soldered my own factory cable this evening from a spare micro-usb cable, and I could start my kindle in fastboot mode
Too late now so I'll take a deeper look and try to flash tomorrow evening and give some feedback - also have to find this damn fastboot command, wouldn't shop up in my terminal?!
Jowyn said:
Congrats and thanks again to you and all involved!
Just soldered my own factory cable this evening from a spare micro-usb cable, and I could start my kindle in fastboot mode
Too late now so I'll take a deeper look and try to flash tomorrow evening and give some feedback - also have to find this damn fastboot command, wouldn't shop up in my terminal?!
Click to expand...
Click to collapse
You will probably need to install the Android SDK to get the fastboot command.
Hashcode said:
You will probably need to install the Android SDK to get the fastboot command.
Click to expand...
Click to collapse
And all the image files that need to be flashed via fastboot need to reside where fastboot.exe is just to clarify.
Hashcode said:
You will probably need to install the Android SDK to get the fastboot command.
Click to expand...
Click to collapse
If you follow the noob guide on rooting the kindle fire 2 it tells you to download two files, inside of either of those two files is adb and fastboot as well as all the needed drivers, if you place the files needed to do this process inside of either of those folders holding down control while right clicking inside of the folder ( making sure nothing is highlighte) select open command prompt here, that way you should be able to do this process without the sdk
Let me know how it turns out and hopefully that will save some people the headache of getting their environmental variables set up correctly ( my computer likes to play stupid )
and nobody mentioned me.. come on, I thought I was listed in credits as moral support, and kid who flashed without a fbcable.. I know how to do it, and you could too if you just read up enough on idme and bootmodes..
No more from me, I don't want to be the one who is in trouble for bricked non factory cable owning users..
im a complete newb to fixing mobile devices and my friend gave me a messed up kindle fire hd.He said he screwed around with the os files and deleted one and he doesnt not know what one it was and when i try to boot it tries to boot but kindle file system recovery comes up. Then it asks me to reboot or factory reset i have tried both multiple times to no avail.I have a fastboot cable so that isnt a issue.Can somebody help me with a step by step or link to one.
huntergero said:
im a complete newb to fixing mobile devices and my friend gave me a messed up kindle fire hd.He said he screwed around with the os files and deleted one and he doesnt not know what one it was and when i try to boot it tries to boot but kindle file system recovery comes up. Then it asks me to reboot or factory reset i have tried both multiple times to no avail.I have a fastboot cable so that isnt a issue.Can somebody help me with a step by step or link to one.
Click to expand...
Click to collapse
You will need that fastboot cord.
Here is a system restore tool. I prefer to push the files manually but it will run as a tool http://forum.xda-developers.com/showthread.php?t=1951254
When you turn the Kindle Fire HD 7 on, push up on the volume rocker for three seconds until the screen shows the blue TWRP screen and release rocker and enter TWRP. (you said it boots into recovery?)
If this is the case, you don't need to do a full system restore. You can push a ROM the zips onto TWRP. Get them from the system restore tool.
If you have questions, feel free to ask. The tablet is recoverable unless something wrong is flashed.
LinearEquation said:
You will need that fastboot cord.
Here is a system restore tool. I prefer to push the files manually but it will run as a tool http://forum.xda-developers.com/showthread.php?t=1951254
When you turn the Kindle Fire HD 7 on, push up on the volume rocker for three seconds until the screen shows the blue TWRP screen and release rocker and enter TWRP. (you said it boots into recovery?)
If this is the case, you don't need to do a full system restore. You can push a ROM the zips onto TWRP. Get them from the system restore tool.
If you have questions, feel free to ask. The tablet is recoverable unless something wrong is flashed.
Click to expand...
Click to collapse
When it failed to boot in went into kindles reboot software and when i asked the individual i got this from he said he didnt install any recovery software.Can I install twerp now
huntergero said:
Can I install twerp now
Click to expand...
Click to collapse
Nope, it has to be a factory restore using your fastboot cord. I will list instructions.
---------- Post added at 09:50 PM ---------- Previous post was at 09:30 PM ----------
huntergero said:
Can I install twerp now
Click to expand...
Click to collapse
First thing is to download the SDK package and set the environment up. Here is a great video tutorial https://www.youtube.com/watch?v=oaNM-lt_aHw This will allow you to use fastboot command which is what you will do to push the images you need onto the bootloader.
To make sure your computer issue fastboot commands, open up a comand prompt as an administrator and type "fastboot -i 0x1949 getvar product" with no quotes and it should return Tate-xxx-xxx. If you don't get that response, do not move forward.
Once your at this point, download this tool http://forum.xda-developers.com/showthread.php?t=1951254 and either use it per the instructions or extract the files and CD from inside the folder and manually flash the 3 images via fastboot issuing these commands
fastboot -i 0x1949 flash boot "image name here" include .img at end"
fastboot -i 0x1949 flash recovery "recovery name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoob
Thanks in Advance
Waido1981 said:
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoobA
Thanks in Advance
Click to expand...
Click to collapse
If you want lollipop, take it to warranty. If you don't mind getting stuck on kitkat (after lollipop update you can run windows or linux on this tablet, and maybe use custom rom if anyone will make it using my idea), just say and I will write you steps how to get kitkat back.
Waido1981 said:
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoob
Thanks in Advance
Click to expand...
Click to collapse
Did you manage to work it out as I'm in the same boat at the moment - I can get to fastboot and can power on and off but stuck at boot! recovery efforts just show dead android and "Error"!
Anyone?
Cheers
noggin-the-nog said:
Did you manage to work it out as I'm in the same boat at the moment - I can get to fastboot and can power on and off but stuck at boot! recovery efforts just show dead android and "Error"!
Anyone?
Cheers
Click to expand...
Click to collapse
yeah my girlfriend has the same tablet. I took a backup with girlfriends device with fbrl and get it on my device. Just had to change settings and accounts and everything works well again.
Hi Everyone, I'm new here too.
I have the same problem in this topic.
I can use fastboot mode Only, I can't use adb mode, and the bootloader is locked.
when i was trying to install original firmware with this command:
fastboot update update.zip
I get this messege:
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
I need solution for this.
I haven't problem to installing any operating system, like Windows, Ubuntu, Tizen, Android x86, or other.
Please, I really need help, more than five months i am looking for a way out from this problem but it's all failed, because the boot loader was locked.
Any help would be very appreciated.
Thank you in advance.
Hi
Doesn't anybody have any ideas to help me ?
Maybe I must unlock bootloader to solve my problem.
But how I can do that ?
Waido1981 said:
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoob
Thanks in Advance
Click to expand...
Click to collapse
For people with access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- shutdown the tablet and press (power and vol-) to go to bootloader.
5- write on adb "adb push update.zip /sdcard/" wait until it finishes (dont leave bootloader)
6- Download Temp Recovery: www.androidfilehost.com/?fid=24052804347782876
7- On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////////////////////////////
//////////////////////////////////////////////////////
For people without access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- copy droidboot.img from .17 and put in in adb folder
5- go to fastboot and write "fastboot boot droidboot.img" it should boot to bootlaoder *do it at least 10 times because sometimes, the tablet boots to software and not bootloader*
6- if you are in bootloader then, Download Temp Recovery: www.androidfilehost.com/?fid=24052804347782876
7- After downloading, On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////
Good Luck! :laugh:
//////////////////////////////
Ruben Craveiro said:
For people without access to bootloader:
1- Download .17 and extract it on desktop
......
7- After downloading, On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
Click to expand...
Click to collapse
Hi Ruben,
What do you mean from step 1 ? Where can I find the (.17) to i can download it ?
When I perform step 7, it gave me error.
Overall, I had sent my problem to Asus support and their interaction was bad enough to hates them.
My problem has now ten months I have not found a solution, and the company asking me to send the device to America and I'm outside America.
I promise you I will avoid buying Asus devices from today onwards.
Thank you for trying to help us.
Venting said:
Hi Ruben,
What do you mean from step 1 ? Where can I find the (.17) to i can download it ?
When I perform step 7, it gave me error.
Overall, I had sent my problem to Asus support and their interaction was bad enough to hates them.
My problem has now ten months I have not found a solution, and the company asking me to send the device to America and I'm outside America.
I promise you I will avoid buying Asus devices from today onwards.
Thank you for trying to help us.
Click to expand...
Click to collapse
Did you manage to boot into the temp TWRP recovery or is that not working either?
lambdadroid said:
Did you manage to boot into the temp TWRP recovery or is that not working either?
Click to expand...
Click to collapse
Hello lambdadroid,
No, It's not work.
Venting said:
Hello lambdadroid,
No, It's not work.
Click to expand...
Click to collapse
You said you have access to fastboot though? Then you should also be able to boot into the temp recovery (e.g. TWRP)
lambdadroid said:
You said you have access to fastboot though? Then you should also be able to boot into the temp recovery (e.g. TWRP)
Click to expand...
Click to collapse
OK ..
I don't flashed the TWRP Recovery, and I can't get into fastboot / droidboot mode.
But when I press on this buttons (Volume up + Volume down + and Power) while booting, the device stopped on the ASUS logo screen, and in this status my PC connected with my Tablet device, and I can use fastboot commands, no thing other.
I can't use the ADB commands.
Also, When I tried flashing the firmware with ASUS Flash Tool, or CMD shell, I got the same message: FAILED (remote failure).
When I was trying to install the original firmware through CMD Shell with this command: "fastboot flash update update.zip"
I got this message:
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
When I tried with IntelAndroid-FBRL-07-24-2015 to flash TWRP or CWM Recovery, I got the error messages such as:
FAILED (data transfer failure (Unknown error))
FAILED (command write failed (No such device or address))
FAILED (command write failed (Unknown error))
I can't write anything to the device, That's everything.
I think i must unlock the bootloader to solve my problem.
But how do I do that ?
Venting said:
OK ..
I don't flashed the TWRP Recovery, and I can't get into fastboot / droidboot mode.
But when I press on this buttons (Volume up + Volume down + and Power) while booting, the device stopped on the ASUS logo screen, and in this status my PC connected with my Tablet device, and I can use fastboot commands, no thing other.
I can't use the ADB commands.
Also, When I tried flashing the firmware with ASUS Flash Tool, or CMD shell, I got the same message: FAILED (remote failure).
When I was trying to install the original firmware through CMD Shell with this command: "fastboot flash update update.zip"
I got this message:
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
When I tried with IntelAndroid-FBRL-07-24-2015 to flash TWRP or CWM Recovery, I got the error messages such as:
FAILED (data transfer failure (Unknown error))
FAILED (command write failed (No such device or address))
FAILED (command write failed (Unknown error))
I can't write anything to the device, That's everything.
I think i must unlock the bootloader to solve my problem.
But how do I do that ?
Click to expand...
Click to collapse
What you're saying doesn't make much sense. How did you actually mess up your tablet?
Please also tell me the following:
- What happens if you power on the tablet normally?
- What happens if you power on the tablet using Vol+ and the power button?
- What happens if you power on the tablet using Vol- and the power button?
Unlocking the bootloader is not possible on this device and it wouldn't help you anyway if you can't get into fastboot (the droidboot screen). As far as I know the fastboot screen you can enter with Vol+ and Vol- and the power button is pretty much useless, you need the droidboot screen to recover your tablet.
lambdadroid said:
What you're saying doesn't make much sense. How did you actually mess up your tablet?
Please also tell me the following:
- What happens if you power on the tablet normally?
- What happens if you power on the tablet using Vol+ and the power button?
- What happens if you power on the tablet using Vol- and the power button?
Unlocking the bootloader is not possible on this device and it wouldn't help you anyway if you can't get into fastboot (the droidboot screen). As far as I know the fastboot screen you can enter with Vol+ and Vol- and the power button is pretty much useless, you need the droidboot screen to recover your tablet.
Click to expand...
Click to collapse
If I press on the power button normally
Or I press on Volume up button, and Power button
Or I press on Volume down button, and Power button
The result is the same, It's a red line is showing on screen bottom, then the device stops working.
You can see this Picture here
Venting said:
If I press on the power button normally
Or I press on Volume up button, and Power button
Or I press on Volume down button, and Power button
The result is the same, It's a red line is showing on screen bottom, then the device stops working.
You can see this Picture here
Click to expand...
Click to collapse
How did you actually mess up your tablet?
I don't think you'll have many options to repair your tablet at this point. You could have luck if you have a powered OTG hub, by booting something like Linux and flashing the necessary stuff back to the internal storage, although depending on how much you messed up, that may not make things better. The other option is sending it in to ASUS.
Venting said:
Hi Ruben,
What do you mean from step 1 ? Where can I find the (.17) to i can download it ?
When I perform step 7, it gave me error.
Overall, I had sent my problem to Asus support and their interaction was bad enough to hates them.
My problem has now ten months I have not found a solution, and the company asking me to send the device to America and I'm outside America.
I promise you I will avoid buying Asus devices from today onwards.
Thank you for trying to help us.
Click to expand...
Click to collapse
what i mean with .17 is the software (first lollipop release)
you can get it here: http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.17_KK-user.zip
and to run the temp recovery make sure you have access to bootloader and have all drivers installed, if your computers says something about adb drivers for bootloader add these drivers so that it works: http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ADB_driver.zip if you still cant acces is because you did not installed properly all the needed drivers. I wish u luck.
---------- Post added at 08:49 PM ---------- Previous post was at 08:44 PM ----------
[/COLOR]
Venting said:
If I press on the power button normally
Or I press on Volume up button, and Power button
Or I press on Volume down button, and Power button
The result is the same, It's a red line is showing on screen bottom, then the device stops working.
You can see this Picture here
Click to expand...
Click to collapse
if you cant access bootloader or fastboot the only way to get it back, is to have a otg powered hub, and run uefi, and then boot linux and then reinstall the android partitions. (im very newbie at this so i cant tell u much about it)
---------- Post added at 09:00 PM ---------- Previous post was at 08:49 PM ----------
Venting said:
OK ..
I don't flashed the TWRP Recovery, and I can't get into fastboot / droidboot mode.
But when I press on this buttons (Volume up + Volume down + and Power) while booting, the device stopped on the ASUS logo screen, and in this status my PC connected with my Tablet device, and I can use fastboot commands, no thing other.
I can't use the ADB commands.
Also, When I tried flashing the firmware with ASUS Flash Tool, or CMD shell, I got the same message: FAILED (remote failure).
When I was trying to install the original firmware through CMD Shell with this command: "fastboot flash update update.zip"
I got this message:
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
When I tried with IntelAndroid-FBRL-07-24-2015 to flash TWRP or CWM Recovery, I got the error messages such as:
FAILED (data transfer failure (Unknown error))
FAILED (command write failed (No such device or address))
FAILED (command write failed (Unknown error))
I can't write anything to the device, That's everything.
I think i must unlock the bootloader to solve my problem.
But how do I do that ?
Click to expand...
Click to collapse
well you have made some stuff wrong, BUT i think you can get it back, first of all its not supposed for you to actually install twrp or cwm, and you need this file: (droidboot.img) https://drive.google.com/file/d/0B3h_JptTNZeeRjdXdE1rWlNLYnM/view?usp=sharing
and place it in c:\\adb and then do fastboot boot droidboot.img and then it should boot to the bootloader if it doesnt, then do it again and again until it does.. (you need to do it several times to make it work, at least thats how i got out of bootloop), then in the bootloader you have access to adb commands so temp recovery should be working, if it still doesnt then it means it needs the adb drivers for the bootloader, after u loaded twrp recovery load .17 update(place the update in microsd, or adb push update.zip /sdcard/) and it should work
lambdadroid, Ruben Craveiro
Thank you guys so much for trying help me.
I tried everything except OTG powered hub.
I will try with OTG powered hub, and I hope solves my problem.
Thank you for everything.
Ruben Craveiro said:
For people with access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- shutdown the tablet and press (power and vol-) to go to bootloader.
5- write on adb "adb push update.zip /sdcard/" wait until it finishes (dont leave bootloader)
6- Download Temp Recovery:
7- On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////////////////////////////
//////////////////////////////////////////////////////
For people without access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- copy droidboot.img from .17 and put in in adb folder
5- go to fastboot and write "fastboot boot droidboot.img" it should boot to bootlaoder *do it at least 10 times because sometimes, the tablet boots to software and not bootloader*
6- if you are in bootloader then, Download Temp Recovery
7- After downloading, On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////
Good Luck! :laugh:
//////////////////////////////
Click to expand...
Click to collapse
Hello
I tried these two methods to recover my unrooted Memo tab. The push method doesn't do anything and the second method says "wating for device"
A little background info on how I got here. The tablet got stuck on the loading screen after the last OTA update. I tried to do the factory reset from the tablet but I get the following messsage, "E: Can't open /dev/block/by-name/misc"
I have also tried to load the zip file using sideload and get the following message.
E:failed to verify whole-file signature
E:signature verification failed
Not sure what else to try...any help is appreciated.
wifebeeter said:
Hello
I tried these two methods to recover my unrooted Memo tab. The push method doesn't do anything and the second method says "wating for device"
A little background info on how I got here. The tablet got stuck on the loading screen after the last OTA update. I tried to do the factory reset from the tablet but I get the following messsage, "E: Can't open /dev/block/by-name/misc"
I have also tried to load the zip file using sideload and get the following message.
E:failed to verify whole-file signature
E:signature verification failed
Not sure what else to try...any help is appreciated.
Click to expand...
Click to collapse
make sure your device is conected to pc and that it has all the drivers needed (adb drivers)...boot into bootloader and load temp recovery and flash latest version
---------- Post added at 10:10 PM ---------- Previous post was at 10:00 PM ----------
Venting said:
lambdadroid, Ruben Craveiro
Thank you guys so much for trying help me.
I tried everything except OTG powered hub.
I will try with OTG powered hub, and I hope solves my problem.
Thank you for everything.
Click to expand...
Click to collapse
you can access dnx mode(fastboot starting #1#2#3), so you can go into bootloader, heres how: get the file efilinux.efi and droidboot.img and put them in adb folder (you can get the droidboot.img on update.zip and if u look on .33 version theres a zip inside of it that its called ESP, you can find efilinux.efi from there) after doing that go into DnX mode on the tablet, and do these fastboot commands: "fastboot flash osloader efilinux.efi" and do "fastboot boot droidboot.img" and this will certainly make you boot to droidboot/bootloader and from there you can load temp recovery and flash the software, and no need for otg hub
Ruben Craveiro said:
make sure your device is conected to pc and that it has all the drivers needed (adb drivers)...boot into bootloader and load temp recovery and flash latest version
HI
I tried temporary recovery and I get the following messege.
error: closed
<waiting for device>
Click to expand...
Click to collapse
Hi,
I updated my good old Kindle Fire HD 7 (tate) to cm 12.1 and because of problems with the Play store I made a factory reset. Since then it is in a bootloop showing only the blue teamwin screen with some flickering about every 5-6 seconds.
As I read here (http://forums.androidcentral.com/sa...p-after-factory-reset-cyanogenmod-12-1-a.html), I need to use fastboot.exe to start a new recovery but... fastboot does not recognize the device.
What is working?
adb status-window shows
...Android Debug Bridge
State: unknown (or recovery)
adb reboot revovery - reboots the device
adb reboot bootloader - reboots the device showing a "fastboot logo"
fastboot devices
< waiting for device > / or just no reaction
fastboot -i 0x1949 getvar product
TATE-PUT-08
Okay, after some research I updated my driver (as seen here http://forum.xda-developers.com/showthread.php?t=2271909) and they seem to be installed properly but nothing changes to the behaviour shown above.
What to do?
And thanks a lot!
My systems: Windows 7 Professional 64 bit or Windows 7 Home Premium 64 Bit
..getting creative, I tried
fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
creating boot image...
creating boot image - 8343552 bytes
downloading 'boot.img'...
OKAY [ 2.817s]
booting...
OKAY [ -0.000s]
finished. total time: 2.817s
..and it reboots into the same teamwin splash screen boot loop
...with adb status-window saying "recovery"
Ok, I had the courage to flash and tate is working again:
1. adb reboot bootloader (then in Fastboot mode)
2. fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img
3. fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
4. two reboots and cm 12.1 is working
Same problem! PLEASE HELP!
I'm stuck with THE EXACT same problem.
Please tell me how to go about this step-by-step?
I hope you reply asap..
TIA.
Diplominformatiker said:
Ok, I had the courage to flash and tate is working again:
1. adb reboot bootloader (then in Fastboot mode)
2. fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img
3. fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
4. two reboots and cm 12.1 is working
Click to expand...
Click to collapse
can you please do a step by step write-up please?
1. start windows command prompt (cmd.exe) in Administrator Mode
2. type "adb reboot bootloader"
3. type "fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img"
4. type "fastboot -i0x1949 boot philz_touch_6.48.4-tate.img"
reboot (perhaps several times)
preparations (if not yet done):
- install Android development kit or download adb somewhere
- download philz_touch_6.48.4-tate.img, copy to same folder as adb
- connect kindle via usb
Good Luck
Diplominformatiker said:
1. start windows command prompt (cmd.exe) in Administrator Mode
2. type "adb reboot bootloader"
3. type "fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img"
4. type "fastboot -i0x1949 boot philz_touch_6.48.4-tate.img"
reboot (perhaps several times)
preparations (if not yet done):
- install Android development kit or download adb somewhere
- download philz_touch_6.48.4-tate.img, copy to same folder as adb
- connect kindle via usb
Good Luck
Click to expand...
Click to collapse
I bricked my kindle by using FireFlash to get into recovery, and I didn't check the box for the bootloader. Now I am stuck in a boot loop. Every time I use a command in adb, it says it can't find a device. I have tried with a factory cable and with a regular USB. I tried updating the driver through the Device Manager, but it can't find a driver for my kindle. I found a few drivers to choose from on a website (I would post the link, but it won't let me), but none of them seemed to work. Is there something I am doing wrong?
whether the tablet says fastboot or teamwin, it will not start fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img, it will just say waiting for device...
hiii
Same situation , no solution until now
unimoose said:
I bricked my kindle by using FireFlash to get into recovery, and I didn't check the box for the bootloader. Now I am stuck in a boot loop. Every time I use a command in adb, it says it can't find a device. I have tried with a factory cable and with a regular USB. I tried updating the driver through the Device Manager, but it can't find a driver for my kindle. I found a few drivers to choose from on a website (I would post the link, but it won't let me), but none of them seemed to work. Is there something I am doing wrong?
Click to expand...
Click to collapse
In device managment, set to see the hidden devices, must appear as TATE-PVT-8, depending the version of Windows you're using must set the signed drivers to disable.
Then update the driver to tate with this controllers.
And use fatbootmode, can use: KFHD_SRTool_v1.2 to revert to completly stock.
Hopes works for you.
Enomaly said:
whether the tablet says fastboot or teamwin, it will not start fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img, it will just say waiting for device...
Click to expand...
Click to collapse
Are you saying that the above mentioned method will not work? So what is the possible solution?
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
Click to expand...
Click to collapse
Go to https://developers.google.com/android/images and flash manually it's work with me
Sent from my BASIC using Tapatalk
When you run the flash all in fastboot, what messages/errors does it show?
I once ran into a similar problem, the fact that you have unlocked the bootloader is good as you can flash the factory image and boot it up.
Usually once in fastboot I check the devices with "fastboot devices", if it shows up, I close the adb window, copy the factory image files to the adb folder, and doublec click the flash all bat. It should do everything by itself and reboot now.
TENN3R said:
When you run the flash all in fastboot, what messages/errors does it show?
I once ran into a similar problem, the fact that you have unlocked the bootloader is good as you can flash the factory image and boot it up.
Usually once in fastboot I check the devices with "fastboot devices", if it shows up, I close the adb window, copy the factory image files to the adb folder, and doublec click the flash all bat. It should do everything by itself and reboot now.
Click to expand...
Click to collapse
Just to add to this, make sure you left the image-coral-[buildnumber].[builddate].zip ZIPPED. Your folder should look something like this one, although you might also have your platform-tools in that same directory, which is perfectly fine, but not necessary if you have them added to your path.
Just try redoing the flash-all.bat again. This time, though, do it from powershell. Here's what to do. Right click in the folder, not on any item, just in the folder, and you should see "open powershell" (or command prompt, if this is the case, then just type powershell into the cmd window), click that. Then, type or copy and paste into the powershell prompt while in that directory:
.\flash-all.bat | Tee xda-flash-attempt.log
and if it still doesn't work and you're stuck in fastboot, just upload that .log file, so we can see what happened. If you're curious, what Tee does is it simultaneously takes standard input (i.e. what you see on the screen, the output of programs) and shows it to you, as well as sends it to a file, in this case, the xda-flash-attempt.log If you really don't want to use powershell, you can accomplish what's needed by typing flash-all.bat > xda-flash-attempt.log, but you will not see any of the output, as it will all be piped into that file. The | key is the one directly below backspace, which is the same key as \, but with shift held down.
Also, if it's not working, it might be worth checking that the checksum of the zip file you downloaded is correct, possibly redownloading it, and also checking what the flash-all.bat contents are. There are two files named flash-all in the folder, one a .sh for *nix systems, and a .bat for windows. While it should automatically assume you meant the .bat, it's best to be explicit. The .sh really wouldn't do anything different, if it worked, so it's a minor issue that really wouldn't make a difference, but still.
Edit: when you do type flash-all, the cmd prompt was in the directory with the flash-all.bat file as well as all of the other necessary files, yes? Seems obvious, perhaps, but just based on the "cd\pp\p" command you ran, which doesn't do anything, you should be changing directory to the directory that holds the flash-all.bat as well as the firmware.
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today ...
Click to expand...
Click to collapse
Like others have said, you need to extract the Google image which has a nested zip file (which you leave alone unless you need something in there). Since you apparently are stuck and cannot boot, I suggest you extract the boot.img from that nested zip file into your tools folder and fastboot flash the boot.img to be able to boot the phone to system. You may need to do the vol-down button press to enter fastboot mode. Once you have your phone back and running, boot into fastboot mode and run the flash-all again. If you extracted the Google image completely, now the script can finish. Not sure if you want to wipe the phone while doing this, so you can also "dirty flash" . If you would like to retain all your apps and app data, edit the flash-all script with notepad and remove the wipe flag (-w) from the script and SAVE it before running. Best of luck. :good:
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
Click to expand...
Click to collapse
Put the unzipped factory image files (should be 6 of them) in your platform tools folder and then open up the command prompt in the platform tools folder and execute the flash-all command. Make sure all remnants of previous factory images, etc. are removed from the platform tools folder beforehand as well so you just have the platform tools default files in there as well as the 6 files from the factory image.
The latest version of platform tools is 30.0.4 I believe so make sure you have that version.
I just switched from a Pixel 2 xl and ran into the exact same problem with the no valid slot to boot error yesterday. It turned out I was not using the latest platform tools when flashing the factory image. I upgraded my platform tools to 30.04 and everything flashed and booted as expected.
Make sure you're using an A to C and not the C to C that comes with the phone when flashing. Yes, it matters.
Hi everyone,
Thank you so much guys for your quick responses . Well , I finally resolved my issue by the following commands so I'm just gonna post it for whomever may run into the same problem as I did .
First thing I did, was to download the latest Platform tools as well as USB Drivers and then I executed the following commands :
fastboot --slot=all flash bootloader ( Drag bootloader image ) By dragging I mean , you should unzip the flash factory image into a folder and then drag bootloader image into command prompt .
fastboot reboot bootloader
fastboot --slot=all flash radio ( Drag radio image )
fastboot reboot bootloader
fastboot --skip-reboot --slot=all update ( Drag Image file )
Boommmmm, my phone back on running again with no issue.
blackbomb1991 said:
Hi everyone,
Thank you so much guys for your quick responses . Well , I finally resolved my issue by the following commands so I'm just gonna post it for whomever may run into the same problem as I did .
First thing I did, was to download the latest Platform tools as well as USB Drivers and then I executed the following commands :
fastboot --slot=all flash bootloader ( Drag bootloader image ) By dragging I mean , you should unzip the flash factory image into a folder and then drag bootloader image into command prompt .
fastboot reboot bootloader
fastboot --slot=all flash radio ( Drag radio image )
fastboot reboot bootloader
fastboot --skip-reboot --slot=all update ( Drag Image file )
Boommmmm, my phone back on running again with no issue.
Click to expand...
Click to collapse
Woohoo! This worked perfectly. Thanks for following up with the instructions.