I am having Nokia 8 TA-1004. I had the same issue as many of them. The phone restarts often whenever I open an app or start interacting with UI. It was so frustrating. But it was find when I am using it while charging. And there is absolutely no problem in it. Many of them were confused whether it is motherboard issues or update issue becuz the problem started only after Feb security update that came last year. Since then I was struggling and I gave up.
Today I had an idea of using custom rom to see whether the problem can be fixed. I searched for custom roms officially there I none. But I got a Pixel Experience Rom, unofficial ofcourse. So I went on with unlocking the bootloader so I followed the official steps and unlocked it. While installing TWRP I was but confused with it becuz it needs to be booted with recovery.img temporarily and flashed with recovery.zip in TWRP.
I wrote the command :
fastboot flash recovery recovery.img it just failed.
I wrote : fastboot boot recovery.img but nothing turned up when I went to recovery mode.
But in one article I found a command :
fastboot flash boot recovery.img
It booted to twrp but I was unaware that I flashed it instead of boot.img and I can't acces MTP to tranfer file to my phone. So I try to boot into os and copy the recovery.zip so that I could install it. But that's it. It went into BOOTLOOP. I can't access the fastboot nor recovery. It just vibrates startes shows powered by Android and loops this. I tried everything to enter fastboot or recovery, if I get atleast one shot of recovery or fastboot I could bring it back.
It loops again and again switches on shows "powered by Android" switches off that's it. I will be so pleased if some have some sort of solution. It will be great to hear suggestions about it.
Thanks in advance.....
You have fallen victim to the A/B partition scheme. It is correct that the TWRP image needs to be first booted with fastboot and from there the .zip file must be flashed. This is because in A/B devices there is no recovery partition (that is why the command "fastboot flash recovery recovery.img" failed). The recovery instead lives in the boot partition together with the kernel. By typing "fastboot flash boot recovery.img" you essentially have deleted the kernel of the device which causes the bootloop. I would suggest you to read this xda article which will help you understand the details: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/ .
Now the only way to fix this is to repair the boot partition of the phone. This can be done with a tool known as NOST: https://github.com/StollD/NOST . (Note that you will lost all of your data with this method so keep this in mind). Once you have downloaded the tool you need to get a complete Nokia 8 firmware image. The one that worked for me was this: https://github.com/resident-nokia/t-virus/releases/tag/5150-revert . Once you have both installed, launch NOST, follow the instructions and select the firmware file. On the screen after that, click the arrow down button next to "Normal Download" and tick the box labeled as "Erase User Data". Now to proceed you must enter download mode. This is a bit tricky in your current situation but it can be done in 2 ways:
1. Wait until your battery dies down. Then hold down the volume down button and connect the phone to a computer.
2. (Bit tricky to pull off and I managed to do it) Hold down the power button until the screen goes black. Then immediately hold down the volume down and connect to a computer.
Once you are in Download Mode disconnect and reconnect the phone to the computer and click the Next button in NOST. If all goes well this will repair your partitions and boot you back to the stock rom.
Hope this helps.
emufan4568 said:
You have fallen victim to the A/B partition scheme. It is correct that the TWRP image needs to be first booted with fastboot and from there the .zip file must be flashed. This is because in A/B devices there is no recovery partition (that is why the command "fastboot flash recovery recovery.img" failed). The recovery instead lives in the boot partition together with the kernel. By typing "fastboot flash boot recovery.img" you essentially have deleted the kernel of the device which causes the bootloop. I would suggest you to read this xda article which will help you understand the details: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/ .
Now the only way to fix this is to repair the boot partition of the phone. This can be done with a tool known as NOST: https://github.com/StollD/NOST . (Note that you will lost all of your data with this method so keep this in mind). Once you have downloaded the tool you need to get a complete Nokia 8 firmware image. The one that worked for me was this: https://github.com/resident-nokia/t-virus/releases/tag/5150-revert . Once you have both installed, launch NOST, follow the instructions and select the firmware file. On the screen after that, click the arrow down button next to "Normal Download" and tick the box labeled as "Erase User Data". Now to proceed you must enter download mode. This is a bit tricky in your current situation but it can be done in 2 ways:
1. Wait until your battery dies down. Then hold down the volume down button and connect the phone to a computer.
2. (Bit tricky to pull off and I managed to do it) Hold down the power button until the screen goes black. Then immediately hold down the volume down and connect to a computer.
Once you are in Download Mode disconnect and reconnect the phone to the computer and click the Next button in NOST. If all goes well this will repair your partitions and boot you back to the stock rom.
Hope this helps.
Click to expand...
Click to collapse
hey, the same thing has happened with my realme c2. I tried to install gsi in it but ended but making it go into boot loop into recovery mode and there is no recovery in it so it keeps on turning off and then restarts and goes into recovery mode again. I can't even access fastboot mode. how to solve this?
Sathvk KVS said:
hey, the same thing has happened with my realme c2. I tried to install gsi in it but ended but making it go into boot loop into recovery mode and there is no recovery in it so it keeps on turning off and then restarts and goes into recovery mode again. I can't even access fastboot mode. how to solve this?
Click to expand...
Click to collapse
Unless you erased the recovery partition yourself, the recovery still exists. Try completely shutting off your phone (waiting for the battery to drain, or pressing the power button for an extended period of time, I don't know the key combinations for your Reame C2) and then enter fastboot mode to fix up the partition that were messed up
emufan4568 said:
Unless you erased the recovery partition yourself, the recovery still exists. Try completely shutting off your phone (waiting for the battery to drain, or pressing the power button for an extended period of time, I don't know the key combinations for your Reame C2) and then enter fastboot mode to fix up the partition that were messed up
Click to expand...
Click to collapse
I have the same problem on a redmi 9 after flashing twrp BUT only partition A
emufan4568 said:
Unless you erased the recovery partition yourself, the recovery still exists. Try completely shutting off your phone (waiting for the battery to drain, or pressing the power button for an extended period of time, I don't know the key combinations for your Reame C2) and then enter fastboot mode to fix up the partition that were messed up
Click to expand...
Click to collapse
cant enter fastboot with key combinations or any other? if i plug in usb it just starts the bootloop again?
smiley.raver said:
cant enter fastboot with key combinations or any other? if i plug in usb it just starts the bootloop again?
Click to expand...
Click to collapse
yep, the guy from service tries to rewrite the motherboard now
Officer X said:
yep, the guy from service tries to rewrite the motherboard now
Click to expand...
Click to collapse
Wat happened actually. I wanted to get my phone serviced, but im scared of the price to repair. They said if the chip still can receive data they will try repair it. But if the it broken, they have to repair the motherboard. IM SCARED THO.
LeBronLaS said:
Wat happened actually. I wanted to get my phone serviced, but im scared of the price to repair. They said if the chip still can receive data they will try repair it. But if the it broken, they have to repair the motherboard. IM SCARED THO.
Click to expand...
Click to collapse
LeBronLaS said:
You might as well tinker around with it my phone did that same thing it didn't have fastboot and computer couldn't see it through ADB drivers but I kept messing with it and kept flashing it and I got it back
Click to expand...
Click to collapse
Oppo Stock ROM
Find Oppo and Realme Stock ROM (Firmware) for various Oppo/Realme Devices. All the Oppo/Realme Firmwares listed are available for free.
oppostockrom.com
This website has real me and Oppo 0FP files
hi evreyone
i have same problem with my galaxt tab s6, Do You have any solution ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
emufan4568 said:
You have fallen victim to the A/B partition scheme. It is correct that the TWRP image needs to be first booted with fastboot and from there the .zip file must be flashed. This is because in A/B devices there is no recovery partition (that is why the command "fastboot flash recovery recovery.img" failed). The recovery instead lives in the boot partition together with the kernel. By typing "fastboot flash boot recovery.img" you essentially have deleted the kernel of the device which causes the bootloop. I would suggest you to read this xda article which will help you understand the details: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/ .
Now the only way to fix this is to repair the boot partition of the phone. This can be done with a tool known as NOST: https://github.com/StollD/NOST . (Note that you will lost all of your data with this method so keep this in mind). Once you have downloaded the tool you need to get a complete Nokia 8 firmware image. The one that worked for me was this: https://github.com/resident-nokia/t-virus/releases/tag/5150-revert . Once you have both installed, launch NOST, follow the instructions and select the firmware file. On the screen after that, click the arrow down button next to "Normal Download" and tick the box labeled as "Erase User Data". Now to proceed you must enter download mode. This is a bit tricky in your current situation but it can be done in 2 ways:
1. Wait until your battery dies down. Then hold down the volume down button and connect the phone to a computer.
2. (Bit tricky to pull off and I managed to do it) Hold down the power button until the screen goes black. Then immediately hold down the volume down and connect to a computer.
Once you are in Download Mode disconnect and reconnect the phone to the computer and click the Next button in NOST. If all goes well this will repair your partitions and boot you back to the stock rom.
Hope this helps.
Click to expand...
Click to collapse
Thanks, I´ts served for me the second option.
So I made the fatal mistake of trying to flash the cfdroid rom for android 12. I failed to realise that I needed T-Virus 2.0 for it to work. I already had T-Virus 1.0, but using TWRP, I wiped out the current Android 9 custom Rom I was running. The flashing of the new one obviously failed, but now im stuck in a bootloop and can no longer boot into recovery at all. I tried letting the phone die but as soon as it gets power again it enters the boot loop and wont eve boot into download mode no matter the key-combination. I am trying to flash T-Virus 2.0 on my linux machine but it if it cant even boot into download mode then it seems I am doomed. The phone has been sitting and practically dead for 2 weeks now. Anyone got any suggestions? I'm running out of options to try.
EDIT: Okay, I managed to get to download mode after posting this. But I am getting a `<Waiting for any device>` message using the `flash_T-Virus_Linux.sh` script. Seems like the phone is not picked up.
EDIT2: I decided to run the script as root and it is now stuck at
Code:
Flashing T-VIRUS partition-table
Sending 'partition:0' (44 KB)
EDIT3: It finally worked. I basically had to unplug the phone, turn it off again and make sure I run the `flash_T-Virus_Linux.sh` script using root privileges. Now I can boot into the phone with a Pixel Experience rom.
I am so rusty, the last time I modded this phone was when Android 9 was a thing.
Thanks so much, Amazing, It work!!! cororectly explained, thanks!!
You know a twrp for Redmi Note 9? I need to unloock again, but i want to set custom rom, because the stock room have problems. If you know letne know please, thanks again
Have the Sam for my older Tab A 10.1 (T510). Flashed an updated TWRP, rebooted, now it keeps rebooting. Powerbutton nor volumes up and down don't work. Just rebooting rebooting...hioefukky when battery goes empty, I can try stuff.
My infinix note 12 g96 is stuck in boot loop saying damage state your device has been locked and can’t be trusted and Just keeps restarting
I recently unlocked the boot loader and immediately rooted using a flashed boot image of the phone I flashed with magisk
I didn’t restart after unlocking and now it’s stuck in boot loop and I can’t enter recovery mode with the hardware keys please I need help
Rayde101 said:
My infinix note 12 g96 is stuck in boot loop saying damage state your device has been locked and can’t be trusted and Just keeps restarting
I recently unlocked the boot loader and immediately rooted using a flashed boot image of the phone I flashed with magisk
I didn’t restart after unlocking and now it’s stuck in boot loop and I can’t enter recovery mode with the hardware keys please I need help
Click to expand...
Click to collapse
me too i have the same problem with my infinix note 12 g96
Please let me know if you've fixed yours i need help
Sounds like u need to flash stock rom, or somhow update with earlier firmware
Related
Last weeknd, the battery of my Nexus one was drained during the night and it didn´t boot next morning.
It has the same symptoms that I've seen in other articles. I press the power button, it vibrates, I see the logo of nexus and that's it. I can boot with 'Power + trackball' and select 'clear storage' or 'recovery', but the result is always the same.
I did the following tests.
- flash recovery image recovery-RA-nexus (vers 1.7.0.1, 1.7.0, 1.5.3) or recovery-RA-cyan.
- flash some versions of radio image, combined with all versions of image recovery.
- flash some versions of system. (At this point, I already very frustrated).
None of this tests changed the behavior of the phone. There is no way to reach the menu "Android system recovery".
Does anyone of those who have had the same problem, has managed to fix it?
If I have to buy another phone, I would be sure there is no way to fix this.
Did you try running adb logcat from your computer to see if it shows any errors?
Does 'Adb logat' work so early?
I try to use adb but I could never find my device.
With 'fastboot devices' find it, but 'adb devices' don´t.
I think that 'adb logcat' starts to work later.
Anyway, I try it right now.
[email protected]:/home/xxx/android-sdk-linux_86/tools# ./adb-linux logcat
* daemon not running. starting it now *
* daemon started successfully *
- waiting for device -
'Normal boot' or 'Recovery' the result is always the same.
Wipe everything, install a ROM, have a clean start.
As long as it works and gets into recovery - the phone is alive.
Sorry Jack_R1
I can`t wipe anything. Because I can´t reach the menu "Android system recovery".
I can flash all partions (boot, system, recovery, radio) using fastboot. This should leave my phone as the first day. Not so.
I think that my problem is more difficult than usual. The phone seems completely locked. Nothing causes no effect.
You could try the PASSIMG.zip method.
I try the PASSIMG.zip method, but it dont changes anything
I made a video of the process.
"Nexus one brick" id '4UU5F6w51Vc' on youtube. (I cant write links!!!)
Maybe, so more people read this. This is terrible.
Ok i have exactly the same problem.. never boot's further then the static X
Tried everything i could think of now..
Can still upload new boot/radio/recovery/system image.. but nothing changes..
No-one has any idea?
bump~ I had the same exact issue, except mines overheated. DUnno why. Im in the same boat as you are. Hope someone can help.
It's difficult to work out the actual problem here.
Is it:
a) that you hang at the static X (known issue)
or
b) that you can't boot into recovery from HBOOT
or
c) both of the above
I have the some problem exactly
It boots in fastboot mode, but will not boot into recovery mode. HELP PLEASE!!
mintuson said:
It boots in fastboot mode, but will not boot into recovery mode. HELP PLEASE!!
Click to expand...
Click to collapse
Don't try and "boot" it into recovery, select "Recovery" from the HBOOT screen... what happens? Exactly.
djmcnz said:
Don't try and "boot" it into recovery, select "Recovery" from the HBOOT screen... what happens? Exactly.
Click to expand...
Click to collapse
He's made a video about it:
http://www.youtube.com/watch?v=4UU5F6w51Vc
To the OP:
Did you try to boot directly into the recovery (hold vol-down instead of the trackball when powering up)
Also... what happens if you remove the sd card?
pikipirs said:
He's made a video about it:
http://www.youtube.com/watch?v=4UU5F6w51Vc
To the OP:
Did you try to boot directly into the recovery (hold vol-down instead of the trackball when powering up)
Also... what happens if you remove the sd card?
Click to expand...
Click to collapse
Difficult to read that... yeah, remove the sd card... or rather, what happens without a pasimg file?
I think the problem lies in an incompatible Hboot (0.35 from korean radio prob) with bootloader..
I got mine to boot again with the last cyan boot loader. But now my android 2.1 stock wich i installed because i didn't know what else to do is not compatible with my radio/boot/hboot and my SD-card and USB connection when the phone is booted don't work..
I think the recovery won't work because the recovery can't detect the SD-card because of incompatibility with Hboot 0.35
Hi everyone.
Answers:
djmcnz - I hang at the static X and I can't boot into recovery from HBOOT.
djmcnz - If I "boot" it into recovery and select "Recovery" from the HBOOT screen, I will hang at the static X.
pikipirs - If I remove the sdcard (or without a pasimg file), nothing changes. I will hang at the static X.
I discovered a curious behavior.
If I boot with battery, the phone will hang at the static X, but if I boot with battery and electric wire, the phone will hang at the static X and reboot after 30aprox seconds. Then the phone starts a reboot loop.
I thought that it was a battery problem, but I probe with two different batteries with the same results.
How much I charged for fix this in the service shop?
Have you tried downgrading your bootloader?
http://forum.xda-developers.com/showthread.php?t=726258
My bootloader is already in version 0.33.0012. This method uses adb comands. I can´t detect my phone with adb
I see this on fastboot menu.
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.33.0012
MICROP-0b15
TOUCH PANEL-SYNT0103
RADIO-4.04.00.03_2
Dec 17 2009,13:05:23
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
jggrnaut said:
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
Click to expand...
Click to collapse
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
berndblb said:
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
Click to expand...
Click to collapse
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
jggrnaut said:
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
Click to expand...
Click to collapse
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
berndblb said:
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
Click to expand...
Click to collapse
Well it has gotten worse and I think I have lost fastboot now. I downloaded the CWM from part 1 above and flashed it in fastboot. I typed fastboot reboot and now I am stuck in a bootloop still. It says "The device is unlocked" at top of Asus splash screen for about 15 seconds, screen turns black and the goes back to Asus splash screen.
I tried holding power and volume key to get back to fastboot but no luck. Any ideas?
Wow! You are really having some bad luck there!!
First the failed firmware update and now this.... Please post the commands you used to flash CWM.
I have no explanantion for this since you did not even boot into CWM.......
Unless..... the bad firmware flash left a command behind calling the stock recovery to do something (which in your case did not work anyway since it just looped) and now the bootloader tries to execute the command which is not "understood" by CWM. But that still does not explain why you cannot boot into the BL anymore......
Can you turn it off by long pressing power? Try every which way to get into fastboot. Without it there is not much you can do I'm afraid.
Try the restart pin hole (I believe it's on the left side of the tablet near the top) in conjunction with Volume Down, try leaving it alone for a while, try timing the button press somewhat differently - anything to get you into the BL again...
I feel very sorry for you, mate!!
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
jggrnaut said:
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
Click to expand...
Click to collapse
I don't know what happened before - maybe you were doomed since the bad firmware flash - but that last step sealed the coffin.
Using Wipe Data from the bootloader with a custom recovery installed is asking for trouble. Never ever do that.... Sorry, it's a brick. [emoji24]
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
mediaman123 said:
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
Click to expand...
Click to collapse
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
jeromechrome1 said:
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
Click to expand...
Click to collapse
Please! Anyone!
by manually do you mean flashing all the separate parts of the stock image separately, system, boot, recovery, cache and so on..........
I don't know what else to do after going through with that process.....
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
I'm a total newb here so take what I tell you with a grain of salt. I had your exact same problem on my Nexus 5. Every single thing you just described is what happened to my N5. And just like your N6...I was able to boot up into recovery (stock and TWRP), I was able to flash all the things manually and even used Wug's NRT. But then whenever I tried to actually boot up the device it could never pass the Google logo....basically EVERYTHING THAT IS HAPPENING TO YOU.
What I did to fix everything? Changed my battery. Sounds stupid and totally irrelevant but that did the trick. When I opened up my phone I noticed my battery had a nasty bulge and realized it was defective. Bought a new one for $25 and have never had any issues ever since. I suggest you look at your battery and see if that is the root of your problem. I have heard of the N6 having some batteries expanding and causing the back covers to pop off...this could be related to your problem.
Like I said I am a newb and thought I'd share my experience in the hopes it solves your problem.
Good luck buddy! :good:
my N6 is actually away getting repaired for the exact issue you described, expanding battery [assumed], and cover coming away from the bezel.....
I believe though that if you keep the device plugged into the wall when trying to boot up with this battery defect it will get through the boot, at least in the beginning anyway....
I believe also that if it was a battery issue the device would power off first, as opposed to just sticking on the Google logo.........
ldkud50 said:
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
Click to expand...
Click to collapse
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
jeromechrome1 said:
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
Click to expand...
Click to collapse
Thats too bad. Maybe the device is hosed. RMA for a new one.
Same thing happened to me. As soon as I updated to the newest version of fastboot on my computer, everything worked...
jeromechrome1 said:
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I know, it's been a long time, but coud you tell me what happened to the phone?
Bootloop, can get to "firmware update screen", fastboot commands not working
Out of nowhere my phone rebooted and started bootlooping. Eventually it came on but within minutes it did it again. After about an hour of pulling the battery abd trying to boot it, it finally came on. I went to use some app (I cant remember the title) to boot into twrp but it froze and started to bootloop again. I had never granted SU permissions to the app and it hadnt come up. Now that i have my computer I was able to boot into download mode (Firmware update screen) but my fastboot boot twrp.img command is stuck on waiting for device. Im guessing a malicious app caused the bootloop as i granted some app SU permissions only to later realize that it never needed it. All it did was download apk files for pentesting and diagnosis apps. It may be one of those apps however. I was on a custom ROM with an unlocked bootloader and twrp (although i cant seem to boot to it). LG Bridge couldnt find the device. Any help would be appreciated as this is my only device and I'm waiting for a call back for a speeding ticket and don't want to be screwed over :crying:
Since you have twrp and unlocked bootloader you should be able to access twrp still. This happened to me but from wiping internal storage by accident. Make sure you have your custom rom of choice on your sd card or the one you were running. Power off your G4 completely and while its off enter recovery mode manually. You may need to do this a few times for your G4 to enter recovery but it will boot to twrp. I believe its hold power button and volume down button then release for a sec both buttons when you see the lg logo then continue to hold them again. Do the factory reset option and after that it will boot to twrp and flash your rom again. Hope this works.
Sent from my LG-H811 using Tapatalk
srod562 said:
Since you have twrp and unlocked bootloader you should be able to access twrp still. This happened to me but from wiping internal storage by accident. Make sure you have your custom rom of choice on your sd card or the one you were running. Power off your G4 completely and while its off enter recovery mode manually. You may need to do this a few times for your G4 to enter recovery but it will boot to twrp. I believe its hold power button and volume down button then release for a sec both buttons when you see the lg logo then continue to hold them again. Do the factory reset option and after that it will boot to twrp and flash your rom again. Hope this works.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
I tried that and it doesnt take me to twrp or the factory reset screen
Did you try it a few times? I had to do it like 5 times before I got the factory reset option. Maybe you have the dreaded hardware failure bootloop.
Sent from my LG-H811 using Tapatalk
Happened to me. Every time I would use the hardware keys to get into TWRP it would go back to the bootloop. Most likely is hardware issue like he said ^^ I contacted LG and they told me to send it. It's on its way back to me
Sent from my LG-H830 using XDA-Developers mobile app
My phone started bootlooping on Saturday so i called T-mobile and i just received my replacement phone today. Now im afraid that they're going to find out that my phone was rooted because when u turn the phone on it says bootloader unlocked and if they even get into recovery mode it will have twrp installed
Sent from my LG-H811 using XDA-Developers mobile app
Hi guys, can anyone pls do help me. been troubleshooting and try to fix this thing for 2 days already.
The problem is, my fon will always boot to recovery. Eventhough i choose restart to system it will always go back to recovery.
I tried turn off, and push the power button only, still it will boot to recovery.
This started happening just a sudden, my fon run out of battery. Then its dead, i recharge. When try boot again the recovery boot problem begin.
I tried to restore my backup that iv made after the fresh installation of the CM13, restoration is good. But it still boot to recovery.
I then tried flashed the original rom with fastboot, ( i can access fastboot via the options in recovery, im using the TWRP recovery.
Or else i wouldnt be able to access fastboot also, even if i push (vol down+power button) when the fon is off, it will goes directly to recovery.
Anyone has any idea? please help =(
Fix
mufanz said:
Hi guys, can anyone pls do help me. been troubleshooting and try to fix this thing for 2 days already.
The problem is, my fon will always boot to recovery. Eventhough i choose restart to system it will always go back to recovery.
I tried turn off, and push the power button only, still it will boot to recovery.
This started happening just a sudden, my fon run out of battery. Then its dead, i recharge. When try boot again the recovery boot problem begin.
I tried to restore my backup that iv made after the fresh installation of the CM13, restoration is good. But it still boot to recovery.
I then tried flashed the original rom with fastboot, ( i can access fastboot via the options in recovery, im using the TWRP recovery.
Or else i wouldnt be able to access fastboot also, even if i push (vol down+power button) when the fon is off, it will goes directly to recovery.
Anyone has any idea? please help =(
Click to expand...
Click to collapse
Go the miui forum and search FIX : MI FLASH PARTITION TABLE DOESNT EXIST
You'll find a link by Harsimrat Sethi, me,, its the perfect fix
Harsimratsethi said:
Go the miui forum and search FIX : MI FLASH PARTITION TABLE DOESNT EXIST
You'll find a link by Harsimrat Sethi, me,, its the perfect fix
Click to expand...
Click to collapse
Hi bro thanks for suggestion, will do try it out. Iv looked at the solution, but it seems that is a problem if cant use fastboot flash with Mi Flash, I have no problem flashing to stock rom in fastboot. Iv used this solution from this link below to manually flash in the fastboot. Its working for people who are having problem of "MI FLASH PARTITION TABLE DOESNT EXIST".
http://forum.xda-developers.com/xiaomi-mi-3/general/guide-flashing-fastboot-miui-roms-t2938279
But the problem is still it will boot up to recovery also.