The phone is the Huawei Nexus 6P (MMB29M). No clue how this happened, but I managed to get root (working fine I can run apps that require root), but TWRP isn't on my phone. When I try to boot to recovery, it gives me the dead android symbol (dead android with front flap opened up and little red exclamation point). I can get into the boot loader just fine though, it's ONLY the recovery that is missing. Is it okay to use the TWRP app to install recovery the easy way? I have the TWRP app on my phone from the (failed) TWRP install, I guess. Or do I need to go through the whole root/recovery fastboot process again?
I don't know how I even got root without recovery, tbh. I was obviously in TWRP when I flashed superSU and busybox, but for whatever reason, it didn't stick. The only thing I can think of is that the phone took the liberty of replacing the recovery on its own when I restarted the phone (I didn't think to go back into recovery immediately, so the phone overwrote it...is that possible?)
The reason I'm asking about the TWRP app is because it has a very specific directory that it says it needs to install into and if that directory is wrong, the phone could be bricked. I've had the phone for less than a week, I'd prefer not to brick it. This is my 5th android device and I've never run into this issue before...in fact, I didn't even know it was POSSIBLE to get root without recovery. I did get a soft-brick earlier in the process, but I fixed it by re-flashing the stock android ROM (I also had to go change my pants afterward, but that's a story for another thread).
Thanks in advance for any assistance you can provide and have a nice Friday.
baronmax said:
The phone is the Huawei Nexus 6P (MMB29M). No clue how this happened, but I managed to get root (working fine I can run apps that require root), but TWRP isn't on my phone. When I try to boot to recovery, it gives me the dead android symbol (dead android with front flap opened up and little red exclamation point). I can get into the boot loader just fine though, it's ONLY the recovery that is missing. Is it okay to use the TWRP app to install recovery the easy way? I have the TWRP app on my phone from the (failed) TWRP install, I guess. Or do I need to go through the whole root/recovery fastboot process again?
I don't know how I even got root without recovery, tbh. I was obviously in TWRP when I flashed superSU and busybox, but for whatever reason, it didn't stick. The only thing I can think of is that the phone took the liberty of replacing the recovery on its own when I restarted the phone (I didn't think to go back into recovery immediately, so the phone overwrote it...is that possible?)
The reason I'm asking about the TWRP app is because it has a very specific directory that it says it needs to install into and if that directory is wrong, the phone could be bricked. I've had the phone for less than a week, I'd prefer not to brick it. This is my 5th android device and I've never run into this issue before...in fact, I didn't even know it was POSSIBLE to get root without recovery. I did get a soft-brick earlier in the process, but I fixed it by re-flashing the stock android ROM (I also had to go change my pants afterward, but that's a story for another thread).
Thanks in advance for any assistance you can provide and have a nice Friday.
Click to expand...
Click to collapse
This happened to me after the first time I installed twrp. I selected read only system after booting into twrp for the first time(they ask you if you want a read only option) and the stock rom would over write twrp with the stock recovery. Only fix for me was starting from scratch using step 11 here http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928. When you install twrp dont select the read only option and you'll be fine. Just remember not to let twrp install Su when it asks you to.
did you not read and follow the VERY detailed and specific instructions on how to do all of this, before beginning the process?
mistakes happen, and we are all here to help, but a softbrick followed by no recovery etc just seems like you tried to wing it without taking the proper time to read how to do it on your new device.
I'm sure someone will be able to give you a definite answer, but I also advise you to read @Heisenberg's guide on how to do it all on your 6P in the General section
Soulfly3 said:
did you not read and follow the VERY detailed and specific instructions on how to do all of this, before beginning the process?
mistakes happen, and we are all here to help, but a softbrick followed by no recovery etc just seems like you tried to wing it without taking the proper time to read how to do it on your new device.
I'm sure someone will be able to give you a definite answer, but I also advise you to read @Heisenberg's guide on how to do it all on your 6P in the General section
Click to expand...
Click to collapse
I read everything and my only mistake was selecting the read only option which clearly tell you that if you select read only it cant prevent the stock rom from over writing twrp with its own recovery. Mistakes happen.
can you not just install twrp again from the bootloader?
ahfu25 said:
I read everything and my only mistake was selecting the read only option which clearly tell you that if you select read only it cant prevent the stock rom from over writing twrp with its own recovery. Mistakes happen.
Click to expand...
Click to collapse
I was responding to the OP, not you.
uicnren said:
can you not just install twrp again from the bootloader?
Click to expand...
Click to collapse
Yes, but I was wondering if it was a bad idea to just let the TWRP app do it? That's what it's designed to do (that, and update TWRP). That's why I asked the question, I wasn't sure if that was a viable way to go about this or whether I just needed to re-do it from the nexus 6p "how to" that's on the site here.
Soulfly3 said:
I was responding to the OP, not you.
Click to expand...
Click to collapse
OK...have a nice day
I can't say for sure that I understand what you mean by using twrp when you don't even have it... but maybe see this post. (The bottom of that post.)
---------- Post added at 11:51 AM ---------- Previous post was at 11:46 AM ----------
oh, I get what you're saying now - can you do it with the twrp app - as in an actual app. i missed that word. I think i remember Heisenburg saying that, no, you shouldn't use the app. I think it doesn't get the right twrp version. the version we need for the 6p is in beta and not available throught the app.
---------- Post added at 12:07 PM ---------- Previous post was at 11:51 AM ----------
In a previous post of mine, I quoted the explanation from TWRP of the system read-only vs read-write thing: http://forum.xda-developers.com/showpost.php?p=64707169&postcount=2143 I think you may need to mount the system read-write to get twrp to "stick". ...or you need root (according to sirxdroid)? I don't know which... I'd love to know how you get it working again!
p.s. Sorry to keep appending to my response...
Good explanations and links, I had the same issue when I decided to root. I did not choose read only during my initial flash of TWRP and could not figure out why every time I flashed TWRP, rebooted then went into recovery, I lost TWRP! After I did my due diligence and read the threads, I realized what I did wrong. I flashed back to stock, then flashed TWRP as recovery. I went into recovery via bootloader and chose read only. Then I installed the su.zip, rebooted the bootloader, then it was all good. Good luck.
I think what I did wrong is fail to wipe the caches (not sure how I missed it, but I did, originally). I'm not entirely sure why that makes any difference, but I went through the rooting process again and installed TWRP, now things are working properly. I did two things differently, wiping the cache and booting directly back into recovery after installing recovery. I saw on the TWRP website that some ROMs will overwrite the boot.img and recovery sections if you don't boot back into recovery immediately (it doesn't overwrite them after the second time, for whatever reason). I'm not sure if this is what happened or not, but it's the one thing that actually makes SOME sense to me.
It's interesting that there's an app out there which claims to install TWRP, but people shouldn't use it, that would be a mighty handy app to have if it worked properly, no more worries and very little fuss.
Why not just fastboot flash recovery........takes 10 seconds.
Related
I tried to root my Nexus 6P and now I'm stuck. It won't finish booting. I followed instructions found on the web. I unlocked bootloader with no problem. I copied the latest SuperSU file to the phone. I installed TWRP recovery. However, I could not find the SuperSU file when using TWRP. Nevertheless, when I went to exit, TWRP asked if I wanted to instal SuperSU. I recall reading somewhere that it will install the wrong version of SuperSU (not the one for 6.0.1). Somehow I must have hit the wrong selection because it installed it anyway. Now I have an infinite loop.
I have tried to factory reset with TWRP. That fails. I downloaded the 6.0.1 images files from Google. I tried to run flash-all.bat, but that doesn't work. I have pushed images and ZIPs to the /sdcard/ folder with ADB. ADB recognizes the device, but fastboot does not (when connected to my laptop) (which is why flash-all doesn't work). I have tried to install the images/zips with TWRP. However, I always get "failed" messages. I get messages that partitions won't load.
Stupidly, I do not have a nandroid backup (yes, I know, a dumb move).
Any suggestions on what to try next? I'm at my wit's end with this. I've searched the web all morning and found all kinds of helpful info, but I can't find anything to get me past this point. I am perfectly willing to wipe it all out and start over again if I could just force it to do that. I just bought it so I suppose I could return it (I think there's a 30-day return policy), but Google might not like it if it comes back in this state, I suppose. I had an AT&T Galaxy Note 5 for half a day but found out, after the fact, that I can't root it.
Thanks for any help or suggestions.
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
jaidev.s said:
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
Click to expand...
Click to collapse
I saw that post. I wish I had followed it. However, the instructions are very similar to what I tried, although not exact. Where I went wrong is letting TWRP install SuperSU for me. I didn't mean to but when I touched the phone it installed it (of course, I hit something, but I don't know what). Fastboot does not recognize the phone in recovery. I can follow Heisenberg's instructions to get back to stock IF fastboot would recognize the phone. ADB recognizes the phone. Would it be possible to use ADB Sideload instead? How can I force fastboot to recognize the phone? If I could do that, I would be able to flash images back to the phone. Thanks!
U should try fastboot in bootloader / download mode instead of recovery mode..
OK, two comments: Duh (as I slap my head) and Bless You! That worked. I'm back to stock. At least the phone works now. I'll try again to root following Heinsenberg's instructions! Thanks. Where do I sent the beer money?
jaidev.s said:
U should try fastboot in bootloader / download mode instead of recovery mode..
Click to expand...
Click to collapse
Well, I'm back to a stock phone, anyway. Flashing SuperSU per Heinsenberg's instructions did not give me root. Oh well. I'll keep trying. It did install and it did reboot just fine. However, root checker says I have no root and Titanium Backup won't run, either. Thanks.
*** NOTE: Please excuse my English.
*** WARNING: I'm not responsible if anything happens to your device, I'm just sharing my experience and what I did to fix my own phone. Proceed at your own RISK.
I bought my Nexus 6p 64gb and as soon as I took it out of the box, I went directly and followed the guide here. So i unlocked the bootloader, flashed TWRP as a custom recovery, flashed CM13 + OpenGapps.
I noticed that every time I boot my device I get this warning:
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
and it does not seem to be a normal warning because when my OS boots up it shows me this
"Android system:
There’s an internal problem with your device. Contact your manufacturer for details"
Later on when I updated to the latest nightly image my camera crashes and doesn't function properly. I also already has an issue with Bluetooth and "Bluetooth share" crashing but that was unrelated. Anyways I was crippled in my day to day usage. Then I thought that I need to fix this asap because it might cause performance/security/hardware problems in the future.
So basically the fix is you should flash the latest bootloader image and radio image. Personally I wanted to start clean and make sure I have no corrupted files so here is what I did,
1. What i did is erase all boot, system, kernel & recovery files by typing the below command using fastboot just incase they were corrupted,
(Note: YOU DONT NEED TO DO THIS STEP, but i prefer starting clean incase i had some corrupted files. YOU WILL ALSO LOSE ENCRYPTION DOING THE FIRST STEP)
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
Source: http://devs-lab.com/...i-nexus-6p.html
2. Then i flashed the latest factory images in this sequence using fastboot, which can be found here: https://developers.g...s/images#angler
(Note: 6.0.1 (MMB29M) was latest image at the time i did this. For people who are doing this for the first time, then you just need to download the image then extract the needed files from it)
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot format userdata
fastboot reboot
Source: http://forum.xda-dev...operly-t3268407
3. From there i reflashed TWRP using fastboot, then flashed the latest beta SuperSU v2.62 at the time, and then CM13, then OpenGapps, then again reflashed SuperSU v2.62 just incase, lol. (Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When using TWRP before you've actually flashed SuperSU 2.50+, when you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.)
What got fixed ?
-FIXED, this won't show up anymore:
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
-FIXED, this won't show up anymore:
Android system:
There’s an internal problem with your device. Contact your manufacturer for details.
-FIXED, Camera is working !
-NOT FIXED, "Bluetooth share" still crashes but I think its unrelated to this issue.
Hope this helps everyone as it helped me, thanks.
Sent from my Nexus 6P using Tapatalk
\*O / Thank you !!
Thanks, but better option? Don't reboot.
Sent from my Nexus 6P using Tapatalk
bob_mord_les said:
\*O / Thank you !!
Click to expand...
Click to collapse
Ur welcome [emoji1]
Sent from my Nexus 6P using Tapatalk
Followed your guide, thanks, but the message "Your device is corrupt. It can’t betrusted and may not work properly." still appears during a CM boot.
The message "There’s an internal problem with your device. Contact your manufacturer for details" appears when I boot into recovery (TWRP)
The camera is working now.
Also, before I was able to flash CM-13 I had to do "WIPE >> Format Data" from TWRP, otherwise CM was exiting with error 7.
The following packages were used:
original 6.0.1 (MMB29P) factory image
BETA-SuperSU-v2.66-20160103015024.zip
cm-13.0-20160115-NIGHTLY-angler.zip
open_gapps-arm64-6.0-micro-20160115.zip
twrp-2.8.7.2-angler.img
I also noticed that when rebooting into factory image, the same warning message appears as well.
Any way to fix it or did I do something wrong?
Why are people trying to fix an non issue? To get rid of the message you need to relock the bootloader which is more of a risk if your rooted. Its a message that only appears for a few seconds when you reboot and you don't need to do anything to get past it.
There is no corruption and the phone is trusted by YOU as you unlocked it and nothing else cares. Where is the issue?
g_kos said:
Followed your guide, thanks, but the message "Your device is corrupt. It can’t betrusted and may not work properly." still appears during a CM boot.
The message "There’s an internal problem with your device. Contact your manufacturer for details" appears when I boot into recovery (TWRP)
The camera is working now.
Also, before I was able to flash CM-13 I had to do "WIPE >> Format Data" from TWRP, otherwise CM was exiting with error 7.
The following packages were used:
original 6.0.1 (MMB29P) factory image
BETA-SuperSU-v2.66-20160103015024.zip
cm-13.0-20160115-NIGHTLY-angler.zip
open_gapps-arm64-6.0-micro-20160115.zip
twrp-2.8.7.2-angler.img
I also noticed that when rebooting into factory image, the same warning message appears as well.
Any way to fix it or did I do something wrong?
Click to expand...
Click to collapse
It's just telling you what you already know. You modified your system partition yourself so don't worry about it.
https://support.google.com/nexus/answer/6185381?hl=en
XxMORPHEOUSxX said:
It's just telling you what you already know. You modified your system partition yourself so don't worry about it.
https://support.google.com/nexus/answer/6185381?hl=en
Click to expand...
Click to collapse
Thanks. I read it in the original Heisenberg's unlock guide and was surprised when I read this post that it was possible to get rid of the warning message without locking the bootloader .
I'm new here in the forum's..I usually just read and carry on..the one think I'd like to say is..I don't understand why people got to say 'why you doing that for, ya don't need to' far as I know..this an educational site to learn..if he wants learn how to get rid of the warning..I don't see any problems in that whatsoever.
The message "There is an internal problem with your device..." seems to be related to the security patch version. This was my biggest issue, the message I get when booting the phone was annoying and I knew it was not a big deal, but having an internal problem warning was concerning, flashing the vendor image was the solution for me. But if you like to start clean then I have the steps written, but if you update then again you'll get the warning when booting up.
Sent from my Nexus 6P using Tapatalk
zooman31 said:
I'm new here in the forum's..I usually just read and carry on..the one think I'd like to say is..I don't understand why people got to say 'why you doing that for, ya don't need to' far as I know..this an educational site to learn..if he wants learn how to get rid of the warning..I don't see any problems in that whatsoever.
Click to expand...
Click to collapse
I think what people are trying to say is the risk/reward for getting rid of the message is not worth it. Especially since its just a brief warning you only see during boot. Just flashing twrp recovery will give the red message. SuperSU will help get rid of it which is why the OP was able to remedy it. It will not work for everyone though. Modifying the bootloader is the only sure fire way to snuff it out for good and you would be a fool to try and mess with your bootloader for something aesthetic. That's how most real bricks happen, is when a bootloader gets corrupted.
XxMORPHEOUSxX said:
I think what people are trying to say is the risk/reward for getting rid of the message is not worth it. Especially since its just a brief warning you only see during bouot. Just flashing twrp recovery will give the red message. SuperSU will help get rid of it which is why the OP was able to remedy it. It will not work for everyone though. Modifying the bootloader is the only sure fire way to snuff it out for good and you would be a fool to try and mess with your bootloader for something aesthetic. That's how most real bricks happen, is when a bootloader gets corrupted.
Click to expand...
Click to collapse
I assume that most people know the drill..you proceed to test at your own risk..the how to in the first post seemed to have worked after it was tested by the author.
zooman31 said:
I assume that most people know the drill..you proceed to test at your own risk..the how to in the first post seemed to have worked after it was tested by the author.
Click to expand...
Click to collapse
Basically just flash SuperSU last in whatever sequence, and as long as it boots,the red message will be gone. But change anything after and it will probably come back. I have nothing negative to say about this thread. I originally posted the nexus link just so people can rest assured that it is not an actual problem and a normal, albeit annoying, side effect of modifying the Nexus 6p. Happy Flashing
XxMORPHEOUSxX said:
Basically just flash SuperSU last in whatever sequence, and as long as it boots,the red message will be gone. But change anything after and it will probably come back. I have nothing negative to say about this thread. I originally posted the nexus link just so people can rest assured that it is not an actual problem and a normal, albeit annoying, side effect of modifying the Nexus 6p. Happy Flashing
Click to expand...
Click to collapse
all i did was flash twrp and unlocked the bootloader and still got the red message. so all i have to do is flash supersu and root? to get rid of it?
TechMillz93 said:
all i did was flash twrp and unlocked the bootloader and still got the red message. so all i have to do is flash supersu and root? to get rid of it?
Click to expand...
Click to collapse
Yes. The SuperSU beta 2.66 is what I use.
XxMORPHEOUSxX said:
Yes. The SuperSU beta 2.66 is what I use.
Click to expand...
Click to collapse
so i just reflashed the vendor and now im in bootloop ;(
TechMillz93 said:
so i just reflashed the vendor and now im in bootloop ;(
Click to expand...
Click to collapse
Why did you flash vendor? Try clearing caches and then reboot. Let it sit for 10 min too while starting up.
XxMORPHEOUSxX said:
Why did you flash vendor? Try clearing caches and then reboot. Let it sit for 10 min too while starting up.
Click to expand...
Click to collapse
im good now i just reflashed all the images im good.
but i have to feflash twrp now, what would u recommend
systemless or traditional ?
TechMillz93 said:
im good now i just reflashed all the images im good.
but i have to feflash twrp now, what would u recommend
systemless or traditional ?
Click to expand...
Click to collapse
Systemless unless you want to use xposed otherwise it doesn't matter. Systemless just makes it so you can use root apps like android pay. I use the 2.66 systemless. The instructions are a little all over the place on that thread. You no longer need a modified boot.IMG. the SuperSU zip patches whatever boot.IMG you have. So all you need to flash is the supersu2.66 for systemless or the traditional zip if going that route.
XxMORPHEOUSxX said:
Systemless unless you want to use xposed otherwise it doesn't matter. Systemless just makes it so you can use root apps like android pay. I use the 2.66 systemless. The instructions are a little all over the place on that thread. You no longer need a modified boot.IMG. the SuperSU zip patches whatever boot.IMG you have. So all you need to flash is the supersu2.66 for systemless or the traditional zip if going that route.
Click to expand...
Click to collapse
so i dont need gapps etc?
its all in there?
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
Yes you can via Rczrider 's TWRP backup
tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
XblackdemonX said:
Yes you can via Rczrider 's TWRP backup
Click to expand...
Click to collapse
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
rczrider said:
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Click to expand...
Click to collapse
if someone can make a guide on HOW-TO (Steps + FIles + Images needed) i can give it a shot...
just send me a PM if you know the HOW-TO :good:
Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?
DrakenFX said:
Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?
Click to expand...
Click to collapse
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!
tele_jas said:
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!
Click to expand...
Click to collapse
I'm curious too and I wanna give it shot,
P. S. Any way to use terminal or adb to pull the partition list with their Extension?
Like for sample. " ext4 system /dev/block/sde13 " or something similar with extension?
Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread
tele_jas said:
Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread
Click to expand...
Click to collapse
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader
It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet
peramikic said:
It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet
Click to expand...
Click to collapse
those steps were the same i was planning to do plus flashing something else, but seems like i may be not doing the other flashing file now......well still gathering more info and will see.
P.S. Thanks for the info. @peramikic
DrakenFX said:
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader
Click to expand...
Click to collapse
Gottcha.... I was just curious, because I'm starting to have a few random issues (reboots, apps opening without tapping them, google voice commands not working like they did just a few days ago) I'd like to get back to stock and maybe start over. Of course, I didn't make a backup up until after I flashed SuperSU and my apps downloaded so I have no "stock" TWRP backup. **But, this all could be "theme" related too, since I'm running a dark theme that isn't quite compatible with the A7 yet.
I may try removing the theme and let it run a day or two and see how it does?
I made a mistake when installing TWRP 3.0.2 on Moto G4 XT1625 US retail version. I selected read-only. So, when I boot back in, I get "No command" in recovery, presumaby stock recovery overwrote TWRP. I can still flash recovery from fastboot and then boot into TWRP, but it does not stay permanent. I can no longer go back and choose to allow TWRP to make changes.
I also found these instructions here:
http://android.stackexchange.com/questions/150211/booting-into-twrp-unsuccessful
But I'm still unable to make TWRP permanent.
When I installed CM13, it made changes so that TWRP is permanent (i.e., it survives when rebooted). But I can't do it with stock as I made a mistake mentioned above. For the time being, I want to go back to stock with TWRP made permanent so that I can install ROMs in the future. Since CM13 was able to make it persistent, I presume there must be some way to allow that to happen.
So, how do I make TWRP permanent with stock, given the mistake made earlier?
thanks
Stock firmware will always re-write the bootloader with the official one. You can always do "fastboot boot twrp...." followed immediately by the installation other ROMS, zips, etc (don't reboot to Android until you are done).
There is no reason to make TWRP permanent - except if you go on the CM ROM's path.
SoNic67 said:
Stock firmware will always re-write the bootloader with the official one. You can always do "fastboot boot twrp...." followed immediately by the installation other ROMS, zips, etc (don't reboot to Android until you are done).
There is no reason to make TWRP permanent - except if you go on the CM ROM's path.
Click to expand...
Click to collapse
That's true. It is just that, without TWRP permanent on the phone, I have to use a computer every time I want to do flashing, backup or restore.
You can move to a CM ROM and you don't need that.
However, flashing without access to a PC with ABD is really not something that you should do. Unless you don't mind to have the phone service cut out...
Have you thought about flashing stock firmware and starting from scratch?
SoNic67 said:
However, flashing without access to a PC with ABD is really not something that you should do. Unless you don't mind to have the phone service cut out...
Click to expand...
Click to collapse
I would say to do so is playing with fire.
---------- Post added at 07:22 AM ---------- Previous post was at 07:18 AM ----------
hooks024 said:
Have you thought about flashing stock firmware and starting from scratch?
Click to expand...
Click to collapse
My exact thoughts! :good:
On some phones, You can flash twrp from a terminal app if your phone is rooted.
Sent from my LG-LS980 using Tapatalk
SoNic67 said:
You can move to a CM ROM and you don't need that.
However, flashing without access to a PC with ABD is really not something that you should do. Unless you don't mind to have the phone service cut out...
Click to expand...
Click to collapse
I did mentioned that when I installed CM13, I did have root. But the battery life was a lot worse than stock.
And yes, the PC is around for when things go wrong. But in most cases, unless there are big things to change, I don't find the need to use the PC for flashing.
hooks024 said:
Have you thought about flashing stock firmware and starting from scratch?
Click to expand...
Click to collapse
Yes... that will be my last resort.
I am now back to stock using a Nandroid backup, but that seems to have /system partition read-only as I can't seem to root (most likely due to my mistake at the beginning). As a last resort I will have to go back by doing everything from scratch. But at this time, I'm not rushing as I have a long overseas trip coming up soon and I don't want to risk being unable to use my phone overseas. Besides, Nougat seems to around the corner....
Hey guys, I'm a little devastated. Hoping I didn't ruin my phone.
So, earlier today I unlocked my Moto G4 Plus's bootloader and installed TWRP recovery. I installed ElementalX and a superuser.zip file as well. After reboot, there was no superuser in my app drawer and when I checked my root status with Phh's Root Checker, it said that my phone was not rooted properly. I then found the guide here on how to root, and noticed that it had Phh's SuperUser. I changed the config.txt file like mentioned in the guide, booted into TWRP recovery and installed it and clicked on reboot. I got the usual bootloader unlocked message, but after that my screen went blackish-grey and has been that way since, which is about 15-20 minutes now. I (panicking and being a noob) tried switching it off using the power button which didn't work. I then checked to see if it showed up as connected device in android sdk/fastboot, which it didn't.
WHAT DO I DO? I can't just buy another phone since I can't afford it as I recently bought this one, so it's a really big deal for me. :crying:
PLEASE HELP ME.
Thank you.
UPDATE.
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
UPDATE #2
So I did what abhi212b told me to do and flashed the stock rom. Everything is fine now.
I'll try rooting it again a bit later. Thanks for the help.
UPDATE #3
I tried rooting my phone again, and it went flawlessly this time! Rooted successfully.
What an emotional rollercoaster lol.
Push the power button for at least 2-3 minutes. Worked for me and others in the past.
SSJGod said:
Hey guys, I'm a little devastated. Hoping I didn't ruin my phone.
So, earlier today I unlocked my Moto G4 Plus's bootloader and installed TWRP recovery. I installed ElementalX and a superuser.zip file as well. After reboot, there was no superuser in my app drawer and when I checked my root status with Phh's Root Checker, it said that my phone was not rooted properly. I then found the guide here on how to root, and noticed that it had Phh's SuperUser. I changed the config.txt file like mentioned in the guide, booted into TWRP recovery and installed it and clicked on reboot. I got the usual bootloader unlocked message, but after that my screen went blackish-grey and has been that way since, which is about 15-20 minutes now. I (panicking and being a noob) tried switching it off using the power button which didn't work. I then checked to see if it showed up as connected device in android sdk/fastboot, which it didn't.
WHAT DO I DO? I can't just buy another phone since I can't afford it as I recently bought this one, so it's a really big deal for me. :crying:
PLEASE HELP ME.
Thank you.
Click to expand...
Click to collapse
Like the poster above stated, hold the power button until the screen shuts off. YOUR PHONE WILL AUTO REBOOT!!! The instant the screen turns off, begin holding the volume down button. When you see the fastboot screen pop up, begin flashing your N images again, or use a custom ROM (which are generally much faster, easier to mess with, and easier to recover from).
Ex didn't flash properly.. That is what I can estimate! If u root on stock kernel, it breaks the device.
As said above go to bootloader (works on any screen... Power and volume down) and then to twrp maybe (flash twrp from fastboot). And then restore any previous nandroid u have.. If not u will have to flash stock via fastboot and then flash ex kernel. When u flash, restart and go to about phone and see if the kernel shows elemental x.. If yes, go to twrp and root it via suoersu, phhh's superuser or magisk su.. Whichever u like.. That should be fine!
UPDATE.
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
SSJGod said:
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
Click to expand...
Click to collapse
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
abhi212b said:
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Click to expand...
Click to collapse
Thank you, will try this now.
Only the last SuperSU Beta defaults to systemless install. Any other ones require writing of a .SuperSU file to force systemless before rooting.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
SSJGod said:
Thank you, will try this now.
Click to expand...
Click to collapse
If you have not done this already, you can give it a try by flashing the stock boot.img via twrp and see if that boots the device.
I am not sure that it will work since, i have not tried it.
Exact same thing with the XT1625. I have also found that the systemless method of rooting with SuperSU kills my wifi and cellular network's connection abilities, which might just be a standard G4 thing but the only way I know of to fix it is reflashing the OS (data wipe not necessary).
Just thought this might be helpful to anyone who ran into similar issues to the ones I had.
also i'm still having issues with the stupid thing actually rooting but i'm gonna try again some other day.
just_magikkal said:
Exact same thing with the XT1625. I have also found that the systemless method of rooting with SuperSU kills my wifi and cellular network's connection abilities, which might just be a standard G4 thing but the only way I know of to fix it is reflashing the OS (data wipe not necessary).
Just thought this might be helpful to anyone who ran into similar issues to the ones I had.
also i'm still having issues with the stupid thing actually rooting but i'm gonna try again some other day.
Click to expand...
Click to collapse
I think that is the kernel issue.. you should try EX.. and then use SuperSU or maybe use Magisk SU..
abhi212b said:
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Click to expand...
Click to collapse
Had the same problem as OP and this fixed it, thanks a lot man!
Good to hear now the phone is alive!