Database Users

[Q] Nexus 7-APX Looping even after successful flashing of a working bootloader 4.23

I was running stock rooted Android KK 4.4.4 on Nexus 2012 Wifi Only with bootloader as unlocked. I attempted the Lollypop update 5.0.2 by OTA but it gave an error while installing and device rebooted to Kit Kat normally.....working fine. OTA was not getting done for some reason may be because i was rooted.
I downloaded the factory image nakasi-lrx22g-factory-2291c36b.tgz from google and attempted to flash it using Nexus Root Toolkit(v 2.0.2) with option "No Wipe Mode" as selected and then the device ran into fastboot mode... NRT run commands like erase system etc then the script gave an error "Failed" "remote -invalid state" while attempting to write bootloader. I thought that the problem is with "No Wipe" selected so i re-attempted it with "No Wipe" being unselected. BUt same error.
I searched the forum & found that the issue may be due to incorrect/corrupted bootloader. I replaced the bootloader-grouper-4.23.img which was in the factory image with the 4.23 bootloader taken from JWR66V as most people over XDA have said that its the working bootloader.
I had flashed the img downloaded from here - http://forum.xda-developers.com/showpost.php?p=45043044&postcount=15
Flashing succeeded and Nexus Root Toolkit did not give error this time it said "OKAY" instead of "FAILED". But it did not proceed forward to flashing other files like system img etc. NRT was stuck at the Flash Bootloader - OKAY cmd.
I powered of the Tablet and Powered On again it showed "Booting Failed" at the Google Screen. I rebooted into Fastboot mode with "vol- and power" held together. It displayed the same screen as it did before i.e. displaying the information of Bootloader.
Product Name - Grouper
Variant - Not Defined Yet
HW Version - ER3
Bootloader version - 4.23
Baseband version - NA
Signing - Not Defined Yet
LOCK STATE = UNLOCKED
Then I read somewhere that after flashing the Bootloader img you have to run the bootloader by rebooting tablet with vol+,vol- and power button all held together.
I did that and wat i saw on computer screen was "APX device found" (((((
The device went into APX mode and since 2 days has not come out.
I tried pressing Power button for like 3mins with power adapter connected/disconnected by usb
I tried pressing vol- and power button for more than 5min. with system connected/disconnected with usb
Nothing worked...
I am wondering what took the device to APX because the bootloader was good one from "JWR66V". It was flashed with success by Nexus Root Toolkit. the device did run into fastboot mode once after flashing it. The Device went into APX after all the 3 keys "vol+ vol- and power" were pressed together. But according to key combo terms APX mode is activated when "Power" and "vol+" are pressed and it exits when "Power" alone is held for 15+ seconds.
What I feel now is that the device is in APX looping (similar to Bootlooping) due to some reason. Corrupted Bootloader can be one of that but its unlikely as flashing was successful and img used was authentic. One more reason of APX looping may be that nothing apart from Bootloader is present in it, no system no recovery. only bootloader is present.
Now what do I do to come out of APX ? Power button and Power+vol- etc not working tried them numerous times. It won't accept fastboot or adb commands as its in apx mode.
Its Out of Warranty so only 2 options left for me now
1. Battery Removal
2. NVFlash
I want to keep things simple so I am thinking of battery removal first. Does the battery removal reset nexus 7 ?
I have a feeling that its effect is same as the power button holding for 15sec. but will have to try. Although the Warranty is voided but will Asus people agree to provide paid service to me if i myself attempt battery removal by opening the back side of the device.
Incase this dont work I will move to nvflash
But I have a few questions regarding nvflash.
1. Does nvflash require blob n sbk even for an unlocked bootloader?
2. I can generate the SBK for my device using the CCSN number and try though but I want only a simple command which will reboot nexus into fastboot mode exiting APX mode.
any help will be appreciated.

BrightHeart said:
I was running stock rooted Android KK 4.4.4 on Nexus 2012 Wifi Only with bootloader as unlocked. I attempted the Lollypop update 5.0.2 by OTA but it gave an error while installing and device rebooted to Kit Kat normally.....working fine. OTA was not getting done for some reason may be because i was rooted.
I downloaded the factory image nakasi-lrx22g-factory-2291c36b.tgz from google and attempted to flash it using Nexus Root Toolkit(v 2.0.2) with option "No Wipe Mode" as selected and then the device ran into fastboot mode... NRT run commands like erase system etc then the script gave an error "Failed" "remote -invalid state" while attempting to write bootloader. I thought that the problem is with "No Wipe" selected so i re-attempted it with "No Wipe" being unselected. BUt same error.
I searched the forum & found that the issue may be due to incorrect/corrupted bootloader. I replaced the bootloader-grouper-4.23.img which was in the factory image with the 4.23 bootloader taken from JWR66V as most people over XDA have said that its the working bootloader.
I had flashed the img downloaded from here - http://forum.xda-developers.com/showpost.php?p=45043044&postcount=15
Flashing succeeded and Nexus Root Toolkit did not give error this time it said "OKAY" instead of "FAILED". But it did not proceed forward to flashing other files like system img etc. NRT was stuck at the Flash Bootloader - OKAY cmd.
I powered of the Tablet and Powered On again it showed "Booting Failed" at the Google Screen. I rebooted into Fastboot mode with "vol- and power" held together. It displayed the same screen as it did before i.e. displaying the information of Bootloader.
Product Name - Grouper
Variant - Not Defined Yet
HW Version - ER3
Bootloader version - 4.23
Baseband version - NA
Signing - Not Defined Yet
LOCK STATE = UNLOCKED
Then I read somewhere that after flashing the Bootloader img you have to run the bootloader by rebooting tablet with vol+,vol- and power button all held together.
I did that and wat i saw on computer screen was "APX device found" (((((
The device went into APX mode and since 2 days has not come out.
I tried pressing Power button for like 3mins with power adapter connected/disconnected by usb
I tried pressing vol- and power button for more than 5min. with system connected/disconnected with usb
Nothing worked...
I am wondering what took the device to APX because the bootloader was good one from "JWR66V". It was flashed with success by Nexus Root Toolkit. the device did run into fastboot mode once after flashing it. The Device went into APX after all the 3 keys "vol+ vol- and power" were pressed together. But according to key combo terms APX mode is activated when "Power" and "vol+" are pressed and it exits when "Power" alone is held for 15+ seconds.
What I feel now is that the device is in APX looping (similar to Bootlooping) due to some reason. Corrupted Bootloader can be one of that but its unlikely as flashing was successful and img used was authentic. One more reason of APX looping may be that nothing apart from Bootloader is present in it, no system no recovery. only bootloader is present.
Now what do I do to come out of APX ? Power button and Power+vol- etc not working tried them numerous times. It won't accept fastboot or adb commands as its in apx mode.
Its Out of Warranty so only 2 options left for me now
1. Battery Removal
2. NVFlash
I want to keep things simple so I am thinking of battery removal first. Does the battery removal reset nexus 7 ?
I have a feeling that its effect is same as the power button holding for 15sec. but will have to try. Although the Warranty is voided but will Asus people agree to provide paid service to me if i myself attempt battery removal by opening the back side of the device.
Incase this dont work I will move to nvflash
But I have a few questions regarding nvflash.
1. Does nvflash require blob n sbk even for an unlocked bootloader?
2. I can generate the SBK for my device using the CCSN number and try though but I want only a simple command which will reboot nexus into fastboot mode exiting APX mode.
any help will be appreciated.
Click to expand...
Click to collapse
U have done it in wrong way
U should have flashed the recovery and system and bootloader manually without nrt
Are able to detect your device via computer in fastboot mode

shivambhai said:
U have done it in wrong way
U should have flashed the recovery and system and bootloader manually without nrt
Are able to detect your device via computer in fastboot mode
Click to expand...
Click to collapse
I used NRT normally as its directed in NRT's thread. Bootloader taken from "JWR66V" was flashed successfully but NRT didnot proceed forward. I powered of the tablet then pressed both volume plus & minus buttons along with power button simultaneously, I read somewhere that pressing all 3 butons is needed to start the bootloader, This resulted in device going in APX mode, although APX mode is activated by holding only vol plus and power button simultaneously. The device seems to be looped in APX i.e. not coming out of it.
It was detectable as a fastboot device earlier but after it went into APX its detected as an "Unknown Apx device" asking for driver, The Asus Transformer Pas driver is installable for it, but i doubt will it work in nvflash.
I jus need a little information about battery removal & nvflash. I have googled about them already but had a couple of queries which I have posted above.
Thanxxxx

Update
Okay last night I attempted battery removal from the device. I took off the back panel of nexus 7 and disconnected the battery cable which is connected to motherboard socket. I reconnected it after 10mins and still no success. I removed it again and connected the device to computer by USB and I found something very strange. the computer detected the Nexus 7 as "Unknown APX Device" even after the battery was disconnected. I was wondering from where is the device drawing power to run? Is it by computer's USB port alone or is there any other power source in nexus7's motherboard like a CMOS cell is present in Computer's MotherBoard which keeps the clock ticking.
Whatever may be the case but it seems that APX Mode is capable of running in minimal power input.
Next test which I performed was to Hold the power button while it was connected to system by USB. After about 7-8secs the device powered off as the computer displayed USB device disconnected message and sound but it repowered on its own in next couple of seconds and again it was detected as "APX device" . Same result observed with simultaneous holding of volume minus+power button as well.
Now I have every reason to believe that device is hard bricked and looped in APX i.e. The Bootloader is corrupted or is not running due to some reason. The device has no option but to go in APX and sit there forever unless its flashed at low level.
I would like to give nvflash a try but i know that theres no1 yet who has made it success and then the only option remaining for me is to visit Asus service center and get some paid service done.
Query - If I visit Asus service center then will they perform software reprogramming i.e. Bootloader fixing or will they replace the hardware ? Incase if they replace the hardware then will they replace the whole board or just the memory unit(which contains Bootloader) from the board?
Experts here please put some light on this

No idea brightheart

Did you have any luck with this BrightHeart? I seem to be in the same boat now...
BrightHeart said:
Okay last night I attempted battery removal from the device. I took off the back panel of nexus 7 and disconnected the battery cable which is connected to motherboard socket. I reconnected it after 10mins and still no success. I removed it again and connected the device to computer by USB and I found something very strange. the computer detected the Nexus 7 as "Unknown APX Device" even after the battery was disconnected. I was wondering from where is the device drawing power to run? Is it by computer's USB port alone or is there any other power source in nexus7's motherboard like a CMOS cell is present in Computer's MotherBoard which keeps the clock ticking.
Whatever may be the case but it seems that APX Mode is capable of running in minimal power input.
Next test which I performed was to Hold the power button while it was connected to system by USB. After about 7-8secs the device powered off as the computer displayed USB device disconnected message and sound but it repowered on its own in next couple of seconds and again it was detected as "APX device" . Same result observed with simultaneous holding of volume minus+power button as well.
Now I have every reason to believe that device is hard bricked and looped in APX i.e. The Bootloader is corrupted or is not running due to some reason. The device has no option but to go in APX and sit there forever unless its flashed at low level.
I would like to give nvflash a try but i know that theres no1 yet who has made it success and then the only option remaining for me is to visit Asus service center and get some paid service done.
Query - If I visit Asus service center then will they perform software reprogramming i.e. Bootloader fixing or will they replace the hardware ? Incase if they replace the hardware then will they replace the whole board or just the memory unit(which contains Bootloader) from the board?
Experts here please put some light on this
Click to expand...
Click to collapse

Same Issue!
seanet1970 said:
Did you have any luck with this BrightHeart? I seem to be in the same boat now...
Click to expand...
Click to collapse
Looks like this problem is quite common and mostly affecting Nexus 7 2012 devices. Mine to got botched after a OTA update. Any possibilities of Google fixing this /RMA beyond warranty ?

[SOLVED] LG G2 D802 can’t unbrick from security error bootloop. PLEASE HELP!

I have international D802 where I have installed a custom rom based on android 4.4.2. Yesterday I wanted to upgrade it to an android 5 rom and and mistakenly installed a new custom rom that was builded for F320S. After reboot only the fastboot mode was displayed. Then I’ve tried to repair the download mode by flash the img files, but as I’ve verified later they was not intended for LG G2 D802 32Gb version. So now if I try to enter either the download mode or the hard reset / recovery I see only the LG logo with security error.
I’ve tried a different button-combinations. Please correct me if it was wrong.
For power off I’ve pressed the power button for about 15 seconds, wait until the logo is displayed then hidden then shortly displayed again and then the display is black.
For hard reset / recovery I’ve pressed press volume down button and power button together until the LG logo appears on the screen. When the LG logo is displayed, un-pressed the power button, but keep pressing the volume down key and then pressed once more the power button. Then the LG logo is displayed again, and then below was the security error displayed.
For download mode, I’ve pressed and hold the volume up button and connected the USB cable. But after some seconds the security error was displayed and the device manager in windows didn’t showed any changes.
Is it possible to recover the phone from the security error state? Any help would be appreciated.
EDIT:
Solved in following steps.
1. Open the phone like described here: LG G2 is UNBRICKABLE NOW!
It was not hard and you don't need any special tools, only a small screw driver. Look first this both videos https://www.youtube.com/watch?v=15krGmydqgQ&feature=youtu.be and http://forum.xda-developers.com/show....php?t=2582142. The do the steps till you can access the processor chip. Ensure the battery is disconnected. By disconnecting the both left and right plates be sure to separate it from the surface.
2. Connect the phone to the PC with USB cable. Open the device manager.
3. Short the test pins on the chips, see the https://www.youtube.com/watch?v=FiofVOqfnxw with e.g. bent paper clip till you'll see the new QHSUSB qualcomm 9006 connection on COM port. Then you'll see a lot of windows messages about to format the new founded partitions. Close them.
4. Flash an images, like laf.img,aboot.img, boot.img from your phone model using export very partition see https://www.youtube.com/watch?v=_d5b_osUTug for details and files.
5. Now the download mode is available. Remove the usb cable, enter the download mode and flash a original stock rom for your model using the LG Flash Tool 2014.
Now your phone is unbricked!
Any questions?

What is the security error on LG G2? Is it a common way to reset some settings to reset it?

Added solution in the first post. If you have any questions, please post.

Ive done till step 3, only one window poped up, and i don't get step 4, i still got the security thing...
Help I guess?

avi57 said:
Ive done till step 3, only one window poped up, and i don't get step 4, i still got the security thing...
Help I guess?
Click to expand...
Click to collapse
You've shorted a wrong pin, please try again step 3 untill you will see the qualcomm 9006 and not 9008 or another number.

Phone stuck at CSC fastboot mode

Hi
I own Asus zenfone max pro m1 & since it started to give occasional issues while accessing either camera or volume buttons, I decided to reset it to factory settings. However soon after I opted for reset option, the phone displayed the msg of "CSC FASTBOOT MODE... LONG PRESS POWER KEY TO SHUTDOWN DEVICE". As instructed on the screen, I did press the power key, however there was no further instructions or activity after that. I tried using the power key again & in combination of volume keys yet I keep getting the same message displayed on the screen.
Kindly help

AjayTawrani said:
Hi
I own Asus zenfone max pro m1 & since it started to give occasional issues while accessing either camera or volume buttons, I decided to reset it to factory settings. However soon after I opted for reset option, the phone displayed the msg of "CSC FASTBOOT MODE... LONG PRESS POWER KEY TO SHUTDOWN DEVICE". As instructed on the screen, I did press the power key, however there was no further instructions or activity after that. I tried using the power key again & in combination of volume keys yet I keep getting the same message displayed on the screen.
Kindly help
Click to expand...
Click to collapse
Go to see service center

I had the same problem using the latest firmware "55" but had a backup on twrp and was just restore that everything went back to normal

100% working Solution for m30s random freezing rebooting stuck at bootlogo.

Hello friends
As many of m30s user reporting random freezing while using and auto reboot on itself or sometime not even turns on by pressing and holding volume down and power key.
I too was mad at this hardware problem
I tried all possible ways like flashing old firmware or using aosp ,lineage os,but nothing was successful
Finally I tried one last method which was randomly tried
But that step unknowingly successful.
I have tested it many times without any previous behaviour.
Please check this link
hopefully it may work for you also.

i there. After (an attempt) to unlock the bootloader of my m30s and installing TWRP Recovery (TWRP_A50_Magisk_Prepatched) i find myself in an orange bootstate. I can't get it into recovery, download or fastboot mode. It seems like a full brick. I can't even power off the device. Only Volume up, Volume down and Power button let's the device reboot but then the same boot problems appear. Is there anything i can do to recover my phone?
Text of first screen when booting up:
"The phone's bootloader is unlocked and it's software integrity can't be verified. Andy data on this phone may be vulnerable to attackers. Don't store any important or sensitive information on this phone". Press power key to continue"
Text of second screen when booting up:
"The phone is not running Samsung's official software. You may have problems with features or security and you won't be able to install software updates"
Any ideas!?

Press and hold volume up and down and Connect to computer with drivers installed.
Flash stock rom using odin tool.

PHONE BRICKED PLEASE HELP

i there. After (an attempt) to unlock the bootloader of my A50 and installing TWRP Recovery (TWRP_A50_Magisk_Prepatched) i find myself in an orange bootstate. I can't get it into recovery, download or fastboot mode. It seems like a full brick. I can't even power off the device. Only Volume up, Volume down and Power button let's the device reboot but then the same boot problems appear. Is there anything i can do to recover my phone?
Text of first screen when booting up:
"The phone's bootloader is unlocked and it's software integrity can't be verified. Andy data on this phone may be vulnerable to attackers. Don't store any important or sensitive information on this phone". Press power key to continue"
Text of second screen when booting up:
"The phone is not running Samsung's official software. You may have problems with features or security and you won't be able to install software updates"
Any ideas!?

TWRP sometimes boots and sometimes the same vol up and power process shows samsung logo screen i need help

okay try this , connect your phone to the laptop or PC and press the volume up button and power button together and once you see Samsung a50 logo come up remove the finger from power button and keep pressing the volume up button till twrp come up and hope fully from there you will get it together and use the phone new
if that dosen't work download the latest firmware of your phone from google and flash it using obin and hopfully it will work
PS you will find plenty of videos how to do it in youtube