Develop Bugs

[Q] Am I bricked?

Please help! I am new to this and am worried I bricked my phone.
I successfully rooted my Verizon Samsung Galaxy Nexus using a toolkit. It was then working fine with 4.2.2. I wanted to install Shiny Rom 4.4.2. I thought I successfully backed up apps and data using Titanium Backup.
I successfully moved the correct zip files to my phone, and realized I needed Clockworkmod recovery. I followed a procedure to get this on my phone by using my computer's command prompt. I successfully booted into Clockworkmod recovery and followed the process of wiping data/factory reset, successfully installed radio and bootloader recommended to install with ShinyROM but got stuck and could not install the ShinyROM itself. I think it is because it requires a later version of Clockworkmod. The one I downloaded using the procedure was 5.5.0.4, but I think I need a later version. I tried following the same procedure using my computer's command prompt and it got stuck at "waiting for device". I cannot get out of Clockworkmod recovery now (even battery pull, etc.). I then found some threads saying I need to restore my old ROM first. (I think) the only ROM on my phone is ShinyROM. I am stuck and stressed out because I do not know of a way of "pushing" the new version of Clockworkmod to my phone.
Can I fix this, or do I need to start shopping?

[email protected] said:
Please help! I am new to this and am worried I bricked my phone.
Can I fix this, or do I need to start shopping?
Click to expand...
Click to collapse
i think u already wiped data partition at first, that why your Rom installation aborted bcoz recovery cant mount any partition.
still got your old system partition here.
from recovery ~ try adb sideload your shinyRom. can your pc detected bootloader (fastboot)/recovery?

memaro_maro said:
i think u already wiped data partition at first, that why your Rom installation aborted bcoz recovery cant mount any partition.
still got your old system partition here.
from recovery ~ try adb sideload your shinyRom. can your pc detected bootloader (fastboot)/recovery?
Click to expand...
Click to collapse
Regarding partition, I have an option to wipe cache partition. Should I do this?
Update
Well, I went ahead and tried this, and still could not install ShinyROM.
I tried to follow a procedure in the link to use ADB sideload.
I downloaded (full) SDK and updates and updated the drivers. When I get to the following steps from the procedure...
-Boot your device in recovery mode (Android logo with a exclamation mark) and connect your device to PC
-Hold down "power" button first, followed quickly by "volume up" button. You should now see the recovery menu
I only boot to CWM and there is no Android with Exclamation mark. Holding down power button only selects whichever option is highlighted within CWM.
Also, it seems within CWM, there is supposed to be an option to sideload a zip file. This option does not exist in my version of CWM.

[email protected] said:
Regarding partition, I have an option to wipe cache partition. Should I do this?
Update
Well, I went ahead and tried this, and still could not install ShinyROM.
I tried to follow a procedure in the link to use ADB sideload.
I downloaded (full) SDK and updates and updated the drivers. When I get to the following steps from the procedure...
-Boot your device in recovery mode (Android logo with a exclamation mark) and connect your device to PC
-Hold down "power" button first, followed quickly by "volume up" button. You should now see the recovery menu
I only boot to CWM and there is no Android with Exclamation mark. Holding down power button only selects whichever option is highlighted within CWM.
Also, it seems within CWM, there is supposed to be an option to sideload a zip file. This option does not exist in my version of CWM.
Click to expand...
Click to collapse
set up fastboot and flash twrp then.

xzilem said:
set up fastboot and flash twrp then.
Click to expand...
Click to collapse
Thanks. I found another thread that led me to the same conclusion, except I was able to do it with CWM and fastboot the latest version using ADB sideload. I still haven't posted enough to link, but here were the details from user camblue.
"
If you know how to use ADB you can always fastboot a recovery.img,,,,this thing is almost impossible to truly brick. IN order to get into fastboot just connect to your computer and run adb with these commands
adb reboot bootloader
once in fastboot mode write this
fastboot devices
that will tell you if your device is connected and reading in fastboot mode if it is you will see something like fastboot and some numbers next to it. If nothing you do not" have the fastboot drivers installed.
then to fastboot flash a recovery.img write this
fastboot flash recovery r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever recovery.img you are using or have in your tools folder of you SDK location).
and in order to get right into CWM if you cant boot write this
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img
hope that helps
"

Phone can't connect to PC at all

When I plug it in into my pc, nothing comes up. I tried going into download mode to download the drivers but it fails everytime. Help please.
Also, here's a little backstory. I accidentally tried installing the new software a month ago when my phone was rooted which caused the phone to be stuck in recovery mode. I fixed this problem by doing this:
"before trying anything else just type in these commands
What worked for me was from the TWRP terminal command was to type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
got help from the IRC xda-devs for the second step to complete the fix."
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
However, now my phone doesn't have recovery mode, but it saids that I'm still rooted. I just want to go back to stock firmware. Please help thank you

Lgg3root.com
Shows a video on how to unroot and go stock stock. Then start fresh
BAD ASS G3

Bricked my LG

We I accept the update to lollipop my phone restart and now is dead...
My phone was a twrp recovery but can't access now... No download mode works...
No screen turn on...
Only my Pc recognize on hardware QHSUSB_BULK
LG TOOLS not reconigce....
Please and help to resurrection my phone...

celtichazard said:
We I accept the update to lollipop my phone restart and now is dead...
My phone was a twrp recovery but can't access now... No download mode works...
No screen turn on...
Only my Pc recognize on hardware QHSUSB_BULK
LG TOOLS not reconigce....
Please and help to resurrection my phone...
Click to expand...
Click to collapse
You can never take an OTA update with a custom recovery. See this thread http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 it may help.

acefsw said:
You can never take an OTA update with a custom recovery. See this thread http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 it may help.
Click to expand...
Click to collapse
My phones don't enter in to download mode screen is turned of all the time

celtichazard said:
My phones don't enter in to download mode screen is turned of all the time
Click to expand...
Click to collapse
its bricked, you have to do some research on what you can do......if anything
never take an OTA if you are not 100% stock

decaturbob said:
its bricked, you have to do some research on what you can do......if anything
never take an OTA if you are not 100% stock
Click to expand...
Click to collapse
all ready do a research all day and no luck to fix

So when the phone is off and you hold the volume up button and plug in the usb it won't go into download mode?

vel0city said:
So when the phone is off and you hold the volume up button and plug in the usb it won't go into download mode?
Click to expand...
Click to collapse
Yeah, I'd at least try a battery pull, have all the drivers/downloads etc. ready for TOT. make sure the usb is plugged in to computer side on a usb 2.0 port, then attempt volume up/plug usb into phone.

If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.

TheCoutures said:
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
Click to expand...
Click to collapse
His screen doesn't turn on, so no TWRP access. He needs download mode or likely a jtag if he can't get that. Battery pull might help or be absolutely useless, especially since his computer is just recognizing the qualcomm chip
Here's some research links celtichazard https://www.google.com/search?q=QHS...458045j0j0&sourceid=chrome&es_sm=122&ie=UTF-8 don't give shady strangers money to unbrick
---------- Post added at 12:35 AM ---------- Previous post was at 12:20 AM ----------
Read this http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853

TheCoutures said:
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
Click to expand...
Click to collapse
Sorry but the phone dot turn the screen thanks

celtichazard said:
Sorry but the phone dot turn the screen thanks
Click to expand...
Click to collapse
Read the links posted above, especially the 2nd one. Also, https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/ is for a one + one phone, not ours, but explains some of what it takes to restore the files for the chipset

acefsw said:
Read the links posted above, especially the 2nd one. Also, https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/ is for a one + one phone, not ours, but explains some of what it takes to restore the files for the chipset
Click to expand...
Click to collapse
Thanks dude but the only problem is I cant find the right driver to make it work
this is my device manager detect whe I plug the phone

Thanks TC the fix worked. Thought I had OTA disabeled

unable to adb reboot recovery reinstall (unable to reinstall twrp)

since this fone was having this issue i decided to try and restore from a working backup:
http://forum.xda-developers.com/g4/help/unable-to-make-phone-calls-dialer-t3278827
i am starting to think that this fones hardware is broken/defective somehow. the key combo to boot into recovery never works.
its supposed to be power+volume-down but it just boots normally.
power+vol-down/release power for 1 second goes into the erase all data: yes/no screen.
whether using android-5.1 or cyanogenmod, adb devices returns nothing; we tried on both windows and fedora; we enabled developer options/adb debugging/oem unlock.
so to test whether the original os could make fone calls i did a twrp wipe/restore of a previous backup. when it booted up it was very unstable/unusable; took a few minutes to respond to touches sometimes; process system has quit errors; random restarts; ...
no apps could launch so that meant i couldnt use quick boot to reboot recovery. adb and key combos dont work so there was no way to get back into recovery.
i put the fone in download mode (volume-up while plugging in usb) and we used LGUP_8994_DLL_Ver_0_0_3_23.msi/LGUP_Store_Frame_Ver_1_14_3.msi to install H81120i_00_0201.kdz which is the lg version of googles version of android-6.0. and we were able to make a fone call. we wanted to boot into twrp to backup but quick boot said that we are no longer rooted. ironically, adb devices now shows the serial-number of the fone so i did sudo adb reboot recovery but when it rebooted instead of going to twrp it showed a green android with a spinning blue cube thingy and rebooted into lg/google-android-6.0 where i had to sign/register for the first time and all our apps/settings were gone.
we origianlly installed twrp using the send_command.exe command on windows awhile back but it no longer works. we installed LGUnitedMobile_Win_Driver_Ver_3.14.1.exe; i run ports.bat and it tells me that the diag port is on COM5; i run Send_command \\.\COM5; it shows me the linux su prompt: #, but when i type in ENTER, it exits back to the windows-dos prompt (i also tried without first typing ENTER, if i try to run something like ls or whoami, it will display: fail).
do all these models have adb/recovery disabled or is this particular unit fubar in that regard ?
any alternative ways to install twrp/ cyanogenmod ?

It is my understanding according to autoprime's thread that you must reinstall twrp after you install the kdz as it wipes that partition as well.

bbenz3 said:
It is my understanding according to autoprime's thread that you must reinstall twrp after you install the kdz as it wipes that partition as well.
Click to expand...
Click to collapse
thanks, how does one install twrp without using send_command.exe.

Flashed the Wrong ROM

Hey guys,
I accidentally flashed the wrong ROM [5.1.1] instead of [6.0.1] on my SM-G925T and now it got stuck on the logo screen with a red message on the top left corner saying Kernel is not SEandroid enforcing.
Any known remedies for fix this issue? My phone still communicates with ODIN and i can get it to download mode but not in recovery. (I had TWRP prior to this issue)
Thanks

Hold Volume Down + Power + Home, this will reboot you to download mode. Press volume down and right after that, hold volume up + power + home. This should bring you back into recovery which I am assuming is TWRP since you are installing a rom. From here you can use ADB to upload a correct custom rom to your device and install it.

Mortifix said:
Hold Volume Down + Power + Home, this will reboot you to download mode. Press volume down and right after that, hold volume up + power + home. This should bring you back into recovery which I am assuming is TWRP since you are installing a rom. From here you can use ADB to upload a correct custom rom to your device and install it.
Click to expand...
Click to collapse
Thanks for your reply. I was able to briefly get it to recovery mode earlier but the phone turned off and never came back since. I am trying to charge it just in case, but it is only showing an empty battery on the screen... How screwed am I?

Minor update, the phone does work and it goes into recovery. Can I install any rom through adb or does it have to be something specific. I wanted to try the one by Mortifix

crematorio said:
Minor update, the phone does work and it goes into recovery. Can I install any rom through adb or does it have to be something specific. I wanted to try the one by Mortifix
Click to expand...
Click to collapse
Yeah it can be any rom. If you install an incorrect rom, your phone will simply not boot. Once you get into TWRP, just go to the Install option and select the zip file. If you are only able to get into recovery, you may be able to transfer the zip from your PC to your phone just by dragging and dropping. This never works for me so I always just use adb push -p "path to the zip on your pc" /sdcard
If you don't have adb setup yet, you can download it from this link: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118

Mortifix said:
Yeah it can be any rom. If you install an incorrect rom, your phone will simply not boot. Once you get into TWRP, just go to the Install option and select the zip file. If you are only able to get into recovery, you may be able to transfer the zip from your PC to your phone just by dragging and dropping. This never works for me so I always just use adb push -p "path to the zip on your pc" /sdcard
If you don't have adb setup yet, you can download it from this link: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Click to expand...
Click to collapse
I installed your ROM through ADB but now it got stuck in a loop through TWRP recovery trying to mount /data and then it restarts again. It looks like it goes directly to the ADB option in TWRP

crematorio said:
I installed your ROM through ADB but now it got stuck in a loop through TWRP recovery trying to mount /data and then it restarts again. It looks like it goes directly to the ADB option in TWRP
Click to expand...
Click to collapse
Hmm, you may need to go to Wipe and do a factory reset. This will wipe cache, system, and data while leaving data/media (/sdcard) intact. After doing this, reboot back into recovery and try to install the rom again.

crematorio said:
I installed your ROM through ADB but now it got stuck in a loop through TWRP recovery trying to mount /data and then it restarts again. It looks like it goes directly to the ADB option in TWRP
Click to expand...
Click to collapse
If you get stuck in a boot loop through TWRP and you can still use TWRP, go to "Advanced" then to "Terminal" and type "reboot"
Good luck!