Related
Hi all. I flashed the full system image of KRT16O when it was released. I then flashed with fastboot the CWM 6.0.4.3 recovery image. I then got the OTA to update to KRT16S. I read online that I didnt have to unroot or go back to the stock recovery so I just let it update like normal. It updated fine, loaded up fine, etc. So I then went to use fastboot to reflash the CWM recovery image however all I get is the android on his back with the red triangle.
Am I doing something wrong? Could my recovery partition be screwed? How do I fix it. Thanks!
i should also mention that when I use fastboot to flash the recovery image, it says it was copied/flashed successfully - but it doesn't work.
You didn't flashed recovery or didn't do it correctly. What you saw is stock recovery.
And remember to flash recovery to the correct partition: fastboot flash recovery cwm.img
yea i dont think u flashed it correctly either.
go to clockworkmod, download the latest.... copy it to the platform tools folder. then fastboot flash it again...
thanks guys. Im familiar with the process - when I flashed the factory image KRT16O I then used fastboot to flash CWM just a few days prior without a hitch. But on Friday it just wouldnt "stick". I tried three times, each time it said successful but then after a reboot it would be gone. On the third time though after I flashed it, and it said success, I then went into recovery from the bootloader screen and it was there, so I rebooted and went back and this time it had stayed. strange.
Side note - does debugging need to be on to use fastboot?
I am having the same problem.
After the OTA, CWM won't stick. I get a red triangle.
fastboot screen shows that I have a secure boot, whereas the phone shows the lock as unlocked.
burnski said:
Side note - does debugging need to be on to use fastboot?
Click to expand...
Click to collapse
USB debugging box should be checked in order to use fastboot.
---------- Post added at 01:53 PM ---------- Previous post was at 01:49 PM ----------
yaronkle said:
I am having the same problem.
After the OTA, CWM won't stick. I get a red triangle.
fastboot screen shows that I have a secure boot, whereas the phone shows the lock as unlocked.
Click to expand...
Click to collapse
try to root the phone again and making sure before flashing the CWM, you should erase the old one, use command in fastboot:
fastboot erase recovery
and then
fastboot flash recovery nameofrecovery.img
I got CWM working again. Not sure how.
I disabled ART, reboot and CWM worked.
Enabled ART and CWM still works, just that it asks if I want to install SU again before booting.
Long story short, hopped over to android following years and years of using IOS.
Bought a nexus 6p, learnt about root, gained root access to the 6p, and began installed root apps.
This morning, i installed Gsam battery monitor root companion, found out it broke the normal Gsam battery monitor app, tried to uninstall the gsam root companion several times. Everytime i uninstalled it and rebooted, it would just reappear on the phone and wouldn't actually uninstall properly at all.
On the third go, it rebooted into the red triangle " Your device is corrupt. It can't be trusted and may not work properly." and is stuck on the google logo.
Accessed recovery and tried to restore the nandroid backup, no luck, still boots up to red triangle and is stuck on google logo.
Accessed recovery and tried to restore to factory default, no luck, still boots up to red triangle and is stuck on google logo.
How do i fix my phone now? Any help would be greatly appreciated.
red triangle with the android mascot logo?
if so, put it into fastboot and reinstall recovery and see if that worked
gd6noob said:
red triangle with the android mascot logo?
if so, put it into fastboot and reinstall recovery and see if that worked
Click to expand...
Click to collapse
Its just a red triangle with an exclamation mark inside.
I can't post an image because i am a new member and need at least 10 posts.
https://support.google.com/nexus/answer/6185381?hl=en - It says it should dismiss by itself.
chichu_9 said:
- It says it should dismiss by itself.
Click to expand...
Click to collapse
The red logo does disappear and the device transitions to the black and white google boot logo.
It is here where the device becomes hung, i assume it is because the boot.img or boot files have been damaged, but i'm just guessing. What i am confused about is if the boot files are damaged, the nandroid restore should fix this problem (shouldn't it?), but it doesn't.
radaga5t said:
Long story short, hopped over to android following years and years of using IOS.
Bought a nexus 6p, learnt about root, gained root access to the 6p, and began installed root apps.
This morning, i installed Gsam battery monitor root companion, found out it broke the normal Gsam battery monitor app, tried to uninstall the gsam root companion several times. Everytime i uninstalled it and rebooted, it would just reappear on the phone and wouldn't actually uninstall properly at all.
On the third go, it rebooted into the red triangle " Your device is corrupt. It can't be trusted and may not work properly." and is stuck on the google logo.
Accessed recovery and tried to restore the nandroid backup, no luck, still boots up to red triangle and is stuck on google logo.
Accessed recovery and tried to restore to factory default, no luck, still boots up to red triangle and is stuck on google logo.
How do i fix my phone now? Any help would be greatly appreciated.
Click to expand...
Click to collapse
After a root went bad I had the same thing happen. I just used SkipSoft ToolKit and restored back to a stock image (MDB08L).
The corruption message disappeared.
Take a look at this guide By Heisenberg as it will help with some details.
The few times I flashed/reset the phone, I accidentally muddled up some steps. Specifically the flashing the boot and bootloader images.
Code:
[U]fastboot flash bootloader X:/bootloader.img[/U]
fastboot reboot bootloader
fastboot flash radio X:/radio.img
fastboot reboot bootloader
[U]fastboot flash boot X:/boot.img[/U]
fastboot erase cache
fastboot flash cache X:/cache.img
fastboot flash recovery X:/recovery.img
fastboot flash system X:/system.img
fastboot flash vendor X:/vendor.img
I would accidentally flash the bootloader.img image over the boot.img and cause the error, specifically the one you mentioned. I had to go through the flashing process VERY carefully again, and when flashing .imgs for root acess over to the stock ones.
I know is sounds trivial and I'm not saying you don't understand it, but give it a try and see if this resolves the issue. double check your lines and triple check your images (make sure there are NO spaces in the bootloader/boot img file directories. or_replace_spaces_with_underscores). I don't know how many times I have screwed up and it was because of a dash in the wrong spot or space in the .img directory. Let us know how you go.
Awesome!
Thank you very much everyone. I will try once i get home from work.
You have all been so helpful. Such a good community.
I hoped it worked out for you
urbanpitch said:
I hoped it worked out for you
Click to expand...
Click to collapse
Yep i was able to restore the phone via the heisenberg guide. Thanks!
radaga5t said:
Yep i was able to restore the phone via the heisenberg guide. Thanks!
Click to expand...
Click to collapse
Was just about to post a link to my guide but it looks as though you already got everything sorted out. I'm glad my little guide was able to assist you.
Heisenberg said:
Was just about to post a link to my guide but it looks as though you already got everything sorted out. I'm glad my little guide was able to assist you.
Click to expand...
Click to collapse
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
---------- Post added at 11:24 PM ---------- Previous post was at 11:17 PM ----------
radaga5t said:
Awesome!
Thank you very much everyone. I will try once i get home from work.
You have all been so helpful. Such a good community.
Click to expand...
Click to collapse
Hey man, could you tell me the exact steps you took to fix yours? I'm having the same exact issue after having use that toolkit.
barondebxl said:
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
Click to expand...
Click to collapse
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.
Heisenberg said:
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.
Click to expand...
Click to collapse
Cool ill give it a shot. Thank you. I'm all out of thanks for today
---------- Post added at 11:53 PM ---------- Previous post was at 11:35 PM ----------
Heisenberg said:
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.
Click to expand...
Click to collapse
Im sorry but I'm completely lost. I have downloaded the factory images of my build, I have extracted the files but there isn't any bootloader.img and radio.img. When I click the extracted file it asks me if I want to download a windows application to open it.
barondebxl said:
Cool ill give it a shot. Thank you. I'm all out of thanks for today
---------- Post added at 11:53 PM ---------- Previous post was at 11:35 PM ----------
Im sorry but I'm completely lost. I have downloaded the factory images of my build, I have extracted the files but there isn't any bootloader.img and radio.img. When I click the extracted file it asks me if I want to download a windows application to open it.
Click to expand...
Click to collapse
You'll need to find a program that can extract the "tar.gz" compression format.
Heisenberg said:
You'll need to find a program that can extract the "tar.gz" compression format.
Click to expand...
Click to collapse
Ok thank you. 7zip works
barondebxl said:
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
---------- Post added at 11:24 PM ---------- Previous post was at 11:17 PM ----------
Hey man, could you tell me the exact steps you took to fix yours? I'm having the same exact issue after having use that toolkit.
Click to expand...
Click to collapse
Basically i followed step 9 of Heisenberg's guide.
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
So i flashed all of the above minus the user data and re-locking the bootloader.
Let me know if you need any more info.
radaga5t said:
Basically i followed step 9 of Heisenberg's guide.
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
So i flashed all of the above minus the user data and re-locking the bootloader.
Let me know if you need any more info.
Click to expand...
Click to collapse
Thanks bud. I'm lost still. I have all the files needed in a folder I called " images" on my desktop. Do I have to write these commands you posted word for word? I mean I know I have to replace with my file name but for example I have the MDB08L so do I do : fastboot flash bootloader C:\angler\images\bootloader-angler-angler-02.01.img ( in my case) even though the folder is on my desktop?
Edit: I tried and it gave me an error saying it cant load it. So frustrating
barondebxl said:
Thanks bud. I'm lost still. I have all the files needed in a folder I called " images" on my desktop. Do I have to write these commands you posted word for word? I mean I know I have to replace with my file name but for example I have the MDB08L so do I do : fastboot flash bootloader C:\angler\images\bootloader-angler-angler-02.01.img ( in my case) even though the folder is on my desktop?
Edit: I tried and it gave me an error saying it cant load it. So frustrating
Click to expand...
Click to collapse
You got an error because you're pointing fastboot to a location where the file doesn't exist. If you had followed my guide and placed the files in C:\angler\images\ then the command would be correct, but you've placed the files in a different location, therefore you need to type the commands so that they include the path to where the files are actually located on your PC.
There's an easy way to do it, type the first portion of the command, for example "fastboot flash bootloader " (make sure there's a space after the last character), then you can grab the appropriate file with your mouse and drag/drop it into the command terminal window and the file path will be completed automatically for you, then just hit enter to execute the command.
Heisenberg said:
You got an error because you're pointing fastboot to a location where the file doesn't exist. If you had followed my guide and placed the files in C:\angler\images\ then the command would be correct, but you've placed the files in a different location.
You need to type the commands so that they include the path to where the files are actually located on your PC. There's an easy way to do it, type the first portion of the command, for example "fastboot flash bootloader " (make sure there's a space after the last character), then you can grab the appropriate file with your mouse and drag/drop it into the command terminal window and the file path will be completed automatically for you, then just hit enter to execute the command.
Click to expand...
Click to collapse
Thanks guys I finally figured it out. I'm at flashing the system and its taking a while obviously. Its actually easy...when you know what youre doing. Thank you so very much to the both of you!
Edit: back up and running! I was just frustrated cause I just got the phone this afternoon that's why. You guys are awesome
---------- Post added at 01:48 AM ---------- Previous post was at 01:36 AM ----------
barondebxl said:
Thanks guys I finally figured it out. I'm at flashing the system and its taking a while obviously. Its actually easy...when you know what youre doing. Thank you so very much to the both of you!
Edit: back up and running! I was just frustrated cause I just got the phone this afternoon that's why. You guys are awesome
Click to expand...
Click to collapse
One last question, whats the best method to root MDB08L? I want that chroma rom
TAnother soft brick Nexus 6p here. So I recently flashed via flashfire the most recent Dec factory image.
The phone since then was acting weird and not being able to make outgoing and receiving calls when I am only connected to Tmobile. It's fine with Wifi on. So, bright idea, I flashed the Modem included with the factory image. Now, the phone rebooted and worked for ~ 10 minutes and then the endless reboots begins. I can still get into fastboot, and into TWRP recovery.
I have tried flashing the Modem firmware via flashboot - NO luck
Tried wiping data, cache, factory reset - NO luck
Tried complete erasing everything - reflashing manually the latest image and also November's image - via Heisenberg's guide, specifically, Part 9. - No luck
Any ideas? Thanks for the help
mintytoo said:
Another soft brick Nexus 6p here. So I recently flashed via flashfire the most recent Dec factory image.
The phone since then was acting weird and not being able to make outgoing and receiving calls when I am only connected to Tmobile. It's fine with Wifi on. So, bright idea, I flashed the Modem included with the factory image. Now, the phone rebooted and worked for ~ 10 minutes and then the endless reboots begins. I can still get into fastboot, and into TWRP recovery.
I have tried flashing the Modem firmware via flashboot - NO luck
Tried wiping data, cache, factory reset - NO luck
Tried complete erasing everything - reflashing manually the latest image and also November's image - via Heisenberg's guide, specifically, Part 9. - No luck
Any ideas? Thanks for the help.
Minh
[email protected]
Click to expand...
Click to collapse
Hi use the Wugfreshes Nexus root toolkit
---------- Post added at 04:21 AM ---------- Previous post was at 04:19 AM ----------
mintytoo said:
Another soft brick Nexus 6p here. So I recently flashed via flashfire the most recent Dec factory image.
The phone since then was acting weird and not being able to make outgoing and receiving calls when I am only connected to Tmobile. It's fine with Wifi on. So, bright idea, I flashed the Modem included with the factory image. Now, the phone rebooted and worked for ~ 10 minutes and then the endless reboots begins. I can still get into fastboot, and into TWRP recovery.
I have tried flashing the Modem firmware via flashboot - NO luck
Tried wiping data, cache, factory reset - NO luck
Tried complete erasing everything - reflashing manually the latest image and also November's image - via Heisenberg's guide, specifically, Part 9. - No luck
Any ideas? Thanks for the help.
Minh
[email protected]
Click to expand...
Click to collapse
Or try this https://drive.google.com/file/d/0B9Qv4K4H8yJYSk1qUWdOQl9mTk0/view?usp=drivesdk
The lastest radio image
Very similar issue. Flashed the engineering radio via DD command in terminal, reboot and nada. Black screen with no way to get into fastboot. When I plug the phone into the computer I get the device alert and COM4 shows up in ports, nothing else. I do fastboot devices and adb devices and nothing shows up. I tried NRT and to reinstall the drivers, now COM4 doesn't show up nor anything else. If I hold vol dn and power I hear device remove sound from windows, then device insert sound. so the device is doing something. Almost like need a factory flash tool to rewrite the radio partition.
boxguy1 said:
Hi use the Wugfreshes Nexus root toolkit
---------- Post added at 04:21 AM ---------- Previous post was at 04:19 AM ----------
Or try this https://drive.google.com/file/d/0B9Qv4K4H8yJYSk1qUWdOQl9mTk0/view?usp=drivesdk
The lastest radio image
Click to expand...
Click to collapse
Flashed the latest radio img, first, just by itself - still bootloops.
Thanks for the suggestion but something is still messed up with the phone. I used the advanced utilities and flashed boot, bootloader, radio, recovery, system, cache, vendor individually, (Dec Factory image) and still did not work.
Then tried the "flashed to stock + Unroot" options and after 20 minutes of boot loop, the phone started for a while, Yay!. But with any activities, using keyboard, using the fingerprint sensor, etc.., it goes back into boot loop.
mintytoo said:
Flashed the latest radio img, first, just by itself - still bootloops.
Thanks for the suggestion but something is still messed up with the phone. I used the advanced utilities and flashed boot, bootloader, radio, recovery, system, cache, vendor individually, (Dec Factory image) and still did not work.
Then tried the "flashed to stock + Unroot" options and after 20 minutes of boot loop, the phone started for a while, Yay!. But with any activities, using keyboard, using the fingerprint sensor, etc.., it goes back into boot loop.
Click to expand...
Click to collapse
Wow did you try a full wipe of everything in TWRP advanced wife and then using Wugfreshes toolkit to restore
amcferrin90 said:
Very similar issue. Flashed the engineering radio via DD command in terminal, reboot and nada. Black screen with no way to get into fastboot. When I plug the phone into the computer I get the device alert and COM4 shows up in ports, nothing else. I do fastboot devices and adb devices and nothing shows up. I tried NRT and to reinstall the drivers, now COM4 doesn't show up nor anything else. If I hold vol dn and power I hear device remove sound from windows, then device insert sound. so the device is doing something. Almost like need a factory flash tool to rewrite the radio partition.
Click to expand...
Click to collapse
Did you get into this mess because of a modem image flash ? Cuz that is how I got here.
Also, my phone screen does turn on, that's how I know it is bootlooping. Also, I can see the screen as it goes into bootloader, and recovery screen.
amcferrin90 said:
Very similar issue. Flashed the engineering radio via DD command in terminal, reboot and nada. Black screen with no way to get into fastboot. When I plug the phone into the computer I get the device alert and COM4 shows up in ports, nothing else. I do fastboot devices and adb devices and nothing shows up. I tried NRT and to reinstall the drivers, now COM4 doesn't show up nor anything else. If I hold vol dn and power I hear device remove sound from windows, then device insert sound. so the device is doing something. Almost like need a factory flash tool to rewrite the radio partition.
Click to expand...
Click to collapse
Try what I posted http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
---------- Post added at 03:02 AM ---------- Previous post was at 03:01 AM ----------
mintytoo said:
Did you get into this mess because of a modem image flash ? Cuz that is how I got here.
Also, my phone screen does turn on, that's how I know it is bootlooping. Also, I can see the screen as it goes into bootloader, and recovery screen.
Click to expand...
Click to collapse
OK check my post out hopefully it helps http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
boxguy1 said:
Try what I posted http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
---------- Post added at 03:02 AM ---------- Previous post was at 03:01 AM ----------
OK check my post out hopefully it helps http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
Click to expand...
Click to collapse
Essentially yes. The phone was completely wiped before I used Wugfresh toolkit. I wiped it completely in TWRP. Then flashed to stock + unroot with Wugfresh. That's when it bootlooped for 20 minutes, booted normally, but then went back into another bootloop.
Seems like flashing this modem really messed up the phone?
mintytoo said:
Essentially yes. The phone was completely wiped before I used Wugfresh toolkit. I wiped it completely in TWRP. Then flashed to stock + unroot with Wugfresh. That's when it bootlooped for 20 minutes, booted normally, but then went back into another bootloop.
Seems like flashing this modem really messed up the phone?
Click to expand...
Click to collapse
Is your warranty still active and did you try formatting
boxguy1 said:
Is your warranty still active and did you try formatting
Click to expand...
Click to collapse
if warranty is 1 year, then I'm out. Bought it 11/04/2015, started using 11/10/15.
Formatting? If you mean erase everything off the phone, then yes, I formatted all userdata, system, cache, dalvik. Im going to try flashing stock+unroot with wegfresh again.
Any other thoughts? Maybe time for a pixel? Lol
mintytoo said:
if warranty is 1 year, then I'm out. Bought it 11/04/2015, started using 11/10/15.
Formatting? If you mean erase everything off the phone, then yes, I formatted all userdata, system, cache, dalvik. Im going to try flashing stock+unroot with wegfresh again.
Any other thoughts? Maybe time for a pixel? Lol
Click to expand...
Click to collapse
Yes
mintytoo said:
if warranty is 1 year, then I'm out. Bought it 11/04/2015, started using 11/10/15.
Formatting? If you mean erase everything off the phone, then yes, I formatted all userdata, system, cache, dalvik. Im going to try flashing stock+unroot with wegfresh again.
Any other thoughts? Maybe time for a pixel? Lol
Click to expand...
Click to collapse
Yep try formatting
Yes. I was flashing the radio250l image so that I could control what LTE bands were turned on for the radio. The stock radio does not have this feature. Instead of flashing in fastboot I used the DD command in terminal then rebooted. I think my problem is I tripped the security mechanism in Nougat with the unsigned radio. I have friends that used fastboot method fine. So the phone is in a state like Samsung Galaxy does where Odin tool is needed to restore firmware and partitions. I can't get to fastboot or recovery mode so none of the traditional restore functions work.
For you maybe drop back to marshmallow and flash that, let it work it's way up back to nougat.
as you guys know June update killed a lot of athenes and same thing happened with my athene. and the BlankFlash is also not working after this update. so is there any update for blankFlash, post a link here.
no updated blankflash ... we should wait la
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
siddhesh9146 said:
as you guys know June update killed a lot of athenes and same thing happened with my athene. and the BlankFlash is also not working after this update. so is there any update for blankFlash, post a link here.
Click to expand...
Click to collapse
sad..... my athne toooooo dead .... we should hope get updated soon... most of moto g4 plus athene dead ...... i dont who gonna make new updated blankflash to recover....... thanks in advance who make new one..... or any other solution... already a post is here but it didnot work out at allll..... pls someone geeks solve this
...... ISSUES LOTS OF MOTO G4 PLUS DEADDD..... EVERYTHING TRIED NO LUCK[ATHENE]XT1643]:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
tamil2692 said:
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
sad..... my athne toooooo dead .... we should hope get updated soon... most of moto g4 plus athene dead ...... i dont who gonna make new updated blankflash to recover....... thanks in advance who make new one..... or any other solution... already a post is here but it didnot work out at allll..... pls someone geeks solve this
...... ISSUES LOTS OF MOTO G4 PLUS DEADDD..... EVERYTHING TRIED NO LUCK[ATHENE]XT1643]:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Nothin
new blankflash HERE : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Does not enter recovery or boot up system
as soon as the blankflash file is updated i flashed it and worked
then i flashed updated gpt and bootloader
then i tried to enter recovery mode but its not entering
and also when i unplug usb cable it is turning off
then i flashed stock rom
but still recovery and system booting are not working,enters only to fastboot that too on charging.
guyss please help me it means a lot to me.Thanks in advance
Geek_manoj said:
as soon as the blankflash file is updated i flashed it and worked
then i flashed updated gpt and bootloader
then i tried to enter recovery mode but its not entering
and also when i unplug usb cable it is turning off
then i flashed stock rom
but still recovery and system booting are not working,enters only to fastboot that too on charging.
guyss please help me it means a lot to me.Thanks in advance
Click to expand...
Click to collapse
Are you mentioning that your device only boots to fastboot now? If you press 'start', does that boot to system or not?
Which stock ROM did you flash, and can you confirm if the flash worked? How did your device brick in the first place?
echo92 said:
Are you mentioning that your device only boots to fastboot now? If you press 'start', does that boot to system or not?
Which stock ROM did you flash, and can you confirm if the flash worked? How did your device brick in the first place?
Click to expand...
Click to collapse
he didn't flashed stock rom yet, he is only trying to flash custom roms zips from recovery. someone please him that this won't work in this case:cyclops:
Blank Flash Files Moto G4 Plus
Yes I have the correct blank flash files for Moto G4 Plus. I was used it on my device XT1643 and it is working.
echo92 said:
Are you mentioning that your device only boots to fastboot now? If you press 'start', does that boot to system or not?
Which stock ROM did you flash, and can you confirm if the flash worked? How did your device brick in the first place?
Click to expand...
Click to collapse
yes,the device boots only to fastboot that too only when charged.if i press start that doesn't boot to system.I flashed "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".I bricked by doing softare update after reflashing stock rom.it also doesnt enter recovery
---------- Post added at 02:09 AM ---------- Previous post was at 02:05 AM ----------
siddhesh9146 said:
he didn't flashed stock rom yet, he is only trying to flash custom roms zips from recovery. someone please him that this won't work in this case:cyclops:
Click to expand...
Click to collapse
sorry if you dont understand.but i flash stock rom "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" in stock recovery.if u could help me please let me know.thanks in advance
Geek_manoj said:
yes,the device boots only to fastboot that too only when charged.if i press start that doesn't boot to system.I flashed "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".I bricked by doing softare update after reflashing stock rom.it also doesnt enter recovery
---------- Post added at 02:09 AM ---------- Previous post was at 02:05 AM ----------
sorry if you dont understand.but i flash stock rom "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" in stock recovery.if u could help me please let me know.thanks in advance
Click to expand...
Click to collapse
I knew that, that file was for flashing in fastboot mode
but you flashed in recovery
Geek_manoj said:
yes,the device boots only to fastboot that too only when charged.if i press start that doesn't boot to system.I flashed "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".I bricked by doing softare update after reflashing stock rom.it also doesnt enter recovery
---------- Post added at 02:09 AM ---------- Previous post was at 02:05 AM ----------
sorry if you dont understand.but i flash stock rom "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" in stock recovery.if u could help me please let me know.thanks in advance
Click to expand...
Click to collapse
As siddhesh9146 had mentioned, the Athene stock ROM cannot be flashed in stock recovery, it is not a flashable zip file. You need a computer and ADB set up, extract the zip on your computer and use the flashing commands in the fastboot ROM thread to flash a stock ROM.
Until you've flashed the stock ROM, I'm not even sure if you have stock recovery, or a stock system on your device. The supplied blank flash does not appear to have a functioning recovery included with it.
echo92 said:
As siddhesh9146 had mentioned, the Athene stock ROM cannot be flashed in stock recovery, it is not a flashable zip file. You need a computer and ADB set up, extract the zip on your computer and use the flashing commands in the fastboot ROM thread to flash a stock ROM.
Until you've flashed the stock ROM, I'm not even sure if you have stock recovery, or a stock system on your device. The supplied blank flash does not appear to have a functioning recovery included with it.
Click to expand...
Click to collapse
I m sorry.I must have described in a better way.I actually mean that i used computer extracted the firmware and then i ran oem_flash,which is the actual way i suppouse in fastboot mode(i ommited for fastboot as stock recovery in previous post,sorry).but i dont know why it still doesnt enter recovery or enter into system or work without plug.i even tried flashing updated gpt.bin and bootloader files again followed by the rom,but noting happened
---------- Post added at 04:24 PM ---------- Previous post was at 04:19 PM ----------
echo92 said:
As siddhesh9146 had mentioned, the Athene stock ROM cannot be flashed in stock recovery, it is not a flashable zip file. You need a computer and ADB set up, extract the zip on your computer and use the flashing commands in the fastboot ROM thread to flash a stock ROM.
Until you've flashed the stock ROM, I'm not even sure if you have stock recovery, or a stock system on your device. The supplied blank flash does not appear to have a functioning recovery included with it.
Click to expand...
Click to collapse
siddhesh9146 said:
I knew that, that file was for flashing in fastboot mode
but you flashed in recovery
Click to expand...
Click to collapse
hey,i ommited in the post telling that i did it in recovery(sorry for that)actually it doesnt enter recovery,which i already mentioned.thanks for being concerned
Geek_manoj said:
I m sorry.I must have described in a better way.I actually mean that i used computer extracted the firmware and then i ran oem_flash,which is the actual way i suppouse in fastboot mode(i ommited for fastboot as stock recovery in previous post,sorry).but i dont know why it still doesnt enter recovery or enter into system or work without plug.i even tried flashing updated gpt.bin and bootloader files again followed by the rom,but noting happened
---------- Post added at 04:24 PM ---------- Previous post was at 04:19 PM ----------
hey,i ommited in the post telling that i did it in recovery(sorry for that)actually it doesnt enter recovery,which i already mentioned.thanks for being concerned
Click to expand...
Click to collapse
So, you booted your device to the bootloader screen (not to recovery), connected your device to your computer, and you've flashed using the OEM_flash script, and yet you're unable to reboot to recovery?
Sounds like your stock ROM flash did not work the first time, leaving you without a recovery or a system. Try the following just to confirm:
1) Ensure your adb folder contains the extracted NPJS25.93-14-8 stock ROM (all the files), should be about 2 GB for the stock ROM. Also confirm that the OEM flash script is in the same location (so your adb folder should have the stock ROM, the flash script and the adb and fastboot.exe and adb.dlls)
2)Reboot your device to the bootloader (power down, then press the power and volume down keys to boot to bootloader) and connect your device to your computer.
3)In the adb terminal, type 'fastboot devices', without the quotes. If communicating, you should see your device respond with its serial number.
4)If communicating, run the OEM flash script again.
5)If your device does not boot properly, then reboot to bootloader.
5a)Copy each of the commands from the script (you can open the script in a text editor) and paste them in the adb terminal window and run each one by pressing Enter on your keyboard. You should see the command report [OKAY] if it's flashed. Any errors, let us know, that might point more accurately to what might be going on.
As an aside, this is one of the reasons why downgrading isn't a good idea....
echo92 said:
So, you booted your device to the bootloader screen (not to recovery), connected your device to your computer, and you've flashed using the OEM_flash script, and yet you're unable to reboot to recovery?
Sounds like your stock ROM flash did not work the first time, leaving you without a recovery or a system. Try the following just to confirm:
1) Ensure your adb folder contains the extracted NPJS25.93-14-8 stock ROM (all the files), should be about 2 GB for the stock ROM. Also confirm that the OEM flash script is in the same location (so your adb folder should have the stock ROM, the flash script and the adb and fastboot.exe and adb.dlls)
2)Reboot your device to the bootloader (power down, then press the power and volume down keys to boot to bootloader) and connect your device to your computer.
3)In the adb terminal, type 'fastboot devices', without the quotes. If communicating, you should see your device respond with its serial number.
4)If communicating, run the OEM flash script again.
5)If your device does not boot properly, then reboot to bootloader.
5a)Copy each of the commands from the script (you can open the script in a text editor) and paste them in the adb terminal window and run each one by pressing Enter on your keyboard. You should see the command report [OKAY] if it's flashed. Any errors, let us know, that might point more accurately to what might be going on.
As an aside, this is one of the reasons why downgrading isn't a good idea....
Click to expand...
Click to collapse
Hey,thanks for bothering.But,it didnt work.i have got no error.But still mobile enters only fastboot that too when charging( only fastboot again).
I tried to clear cache memory by booting my g4 plus in recovery mode. the phone hanged up and switched off now unable to boot. tried the blank flash file to update but the same is not working. Can any one help !!
Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)
Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?
Azpre said:
Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)
Click to expand...
Click to collapse
From my understanding ... After you get the bootloader unlocked and the critical partition as the poster above stated. Pretty sure, Magisk, when booted into the android OS should be installed.. After that you can patch the boot image(to include root) without root! And then, fastboot flash boot (path/to/boot.img).
For not being able to boot into TWRP .... Did you use the command fastboot boot twrp.img? Or fastboot flash recovery twrp.img ?
If you used the boot command - TWRP will not stick.
If you used the flash command and cannot access TWRP, IDK, you may be on the wrong partition. I personally had a bit of difficulty with there being two partitions. Just made it a bit confusing...
As the above poster asked, .... Are you able to get to the bootloader? If so, I don't think all is lost... I'm thinking you'll just have to do some fastboot commands again, like, fastboot boot TWRP.img . Then you should be able to just press the volume a time or two to boot to recovery. As @BakedTator asked
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
BakedTator said:
Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?
Click to expand...
Click to collapse
Was that advise sound enough???
---------- Post added at 05:49 PM ---------- Previous post was at 05:44 PM ----------
Azpre said:
Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/help/partition-t3733811. Check out this thread, it may help or give you some understanding.
BakedTator said:
Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?
Click to expand...
Click to collapse
This is what I got when I tried to use this command
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock_critical
fastboot: usage: unknown command unlock_critical
yesterday I couldn't find a way to access the bootloader, but for some reason when I gave another shot today it worked
going to try flash twrp once again
Azpre said:
This is what I got when I tried to use this command
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock_critical
fastboot: usage: unknown command unlock_critical
yesterday I couldn't find a way to access the bootloader, but for some reason when I gave another shot today it worked
going to try flash twrp once again
Click to expand...
Click to collapse
fastboot flashing!!! fastboot flashing unlock_critical
From HERE - !!!
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
dirtyreturn said:
From my understanding ... After you get the bootloader unlocked and the critical partition as the poster above stated. Pretty sure, Magisk, when booted into the android OS should be installed.. After that you can patch the boot image(to include root) without root! And then, fastboot flash boot (path/to/boot.img).
For not being able to boot into TWRP .... Did you use the command fastboot boot twrp.img? Or fastboot flash recovery twrp.img ?
If you used the boot command - TWRP will not stick.
If you used the flash command and cannot access TWRP, IDK, you may be on the wrong partition. I personally had a bit of difficulty with there being two partitions. Just made it a bit confusing...
As the above poster asked, .... Are you able to get to the bootloader? If so, I don't think all is lost... I'm thinking you'll just have to do some fastboot commands again, like, fastboot boot TWRP.img . Then you should be able to just press the volume a time or two to boot to recovery. As @BakedTator asked
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
Was that advise sound enough???
---------- Post added at 05:49 PM ---------- Previous post was at 05:44 PM ----------
https://forum.xda-developers.com/essential-phone/help/partition-t3733811. Check out this thread, it may help or give you some understanding.
Click to expand...
Click to collapse
thanks for the thread man, helped alot
I managed to flash twrp by some miracle, I remember my device entering a bootloop once I tried to access the bootloader menu, but now its all good. I waited for the Essential run out of battery, then I plugged-in my pc the fastboot commands were working once again
going to try install a boot image now
dirtyreturn said:
fastboot flashing!!! fastboot flashing unlock_critical
From HERE - !!!
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Click to expand...
Click to collapse
oh my god Im such a dumbass, sorry
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.