Database Users

How to go from VillainRom to Litening or other Custom Rom :)

I noticed a lot of people getting into boot loops after flashing new roms to their phone. I encountered the same issue and this is the method I used to solve it.
Firstly boot into recovery mode by powering off the phone and then rebooting by holding volume up + power + home. Wipe your cache and user data. Then turn off the phone by holding the power button.
Download stock kernel from here for you firmware and flash this via Odin.
To do this, hold volume down + power + home to boot into download mode, press power up to continue when prompted. Then plug in your USB cord.
Now in Odin, select PDA and browse to where you downloaded the kernel to and select it. Make sure you don't change anything in Odin but do make sure Auto Reboot and F.Reset Time are selected (they should be by default). Click start and wait until this is finished.
You should then be able to flash your new rom onto the phone
I'm not sure that this will work for everyone, but this solution worked for me so I thought I would share it

HELP

I was on MALICE rom (JVQ) and i was trying to update to v 4.1.1 with the frameworkres.apk and in the process i had to delete the existing one that i already had with root explorer so i can install the apk that is posted in his thread but i had to reboot and now it will not boot to download mode or recovery mode. I tried all button combinations and all sorts of ways but cannot reboot to anything else. I'm stuck on galaxy s logo. Anybody know how to get to download mode or recovery mode from here or to restore phone to stock??

Did you paste the framework res apk into the system/framework folder? All you had to do has paste it in there. You didnt have to delete anything. And keep trying the button combos or buy a jig.

Same thing happen to me on SH, I kept trying for one hour until it did it. Pull the battery, put it back in, plug phone into pc until you see the charging indicator, then try vol down and power button or both volumes and power. Keep trying that until it boots into recovery.
For d/l mode make sure phone is plugged into pc and its vol. up and power. That should work every time.

The button combo's are different for GB bootloaders. If you can't get into download mode with the button combination you should look into purchasing a jig. Good luck!
*EDIT*
You should probably replace system files, instead of deleting and then moving this way there is one in there at all times. If that makes any sense.

battery out. put battery back in hold volume up and down at the same time continue holding and plus in usb. flash using odin with your pit and pda. if u see a phone with this (!) just plug it in load ur pit and pda and click start on odin. it has worked for me once before

Soft bricked my T280 and so confused!!

I recently updated my Samsung Galaxy Tab A T280 to the latest firmware and I lost my root. So this afternoon I re-rooted it. Or I attempted to, anyway. Everything seemingly went fine, and I booted into TWRP just fine. I went to flash the ROM and I also selected wipe cache/davlik cache to be done as well, and tapped reboot. My device then turned off and when it started the reboot, it got stuck on the Samsung Galaxy Tab A logo screen and would not move or power off by holding the power button (I tried for a LONG time by using a rubber band to hold it down so I didn't have to, with no luck), and every other combination of buttons wouldn't do a thing, except for holding power + vol down, which made it turn off and back on, but it wouldn't finish rebooting and it just got stuck at the Samsung Galaxy Tab A logo again. So then I thought that maybe plugging it into a charger might not be a bad idea, and after holding down power + vol down again, it turned off and turned on and showed a battery with a charging symbol. I've had it plugged in for an hour and it does not show a charge or do anything except for go back to that boot logo if I unplug it from the charger and again hold down power and volume down separately.
I know it's not hard bricked because it is somewhat responsive so I think there's a chance to fix it, hopefully. I just want it to turn on and fully reboot into anything or in any way that will allow me to be able to fix the issue. My computer will not recognize the device so ADB is not an option right now unless I'm wrong.
Thanks a lot guys, I am so confused and could really use some advice.

What firmware did you install

Try to install original firmware via software "Samsung Smart Switch" on your PC with connected tablet.

I too recommend that you try installing the last firmware that you were on via Odin. Also, when you hit that screen lock issue after a firmware flash, where only the Samsung logo appears do this:
1. press and hold Home + volume up and volume down along with power button (that's all 4 buttons). Hold it there for at least 20 seconds and it should power off.
2. Once the device powers off keep holding the buttons but let go of the volume down button.
3. Once the tablet starts to power back up again release the power button and then in about 1 to 2 second release the rest of the buttons.
This should get you back into recovery. You should at least be able to restore any backup, that you should have already, on your external micro SD.
Good luck.. : )
"Chance Favors the Prepared"

the above post is 100% right. Reboot back into recovery and you'll be good to go. Also twrp has a option to reboot back to recovery so this doesn't happen, just a fyi for future knowledge. Best of luck..

You tried to flash a rom with twrp?
You need to flash stock firmware with odin.

Help - Stuck at Samsung Logo - recovery/boot loop

I have S7 Edge Exynos, Marshmallow.
Successfully rooted using CF-autoroot.
Verified rooted using Root Checker.
After rooting, tried to install TWRP via Odin. Disabled the auto-reboot in Odin.
Flashed twrp-3.0.2-2-hero2lte.img.tar in Odin. Got a green PASS! in Odin.
Rebooted phone, no TWRP. Tried to reboot into recovery (TWRP), not successful.
I thought TWRP has been installed, but maybe my key combo is not correct, so I tried another way to reboot into recovery (TWRP) via app. I installed Quick Reboot app from Google Play Store, gave it Root Permission. Pressed "Boot into recovery".
Now the phone is stuck on the Samsung Galaxy S7 Edge logo. I pressed and hold power button - nothing. Pressed and hold Volume Up, Power and Home - nothing. I pressed and hold Volume down, Power and Home, the screen blanks for a short while, then gets stuck at the Samsung S7 Edge logo screen.
I tried connecting the phone to PC and to Odin, device not detected.
What should I do? Please help.

You need to flash via Odin.. than boot into recovery.. flash dm verity and enc.. patch.. otherwise phone wont boot

ManXXXX said:
You need to flash via Odin.. than boot into recovery.. flash dm verity and enc.. patch.. otherwise phone wont boot
Click to expand...
Click to collapse
Thanks for the advice. I'm not sure how to flash via Odin. The phone is currently stuck at Samsung logo. Cant power off, cant reboot. It just stays on at that Samsung logo. When I connect the phone to my laptop, the device is not connected. Odin doesn't detect the phone.

You need to reboot into download mode to flash with odin hold the power and home button and the volume down button for a minute or so them use odin

1. get your phone into download mode. (hold power+home+v.down)
2.once in download mode connect it to your pc
3. go to sammobile.com and find the right firmware for you. (according to phone model)
https://www.sammobile.com/firmwares/search/galaxy s7/
4. once odin shows that your phone is connected with something like : <ID:0/003> Added!! in the log tab and 0:[COM3] above it you're ready to flash.
*I hope that by now your download is ready, and you have a zip file. click to open the zip and extract ONLY the ap file from there.
for me (SM-G935F) the file name is : AP_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship_meta.tar.md5. (notice the AP before the file name).
5. now press the AP button and choose the AP_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship_meta.tar.md5 or whatever you extracted and press start. after that your phone should boot and you'll be good to go.

Eightan said:
1. get your phone into download mode. (hold power+home+v.down)
2.once in download mode connect it to your pc
3. go to sammobile.com and find the right firmware for you. (according to phone model)
https://www.sammobile.com/firmwares/search/galaxy s7/
4. once odin shows that your phone is connected with something like : <ID:0/003> Added!! in the log tab and 0:[COM3] above it you're ready to flash.
*I hope that by now your download is ready, and you have a zip file. click to open the zip and extract ONLY the ap file from there.
for me (SM-G935F) the file name is : AP_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship_meta.tar.md5. (notice the AP before the file name).
5. now press the AP button and choose the AP_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship_meta.tar.md5 or whatever you extracted and press start. after that your phone should boot and you'll be good to go.
Click to expand...
Click to collapse
Thank you very much for the detailed step by step instruction. I followed your instruction and managed to restore the stock rom, and the phone now works normally again. What a relief. You are a life saver!
The hardest thing was to get the phone to boot into download mode, because it just refuses to do so. It just stayed on, stuck at the samsung logo. Pressing down, home and power only make the screen flash briefly, then stuck at the logo again. The phone wont turn off. I had to leave the phone as it is to drain its battery. Once the battery is out of juice, the phone is finally off, then I connect it to PC, and pressed the key combo to enter download mode. After second try I managed to get into download mode. From there I followed the instruction to flash the stock rom again. I wouldnt know to extract and use only the AP file, as the instruction from sam mobile didnt say anything about it. But your detailed instruction did. The phone now works as normal. Thank you again! :good::good:
And thanks the rest who also provided advice in this thread as well. Much appreciated.

kevlarr said:
Thank you very much for the detailed step by step instruction. I followed your instruction and managed to restore the stock rom, and the phone now works normally again. What a relief. You are a life saver!
The hardest thing was to get the phone to boot into download mode, because it just refuses to do so. It just stayed on, stuck at the samsung logo. Pressing down, home and power only make the screen flash briefly, then stuck at the logo again. The phone wont turn off. I had to leave the phone as it is to drain its battery. Once the battery is out of juice, the phone is finally off, then I connect it to PC, and pressed the key combo to enter download mode. After second try I managed to get into download mode. From there I followed the instruction to flash the stock rom again. I wouldnt know to extract and use only the AP file, as the instruction from sam mobile didnt say anything about it. But your detailed instruction did. The phone now works as normal. Thank you again! :good::good:
And thanks the rest who also provided advice in this thread as well. Much appreciated.
Click to expand...
Click to collapse
If it won't boot up to Download mode.. in the future. just leave the combination pressed like for 30sec

ManXXXX said:
If it won't boot up to Download mode.. in the future. just leave the combination pressed like for 30sec
Click to expand...
Click to collapse
I didn't know that. Good info to have. Thanks.

Hi. Something just occurred to me. In sam mobile site, there are like 5 versions of 6.0.1 stock roms. I wasnt sure which ones were mine, so i just chose one. And I only installed the AP file, as per your instruction. Is it okay not to install the rest of the files like the BL, CP etc?
Then later, i decided to try out nougat, and flashed the stock nougat rom from sam mobile, again i only flashed the AP file. I didnt flashes the rest of the files like BL, CP, CSC etc. Is this okay? Or should i flashed all those files too?

[Solved] Moto G4 Plus hard bricked after rooting : won't detect qhsusb

I tried rooting Moto G4 Plus and just after flashing the supersu and rebooting, it got bricked. Nothing shows except LED blink while connecting to PC/charger. Also, it won't detect in the device manager as a qualcomm device/qhsusb bulk or anything... I seriously need your help. Please help.
PS: I surfed over various related threads and all of them required the device to be detected on PC.

1) are you able to power off your device, then hold down the power and volume down keys? Does that boot you into the bootloader?
Or can you hold the power button for 1-2 minutes to force a hard shutdown, then attempt to boot into the bootloader?
2) did you flash a custom kernel before attempting to root? On stock Nougat for our device, you need a custom kernel.

The device is already in the switched off stage. When I press and hold the power button, nothing happens. When connected to USB cable, the front LED blinks. Nothing more. It doesn't return any sound or indication while connecting to PC. I tried installing various Qualcomm drivers to get it detected on PC. The Windows device manager shows nothing.
I tried this tutorial to root my device. I missed flashing the elementalx kernel during the root process. it caused the brick.

technorajeev10 said:
The device is already in the switched off stage. When I press and hold the power button, nothing happens. When connected to USB cable, the front LED blinks. Nothing more. It doesn't return any sound or indication while connecting to PC. I tried installing various Qualcomm drivers to get it detected on PC. The Windows device manager shows nothing.
I tried this tutorial to root my device.
Click to expand...
Click to collapse
That tutorial should work, provided you flashed the ElementalX kernel before rooting.
Hmm, what happens if you try to boot by holding down both the power button and the volume down key at the same time? You should still be able to boot into the bootloader (with the AP fastboot secure mode).
What TWRP and SuperSU did you try to flash?

echo92 said:
That tutorial should work, provided you flashed the ElementalX kernel before rooting.
Hmm, what happens if you try to boot by holding down both the power button and the volume down key at the same time? You should still be able to boot into the bootloader (with the AP fastboot secure mode).
What TWRP and SuperSU did you try to flash?
Click to expand...
Click to collapse
I used twrp and supersu as exactly as mentioned in the root thread (twrp-3.2.1-0-athene.img & phh's supersu).
The key combo doesn't work either. No response. Is there any way to get it detected on PC?
I previously had it happened on my Yureka and I had to short the board to get it detected as a qcomm device.

technorajeev10 said:
I used twrp and supersu as exactly as mentioned in the root thread (twrp-3.2.1-0-athene.img & phh's supersu).
The key combo doesn't work either. No response. Is there any way to get it detected on PC?
I previously had it happened on my Yureka and I had to short the board to get it detected as a qcomm device.
Click to expand...
Click to collapse
That's odd, as that key combo should get you booting to the bootloader (as in the tutorial), which should then get your device detected via fastboot. Did your bootloader look similar to this when you were flashing TWRP?
https://plus.google.com/photos/106899236533864901773/album/6441285188929274337/6441285190332216978
If your device is still on, try a hard shutdown (hold power button 1-2 minutes until shutdown, verify it's off by connecting power, you should see the charging symbol come on), then boot by holding volume down and power at the same time.
You could also try a hard reboot https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/110630/p/30,6720,9687

I just found that the volume down key is broken. I hope that's the reason it won't boot to the bootloader. Let me fix it first and try your suggestion.
And yes, the bootloader menu was the same as shown in this pic.
Thanks a lot for your time bro. Much appreciated.

echo92 said:
That's odd, as that key combo should get you booting to the bootloader (as in the tutorial), which should then get your device detected via fastboot. Did your bootloader look similar to this when you were flashing TWRP?
https://plus.google.com/photos/106899236533864901773/album/6441285188929274337/6441285190332216978
If your device is still on, try a hard shutdown (hold power button 1-2 minutes until shutdown, verify it's off by connecting power, you should see the charging symbol come on), then boot by holding volume down and power at the same time.
You could also try a hard reboot https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/110630/p/30,6720,9687
Click to expand...
Click to collapse
I just disassembled the phone and flipped the volume rockers so that the volume down should work fine. Then pressed and hold vol - & power button. Violaaa. Got into the bootloader. On TWRP, Just wiped data and flashed the ElementalX followed by SuperSU. It's working super fine now. A billion hugs for your support.