Hi all,
A definite noob here and to these devices in general so any help is greatly appreciated. I did use the search function but really did not find any discussion that addressed this problem. I work for a repair/refurb/insurance facility and can not get Bootloader mode to display on some M919 devices. Display stays blank(black). When I connect to Anyway jig/Odin, device does not indicate it is in Factory Mode, display is black(blank). I can not even tell if they have been rooted since nothing is displayed.
Version of software in devices shows it to be AMDL.
Odin connects to device and can flash device to latest MK2, but still will not go into or indicate that it is in Bootloader mode when using Volume – down, Home, and Power buttons. Factory reset from menu did not work either.
If just turning the devices on they work just fine. Except now I have noticed that the softkeys, Menu and Back Arrow do not work. The rest of the touch display does..odd.
So questions are basically...
1.)Why does Bootloader mode/counters not show when holding the volume down/Home/Power keys?
2.)Why when connected to Odin via Anway jig does device not indicate it is in factory mode like other like devices as well as other models do?
3.)Why do the Menu and Back Arrow softkeys no longer work after flashing to MK2?
Related
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 have been trying to search for the past month regarding any related information on the bootloader info of the n7105.
If I go to ROM Download mode, my phone will get stuck on the first screen, and pressing the up or down volume button won't work. In normal phone operation btw, both keys volume up and down works perfectly fine. In the first screen download mode, we usually get the bootloader info in the upper left corner of the screen in red text. However my device has none. It just blank. So I dont see any info as how many times a ROM was flashed or knox has been triggered, bootloader version, etc.
If I want to flash a ROM on the n7105, I can opt to utilize adb commands to force go into download mode or use a 3rd party recovery with booting into download mode option.
Any help as to how I can restore my bootloader info is much appreciated.
Thanks.
no one can help me?
Hey mate did you get this sorted?
BTW you havent seen jigs around have ya?
Hi
Could some one tell me why i cant get in recovery or factory mode with hardware buttons, i am on stock 10d with twrp recovery installed and rooted wirh super su through twrp. I installed twrp through adb with normal command and device works just fine through reboot apps from os, boots in recovery,fastboot etc just fine,same through adb commands.
But there's no hardware combo or anyrhing working when trying to enter recovery or factory reset working at all?
Tryied every combo i could find saying how to from internet.
It just boot up in os as usual.
And phone dosen't reset while holding power button for 10s + either
It's a bit scary because bootloop is going to come eventually for sure and then there's no rescuing avalible
Could someone plz tell me whats going on?
Im new to g4 so, some help would be nice.
Thanks in advace
It's a bit tricky, to be honest.
• Power off your phone
• Hold "Volume-Down" and keep your "Power-Button" pressed. So you should keep both pressed, until the 1st LG logo appears
• Now just leave the "Power-Button" for ~1 second whilst kept the "Volume-Down" button still pressed, press now the "Power-Button" again and keep holding it
You're now forced to deal with the standard-ui from LG. Go to "Yes" and again "Yes". TWRP now boots and you should be fine .
Edit: Just my tiny story... I watched several videos and also had a nasty bootloop. I was afraid, I now bricked my phone. But a nice user showed me this way and this was the only way, I got my phone recovered.
Soo.... I messed up and edited the build.prop specificly the ro.build.type property. I tried to enable some debug options without validating if this would be a good idea (hint: it's not).
It seems that this has bricked my phone, the first LG splash screen shows up with the powered by android, and the second animation just keeps loading forever (making the phone very hot). And the LED flashes blue continously.
I did manage to get the device visible in ADB but it tells me that the device is offline so I can't do anything with it.
Tried booting in recovery mode (holding power button + volume down) but it just own't go into recovery mode.
Some extra info of what runs on my phone:
- version H815
- Android 6.0
- bootloader unlocked
- TWRP installed
- Rooted
- XPosed installed
Any idea on what I could try to fix it? (I guess stuck with a brick but oh well).
Thanks!
What do you mean, by it can't go into recovery mode?
Nothing is showing on screen?
Go to downlod mode either use lgup or lg flashtool to reflash the firmware that you are on... Do u remember which firmware you were on ?
Thanks for the replies!
Vortuks said:
What do you mean, by it can't go into recovery mode?
Nothing is showing on screen?
Click to expand...
Click to collapse
I meant that it just boots 'normally' when I press those buttons, it shows me the first LG logo and the second animation just hangs, whatever I do. I tried all sorts of combinations with the power button + volume down. (Keeping it pressed, briefly letting it go after the lg logo and repressing them).
jinderation said:
Go to downlod mode either use lgup or lg flashtool to reflash the firmware that you are on... Do u remember which firmware you were on ?
Click to expand...
Click to collapse
I don't know exactly which firmware I was on but I can't even get my phone into download mode (same as my other response, pressing volume up doesn't do anything).
The recovery and download mode used to work but I have no idea why it doesn't now...
When booting the phone, hold the power button and volume down button simultaneously, when LG logo appear, push the power button again. You should see the white screen, where you choose "YES" twice. Then the phone should kick you into TWRP or different recovery mode.
But how the hell editing build.prop can mess with recovery and download mode? Sounds incredible
Vortuks said:
But how the hell editing build.prop can mess with recovery and download mode? Sounds incredible
Click to expand...
Click to collapse
Maybe he has bootloop issue... ILAPO
Yeah I have no idea why the buttons aren't working for me. After a lot of searching I found this thread:
http://forum.xda-developers.com/g4/help/soft-bricked-device-t3248144
Which is basicly the same thing I'm experiencing, ADB comes online for just a brief second (kept spamming the reboot recovery command) and got in TWRP and I just flashed another which worked fine.
Odd thing is, even now my phone works I can't start recovery or download with the hardware buttons...... oh well, thankfully adb works as it's supposed to.
Thank you all for your help!
Hey! Need some help if possible. I was messing around with my Captivate Glide. Tried to install some other ROM's but all of them made the phone lost the baseband and IMEI (EFS). I tried restoring the EFS using EFS Pro Tool, but my phone is not being recognized while on CM 11. I decided just to flash back to stock, using the I927UCLJ3_I927ATTLJ3_ATT (which was the only ROM that was showing up the IMEI and got connectivity).
Something that's been bugging me is that after doing all this, the phone boots normally, but there was no welcome screen, it just jumped straight to the main menu without asking for the google account. On top of that, the power button no longer shows the options it did before (reboot, power off). With one press it powers off the screen. If I press it for 2 seconds the phone turns off. There's no even a lock screen on my phone. I've been unable to set lock screen security options. Any options that I select are useless. They do show up under settings, but they don't do anything.
I've been trying everything to get this options back, but I'm not sure how to. I've already flashed my phone to stock, tried with other ROMS, using the same I927ATTLJ3 as reference (since it's the only one that shows the IMEI for me) but nothing. It was showing on CM11 though, all power options where working, as well as the lock screen options. I'm desperate now.
Any help on this?
leonardoor said:
Hey! Need some help if possible. I was messing around with my Captivate Glide. Tried to install some other ROM's but all of them made the phone lost the baseband and IMEI (EFS). I tried restoring the EFS using EFS Pro Tool, but my phone is not being recognized while on CM 11. I decided just to flash back to stock, using the I927UCLJ3_I927ATTLJ3_ATT (which was the only ROM that was showing up the IMEI and got connectivity).
Something that's been bugging me is that after doing all this, the phone boots normally, but there was no welcome screen, it just jumped straight to the main menu without asking for the google account. On top of that, the power button no longer shows the options it did before (reboot, power off). With one press it powers off the screen. If I press it for 2 seconds the phone turns off. There's no even a lock screen on my phone. I've been unable to set lock screen security options. Any options that I select are useless. They do show up under settings, but they don't do anything.
I've been trying everything to get this options back, but I'm not sure how to. I've already flashed my phone to stock, tried with other ROMS, using the same I927ATTLJ3 as reference (since it's the only one that shows the IMEI for me) but nothing. It was showing on CM11 though, all power options where working, as well as the lock screen options. I'm desperate now.
Any help on this?
Click to expand...
Click to collapse
Have you factory reset your phone? That described things can happen especially when switching between ROMs