Related
I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.
OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.
I had TWRP 3.0.1 so I downloaded the latest TWRP 3.0.2 IMG file and booted to Recovery and selected the image and then selected Recovery as to where to flash and it flashed no errors so I backed out and went to reboot and selected Recovery and it rebooted to bootloader and when I stroll volume keys to Recovery then power to select it just hangs there I have to do a power long press to get it to reboot back to Android. Any ideas why Recovery will not load now ?
I'm on MHC19l
Stock rooted no mods
System rooted
Sent from my Nexus 6P using Tapatalk
A bad flash, perhaps? Have you checked the MD5 after downloading?
Possible bad download but at this point I can't reflash the recovery until I can fast boot .. I gotta order another Type C to USB to connect the phone to the computer for fast boot grrrrr...
Thx
Sent from my Nexus 6P using Tapatalk
Glad to help! Next time make sure you check MD5 before flashing (even then an occasional bad flash could still cause trouble, but hey, what's the choice here?) You can still boot to Android normally, no?
Sidenote: anyone knows if a micro B to C adaptor would work with fastboot?
Yeah I can still boot to Android fine jus when I select recovery n bootloader it hangs in bootloader. I have to hard reset to get out of bootloader mode lol....
Jus sucks BC now I gotta wait until friday to order a Type C to USB cable to use the computer to fast boot TWRP to recovery.. :/
I jus got this 6P 4 days ago coming from the HTC M9 Developer Edition I decided to go with the 6P over the M10 even though I would have gotten $100 off the M10 for not using my UhOh protection.
But I'm currently Stock w/ root until I figure out or understand this whole Vender thing when flashing Roms.. Jus being very cautious.
With HTC you jus flash the ROM you want but here some say jus flash the ROM and some say flash the Vender matching the ROM.. Lol,..
Sent from my Nexus 6P using Tapatalk
About the vendor img... Not too sure about the whole technical details behind them, but I just flash them every time Google updates them (think monthly security updates), at the very least to get rid of the 'vendor img outdated' popup. You don't need to flash a new vendor img everytime you update/switch ROMs, but only when there's a new vendor.
I usually just flash recovery with flashify. Never had an issue doing it that way. Or fastboot.
Sent from my Nexus 6P using XDA-Developers mobile app
scoot0073 said:
I had TWRP 3.0.1 so I downloaded the latest TWRP 3.0.2 IMG file and booted to Recovery and selected the image and then selected Recovery as to where to flash and it flashed no errors so I backed out and went to reboot and selected Recovery and it rebooted to bootloader and when I stroll volume keys to Recovery then power to select it just hangs there I have to do a power long press to get it to reboot back to Android. Any ideas why Recovery will not load now ?
I'm on MHC19l
Stock rooted no mods
System rooted
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
People have been facing the same issue all around. Even I did, last night after updating to N Preview. Anyhow, the only solution I know right now is to have a decrypted filesystem (disable encryption), for TWRP to boot and work properly.
Yeah disable encryption I believe I read requires booting into recovery and wiping User Data or something alone those line's.
Unless there's a option in Android settings to disable it idk yet as I jus had the phone a few day's.
But so far I happy with my decision to get the 6P over the M10 even if the 6P is 4 or 5 moths old...
Sent from my Nexus 6P using Tapatalk
OK I got the latest TWRP Recovery flash . I used Flashify app and it flashed the recovery and I got a working recovery now..
Sent from my Nexus 6P using Tapatalk
Pain-N-Panic said:
I usually just flash recovery with flashify. Never had an issue doing it that way. Or fastboot.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank u so much that fixed my borked recovery thank you again
Sent from my Nexus 6P using Tapatalk
Hi guys,
I have a honor 6 plus (PE-TL10), it was running EMUI 4. I flashed TWRP 2.8.7 and then wiped all partitions through it(cust,system,etc) then flashed stock recovery back, now i am trying to install EMUI 4.0.1(Android 6.0) via 3 buttons Huawei update but it stops at 5% and fails. Can you guys provide me with any help, I really need it.
Also now when i am trying to wipe data thru stock recovery i get an weird error message at almost 25% saying "reset balong modem setting fail", which making it more difficult to get back stock rom.
Just last question; the Unbrick option in the "HONOR_6_and_6Plus_Multi-Tool", wil it restore the device to stock rom and fully functional state after that or it will miss some parts of the stock rom ?
Many thanks and regards
demonjo2001 said:
Hi guys,
I have a honor 6 plus (PE-TL10), it was running EMUI 4. I flashed TWRP 2.8.7 and then wiped all partitions through it(cust,system,etc) then flashed stock recovery back, now i am trying to install EMUI 4.0.1(Android 6.0) via 3 buttons Huawei update but it stops at 5% and fails. Can you guys provide me with any help, I really need it.
Also now when i am trying to wipe data thru stock recovery i get an weird error message at almost 25% saying "reset balong modem setting fail", which making it more difficult to get back stock rom.
Just last question; the Unbrick option in the "HONOR_6_and_6Plus_Multi-Tool", wil it restore the device to stock rom and fully functional state after that or it will miss some parts of the stock rom ?
Click to expand...
Click to collapse
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the last installed one.
Post your results and I will try to help.
1:Extract the ROM with huawei update extractor
2:download latest minimal adb and fastboot drivers and install them
3ut the extracted system.img,recovery.img,cust.img,boot.img and userdata.img into the fastboot.exe folder
4: boot into the fastboot mode
And finally flash the above mentioned imgs one by one with this command
fastboot flash XXX XXX.img
After flashing files type
Fastboot reboot
and every thing should be fine again
Sent from my H30-U10 using Tapatalk
zinko_pt said:
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the last installed one.
Post your results and I will try to help.
Click to expand...
Click to collapse
Thank you for answering, I did used Huawei MultiTool and Unbricked my device. I flashed four img files(SYSTEM,CUST,RECOVERY,BOOT) and now i am back to stock rom and running smoothly.
I tried to use force update feature on my device after that but again i got the same result, it stopped at 5% and failed. I guess i will keep it the way it's now.
Many thanks; you guys are awesome!
hamzio7 said:
1:Extract the ROM with huawei update extractor
2:download latest minimal adb and fastboot drivers and install them
3ut the extracted system.img,recovery.img,cust.img,boot.img and userdata.img into the fastboot.exe folder
4: boot into the fastboot mode
And finally flash the above mentioned imgs one by one with this command
fastboot flash XXX XXX.img
After flashing files type
Fastboot reboot
and every thing should be fine again
Sent from my H30-U10 using Tapatalk
Click to expand...
Click to collapse
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
demonjo2001 said:
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
Click to expand...
Click to collapse
It's for the other partitions like cust, modem etc.
demonjo2001 said:
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
Click to expand...
Click to collapse
Don't use any other img file. And don't flash userdata.
If it works, don't change it. ?
Got similar issue on my honor 6. Can't update via SD card method or 3 button after leaving developer preview. Not even OTA updates install. All fail at 5%. So I'm stuck on B830 for now. Will try for a solution later.
goldfinv said:
Got similar issue on my honor 6. Can't update via SD card method or 3 button after leaving developer preview. Not even OTA updates install. All fail at 5%. So I'm stuck on B830 for now. Will try for a solution later.
Click to expand...
Click to collapse
Fastboot woukd be the only choice.
Sent from my honor 5X using XDA Labs
adriansticoid said:
Fastboot woukd be the only choice.
Click to expand...
Click to collapse
I've installed several versions of 6.0 via fastboot. Same thing. I just get stuck on that version. Can't even reinstall same version.
goldfinv said:
I've installed several versions of 6.0 via fastboot. Same thing. I just get stuck on that version. Can't even reinstall same version.
Click to expand...
Click to collapse
What partitions did you flash?
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
What partitions did you flash?
Click to expand...
Click to collapse
The usual. Boot. System. Recovery. Cust.
goldfinv said:
The usual. Boot. System. Recovery. Cust.
Click to expand...
Click to collapse
No errors in fastboot?
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
No errors in fastboot?
Click to expand...
Click to collapse
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
goldfinv said:
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
Click to expand...
Click to collapse
Goodluck with it man. I am sorry I can't help you any further as I am new in hsing fastboot. I got used to Odin in Samsung.
Sent from my Galaxy Tab 3 using XDA Labs
goldfinv said:
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
Click to expand...
Click to collapse
There's no other solution, either stock img files or some sort of transitional package.
zinko_pt said:
There's no other solution, either stock img files or some sort of transitional package.
Click to expand...
Click to collapse
Stock is a no go for me. I'll try transition package next. Maybe only just the recovery. Might work for the OP as well.
goldfinv said:
Stock is a no go for me. I'll try transition package next. Maybe only just the recovery. Might work for the OP as well.
Click to expand...
Click to collapse
Let us know if you fixed it.
Sent from my Galaxy Tab 3 using XDA Labs
Same issue with me as well please help me in this case.
zinko_pt said:
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the lasthttps://cdn-cf-3.xda-developers.com/images/smilies/frown.gif installed one.
Post your results and I will try to help.
Click to expand...
Click to collapse
Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
EDIT: I forgot to mention, I'm not getting the boot animation as well. I press the power key and nothing at all happens.
d1nesh said:
Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
Click to expand...
Click to collapse
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
avirk said:
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
d1nesh said:
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
Click to expand...
Click to collapse
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
avirk said:
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
==vj== said:
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
Click to expand...
Click to collapse
i'm really sorry about posting in wrong thread.
While trying to flash ElementalX kernel through memory card, I'm getting error: Zip signature verification failed, (in red).
nazim7 said:
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
Click to expand...
Click to collapse
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
d1nesh said:
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
Click to expand...
Click to collapse
What did you mean by your device not being detected in bootloader mode. Did you install the right drivers. Did you install minimal adb and fastboot. Can you do the below steps and tell me the result.
1. Download the drivers from here.
For Windows: http://www.devfiles.co/download/5eEx...ager_2.5.4.exe
2. Download the Minimal ADB and Fastboot = https://www.androidfilehost.com/?fid=745425885120698566
3. Install Minimal ADB and Fastboot = https://forum.xda-developers.com/sho....php?t=2317790
4. Restart the Moto G4 in fastboot mode. (Bootloader mode)
5. Connect the Phone to the computer.
6. In adb fastboot folder shift+right click and then in the pop up click "open command window here"
7. In the command line type: "fastboot devices"
Seeing your serial number means we know all is good and your phone is connected and you can go on flash the stock firmware. If the serial number is not showing, the drivers are not properly installed.
---------- Post added at 01:33 PM ---------- Previous post was at 01:25 PM ----------
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I thought he don't have TWRP installed. If TWRP is installed, then go on with what he said. That is the best solution for you. :good:
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
d1nesh said:
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
Click to expand...
Click to collapse
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
avirk said:
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
Click to expand...
Click to collapse
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
Try with other pc or change the port for data cable. It seems your system partition got corrupted, also you can mount system partition under twrp and then try to format it.
d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
nazim7 said:
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
Click to expand...
Click to collapse
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
As @nazim7 suggested you to flash the latest TWRP and then try to flash the rom again, also you can try to resize the partition and try to format it from twrp from the option in twrp. Just let us know what the result come back.
nazim7 said:
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
Click to expand...
Click to collapse
There's one more problem like I've mentioned previously. I have the latest drivers even then the device is not being detected via adb when in bootloader, but as soon as I boot into recovery, the device shows up on adb after command. How do I flash the recovery if the device doesn't show up in bootloader on adb?
hello friends,
i unlocked my bootloader and flashed a custom Rom. i was experiencing problems and i decided to revert to stock google rom, i mistakenly locked the bootloader with twrp recovery installed and i now get the message that my phone is corrupt and cannot be trusted. The phone doesn't boot it stucksat the Google logo. I the tried unlocking but not successful,
is there any help for me? thanks in advance
Dont wanna be the bad news guy but I think you broke your device.
You can't do anything in the bootloader now. Try to do stuff in TWRP. If TWRP still functions normally we can do something.
HeroPlane said:
Dont wanna be the bad news guy but I think you broke your device.
You can't do anything in the bootloader now. Try to do stuff in TWRP. If TWRP still functions normally we can do something.
Click to expand...
Click to collapse
twrp cannot read the internal memory
Frenzy23 said:
twrp cannot read the internal memory
Click to expand...
Click to collapse
Then sorry dude, I don't know but I am sure there is a way to fix it.
Wait for more comments
Hi.
Go to:
http://www.androidbrick.com/download/unbrick-nexus-6p-angler/
And follow that guide ?
If it boots up just boot it. I face this corruption screen every day on 5X, I also have locked bootloader with TWRP onboard and no issues so far (stop talking bull**** that this will brick device, btw).
You said it can't read internal memory. What exactly it display (I assume it can't decrypt it)
Try to sideload random ROM and install it, then toggle OEM unlock.
Sent from my Nexus 5X using XDA Labs
Banan PL said:
If it boots up just boot it. I face this corruption screen every day on 5X, I also have locked bootloader with TWRP onboard and no issues so far (stop talking bull**** that this will brick device, btw).
You said it can't read internal memory. What exactly it display (I assume it can't decrypt it)
Try to sideload random ROM and install it, then toggle OEM unlock.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
thanks
that's right twrp cant decrypt the device and also the file manager on the twrp is not able to read the files on the device, it also says no OS installed
it boots to the bootloader alright, but it stucks up on the google logo
rhaavin said:
Hi.
Go to:
http://www.androidbrick.com/download/unbrick-nexus-6p-angler/
And follow that guide
Click to expand...
Click to collapse
thanks ill give it a try and get back to you
I see no other option than full wipe and reflashing stock. So your data will be gone
Format /data in TWRP,
Reboot recovery,
Put any stock system image you have (system vendor, boot, recovery) to internal storage. (I assume you have at least one factory image on PC if not download),
Flash them in recovery (flash recovery last just in case)
Device SHOULD boot up.
Sent from my Nexus 5X using XDA Labs
I also tried to change my stock rom to custom rom. I don't know what happened, only twrp3_1_1_4Cores.img works on my device. I can install a custom rom but it doesn't boot into it. I cannot find any further informations about it. Can someone help me?