Lenovo k1 ideapad stuck in apx mode from low battery - Thinkpad Tablet General

My k1 is stuck in apx mode from low battery is there any way to get it to charge? Or out of apx mode? Is there anything i can do to fix this? If anyone could help me out id appreciate it alot
Sent from my DROID4 using Xparent Red Tapatalk 2

Looks like no help eh...
Sent from my DROID4 using Xparent Red Tapatalk 2

Perhaps some more information would be helpful.
What did you do before your K1 got stuck in APX mode?
Does your computer recognize the tablet when it is in APX mode and you connect it through USB?
What does nvflash show if you send a command?
What happens if you turn off your K1 and plug in the battery charger?
What happens if your K1 is in APX mode and you plug in the battery charger?

It wont flash anything it stops in the middle of the first sending step and ive tried more then once and when i started i was at 90 percent,
Sent from my DROID4 using Xparent Red Tapatalk 2

Well i was trying to get back to stock, the screen will light up and then dim when its connected to the charger with the two lights still lit, and when i got hook up to the computer recognizes it says its apx

Why do you think the problem is a low battery? Is there an error message saying so?
Are you using the right K1 stock ROM from this thread?
Could you please post a screenshot of nvflash when the flashing process stops?

It kind of sounds like your volume buttons are stuck.

Yes i could take a pic and post it thnx guys and yes thats the stock one ive been trying, also the one witn root, i was on the cm9 one also if that makes a difference
edit i just tried the cm9 to try and go back to it and it says bad data for the bootloader.bin ?
Stock> results from trying now
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks for the screenshot. If you try to flash the stock ROM again, does it stop at exactly the same position (system.img 319750144/419430400 bytes)?
I think it might be a problem with the USB connection. Do you have the chance to use another K1 USB cable? Do you use an USB hub that might cause problems?

isime13 said:
Thanks for the screenshot. If you try to flash the stock ROM again, does it stop at exactly the same position (system.img 319750144/419430400 bytes)?
I think it might be a problem with the USB connection. Do you have the chance to use another K1 USB cable? Do you use an USB hub that might cause problems?
Click to expand...
Click to collapse
i only have one cable and its like two months old only ,and ill try again and see if it does and ill test out different ports with the usb cable and ill let you know asap i didn't pay attention to that part but i will this time

i tried on another port and obviously its stuck on that part ill keep messing around =/
Sent from my DROID4 using Xparent Red Tapatalk 2

This pic Using a port in the back of my pc, the one that got stuck near the first part i used the port on the front of the pc near the power button, the one that got bad data with system.img at 3197 the front second port
Sent from my DROID4 using Xparent Red Tapatalk 2

I was able to fix my tablet ty! You were right about the usb ports
Sent from my Xoom using Xparent Red Tapatalk 2

Hello! I know it is been a year. Got here while browsing the web. I also am facing the same issue. My K1 got stuck on APX mode only. If you still remember, how did you get it done or revive your K1 fro this issue. Thanks!
UPDATE:
I recovered my K1 too for the 2nd time

Related

I think I have a brick :(

Hey guys this may amuse some of you but hoping someone can help me out. I bought my SGS i9000 this morning about 4 hours ago and it was running Eclair. I tried flashign with Kies but wasn';t having much luck. Needed to try and get into download mode for Odin so decided to flash a key combo fix to get into Download mode because it wasn't working. Next thing I know Odin crashes and my phone boots to this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Probably have a brick but hoping someone can help me see light at the end of the tunnel!
I've had that screen before
I was on Gingerbread, but was able to use the three button combo (vol down + home + power) to get back into download mode.
Unfortunately the key combo never worked for me. That's what I was trying to fix
Hello you have to buy usb.jig for sgs in ebay.for 5 euros or less and its solved
Sent from my GT-I9000 using XDA App
clarkey15 here is the solution for you http://forum.xda-developers.com/showthread.php?t=1153310
I tried that but PC is not recognising phone
Do you have samsung usb drivers installed on your pc ?
Yes I installed them before trying to flash. The PC is not even making any sounds while connected
Try a different USB port.
That sometimes resolves the PC not finding the phone.
I was under the impression that the I9000 was practically unbrickable.. Hm, there you go I guess.
Sent from my GT-I9000 using Tapatalk
aureleuz said:
I was under the impression that the I9000 was practically unbrickable.. Hm, there you go I guess.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
My reputation on other forums will suggest otherwise
Sorry for you guy.
I semi bricked my sgs so many times and flashed it with odin. But never seen your screen.
I read somewhere that with only usb plug modified you can go to download mode. But i don't remember how
Thanks everyone for your replies. I have just ordered a USB jig for the phone. Hope it will help my situation
Hope it'll work ^^
Firstly this is not a bricked phone - I've been there - a brick is dead, dodo - yours is semi-bricked (its recoverable without returning to Samsung)
remove battery and replace battery
plug in USB
hold vol-, home, power buttons - it might force download mode from where you can flash a new rom
this thread holds all you need to know
http://forum.xda-developers.com/showpost.php?p=14957283&postcount=1
finally, a jig will work - I've had one since samsung f*cked the bootloaders up in their stock 2.2 eclair. Its the last resort but WILL work
best of luck, let me know if you have any luck with this advice
Thanks for the reply. I am glad to know that someone has been through this before and has fixed it with a Jig. Only down side is I have to go back to my Hero while waiting for my jig.
have you tried the link I gave you? have you tried option (a) to the letter? Where are you in S wales? I'm in Cardiff and I've got one
Good i found this thread, i've reflashed my phone like 50 times and done a lot of testing. Well first time i got that picture too but it was because my windows had gone wonky and odin did not find phone and i just removed battery and put it in again and the pic was there automaticly. The three button combo for download mode worked like a charm, was going to test it first but tought i better go and read before doing anything hasty
mossy1963 said:
have you tried the link I gave you? have you tried option (a) to the letter? Where are you in S wales? I'm in Cardiff and I've got one
Click to expand...
Click to collapse
I've done most of those things. I've been at it for a while now. Only had the phone today too. I'm in Bridgend
ok....first follow that thread option (a) to the letter and it should work - if you got it from Carphone warehouse take it back - the one in Queen Street Cardiff fixed mine same day when I semi bricked mine in work and wasn't going home to sort out. as a bonus they flashed the latest FW - just play dumb - maybe try saying KIES offered you an upgrade which failed.
Finally when you get it sorted delete ALL drivers from your PC - your KIES problems are due to incompatibility of drivers following running Odin. Make sure that KIES is detecting your phone ok before letting Odin install its own drivers

Root GT-N8013

Hello All,
I've been trying to root my device following this thread:
http://forum.xda-developers.com/showthread.php?t=1957002
However once I reboot the device pressing the volume down, I don't get the ID:COM to light up in yellow.
If I plug the device in while its on, I do get the ID:COM to light up, so I'm guessing the drivers are correctly installed.
I have no idea what to do...
The reason for using this specific method, is because its supposed to be good for beginners.
I cant seem to find much additional information about what else to do.
Honestly I'm clueless and been searching around for a while online.
Any help would be appreciated.
fmf.post said:
Hello All,
I've been trying to root my device following this thread:
http://forum.xda-developers.com/showthread.php?t=1957002
However once I reboot the device pressing the volume down, I don't get the ID:COM to light up in yellow.
If I plug the device in while its on, I do get the ID:COM to light up, so I'm guessing the drivers are correctly installed.
I have no idea what to do...
The reason for using this specific method, is because its supposed to be good for beginners.
I cant seem to find much additional information about what else to do.
Honestly I'm clueless and been searching around for a while online.
Any help would be appreciated.
Click to expand...
Click to collapse
Did you install the samsung usb drivers on your pc?
fmf.post said:
Hello All,
I've been trying to root my device following this thread:
http://forum.xda-developers.com/showthread.php?t=1957002
However once I reboot the device pressing the volume down, I don't get the ID:COM to light up in yellow.
If I plug the device in while its on, I do get the ID:COM to light up, so I'm guessing the drivers are correctly installed.
I have no idea what to do...
The reason for using this specific method, is because its supposed to be good for beginners.
I cant seem to find much additional information about what else to do.
Honestly I'm clueless and been searching around for a while online.
Any help would be appreciated.
Click to expand...
Click to collapse
This method is easy and works .
Download Mode .
Put file to PDA in Odin .
Connect cable .
Flash .
http://forum.xda-developers.com/showthread.php?t=1831173
jje
I did...
conan1600 said:
Did you install the samsung usb drivers on your pc?
Click to expand...
Click to collapse
Yes, I installed kies as per instructions.
And I see the com port and tablet detected when I plug it in without being in download mode.
Thanks for the suggestion
Thanks All
fmf.post said:
Yes, I installed kies as per instructions.
And I see the com port and tablet detected when I plug it in without being in download mode.
Thanks for the suggestion
Click to expand...
Click to collapse
Ok... so guess what?
I was just being an idiot.
Instead of power and volume down, I was doing volume up.
Now it worked perfectly.
Thanks to all for comments.
fmf.post said:
Ok... so guess what?
I was just being an idiot.
Instead of power and volume down, I was doing volume up.
Now it worked perfectly.
Thanks to all for comments.
Click to expand...
Click to collapse
Is this after doing the JB update your using this root?
Yes
domethiuos said:
Is this after doing the JB update your using this root?
Click to expand...
Click to collapse
Yes, after the update.
It works perfectly.
Really easy and straight forward.
Took about 15 seconds.
fmf.post said:
Yes, after the update.
It works perfectly.
Really easy and straight forward.
Took about 15 seconds.
Click to expand...
Click to collapse
You didnt any files specific to 4.2.1 just the ones in his zip?
Sent from my GT-N8013 using Tapatalk HD
no. ..
domethiuos said:
You didnt any files specific to 4.2.1 just the ones in his zip?
Sent from my GT-N8013 using Tapatalk HD
Click to expand...
Click to collapse
The third post in that thread contains the specific files for our tablet.
Make sure you use the correct one.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The first file on the first post only contains the software needed on your pc.
Let me know if you need any more help, i was really clueless the first time.

Nexus 4 dead on 4.4.3 official

Hello, i whant to put 4.4.3 on N4 and with normal flash-all.bat(did it many times before on 4.4.2) and then phone was flashing booloader..waiting devices...and nothing.Phone screen is black only a sound on windows when i connect it.
How can i fix my nexus?
Edit: 1)if i shutdown with pwrbutton 10 sec and turn on via pwr+volume i hear as i connected the phone
2)if turn on normal red light a few sec..
Bricked???
Are you able to get to bootloader? Was it unlocked before you flashed the 4.4 3 image
Sent from my HTC One using Tapatalk
mrao said:
Are you able to get to bootloader? Was it unlocked before you flashed the 4.4 3 image
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
1)I had PA before on it
2)Yes i was unlocked
3)Black screen...nothing.Just a beep like i connect it to pc....and a red dot a few seconds.
krystyuc said:
1)I had PA before on it
2)Yes i was unlocked
3)Black screen...nothing.Just a beep like i connect it to pc....and a red dot a few seconds.
Click to expand...
Click to collapse
Just a wag, but have you tried letting it charge first?
Sent with my Nexus® 10 minus 3
Berrydroidcafe said:
Just a wag, but have you tried letting it charge first?
Sent with my Nexus® 10 minus 3
Click to expand...
Click to collapse
Yes.
Edit: If i plugit into a new pc it shows me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After some serch i think it's bricked....only Jtag can fix it
Don't think its bricked. Try type "fastboot devices" in a command prompt in your fastboot folder. If it shows up under listed devices its not bricked. I've had this happen where just the file that makes the screen light up didn't get installed. Just have to reinstall the bootloader. No big deal.
Scratch that!
I'll buy it from you for $5
M3drvr said:
Don't think its bricked. Try type "fastboot devices" in a command prompt in your fastboot folder. If it shows up under listed devices its not bricked. I've had this happen where just the file that makes the screen light up didn't get installed. Just have to reinstall the bootloader. No big deal.
Scratch that!
I'll buy it from you for $5
Click to expand...
Click to collapse
1)Already tryed that and the adb devices...no luck
2)Nothing is displayed on my n4 screen,absolutly black,but it's still on
3)my pc dose a sound when i connect/disconnect the phone
I found something
"Seems that while flashing that ROM you have managed to destroy parts of the Bootloader, wich finaly results in the device doing nothing. (Black Screen etc)
Partitialy you are right yes "QHS-USB Mode" means your device is hard bricked an in the so called QHS-USB Download Mode
but this mode is meant for vendors to flash bootloaders etc on the devices.
To access the device in a propper way u need some "non-public" tools wich QCOM usaly only supplies to vendors not to endusers!
Without thoose programs u will be not able to access the device in any way, even with thoose tools without the expierience and knowledge and files u need, i guess u will not be able to recover it yourself.
I do not want to risk some trouble with QCom at all so i do not can point u to the propper tools to use but i'm sure when using google u will be able to find out what tools i'm talking about.
In my mind the best way for you to recover that device is a JTAG
So my suggestion is to search for a JTAG in your region a JTAG in europe usaly is arround 30 euro but price can differ in your country"
So.....no luck till now,the phone is hardbricked.I'll send it monday to warranty,maybe they will fix it for free if not....then this is an excuse to buy N5

OnePlus 6T Bricked

Hello,
This problem has come up a lot i'm sure, but having looked at what feel like everything in xda website nothing has worked for me.
How did this happen? Phone froze and i held power button to shut it off, and it never booted past oneplus logo(Somehow corrupted itself). I went into recovery and wiped the phone since i dont keep much data on it. Instead now my phone is stuck on wiping itself.
FYI, the phone had Android 10.0.1 installed on it if that makes a difference.
My OnePlus 6T is bricked and here is what i can and cannot do:
Can do:
Boot into fastboot mode
Have the phone detected in ADB tools
Have the phone detected as Qualcomm HS-USB QDLoader 9008
Can't do:
Unlock the bootloader(Bootloader has never been unlocked on this device so i cant flash anything)
Boot into recovery mode(Vol up + power boots the phone instead)
Device wont boot past "Wiping, please wait." (Yes, i have waited HOURS for this to fix itself, nothing happens)
Tools i have tried to no avail:
MsmDownloadTool (All versions, nothing works! I get "FireHosecheckrsp failed errno 258" error. I have tried all possible drivers and cables as per some tutorials and discussion but nothing
I have tried MsmDownload tool int Windows 10, 7, even Vista(FireHosecheckrsp failed errno 258 every time)
Tool All In One, I cant flash anything through here since my bootloader is locked and i cant unlock it.
Flashing TWRP or other recoveries doesnt work because of locked state.
Anyway, sorry to ramble here. If anyone has any ideas, i would be happy to hear.
Best Regards
You have several serial ports interfering with the tool, so click the COM port bar and select the one belonging to the Snapdragon modem in the OnePlus 6T phone, and run this tool again. Error 258 is serial port conflicts or USB connection issues.
If unsuccessful, you will need to install Qualcomm USB driver. I am not sure if you have installed it though.
Sent from my ONEPLUS A6013 using Tapatalk
Dr. Mario said:
You have several serial ports interfering with the tool, so click the COM port bar and select the one belonging to the Snapdragon modem in the OnePlus 6T phone, and run this tool again. Error 258 is serial port conflicts or USB connection issues.
If unsuccessful, you will need to install Qualcomm USB driver. I am not sure if you have installed it though.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
COM4 is currently the only one that shows in MsmDownlaodTool and Qualcomm drivers are installed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's odd. Did you either try new USB-C cable, or getting the lints out of the USB-C port on the phone?
Sent from my ONEPLUS A6013 using Tapatalk
Dr. Mario said:
That's odd. Did you either try new USB-C cable, or getting the lints out of the USB-C port on the phone?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I have tried the original cable along with 2 others, which are from OnePlus as well. There is no dust or lint or anything in the port, fairly clean. :good:

Custom Binary (SYSTEM) Blocked by OEM lock

hey guys i recently had an update on my s10+ and mid through the update the phone just powered off(it was plugged to the charger) and since then ive been stuck on a blue screen saying i have to use the emergency recovery function in the smart switch pc app so i downloaded the app and tried to do that but the app wont recognize my phone. i searched all over the internet i tried flashing with odin a previous version and even the version it was trying to update to but it all failed. it gets stuck around 50% through the install and just sits there for hours without continuing. i am hopeless and have no idea what else i can do i even took the phone to a repair shop and they also failed to fix this problem. my last resort would be changing motherboard but i doubt its worth it. anyone has ideas what else i can do in order to fix this issue?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you able to get in to oden mode Google this to see how it's done.....
Sent from my CPH1951 using Tapatalk
stinka318 said:
Are you able to get in to oden mode Google this to see how it's done.....
Sent from my CPH1951 using Tapatalk
Click to expand...
Click to collapse
no i am unable to get into download mode i tried everything possible but the phone wont respond its stuck on a blue screen saying " An error has occurred while updating the device software. use the Emergency recovery function in the smart switch pc software.
also the phone only power on when its plugged to charger or a pc but it has battery for sure
Here is something to try......no guarantee.
https://drfone.wondershare.com/android-issue/android-blue-screen-of-death.html
Sent from my CPH1951 using Tapatalk
stinka318 said:
Here is something to try......no guarantee.
they dont have the latest phones on their list. latest version available they have is s9 plus
Click to expand...
Click to collapse
MrJoni94 said:
stinka318 said:
Here is something to try......no guarantee.
they dont have the latest phones on their list. latest version available they have is s9 plus
Click to expand...
Click to collapse
Email them to see if they can help in some way not sure if they'll can but it is worth a try but as I said no guarantee.......
Click to expand...
Click to collapse
Not sure if you've tried this but maybe it will work...
1) Hold bixby, volume down and while holding these, put the usb-c cable in the s10 when connected to the PC. This will (hopefully) get you into download mode if the other method fails
2)If Odin is still recognizing your phone, you have hope.
3)Make sure you use the latest version of Odin. I have previously tried to flash a new firmware with an old Odin and failed
4)Once you have the right Odin, try flash the latest stock firmware you can find. You may not be able to downgrade once upgraded

Categories

Resources