Need help, stuck on update - LG Q6 Questions & Answers

Hello everyone
Today I went and download some update and then go on and install it but I got stuck on rebooting and update screen.
It gives me that update screen saying 1/2 and after few seconds it goes to boot screen (LG Q6) and then to update screen over and over again. Can I restart it somehow or do anything.
Thanks in advanced

I guess it's better for you to enter the Download mode and reflash the Oreo or Nougat stock ROM via LGUP.
You'll probably lose your data.

CygnusBlack said:
I guess it's better for you to enter the Download mode and reflash the Oreo or Nougat stock ROM via LGUP.
You'll probably lose your data.
Click to expand...
Click to collapse
But the problem is that i cant enter any mode, safe, factory, fast, download or any

alens0nee said:
But the problem is that i cant enter any mode, safe, factory, fast, download or any
Click to expand...
Click to collapse
Then it's warranty time

Related

MATE 7 not booting

Hi, need some urgent help here.
I was trying to install a custom rom, so I unlocked first the bootloader, then flashed twrp 3.0.2 for Android 5.1 and with it I flashed KangVip rom (porto from honor 6).
Problem was it didn't boot, just black screen.
So I supposed the problem was with the rom so I flashed via fastboot the aosp 6, obviously with same results.
I tried lot of stuff (twrp 2.8.x.x, reinstall stock firmware, restore twrp backup of stock full firmware and so on - I did almost everything I could do) and now I'm with a Huge problem: no huawei logo at start, just a white screen and nothing happen. I have twrp 3.0.2 for 5.1 installed right now but I can't install stock recovery.
Please help me, what do I gotta do?
[emoji30]
the ported rom is based on Android 6.0 you have Android 5.1 youk should flash 5.1 based rom..
it's good to flash stock and update official to b560 or b571 depending on which region to have then flash twrp recovery and then flash desire rom..
fazi2015 said:
the ported rom is based on Android 6.0 you have Android 5.1 youk should flash 5.1 based rom..
it's good to flash stock and update official to b560 or b571 depending on which region to have then flash twrp recovery and then flash desire rom..
Click to expand...
Click to collapse
Thx for this.
But I have a problem, I can't install stock recovery and if I try to flash the .img files extracted from update.app nothing happens.
Also, I still have that problem with huawei logo disappeared and a blank white screen instead.
Sent from my HUAWEI GRA-L09 using Tapatalk
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
fazi2015 said:
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
Click to expand...
Click to collapse
Solved, thanks!
Sent from my HUAWEI GRA-L09 using Tapatalk
fazi2015 said:
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
Click to expand...
Click to collapse
Hope you can help me out here...I had just gotten my HAM7 for a couple of days. Was on 4.4.2 B120, was able to get it up to B326. Just yesterday I attempted to flash up to B331 and it succeeded according to the "local update" option. Then it went on boot loop. I tried doing the force 3-button option and that worked to the point of saying it succeeded and will reboot. Now I'm stuck on Ascend Mate logo. I can no longer get into factory option mode (V+Power), only fastboot mode. Also, I can't do force update no more so I can't try any other "update.app" unless I'm missing something here.
Any help in getting this unit at least back to working condition will be a BIG help. I just received this two days ago.
Thx!!!!
jfer671 said:
Hope you can help me out here...I had just gotten my HAM7 for a couple of days. Was on 4.4.2 B120, was able to get it up to B326. Just yesterday I attempted to flash up to B331 and it succeeded according to the "local update" option. Then it went on boot loop. I tried doing the force 3-button option and that worked to the point of saying it succeeded and will reboot. Now I'm stuck on Ascend Mate logo. I can no longer get into factory option mode (V+Power), only fastboot mode. Also, I can't do force update no more so I can't try any other "update.app" unless I'm missing something here.
Any help in getting this unit at least back to working condition will be a BIG help. I just received this two days ago.
Thx!!!!
Click to expand...
Click to collapse
are you have unlock bootloader or not..
fazi2015 said:
are you have unlock bootloader or not..
Click to expand...
Click to collapse
Yes, bootloader is unlocked. FYI, I can't do Vol+ Power or 3-button force. I have no idea what went wrong after the B331 update.app flash. It said successful then boot loop after. I have looked all over the forums and tried everything from flashing C900B300 rollback to try and get 4.4.2 that I started out with, but I really don't know which firmware to start with. The last update.app files I was using was the European variants. Phone was originally locked to Ecuador MoviStar network at B120SP04, then I flashed up to B324 5.1.1. Rooted and then wanted to upgrade to B331 so I unrooted and flashed. Now I'm stuck.
jfer671 said:
Yes, bootloader is unlocked. FYI, I can't do Vol+ Power or 3-button force. I have no idea what went wrong after the B331 update.app flash. It said successful then boot loop after. I have looked all over the forums and tried everything from flashing C900B300 rollback to try and get 4.4.2 that I started out with, but I really don't know which firmware to start with. The last update.app files I was using was the European variants. Phone was originally locked to Ecuador MoviStar network at B120SP04, then I flashed up to B324 5.1.1. Rooted and then wanted to upgrade to B331 so I unrooted and flashed. Now I'm stuck.
Click to expand...
Click to collapse
now you should flash twrp recovery in fastboot mode and then flash a custom rom like kangvip I'll send you link soon...
fazi2015 said:
now you should flash twrp recovery in fastboot mode and then flash a custom rom like kangvip I'll send you link soon...
Click to expand...
Click to collapse
Thank you very much....hope that will solve the boot issue and bring this unit back to life
Alright, so I've given up complete hope that I can get my unit back up and running again. I've tried so many ways already with no success (fastboot/adb, force upgrade, etc.,), and even tried to copy my second HAM7 images (via sdk tools) and to no avail.
The thing I'm trying to understand is where exactly do I start with trying to revive? When I first got this device from eBay, it was apparently still on "MoviStar" Telefonica-Spain network so my network bars showed "R" for roaming. Somehow, I was able to flash it from being on V100R001C00B120SP04a and upgrade to B127>B145>B324 which made me able to use my own service normally. It worked fine and I was even able to root it. Decided to do a last upgrade to B331 and while the local update option showed it as successfully installed, it went into boot loop ever since. Hence, I used European firmwares for most of the flashing. My second mate was on B145 and I was able to get that to B331, which is running fine right now.
ATM, I am ONLY able to do Volume-/Power to get into fastboot.
Doesn't work:
- V+/Power (stock recovery)
- V-+/Power (3-button force)
What works:
- V-/Power with USB for fastboot
*Bootloader is unlocked, but I do believe that after flashing the last firmware of B331, I may have done a factory wipe, which probably reset the USB debugging option as well. So, I'm sure I'm stuck with a device that just might be flashed on the wrong firmware and is factory reset which prevents me from flashing a custom rom or even the stock rom???
Any last advice I would be so thankful for...still waiting on the link for KangVip rom from (fazi2015)
All the best...
jfer671 said:
Alright, so I've given up complete hope that I can get my unit back up and running again. I've tried so many ways already with no success (fastboot/adb, force upgrade, etc.,), and even tried to copy my second HAM7 images (via sdk tools) and to no avail.
The thing I'm trying to understand is where exactly do I start with trying to revive? When I first got this device from eBay, it was apparently still on "MoviStar" Telefonica-Spain network so my network bars showed "R" for roaming. Somehow, I was able to flash it from being on V100R001C00B120SP04a and upgrade to B127>B145>B324 which made me able to use my own service normally. It worked fine and I was even able to root it. Decided to do a last upgrade to B331 and while the local update option showed it as successfully installed, it went into boot loop ever since. Hence, I used European firmwares for most of the flashing. My second mate was on B145 and I was able to get that to B331, which is running fine right now.
ATM, I am ONLY able to do Volume-/Power to get into fastboot.
Doesn't work:
- V+/Power (stock recovery)
- V-+/Power (3-button force)
What works:
- V-/Power with USB for fastboot
*Bootloader is unlocked, but I do believe that after flashing the last firmware of B331, I may have done a factory wipe, which probably reset the USB debugging option as well. So, I'm sure I'm stuck with a device that just might be flashed on the wrong firmware and is factory reset which prevents me from flashing a custom rom or even the stock rom???
Any last advice I would be so thankful for...still waiting on the link for KangVip rom from (fazi2015)
All the best...
Click to expand...
Click to collapse
https://mega.co.nz/#!3N4RzbJY!saB4NY...Ao5goVNiSXAjEc
I am not 100% sure about this rom but you can try it in fastboot you should flash twrp recovery first..
fazi2015 said:
https://mega.co.nz/#!3N4RzbJY!saB4NY...Ao5goVNiSXAjEc
I am not 100% sure about this rom but you can try it in fastboot you should flash twrp recovery first..
Click to expand...
Click to collapse
Unfortunately, it says the file is no longer available
jfer671 said:
Unfortunately, it says the file is no longer available
Click to expand...
Click to collapse
try this all information is here
https://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597
fazi2015 said:
try this all information is here
https://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597
Click to expand...
Click to collapse
Okay, so final result is I'm stuck on a frozen logo now. The twrp bat file again showed success in flashing and rebooted the device, but I'm hung on the "Huawei Ascend" logo. I have to pull the battery to shut it off, otherwise it stays on. So I'm now sure that it's a hard bricked device since I did the stupid thing of factory resetting which probably reset the usb debug...making it almost impossible to flash any firmware now.
Thanks for the help anyways...I really appreciate it. Gonna throw this up on eBay and see if anyone wants it for parts
jfer671 said:
Okay, so final result is I'm stuck on a frozen logo now. The twrp bat file again showed success in flashing and rebooted the device, but I'm hung on the "Huawei Ascend" logo. I have to pull the battery to shut it off, otherwise it stays on. So I'm now sure that it's a hard bricked device since I did the stupid thing of factory resetting which probably reset the usb debug...making it almost impossible to flash any firmware now.
Thanks for the help anyways...I really appreciate it. Gonna throw this up on eBay and see if anyone wants it for parts
Click to expand...
Click to collapse
I know it's annoying but last time I research more and guide you I was have same problem don't give up....
I send you recovery flash in fastboot no need of usb debugging usb debugging need for adb not for fastboot in fastboot flash recovery by your self download it
https://mega.co.nz/#!GRw0CZjQ!iZllDkA6yJeWk7iEA4vEVA94r2nM_YjAuiS8B9IZdm0
then extract the zip go to resource and hold shift and left click then select open command port here then power off device completely boot into fastboot (bootloader) connect the device to pc and in command port type
fastboot flash recovery twrp_2_7.img
after that type
fastboot reboot and hold the volume- button of device it'll boot into recovery if you success then reply..
I've noticed two things when flashing KK or LP. On KK, the phone does a constant boot loop with Huawei logo (on off on off), but on LP the Huawei logo hangs...it doesn't boot loop. Is this an indication or just a fault with both OS?

Bootloop in my S8 Plus, where to download Stock Firmware?

Hi,
I have S8 Plus SM-G955F in Germany.
Dont knwo what exactly happend, but my phone was just still running fine (bootloader is unlocked) and I rebooted but then was stuck at "Installing system updates" screen which appear before getting into recovery. However, it does not enter into recovery and reboots after few seconds into "installing updates" mode which then fails.
It does not boot up into Android.
All I can access to is Download Mode.
I flashed "BL_G955FXXU1AQF7_CL11544126_QB13847503_REV00_user_low_ship.tar" Bootloader and rebooted and now it is stuck in Samsung boot logo. If I press Vol up + Bixpy Button + Power nothing happends, it does not even start to load Recovery mode.
I now downloaded following stock firmware through SamFirm: "SM-G955F_1_20171214140840_hlcm4r582t_fac.zip.enc4" (3332 MB)
but when trying to flash it in odin I get FAILED !!! Also if I try to flash TWRP recovery "twrp-3.1.0-1-dream2lte.img" I get FAILED in Odin I now also tried to flash "AP_G955FXXU1AQH3_CL12050265_QB14545623_REV00" firmware using this tutorial: https://www.youtube.com/watch?v=2y0ZZxcNVnE which also FAILED. I think I am completely bricked !!
Please help, phone is completeley useless now
Thanks!
tobyffm said:
SM-G955F_1_20171214140840_hlcm4r582t_fac.zip.enc4" (3332 MB)
Click to expand...
Click to collapse
I had the same problem with downloading stock firmware. My problem was that I couldn't download from SamMobile because of server maintenance. So I downloaded from here. An with this tool there's the option to decrypt the file automatically. I forgot to tick this option and had a .enc4-file like you have there. The problem could decrypt this file and then I could unzip it and use it with odin.
So that's your problem: you are trying to use an encrypted file. But you have to use an decrypted file.
Maltonator said:
I had the same problem with downloading stock firmware. My problem was that I couldn't download from SamMobile because of server maintenance. So I downloaded from here. An with this tool there's the option to decrypt the file automatically. I forgot to tick this option and had a .enc4-file like you have there. The problem could decrypt this file and then I could unzip it and use it with odin.
So that's your problem: you are trying to use an encrypted file. But you have to use an decrypted file.
Click to expand...
Click to collapse
Hi,
thank you! But its actually not my problem. Samfirm decrypted and I got the zip with the BL, AP, CSC, CP files in it. But ODIN fails everytime anyway and I have no idea what I could still do now.
tobyffm said:
Hi,
thank you! But its actually not my problem. Samfirm decrypted and I got the zip with the BL, AP, CSC, CP files in it. But ODIN fails everytime anyway and I have no idea what I could still do now.
Click to expand...
Click to collapse
But you flashed all four files at the same run together?
Maltonator said:
But you flashed all four files at the same run together?
Click to expand...
Click to collapse
Yes, like the howto video described.
tobyffm said:
Dont knwo what exactly happend, but my phone was just still running fine (bootloader is unlocked) and I rebooted but then was stuck at "Installing system updates" screen which appear before getting into recovery.
Click to expand...
Click to collapse
But this happens with my phone to if I press volume up.
tobyffm said:
If I press Vol up + Bixpy Button + Power nothing happends, it does not even start to load Recovery mode.
Click to expand...
Click to collapse
But you have to press Vol down
Maltonator said:
But this happens with my phone to if I press volume up.
But you have to press Vol down
Click to expand...
Click to collapse
Usual behaviour was this: Vol up, bixpy and Power -> Recovery mode which fist starts with "Installing update..." then failed and then it goes into some black recovery mode where you can choose Apply update.zip etc. right? However, in my case this black screen with more commands did not show up, before it was rebooting again by itself.
Now I cannot even get into this "installing updates" mode before recovery, because "Vol up, bixpy and Power" does not bring any action.
Vol down, Bixpy and Power still works and brings me to Download Mode. But it doesnt help me, because once I tr to flash any firmware in Download Mode, it FAILS in Odin, so I am completely stuck, hope you understand
tobyffm said:
Usual behaviour was this: Vol up, bixpy and Power -> Recovery mode which fist starts with "Installing update..." then failed and then it goes into some black recovery mode where you can choose Apply update.zip etc. right? However, in my case this black screen with more commands did not show up, before it was rebooting again by itself.
Now I cannot even get into this "installing updates" mode before recovery, because "Vol up, bixpy and Power" does not bring any action.
Click to expand...
Click to collapse
But why do you boot in recovery mode?
tobyffm said:
Vol down, Bixpy and Power still works and brings me to Download Mode. But it doesnt help me, because once I tr to flash any firmware in Download Mode, it FAILS in Odin, so I am completely stuck, hope you understand
Click to expand...
Click to collapse
Download mode is the only mode you need for restoring stock firmware.
Try this guide. (Spoiler "Flashing Standard Firmware:")
Yesterday I did it with this one too and it worked flawlessly. But I used Odin v3.12.3 not as said in the guide V3.12.7.
Maltonator said:
But why do you boot in recovery mode?
Download mode is the only mode you need for restoring stock firmware.
Try this guide. (Spoiler "Flashing Standard Firmware:")
Yesterday I did it with this one too and it worked flawlessly. But I used Odin v3.12.3 not as said in the guide V3.12.7.
Click to expand...
Click to collapse
it automatically loaded into recovery before, I was not able to boot into Android, it loaded recovery (but without black screen with more commands) automatically by default and rebooted, loaded recovery again and rebooted, loaded recovery againd and rebooted etc...all I could to to interrupt this was loading download mode.
However, thanks for the link, but it does describe what I did already. And yes, I also used Odin 3.12.3 already because in the video tutorial I linked some posts before they said also, I need to use that version.
However, it simply does not work. Odin FAILS everytime
I am not doing anything wrong, I am sure. The only thing could be that the Firmware I downloaded is still wrong, even I cannot imagine this.
tobyffm said:
I am not doing anything wrong, I am sure. The only thing could be that the Firmware I downloaded is still wrong, even I cannot imagine this.
Click to expand...
Click to collapse
Yes that's the only thing that comes on my mind too if you think everything else is right. Download another firmware file maybe from a different provider than SamMobile.
Or try using different USB-Port, USB-Cable and/or different PC.
Maltonator said:
Yes that's the only thing that comes on my mind too if you think everything else is right. Download another firmware file maybe from a different provider than SamMobile.
Or try using different USB-Port, USB-Cable and/or different PC.
Click to expand...
Click to collapse
Did already, did not help. I think maybe there is something realldy bricked, so flashing stock firmware wont be possible at all anymore?! Is this possible somehow?
btw: Just managed to load into TWRP, randomly it does load twrp, dont know how, because if I press the keys for loading into recovery, it actually does not do anything, but currently I see twrp.
Is see anything I can try from there? btw: formated data (incl. internal storage) earlier already, but it did not change anything.
But any idea what I can try to flash from TWRP maybe? Is there a way to flash stock firmware from TWRP somehow?
I found a backup in twrp, I am currently trying to restore it...
tobyffm said:
But any idea what I can try to flash from TWRP maybe? Is there a way to flash stock firmware from TWRP somehow?
I found a backup in twrp, I am currently trying to restore it...
Click to expand...
Click to collapse
Google found this. But I don't know if this works. I only flashed custom ROMs via TWRP. Stock ROMs always via Odin.
Maltonator said:
Google found this. But I don't know if this works. I only flashed custom ROMs via TWRP. Stock ROMs always via Odin.
Click to expand...
Click to collapse
Puuuuh, I was able to fix phone with hat TWRP backup I found!
Thanks for your efforts anyway, much appreciated!
tobyffm said:
Puuuuh, I was able to fix phone with hat TWRP backup I found!
Thanks for your efforts anyway, much appreciated!
Click to expand...
Click to collapse
Glad it worked! :good:
tobyffm said:
it automatically loaded into recovery before, I was not able to boot into Android, it loaded recovery (but without black screen with more commands) automatically by default and rebooted, loaded recovery again and rebooted, loaded recovery againd and rebooted etc...all I could to to interrupt this was loading download mode.
However, thanks for the link, but it does describe what I did already. And yes, I also used Odin 3.12.3 already because in the video tutorial I linked some posts before they said also, I need to use that version.
However, it simply does not work. Odin FAILS everytime
I am not doing anything wrong, I am sure. The only thing could be that the Firmware I downloaded is still wrong, even I cannot imagine this.
Click to expand...
Click to collapse
My mistake, sorry - I posted in the wrong place- sorry. (I do hope you find a way to get t his fixed) good luck
I just ran into this thread: https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
It looks like you're not the only one...
You know, you might want to try and remove the more current apps you installed and see if that is causing the loop, and if that does not work, just dirty flash over what you have. For me, a lot of time a dirty flash will solve the issue, as it overwrites the OEM software, and in that manner, takes my phone OS back to normal/new state, while leaving my data.

J4 plus (J415GB) bricked

Is there anyone here facing same with my situation? today i bricked my J4 plus, Dunno if its hard bricked or soft brick, I can't enter to download mode and system restore anymore. Im just trying to get oreo back because i fell little laggy on my current os (pie). I went to samsung service center and they told to use JTAG to get it fix but its too expensive for me to pay hundreds buck for this.
Thank you
its not bricked. your battery is full drained. i had the same problem and how i fixed!!! i presed all 3 buttons and put usb cable to my pc and my phone. it goes like bootloop starts and shuts. you will wait with pressed buttons from 5 to 10 mins depend how low is your battery. and finaly will go to download mode and you can flash it then!!!
Bricked my J4+
Can someone help me with a bricked J4+?
I wanted to install TWRP, I followed the guide to the letter on how to install TWRP.
After successfully flashing TWRP 3.2.3-0 and flashing RMM bypass zip (without booting to the OS) I also performed a Wipe Cache in TWRP.
I booted to the Samsung OS and the system overall felt laggy.
I performed a Factory Reset, still the system felt laggy.
I decided to use Odin and install the Samsung factory system (thus go back to Samsung OS).
I booted successfully and decided to give TWRP 3.2.3-0 another chance.
Odin resulted in FAIL when trying to flash with the following error: Can't open the specified file (line: 1892)
I tried different versions of Odin (from last to previous ones), different USB ports, I even tried another PC but no success.
I performed another factory reset and now the phone is hard bricked I guess because it will power on...try to get in stock recovery and Erase...and then power off. I can't get to download mode or stock recovery.
Any help I would highly appreciate it.
Thanks.
FL0R1AN said:
Can someone help me with a bricked J4+?
I wanted to install TWRP, I followed the guide to the letter on how to install TWRP.
After successfully flashing TWRP 3.2.3-0 and flashing RMM bypass zip (without booting to the OS) I also performed a Wipe Cache in TWRP.
I booted to the Samsung OS and the system overall felt laggy.
I performed a Factory Reset, still the system felt laggy.
I decided to use Odin and install the Samsung factory system (thus go back to Samsung OS).
I booted successfully and decided to give TWRP 3.2.3-0 another chance.
Odin resulted in FAIL when trying to flash with the following error: Can't open the specified file (line: 1892)
I tried different versions of Odin (from last to previous ones), different USB ports, I even tried another PC but no success.
I performed another factory reset and now the phone is hard bricked I guess because it will power on...try to get in stock recovery and Erase...and then power off. I can't get to download mode or stock recovery.
Any help I would highly appreciate it.
Thanks.
Click to expand...
Click to collapse
you didnt follow guide from letter to letter. is obviuosly you didnt do all you need to do. if you in pie update you need to flash twrp (you did) then NEED to format data(go to wipe choose format data(not wipe data,cache) write yes and swipe to format data.this step is important.then go to recovery again and flash pie patched boot.img and oreo enforcing.zip,then RMM bypass,and then you can do boot up your device.thanks.
rudi021 said:
you didnt follow guide from letter to letter. is obviuosly you didnt do all you need to do. if you in pie update you need to flash twrp (you did) then NEED to format data(go to wipe choose format data(not wipe data,cache) write yes and swipe to format data.this step is important.then go to recovery again and flash pie patched boot.img and oreo enforcing.zip,then RMM bypass,and then you can do boot up your device.thanks.
Click to expand...
Click to collapse
The part where I had to format the data...I have missed that. Thanks for pointing it out.
I took the phone to a repair shop because it is hard bricked and it needs jtag to unbrick it.
As soon as I have it back I will try again to install TWRP.
Thanks for the help, I appreciate it.
FL0R1AN said:
The part where I had to format the data...I have missed that. Thanks for pointing it out.
I took the phone to a repair shop because it is hard bricked and it needs jtag to unbrick it.
As soon as I have it back I will try again to install TWRP.
Thanks for the help, I appreciate it.
Click to expand...
Click to collapse
no need to thanks.btw if your device is unlocked you cant be bricked.just flash firmware you want and thats it.btw your device must be unlock to do this stuff(twrp,gsi,etc....) btw you can have read my guide for flashing gsi on samsung j4+.https://forum.xda-developers.com/galaxy-j4+/how-to/how-to-flash-gsi-genericsystemimage-to-t3942554.
if you have any question be free to ask.i will help you if i can.
rudi021 said:
no need to thanks.btw if your device is unlocked you cant be bricked.just flash firmware you want and thats it.btw your device must be unlock to do this stuff(twrp,gsi,etc....) btw you can have read my guide for flashing gsi on samsung j4+.https://forum.xda-developers.com/galaxy-j4+/how-to/how-to-flash-gsi-genericsystemimage-to-t3942554.
if you have any question be free to ask.i will help you if i can.
Click to expand...
Click to collapse
This is a phone from work and I did toggle EOM unlock and USB debugging in order to flash TWRP.
I did not enter any password, face unlock, pattern or sign in to google....nothing of the sort. As soon as I opened the phone from the box tried to install TWRP knowing it will erase everything after TWRP installation. I really hate Samsung UI and wanted to try Lineage OS or another custom ROM which is not laggy like ONE UI.
After installing TWRP the phone became very laggy (obviously I did not perform a format data...my bad) I did use Odin and flashed the corresponding firmware of the phone and it did that successfully.
I tried to give TWRP another shot by flashing it again but I was getting a FAIL in Odin with the following error: Can't open the specified file (line: 1892)
After this I tried to flash again the same Samsung firmware but kept getting the same FAIL and the same error: Can't open the specified file (line: 1892)
I have tried all versions of Odin but the same FAIL and same error.
Now I can't even get into Download mode or Samsung recovery mode.
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately.
As soon as I get the phone I will check your link on XDA and try a GSI ROM.
Which one do you recommend...this is a work phone, all I care about is speed and fluidity and it has to be a daily driver.
FL0R1AN said:
This is a phone from work and I did toggle EOM unlock and USB debugging in order to flash TWRP.
I did not enter any password, face unlock, pattern or sign in to google....nothing of the sort. As soon as I opened the phone from the box tried to install TWRP knowing it will erase everything after TWRP installation. I really hate Samsung UI and wanted to try Lineage OS or another custom ROM which is not laggy like ONE UI.
After installing TWRP the phone became very laggy (obviously I did not perform a format data...my bad) I did use Odin and flashed the corresponding firmware of the phone and it did that successfully.
I tried to give TWRP another shot by flashing it again but I was getting a FAIL in Odin with the following error: Can't open the specified file (line: 1892)
After this I tried to flash again the same Samsung firmware but kept getting the same FAIL and the same error: Can't open the specified file (line: 1892)
I have tried all versions of Odin but the same FAIL and same error.
Now I can't even get into Download mode or Samsung recovery mode.
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately.
As soon as I get the phone I will check your link on XDA and try a GSI ROM.
Which one do you recommend...this is a work phone, all I care about is speed and fluidity and it has to be a daily driver.
Click to expand...
Click to collapse
1. two possible mistake. 1.after you try flash firmware dont check user data,just check AP,BL,CP,CSC and flash firmware.2.no need to try old odin. all new firmware is work on new odin.just need to know what to checked to flash. about gsi all is good but i like Havoc OS, Lineage OS 16, RR,almost all.again you are welcome to ask help if you want.:good:
rudi021 said:
1. two possible mistake. 1.after you try flash firmware dont check user data,just check AP,BL,CP,CSC and flash firmware.2.no need to try old odin. all new firmware is work on new odin.just need to know what to checked to flash. about gsi all is good but i like Havoc OS, Lineage OS 16, RR,almost all.again you are welcome to ask help if you want.:good:
Click to expand...
Click to collapse
Hmmm I did check USER DATA. So that bricked my device. Thanks for letting me know.
FL0R1AN said:
Hmmm I did check USER DATA. So that bricked my device. Thanks for letting me know.
Click to expand...
Click to collapse
yeeeahhh. i am knowing that in hard way. you can check user data only if you have ORIGINAL firmware and not rooted phone(mean twrp),if you have rooted(twrp) then flash with or without user data. some firmwares on web can flash with user data, some cant.anyway as i say you can always ask for help.i will gladly help if i can. good luck.
rudi021 said:
yeeeahhh. i am knowing that in hard way. you can check user data only if you have ORIGINAL firmware and not rooted phone(mean twrp),if you have rooted(twrp) then flash with or without user data. some firmwares on web can flash with user data, some cant.anyway as i say you can always ask for help.i will gladly help if i can. good luck.
Click to expand...
Click to collapse
Thanks. I will wait for the phone to be unbricked and then will try TWRP again.
Can i install gsi rom if the phone is in oneui?
FL0R1AN said:
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately .
Click to expand...
Click to collapse
What you're describing are symptoms of a flat battery and a direct boot to recovery.
To boot to download mode plug in the USB cable first then hold vol up, vol down and power until download mode appears.
There is absolutely no way TWRP caused the lag. TWRP runs in its own minimal OS environment and has no effect on a booted android OS whatsoever.
Lastly your device wasn't hard bricked, a device that powers on even if it doesn't boot is only soft bricked.
Usually recoverable using the right procedure.
ashyx said:
What you're describing are symptoms of a flat battery and a direct boot to recovery.
To boot to download mode plug in the USB cable first then hold vol up, vol down and power until download mode appears.
There is absolutely no way TWRP caused the lag. TWRP runs in its own minimal OS environment and has no effect on a booted android OS whatsoever.
Lastly your device wasn't hard bricked, a device that powers on even if it doesn't boot is only soft bricked.
Usually recoverable using the right procedure.
Click to expand...
Click to collapse
I managed to boot into the Revovery and perform a factory reset, now the phone booted normally.
I will try and install TWRP.
When these strange things happened the device had over 80% battery...at least that's what it showed on screen.
Now I see that indeed it was flat 0% and you were right to point out that this is a flat battery problem.
Thanks for the help I really appreciate it.
FL0R1AN said:
I managed to boot into the Revovery and perform a factory reset, now the phone booted normally.
I will try and install TWRP.
When these strange things happened the device had over 80% battery...at least that's what it showed on screen.
Now I see that indeed it was flat 0% and you were right to point out that this is a flat battery problem.
Thanks for the help I really appreciate it.
Click to expand...
Click to collapse
well like i told you it is not problem of twrp.but as senior member ashyx told in answer today device cant be hard bricked.just flash firmware and device will boot as normal. btw keep battery full
rudi021 said:
well like i told you it is not problem of twrp.but as senior member ashyx told in answer today device cant be hard bricked.just flash firmware and device will boot as normal. btw keep battery full
Click to expand...
Click to collapse
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
FL0R1AN said:
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
Click to expand...
Click to collapse
install twrp(in odin option uncheck Auto Reboot) ,format data reboot to recovery,flash oreo enforcing.zip,flash RMM,flash magisk(newest) then reboot.
rudi021 said:
install twrp,format data,flash oreo enforcing.zip,flash RMM,flash magisk(newest) then reboot.
Click to expand...
Click to collapse
Got it, Thanks.
FL0R1AN said:
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
Click to expand...
Click to collapse
It's correct, but if you want access to the data partition in twrp you need to also install the encryption patch.
You will also need to either install magisk or some other patch that disables dmverity.
ashyx said:
It's correct, but if you want access to the data partition in twrp you need to also install the encryption patch.
You will also need to either install magisk or some other patch that disables dmverity.
Click to expand...
Click to collapse
Got it, Thanks

I soft bricked my over a year ago and would like to get it working again.

From what I remember it had TWRP on it, I had it rooted on stock image for a while. Got absolutely fed up with their software and tried to install a stock android rom on it. Got through a few that wouldn't load properly so went to go back to a stock rom and it's stuck in a bootloop now. I've never been able to get into recovery no matter what button combo. It goes to the yellow text page then reboots. Not matter what combo of buttons i push.
Not really sure what to look for or what to do beyond this point as most help i've found has been guided to get into recovery. The most I've been able to get is this basically a downward facing parentheses with a small circle that appears and runs through it.
Can you get into fastboot? - Turn it off, connect USB and hold power and vol -
If yes, its easy to fix. Or you can try going to eRecovery and Format all data and download latest software.
Just tried. That would be a yes.
bump.
Did you fix it or you still need help? If yes, what version of android were you using? Do you have an sd card you can use to install stock firmware?
The point is, we need to get you running on oreo, after that is everything ez. There is probably no way of getting oreo other way than using hisuite, but I dont know. For hisuite. To make hisuite show oreo update, you need to get latest nougat running on your phone. It should be ez with twrp. You can use firmware finder on windows or other phone to download proper full ota update and flash trough twrp. If anything, feel free to ask me here.
Still stuck at the fastboot option. I don't really remember what version it was. Whatever it was exactly 1 year ago is all I can remember. I don't think it was oreo though?
I can't use TWRP though, as I said, I can't get into any recovery stock or TWRP, only fastboot.
delete
Spykez0129 said:
Still stuck at the fastboot option. I don't really remember what version it was. Whatever it was exactly 1 year ago is all I can remember. I don't think it was oreo though?
I can't use TWRP though, as I said, I can't get into any recovery stock or TWRP, only fastboot.
Click to expand...
Click to collapse
Did you tried Dload? It should work. Download latest nougat for your device from firmware finder and flash it with Dload.
EDIT: If fastboot works, just download latest twrp for nougat and flash it. After that just downlaod stock nougat and flash trough twrp.
PremiumBlaze said:
Are you able to flash anything in fastboot like the stock recovery?
Does fastboot say that the phone is unlocked?
Does fastboot say that FRP is unlocked?
Click to expand...
Click to collapse
Says both are unlocked. I flashed the latest recovery (for nougat) to it and both said ok.
Then I did fastboot reboot recovery command and it says OKAY on the sending, but under "booting" it says FAILED. Command not allowed?
Can't manually boot into twrp either, phone stays stuck on your device is booting now.
delete

Samsung A30s stuck at bootloader After TWRP !

Hello all,
I own a Samsung a30s and decided to root it via magisk, all worked well until I decided to get TWRP on it.
I flashed TWRP via the app and it let me flash through it as my phone was already rooted.
After it had flashed, I restarted my phone and tried to go to recovery, but the phone just turned off, it won't get up, I tried to force restart it by holding down the VOLUME DOWN + POWER button. It turns on, shows the logo, and then shuts down again.
Cant go to download mode as well
HELP NEEDED!!!
Reflash phone's Stock ROM to get rid off of all modifications you applied so far.
jwoegerbauer said:
Reflash phone's Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
Cant even get into recovery or download mode to reflash
Take it to authorized service center and let them try to fix it.
samibull001 said:
Cant even get into recovery or download mode to reflash
Click to expand...
Click to collapse
Wait until the battery is fully discharged
Or open the back cover and disconnect the battery and then plug it in again
Try booting the device to download mode afterwards

Categories

Resources