Database Info

No Recovery, garbled screen, can I recover?

I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks

Did you wipe before restore?

davebugyi said:
Did you wipe before restore?
Click to expand...
Click to collapse
Yes, I did a full wipe including dalvik cache before all restores. At this point, though, my primary concern is just finding a path back to usability!

DIncLover said:
I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks
Click to expand...
Click to collapse
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..

bruuuno said:
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..
Click to expand...
Click to collapse
I can try this when I get home today.... I'm just concerned because the method involves nvflash .... which I thought didn't work from the newer TF models (I have a model B80). I needed to wait for the RazorClaw exploit because previous attempts at using nvflash failed....

Then NVFlash will fail still...

davebugyi said:
Then NVFlash will fail still...
Click to expand...
Click to collapse
So am I hopelessly hosed?

Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.

baseballfanz said:
Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.
Click to expand...
Click to collapse
OK .... my bad.... I guess I wasn't pressing the buttons in the right sequence/duration. I CAN get to CWM!
So, once again, I try to restore the Nandroid backup and after rebooting, end up with the screen situation as in the reference you provided.
So, I am assuming my Nandroid backup is not restoring the kernel that it needs. I was running a recent OTA update; I believe the version was 8.6.5.19.
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?

DIncLover said:
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?
Click to expand...
Click to collapse
Look here
http://www.gnufabio.com/revolver/dls/

Same issue, no recovery though
Hi,
I have the same issue as the original poster, B80 serial, RazorClaw root. However, when I boot to recovery I get the green android with yellow triangle and exclamation mark.
I need to restore a recovery on my device as I may need to unroot to send to Asus. I have an even deeper problem of having to have the device connected to power for it to turn on after shut down.
However my main question is for that serial number and root method, what is the best way to flash a recovery on my device (stock or CWM) if I can not get into recovery to begin with?
P.S. RecoveryInstaller will not work, after installing the apk, I click the flash recovery button, the system holds for a bit, then nothing happens.
I will continue to search the forms for some answers, any insights or direction will be appreciated.
I can get into apx mode.
Thank you community!

I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?

gee one said:
I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?
Click to expand...
Click to collapse
Everything I see in the forms requires one of several conditions which my TF doesn't currently meet.
1. Recovery. I can not go into any recovery, thus I can not perform any flashing of any other rom or recovery.
2. B70 or later. Because of the security in the boot for these new serials, I can not use the NVFlash tools to un-brick / flash.
I am already rooted, however I do not know the reason for lack of recovery on this device. I unfortunately bought it yesterday from Craigslist, so not sure what this guy did before I got it.
I searched for flashing recovery staging partition and did not find anything immediately relevant. Please advice is there is a different wording I should use in my search as I am now getting an immense download on all of this trying to figure out what to do. I am also fairly new to Android devices having 1 other phone that is rooted.
Thank you for all the support and quick response! wonderful community here.

Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision

gee one said:
Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Thank you gee one. I have since been able to install clockworkmod. My issue with the power not turning on if not plugged in still persists, I have started a separate thread.
I found your post on the staging partition here:
http://forum.xda-developers.com/showthread.php?t=1309949&highlight=power
Do you recommend this for the issue still persisting?
If so, considering I am on 8.6.5.19 will I have to use the blob from that? It is not on Asus website as I got it from the firmware update option in the settings before loading up my new ROM.
Do you recommend this step as the only resolution or is there another way?

Ok let me get this straight:
You have clockworkmod installed. Can you boot into it and do the buttons work?
Are you getting a garbled screen when you boot into the rom? Or are you just trying to unroot?
The tricky part is to avoid the bootloops of death.
sent from my cyanogen(mod) vision

Honestly what i would do if i were you, assuming i understood correctly that you can get into clockworkmod, just reflash the prime rom you didnt like(after wiping everything, including cache and dalvik), and if it boots and everythings okay, at least you know nothings really wrong with ur tablet. As for the plug in situation, make sure your battery isnt simply dead. As far as i know, it wont charge from recovery, so if uve been stuck without a booting rom for a while, it being dead could definitely be possible. Once you are in a working rom and you sorted out the charging issue, then you should worry about getting back to stock.

Thank you camaros,
I am able to load stock ROM successfully.
Battery is not dead as it is fully charged, and will run un tethered after powerup. I will test resetting it although I doubt that is causing it.
What i would like to determine is, is this related to a hardware or software issue?
Also, is there a way to restore stock recovery from CWM?

[Q] Yet Another Potential Brick

Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You

coltp10 said:
Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You
Click to expand...
Click to collapse
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?

cr1960 said:
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?
Click to expand...
Click to collapse
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on

coltp10 said:
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on
Click to expand...
Click to collapse
Sadly based on my knowledge and experience(I learned this the hard way by taking the ATT OTA) if the led doesn't come on while charging and you cant access your bootloader your phone is sadly dead. However you can double check to see if its your cord and if it is not then call HTC if device is still under warranty. They replaced the internals of mine and recieved it back at no charge.
If I have helped in any way hit the Thanks button please.

Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.

redpoint73 said:
Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.
Click to expand...
Click to collapse
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue. So i figured that i would just flash over TWRP and use mount to usb as a second shot. I will have to try and leave it plugged in later after work. Yes the ROM that i installed was for the EVITA, it was running fine except the wifi wouldnt turn on.

coltp10 said:
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue.
Click to expand...
Click to collapse
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.

redpoint73 said:
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.
Click to expand...
Click to collapse
Okay thanks for the input i will check it out as soon as I am able

When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash

coltp10 said:
When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash
Click to expand...
Click to collapse
After holding the power button down and let the capacitive keys flash 6 times. The 6 flashes means a hard reset and it's about to start rebooting. Let go of the power button and immediately hold volume down. It should take you into the bootloader. Then you can fastboot flash TWRP.
Sent from my HTC One X using Tapatalk 2

Thank you
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!

coltp10 said:
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!
Click to expand...
Click to collapse
Good luck
Sent from my HTC One X using xda premium

Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks

coltp10 said:
Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks
Click to expand...
Click to collapse
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.

pside15 said:
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.
Click to expand...
Click to collapse
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?

coltp10 said:
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?
Click to expand...
Click to collapse
because the rom you flashed is based on CM so it was compatible enough to boot but not have everything working as it should. if you don't flash the boot.img, the previously used kernel would still be used.

The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen

coltp10 said:
The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen
Click to expand...
Click to collapse
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.

exad said:
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.
Click to expand...
Click to collapse
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up

coltp10 said:
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up
Click to expand...
Click to collapse
You can also use the flash image GUI app to flash a boot image in Android right before you boot to recovery to flash the ROM. But I would definitely look into s-off. It's a very easy process and then you don't ever have to worry about the boot.img at all.

Phone broken because of TWRP change file system

I used a video on youtube to install TWRP on my galaxy s7 (SM-G930F)
Almost everything worked fine, except I was not able to make a backup. I got the error "Unable to Mount /data". A lot of videos told me that I need to 1. wipe 2. advanced 3. change filesystem 4..exFat and then EXT4. I tried this method, but TWRP froze after some time during the exFAT change process. Now my phone tries to boot into recovery mode, but won't go further than the very first screen of TWRP (where you see the version number and the logo).
What should I do now? I tried to reflash TWRP, but it still doesn't go past the very first screen. I am also not able to turn off my phone, because it keeps rebooting into recovery mode. I think that I need to find a way to change my filesystem to EXT4, but I cant do that with TWRP.
Can somebody help me plz (and sorry for my bad English)

press vol down + home button + power button to boot into download mode and reflash stock rom.
download rom from here https://www.sammobile.com/firmwares/

arodim said:
press vol down + home button + power button to boot into download mode and reflash stock rom.
download rom from here
I just tried this, but it does not work.
Odin says that thread has successfully flashed all the files. My phone is installing the software update and erasing, but after that the screen is black. I cant boot the device or even enter recovery mode (download mode still work). I tried both flashing CSC and HOME_CSC, but both didnt work.
What should I do now?
Click to expand...
Click to collapse

Did you fix your problem?, literally this happen to m, but when I try to flash stock rom with odin just failed and not install nothing.

mrNEEDHELP said:
I used a video on youtube to install TWRP on my galaxy s7 (SM-G930F)
Almost everything worked fine, except I was not able to make a backup. I got the error "Unable to Mount /data". A lot of videos told me that I need to 1. wipe 2. advanced 3. change filesystem 4..exFat and then EXT4. I tried this method, but TWRP froze after some time during the exFAT change process. Now my phone tries to boot into recovery mode, but won't go further than the very first screen of TWRP (where you see the version number and the logo).
What should I do now? I tried to reflash TWRP, but it still doesn't go past the very first screen. I am also not able to turn off my phone, because it keeps rebooting into recovery mode. I think that I need to find a way to change my filesystem to EXT4, but I cant do that with TWRP.
Can somebody help me plz (and sorry for my bad English)
Click to expand...
Click to collapse
The same thing happened to me. Keep trying to access the TWRP even if it takes a bit longer than an hour it will enter. You do not have to do anything else, just keep trying, when you access, you'll be able to repair the partitions, change them to fat32 instead of exfat, and then return to EXT4. It will work.

j0shyc0re said:
Did you fix your problem?, literally this happen to m, but when I try to flash stock rom with odin just failed and not install nothing.
Click to expand...
Click to collapse
What phone do you have?
What network are you using?
What country are you in?
What firmware are you trying to flash?

cooltt said:
What phone do you have?
What network are you using?
What country are you in?
What firmware are you trying to flash?
Click to expand...
Click to collapse
Actually, I was flashing an los ROM shock, I flash the newest ROM, And it works. S7 Flat g930f Android 8 february 2019 update. Thanks anyway.

k1w3l said:
The same thing happened to me. Keep trying to access the TWRP even if it takes a bit longer than an hour it will enter. You do not have to do anything else, just keep trying, when you access, you'll be able to repair the partitions, change them to fat32 instead of exfat, and then return to EXT4. It will work.
Click to expand...
Click to collapse
Had a feeling that this would work, but really didn't had the time to wait. Have wasted €20 to fix it, but still thanks for the reply (even if you are a few months late )
Hope this will help out other people who have the same problem

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 need help. I relocked my bootloader, and now my phone (OP7P) won't even turn on

So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work

gotdiamonds99 said:
So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work
Click to expand...
Click to collapse
U probably should have flashed stock firmware before relocking the bootloader

As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.

cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
OK here's the order. Boot into twrp, don't flash.
Wipe -> ADVANCED -- select system + vendor -> SWIPE TO WIPE
reboot bootloader
fastboot boot back into twrp
-- then --
Format data, Wipe cache & dalvik-cache
Flash ROM.
Then reboot system. Boom.
Remember you will most likely have to flash the ROM via sideload. As transferring will not work in a bricked phone.

cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root

Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Damn forgot about that. Yeah In that case its most likely bricked to hell OP with no method of recovery as far as I know.