Frp lock, stock rom doesn't boot - General Questions and Answers

I used lineage 16 on Galaxy A3 2017 for several weeks without problems. Suddenly when trying to connect to a stored WiFi, nothing happened. Hit reboot to try reconnecting and got into bootloop due to FRP lock. No access to system or recovery possible.
After flashing stock firmware with Odin, stuck at the blinking Samsung logo, so still no access to system. Flashing TWRP fails too due to FRP lock.
An ideas how I can restore the OS, or any OS whatsoever?

Additional info after some more experimenting: Even fastboot is not working at all.
- In recovery, adb finds the device (however, only sideload mode, which is no help here). Fastboot does not.
- In bootloader, neither adb nor fastboot list the device. (Flashing with Odin works, obviously, but is no help since original firmware doesn't boot and TWRP fails due to FRP lock.)
- When stuck at the flashing Samsung logo on system reboot, the phone is recognized by the computer. But again, neither adb nor fastboot list the device.
A lot of dead ends and no more options for me to explore after hours of unsuccessful web-searching. Any help is appreciated, as I am this close to buying an iphone, which is something I promised myself I would never do

bart753 said:
Additional info after some more experimenting: Even fastboot is not working at all.
- In recovery, adb finds the device (however, only sideload mode, which is no help here). Fastboot does not.
- In bootloader, neither adb nor fastboot list the device. (Flashing with Odin works, obviously, but is no help since original firmware doesn't boot and TWRP fails due to FRP lock.)
- When stuck at the flashing Samsung logo on system reboot, the phone is recognized by the computer. But again, neither adb nor fastboot list the device.
A lot of dead ends and no more options for me to explore after hours of unsuccessful web-searching. Any help is appreciated, as I am this close to buying an iphone, which is something I promised myself I would never do
Click to expand...
Click to collapse
Fastboot isn't working because Samsung does not support fastboot.
The XDA rules prevent us from helping you or anyone else in finding a way to bypass FRP lock. It is pointless to ask your question here.
I wish you luck, but we can't help you. Your only options are:
1) remember the original Google email and password.
2) keep searching the internet to find your own method.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Fastboot isn't working because Samsung does not support fastboot.
The XDA rules prevent us from helping you or anyone else in finding a way to bypass FRP lock. It is pointless to ask your question here.
I wish you luck, but we can't help you. Your only options are:
1) remember the original Google email and password.
2) keep searching the internet to find your own method.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I would not need to bypass the FRP lock, if I could just boot into system. I know the email and password for the Google account. I just have no means of entering it. The main problem is my phone stuck in bootloop even after flashing the original firmware.

Did some more experimenting and it's getting weirder by the hour.
- Newer versions of the original firmware (downloaded from Sammobile) all fail at flashing "hidden.img". Reverting to older versions is now blocked.
- Tried the newest versions of all available vendors, every single one fails at hidden.img.
- Many reports of other users having this problem, all seem to be solved by removing hidden.img from the CSC archive and packing it again.
- I can flash the firmwares without hidden.img, but again get stuck in the same bootloop at the flashing Samsung logo.
- Flashing the hidden.img alone in AP slot after the rest of the firmware also fails.
- Found no more help online as all threads end after removing the hidden.img.

bart753 said:
Did some more experimenting and it's getting weirder by the hour.
- Newer versions of the original firmware (downloaded from Sammobile) all fail at flashing "hidden.img". Reverting to older versions is now blocked.
- Tried the newest versions of all available vendors, every single one fails at hidden.img.
- Many reports of other users having this problem, all seem to be solved by removing hidden.img from the CSC archive and packing it again.
- I can flash the firmwares without hidden.img, but again get stuck in the same bootloop at the flashing Samsung logo.
- Flashing the hidden.img alone in AP slot after the rest of the firmware also fails.
- Found no more help online as all threads end after removing the hidden.img.
Click to expand...
Click to collapse
After flashing the stock firmware, if it bootloop, boot into stock recovery and factory reset the device then wipe the cache partition then reboot and see if you still bootloop.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
After flashing the stock firmware, if it bootloop, boot into stock recovery and factory reset the device then wipe the cache partition then reboot and see if you still bootloop.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I just performed those exact steps, bootloop still continues...
Edit: It actually did finally boot after waiting quite some more. (I was just so used to seeing the flashing logo that I didn't believe it possible.)
Not sure which part I was missing before, but somehow it worked now. Thanks man!

bart753 said:
I just performed those exact steps, bootloop still continues...
Edit: It actually did finally boot after waiting quite some more. (I was just so used to seeing the flashing logo that I didn't believe it possible.)
Not sure which part I was missing before, but somehow it worked now. Thanks man!
Click to expand...
Click to collapse
It can take up to an hour when booting for the first time after flashing a new system.
You were probably getting a bootloop due to the user data stored on the device conflicting with the new system. Factory resetting and wiping cache removes the conflicting data and allows the device to boot. Flashing via Odin does not wipe the data from the device during the flashing process unless the firmware being flashed has an upgraded/downgraded bootloader. If the bootloader is the same as the bootloader already on the device, it does not wipe the device during flashing.
Sent from my SM-S767VL using Tapatalk

Related

[Q] RAZR HD system corrupt after flash.

Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
ShiningRaven said:
Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.
tzlot said:
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.
Click to expand...
Click to collapse
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.
ShiningRaven said:
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.
Click to expand...
Click to collapse
Can you get back into fastboot now? If so
Use fastboot to flash a custom recovery (CWM, TWRP or OUDHS)
use the recovery to factory reset, wipe cache/dalvic, AND format system (sometimes in the advanced menu)
then flash rom of your choice.
If you can't get fastboot working you'll need smarter help than I can give you... but the format system step clears out all kinds of gremlins.
I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.
ShiningRaven said:
I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.[/QUOTE
If you can get into fastboot then you should be able to unlock b/l with this toolkit I used it and it worked for me you can also flash rom with it its in the orginial development thread
http://forum.xda-developers.com/showthread.php?t=2154995
Click to expand...
Click to collapse
ShiningRaven said:
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Had the same problem after a fastboot via the utility. Try powering your phone down completely and leaving it off for about 5-10 min. This can be tricky with the hardware buttons so if you have access to TWRP that will help as it has a power off option. You might also try flashing again via the utility. I believe that's what I had to do, but the power down method is what a friend suggested based of his experience with the same exact problem you documented.
FIXED!!!
OK first I want to thank everybody who responded. I got tied up with work and kind of forgot about this project for a few days.
Repeated uses of the Utility and RSD both left me stuck with the phone freezing every time it tried to load the system into memory.
I had checked out the toolbox before but I didn't think I could do much from a locked bootloader.
After your suggestion jmcdonald I tried it again. It says my device isn't available to be unlocked so I tried downgrading back to ICS.
The toolbox says that it failed but it must have fixed something because the phone booted back up to android 4.1.2 stock!
So far I have bricked a lot of phones and learned a lot about ADB in the process of fixing them but I've never had one I was so certain was bricked permanently. But now it seems to be working fine, I'm scared to try rebooting in now.
Definatly going to unlock the bootloader pronto.
Thanks again jmcdonald!

[Q] Stuck at Samsung logo during boot even on stock rom

I have soft bricked and then recovered a lot of devices but this one has me stumped. I tried to install a custom kernel that I compiled myself using odin. When that didn't work I tried to copy the image using dd. My theory is that I wrote to the wrong block device and broke something. When it wouldn't boot I figured it was no big deal, I'll just revert to stock. I have tried flashing the stock rom with Odin and by using Kies emergency recovery. Both seem to succeed but whenever I boot I just get stuck at the samsung logo which displays on the screen forever. I can still get into download mode and recovery mode just fine.
Things I have tried:
- Factory reset (I've done this many times from stock recovery and TWRP)
- Cache wipe (Also tried several times from stock recover and TWRP - in TWRP I tried all the different wiping options)
- Flash stock ROM
- Turn off device and wait for more than an hour (since there is no way to do a battery pull)
My understanding is that the bootloader must be functioning otherwise I would not be able to get as far as I do. And since flashing stock ROM doesn't do anything there must be a partition with corrupt data that is not being rewritten when I install the ROM. Any ideas what this might be? Are there any resources I can use to completely repartition the device?
Any ideas are appreciated.
I fixed my problem so I just though I'd post the solution here in case someone finds this on Google or something.
It seems that I did indeed corrupt a partition that is not rewritten when you flash a stock rom or do an emergency system restore with kies (which I believe does nothing more than download the stock rom and then flash it). I actually had to buy a second device and use dd to copy over all the partitions and then returned the second device
So if you have this problem you might have to ask someone on this forum to give you an image of whichever partition you broke.

IT WAS THE FINAL STEP... and it did not work. (Stuck on boot loader warning screen)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.
I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you
I have almost the same problem as if the fastboot not install anything despite not display errors
great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.
do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.

Oem locked, frp block, and drk help

Hey guys. I'm in a hell of a bind and could use some help.
My Galaxy Note 5 (N920T, rooted) was running fine on this ROM: https://forum.xda-developers.com/tm...m-qc6-lite-rom-bloated-knoxed-odexed-t3598686 ; however, I had disabled OEM unlock at one point to try and fix a random app I was playing with. The battery died not long after, causing the phone to reboot. On power, it failed to boot due to custom binary block from FRP, so I decided to try and run the usual troubleshooting of flashing a stock ROM via Odin. Stock images will flash (tried 5.1.1, 6.1, and 7); however, when they try to install I get the error for no DRK. Sometimes I'll also get a dm-verity error as well... So I then tried to flash TWRP or any recovery via Odin to let me fix this issue; however, any custom recoveries I try to flash are being blocked by FRP.
So, I'm in a loop. I can't use my initial ROM because FRP, however I also can't install a stock ROM because of missing DRK, AND I can't fix the DRK or verity errors because I can't install a recovery capable of doing so because of FRP.
IMEI is intact when I look into Download mode, but I can't seem to get anything to work. I've tried the FRP Tool and crack, but that gives me FRP blocks as well (USERDATA).
Am I boned?
B U M P
Anyone?
same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*
You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.
Metabolic12 said:
You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.
Click to expand...
Click to collapse
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.
x24veggie said:
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.
Click to expand...
Click to collapse
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.
craig198 said:
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.
Click to expand...
Click to collapse
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP
craig198 said:
same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*
Click to expand...
Click to collapse
No. It started because you didn't back up your phone properly with twrp before going flash crazy
---------- Post added at 08:52 AM ---------- Previous post was at 08:47 AM ----------
x24veggie said:
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP
Click to expand...
Click to collapse
https://www.google.ca/amp/s/forum.x...to-solve-dm-verity-verification-t3293306/amp/ have you tried this? If we can figure this out please don't ever play with oem or have a stock recovery ? that's your security blanket

[Bricked] One of the harder ones =|

I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Whole story:
This whole episode began when I wanted to install Magisk to use MagiskManager's HideMe feature. This required me to install TWRP recovery which inturn lead me to unlock my bootloader in the process, straightforward and went off nicely. Now it was time to gain superuser which I already had done before on another device, installing SuperSU through TWRP recovery was painless but after booting found out MagiskManager needs Magisk Root to work. I then followed Android Exlpained's article to do so. Running unSU through recovery went smoothly but running Magisk didn't, on the initial run I was prompted to use Adrian DC's BootBridge which after removing a few Assert lines ran nicely. However there was no root install, SuperSU was removed though.
At the time I wasn't sure what exactly I was doing and ended up soft-bricking by flash boot through TWRP, at this time FRP was unlocked. After many many hours I restored to stock firmware by using YMNDLZ's guide. I used BLN-L24C567B370(OTA-MF-FULL) for the img files then proceed to flash the vendor.img using TWRP and the rest (boot.img, recovery.img, system.img) using fastboot in that order as instructed. The only part which didn't work was the forced update, it always failed at 5% however after more hours going recovery mode (now stock) wiping the cache and data/factory reset did the trick (Note: my model showed BLN-L24C567B369). I proceeded to reinstall TWRP, installed MagiskManager, tried to install Magisk 16.0 which ran but didn't root me but was fine because MagiskManager's download worked. I then thought since I went through all this trouble might as well install a custom rom, EliteRom was my ROM of choice. At this point I had logged in with my gmail credentials FRP was now locked.
*Before further action was taken I took the precaution to backup my current stable stock ROM after installing EliteROM but before booting*
The steps to install EliteROM went by flawlessly, installed EliteTWRP reboot into it, ran EliteROM
went through the setup without any hiccups. However up system restart I the ROM wouldn't boot leading me to boot into my recovery only to be prompted for an encryption password (???). Since I didn't recall setting one, couldn't boot into the OS, and FRP was locked I couldn't read my own internal storage. So I reformatted the internal storage and tried what had worked before, flashing the img files using TWRP then booting into stock recovery wiping cache and data/hard reset. . . this did not work. And here I am FRP locked so fastboot isn't useful (I think?), stock recovery doesn't work, eRecovery fails connection, and force update still fails at 5% with "Software install failed!".
Click to expand...
Click to collapse
Lemme know if there is any insight anyone can provide and thanks in advance.
This problem has been solved?
MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
you have to follow only xda methods to root or change to custom rom. i have never heard about flashing stock images from twrp. i think u didn't followed elite rom instructions clearly. you need to formate data then reboot to recovery then wipe everything then flash the os in this way you won't get encription error. anyway now your frp is locked so there is no way to flash twrp so download all the available firmwares for your phone oeminfo then do flashing via dload you will get it worked.
even i was also once stuck with elite rom. i didn't liked it because missing apps icon and forgetting permission. i tried to go back to stock but stuck at 5% error. then went to google searched stock rom for honor 6x india and downloaded nearly 3 roms last one worked helped me to get back to stock.
never flash system images boot,vendor etc from fastboot and twrp unless you are on emui8 and going to try gsi roms.
hey i cant revert back to stock rom. it fails to get package from server. does jio voice calling works on this device?? if no then plz guide me how to go back to stock rom..
MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
Register for update using firmware finder and Puts dns address in the router settings and then use erecovery

Categories

Resources