Unfortunately I have been blessed with the luck of having the wonderful Cyanogenmod 13 recovery menu which - lets be honest needs some serious beefing up! wish I had stuck with teamwin recovery!!!
I sadly flashed the wrong version of openGapps then tried to flash the correct version after I got the horrible Red frame. the version of gapps "micro" switched strict mode on automatically as I did not enable this setting. Anyway managed to get rid of red frame blinking on and off by editing the build prop file and adding these 2 lines to the end of the file: persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
rebooted phone, everything great again! as per usual I get carried away and want to reinstall all the apps that I had on before as well as including SuperSu!
This is where my trouble started! Supposedly one doesnt need SuperSU in Cyanogenmod as it has its own SU binaries, now I am stuck in perpetual boot loop with blue head flashing away. have tried now for 8 hours to try and get my phone to boot to OS. I can get to recovery and I was able to push files to it via adb for a bit but could never see the files so as to update from them. I think that this might be a potential flaw with cyanogenmod recovery. Is this perhaps the problem with cyanogenmod having systemless root?? how can I fix my phone now as the pc sees it via minimal adb but it says unauthorised next to it!?? I did factory reset from both the bootloader menu and the cyanogenmod recovery, nothing! I did a cache wipe and again no difference. I dont even know which cache that is as cyanogenmod recovery is lacking in details. not the same options as in twrp or cwm, why not?!!! I'm pretty stuffed now as this is my work phone! what to do anyone know what I have done? have I basically soft bricked my phone and how to get OS back on and boot my phone again??? very sad and frustrated and tired
I luckily found a solution, while not ideal as had to start from clean install again, I now have a working phone again so I am over the moon! here is the solution which I had no idea would work but it did, thankfully:
https://youtu.be/Oo2cErfUSSE
Related
I have a p5113 and it is running 4.2.2 it is a friends. It turns on all the way to the homescreen for about 30 seconds. Then it reboots. I have gotten into recovery and it lets me wipe data factory reset. Then when I go to reboot it shows an error below the android and there has been no data wipe when it reboots. and reboots and reboots.........It also says NO COMMAND when booting recovery below the android. OH, I also tried flashing another stock recovery. Did not fix issue with recovery.
I have gotten into download mode and tried to cf root. Doesnt work, no recovery. Still same as above just goes to stock with no command written at bottom then error when you go to reboot it. Tried both versions of CWM and TWRP Odin files. DONT WORK. Tried to flash recovery by zip and get signature verification failure.
I figured oh, I will do what I always do to tablets try and reinstall the firmware. Which is the 4.2.2 firmware I go ahead and odin it, everything looks fine, it did take way too long like an hour and half. Passes, reboots, same operating system same data didnt change a thing! Still rebooting still recovery errors. Tried to downgrade to ICS and it passed after an hour and a half of slow odining NOTHING again same story as JB didnt change anything.
I have noticed that there is an avg in apps. I never get enough time to uninstall it. It always reboots before I can get to it. ANY HELP IS APPRECIATED.
jhr5474 said:
I have a p5113 and it is running 4.2.2 it is a friends. It turns on all the way to the homescreen for about 30 seconds. Then it reboots. I have gotten into recovery and it lets me wipe data factory reset. Then when I go to reboot it shows an error below the android and there has been no data wipe when it reboots. and reboots and reboots.........It also says NO COMMAND when booting recovery below the android. OH, I also tried flashing another stock recovery. Did not fix issue with recovery.
I have gotten into download mode and tried to cf root. Doesnt work, no recovery. Still same as above just goes to stock with no command written at bottom then error when you go to reboot it. Tried both versions of CWM and TWRP Odin files. DONT WORK. Tried to flash recovery by zip and get signature verification failure.
I figured oh, I will do what I always do to tablets try and reinstall the firmware. Which is the 4.2.2 firmware I go ahead and odin it, everything looks fine, it did take way too long like an hour and half. Passes, reboots, same operating system same data didnt change a thing! Still rebooting still recovery errors. Tried to downgrade to ICS and it passed after an hour and a half of slow odining NOTHING again same story as JB didnt change anything.
I have noticed that there is an avg in apps. I never get enough time to uninstall it. It always reboots before I can get to it. ANY HELP IS APPRECIATED.
Click to expand...
Click to collapse
so you wanna say that your tab is in bootloop
if that then please revert to stock rom
also if you are not able to do this then i have to say that your tab is bricked
try triangle away or take it to customer care
yep its
aditya rathee said:
so you wanna say that your tab is in bootloop
if that then please revert to stock rom
also if you are not able to do this then i have to say that your tab is bricked
try triangle away or take it to customer care
Click to expand...
Click to collapse
not a brick and I am on stock if you would have read the OP you would know that. I have had a brick before the definition of a brick is a device that does not turn on. I have flashed many tabs with stock and customs. Thanks for the great advice but I am a member of XDA and I like to do things myself or with the help of others in my community. I REFUSE TO TAKE ANY ANDROID DEVICE TO CUSTOMER CARE THAT STILL TURNS ON>
jhr5474 said:
not a brick and I am on stock if you would have read the OP you would know that. I have had a brick before the definition of a brick is a device that does not turn on. I have flashed many tabs with stock and customs. Thanks for the great advice but I am a member of XDA and I like to do things myself or with the help of others in my community. I REFUSE TO TAKE ANY ANDROID DEVICE TO CUSTOMER CARE THAT STILL TURNS ON>
Click to expand...
Click to collapse
i like your confidence brother but i was just helping you
also with your threads title in thought you were still having bootloop
also boot loop mainly happens when system files interfere with each other and result in instability during boot and crashes also it is not always necessary that in boot loop device would not turn on as you said earlier
i have seen boot loop on my tab even during charging animation as it was off it was due to use of flashing scripts that conflicted with each other
Hi all
I’m a complete noob at this and it seems like I have got myself into a bit of a pickle. Sorry for the massive description but I thought it would make it easier to get a good answer.
My Phone:
Samsung Galaxy S4 GT 19505 LTE
PDA I9505XXUEMK8
CSC I9505BTUEMK5
MODEM I9505XXUEMK8
I successfully rooted my phone using Odin. In Odin I added the "CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5" file to the PDA field then rebooted the device. Then I added the "openrecovery-twrp-2.6.3.1-jfltexx" file to the PDA field, rebooted the device and the phone automatically opened in TWRP recovery. In recovery mode I wiped the cache, system and dalvik cache. I then went to install, browsed to the "I9505 Official_Google_Edition_4.3_by_Jamal2367_Finaly_v2.0" file on my SD card, rebooted the device and the Google logo came up on the screen for a few minutes and all was good. Got my new ROM, ran a root checker and all was good.
After some research I decided I wanted to use the Pacman ROM as it seemed to a lot more customisable. Using the same method I went to TWRP recovery wiped the cache, system, and dalvik cache. I then went to Install, browsed for the pacman ROM and the Gapps file on my SD card and everything installed ok, the phone restarted and the pacman logo came up everything was fine. Although I did notice on start up that I got this message.(and have had this error message ever since)
kernel is not seandriod enforcing
set warranty bit : kernel
After using the Pacman ROM for a day I noticed a lot of bugs like my apps would disappear, I couldn't use my banking apps and my phone was generally performing very badly. So I decided to remove the ROM and use CyanogenMod ROM under the recommendation of a friend. So again I pressed home+power+vol up to enter recovery mode but this time it didn’t enter the TWRP recovery it entered the stock recovery mode. This was slightly concerning but I proceeded to use the list menu and cleared the cache etc, browsed the SD card and went to the CyanogenMod 10.2 ROM I previously downloaded. It began to install but in red I got the error message stating that I didn’t have the right permission or signature. The phone rebooted back to the Pacman ROM. I tried the above three times and it still continued to boot back into Pacman ROM sometimes I struggled to even get back into recovery mode.
Soooooo I decided to try and go back to the Google Edition 4.3 ROM and play it safe, using the method from my first paragraph. But when it installed through TWRP I got an error message saying cant find MD5 file. The device rebooted and the Google edition logo came up on the screen but it seems to be locked in a loop. The Google logo wont go away and the phone vibrates once then three times quickly every 10 seconds.
I can still enter both TWRP recover and Download Mode. But I don’t want to mess around with it anymore without getting some advice. Any help would be much appreciated as I really need my phone working.
Thanks again
Aiden
Did you create a backup while on your first run with google edition? If so wipe cache, system, and dalvik and restore to your backup. Should put you back to where you began.
Sent from my LGMS769 using XDA Premium 4 mobile app
I know I should, but I didnt. Is it still fixable ?
*Update*
Couldnt help myself had to have a tinker around. Managed to get Cyanogenmod 10 working with Gapps. Gonna see how I get on with this. Although still would like to know I have been having all these problems.
Sometimes things just dont go as planned: p I have easily soft bricked my phone around 10 times and always able to fix it. You really should have made a stock backup before flashing anything. I recommend doing it now so you at least have a known working configuation backed up for future use. Trust me backups are your friends!
Sent from my LGMS769 using XDA Premium 4 mobile app
Thanks for your replies.
Ye gonna that right now Cyan Mod so far is running very smooth without any problems.
Regards
Aiden
Alright, so yesterday I tried to root my tablet (Samsung Galaxy Tab 3 10.1 Wifi) yesterday by installing TWRP and then loading the Superuser zip found in their link in the play store. It worked fine--I had root access and all was going fairly well. I then tried to make a small tweak to the build.prop file by changing ro.build.version.codename from REL to L.
When I rebooted to apply that change, I could not start up, so I did a factory reset (not a big deal, no essential files on there). It then booted fine, but when I reinstalled/updated all my apps, the Google services were crashing like mad. So I reverted the build.prop file back to REL and again it would reboot, so I did another factory reset and all was good; the Google apps were fine.
Well I was still rooted and I wanted to take advantage of all that time I spent doing it, so I downloaded the bootanimation zip found on this thread and replaced my bootanimation.zip that was already on there. I restarted to see the animation, and this is when the real nightmare started happening. I could not boot now at all.
I did another factory reset, and still it wouldn't boot. I then used TWRP to do a full reset, and still nothing. I did an advanced reset and somehow managed to delete the operating system files (I have no idea how), causing TWRP to say that no operating system was installed. I still couldn't boot, of course.
Finally, I decided I had had enough of this rooting ****. I searched all over the internet looking for a North American version of my stock ROM, and finally found one posted on this forum post. I wouldn't normally trust any random file, but I was getting desperate here. I used Odin to flash that ROM, and there were no errors. Now when I go into recovery, it gives me stock and not TWRP, so I know that was probably successful.
However, I still cannot boot. I get stuck on the screen that says Samsung Galaxy Tab 3, which sometimes goes away and then comes back. I can't send it in for warranty, because it still says "custom" in the recovery mode. How can I fix this? any ideas?
I really want my tablet back :crying:
Hi All.
So I'm not new to rooting / ROMs (nor am I an expert, as you'll see), but somehow have totally screwed up my tab. I've now honestly done so many things to try to recover, that I couldn't begin to summarize how I got into this mess, but I'll try.
Model is GT-P5113. Most recent working ROM was SlimLP 5.1
I went to flash CM12.1 (using CWM) and God only knows what happened. After it flashed, I tried to reboot and it would only go to CWM recovery. If I chose to reboot device, it would only shutdown, not reboot (This was actually one of the issues I was having with SlimLP as well, so I don't think the flashing had anything to do with that???)
After many attempts at reinstalling CM and SlimLP (I used the same Zip that had worked previously with SlimLP, and the flashing would say installed) it would still only boot to recovery. I finally said, screw it, I'll just start completely over
So attempted to go back to stock 4.2.2 using Odin3.09. Got the stock ROM off SamMobile site. ODIN seemed to flash,but again when it would go to reboot, it would just power down and a charging battery would show up. So I would unplug from the computer, push power button. When it powered up, it would say Installing system update, then after the status bar moved a bit, it would say Error and shut down. When I restart, it very briefly says installing system update, then show the dead android with a red triangle and No Command, and it would boot to the stock android system recovery (I assume CWM was taken off in the process). In yellow, under the stock recovery it says
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
I've tried installing the other ROMs again, this time with TWRP, but only for it to boot to recovery after the Samsung Tab 10. 1 logo.
I have no clue where to go from here. No clue if I'm still rooted (doubt it). At this point I don't care. I just want a functioning tab. I've spent hours searching, but nothing works. I'm open to any / all ideas.
Thanks
Aw, show me a little love, bros. Someone' gotta know something. I'm not above begging / pleading.
I can give more info, less info, post somewere else. Just let me know,and help me resuscitate my tab.
thanks again!
Hello, I need serious help with my phone.
So, after a long while of having my phone rooted, and had a case of boot loop with twrp, I decided to go back to stock os and hung up the root days. I thought i did it right by getting a stock os and flashed it, and it worked for couple months, until yesterday.
My phone keeps going into Cyanogen Recovery, I tried rebooting so many times, once it did boot up to OS, but it went back after i restarted phone or it died.
Now I can't no longer get back, I thought factory resetting will work but it didn't. (Tried both wipe cache partition and Full factory reset option from the recovery) I found unroot your phone toolkits, thinking it could help fix my problem and just unroot/ give me back to OS (I wished i found this before flashing that custom stock rom).
But the toolkit doesn't work for me, it finds adb devices, but it cant find fast boot devices, because my phone cant even go into fast boot.
I tried manual, and the option from the recovery, it keeps going back to recovery. I have an option for apply update, and then apply from ADB, that was the only way for my pc to recognize my phone from adb devices. Any clues on how to fix?
Hi !
I may suggest you this thread https://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Good luck !
xanthrax said:
Hi !
I may suggest you this thread https://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Good luck !
Click to expand...
Click to collapse
Will try, Ill respond back if anything happens!
Hmm I'm still having trouble because, I can't get into fast boot for some reason. It's keep going back to Cyanogen recovery. It has the option to reload into bootloader, but goes into cyanogen recovery again.
There is an option in dev options, uncheck the "update cyanogen recovery" and flash twrp again
Sent from my SHIELD Tablet using Tapatalk