Hello
I was trying to update my friend´s i9505 to the latest AntaresOne CM12 build, but forgot to flash gapps, and since i coulnd´t for some reason enter CWM (the phone just reboots), i had to flash stock firmware over again so i could start over.
But now the phone isn´t booting even on stock firmware. That usually did the trick.
The wierd thing is that Phils Touch Recovery was working before, but ever since i used Triangle Away to reset binary counter, the recovery won´t boot up anymore.
The only way that i could get into Phils Recovery was to install the TWRP recovery installer, and throught the app i would tell it to flash, and it would reboot into Phils Recovery
Now since system isn´t booting, i can´t install and use the TWRP installer to reboot into recovery mode for me.
Tried to flash stock recovery, the same thing happens: the phone just black screens, vibrates and reboots.
Any ideas of why this might be happening?
Go to stock recovery if you can and wipe data/factory reset. Install stock ROM then.
@guguts
As clearly wrote in 1st post of my thread, you need to do "format /system" before installing ROM's builds starting from 26/11 one and latest ones, including 3/12 and the ones that will come in the future.
I strongly suggest you to take a look again at installation instructions, but this time carefully.
If you need anything else, write directly in its Q&A thread (you can find it in this section) where surely you can be helped more and better
Inviato dal mio GT-I9505
Flash a custom recovery with Odin. Uncheck auto-reboot before flashing.
Then boot into the recovery using the botton combo. Keep holding it as long as it takes to enter recovery.
Hey guys, i managed to work it out.
It was probably a loose vol up or home button, because i didn´t do anything but a few moments later i tried to enter stock recovery and it went fine.
The issue was not with the custom rom (which by the way is great, my friend says its running smooth).
The issue happened because i forgot to do i data wipe after installing the rom and prior to installing the stock rom.
So the stock ROM was trying to load using lollipop data and cache, and thats why it got stuck in the samsung logo.
As soon as i managed to enter stock recovery again, and made a data wipe, the stock room booted fine.
So i tried again, but this time didn´t forget to flash gapps, and even better, now Phils Recovery is booting up normally (go figure...)
So i formated /system and /data, flashed AntaresOne ROM and gapps, and everything went fine.
Just posting here in case anyone in the future goes througyht the same hassle.
Thank you so much for your work Antares.
Its people like you, quarx and pawtip (and many others top developers) that makes this community great.
Related
Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati
Nepoznati said:
Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati
Click to expand...
Click to collapse
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).
antique_sonic said:
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).
Click to expand...
Click to collapse
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?
Nepoznati said:
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?
Click to expand...
Click to collapse
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.
SOLVED
antique_sonic said:
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.
Click to expand...
Click to collapse
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!
Nepoznati said:
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!
Click to expand...
Click to collapse
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.
antique_sonic said:
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.
Click to expand...
Click to collapse
It could probably be a problem with TWRP as you mentioned earlier. After using CWM everything went smooth after updating my kernel. Last night I couldnt hold me back to try one more time, and I flashed X-NOTE with TWRP and I got the same problem as described in #1 post. Then I installed CWM and flashed X-NOTE again and everything got messed up. Then I restored everything, force installed the kernel and bootlaoder. After that installed CWM and then I was able to run X-NOTE without any problem.
I am not a professional developer but I may think that the problem is TWRP when it tries to flash the kernel under the process with may results in some problems. When using CWM from the beginning I do not get any problems but when using TWRP I need to restore everything back.
Hello,
I've rooted my own note 3 and flashed Temaseks unofficial cm 12 rom. Everything works perfect so I decided to do the same thing for my father. It all went well, first I rooted his phone, then I flashed CWM and flashed cm 12 by temasek. The rom works fine but I forget to install the Gapps. So I tried to install Gapps but I got an error "Failure Status 6". I googled on that error and someone told it has to do something with CWM. I tried to flash a different version of CWM but now I can't reboot into recovery mode anymore. So I can't flash anything.
I flashed another version of CWM but this one also doesn't work. Whenever I try to boot the phone into recovery mode, the blue line shows up. Rebooting into recovery mode, but after a few secs, the phone just boots the normal way. Is there anyone that can help me to get CWM back to work? In the mean time I'll try to flash TWRP by Odin.
Thanks in advance!
So I flashed latest version of CWM: Buildversion; 6.13.0, CWM Base Version V6.0.4.7. I can reboot into recovery now but still can't install Google Apps due to failure status 6. On my own Phone I run a different version of CWM, but when I try to flash it, the phone won't boot into recovery mode anymore. It only boots into recovery when I flash this V6.0.4.7 . How can I get rid of this version and flash an older version of CWM?
You'll probably have to Odin back to stock and start over...
Morningstar said:
You'll probably have to Odin back to stock and start over...
Click to expand...
Click to collapse
You mean If there is no other way to get the Google Apps on the phone, I have to go back to stock. I did make a backup with CWM on the while it was running custom firmware. Now I have 4 files on my comuter, 3.tar and 1.md5 . If I recover them, I will still have this not working CWM version on my phone right? Isn't there a easier way to delete CWM, can I flash TWRP over CWM and see if it will install these Gapps?
Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.
Morningstar said:
Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.
Click to expand...
Click to collapse
I appreciate your effort, thank you. The recovery issue is solved. I flashed Chainfires Root script and that installed the stock recovery. However, when I tried to install and older CWM version I got back in the recovery reboot cycle. But once I installed the latest CWM it booted in recovery. So I flashed Chainfires Root once again and had the stock recovery back. From there on I tried to install TWRP but got the recovery boot cycle again. My phone is now running android 5.0.2 and I think that's the problem.... :S I'll try again to flash Chainfires Root script to get the stock recovery back. From there on I will try to flash the link you gave to me with Odin and hope that will fix it. Do you have any ideas on what I'm doing wrong?
Your version of TWRP works so far. It reboots into RecoveryMode. Now I'll wipe and try to install Temaseks Cm 12 followed by Gapps! Thanks so far!
Okay, it's solved. Can't thank you enough for you help. Bless you!!
No problem. Glad you got it figured out!
[emoji106]
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje
Hi guys, been using my rooted but otherwise stock OOS rom with TWRP and Magisk for the past few weeks. Today I decided to take the plunge and try either the Lineage OS or Resurrection Remix roms.
I'm using the latest OFFICIAL TWRP.
So I decrypted following the instructions to flash "no-verity-opt-encrypt-5.1.zip", then format data. All went well, so I then sent over the ROMS I wanted to try out. I started with the official ResurrectionRemix. Bootloop. Then the unofficial LineageOS. Bootloop.
Ok, well I guess I'm not gonna get to use any of the cool new OS's for awhile. I'll install the full stock firmware zip so I can have a working phone again. Bootloop.
Now when I say bootloop, the phone is booting to the BootAnimation and just repeating it. It shows the proper boot animation for whatever zip I have installed (resurrection/LOS/OOS), but it stays on there for up to 20 minutes before I have to hard reboot to the recovery again.
I decided to install the stock recovery trying a few methods. I first tried the ALL-IN-ONE tool. It said it flashed the recovery fine, so I booted to the recovery and after staying on a black screen for too long, the language options came up and I sighed a breath of relief. But before I could select English with the volume buttons, it rebooted by itself. It did this again when I manually entered recovery. So I figured maybe the tool flashed the wrong version, so I googled stock recovery for OnePlus 5, I found a few random links for stock recoveries for the OP5 and flashed them, but they more or less do the same thing or not boot at all.
I've tried changing the filesystem for both Data and System using any combinations of EXT4 and F2FS. Everything results in boot animation bootloops.
I have been flashing Roms since the Samsung Galaxy S3 and every phone since and never had any problems.
Currently when trying to install the stock Full OOS official zip with TWRP, the phone won't even go to the boot animation, it only goes to a black screen with the top LED in a light blue color.
I have also tried every version of TWRP there is for the OnePlus 5. Unofficial, Official, 3.1.1-0 and 3.1.1-1.
So I guess my question is....What filesystem is each partition supposed to be on and for which OS?
Lineage based:
System: ?
Data: ?
OOS Based:
System: ?
Data: ?
And any ideas on getting my phone running again?
And anyone have an official confirmed working version of the stock recovery? The one from ALL-IN-ONE TOOL doesn't work for me. It loads the language selection, then the screen goes black with a light blue LED on the top of the phone.
Actually I'm getting that on some roms instead of the bootanimation, like FreedomOOS. What does it mean when you have a black screen and a white LED?
Man, I really thought I was getting somewhere. If I boot into TWRP, change the Data partition to "F2FS", then flash the stock recovery, the stock recovery will boot, however, when inside the stock recovery and I try to flash the stock zip, it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
Ok, I have the official stock recovery from the OnePlus site, but still can't use it. Here is was happens depending on how I left it with TWRP:
System: F2FS
DATA: F2FS
- Stock recovery will load after some time, freeze, then the screen goes black with white LED on top.
System: EXT4
DATA: F2FS
- Stock recovery loads fine, I can go through the settings and install from SD card, but when I do it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
System: EXT4
DATA: F2FS
- If I try to flash stock rom through TWRP, it just boot loops on the animation forever.
I have now also tried flashing the stock boot.img, but no difference.
I have 2 things you can try!
First, replace the bootloader with stock and do a factory reset:
1. flash the stock recovery over
2. then in fastboot mode enter, fastboot oem lock (This forces the phone to wipe cache and data, and also do a complete reset)
Did it work? if yes YAY if not go to Second!
Second if your system.img is ****ed up you have to replace it!
Download the newest version of the stock rom from oneplus link here
Unpack it
research how to use an extractor to convert the system.new.dat to system.img
once thats completed enter fastboot mode and flash the new system.img over with Fastboot flash system system.img
now go into recovery and do a factory reset and wipe cache, and dalvik
Please reply back wether or not this work
"Ihave 2 things you can try! First, replace the bootloader with stock and do a factory reset..."
Is the bootloader simply the boot.img?
After doing the first thing, it simply says that the device is corrupt and will not boot. But it is locked again.
But I will have to unlock it again to do any further flashing.
Hmm, I think I may have gotten it. After unlocking again, flashing the stock recovery and boot.img, then locking again and wiping in the stock recovery, I have finally booted into the stock rom.
I still have no idea what went wrong, and I really want to know, so that in the future I can flash other Roms, like LineageOS.
I mean, I followed the steps exactly.
If it says the device is corrupt it simply means you got something else besides stock rom.
So now unlock it and try the system.img instead
It was because I still had TWRP with the stock rom.
I got it working though, thanks for your help.
Do you have any idea on what might have went wrong when trying to flash the lineageOS based roms and why it got messed up so royally?
Great to hear you fixed it ^_^
Probably some minor bug, if you wanna try installing lineageos again use the 3.1.1 TWRP build that supports backups and do a full backup so you don't have to go thru all this again
---------- Post added at 12:17 AM ---------- Previous post was at 12:13 AM ----------
Not really just try again but remember to use TWRP 3.1.1, as 3.1.0 don't support backup and probably have been part of your problem
If your trying again and gets it successfully installed could you do me a favor and test if Drivedroid works on it? And pm me the result, I'm looking for a rom where Drivedroid will work... Haven't found one so far
You know, I did do a backup with the OFFICIAL TWRP, but it also resulted in a bootloop. I made the backup after decrypting, so I don't know why it bootlopped.
https://forum.xda-developers.com/oneplus-5/development/rom-unified-lineageos-7-1-2-t3635483
Is this the one you tried installing?
I tried like every ROM at one point yesterday, but I think I started with
https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578
Did you remember Gapps?
Also in some cases its better not to root before you have the custom rom running, you usually only need a custom bootloader like TWRP
Yeah, I tried with Gapps, and I never rooted before first trying to boot.
As of yesterday Ressurrection remix, released the first official stable build so try again your should'nt have any problems if you follow the guide 100%
Ever find a solution? I'm stuck here now. Can't get any ROM to boot up, they all get stuck on the boot animation
Bump. I am also stuck in this state
I tried to factory reset a custom ROM, got sent to TWRP then I can't reboot to system from there. Tried a clean install but to no avail. I've looked around on the internet and I think I have to reinstall stock ROM and then reinstall custom recovery and ROM, except if I were to install the stock ROM once again (with sp tools) I need my phone to be turned off, not in recovery mode. So how exactly should I proceed now?
EDIT: Managed to get rid of the TWRP bootloop by restoring from a stock nandroid I've found on the forums, coupled with flashing a stock recovery image using TWRP. Reunlocked bootloader, flashed TWRP all over again and then flashed custom ROM and Gapps. Everything running fine now.
Mods feel free to delete this post since it's solved itself, or leave it in case anyone needed help concerning the same issue, up to you.
Hi
Bibi if you’re still active on xda reply to this
Help me i got same issue with you. Can provide me with ur stock rom and stock recovery? And how to do. Thanks very much.
Bibicp said:
I tried to factory reset a custom ROM, got sent to TWRP then I can't reboot to system from there. Tried a clean install but to no avail. I've looked around on the internet and I think I have to reinstall stock ROM and then reinstall custom recovery and ROM, except if I were to install the stock ROM once again (with sp tools) I need my phone to be turned off, not in recovery mode. So how exactly should I proceed now?
EDIT: Managed to get rid of the TWRP bootloop by restoring from a stock nandroid I've found on the forums, coupled with flashing a stock recovery image using TWRP. Reunlocked bootloader, flashed TWRP all over again and then flashed custom ROM and Gapps. Everything running fine now.
Mods feel free to delete this post since it's solved itself, or leave it in case anyone needed help concerning the same issue, up to you.
Click to expand...
Click to collapse
Bibicp said:
I tried to factory reset a custom ROM, got sent to TWRP then I can't reboot to system from there. Tried a clean install but to no avail. I've looked around on the internet and I think I have to reinstall stock ROM and then reinstall custom recovery and ROM, except if I were to install the stock ROM once again (with sp tools) I need my phone to be turned off, not in recovery mode. So how exactly should I proceed now?
EDIT: Managed to get rid of the TWRP bootloop by restoring from a stock nandroid I've found on the forums, coupled with flashing a stock recovery image using TWRP. Reunlocked bootloader, flashed TWRP all over again and then flashed custom ROM and Gapps. Everything running fine now.
Mods feel free to delete this post since it's solved itself, or leave it in case anyone needed help concerning the same issue, up to you.
Click to expand...
Click to collapse
can you put a link where you find the stock recovery, cos i've restore stock recovery on twrp but my device keep booting to twrp