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.
Related
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
firstrival said:
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
Click to expand...
Click to collapse
Dont try flashing a custom ROM on to the phone. Try flash the stock ROM through the lastest odin with the lastest drivers and let me know how that works out for ya. Unless that wipes the phone ( havent used it in quite some time) then I have no idea man.
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
firstrival said:
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
Click to expand...
Click to collapse
I'm not sure maybe want to ask someone else I'm not as experienced as some people on here. Sorry man goodluck
I hope someone can help you out. I would say your cache partition somehow got renamed but I'm not sure if thats possible and if so how to fix it. Maybe someone with ADB knowledge can help?
Also what TWRP were you trying to install? I've had problems when I tried to flash older versions
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
kireflow90 said:
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
Click to expand...
Click to collapse
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
firstrival said:
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
Click to expand...
Click to collapse
Thanks for the quick reply. Its a shame to hear that it didn't work
How did you come to this? as to me it seems the partions have be modified hence why giving those errors I seen similar errors to when users change cache sizes which tends to brick device or from using incorrect pit files.
You never be able to recover data from flashing Odin may be slim chance by custom Rom thru recovery if was a bkup of original system and not selecting data your old data may conflict causing either bootloop or basically stuck on splash screen.
If you was ever able to best way to pull data from device would be thru adb may have a chance.
This phone belongs to a friend of a friend. They said they brought it to T-Mo because it hung up during boot. The store worked on it for a few minutes, but couldn't get it to boot up either. When I tried to go into recovery, they said the store already went into that screen too. They have since bought a new phone, but would like to get the photos off it if possible. They never had an SD card so it's still on the device.
At the moment, I can just go into download mode. I was hoping to flash a custom recovery so I might possibly be able to ADB from there since it won't load the stock recovery.
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
fulgorevinnie said:
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
Click to expand...
Click to collapse
ok so i read all that you have done which is basically everything i would of suggested to you other then could it be the battery may be faulty just random thought noticed you never mentioned trying kies you may have a chance with it beening detected as i see you can enter download mode so that help with odin also kies also have you tried firmware from here sam mobile here T399 or T399N OH2 lastest for tmo and OH3 for metro.
Try to only flash that thru odin i use 3.07 or 3.09 only difference is the pda button changes to AP .works perfect for me so i suggest it then returning back to stock recovery/firmware if it boots then awesome. then return to TWRP 2.8.4.0 beening lastest for this device also needed for CM12 also my projects for device current and future.
when using odin make sure that only “Auto Reboot” and “F. Reset Time” options are selected.
also just note when going into twrp release buttons as soon as you see logo otherwise it will continue to boot thru well happens to me when daydreaming lol.
also if your seeing this adb get-state returns "unknown" i believe installing kies may install the drivers for detection im not postive on that but im sure it something to do with missing the adb driver for device maybe another dev can confirm this ?
hopefully this may be of some help i keep on thread to see how the outcome goes
Thanks for the reply DJBoxer!
Regarding the battery it's a new one and I can confirm it's not a battery problem considering that the phone can stay in download mode and unplugged from any power source for very long times without turning off/rebooting and it never failed to keep the charge so far. I also tried with the old battery and the phone behaves exactly the same way.
I used 3 different versions of Odin (1.87, 3.07 and 3.09) with only “Auto Reboot” and “F. Reset Time” options selected and every time I got the PASS message even though the phone keeps rebooting after the first reboot once the procedure is terminated.
To clarify one thing : when I said "it shows the TWRP splash screen but it reboots right after and this happened even after I flashed CWM" I meant to point out that it looks odd to see the TWRP splash screen (even for just a few seconds) after I just flashed CWM and that makes me think that I'm really not flashing anything here...
Thank you very much for taking the time of posting the links and I actually didn't try with that latest OH2 version.
I am downloading it right now (it takes a while from sammobile) and I will keep you posted on the outcome.
I will try to flash it via Odin and I'll also try the latest version mentioned on sammobile (Odin3_v3.10.7).
Regarding Kies I wasn't able to have it recognize the phone. I may be missing something but I tried updating drivers and going through all the guided procedures with no luck... If you say it should recognize the phone right away while in download mode then something is amiss.
Could you please confirm that I should also be able to use adb commands with the phone connected via USB in download mode? Cause that doesn't look like the case either...
Thank you again and I'll give updates here about my last attempts.
Sorry for the late reply...
Nothing changed by the way...
I am about to send the phone back to the seller who told me they'll try to fix it. Let's see how it goes.
Hi Everyone,
I unlocked the bootloader a while back, planning to root and install 3rd party roms, but I never ended up doing that.
I only played around with removing "Unlocked Bootloader" message, and that's all. It took a trip to Motorola and came back once, is it possible they removed recovery?
Anyway, is there anyway to revive the device? It boots fine but I am having issues with google play store, it keeps crashing so I wanted to do factory reset, that's when I realized that recovery is missing.
Why did it go to Motorola?
Is the bootloader still unlocked? If it is,
I'm not sure what issue you got, but I would recommend you flashing a twrp recovery of the respective model. Also, Resurrection Remix 5.6.8 or AICP ROM. They are currently the most stable ones for the device.
PseudoDev said:
Why did it go to Motorola?
Is the bootloader still unlocked? If it is,
I'm not sure what issue you got, but I would recommend you flashing a twrp recovery of the respective model. Also, Resurrection Remix 5.6.8 or AICP ROM. They are currently the most stable ones for the device.
Click to expand...
Click to collapse
Hi, it went to motorola because the SIM slot pins were bent, of course it came right back with a little note "sorry, bootloader unlocked, we won't fix it" basically bootloader unlocking also voids all physical/mechanical warranty as well, I understand, I shouldn't have unlocked the bootloader on day 1 and get the sim slot messed up on day two, ended up with $50 paperweight.
Thank you so much for the suggestions, I don't want to mess it up more than it already is.
It's a CDMA+GSM edition, supposedly identical to Verizon model. I think I already have adbfastboot, I should be safe following this video here, unless you have any other suggestions
https://www.youtube.com/watch?v=R4c0fO8Kr_Q
Thanks again.
"No command" it says that on the stock recovery.
So i think i are expecting to see the TWRP screen but it's not showing.
You need to investigate putting TWRP onto your phone.
Then do a factory reset that way (i think that is what you are TRYING to do)
Did you trying booting into safe mode ?
You could try safe mode and see if that helps too.
Hold down Power Button then tap & hold down the button that shows on screen.
It will ask you if you want to reboot in safe mode..
I recently tried installing a custom play store and it worked ok for me.
I found one online that had a color scheme change to Black.
So you may want to investigate using a different version of it
or look into re-installing it clean.
I am suspicious you have some serious problem though.. the Play Store should not be crashing.
My advice is get it fixed up or factory reset etc like new then make sure to do a TWRP backup when it's clean & new.
I had to learn the hardware on that myself.
Plus it's waaaay quicker to restore a TWRP backup than it is to re-install.
Another option you can do and what i would do if i were you is go to the big firmware topic then on the first post get the FileFactory link and then match your phone model properly and then re-install the firmware fresh.
That big topic is full of info on doing this.. and it's the one with the most page hits & replies.
Usually on page 1 or 2.
xpmule said:
"No command" it says that on the stock recovery.
So i think i are expecting to see the TWRP screen but it's not showing.
You need to investigate putting TWRP onto your phone.
Then do a factory reset that way (i think that is what you are TRYING to do)
Did you trying booting into safe mode ?
You could try safe mode and see if that helps too.
Hold down Power Button then tap & hold down the button that shows on screen.
It will ask you if you want to reboot in safe mode..
I recently tried installing a custom play store and it worked ok for me.
I found one online that had a color scheme change to Black.
So you may want to investigate using a different version of it
or look into re-installing it clean.
I am suspicious you have some serious problem though.. the Play Store should not be crashing.
My advice is get it fixed up or factory reset etc like new then make sure to do a TWRP backup when it's clean & new.
I had to learn the hardware on that myself.
Plus it's waaaay quicker to restore a TWRP backup than it is to re-install.
Another option you can do and what i would do if i were you is go to the big firmware topic then on the first post get the FileFactory link and then match your phone model properly and then re-install the firmware fresh.
That big topic is full of info on doing this.. and it's the one with the most page hits & replies.
Usually on page 1 or 2.
Click to expand...
Click to collapse
Thanks, I managed to get TWRP to work on the device using ADB Fastboot, and I got the phone rooted. I removed the old Google Play store manually, restarted, and then installed it from apkmirror, and now everything seems to work just fine, but somehow I think stock recovery image is gone, I don't think I have the factory image anymore.
I checked around but couldn't find it, would you happen to know what is the stock rom for XT1526?
Thanks.
Like i was saying just look it up as per your model number..
And glad you got it working.. that is all that really matters.
Plus that screen that shows the Droid Operation with the words "no command"
that is the stock recovery.. if you installed TWRP you should never see that booting recovery.
See what i mean ?
So check this page.. it's where a lot of us got our Firmware from.
http://www.filefactory.com/folder/752fdb49361c7f62/?sort=filename&order=ASC&show=100&page=2
But research your phone model first and see what people are saying.
Mine has a tab of little plastic cover paper that pulls out that shows my Model number.
Or get it from the bootloader screen then look around using search to see what people are saying.
Some of them have restrictions.. and some are GSM versions which are a bit different.
I am not too familiar with your phone version but i Google'd it and i see Sprint & Boost coming up..
Such as this topic..
http://forum.xda-developers.com/moto-e-2015/general/moto-e-2015-cdma-sprint-xt1526-custom-t3241117
Basically i don't want to say hey go flash firmware then see you have problems
And all i did was go to that Firmware page and search for the model number
by hitting ctrl+F with Firefox then cycle through them.
There is a few of them.. that follow a file name format.
XT1526_SURNIA_ACG_5.1
ACG would be the region part of it or provider such as Boost
So that page has 16 versions of Lollipop for your model number.
What i would do is ask guys on the firmware topic what one they used.
This is where i got the Filefactory link on post one (you can look in the Mega links too)
http://forum.xda-developers.com/moto-e-2015/general/stocks-firmwares-moto-e-t3113235
I would search through that topic and ask on that topic what others used.
Then search around the forum (General section or maybe help section) and then with Google too.
For example, i googled this "XT1526_SURNIA_BOOST_5.1_LPI23.29-18-S.8_cid9_subsidy-DEFAULT_CFC.xml.zip"
And it showed this topic..
http://forum.xda-developers.com/mot...nt-version-t3052844/post64438539#post64438539
Research.. better safe than sorry LOL
Thanks for all the info, sometimes was messed up because phone received an update from Google and when it attempted to update, it got stuck in recovery (would not update). Was there a notice somewhere that we shouldn't update the phone? Anyway, it kept trying to reboot the phone after it turns on but it gets stuck at TWRP and won't update.
I was able to get into the settings and wipe the phone, now I am trying to go through set up again, but I think my best bet is to flash stock firmware and start over. Next time instead of trying wipe, I can just reflash stock firmware over it.
Hey guys, I was running stock ZVC (with stock recovery and bootloader) until just a few minutes ago, when I finally gave in and told the phone to apply the OTA update that was pushed out last week (the "ZVE" one). It started doing its thing, but next time I looked back at the device it was in recovery mode, just sitting there at the menu prompt...
I've since tried rebooting and powering off about half a dozen times, but it just keeps looping back to recovery mode. I also tried wiping the cache and rebooting, with no luck... It still loops back to recovery mode. I don't know what went wrong, but I'm assuming it could be related to one of two things that I didn't think about until afterwards:
1) The phone was rooted via Kingoroot, and root was still active when I tried to apply the update.
2) Just a FEW programs were frozen via TitaniumBackup (as well as Android's own app management system, using the "disable" feature), but these weren't system- or kernel-critical apps. They were things like LG Health, Sprint Money, etc...
Can anyone suggest a fix? Right now it just keeps rebooting into stock recovery and I've never had to deal with an issue like this, so I'm not sure what to do. I was obviously running the stock ROM, so I'm not set up to flash stuff. Although if it can be done with the default recovery, I suppose I could obviously do that... Once again, everything was stock on the phone except for Kingoroot, which was still enabled during the update.
I'm in a pickle here, guys. It's not like I'm any different than everyone who "needs their phone for work," but yeah, I need my phone for work... If I have to wipe data/factory reset, there's probably no way to pull some data off of the phone via PC first, is there? I suppose it's not that big of a deal, but I have some data and some program data that I hadn't gotten around to backing up yet, because I didn't think I'd need to until before I attempted to flash a new ROM or custom recovery.
Any help would be HUGE. Thanks...
EDIT: I took it into the Sprint store today a couple hours after I posted this, and they said I'd have to send it in to LG for warranty service. I don't know if the Sprint tech person knew what she was doing or not (because she had to use Google to figure out how to put the phone into download mode, even though she owns the same model), but she said that she couldn't establish a connection between the PC and the phone...
Now I'm not sure if that's the case, or if she just didn't have the right drivers installed, or if she was even in the right mode (I think she was using some Sprint-made flashing tool, but she did get it into download mode). She also seemed bored and like she just didn't wanna deal with it, so I don't know...
Assuming I can flash back to an earlier build like ZVB (and assuming I can even find it online), is that done from download mode or from recovery? By the way, we also tried just doing a factory reset and that didn't work either; just keeps rebooting to recovery...
Thanks...
EDIT 2: Fixed by flashing to stock via these instructions. Had to select Board DL and use a different key sequence as described here.
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.
It doesn't seems to be working to root an S9+ 256GB DUOS SM-G965F (NEE - BRF8). NEE is Finland but it seems to be used in the whole Nordic.
After doing all the steps everything works but when the phone goes to sleep (the screen turns off and after a minute or two)) it will freeze (someone wrote it was AOD but it doesn't matter if it is running or not).
I also noticed the phone is lagging when using the startup guide, but it disappear after a reboot, but if i leave the phone and letting it fall in to sleep it will freeze and won't wake up again.
The only difference between "SuperSU 2.82-SR5" and "Magisk 16.6" is that with Magisk the phone is lagging at the startup guide and with SuperSU i have no SuperSU icon in apps to run.
And believe me, i have rebooted, but it won't help, no SuperSU icon. When the phone goes to sleep it freezes again.
I install TWRP with ODIN and Wiped the phone and rebooted into recovery, then i did:
1. no-verity-opt-encrypt-6.0-star.zip
2. rebooted into recovery
3. RMM-State_Bypass_Mesa.zip (i have even tryed RMM-State_Bypass_Mesa_v2.zip)
4. SR5-SuperSU-v2.82-SR5-20171001224502.zip (or Magisk 16.6)
5. samsung-antiroot-removal-2.4.zip (i have even tryed samsung-antiroot-removal-4.1.zip)
6. reboot and wait
The phone will always show the "OEM unlock" so i don't need to wait 7 days for it to appear.
Any advice on how i should proceed?
Additional information:
I have now restored the phone back to default (ODIN and the 4 firmware files) and now it won't freeze anymore and "OEM unlock" is still enabled with this text below "Bootloader is already unlocked". Unfortunately the phone isn't rooted now
It seems that if i only flash TWRP i get the same behavior, it freeze after a while after the screen has turn it self off.
Samsung galaxy s9+ 64GB
Hi, first thing I want to say is I registered on this site just now. This is my first reply so please be a bit forgiving if I'm doing something wrong. That said....
I have the exact same problem.
I have the s9+ 64GB SM-G965F.
Here's what I did...
I flashed twrp through Odin which works perfect. On reboot into recovery I formatted data.
Reboot into recovery again and flash no-verity.
Reboot into recovery again and flash RMM.
Without rebooting also flahed superSU and antiroot.
The versions of those files are the exact same as mentioned above and in all the guides....
After all this system reboots and starts up just fine.
All seems okay but when my screen turns off it freezes after a minute or so and the only remedy is a hard reset by holding volume down and power.
It reboots perfectly fine then but the same thing.
When the screen goes of it freezes..
At first I thought it could be the official Samsung firmware so I completely wiped the entire system and flashed resurrection remix rom. All works but when I root this rom the same thing happens. Only this time the root seems to work while flashing but on reboot there's no SuperSU app and it's not rooted according to root checker. Same thing with the freezing though....
So I downloaded the latest official firmware from Samsung, BRF8 I think. Flashed that through odin and all works fine. No freezing. But also no root and no twrp or any custom rom.
So I'm thinking it has to be the rooting that causes it. Tonight I will try to only flash twrp and flash no-verity and RMM, I'll leave the root itself out of it just to see what happens.
I'll post the results back here... If anyone has any ideas it would be appreciated very much!
OH another thing to mention.... I have had oem unlock activated all the time, I checked on each boot and it was always active for me too.....
SHOTOKANKATANA said:
So I'm thinking it has to be the rooting that causes it. Tonight I will try to only flash twrp and flash no-verity and RMM, I'll leave the root itself out of it just to see what happens.
Click to expand...
Click to collapse
If i only flash TWRP i get the same freeze. I used twrp-3.2.1-2-star2lte.
Oh... You beat me to it...
That's no good then, if it's caused by twrp there isn't much we can do I guess. It all starts with twrp.
I'm using the same version as you are.
Maybe we can try a previous version, I don't know what that's going to do though, if it would even be compatible...
I did find a separate official recovery file.
Maybe it's an idea to install the official recovery after acquiring root?
I'm not sure if the file is legit though, I've never done that before. Twrp always worked for me, on all phones I owned.
What's your though on that....?
I wondering if this should be reported to the Github issues log for TWRP? The problem seems to be TWRP.
Maybe we are doing something wrong I'm not sure.
I know I followed multiple guides up to the smallest detail. The result is the same every time. There's 1 thing I noticed though.
I'm using the BRF8 firmware as are you, maybe that's the problem? In the video guides they're mostly on BRE5.
It looks like it's just us with this issue. I can't find any other info on this particular matter...
I've posted this question on another thread.
Here's the link in case you want to follow....
https://forum.xda-developers.com/ga...cross-device-development/twrp-exynos-t3763464
I found the solution. I got it working now...
I installed twrp 3.2.1-1 instead of 3.2.1-2.
Has to be some kind of issue in the latest version...
I used the same install procedure as supposed to.
Only used the other twrp version.
My phone hasn't froze for the last 2 hrs so I'm pretty confident it's working now...
Ahhh cancel that. It just froze again!
Could you see if you can find the tmp/recovery.log?
On the github TWRP ask for it: "/tmp/recovery.log"
and the output of "dmesg" --> "/tmp/recovery.log"
really hoping we could find the fix for this.
The freeze happen because of the real time kernel protection. You need to flash custom kernel before root.
ione2380 said:
The freeze happen because of the real time kernel protection. You need to flash custom kernel before root.
Click to expand...
Click to collapse
LOL, it's right in the twrp instructions, including the phrase"flash custom kernel before root or be screwed"
Thanks you
The problem is solved.
vannsangha said:
Thanks you
The problem is solved.
Click to expand...
Click to collapse
What did you do? I'm still geting freezes with custom rom so i wondering what i'm doing from?
jagflashardinxbox360 said:
It doesn't seems to be working to root an S9+ 256GB DUOS SM-G965F (NEE - BRF8). NEE is Finland but it seems to be used in the whole Nordic.
After doing all the steps everything works but when the phone goes to sleep (the screen turns off and after a minute or two)) it will freeze (someone wrote it was AOD but it doesn't matter if it is running or not).
I also noticed the phone is lagging when using the startup guide, but it disappear after a reboot, but if i leave the phone and letting it fall in to sleep it will freeze and won't wake up again.
The only difference between "SuperSU 2.82-SR5" and "Magisk 16.6" is that with Magisk the phone is lagging at the startup guide and with SuperSU i have no SuperSU icon in apps to run.
And believe me, i have rebooted, but it won't help, no SuperSU icon. When the phone goes to sleep it freezes again.
I install TWRP with ODIN and Wiped the phone and rebooted into recovery, then i did:
1. no-verity-opt-encrypt-6.0-star.zip
2. rebooted into recovery
3. RMM-State_Bypass_Mesa.zip (i have even tryed RMM-State_Bypass_Mesa_v2.zip)
4. SR5-SuperSU-v2.82-SR5-20171001224502.zip (or Magisk 16.6)
5. samsung-antiroot-removal-2.4.zip (i have even tryed samsung-antiroot-removal-4.1.zip)
6. reboot and wait
The phone will always show the "OEM unlock" so i don't need to wait 7 days for it to appear.
Any advice on how i should proceed?
Additional information:
I have now restored the phone back to default (ODIN and the 4 firmware files) and now it won't freeze anymore and "OEM unlock" is still enabled with this text below "Bootloader is already unlocked". Unfortunately the phone isn't rooted now
It seems that if i only flash TWRP i get the same behavior, it freeze after a while after the screen has turn it self off.
Click to expand...
Click to collapse
Hey how do I restore my phone back to default. I have the same problem as you. My phone keeps freezing HELP PLEASE!
Benjamony said:
Hey how do I restore my phone back to default. I have the same problem as you. My phone keeps freezing HELP PLEASE!
Click to expand...
Click to collapse
I suggest you to download the latest Firmware from Sammobile for your Device and flash it with Odin .
Btw i would always check how to Recover my Phone before i do Modefication like this , then its much more easy to go back to Stock if something goes wrong .
Benjamony said:
Hey how do I restore my phone back to default. I have the same problem as you. My phone keeps freezing HELP PLEASE!
Click to expand...
Click to collapse
I'm running DevBase and it is now working perfect. Try to install it. I don't believe you need to go to stock first.
https://forum.xda-developers.com/ga...-development/rom-u1arc5-devbase-v5-2-t3764822
SHOTOKANKATANA said:
Maybe we are doing something wrong I'm not sure.
I know I followed multiple guides up to the smallest detail. The result is the same every time. There's 1 thing I noticed though.
I'm using the BRF8 firmware as are you, maybe that's the problem? In the video guides they're mostly on BRE5.
It looks like it's just us with this issue. I can't find any other info on this particular matter...
I've posted this question on another thread.
Here's the link in case you want to follow....
https://forum.xda-developers.com/ga...cross-device-development/twrp-exynos-t3763464
Click to expand...
Click to collapse
its not the csc. i'm on csf2 and i have the same problem