So this may be a stupid question (but it's my first post so go figure) but I've read a few forum posts and I still can't seem to find a resolution.
I'm using a Rogers SGH i3170 with Android 4.3. I used the cf auto root file to root my phone with ODIN and otherwise did not modify the original software I manually installed the SuperSu apk to get around KNOX.
I was going to sell the phone so I went into the backup & reset option to clear out all my information. the phone seemed to clear itself just fine but now it won't go back the 'samsung' boot screen.
It'll show the device name, do the boot animation and otherwise just sits there.
The battery is at 80-90%
My main issue is that I would flash the stock ROM but it also won't go into recovery mode. It just reboots without actually going there.
Did I just brick my phone?
**I'm fairly new to rooting, I've rooted my S4 and Nexus 5 and was able to reset them without issue through the menus without using CWM or TWRP. I'm familiar enough with the processes just need some direction I guess!
Try this: Vol down& power& home. That'll put you into download mode so you can use Odin to return to stock...
You can also try THIS
If that doesn't help then goHERE for more INFO:thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk
LENT0N said:
So this may be a stupid question (but it's my first post so go figure) but I've read a few forum posts and I still can't seem to find a resolution.
I'm using a Rogers SGH i3170 with Android 4.3. I used the cf auto root file to root my phone with ODIN and otherwise did not modify the original software I manually installed the SuperSu apk to get around KNOX.
I was going to sell the phone so I went into the backup & reset option to clear out all my information. the phone seemed to clear itself just fine but now it won't go back the 'samsung' boot screen.
It'll show the device name, do the boot animation and otherwise just sits there.
The battery is at 80-90%
My main issue is that I would flash the stock ROM but it also won't go into recovery mode. It just reboots without actually going there.
Did I just brick my phone?
**I'm fairly new to rooting, I've rooted my S4 and Nexus 5 and was able to reset them without issue through the menus without using CWM or TWRP. I'm familiar enough with the processes just need some direction I guess!
Click to expand...
Click to collapse
My guess would be depending on what options you chose for wiping your data you probably wiped the root folder.
in which case there is nothing to boot to.
I have done that before in error and its a pain.
If you still have a recovery great you just need to flash a ROM.
Otherwise you might have to ODIN a recovery back on and then flash. Which is what I had to do.
long story short i have a Sprint galaxy s3 that is locked w a pattern lock and im unable to get in. i did ALOT of research and came across a few options but none work. one method says i should use adb to remove the lock ( http://forum.xda-developers.com/showthread.php?t=1800799) got stuck cause its not rooted and no custom recovery. i tried to flash CWM and root using this method (http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/) odin said pass but i wasnt able to get into any custom recovery it would just hang when using the vol+ home power combination. stock recovery still works the same.
All i want to do is unlock this phone that has a pattern lock.Google account not an option.the owner passed away and im trying to unlock for her family to get contacts and internal photos etc. im not sure if usb debug is on however adb recognized the device so i assumed it was. the reason i guess im having a hard time is because not alot of information is available given the circumstances. Ive been reading for 7+ hours now afraid to ask for help as ppl always get flamed if there is already a solution somewhere. if there is i havent found it. Thanks for any help
Follow this to get custom recovery: http://forum.xda-developers.com/showthread.php?t=2011491
Then mount /data and delete /data/system/gesture.key from recovery
tried.that didnt work because i didn't have su in adb. i was finally able to root using cf auto root method and then install LATEST CWM and followed this guide to reset lock screen. success. http://forum.xda-developers.com/showthread.php?t=2437946
alfizzle said:
tried.that didnt work because i didn't have su in adb. i was finally able to root using cf auto root method and then install LATEST CWM and followed this guide to reset lock screen. success. http://forum.xda-developers.com/showthread.php?t=2437946
Click to expand...
Click to collapse
It probably does the same thing I just said, delete the data/system/gesture.key file
Please help!
I must have disabled samsung keyboard a while back, as I only use swype, but I use fingerprint auth which requires password typed in after each reboot.
I tried ultra power saving mode today and it powered off when the phone died anyway, but now on reboot, I can't type the password in because it won't load swype keyboard and apparently samsung keyboard is disabled, or something(maybe I disabled it with titanium backup? I don't remember).
adb apparently doesn't work in UPSM, but I can reboot to TWRP recovery, but what do I do? safe mode had the same problem, and I tried this:
https://www.youtube.com/watch?v=3b9rtnCgvlw
Through TWRP, but I still can't type the password on startup. As mentioned, adb doesn't see the device in UPSM, it seems, so I can't insert a keyboard event.
Please help, trying to avoid factory reset!
I disabled launchers with Titaniumbackup without installing one i rebooted wtf bricked the phone. Thankfully i got backups. Only got into after a restore. If that helps any. U might have to odin stock if all else fails.
Jimmy1life said:
I disabled launchers with Titaniumbackup without installing one i rebooted wtf bricked the phone. Thankfully i got backups. Only got into after a restore. If that helps any. U might have to odin stock if all else fails.
Click to expand...
Click to collapse
I had to use odin stock, but fortunately, I used:
ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar.zip
And my battery performance is now like 70% better.
Instead of flooding the bootloader thread, I humbly ask for anyone's help in getting my N4 rooted so that I can unlock the bootloader.
1. I am able to use Kingroot to obtain temp root
2A. I open Root Checker and N4 reboots
OR
2B. Root checker OK then I get to ADB and enter a push command, the N4 reboots
This is where I am stuck.
Bootloader
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
coledeb said:
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=66371097&postcount=237
I had the same bootloop problem and following those directions fixed it for me. I had to use Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip as my kernel. Later versions didn't work (wrong phone version?).
coledeb said:
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
Click to expand...
Click to collapse
Why don't you guys flash a ROM that is rooted instead of flashing SU?
Edit:
But if whatever you guys are doing works eventually, keep doing that.
thanks for everyone's help - I finally got DEV mode to stick!
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
stefan1301 said:
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
Click to expand...
Click to collapse
Sounds to me like the hardware itself is bricked or damaged. If that is the case, the only option is to replace the motherboard.
Sent from my SM-S767VL using Tapatalk
Try to flash latest rom
Here is the solution
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
alaanhaliko said:
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
Click to expand...
Click to collapse
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
alaanhaliko said:
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
Click to expand...
Click to collapse
No, I'm talking specifically of FRP lock.
The point you make about binaries has nothing to do with FRP. Binaries can be blocked on both FRP locked and FRP unlocked devices. The binaries only prevent flashing firmware with a lower binary than the current binary installed on the device. Binary version is related to RMM or KG state, not FRP. FRP is directly related to MDM and only "partially" related to the things you mention and only because there are other "tamper-proof" elements that "can" trigger FRP. Have you ever noticed that a device that does not have a Google account signed in does not encounter FRP issues when the device is factory reset, but if there is a Google account signed in the device, factory reset triggers FRP? If it were as you you seem to be suggesting, FRP would be triggered on devices that have no Google account associated to them when attempting to flash/modify the device, but this is not what happens.
OEM unlock really only applies to unlocking bootloader in order to flash unapproved software or make modifications to the system partition without being blocked.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk