Today I received my GT-N7105 back from the repairers after having the screen replaced, or maybe the whole phone replaced as for some reason my phone was un-rooted! God knows why they would have to do that to replace the screen.
So I've just rooted again and installed ROM Manager and attempted to flash CWM recovery, according to the app it went fine, but when trying to boot to recovery using the ROM Manager app and the volume up + home + power method I'm met with the stock recovery.
I have tried using Odin to install CWM recovery but the device freezes on the boot screen every time I try, and freezes there when I take the battery out and attempt to boot the phone again. So I have to root again just to get the device to turn on.
Its been years since I flashed a custom recovery so tried following a couple guides, but no luck.
I want to flash CyanogenMod to the device but cant do this without CWM (I've never attempted to use TWRP, better the devil you know!)
I have noticed Knox has appeared on my device, but I have not activated it as I hear this causes issues with rooting, and the reason I think this is a different device altogether is the flash counter was at 0 when first rooted this one, but I must have pushed this p to at least 15 before it went in for the repair.
Am I missing something? Please don't make me have to use the bloated to the heavens stock Android!
Thanks in advance and will be thanking any help.
Related
I am not new to the concept of rooting and loading a custom rom. This is the 3rd android phone that I have bothered with. However it is the first one I have had to use Odin to root or push files to.
I have used CarpeNoctem's writeup on how to root and utkanos' CWMR port writeup. Ofter verifying I had root, I decided I would try out Carpe's OsiMood. No problem right? Here is where I am wondering what if anything went wrong on the previous steps.
I made a back up ofter finally getting it to recovery mode, and when I tried flashing the new rom, it would not complete the process.
As it sits, when I choose recovery from CWM it reboots to the android with triangle screen(see attached video). What concerns me is the lack of fluidity into the recovery, the fact that it loads in only after the battery is removed and the phone is turned back on and lastly that I cannot flash a new rom.
It appears as though I need more posts to add my link for youtube.
Please add standard youtube weblink before this to watch the video.
/watch?v=qpQyQB1aozs
What would you recommend my first action be?
Thanks,
Steve
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Thanks for your insight. I tried volume down and power before but when I saw the samsung logo pop up I figured it wouldn't work.
I will try flashing again and report back. Thanks again.
-Steve
Tried flashing again, worked great. If only the glide had more support. Lol.
Currently running OsiMood.
Sent from my SAMSUNG-SGH-I927R using Tapatalk
gabby131 said:
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Click to expand...
Click to collapse
My glide does not boot. I can get into Download Mode. I can NOT get into de recovery mode. I think my NAND is corrupted.
How can I mount the /system partition? Because I flashed too many roms with ODIN, but nothing, still not booting, I get stuck in the samsung logo.
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Kodiack99 said:
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Click to expand...
Click to collapse
I've already flashed the stock recovery, the CWM, a lot of kernels, even I tried to flash the kernel and bootloader of the Galaxy S II, but nothing.
I'm starting to think that maybe is a hardware problem. Hope not, but I'm not moving foward.
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
I had a boot loop once ,had me stumped and it turned out to be my sd card was poached and caused the loop.
Kodiack99 said:
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
Click to expand...
Click to collapse
Exactly... It goes all over the process bar, says succesfull, the phone turns off, and nothing. The phone not even restart itself, I have to remove the battery, put it back again, and then it turns on, but just to show me the samsung logo.
I've used the ODIN version 1.85 and the new one 3.04. But nothing. This is so frustating.
---------- Post added at 04:23 AM ---------- Previous post was at 04:04 AM ----------
I've opened a thread with all the symptoms of my bricked phone:
http://forum.xda-developers.com/showthread.php?t=2035742
Please, tell me there is a solution...
There are one alternative to boot
1. Shut down and then restart phone in recovery mode. For the Samsung Captivate Glide, this required pressing the power, volume down and home keys all at the same time.
2. The initial screen which appears gives you a choice of loading a replacement OS (volume up) or entering recovery mode (volume down). Note you have to hold the volume down key for several seconds before the recovery mode menu appears.
Hi all,
I'm new to android. I did root my note 2 using the instruction by dr.ketan. I used method#1, flashing with changelu's cwm6-root-note2.tar, everything was successful. However, I can not boot into cwm recovery. I tried press and hold vol up+home+power when the text samsung galaxy note ii appeared let go the power, but nothing happen. My device would reboot again. I tried to use rom manager to reboot to the recovery, the device would show the samsung galaxy note ii and keep rebooting. Any tips on accessing the cwm recovery?
As I could access the download mode just fine, I will tried to reinstall the stock rom again and hope that it will be normal again.
I used stock rom, namely the N7100XXALIE_N7100OLBALI9_THL, and changelu's cwm6-root-note2.tar
One more thing about OTA, from what I understand, if I rooted with stock rom then using TriangleAway to reset the counter.
I will still have System Status: Custom which I read that it could be set to Official by using cwm then clear cache and wipe the device.
With binary counter: no, everything else is official, will I be able to update using OTA?
Thank you,
beau
Have you reset counter?
to boot into recovery it's necessary to press the power button only till the "galaxy note2" screen comes up, then you have to hold the vol button and the center button until the recovery shows up. maybe you'll have to try it one or two times to get the proper timing, after you've done it a few times you're into it!
regarding the reboot issue:
i had this on several devices sometimes, i fixed it always by reflashing kernel and recovery. so don't panic, its no brick for sure! had this today when i swapped my note2 for another one (due to display flaws, same old story as with sgs2 and note1). after rooting the new one i could not shut down the phone, after restoring the nandroid all was fine again!
hope that helped!
Update on my status:
I just finished reflash the stock rom. Everthing seems normal now. I just saw in dr.ketan thread that someone else also had the same issue, can't boot into recovery after using triangleway to reset the counter.
Thanks dr.ketan & TML1504 :good:
But i can't fix my problem.my phone always logo hang on startup.i try to recovery mode but phone not getting to recovery.
I think its another soft brick.i try kerner,cwm recovery & 5 different version of firmware but ODIN just says fail & there is no pit partition.
4 times Pm to dr.ketan but he also Silent.
What to do now?
Hi folks,
I'd appreciate some assistance in identifying the problem with my sm-p605. The color balance (RGB) on it went all bonkers. Red was alright, but the green and blue were almost completely faded. When I booted into download mode the colors were right, so I figured it's gotta be a software problem. I tried re-installing the firmware, first through Kies, but it got disconnected in the process, so I found stock firmware on sammobile and flashed it with Odin with a PASS. After that, the device would get stuck in a boot loop with "recovery booting....." written in the top left corner whether I tried to boot it normally or in recovery mode. But the download mode still worked so I tried flashing a custom recovery. I don't know if a device needs to be priorly rooted for that, but I flashed CF Auto Root and TWRP both with a PASS. After that, the device still wouldn't boot into recovery mode. It would say "recovery is not seandroid enforced". I tried several supposedly compatible versions of the recovery with the same result. But now it does boot normally into the OS except none of the things I flashed stuck. It's still the same non altered system it was before I did anything with it, even though I re-installed stock firmware twice now, second time even with Kies. So what's going on?
I took a screenshot of the app drawer after all this, and the colors are alright when viewed on a computer screen, so it might be a hardware issue after all, although I don't have a definite conclusion since capturing and displaying aren't the same part of the OS. There are other issues with it being non responsive when I'm trying to wake it up. I still want a fresh ROM so I can know for sure and I'm not able to install one, be it custom or stock. Any ideas?
I'll try to be clearer. Current ROM I have is stock 4.4.2, but it's barely usable, so I wan't a fresh one. I cannot get into recovery mode. If I flash stock firmware, I cannot boot into either the OS or recovery. If I flash custom recovery on top of that I still can't boot into it, but I can boot into the OS, which reverts itself like I never flashed fresh stock. So I'm stuck with what seems to be a corrupt OS with no way of installing a new one. Is there something I can try?
If you can flash a custom recovery. Boot into it and try factory reset. Either that or try a custom ROM if any are available (font have tablet)
Sent from my LG-D850 using XDA Free mobile app
Factory reset was the first thing I tried, I wish it had been that simple. I can flash a custom recovery, but I can't boot into it. The only thing it acomplishes is breaking the bootloop from stock recovery, so I can boot back into the OS, which stays the same no matter if I flashed new stock (it boots up already user configured). To install custom ROM I need custom recovery, unless there are some methods of installing that don't require flashing from storage.
I was on stock F240L20D, 4.4.2 Kitkat, rooted, PhilZ Touch 6 installed. I've tried some ROMs before but reverted back to this one. So, basically, I've been to the recovery several times, but only used the ADB method to access it, and I've made several backups too.
However, one thing that happened today has frustrated me completely. Long story short, I thought about making a backup again, although this time, I used the power keys to get to the recovery instead of the ADB method, backup completes successfully, nothing wrong just yet, but just as I tap on 'Reboot System Now', it boots back in to recovery.
I've tried everything, tried using all the ADB commands, even going through all the options in the recovery, but it always seems to boot back in to the recovery. Really can't figure out what's happening. Any help would be extremely appreciated.
UPDATE: So I've flashed a KDZ, the Lollipop one using the LG Flash Tool. It's taking a bit too long to start, currently stuck at the U+ Lte logo. I hope it gets fixed.
UPDATE 2: It says Android is upgrading, YES YES!!!!! This is so exciting, but I'm still not convinced.
With most of cwm version after 6.4.7, any time you use power + volume up to access the recovery, you will get the boot loop. Go here and down load the zip file from the first post. Flash the zip and you should be go to go.
http://forum.xda-developers.com/showthread.php?t=2619403
PROBLEM SOLVED.
So at first I used Kingroot to rood my device, and it failed, but then i just realized few days later that Kingroot was installed and used root checker to check and said that it does have root access. After that decided to change the Kingroot to SuperSU by following this video https://www.youtube.com/watch?v=WevWdErXWy4 (It's the SuperSU Me app). I then updated SuperSU binaries and restarted the phone, and now its stuck at the loading screen. I tried hard resetting my phone but it would only show the screen with the android logo and shapes in its belly for about 2 second and go back to the stuck logo screen. Now I'm wondering if there's any fix for it, and if there's no fix then I'm going to try resetting it through this http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/ guide and I was wondering if I should download and use the bell stock factory firmware (I have a virgin mobile version).
Edit: fixed to be more clear.
I Nid 2P said:
So at first I used Kingroot to rood my device, and it failed, but then i just realized few days later that Kingroot was installed and used root checker to check and said that it does have root access. After that decided to change the Kingroot to SuperSU by following this video https://www.youtube.com/watch?v=WevWdErXWy4 (It's the SuperSU Me app). I then updated SuperSU binaries and restarted the phone, and now its stuck at the loading screen. I tried hard resetting my phone but it would only show the screen with the android logo and shapes in its belly for about 2 second and go back to the stuck logo screen. Now I'm wondering if there's any fix for it, and if there's no fix then I'm going to try resetting it through this http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/ guide and I was wondering if I should download and use the bell stock factory firmware (I have a virgin mobile version).
Edit: fixed to be more clear.
Click to expand...
Click to collapse
if you can get into recovery you can probably do it without unbricking. to you have stock recovery or twrp or what? If you have stock recovery then boot into recovery and just run it and itll hard reset your phone, if you have twrp or something just download the flashable rom of your choice (there are stock modded roms too if you like stock) put it on an sdcard and wipe and install that rom.
if you don't know how to get into recovery then make sure your phone is off (if ur not sure do a battery pull and put it back in). hold volume down and power button until the screen comes on. when it comes on let go of vol down and power and then push vol and power again and hold again until you see the writing)
btw if you do a stock recovery hard wipe then you will lose root.
I also faced this problem...
Sent from my SM-E500H using Tapatalk
Problem solved. I just flashed the stock firmware onto my phone and it fixed the stuck on logo problem.