Related
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
bweN diorD said:
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
Click to expand...
Click to collapse
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
ajh305 said:
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
Click to expand...
Click to collapse
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
bjoostema said:
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
Click to expand...
Click to collapse
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
EDIT: I tried another 4.3 rom and booted it up. Set some things up then updated su binaries and restarted and let it sit there at the unlocked bootloader warning for 15 minutes with no changes.
bweN diorD said:
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
Click to expand...
Click to collapse
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
ajh305 said:
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
Click to expand...
Click to collapse
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
bjoostema said:
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
Click to expand...
Click to collapse
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
ajh305 said:
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
bjoostema said:
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
Click to expand...
Click to collapse
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
ajh305 said:
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
Click to expand...
Click to collapse
Awesome man! I'm glad it booted up for you welcome to the 4.3 side!
ajh305 said:
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
Click to expand...
Click to collapse
glad you got it fixed but i have to ask, in the sequence above why are you restoring a backup? you should be going right from stock to 4.3. also, some people have issues with twrp and 4.3, thats why i suggested cwm.
I'm not sure why I restored the backup. I didn't think coming from stock would work for some reason.
Sent from my XT926 using xda app-developers app
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
sgtslaughter64 said:
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
Click to expand...
Click to collapse
This was the only thing that worked for me. You could maybe try updating to the most current recovery instead of the one listed.
the only 2 issues i have seen to cause this problem are covered in the post a few below, and fixed it every time. my only suggestion would be to install cwm after rooting, then reboot, then continue with the steps. just my preference, it may not matter.
Not really sure how bad it is but here's what I did
Last night I got an update notice for cm-10.2-20131102-SNAPSHOT-M1-i9300.zip I decided to install it.
Install went great. I went to sleep
Woke up I realized it was really unstable my phone would restart, applications would crash decided to go back to my old rom.
I went to software update and I ran 10.1.3 and my phone was stuck at the loading screen.
I then decided to take out the battery and use a backup to restore to Samsung's Touchwiz I did that.
I then used MOBILE ODIN to flash 9.1.0 worked fine so I decided to try and flash 10.1.3 back on it with MOBILE ODIN but the version of mobile odin was really old and it didn't work and now my phone is just a black screen unless I go into CWM.
So now I'm stuck in ClockworkMod and it says I have no backups to restore to...
I found the backups
/sdcard/0/clockworkmod/backup/
but when I press restore it says no files found.
You can download a rom on your computer put it on your sdcard then flash it in recovery. Just make sure the rom is for your model of phone. If you have a verizon phone you do not want to flash the i9300 file again you are lucky your phone even turns on.
Sent from my SCH-I535
jhoutz said:
You can download a rom on your computer put it on your sdcard then flash it in recovery. Just make sure the rom is for your model of phone. If you have a verizon phone you do not want to flash the i9300 file again you are lucky your phone even turns on.
Sent from my SCH-I535
Click to expand...
Click to collapse
I have an i9300 phone international version... oh god I just realized I'm in the verizon section. How do I flash with CWM? Because I already have a 9.1.0 cyanogenmod rom in my phone.
iaxx23 said:
I have an i9300 phone international version... oh god I just realized I'm in the verizon section. How do I flash with CWM? Because I already have a 9.1.0 cyanogenmod rom in my phone.
Click to expand...
Click to collapse
First do a full wipe. Meaning format data, system, cache, and dalvik cache. The go to install, find your zip and go. Also with cm you prolly need to install the gapps too.
Sent from my SCH-I535
jhoutz said:
First do a full wipe. Meaning format data, system, cache, and dalvik cache. The go to install, find your zip and go. Also with cm you prolly need to install the gapps too.
Sent from my SCH-I535
Click to expand...
Click to collapse
Thank you so much. I was pretty scared... I heard the word brick like 3-4 times today I was about to lose my ****.
Thanks a lot!
i just did this myself and although i don't remember setting a password at all on TWRP, it's asking me one and i have no idea what it is. This is not allowing me to access data folder, sd card and such.
Can someone help me please?
---------- Post added at 06:57 AM ---------- Previous post was at 06:31 AM ----------
well, if i didn't type anything at all and cancel the password request, it seem to get by fine.
i was able to delete data and mount sd card.
my initial problem was that i kept trying passwords and getting errors, and then canceling the request.
Problem Solved.
You will just download a custom rom and install it with full wipe or use odin if you want to go back to original stock rom. It's just a softbrick, at least you can go to Clockworkmod Recovery, you can still recover your dead cellphone unlike to hardbrick which will go to a very complicated steps.
Hi There,
So, I have a Samsung Galax S2 Telus SGH-T989D phone and I decided to root it using the 4.4 KitKat and it went well and everything was great.
However, afterwards to resolve some other issues I was having I decided to make the mistake of loading the gapps which was for another
package into my phone and that messed everything up!
So, I have been struggling with the phone and first it wouldn't let me install another ROM from recovery and kept on giving me error 7 and 6
But, I fixed that and now I can install any ROM from the recovery or Odin (download mode) without any errors.
However:
The phone vibrates , brings up the galaxy logo and then the Koodo logo appears and a bar fills up quickly under it but it never goes away!!!
Phone freezes there and that's that!! Even after taking out the battery I noticed the logo was still stuck on the screen where as normally
it goes blank!!
So, at this point I am not sure what else to do! This is annoying and I'm tired of experimenting. I went through some XDA foroums here and
tried the Super Vipe (taking out the battery has been tried, factory reset and wiping the cache all have been tried)
So, please please please help me out here. I used to have a MyTouch4G which I rooted with CyanogenMod back in the day and it's the most
stable thing ever and all I wanted to do was to perform the same thing on my Galaxy S2 and boom not this time!!!
Awaiting your response and thanks in advance
King-2012 said:
Hi There,
So, I have a Samsung Galax S2 Telus SGH-T989D phone and I decided to root it using the 4.4 KitKat and it went well and everything was great.
However, afterwards to resolve some other issues I was having I decided to make the mistake of loading the gapps which was for another
package into my phone and that messed everything up!
So, I have been struggling with the phone and first it wouldn't let me install another ROM from recovery and kept on giving me error 7 and 6
But, I fixed that and now I can install any ROM from the recovery or Odin (download mode) without any errors.
However:
The phone vibrates , brings up the galaxy logo and then the Koodo logo appears and a bar fills up quickly under it but it never goes away!!!
Phone freezes there and that's that!! Even after taking out the battery I noticed the logo was still stuck on the screen where as normally
it goes blank!!
So, at this point I am not sure what else to do! This is annoying and I'm tired of experimenting. I went through some XDA foroums here and
tried the Super Vipe (taking out the battery has been tried, factory reset and wiping the cache all have been tried)
So, please please please help me out here. I used to have a MyTouch4G which I rooted with CyanogenMod back in the day and it's the most
stable thing ever and all I wanted to do was to perform the same thing on my Galaxy S2 and boom not this time!!!
Awaiting your response and thanks in advance
Click to expand...
Click to collapse
Clean solution: Flash stock firmware via Odin or install custom rom via recovery
LS.xD said:
Clean solution: Flash stock firmware via Odin or install custom rom via recovery
Click to expand...
Click to collapse
Thank you for your reply. However, as I've mentioned before, I've already tried those (from ODIN and through RECOVERY) with multiple different
ROMS and it's not doing anything which is why I am posting this here.
King-2012 said:
Thank you for your reply. However, as I've mentioned before, I've already tried those (from ODIN and through RECOVERY) with multiple different
ROMS and it's not doing anything which is why I am posting this here.
Click to expand...
Click to collapse
Did you perform a FULL wipe? Custom recovery -> format ALL partitions except EFS?
I have tried the Super Vipe off the SD card through the recovery mode and also from recovery I've tried the wipe cache,
factory reset and wipe cache partitions.
I am not sure about "format ALL partitions except EFS" nor am I aware of the procedure.
How would I perform that?
Have you installed a working custom recovery?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
LS.xD said:
Have you installed a working custom recovery?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
Yes I'm able to successfully install recovery-clockwork-5.0.2.7-hercules or CWM_Root_Superuser_3.1.3_Busybox_1.20.2
from the recovery without any errors (same if rooted through Odin)
If there's a specific ROM you are thinking about please let me know and I will be more than glad to give it a shot.
You really should use a newer recovery version. But for now go to mounts and storage and format all partitions except EFS. Then try flashing stock firmware via Odin
Here you can get the latest recovery for your device --> TWRP for hercules
LS.xD said:
You really should use a newer recovery version. But for now go to mounts and storage and format all partitions except EFS. Then try flashing stock firmware via Odin
Here you can get the latest recovery for your device --> TWRP for hercules
Click to expand...
Click to collapse
Under mounts and storage and format all partitions except EFS > Don't even see ESF there to begin with..
Do you have a working link for downloading the stock firmware? I have downloaded few and none of them even let me install them (status 0 error)
Any ideas?
Odin is already being used v3.0.7
Format System Data Cache dalvik. Realy... Then flash stock firmware using ODIN!
Sent from my beloved HTC One S using (most time buggy) Tapatalk
LS.xD said:
Format System Data Cache dalvik. Realy... Then flash stock firmware using ODIN!
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
I was able to finally bring it up!!
Basically I looked for a stock firmware for T-Mobile and after formatting the phones multiple times I tried this ROM
using ODIN and it got rid of the Koodo logo and replaced it with a T-Mobile logo and then it BOOM loaded to start screen finally!! :laugh:
I was about to hammer the phone. So, trust me I was very happy to see it work.
Thank you for your quick and helpful response :good:
Cheers :victory:
I have been having a persistent issue trying to encrypt my phone's internal storage. (Samsung Galaxy S4 mini LTE (GT-I9195). I thought it might be related to me rooting the device, since I read that you can't encrypt a rooted phone.
So a few minutes ago I plucked up the courage to follow the tutorial to flash my original downloaded firmware to the phone, in an attempt to erase all trace of root. Well the phone came up and wanted my password, so I rebooted and installed TWRP via odin again, then did a factory reset and then used the wipe data option and proceeded to make a backup, assuming this would be as useful and as good as odin-flashing my original firmware back for future use and more convenient and less dangerous than using odin.
Well, after booting it up, going through the setup wizard and then adding a lockscreen password, I am still unable to encrypt the phone. It shows the green android robot, screen fades out, then very soon after that the phone reboots and it all comes back up as normal unencrypted. Bare in mind that this is still the stock firmware that was odin-flashed and then a factory reset.
After all this, what would I need to do to get the phone encryption working?
Also, is my assumption correct, that the new TWRP backup I made, after flashing the original firmware via odin, is that new fresh backup as good as flashing the original again via odin? At least in terms of the OS status? I know the recovery isn't changed by such a backup and odin wipes absolutely everything, but I think you know what I am asking.
Morthawt said:
I have been having a persistent issue trying to encrypt my phone's internal storage. (Samsung Galaxy S4 mini LTE (GT-I9195). I thought it might be related to me rooting the device, since I read that you can't encrypt a rooted phone.
So a few minutes ago I plucked up the courage to follow the tutorial to flash my original downloaded firmware to the phone, in an attempt to erase all trace of root. Well the phone came up and wanted my password, so I rebooted and installed TWRP via odin again, then did a factory reset and then used the wipe data option and proceeded to make a backup, assuming this would be as useful and as good as odin-flashing my original firmware back for future use and more convenient and less dangerous than using odin.
Well, after booting it up, going through the setup wizard and then adding a lockscreen password, I am still unable to encrypt the phone. It shows the green android robot, screen fades out, then very soon after that the phone reboots and it all comes back up as normal unencrypted. Bare in mind that this is still the stock firmware that was odin-flashed and then a factory reset.
After all this, what would I need to do to get the phone encryption working?
Also, is my assumption correct, that the new TWRP backup I made, after flashing the original firmware via odin, is that new fresh backup as good as flashing the original again via odin? At least in terms of the OS status? I know the recovery isn't changed by such a backup and odin wipes absolutely everything, but I think you know what I am asking.
Click to expand...
Click to collapse
ODIN doesn't wipe everything. Perform a factory reset via stock recovery immediately after flashing the firmware via ODIN to set your phone back to stock. And who told you that enryption doesn't work with rooted phones?!
LS.xD said:
ODIN doesn't wipe everything. Perform a factory reset via stock recovery immediately after flashing the firmware via ODIN to set your phone back to stock. And who told you that enryption doesn't work with rooted phones?!
Click to expand...
Click to collapse
I did a factory reset and deleted data and performed a new backup that I have saved to the computer.
But when I started to realise I could not encrypt I went googling and found a blog post by someone who claimed that he had to jump through all kinds of hoops to get it to encrypt after he rooted his S4 mini. But my problem is even non-rooted on default firmware with TWRP recovery installed I cannot encrypt So I am hoping someone here will have the answer.
Morthawt said:
I did a factory reset and deleted data and performed a new backup that I have saved to the computer.
But when I started to realise I could not encrypt I went googling and found a blog post by someone who claimed that he had to jump through all kinds of hoops to get it to encrypt after he rooted his S4 mini. But my problem is even non-rooted on default firmware with TWRP recovery installed I cannot encrypt So I am hoping someone here will have the answer.
Click to expand...
Click to collapse
The point is that that KNOX detects the TWRP recovery. Enryption is possible with any rooted custom rom and probably with any roms but Samsung's S4 generation and newer due to the stupid KNOX security.
LS.xD said:
The point is that that KNOX detects the TWRP recovery. Enryption is possible with any rooted custom rom and probably with any roms but Samsung's S4 generation and newer due to the stupid KNOX security.
Click to expand...
Click to collapse
Well I did get encryption working one time on a custom rom but I have no idea how I did it. What should I do to improve my chances of getting encryption working? I thought when I rooted the original rom it removed knoxx?
unlocked note 3 n900 t mobile version, has twrp on it but my son either wiped or factory reset it, no operating system on it, d/l one (zip file) clicked install selected the zip, but it just seems to sit on the samsung galaxy note 3 screen, how long should this take? While I can do some stuff on computers, phones are a different fish.
kevin24018 said:
unlocked note 3 n900 t mobile version, has twrp on it but my son either wiped or factory reset it, no operating system on it, d/l one (zip file) clicked install selected the zip, but it just seems to sit on the samsung galaxy note 3 screen, how long should this take? While I can do some stuff on computers, phones are a different fish.
Click to expand...
Click to collapse
You booted to recovery, selected install zip, then after flashing, did you factory reset, wipe cache and wipe dalvik cache? If you didn't do the factory reset and wipe the 2 cache partitions, that would explain the bootloop(stuck at note 3 screen). If this is what you did, try booting to TWRP then factory reset and wipe the 2 cache partitions then reboot, it might take up 20 mins to an hour to restart and load the OS, just give it time to be sure.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You booted to recovery, selected install zip, then after flashing, did you factory reset, wipe cache and wipe dalvik cache? If you didn't do the factory reset and wipe the 2 cache partitions, that would explain the bootloop(stuck at note 3 screen). If this is what you did, try booting to TWRP then factory reset and wipe the 2 cache partitions then reboot, it might take up 20 mins to an hour to restart and load the OS, just give it time to be sure.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I did not do those things, thank you for taking the time to reply. What I did instead was download Odin, found a stock rom and loaded that, it worked the phone is functional. It's kind of fun actually, since I don't actually need this phone. My next step is to find out how to remove the rom and use a different one. I'm guess once it's unlocked it's unlocked and I don't have to contact the company again, right? thanks for your time.
kevin24018 said:
I did not do those things, thank you for taking the time to reply. What I did instead was download Odin, found a stock rom and loaded that, it worked the phone is functional. It's kind of fun actually, since I don't actually need this phone. My next step is to find out how to remove the rom and use a different one. I'm guess once it's unlocked it's unlocked and I don't have to contact the company again, right? thanks for your time.
Click to expand...
Click to collapse
If the stock firmware that you flashed has a locked bootloader, you won't be able to use TWRP or flash custom ROMs. If the bootloader is unlocked, then you can use TWRP and custom ROMs.
If there are any custom ROMs for your specific model number, you can do what you did previously, just do things in the right order this time.
Flash TWRP via Odin, boot into TWRP, select install, then select your custom ROM zip, then select "add more zips", then select the Gapps file to be flashed with your ROM(the correct gapps should be linked in the ROM thread where you find your ROM), swipe the slider to flash. After the ROM and Gapps are flashed, make sure you factory reset, wipe cache and wipe dalvik cache(do not do any other wipes), then reboot and wait for the OS to load and then sign in to the phone. You "should" be good to go after that, then you can install whatever apps you want and set everything up the way you want.
Sent from my LGL84VL using Tapatalk
Droidriven said:
If the stock firmware that you flashed has a locked bootloader, you won't be able to use TWRP or flash custom ROMs. If the bootloader is unlocked, then you can use TWRP and custom ROMs.
If there are any custom ROMs for your specific model number, you can do what you did previously, just do things in the right order this time.
Flash TWRP via Odin, boot into TWRP, select install, then select your custom ROM zip, then select "add more zips", then select the Gapps file to be flashed with your ROM(the correct gapps should be linked in the ROM thread where you find your ROM), swipe the slider to flash. After the ROM and Gapps are flashed, make sure you factory reset, wipe cache and wipe dalvik cache(do not do any other wipes), then reboot and wait for the OS to load and then sign in to the phone. You "should" be good to go after that, then you can install whatever apps you want and set everything up the way you want.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
yeah I think I may have relocked it I'll mess with it later, but I think I tried to load it back into twrp with the power,home and up vol button but it didn't load into twrp, would I have to call tmobile to have it unlocked again? thanks for the help btw, much appreciated.
kevin24018 said:
yeah I think I may have relocked it I'll mess with it later, but I think I tried to load it back into twrp with the power,home and up vol button but it didn't load into twrp, would I have to call tmobile to have it unlocked again? thanks for the help btw, much appreciated.
Click to expand...
Click to collapse
TWRP was removed and replaced with stock recovery when you flashed the firmware via Odin.
Most Samsung devices with locked bootloader these days, can't be unlocked. You might get lucky though, T-mobile might unlock it for you or allow you to unlock it. If you get it unlocked, you can flash it with custom software, but if they won't allow it to be unlocked, you'll be out of luck and stuck with stock.
Sent from my LGL84VL using Tapatalk
Droidriven said:
TWRP was removed and replaced with stock recovery when you flashed the firmware via Odin.
Most Samsung devices with locked bootloader these days, can't be unlocked. You might get lucky though, T-mobile might unlock it for you or allow you to unlock it. If you get it unlocked, you can flash it with custom software, but if they won't allow it to be unlocked, you'll be out of luck and stuck with stock.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
bummer, well I'll give it a try, I couldn't get anything to load with twrp so i used Odin, still learning this stuff, thanks again.