[Q] Stuck on boot screen, no recovery, and now just stock 4.4.2 - Verizon Samsung Galaxy Note II

I have a massive issue...
Somehow I lost my TWRP recovery and when I tried to reflash it, I got the "software unauthorized by Verizon error" each time I started my phone.
I thought, no biggy, I'll just reflash back to VRALJB and all will be well with the world. Did it. No problem.
I then tried to unlock the bootloader. This is when all hell broke loose. I had to reflash VRALJB again and since then, I started getting stuck on the "Samsung Galaxy Note 2" screen (the first one, immediately after the phone turns on). I could not enter recovery using the (Volume UP + PWR + HOME) key combo. I could only enter download mode and use odin.
I tried everything. The only thing that worked was downloading the stock 4.4.2 Verizon image released a few days ago from sammobile.com
(I605VRUFND7_I605VZWFND7_VZW).
Now, I do not have root and my bootloader is locked, but at least I have a working phone and KitKat.
Hopefully the above helps someone, but, my question is, where do I go from here?
How do I go about installing a custom recovery and getting root? I would like to keep stock 4.4.2 as well and before anyone asks why, I want custom recovery for the sole purpose of managing my TWRP backups. Stock OS though.

Since you updated to 4.4.2, there isn't much you can do. No root, no recovery, no safestrap...yet. The only thing you can do is wait for developers to find a way to root this version of android.

Hi my friend, I have met the same problem, so could you tell me how to get that I605VZWFND7_VZW rom~
Please~~

Related

[Q] Can't access recovery

Okay. So. After some trouble with houstonn's latest rom's lately (getting stuck on boot), I decided I'd give one more try for the 4/30 release. Clean wipe, flashed it, flashed minimal apps. Stuck on boot. WOOP WHO CARES?
This time was different - I couldn't access recovery. So I tried like 30 more times to access recovery. Couldn't do it. LGNPST back to the ICS stock bin (11c). Get my OTA update to 4.1.2, rooted with this method http://forum.xda-developers.com/showthread.php?t=2006946. After that, I tried to access recovery mode again. Couldn't do it. So, I was like "what the hell, maybe FreeGee will help." So I continued on to unlock the bootloader with FreeGee and with CWM. Installed quickboot and chose to restart to recovery. SAME THING. Black Screen after LG logo. Can't get into recovery.
Now I'm LGNPSTing back to stock to repeat process. Any ideas on what's going on?
Edit: Running into quite a few problems with LGNPST. Gets stuck at 85% and won't boot even after power cycle.
Edit 2: TeenyBin AltBin let me format my partitions and then the LGNPST worked. Got the OTA. Rooted again, used FreeGee, except this time with TWRP 2.5.0.0. Wouldn't reboot afterwards, so moved on to TeenyBin AltBin again. The phone booted up and everything runs fine. One thing to note: I had some wifi problems when I just TeenyBinAltBin'd and used a restore point for stock 4.1.2 which is why I was so adamant to LGNPST like normal. Still can't flash any of the newer ROMs of houstonn's, but I can others. On the good side, I still have a phone. Hopefully if anyone else has the issue, they can follow this and resolve it.

[Q] Bricked?

Hey guys,
I am really hoping someone can please help me out with this, as I am travelling and relying on my transformer to get me around. This is what I’ve done: basically I didn’t like the stock software, so I updated from ICS to JB, downloaded the unlock tool, unlocked the bootloader and rooted my tablet and installed TWRP recovery
From there I installed some version of Paranoid Android which kept freezing up and being jittery, so I figured I’d play it safe with a stable cm10 build, tried to flash it with TWRP and it just got stuck on the ASUS splashscreen, which I later realised was due to TWRP not being at the latest version (did I mention I am clearly a total rookie).
So I flashed paranoid back, and tried to update TWRP which I couldn’t get my head around (GooManager wouldn’t allow me to update it) so I decided to try ClockworkMod Recovery, which I downloaded this .zip and just flashed it over the top, which I thought you could do… Now my tablet won’t boot past the Asus splashscreen, nor will it boot into recovery. I could access the bootloader screen before but now I can’t.
The only thing I can think to do that worked for someone somewhere on the internet was to just let the battery run dead and then try holding down the Vol Down + Power.
Can anyone recommend anything? Or at least tell me what I’ve done?
thanks all
Twinning92 said:
Hey guys,
I am really hoping someone can please help me out with this, as I am travelling and relying on my transformer to get me around. This is what I’ve done: basically I didn’t like the stock software, so I updated from ICS to JB, downloaded the unlock tool, unlocked the bootloader and rooted my tablet and installed TWRP recovery
From there I installed some version of Paranoid Android which kept freezing up and being jittery, so I figured I’d play it safe with a stable cm10 build, tried to flash it with TWRP and it just got stuck on the ASUS splashscreen, which I later realised was due to TWRP not being at the latest version (did I mention I am clearly a total rookie).
So I flashed paranoid back, and tried to update TWRP which I couldn’t get my head around (GooManager wouldn’t allow me to update it) so I decided to try ClockworkMod Recovery, which I downloaded this .zip and just flashed it over the top, which I thought you could do… Now my tablet won’t boot past the Asus splashscreen, nor will it boot into recovery. I could access the bootloader screen before but now I can’t.
The only thing I can think to do that worked for someone somewhere on the internet was to just let the battery run dead and then try holding down the Vol Down + Power.
Can anyone recommend anything? Or at least tell me what I’ve done?
thanks all
Click to expand...
Click to collapse
CWM is not compatible with Jellybean. Unfortunately you are hard bricked.
Why didn't you make a backup with NvFlash? If you did that you could restore your tablet.

[q] help!! Note down

So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:

Need help please, rooted, soft bricked, and now.. no idea what this state is called.

So the first thing was I rooted a Samsung S4 SGH-M919.
I used Chainfire's files and Odin. it worked just fine.
Gave the phone to my wife but the firmware 4.4.2 was clearly outdated that none of the apps she played worked, everything just froze on her or crashed.
So I decided to install a custom rom, this led me to Imperium Lollipop 5.0.1
Well that in turn made the phone unbootable. It would continuously go into these 4 circular swirling balls and get stuck there. I cant even get into Recovery Mode. Only Download Mode.
So this made me do some searching and I dl'ed SGH-M919 stock firmware 4.2.2
I used Odin to flash that and it failed.
So now the phone boots into a screen that telling me to uses Kies to fix the issue.
I'm at a loss what to do next.
Can someone give me the necessary steps to fix the phone and where I intended to go with this?
Much appreciated. thanks.
catheapp said:
So the first thing was I rooted a Samsung S4 SGH-M919.
I used Chainfire's files and Odin. it worked just fine.
Gave the phone to my wife but the firmware 4.4.2 was clearly outdated that none of the apps she played worked, everything just froze on her or crashed.
So I decided to install a custom rom, this led me to Imperium Lollipop 5.0.1
Well that in turn made the phone unbootable. It would continuously go into these 4 circular swirling balls and get stuck there. I cant even get into Recovery Mode. Only Download Mode.
So this made me do some searching and I dl'ed SGH-M919 stock firmware 4.2.2
I used Odin to flash that and it failed.
So now the phone boots into a screen that telling me to uses Kies to fix the issue.
I'm at a loss what to do next.
Can someone give me the necessary steps to fix the phone and where I intended to go with this?
Much appreciated. thanks.
Click to expand...
Click to collapse
Are you sure that you have the right bootloader installed for the lollipop rom? Did you factory reset before installing custom rom? Try to wipe davlik after installation completes before restarting device. Also follow the instructions given by the rom thread op.

My Galaxy S6 stuck in boot loop after root

Hello, so I have a Galaxy S6 on Android 6.0.1 and I'm with T-mobile. I tried to root the phone using Odin first, downloaded a root checker and got the confirmation. And then I tried to get Xposed using TWRP but I had to back up my phone and all that first. After being prompted to reboot I chose an Xposed zip and since then I haven't been able to get past the Samsung logo during reboot. I've tried all the button combinations and I can get as far as the Warning screen about downloading custom OS asking to press volume up to continue or down to cancel and restart. Both of them take me to the Samsung logo where I get stuck with it flickering at me. At this point I'm panicking and waiting for the battery to drain on the blue Warning screen. Right now I have it plugged into the computer on the battery charging screen. I'm scared to turn it on and see I'm still stuck in the loop. Please help me, I cannot afford another smart phone and I had to buy this one unlocked full price. Thanks.
Edit: After turning on my phone and seeing the boot loop was still very real, I went into download mode and tried to factory reset the phone. This actually took me to the Team Win Recover Project 3.0.2-1 where is has the standard buttons for install, backup, restore, reboot, etc. At this point I am not sure what to do, I believe this is where I would want to install the Xposed zip but I am not going to proceed until I have a clear understanding on what it is I need to do.
Edit 2: I should also mention that on the TWRP recovery screen, the restore tab is EMPTY. I guess I either did not completely save a nandroid state, or didn't name it something I could find. I'm unsure on how to restore the phone to factory settings, if at all possible, with TWRP.
Edit 3: After doing some research, I've decided that my best bet is probably to download the necessary firmware for my phone, Model number SM-G920F, and use Odin once again or Smart Switch to hopefully revert back to factory settings. The problem I am now having is finding the right firmware. I'm on SamMobile but I cannot find a firmware that fits my country and carrier. I know that unstalling the wrong firmware can brick my phone so I am being very hesitant here. Can anyone help me?
I'm a bit confused...did you already install a version of Xposed that caused the bootloop or it just started bootlooping after the first reboot after it booted from the rooting process?
es0tericcha0s said:
I'm a bit confused...did you already install a version of Xposed that caused the bootloop or it just started bootlooping after the first reboot after it booted from the rooting process?
Click to expand...
Click to collapse
I only installed Xposed once, and that is when the boot loop started. I had to reboot my device two times; once for Odin, and once for TWRP to get Xposed. Like I said, I went with Odin first for the rooting process and then I used TWRP in an attempt to get the third party firmware. After rebooting for Odin I ran the root checker and everything was confirmed. If it isn't obvious by now, I'm new to this whole process and goofed somewhere along the line so there's my disclaimer. At this point I'm willing to do anything to get this phone working again. I appreciate any help.
Just run the Xposed uninstaller in TWRP.
I have seen this with my wife's galaxy s6 edge, she had dropped the phone after having it for three weeks and then the phone started to act funny. Luckily for me I did not root the phone yet so I did the button combination but instead of volume down I did volume up so I can do a complete factory reset. That had seemed to help, you can always go back to the Samsung site to get the rom you need for your phone and if its with T-Mobile which I also have, you should have no problem getting it.
espinozaea said:
I have seen this with my wife's galaxy s6 edge, she had dropped the phone after having it for three weeks and then the phone started to act funny. Luckily for me I did not root the phone yet so I did the button combination but instead of volume down I did volume up so I can do a complete factory reset. That had seemed to help, you can always go back to the Samsung site to get the rom you need for your phone and if its with T-Mobile which I also have, you should have no problem getting it.
Click to expand...
Click to collapse
I have tried the button combination that is supposed to lead to the factory reset, but this is what is taking me to the TWRP screen. What I haven't tried is finding the ROM from the site so I will try that now, thanks!
Wolf Town said:
I have tried the button combination that is supposed to lead to the factory reset, but this is what is taking me to the TWRP screen. What I haven't tried is finding the ROM from the site so I will try that now, thanks!
Click to expand...
Click to collapse
You don't need to flash the whole rom. Just run the Xposed uninstaller. It was specifically made to resolve these types of issues.
es0tericcha0s said:
You don't need to flash the whole rom. Just run the Xposed uninstaller. It was specifically made to resolve these types of issues.
Click to expand...
Click to collapse
In the TWRP screen I'm not seeing anything about unistalling Xposed, do you know what tab it would be under?
You have to grab the zip from the Xposed thread. You should be able to connect your phone in recovery to the PC and drag and drop it. If not, you might need to use ADB.
Don't flash a firmware unless you are 100% sure it's the official firmware for your device. Maybe you could contact the company's website and ask for the firmware. Sometimes this works. If it doesn't search for one but be sure to flash the official one or it may cause problems.

Categories

Resources