Help - I'm stuck in a bootloop 4 circles ! - Nexus 4 Q&A, Help & Troubleshooting

Hi I just tried to flash Android 4.4.4 without wiping & losing root using Nexus Root Toolkit
as per this link trendblog.net/flash-android-4-4-4-without-wiping-and-loosing-root/
I had slimkat 4.4.4 and tried to put stock 4.4.4 on this
After success messages the toolkit told me to wait for it to boot up but I am stuck on the four circles.
I have no recovery !!!
What can i do ?

Stop using took kits. They're nothing but trouble. Flash the factory image in fastboot and start over
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?

k500zm said:
Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?
Click to expand...
Click to collapse
First Google 15 second adb install xda. That'll set up fastboot on your PC. Then download the factory image. Google nexus 4 factory image. Extract that using 7-zip or winrar. In there is a flash-all.bat. just double click it. It will wipe your device so backup off the device first
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

k500zm said:
Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?
Click to expand...
Click to collapse
Here is an excellent guide how to use fastboot:
http://forum.xda-developers.com/showthread.php?t=1907796
It is guide for Nexus 7, but the proceeding is just identic like with all other Nexus devices.
tetakpatalked from Nexus 7 flo

Thanks guys. I am in a bit of a panic here.
couple of questions
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Also is it possible to get my files from the device before I wipe ?
I never used fastboot before - but I'm gonna learn fast now !

k500zm said:
Thanks guys. I am in a bit of a panic here.
couple of questions
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Also is it possible to get my files from the device before I wipe ?
I never used fastboot before - but I'm gonna learn fast now !
Click to expand...
Click to collapse
You say you can't boot into recovery? That's going to be a problem retrieving data
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

Is there no way to get cwm back on there ?

k500zm said:
Is there no way to get cwm back on there ?
Click to expand...
Click to collapse
Maybe, you'll need fastboot for that too. Download the latest image file from here. Rename it recovery
http://techerrata.com/browse/twrp2/mako
We'll go from there. You're going to learn a lot more than you bargained for
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

k500zm said:
Thanks guys. I am in a bit of a panic here.
couple of questions
Click to expand...
Click to collapse
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Click to expand...
Click to collapse
Correct, but I'm not sure for the bootloader mode. I don't own a N4. Rather charge your battery first, it should work.
Also is it possible to get my files from the device before I wipe ?
Click to expand...
Click to collapse
If you're lucky, ADB might work even in bootloop if USB debugging was enabled in the developer options. As you didn't wipe, there is a small chance ADB pull might work.
IMHO the best you can do is to flash any custom recovery like TWRP or PhilZ with fastboot. The recovery.img file must be saved in the same folder where fastboot.exe is.
I assume Google USB driver is properly installed?
Fastboot must work, check in the guide I posted link for in my first post here how to check that fastboot commands are working. If "fastboot devices" returns "(your N4 serial No) fastboot" and your custom recovery is saved in proper folder, enter in CMD:
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
After that, enter recovery mode, there is another chance your ADB pull function might work. The phone should charge in recovery mode.
To install SlimKat again, format: system, data, cache, dalvik cache (TWRP) or choose factory reset and "clean to install new ROM" in PhilZ. Then flash ROM and Gapps, best with ADB sideload.
tetakpatalked from Nexus 7 flo

Ok I'm all ears and eager to learn
Ok downloaded - renamed to 'recovery.img'

k500zm said:
Ok I'm all ears and eager to learn
Ok downloaded - renamed to 'recovery.img'
Click to expand...
Click to collapse
Did you install fastboot with the 15 second adb install?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

I have installed Android SDK manager and the 15 sec drivers

I have android bootloader interface in my xp device manager

k500zm said:
I have installed Android SDK manager and the 15 sec drivers
Click to expand...
Click to collapse
OK, we'll try with that. Put your recovery image in the same folder as fastboot.exe. Open a command window in that folder, shift right mouse click in a open area in that folder
Plug your device into the USB port. Type
fastboot devices (return) in the cmd window
Is your device recognized? If it is then in the cmd window type
fastboot flash recovery recovery.img
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

ok - this is what I got...
C:\adb>fastboot devices
fastboot
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (7928 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.703s
C:\adb>

Ok I have TWRP started on my device [ i use cwm though will my nandroid backup be compatible with twrp ?]

k500zm said:
ok - this is what I got...
C:\adb>fastboot devices
01...... fastboot
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (7928 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.703s
C:\adb>
Click to expand...
Click to collapse
That sounds excellent, mate! Now try to reboot into the recovery mode
BTW: it isn't recommended to write down your device's serial No in worldwide public forum, it is your privacy in fact. Best edit your post now and remove big part of it (I also did it im my quote of your post)
tetakpatalked from Nexus 7 flo

k500zm said:
Ok I have TWRP started on my device [ i use cwm though will my nandroid backup be compatible with twrp ?]
Click to expand...
Click to collapse
Good job. The nandroid won't be compatible. Let me see if I can find a cwm image. Now that you know how to use fastboot
Sent from my Nexus 5 using XDA Free mobile app

I have a nandroid backup from cwm just before i fcud up - is there any way to restore this ?
Thanks for your help so far geezers

Related

Completely wiped my device... Need HELP to recover!!!

Hi Guys,
I did the most stupid thing and wiped everything on my device including the internal storage . Now i am stuck in TWRP recovery and i am not able to push files to /sdcard to flash a new rom and boot my device.
Can anyone help me???? i dont have any files on my storage now , but TWRP recovery is working fine. i tried
"adb push adb push C:\Users\Admin\Desktop\pa_grouper-2.10-06SEP2012-221306.zip /sdcard/"
please help me recover my Nexus 7.
Thanks a lot.
Download google factory image
Boot into fast boot (all3 buttons) then in terminal on computer use fastboot flash all nakasi-stock file name.tar.gz
Sent from my Nexus 7 using xda app-developers app
Harry GT-S5830 said:
Download google factory image
Boot into fast boot (all3 buttons) then in terminal on computer use fastboot flash all nakasi-stock file name.tar.gz
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi Harry GT-S5830,
Thanks , i am still in recovery , does it has to be factory image? can i just flash any custom rom , since that was my main purpose.
Just confirming the step:
* go into bootloader and then fastboot flash all <filename>
will that work?
EDIT: " fastboot flash all " didnt work.
i got the error :
asi-jro03d-factory-e102ba72.tgz
sending 'all' (257604 KB)...
OKAY [ 32.790s]
writing 'all'...
FAILED (remote: Invalid Partition Name.)
finished. total time: 32.820s
Please help.
Nexus toolkit has an option to restore to stock.
Use that.
Harry GT-S5830 said:
Download google factory image
Boot into fast boot (all3 buttons) then in terminal on computer use fastboot flash all nakasi-stock file name.tar.gz
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
well i just recovered the tablet using stock image via the fastboot commands.
i cant believe i erased internal storage. Big lesson learnt , never do two things at once ... at least when you are flashing a rom
Thanks everyone for their help, just wondering is there no way for us to push zip files to /sdcard folder via fastboot or recovery???
smartanks said:
well i just recovered the tablet using stock image via the fastboot commands.
i cant believe i erased internal storage. Big lesson learnt , never do two things at once ... at least when you are flashing a rom
Thanks everyone for their help, just wondering is there no way for us to push zip files to /sdcard folder via fastboot or recovery???
Click to expand...
Click to collapse
Its not in adb mode
Sent from my Nexus 7 using xda app-developers app

[Q] Need to flash 4.3 stock recovery

Hello,
I installed Open Recovery with TWRP and I want to return to the stock recovery.
Where and how can I find the 4.3 stock recovery in order to install it and how ?
Many thanks :good:
this what you're looking for?
http://forum.xda-developers.com/showthread.php?t=2010312
No, I need only the 4.3 Stock Recovery and without any wipe.
isotoper said:
No, I need only the 4.3 Stock Recovery and without any wipe.
Click to expand...
Click to collapse
You can try Wugfresh's Nexus Toolkit, it has many tools such has a stock recovery flasher.
Since I am on holiday I have no idea if Android 4.3 is supported on the Toolkit yet.
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
You can try Wugfresh's Nexus Toolkit, it has many tools such has a stock recovery flasher.
Since I am on holiday I have no idea if Android 4.3 is supported on the Toolkit yet.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Toolkit doesn't support 4.3 yet.
isotoper said:
Toolkit doesn't support 4.3 yet.
Click to expand...
Click to collapse
Android 4.3 does have a new recovery which does look better so I have no idea how to rip it out.
Sent from my Nexus 4 using Tapatalk 4 Beta
---------- Post added at 02:55 PM ---------- Previous post was at 02:30 PM ----------
Maybe you can get the recovery from the Nexus Stock Image site:
https://developers.google.com/android/nexus/images#occamjwr66v
Extract it and try to get the image.
Once you get the image go to Fastboot mode and enter the command: fastboot recovery [image name].img
Sent from my Nexus 4 using Tapatalk 4 Beta
Thanks, but I'm not so familiar with that fastboot script.
Easiest way is to download the 4.3 stock image and just flash the recovery image.
Any instructions?
isotoper said:
Any instructions?
Click to expand...
Click to collapse
my friend the task you are trying to accomplish will have instructions where ever you find the images. Have you search for the image you need? I think you are just looking for a zip file with stock recovery in it. This is not the norm but if you want stock that badly you may have to learn how to use fastboot and flash all stock that way. I know you dont want to lose your data but you may have to make the choice of data vs custom recovery. Go into the CWM or TWRP thread and kindly ask if someone can package the stock recovery in a zip file for you
isotoper said:
Any instructions?
Click to expand...
Click to collapse
Download the Android ADT Bundle from http://dl.google.com/android/adt/adt-bundle-windows-x86-20130717.zip
Extract the file and copy the "platform-tools" folder to C:\Android (create this folder if it doesn't exist). The final path should be C:\Android\platform-tools
Download the factory images from https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz . Extract them and find a file called "recovery.img". Copy this file to your platform-tools folder in C:\Android
Open a command Window in your platform-tools folder by holding SHIFT and right-clicking on it
Type:
Adb devices
And make sure it says "device" after some numbers.
Now type:
Adb reboot-bootloader
Wait for the device to reboot to bootloader.
Now type:
Fastboot flash recovery recovery.img
That's it.
Wow, thanks. I will try that and update.
It's not suppose to wipe any data, right?
Ok, done that and this is the cmd output :
sending 'recovery' (6738 KB)...
OKAY [ 0.220s]
writing 'recovery'...
OKAY [ 0.411s]
finished. total time: 0.634s
I think it worked just fine !
But how should I verify that I do have the stock 4.3 recovery and process succeed ?
Thanks !!
isotoper said:
Ok, done that and this is the cmd output :
sending 'recovery' (6738 KB)...
OKAY [ 0.220s]
writing 'recovery'...
OKAY [ 0.411s]
finished. total time: 0.634s
I think it worked just fine !
But how should I verify that I do have the stock 4.3 recovery and process succeed ?
Thanks !!
Click to expand...
Click to collapse
Yes, that's OK.
You see the stock recovery for yourself by turning off your device (unplug from charger if that's the case), and then press and hold its power and volume down buttons at the same time for a few seconds until you boot into bootloader. From there you can access the recovery using the volume buttons.
You can also type:
adb reboot-bootloader
In a command Window and then go to recovery using the volume buttons.
The stock recovery has an android laying on its back (or face down, can't remember right now).
By the way, a little tip: you won't see any options in the stock recovery unless you press and hold the power button and press the volume up once. I mention it because you may need it someday
Cheers
Mercado_Negro said:
Yes, that's OK.
You see the stock recovery for yourself by turning off your device (unplug from charger if that's the case), and then press and hold its power and volume down buttons at the same time for a few seconds until you boot into bootloader. From there you can access the recovery using the volume buttons.
You can also type:
adb reboot-bootloader
In a command Window and then go to recovery using the volume buttons.
The stock recovery has an android laying on its back (or face down, can't remember right now).
By the way, a little tip: you won't see any options in the stock recovery unless you press and hold the power button and press the volume up once. I mention it because you may need it someday
Cheers
Click to expand...
Click to collapse
I like seeing the kindness you shared here. For the sake of many I thank you. Though I've been helping for several years its more often I find [email protected]@holes responding as though they were born with the device and Google code 101 in their hands. I do not tolerate smartarses or lazy but I do find it nice to see people helping. Thanks again..
Sent from my Nexus 4 using xda premium
Droid2drummer said:
I like seeing the kindness you shared here. For the sake of many I thank you. Though I've been helping for several years its more often I find [email protected]@holes responding as though they were born with the device and Google code 101 in their hands. I do not tolerate smartarses or lazy but I do find it nice to see people helping. Thanks again..
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Those words mean a lot to me, thanks. It makes it worth the effort
Have a beautiful day/night, kind sir!
Cheers
Mercado_Negro, I don't have words to thank you ! This is what the forum exits for, I myself helping as much as I can to others with things that I know, instead of telling them to go and search for syntax or other solutions . You helped me so much !!
I wish that most of the forum members will be kindly like you .
Regarding to the recovery, also my previous custom recovery ("Open Recovery") looked like the stock one with an Android lying on his back and some rows of data under him so I cannot see the difference visually.
Maybe there is an app for knowing what is your system data which can verify I have the stock recovery now.
Thanks!
isotoper said:
Mercado_Negro, I don't have words to thank you ! This is what the forum exits for, I myself helping as much as I can to others with things that I know, instead of telling them to go and search for syntax or other solutions . You helped me so much !!
I wish that most of the forum members will be kindly like you .
Regarding to the recovery, also my previous custom recovery ("Open Recovery") looked like the stock one with an Android lying on his back and some rows of data under him so I cannot see the difference visually.
Maybe there is an app for knowing what is your system data which can verify I have the stock recovery now.
Thanks!
Click to expand...
Click to collapse
You're welcome!
No, that's not the recovery, that's the bootloader. Once you're there, push your volume buttons until you see an option called "Recovery Mode". one you see it, push your power button and it will take you to recovery. There you'll see another Android laying on its back but no letters below. That's the stock recovery.
The openrecovery a.k.a. TWRP is very different and you'll notice the difference right away
Yes it is, great.
Thank you very much sir.

[Q] Nexus 10 stuck on Google logo

Hi I've done stupid thing for myself:
i tried flashing 4.4.2 stock rom. coming from 4.2 (i think) did the usual format data/cache. then rebooted then it loops on google logo. I can go to recovery mode.
So are you rooted? Custom recovery? Looking to flash stock? What bootloader do you have? Ota flash? Fastboot flash?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hoygl3n said:
Hi I've done stupid thing for myself:
i tried flashing 4.4.2 stock rom. coming from 4.2 (i think) did the usual format data/cache. then rebooted then it loops on google logo. I can go to recovery mode.
Click to expand...
Click to collapse
Read this fourm I just help this user recover from the same thing!!
http://forum.xda-developers.com/showthread.php?t=2663286
lj50036 said:
Read this fourm I just help this user recover from the same thing!!
http://forum.xda-developers.com/showthread.php?t=2663286
Click to expand...
Click to collapse
demkantor said:
So are you rooted? Custom recovery? Looking to flash stock? What bootloader do you have? Ota flash? Fastboot flash?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hi i followed all the instruction till CMD and tried typing fastboot
and nothing came up.
This will help
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
This will help
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I still cant get fastboot up. ive used minimal fastboot and/or SDK Package. also changed the path for environmental variables.
So more info will help, usually the more info you give the faster your issues can be fixed
Are you in bootloader mode? I take it your using windows, what version? Has adb or fastboot ever worked before? When you type
fastboot devices
You get nothing? Can you post a screen shot of terminal, of environmental variables? Are all proper drivers installed? Does anything pop up in device manager when tablet is plugged into USB while in fastboot, recovery or os? Are you using factory USB cable?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So more info will help, usually the more info you give the faster your issues can be fixed
Are you in bootloader mode? I take it your using windows, what version? Has adb or fastboot ever worked before? When you type
fastboot devices
You get nothing? Can you post a screen shot of terminal, of environmental variables? Are all proper drivers installed? Does anything pop up in device manager when tablet is plugged into USB while in fastboot, recovery or os? Are you using factory USB cable?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry about that.
im in fastboot mode with power and both volumes pressed. i can also go into recovery mode TWRP v2.5.0.0
also rooted and yes windows 7 64 bit. recovery mode or fastboot mode . it doesnt recognized my nexus.
not sure if i have the right drivers. i cant find any drivers to download for nexus 10
Does anything pop up in device manager when tablet is plugged into USB while in fastboot, recovery or os? - No
and yes im using nexus 10 OEM cable.
i really appreciate the time to help me out with this issue.
Its no problem,
The SDK should have the drivers you need, or you can install the universal drivers made by koush or a number of others as well. Just Google search or a search xda for terms like
Nexus 10 drivers
Universal android drivers
Android naked drivers
You will find many that will work just fine for you
If in cmd you type
fastboot
And you see a list of commands than you know you have it installed
When you type
fastboot devices
And you see your serial number your good, if just a blank line then you need to get tab to communicate, this is most often a driver issue. If you can't find ones that work let me know and I'll link some to you, also you may need to uninstall old drivers and than manually install new ones, windows doesn't always do the best job of picking the correct drivers
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Its no problem,
The SDK should have the drivers you need, or you can install the universal drivers made by koush or a number of others as well. Just Google search or a search xda for terms like
Nexus 10 drivers
Universal android drivers
Android naked drivers
You will find many that will work just fine for you
If in cmd you type
fastboot
And you see a list of commands than you know you have it installed
When you type
fastboot devices
And you see your serial number your good, if just a blank line then you need to get tab to communicate, this is most often a driver issue. If you can't find ones that work let me know and I'll link some to you, also you may need to uninstall old drivers and than manually install new ones, windows doesn't always do the best job of picking the correct drivers
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
finally found the driver that works and now
i get R32D2009DAT
Im assuming thats serial number whats the next step
Google search
Android factory images
Here you will download the correct one, latest manta for the nexus 10
Then extract the contents of the zip
Now if you want to keep custom recovery that's a good idea but if you want KitKat you will need stock or at least update to the newest twrp (as you current one won't flash kk)
So if you want twrp then google search
Twrp recovery manta
And then find the latest image, 2.6.x?
Oh and its a good idea to check md5sum for both the zip from android source and for the recovery image, both will tell you what it should be in download screen and there are many ways to check, just google search
Windows md5
There is both official and none official, I personally use Linux command line and can't recall the name of the program I use for windows off hand
Also note that the following commands will wipe all from tablet, it is good to do this but if there is anything real important back it up first
Now from fastboot, enter these commands
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now find the bootloader image you extracted from the android .zip
fastboot flash bootloader nameofbootloader.img
Now if you want stock find the system image
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now find the twrp recovery image
fastboot flash recovery nameofrecovery.img
Here you can boot to new recovery and install superuser or just boot to pure stock, or if you want one of the many great custom ROMs you can boot to recovery and use adb sideload to flash one
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
google search
android factory images
here you will download the correct one, latest manta for the nexus 10
then extract the contents of the zip
now if you want to keep custom recovery that's a good idea but if you want kitkat you will need stock or at least update to the newest twrp (as you current one won't flash kk)
so if you want twrp then google search
twrp recovery manta
and then find the latest image, 2.6.x?
Oh and its a good idea to check md5sum for both the zip from android source and for the recovery image, both will tell you what it should be in download screen and there are many ways to check, just google search
windows md5
there is both official and none official, i personally use linux command line and can't recall the name of the program i use for windows off hand
also note that the following commands will wipe all from tablet, it is good to do this but if there is anything real important back it up first
now from fastboot, enter these commands
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
now find the bootloader image you extracted from the android .zip
fastboot flash bootloader nameofbootloader.img
now if you want stock find the system image
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
now find the twrp recovery image
fastboot flash recovery nameofrecovery.img
here you can boot to new recovery and install superuser or just boot to pure stock, or if you want one of the many great custom roms you can boot to recovery and use adb sideload to flash one
sent from my nexus 4 using xda premium 4 mobile app
Click to expand...
Click to collapse
never mind its fixed
you are the man!
Thank you so much!

Unbrick/Restore Amazon Fire (7in 2015 5th Gen) using Stock Recovery's ADB Sideload

for Fire 7in 2015 5th Gen Only ( KFFOWI/Ford)
Downgrading Options
If flashing Stock over a custom rom
5.3.1.0 is the safest rootable version, if original firmware is unknown. -25 Oct 2018
Fire OS 5.3.1.0 was the last rootable version for all Fires,
except the HD 10.
Do not attempt to downgrade. 24 Oct 2018
5.3.2.1 cannot be rooted, nor downgraded -28 Dec 2016
5.3.2 can not be rooted, but can be downgraded to 5.3.1.0 - 28 Dec 2016
5.3.1.0 cannot be downgraded, trying will brick - 19 Jul 2016
System version 5.1.4, 5.1.3 & 5.1.2.1 can be downgraded to 5.1.2 - 5 June 2016
System version 5.1.4, 5.1.3, 5.1.2.1, and 5.1.2 cannot be downgraded to 5.1.1 or lower
System Version 5.1.X cannot be downgraded to 5.0.X
Download Firmware
Fire (5th Generation) Software
Note:This Can be done with PC/Mac/Linux but I'm just including PC instructions for now.
Watch
[Video]How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet
Mac
How to Downgrade the Firmware on the Amazon Fire 5th gen from 5.3.2 to 5.3.1 using Mac OS
https://youtu.be/iv0VcNM8IAw
PC Steps
Install ADB Drivers and verify they are installed correctly
Setup ADB
Download the Amazon Fire Firmware and place it with your ADB.exe files
Verify that Firmware file is correct version, size, and best to check the MD5 or SHA-1 checksum
Boot into recovery: Hold Volume Down button & Power button at the same time (If it boots to Fastboot mode, use the other Volume button)
Connect to PC via usb cable
Select Sideload in recovery
Recheck Device Manager (PC)
Send adb code (change to filename of firmware)
Code:
adb sideload filename
Its going take 5- 10 minutes so be patient
Once the recovery options come back up, wipe data and cache.
Select Reboot
Reboot is going to take few minutes BE PATIENT!!
Troubleshooting
Device may not connect to PC until you select apply update from ADB,
check device manager, Fire should be listed ADB sideload or adb composite interface, when in recovery mode
If device is in adb sideload mode
Code:
adb devices
should return
Code:
A000XXXXXXXXXXX.........sideload
if not drivers are not correct
Manually Fix Drivers
Open device manager Settings>Devices>Device Manager
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
next
you may have to reboot pc
Error
cannot read 'adb sideload update-kindle-37.5.2.2_user_522054520.bin'
Make sure Firmware.bin file is in same location, that is listed in command prompt
(ex: C:\Program Files (x86)\Minimal ADB and Fastboot>)
saved
how can i get to recovery mode on 5.1.1 ?? i cannot see recovery mode when i hold power and volume up button it just says amazon and reboots again.
fastcar22 said:
how can i get to recovery mode on 5.1.1 ?? i cannot see recovery mode when i hold power and volume up button it just says amazon and reboots again.
Click to expand...
Click to collapse
That has been an issue with 5.1.1 after trying to flash a Rom with FlashFire.
Is rom booting?
Sent from my XT1060 using Tapatalk
sd_shadow said:
That has been an issue with 5.1.1 after trying to flash a Rom with FlashFire.
Is rom booting?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
nope got stuck in cyanogen icon mode. thats why ia m trying to recover to factory flash
fastcar22 said:
nope got stuck in cyanogen icon mode. thats why ia m trying to recover to factory flash
Click to expand...
Click to collapse
could try wiping cache and or data in fastboot mode
not sure that is even possible, but worth trying
need to setup adb/fastboot then
fastboot wipe cache command
Sent from my XT1060 using Tapatalk
sd_shadow said:
could try wiping cache and or data in fastboot mode
not sure that is even possible, but worth trying
need to setup adb/fastboot then
fastboot wipe cache command
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Can you give me the fastboot commands? i can get to fastbootcommand prompt to do this?
i even tried the "fastboot install filename.zip" it says it could not find the android-info.txt in the zip file.
Thanks
fastcar22 said:
Can you give me the fastboot commands? i can get to fastbootcommand prompt to do this?
i even tried the "fastboot install filename.zip" it says it could not find the android-info.txt in the zip file.
Thanks
Click to expand...
Click to collapse
Code:
fastboot erase data
fastboot erase cache
Sent from my XT1060 using Tapatalk
sd_shadow said:
Code:
fastboot erase data
fastboot erase cache
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
it does not recognize data in the command i get this message
erasing 'data'...
FAILED (remote: unknown command)
finished. total time: 0.000s
fastcar22 said:
it does not recognize data in the command i get this message
erasing 'data'...
FAILED (remote: unknown command)
finished. total time: 0.000s
Click to expand...
Click to collapse
i was afraid of that, I do not have any ideas how to fix.
could try flashing stock boot.img, then return to Amazon
Sent from my XT1060 using Tapatalk
sd_shadow said:
i was afraid of that, I do not have any ideas how to fix.
could try flashing stock boot.img, then return to Amazon
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
i even tried that it says flashing not allowed
target reported max download size of 134217728 bytes
sending 'boot' (4348 KB)...
OKAY [ 0.140s]
writing 'boot'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.156s
is there anythign else in fastboot commands to delete the files?
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
can you tell me how to get to adb mode using volume up and power button, some are sayiing that it does not show recovery command but remove finger from power button when u see logo and side load?
fastcar22 said:
i even tried that it says flashing not allowed
target reported max download size of 134217728 bytes
sending 'boot' (4348 KB)...
OKAY [ 0.140s]
writing 'boot'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.156s
is there anythign else in fastboot commands to delete the files?
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
can you tell me how to get to adb mode using volume up and power button, some are sayiing that it does not show recovery command but remove finger from power button when u see logo and side load?
Click to expand...
Click to collapse
there is no button combination, for adb
but it is not possible that adb is available during part of the boot, unlikely though
Power off then power on
try
Code:
adb reboot recovery
Sent from my KFFOWI using Tapatalk
sd_shadow said:
there is no button combination, for adb
but it is not possible that adb is available during part of the boot, unlikely though
Power off then power on
try
Code:
adb reboot recovery
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
i am sorry i meant to ask a different question, is there a way to get to stock recovery mode in 5.1.1 when flashfire is used?
fastcar22 said:
i am sorry i meant to ask a different question, is there a way to get to stock recovery mode in 5.1.1 when flashfire is used?
Click to expand...
Click to collapse
what likely happened is FlashFire moved the wipe option to last task
so the rom was wiped from system, then device rebooted
for some reason those with the 5.1.1 bootloader, lose recovery, for some reason.
if the rom was Bootable, i believe stock recovery would also still work.
right now I have no idea how to fix it.
Sent from my KFFOWI using Tapatalk
sd_shadow said:
what likely happened is FlashFire moved the wipe option to last task
so the rom was wiped from system, then device rebooted
for some reason those with the 5.1.1 bootloader, lose recovery, for some reason.
if the rom was Bootable, i believe stock recovery would also still work.
right now I have no idea how to fix it.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
thanks for your replies, i will wait for a solution until then i will stick with my bricked device
Hello, i have the same problem. Is it possible to unbrick my device with 5.1.1? Maybe is it now possible, i hope so.
Thanks a lot.
Nea
Nea123 said:
Hello, i have the same problem. Is it possible to unbrick my device with 5.1.1? Maybe is it now possible, i hope so.
Thanks a lot.
Nea
Click to expand...
Click to collapse
There seems to be a few of us with this problem but all we have is fastboot to work with so it doesn't look good, without adb i don`t know how we can flash anything.
Nea123 said:
Hello, i have the same problem. Is it possible to unbrick my device with 5.1.1? Maybe is it now possible, i hope so.
Thanks a lot.
Nea
Click to expand...
Click to collapse
All 2015 Fires are within 1 year warranty. Contact Amazon for replacement options.
I think this is not a good idea. The fire hangs on the boot screan with cm12.1 .

Help with rooting P8-lite Ale L21 dual-sim C432B564

I have a relatively new P8-lite L21 dual sim phone and I am quite happy with it. It came with C432B170 which is Lollipop I think 5.01. After a few days it updated to B172. I have unlocked the bootloader after registering with Huawei and waiting 2 weeks. Then I have successfuly rooted the phone with Kingroot phone version. Two or three weeks ago I have updated the phone to MM (6) and Emui 4 with local update (B560) that I have gotten from this forum. 2 days ago I recieved the notification of OTA B564 which went smoothly beside the fact that it reset the phone but i have succesfully restored (contacts, data etc.) All of this time since I upgraded to MM i have tried to root the phone but I was unsuccesful either with any software solution ( Kingroot, Kingoroot or others). After reading most if not all discussions on this forum and several blogs and how -tos, I tried the so called fastboot method others have recommended but here is now the gist of my problem. My phone is seen by my PC - OK so USB drivers are properly installed (by the way my PC is Win 10) and I have installed Android SDK as well as minimal ADB. When i try to flash TWRP 3.00.2 I can not do it (the message says something about not able to access or i think remote command not allowed. So since I cannot flash TWRP i am unable to put SU on the phone and root it. I hope someone more experienced and skillfull in Android world can point me in the right direction and help me. Thank you
Download mininal adb fastboot and then try to flash twrp via fastboot.
That error occurs because your adb doesn't have full permissions.
Minimal adb will solve this.
VladHD said:
Download mininal adb fastboot and then try to flash twrp via fastboot.
That error occurs because your adb doesn't have full permissions.
Minimal adb will solve this.
Click to expand...
Click to collapse
Downloaded minimal adb fastboot and installed it. Tried the procedure. Copied TWRP recovery to the minimal folder. Shift right clicked in the folder of minimal and opened command window. Adb rebooted to bootloader. Phone shows it is unlocked. The device is seen in fastboot window but flashing recovery doesn't work (same message) I am really confused. How do I give adb full permissions ?
Any way thanks in advance.
Did you activate usb debugging ?
VladHD said:
Did you activate usb debugging ?
Click to expand...
Click to collapse
Yes of course !
Try reinstalling drivers with universal adb.
Are you sure your bootloader is unlocked?
Type fastboot devices and let me know the output.
VladHD said:
Try reinstalling drivers with universal adb.
Are you sure your bootloader is unlocked?
Type fastboot devices and let me know the output.
Click to expand...
Click to collapse
The drivers were reinstalled. My bootloader shows unlocked on bootloader (bottom of fastboot screen). Fastboot devices does nothing. Adb devices shows my phone serial number correctly (I have it written down). But then when i try to flash recovery it is unsuccessfull. It says "FAILED (remote: Command not allowed)"
What is the command that you typed..?
Fastboot flash recovery xxx.img
Sent from my ALE-L21 using XDA-Developers mobile app
amageek said:
What is the command that you typed..?
Fastboot flash recovery xxx.img
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Fastboot flash recovery recovery. img I renamed the twrp 3.0 to recovery.img
doomking_99 said:
Fastboot flash recovery recovery. img I renamed the twrp 3.0 to recovery.img
Click to expand...
Click to collapse
sorry, if you've already answered this, but you can also do it by flashify... flash the recovery image via flashify (root needed though)
amageek said:
sorry, if you've already answered this, but you can also do it by flashify... flash the recovery image via flashify (root needed though)
Click to expand...
Click to collapse
Thanks, but my problem is that i cannot root without installing TWRP is my understanding.
doomking_99 said:
Thanks, but my problem is that i cannot root without installing TWRP is my understanding.
Click to expand...
Click to collapse
ahhh... sorry mate, dont know the solution.. but try re-installing adb drivers again ...
Are you logged as adminstrator on pc?
Try to plug usb into different slots.
VladHD said:
Are you logged as adminstrator on pc?
Try to plug usb into different slots.
Click to expand...
Click to collapse
I am and I have. I am stumped. Obviously something is wrong with windows permissions I think. Is it possible to put recovery. img on sd card or on phone and flash recovery from the phone ?
This is the output every time no matter which usb port
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
W3D7N15C08019820 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.624s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.627s
C:\Program Files (x86)\Minimal ADB and Fastboot>
The thing i don't understand is why fastboot command doesn't show device while adb command does.
You said that you have android sdk too... Have you tried using that?
If it doesn't help them try to do it on other computer or reset your windows...
Sent from my ALE-L21 using XDA-Developers mobile app
amageek said:
You said that you have android sdk too... Have you tried using that?
If it doesn't help them try to do it on other computer or reset your windows...
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you but i have tried with SDK and with minimal and always the same result as i posted. I will try and do it on my wife's PC.
doomking_99 said:
Thank you but i have tried with SDK and with minimal and always the same result as i posted. I will try and do it on my wife's PC.
Click to expand...
Click to collapse
Sorry for the zombiethreading here, but... what whas the solution? I'm curious
For the time being there is no solution. Can not flash TWRP - phone not rooted
doomking_99 said:
For the time being there is no solution. Can not flash TWRP - phone not rooted
Click to expand...
Click to collapse
Weird... i can't think of anything else myself that hasn't been said. Perhaps... redownloading twrp? Maybe the image is corrupted by something... ot's a long shot because ot should flash everytging that comes its way. But it's the only thing you hven't tried.

Categories

Resources