Related
Hello,
I have succesfully rooted my phone and installed Android Revolution HD 6.x
After I saw that 7.0 was released I installed total wipe (the zip file) and the new rom zip file to my sd card.
I installed the total wipe and then the rom and now it loops.
I have tried everything the forum has told me, but no result.
Flashing won't help. It does not regonize the phone. I tried everything on the forum.
Is there anyone out there that can help me with this problem. I am not a total nubb so don't be gentle with the words/ solutions..........
Please help me!!!
Kind regards
Casper
windows7mce said:
Hello,
I have succesfully rooted my phone and installed Android Revolution HD 6.x
After I saw that 7.0 was released I installed total wipe (the zip file) and the new rom zip file to my sd card.
I installed the total wipe and then the rom and now it loops.
I have tried everything the forum has told me, but no result.
Flashing won't help. It does not regonize the phone. I tried everything on the forum.
Is there anyone out there that can help me with this problem. I am not a total nubb so don't be gentle with the words/ solutions..........
Please help me!!!
Kind regards
Casper
Click to expand...
Click to collapse
did you post in this place ?
I insist to post there it's impossible not to get help here this is a Big Brother phone:cyclops:
loops at what level when starting at splashscreen or later when running bootanimation (just before to enter Android interface)
loops usually happen just because this is not a clean flashing
unfortunately you have work to do: try to describe in details how you made that upgrade
have you used CWM-clockworkmod recovery ?
what do you mean by " not recognize the phone" ? have you tried to reinstall ADB drivers ?
if by looping you mean looping at the boot animation, you have to erase the cache with fastboot... and fyi i DID find the answer here at xda...
I've seen this problem mentioned in a few threads but not seen any definitive fix.
My current install :
Stock NPD35K system, vendor, bootloader
Xceede's v8.01 kernel
TWRP 3.02 v6.0
Encrypted data partition
I currently get bootloops every time I boot into TWRP. After using TWRP and attempting to reboot it will then bootloop into recovery refusing to boot the system.
I have found it can be fixed by rebooting into fastboot and the "fastboot reboot" command. But this is frustrating if I don't have a laptop handy.
This happens every time I need to boot into recovery to install or update via TWRP. Is anyone else getting the same bootloops and has anyone found a permanent fix?
Thanks guys.
Sent from my Nexus 6P using Tapatalk
Hi Jake,
I had exactly the same issue since NPD35K except the fastboot reboot solution did not work for me.
What i could find was that if you flash the default vendor, recovery and cache partition via fastboot and then put off the tablet, it should after all of this boot correctly to the system.
Cheers,
Mathieu
You are not alone ..
I had the recovery bootloop once myself.
I did the "fastboot reboot" command and since then the Pixel C is booting fine again.
Did several installations afterwards .. no problems anymore.
Just once ..
But if you get it every reboot this a real problem.
Right now I am not able to help you .. just don't know the root cause and how to fix it.
As it looks like, it helps if you go back to stock recovery, like mentioned above.
I can not confirm this .. as I don't have the problem.
Good luck !
Thanks for the advice guys.
As I said it only bootloops immediately after boating into TWRP (even if I don't install anything), if I reboot from system it's fine.
At the moment I prefer to keep TWRP installed and reboot from fastboot if I need to use TWRP. I don't see an advantage to installing the stock recovery. It would be great to pinpoint what's causing this though.
Sent from my Pixel C using Tapatalk
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
badwiring said:
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
Click to expand...
Click to collapse
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well.
Reboot directly into TWRP and not into system in between.
Install SuperSu.zip v2.79 in TWRP.
Reboot into system.
The first time the system will boot twice .. it's normal.
followmsi said:
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well..
Click to expand...
Click to collapse
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
badwiring said:
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
Click to expand...
Click to collapse
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
EDIT: .. no need to wipe data here. Just a fresh system, vendor, cache and boot image from factory image.
followmsi said:
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
Click to expand...
Click to collapse
I think that answers my question - the original factory image including the bootloader.
I'll try it in a few hours. Thank you very much!
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
badwiring said:
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
Click to expand...
Click to collapse
You are welcome ..
``
tried numerous times to flash TWRP to my Pixel C 8.0.0 (OPR1.170623.032, Nov 2017) every time with bootloop in to recovery...
most recently hoping twrp-3.2.0-0-dragon would work
---------- Post added at 07:44 PM ---------- Previous post was at 07:29 PM ----------
tried to reflash ryu-opr1.170623.032-factory-020f1cf9's boot.img and it still bootlooped.
Tried to flash the recovery and now its bootlooping into stock recovery. Any ideas?
for a stock google device, this things a nightmare to work with compared to my nexus devices
hey guys,
i have a big problem.
i unlocked my one+ 3 2 weeks ago and installed twrp and cm13. all worked fine.
yesterday i read the news from cm the first devices will get offical cm14.
so i donwloaded the first rom and updated my phone (without a wipe!).
the cm14 starts good and all worked fine.
But, i find out, i can´t hear a phone call.
so, i want to go back to the twrp to restore my backup of cm13.
the problems begins....
i can´t boot twrp. i see the bootloader screen and after switching the screen to recovery (normaly) i got a black screen (seems like to shut off the screen).
then i tried to reinstall it, nothing.
after a full evening of trying i wiped it (factory reset) from android 7.
after the reboot i got the same problem. -> black screen after bootscreen Android won´t start, recovery won´t start.
then i downloaded a toolbox and installed the stock recovery -> no change -> black screen.
then i tried to find a stock image als *.img format to flash it with all (kernel and recovery, etc) with fastboot, but i didn´t find an image.
my last try was to make a full wipe with "fastboot -w". but this won´t work too.
so, now my phone will only boot into fastboot and thats it.
i need urgend help.
can anyone tell me what i can do? how can i install any os and wipe via fastboot and with no recovery?
thx a lot for your help.
ravn
ravn83 said:
hey guys,
i have a big problem.
i unlocked my one+ 3 2 weeks ago and installed twrp and cm13. all worked fine.
yesterday i read the news from cm the first devices will get offical cm14.
so i donwloaded the first rom and updated my phone (without a wipe!).
the cm14 starts good and all worked fine.
But, i find out, i can´t hear a phone call.
so, i want to go back to the twrp to restore my backup of cm13.
the problems begins....
i can´t boot twrp. i see the bootloader screen and after switching the screen to recovery (normaly) i got a black screen (seems like to shut off the screen).
then i tried to reinstall it, nothing.
after a full evening of trying i wiped it (factory reset) from android 7.
after the reboot i got the same problem. -> black screen after bootscreen Android won´t start, recovery won´t start.
then i downloaded a toolbox and installed the stock recovery -> no change -> black screen.
then i tried to find a stock image als *.img format to flash it with all (kernel and recovery, etc) with fastboot, but i didn´t find an image.
my last try was to make a full wipe with "fastboot -w". but this won´t work too.
so, now my phone will only boot into fastboot and thats it.
i need urgend help.
can anyone tell me what i can do? how can i install any os and wipe via fastboot and with no recovery?
thx a lot for your help.
ravn
Click to expand...
Click to collapse
Lots off people are getting this problem and trust me for some reason people post steps to fix this that are complicated for people who are just getting to playing around with TWRP.
Look, download the original TWRP recovery from here, https://dl.twrp.me/oneplus3/ the one you need is the 3.0.2-1 . I used it and I got back to MC13 From MC14.1 which by the way is now working pretty good. Once you fastboot flash recovery .this 3.0.2-1 recovery you can actually use it with MC14.1 as am doing right now. In any case. flash recovery >factory reset > adb your MC13 Zip to the phone > reboot...
Remember All Of This Steps Are Always Taken At Your Own Risk !!
Best of luck!!! [emoji6]
Sent from my ONEPLUS A3000 using Tapatalk
DiMatador said:
Lots off people are getting this problem and trust me for some reason people post steps to fix this that are complicated for people who are just getting to playing around with TWRP.
Look, download the original TWRP recovery from here, https://dl.twrp.me/oneplus3/ the one you need is the 3.0.2-1 . I used it and I got back to MC13 From MC14.1 which by the way is now working pretty good. Once you fastboot flash recovery .this 3.0.2-1 recovery you can actually use it with MC14.1 as am doing right now. In any case. flash recovery >factory reset > adb your MC13 Zip to the phone > reboot...
Remember All Of This Steps Are Always Taken At Your Own Risk !!
Best of luck!!! [emoji6]
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply.
to flash only the new recovery will not help.
tomorrow i will try to flash, wipe (with "fastboot -w" and copy the zip file.
Will the copy install the cm13 version? or do u mean sideload to have the cm13 zip for the twrp to flash?
Try to flash the modified twrp. Check the official topic for cm 14, it is linked over there
Edit: this one http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
superiscch said:
Try to flash the modified twrp. Check the official topic for cm 14, it is linked over there
Edit: this one http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
@superiscch just provided you with the TWRP that works. This is what i did !
Flash the recovery provided on the link >boot to the new recovery, you well see the version at the top left corner as 3.0.2-1 > factory reset > adb sideload the MC 13 ....... Reboot system > than add your choice of google apps to the sdcard root > reboot to recovery > flash google apps from with recovery than reboot, you would be golden. After, if your interested just flash the TWRP from the original twrp team. Cuss the one you just installed is modified, it be your choice !!
Sent from my ONEPLUS A3000 using Tapatalk
Hey guys,
thx for your replay. i will try it after work.
but i have one question ... what do u mean exactly with " adb your MC13 Zip"?
do u mean to transfer the zip to install with twrp or is there a command to install the zip to the systempartition?
ravn83 said:
Hey guys,
thx for your replay. i will try it after work.
but i have one question ... what do u mean exactly with " adb your MC13 Zip"?
do u mean to transfer the zip to install with twrp or is there a command to install the zip to the systempartition?
Click to expand...
Click to collapse
Okay... Look, once you have flash the modified recovery and you reboot. You be able to boot to your OS. Than you have to simple options 1. Load the CM13 ZIP file to your sdcard which you can use for installing with recovery
2. Boot into recovery and side load the MC 13 ZIP file into your phone using adb...sideload would be using adb
ADB... adb sideload <name of file> without the brackets...
Good luck man
Sent from my ONEPLUS A3000 using Tapatalk
Thx a lot guys, now it works and in installed my phone successfully.
it was the wrong twrp version.
now, the weekend is save :silly:
ravn83 said:
Thx a lot guys, now it works and in installed my phone successfully.
it was the wrong twrp version.
now, the weekend is save :silly:
Click to expand...
Click to collapse
Alriiiight !!
Sent from my ONEPLUS A3000 using Tapatalk
Hi guys I got bootloop in my moto g5. First I got "failed to mount /data", now the phone boots in unlocked warning screen then says "erasing" then reboots and start over again.
Before the procedure my actions was:
- I got OTA update
- inserted a microSD
- unlocked bootloader
- boot on TWRP 3.1.0
- backup to microSD
-install TWRP
as shown by bootloader screen, my model is "cedric XT1672 32GB P5", M8937_8000.122.02.45R CEDRIC_BRAZILDSDS_CUST.
What I don't understand is why TWRP don't restore, as a made a backup before the procedure.
I appreciate if somebody could help me out!
I had the same problem. Wiping /data corrupted my partition table or system partition.
You need to flash the system and / or the partition table via fastboot from the extracted stock rom (see the other thread arround here, make sure you use the right link (cedric, not the potter one)
-> boot to fastboot
fastboot flash system system.sparsechunk.0
fastboot flash system system.sparsechunk.1
...
It should boot normally afterwards, but probably twrp is gone / twrp has no access to your /data again. See the twrp thread, i'm facing the same issue. But at least the phone works again - without root
Greetings,
Chris
-> boot to fastboot
fastboot flash system system.sparsechunk.0
fastboot flash system system.sparsechunk.1
Click to expand...
Click to collapse
Did not work for me!
I hope you flashed all the system files?
Otherwise try to flash the full stock rom via fastboot. There are tons of guides explaining
Help NPP25.137-33 It doesn't work filefactory
.sirhc said:
I hope you flashed all the system files?
Otherwise try to flash the full stock rom via fastboot. There are tons of guides explaining
Click to expand...
Click to collapse
Help with stock NPP25.137-33 someone who has it in google driver to download
Got it back I, like you said! The first time I think I got any of those system file corrupted!!
I just dont know until when it gonna be good cos I am going to root this s.. now!
thks
linsspinho said:
Got it back I, like you said! The first time I think I got any of those system file corrupted!!
I just dont know until when it gonna be good cos I am going to root this s.. now!
thks
Click to expand...
Click to collapse
// already found how to root. won't do it right now as there are no success stories
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
I have the same problem, it comes back to recovery all the time and we can tell you about it, some help please
---------- Post added at 09:59 PM ---------- Previous post was at 09:43 PM ----------
Hi, I've come back, hahaha, I installed resurrection remix 7.1, previous all the wipes and reboot in bootloader I gave start and started, great.
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
CypherPotato said:
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
Click to expand...
Click to collapse
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
SuperUtilisateur said:
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
Click to expand...
Click to collapse
Have you tried to boot from Fastboot?
Yes, it works once...
But if I have to restart it (or turn off and start with the power button), the phone boot always in recovery.
It is then necessary to restart fastboot then press "start".
Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
Try do a full reset through fastboot and then try installing whatever you need through fastboot and recovery. Much more reliable han ota installs/updates
Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
grosobart said:
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
Click to expand...
Click to collapse
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
It always says that
As long as it says at the end
Write OK
It flashed successfully
OK,
After flash,
boots automatically into recovery ...
--
I tried with various boot.img. (linéage, AOSP, OctOS, ... )
Does not work ..
I started (into fastboot), I was errors. (Process stopped)
I just restored my phone ( https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/ )
... boot correctly.
Never mind ...
thank you all
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/how-to/fyi-recovered-g5-xt-1676-to-stock-t3626088
try this first, regards
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Moto G5 boots to TWRP
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Backing up Gigs of data is a huge pain. Even if I have to copy to my pc. So, just something that's less cumbersome.
Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Read the faq section (2nd post) - answer is there
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
grosobart said:
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Click to expand...
Click to collapse
Anyone get the stock for 16gb/2gb version?