Database Develop

[Q] Bricked Phone

Hi,
I recently got asked by a friend to flash his google nexus one phone. like a mug i said yes and now i have a issue where it turns on, vibrates 7 times and stays at the splash screen with the x on it. I can boot into the fast boot / recovery mode but nothing works.
this happened after i tried to root the phone, it said waiting for device and didnt do anything so i killed the app (Superoneclick) the phone disappeared from device manager and now wont go past the splash screen.
Does anyone have any idea how i can get it back? .. thanks in advance for any help.
James

I'm guessing, since you used S-O-C, the bootloader is not unlocked. The only way I know how to fix it is if you OEM unlock it. You'll need fastboot and your Android SDK setup correctly.
Once you have the setup done, change directories to the tools folder, wherever you put your sdk. Boot your phone into fastboot by holding the trackball while powering it on.
Code:
cd C:\asdk\tools\
Plug your phone into USB, and check if the computer sees it
Code:
fastboot devices
Unlock the bootloader (THERE IS NO GOING BACK! You can never re-lock a Nexus)
Code:
fastboot oem unlock
Now you can flash a boot.img and system.img (preferably pre-rooted) from fastboot, and it should boot normally. If the phone boots, the phone is perma-rooted, and won't need any other rooting procedure (you just need to flash a rooted rom). Next time, be a little more careful

Hi wdfowty
at running the risk of asking for more help and making you cross could you post some links to these downloads?
I am a total newbie to these phones and want to make sure i have the right apps.
thanks again for the help and the quick response... and if i manage to get this phone back believe me it will be the last one i try to flash !!
cheers
James

Nah, you've got me wrong. I'm all about helping people that are willing and able to be helped.
Follow this guide, it'll walk you through the steps to set up your sdk and unlock the bootloader. The guide is a little dated, so the info might not be 100%, but it's generally everything you'll need to know. If you get stuck, feel free to ask.

Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james

jamesabennett said:
Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james
Click to expand...
Click to collapse
With the latest version of the SDK tools, they changed the directory for adb and fastboot. Unfortunately I'm not on my Windows machine... but check in the directory where you have the SDK extracted to and look for a platform-tools directory (iirc). From there, you should see fastboot.
So basically where it says this "Type: cd C:\android-sdk-windows\tools" change it to "C:\android-sdk-windows\platform-tools". Keep in mind that directory name may change... again, I'm not on my Windows machine right now.

Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James

jamesabennett said:
Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James
Click to expand...
Click to collapse
Have you flashed the recovery image using fastboot, or did you only copy the recover image to the sdcard? Step IV in that guide.

It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!

I ran the fastboot command and used the flash image ending 2.0.0
this is driving me round the bend !!

What happened when you used the fastboot flash command? Did you see a bar on the top right of the phone?

wdfowty said:
It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!
Click to expand...
Click to collapse
i do that and it accepts the recovery file and the progress bar goes up on the right hand side and the cmd prompt says its all good. then when i select recovery the phone goes to the black background with the four coloured cross and the unlocked padlock, vibrates 7 times and just hangs on that screen
beleive it or not it booted up a moment ago and the phone worked like it did before with v2.2 on it. so i am happy now it can be recovered... i just dont know what to do to straighten it out!

yes. the bar goes up on the right hand side of the phone. and i have definitely unlocked it as it now says unlocked at the top of the menu.

Have you tried to reimage the phone with the passimg method? Directions are provided in the wiki, under the unlock/restore heading:
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Follow PASSIMG method (filename is case sensitive).
The link to the files is on the word "here" on step 2.
Use FRG33.
Sent from my Nexus One using XDA App

stuck at red logo

Hey guys,
i did stupid things witch my razr i and now i'm completely lost…maybe someone can help?
I've been impatient enough to try to flash the leaked jb rom 3 days ago. That did'nt work
No, whenever i power up the phone it shows the red M logo and nothing happens.
I can power it down by holding vol+down and power for more than 4 seconds.
If i release the keys, it goes back to te red M,
If i keep holding vol+down it boot s into AP fastboot flash mode (secure boot) 20.0f
i can choose recovery and that'll work, but i don't have an update for external storage. rebooting from there leads to red M.
Normal Powerup, Factory and BP Tools are choosable, log says Booting into… but nothing happens after that, i'll stay in fastboot.
Power off works.
I tried to flash various images via »fastboot flash boot/recovery/system«, but nothing worked out.
I flashed the files from Razri_Root_Linux, two files (retail central europe) from here sbf.droid-developers, but nothing helped, every reboot leads to the red M.
I read about RSD-Lite, tried to install it under Win7, got it, but was lost after the Program always complained about an invalid xml.
Since i don't own that machine i went back to my linuxbox where i found sbf_flash, but i don't get it how to put the pieces together (which file/s to use)
Any hints on how to go from here?
[EDIT:] I downloaded 91.2.26001.Retail.en.EU.zip and did all the steps from flashandboot.bat, read
fastboot flash boot
fastboot flash system
fastboot flash recovery
next step ist to select recovery, did this an cwm comes up, sideloaded RAZRiRoot2.zip everything is pisitively quited, no errors are shown.
reboot leads to red M
wiped data/factory reset, reboot
red Logo.
I'm completely lost, please help
[\EDIT]
greetings, D.

I had same problem
Hello.
I had same problem because I did very stupid thing. I flashed homemade JB and because some apps don´t work I tried downgrade my i to ICS back....
My i stucked at the red M then I tried same thing as you and phone still booted into red M.
So I tried in windows cmd and FlashAndRoot.bat from this .zip "91.2.26001.Retail.en.EU - 4.1.2" it did nothing, but I tried to choose in fastboot mode BP Tools, then my i booted and started to flash JB what I can see in command window. Phone was still connected to PC. After next reboot my phone has work normally with JB.
I hope to help you. Let me know.
Lucki

Hi Lucki
thanks for jumping by.
Lucki_X said:
Hello.
So I tried in windows cmd and FlashAndRoot.bat from this .zip "91.2.26001.Retail.en.EU - 4.1.2" it did nothing, but I tried to choose in fastboot mode BP Tools,
Click to expand...
Click to collapse
I tried this, and display on razr i says »Booting into BP Tools mode…«
and nothing more happens, display stays on…
and after some time pc automounts a "cd-rom drive" with some motorola files (Autorun.inf MDMSetup.xml MotorolaDeviceManagerSetup.exe MDMSetup.ini MotorolaDeviceManager_2.2.28)
but it still won't reboot…
i don't know.

Hi.
I had opened command window, "FlashAndRoot.bat" was running (I pressed any key) process was running (it means freezing ) and at this time I chose in fastboot booting into BP tools mode. My phone did restart and after it "FlashAndRoot.bat" process started to flash JB. After flashing my phone is going normally with JB. But some apps don´t work in JB.
Lucki

Lucki_X said:
Hi.
I had opened command window, "FlashAndRoot.bat" was running (I pressed any key) process was running (it means freezing ) and at this time I chose in fastboot booting into BP tools mode. My phone did restart and after it "FlashAndRoot.bat" process started to flash JB. After flashing my phone is going normally with JB. But some apps don´t work in JB.
Lucki
Click to expand...
Click to collapse
Doesn't work. :crying:
since i use linux i opened FlashAndRoot.bat in texteditor and executed the comands from there in terminal
only chance for the script to stop and wait is IMHO(correct-me-if-i'm-wrong) "adb wait-for-device push RAZRiRoot2.zip /sdcard/RAZRiRoot2.zip & adb reboot bootloader"
but that message "Booting into BP Tools mode…" just stays there forever, or does it take longer than 5minutes?

dogo77 said:
but that message "Booting into BP Tools mode…" just stays there forever, or does it take longer than 5minutes?
Click to expand...
Click to collapse
In my case it booted within 10 second and ran.
I am noob, I am writing just my experience. I couldn´t give you another advice, sorry.

I'm not sure how far the real installation went, but i would find Windows computer, get RSD (6.0-6.14) and try to flash ICS first. If failed due to impossibility of downgrading, then try JB. While you are able to boot to Recovery - don't loose hope yet

okaban said:
I'm not sure how far the real installation went, but i would find Windows computer, get RSD (6.0-6.14) and try to flash ICS first. If failed due to impossibility of downgrading, then try JB. While you are able to boot to Recovery - don't loose hope yet
Click to expand...
Click to collapse
Yeah. I'm still stuck at the red logo, or indeed, at a blueish "Bootloader unlocked warnig" message since i was able to install parts of an image from sbf.droid-developers. But flashing always fails while trying to flash system.img_signed.
After reading and trying a lot these last days i think i have to install windows somewhere just to get rsd-lite to run.
sbf_flash for linux didn't work for me and fastboot gives stange warnings about "Invalid sparse file format at header magi"…
so i'll give rsd a try before i give up. As i read in posts by HSDPilot, this is the only tool that works
thanks for your help!

Phone can't boot stuck at "Your device is booting now" Please Help

Hello, I wanted to install TWRP and ROOT my phone. I flashed TWRP using adb terminal. But when I tried to boot into TWRP it was stuck on "Your device is booting now..". Then if I held the power button for few secs it rebooted normally. So I tried to google it and I found adb command that reboots to recovery
Code:
adb reboot recovery
. When I executed the command it rebooted to the "Your device is booting now.." screen and it stays like this forever. No button combination works to reboot the phone if i hold power button it reboots shows honor logo and then shows the "Your device is booting now.." screen. I waited for the battery to drain and then i put the phone on charger and when I tried to boot it, it was the same. Now when I try to reboot the phone it shows ultra low baterry symbol and then boots to "Your device..." screen.
NEM-L21; EMUI 5.0; 7.0 Nougat

Which twrp you flashed? Check the correct twrp in my signature for honor 5C repository.

TassiloBalbo said:
Hello, I wanted to install TWRP and ROOT my phone. I flashed TWRP using adb terminal. But when I tried to boot into TWRP it was stuck on "Your device is booting now..". Then if I held the power button for few secs it rebooted normally. So I tried to google it and I found adb command that reboots to recovery . When I executed the command it rebooted to the "Your device is booting now.." screen and it stays like this forever. No button combination works to reboot the phone if i hold power button it reboots shows honor logo and then shows the "Your device is booting now.." screen. I waited for the battery to drain and then i put the phone on charger and when I tried to boot it, it was the same. Now when I try to reboot the phone it shows ultra low baterry symbol and then boots to "Your device..." screen.
NEM-L21; EMUI 5.0; 7.0 Nougat
Click to expand...
Click to collapse
I think you have flashed wrong twrp.download correct twrp and flash it via adb fastboot

hassanjavaid8181 said:
I think you have flashed wrong twrp.download correct twrp and flash it via adb fastboot
Click to expand...
Click to collapse
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...

Crocni said:
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...
Click to expand...
Click to collapse
Meaning you can boot to fastboot but your pc doesn't recognise it?

Crocni said:
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...
Click to expand...
Click to collapse
Did you try all method to going in fastboot.by adb fastboot command or by pressing vol- and power button?

Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support

Crocni said:
Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support
Click to expand...
Click to collapse
Glad that you fix your device.
If it is not bothering you let it be and enjoy using your phone.

Crocni said:
Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support
Click to expand...
Click to collapse
Can you please explain to me how did you managed to boot into fastboot? I tried waiting for the battery to drain completely. Now I can't fully charge my phone. When i connect it with charger. It starts normally charging like it would with 0% battery then after a few moments the honor logo shows up and then the screen "Your device.." shows. When I try vol- and powerbutton it vibrates and shows the red lightbolt then after few moments it boots the same way into the your device screen. When I connect it to the pc it doesn't react. I don't even hear the classic windows beep sound.

TassiloBalbo said:
Can you please explain to me how did you managed to boot into fastboot? I tried waiting for the battery to drain completely. Now I can't fully charge my phone. When i connect it with charger. It starts normally charging like it would with 0% battery then after a few moments the honor logo shows up and then the screen "Your device.." shows. When I try vol- and powerbutton it vibrates and shows the red lightbolt then after few moments it boots the same way into the your device screen. When I connect it to the pc it doesn't react. I don't even hear the classic windows beep sound.
Click to expand...
Click to collapse
Try removing the usb cable and then try to biot to fastboot. What about erecovery

shashank1320 said:
Try removing the usb cable and then try to biot to fastboot. What about erecovery
Click to expand...
Click to collapse
When I remove the usb cable it's still the same. When i try to press the power button it vibrates shows the low battery red lightbolt and dies. If you mean by erecovery emui recovery, then it looks like it's not installed.

TassiloBalbo said:
When I remove the usb cable it's still the same. When i try to press the power button it vibrates shows the low battery red lightbolt and dies. If you mean by erecovery emui recovery, then it looks like it's not installed.
Click to expand...
Click to collapse
You need to press power + volume down key to boot into fastboot. Keep trying 4-5 times sometimes it takes due to wrong press

shashank1320 said:
You need to press power + volume down key to boot into fastboot. Keep trying 4-5 times sometimes it takes due to wrong press
Click to expand...
Click to collapse
So I managed to get into the fastboot. Where can I get boot.img, recovery.img and system.img? I have downloaded some update.zip files from this russian site (first 5) http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=NEM-L21&firmware_page=0. But I don't have boot, recovery and system images in these zips.
I also tried reboot in fastboot but its still the same:
fastboot devices
8SC4C16A13006909 fastboot
fastboot reboot
rebooting...
finished. total time: 0.026s[/CODE]

TassiloBalbo said:
So I managed to get into the fastboot. Where can I get boot.img, recovery.img and system.img? I have downloaded some update.zip files from this russian site (first 5) http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=NEM-L21&firmware_page=0. But I don't have boot, recovery and system images in these zips.
I also tried reboot in fastboot but its still the same:
fastboot devices
8SC4C16A13006909 fastboot
fastboot reboot
rebooting...
finished. total time: 0.026s[/CODE]
Click to expand...
Click to collapse
Meaning the fastboot is accessible.
Now you have firmware zip, extract it amd you will get few files. Use dload method as given in my signature and you are good to go.
Else use Huawei extractor and browse to update.app you just got in above downloaded zip. You will get boot, recovery, system img you need.

I downloaded some firmware versions and extracted them. I don't know which is for my device. So I tried one of them. I flashed boot.img and recovery.img but I din't flashed the system.img, becouse it was too big. When I tried to reboot the phone it was the same. The fastboot was no longer accessible. I put the phone into servis but they didn't fixed it. it's the same but I can enter erecovery

TassiloBalbo said:
I downloaded some firmware versions and extracted them. I don't know which is for my device. So I tried one of them. I flashed boot.img and recovery.img but I din't flashed the system.img, becouse it was too big. When I tried to reboot the phone it was the same. The fastboot was no longer accessible. I put the phone into servis but they didn't fixed it. it's the same but I can enter erecovery
Click to expand...
Click to collapse
Please flash only files for your device and nothing else. Did you try dload method?
Give me model and build number, will get the correct files for you

shashank1320 said:
Please flash only files for your device and nothing else. Did you try dload method?
Give me model and build number, will get the correct files for you
Click to expand...
Click to collapse
NEM-L31 but I don't know the build number

TassiloBalbo said:
NEM-L31 but I don't know the build number
Click to expand...
Click to collapse
Build number is necessary to get right files..

hassanjavaid8181 said:
Build number is necessary to get right files..
Click to expand...
Click to collapse
I know. So do you think it's dead?

TassiloBalbo said:
I know. So do you think it's dead?
Click to expand...
Click to collapse
You should try huawei service center....

Any help, i may have bricked my fire

Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks

vetteguy82 said:
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
Click to expand...
Click to collapse
Permanently bricked; can't downgrade below 5.4. Sell it for parts or take it to the target range.

Thanks
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks

vetteguy82 said:
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
Click to expand...
Click to collapse
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>

thanks
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Davey126 said:
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
Click to expand...
Click to collapse

vetteguy82 said:
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Click to expand...
Click to collapse
You need to install this tool on the host PC. Make note of the installation folder as you will need to execute the fastboot command from there. You'll also need to copy any necessary files (eg: twrp image) to that folder unless versed in referencing other folders from the command prompt.
Keep in mind it is highly unlikely your looping device will be able to boot twrp. Only the earliest models had this vulnerability which Amazon quickly plugged.

Question Phone stuck in boot loop, unable to get to FastBoot

Hi,
Sequence of steps:
1. Extracted the boot.img from payload.bin and flashed it to the phone. At this point I was able to get into Fastboot
2. While in Fastboot I went into advanced and wiped the "System Settings", and that's when the trouble started - now the phone is stuck into a boot loop forever, I do however get the options to "Power Off" and "Restart"
3. But none of the options above in Step 2 is able to bring me back to Fastboot (and hence into fastbootd either)
Question: How can I get the phone into Fastboot Mode - have tried MSM Tool v4 as well, but that doesn't even recognize the phone

Edit - This seems to have been resolved now, think I had to press Vol Down + Power instead of Vol Up + Power
Was able to enter into Fastbootd as well, will try to proceed with unbricking the phone with a fresh mind tomorrow

FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong

VoltaGe86 said:
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong
Click to expand...
Click to collapse
Thats right, "fastboot boot <file_name>" loads temporarily your custom recovery of choice. After rebooting your phone, the custome recovery is gone.
Otherwise, the command "fastboot flash <file_name> recovery" flashs permamently your custom recovery of choice to your device.

Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice

Zekedw said:
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
Click to expand...
Click to collapse
I have exactly the same issue, on a nord 2

How about vol+/vol-&power all together? When stuck that gives me some screen that allows start, recovery (the one where you can enter advanced settings I expect from your description) and bootloader booting.