Hi,
I'm trying to upgrade the phone so I can get a new android version to play pokemon go on for my son.
I have tried pressing volume +- down , power volume +, and power volume -.
Everything I tried gets me to the standard recovery.
This is a non-modded phone.
Any ideas?
I have an option in the recovery mode to apply update from ADB. That knocks out odin but I'm not sure if the default android recovery will work for that.
Any suggestions?
Hello, I don't know if you are still having trouble, but to enter recovery mode you must hold volume up and volume down while plugging in a USB cable (one that is plugged into a computer). You can find the latest stock update, Jelly Bean, for this device here:
https://forum.xda-developers.com/showthread.php?t=2226886
However, I believe Pokemon Go requires Android Kitkat or newer so you may need a custom ROM. If you decide to install a custom ROM you should still flash the newest stock update via Odin first to ensure your device is fully updated. Although I am not entirely certain if Pokemon Go will work on a custom ROM, as you may run into problems with SafetyNet.
I wish you the best of luck . Let me know if you need any more help.
Related
so i will start with the main problem of the phone
the down volume is not working.
so i rooted the phone,flash recovery,and flashed rootbox rom
but the rom isnt going up and stuck on the animation screen
but now i cant go inside the recovery since if want to do it via the toolbox so i need the phone to be on,
and i cant do it the normal way- down+power because the down volume isnt working
its really important please help??
Help someone???
It's really important
I believe you have two solutions, to fix the volume key or to buy a jig. As I don't believe there is another way to boot into any of the helpful modes (recovery, bootloader, odin) without adb, a working OS, or the volume key(s).
GT-N5100 After OTA 4.2.2 stuck in safe mode. I didn't expect problems from a stock update.
It was working perfectly yesterday. I have wiped it clean, no change.
Kies doesn't seem to offer anything that will recover it.
Does anyone have 4.1.2 for North America? It is the international version tablet.
The one strange thing is that the volume down button does not work now.
Baseband version: N5100XXCMJ2
Build Number: JDQ39.N5100XWCNA1
Any ideas?
Dulie said:
GT-N5100 After OTA 4.2.2 stuck in safe mode. I didn't expect problems from a stock update.
It was working perfectly yesterday. I have wiped it clean, no change.
Kies doesn't seem to offer anything that will recover it.
Does anyone have 4.1.2 for North America? It is the international version tablet.
The one strange thing is that the volume down button does not work now.
Baseband version: N5100XXCMJ2
Build Number: JDQ39.N5100XWCNA1
Any ideas?
Click to expand...
Click to collapse
Try volume up and hold until you see the Samsung on the screen. I use that to boot when hung with odd firmware issues arise.
You can try going into stock recovery holding down home, volume down and power key when powering up.
If you get the notice... you should be able to connect via USB to your computer and use Odin 3.7 and flash a compatible ROM for your device, if available. I don't have a 5100, so I am not able to assist in locating one for you. You should state what carrier your tablet is with. So others can assist with the right ROM.
gooberdude said:
Try volume up and hold until you see the Samsung on the screen. I use that to boot when hung with odd firmware issues arise.
You can try going into stock recovery holding down home, volume down and power key when powering up.
If you get the notice... you should be able to connect via USB to your computer and use Odin 3.7 and flash a compatible ROM for your device, if available. I don't have a 5100, so I am not able to assist in locating one for you. You should state what carrier your tablet is with. So others can assist with the right ROM.
Click to expand...
Click to collapse
T-mobile is my carrier. I tried the phone and text messages and they are not working, yet the mobile data is.
When I tried the home/voldwn/pwr I get the
Warning!
A custom os can cause critical problems in phone and installed applications.
If you want to download a custom os,press vol up key.
Otherwise, press the volume down key to cancel.
At this screen I can't press either button. Neither will do anything. I know the volup was just working.
I get different screens by either using the volup or voldwn. So this would indicate the vol buttons are fine as I knew yesterday.
I also was not wanting to do anything to void the warranty at this point since it is less than 1 month old.
OK, well then as long as it was an OTA and you did not root... I would take it back to T-mobile and ask for a replacement. They should be able to give you a replacement if they cannot reload the ROM and correct the issue.
gooberdude said:
OK, well then as long as it was an OTA and you did not root... I would take it back to T-mobile and ask for a replacement. They should be able to give you a replacement if they cannot reload the ROM and correct the issue.
Click to expand...
Click to collapse
Samsung said to stop by a best buy where the samsung store is inside and have them reflash it with a US carrier firmware.
That seemed like a good idea, but he was unable to get to his server where the firmware resides. He also made mension of the fact they have heard of this model having these issues. So he was unable to do anything after an hour of computer issues with reaching their internal site.
Stuck in "Safe Mode" Issue Corrected
:laugh:
The Samsung reps at my local BestBuy could not fix it. They said they could fix anything. Not this apparently.
I remember that sometimes after firmware loads need to be cleared out. So I found this procedure, which is part of a manual firmware update, and figured maybe it would clear the issue causing safe mode.
If Galaxy Note 8.0 N5100 stuck at booting animation after Step 10 then go to recovery mode (press and hold the Volume Up, Home and Power buttons together) and perform Wipe data/Factory Reset and Wipe Cache Partition task before selecting reboot system now function. In recovery mode use Volume keys to navigate between options and Power key to select the option. Please note, performing wiping task will erase your device internal memory data and not external SD card data.
YES, no more safe mode!!
i just bricked my M8 (stock 4.4.2 just rooted)
i rooted my phone so i couldn't get OTA updated to i tried to use "[GUIDE] How to add root access & and keep official OTA updates | 3.28.401.9"
but after i flashed boot.img using fastboot flash boot boot.img command in the fastboot mode the phone stuck on boot screen (HTC logo boot up screen) even after i heard the rom sound load up
now i can't even restart my phone to be able to access the boot menu
i tried to use Android Revolution HD rom to i use their "Flash_recovery_3.28.401.7" now i can't even log into recovery "i wait to the battery is empty to be able to access boot menu :crying
any help plzzzzz :crying:
thx in advance
sahmeds said:
i just bricked my M8 (stock 4.4.2 just rooted)
i rooted my phone so i couldn't get OTA updated to i tried to use "[GUIDE] How to add root access & and keep official OTA updates | 3.28.401.9"
but after i flashed boot.img using fastboot flash boot boot.img command in the fastboot mode the phone stuck on boot screen (HTC logo boot up screen) even after i heard the rom sound load up
now i can't even restart my phone to be able to access the boot menu
i tried to use Android Revolution HD rom to i use their "Flash_recovery_3.28.401.7" now i can't even log into recovery "i wait to the battery is empty to be able to access boot menu :crying
any help plzzzzz :crying:
thx in advance
Click to expand...
Click to collapse
Well that's one of the perks of flashing a 3.xx.xxx.x ROM on 1.xx.xxx.x(4.4.2) firmware. You get to have extremely long boot up times and you won't have a proper working radio which leaves you with no wifi, data, gps, bluetooth...
Your OTA probably didn't work because of a custom recovery, not because it was rooted. Root does NOT prevent OTA updates from installing, though you might lose root access after the OTA.
If you're stuck at Boot screen hold Volume UP + Power button for 10seconds, as soon as the screen goes black press volume Down + Power button to enter into Bootloader.
Flash a custom recovery like TWRP. Go into recovery and restore a nandroid backup for your device.
first thx alot for replaying
i already got TWRP installed but the screen is stock on boot screen but still manage on the back ground to load my current rom as i'm hearing the log in sound of the rom :S
so i tried to power it off without seeing by holding the power key the power option pop up and touching random parts of the screen but i failed
i even waited for the battery to empty and factory reset the phone with no use
is these is any way even by adb to power off my phone
plzzz help
thx again for replaying
sahmeds said:
first thx alot for replaying
i already got TWRP installed but the screen is stock on boot screen but still manage on the back ground to load my current rom as i'm hearing the log in sound of the rom :S
so i tried to power it off without seeing by holding the power key the power option pop up and touching random parts of the screen but i failed
i even waited for the battery to empty and factory reset the phone with no use
is these is any way even by adb to power off my phone
plzzz help
thx again for replaying
Click to expand...
Click to collapse
By the look of things you are booted in OS but have no screen, hence why try and hold power button in and randomly tap to shut off?
I told you already to Hold Volume UP + Power button for about 10seconds and then hold volume down + power to enter bootloader.
You can of course also just plug it in and try to reboot to bootloader using adb, if you have USB debugging enabled. adb reboot bootloader
As already said just hold power and volume up for around 12 seconds then immediately press and hold power and volume down. This will always get you into the boot loader.
However if adb is working just use the command above. Reflash the original boot.img and you should be good.
ashyx said:
As already said just hold power and volume up for around 12 seconds then immediately press and hold power and volume down. This will always get you into the boot loader.
However if adb is working just use the command above. Reflash the original boot.img and you should be good.
Click to expand...
Click to collapse
ya power and volume up worked for me thx
i flashed the boot.img using adb and stock recovery that make it don't even continue to the rom but hang up
so i installed twrp-2.8.0.1 so now i got recovery working but i still can't get in the rom as it's still no screen
must it install a new rom or can you give me a stock boot.img (may be mine have an issue)
and if i need to install a new rom can u recommend one for me (just direct me to the link)
thx again now i got a new hope
http://forum.xda-developers.com/showthread.php?t=2701376
Use that to get back to the stock rom for your phone. Then after installing the right one, get the OTA
sahmeds said:
ya power and volume up worked for me thx
i flashed the boot.img using adb and stock recovery that make it don't even continue to the rom but hang up
so i installed twrp-2.8.0.1 so now i got recovery working but i still can't get in the rom as it's still no screen
must it install a new rom or can you give me a stock boot.img (may be mine have an issue)
and if i need to install a new rom can u recommend one for me (just direct me to the link)
thx again now i got a new hope
Click to expand...
Click to collapse
Never leave your device with an empty battery. In any circumstances.
Because you might not be able to charge it. Recover the device while you have some power on your battery.
Remember, this is a unibody device. It's not so easy to pull out the battery.
Hi all,
I am trying to get my Galaxy Tab 3 7.0 back to live, in a way.
It is currently running on stock, end it is super slow, almost a nightmare.
So what about an alternative Rom. I want to try Lineage OS.
Now I have understood that you need to have TWRP recovery if you want to be able to install/flash Lineage OS
Now here I am getting stuck.
The device is Rooted, rooted and checked with Kingo Root
When I flash (via ODIN) TWRP (any version) on the Tablet, I am unable to get in to recovery . If I use stock bootloader there is no problem, if I flash CMW I also can get in to Recovery, but when I flash TWRP, forget it. Flashing with ODIN doesn't give me an error, flash always succes full.
I even tried the App (Official TRWP App) to flash, but no way.
What do I mean with it doesn't work, well I turn the device of then I Press "HOME" + "Volume UP" + "Power On" I get stuck on the Samsung Galaxy Tab 3 logo, nothing happens, until I long press Power button and it restarts normally, but forget about recovery it wont work, if I try "HOME" + "Volume Down" + "Power On" it works fine to get to the download part.
When I put the Stock Bootloader or CMW it is no problem to get in to Recovery.
What is going on??
Where did you TWRP file from, is it for the correct device?
I have a bootloop when trying to enter recovery mode. I can kind of fix this by constantly trying to enter the download mode (power+VolDown). After a while when hitting just the right time this works. When in downloadmode I can install TWRP via ODIN and after the installation my device boots normally again.
So I can make my device work again but still cannot update android. I am still on 5.1.1. (rooted). It does not matter if I try to enter recovery by pressing the hardware buttons or using the TWRP App. The result is always the same.
Are there any other ways to install a current Lineage OS without recovery mode? Maybe using ODIN or ADB? Or is there anything in addition I can try to do to make recovery work again?
I have some weird theory. If Magisk is installed, it can be located on the recovery instead of bootloader or kernel partition. Then the keys won't work, but after 20-30mins of booting or bootlooping of the system you will be taken to TWRP. That's what i experienced on my Galaxy S5 recently.
I'd never use the boot key combo as long as system is still working, custom roms have the option to reboot to recovery, with stock you need an app and root.
On the p605 you don't need to press Home, despite common opinion,so it's quite foolproof to keep the other buttons down and release power, when the screen lights up. If this don't work, then it's the other fault condition, i'm just not sure whether my assumption's right. And whether you can count on the watchdog timer or will have to finally use Fastboot and a pc connection(i did not in years).