Hi all,
I am stuck at stock recovery. Can anybody help me to restore stock ROM?
Here is the story:
After I root GTAB manually according to that thread http://forum.xda-developers.com/showthread.php?t=859712, I tried to apply the GPS trick explained @ http://forum.xda-developers.com/showthread.php?t=922692
Actually instead of using root explorer to place the files, I tried to replace files in zip file manually(via adb). It looks like something was wrong and device doesn't boot normally anymore. It just reboots to recovery instead. In addition, adb still founds device during recovery but "adb shell" gives an error saying link error. I assume "sh" binary was depending on one of the files I modified.
So, is there an instruction to restore stock ROM on the device.
My current recovery screen says:
Android System Recovery 3e
Samsung Recovery Utils
for BML
- Reboot System
- apply sdcard: update.zip
- wipe data /factory ...
- wipe cache
...
Installing Multi-CSC
All information related to flashing/recovering a device at recovery can be found at
http://www.thegalaxytabforum.com/in...flashing-euro-firmware-on-samsung-galaxy-tab/
I also had to use trick mentioned at that thread to get rid of blank screen after first boot:
http://forum.xda-developers.com/showthread.php?t=899196
Thanks everybody!
Hello,
I have an issue with my brand new G6.
It is in a loop "Your device is corrupt it cannot be trusted and will not boot" , no more recovery available.
What i did:
I unlocked the bootloader and flashed Magisk via TWRP the device displayed that the partition was corrupt and need to be erased.
After that the device was in a loop to twrp, whatever the wipe or ... no system boot.
I read that i had to format the data partition so i adapted a what i found here to my available partitions
https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
the device is now in a constant loop.
Does someone can help me please ?
is there any way to recover it ? download mode ? how ?
Update : I succeed to boot into download mode but LGUP gives me an error while trying to flash
error 0x2000 ... ... cefs::initialize()
docizoc said:
Hello,
I have an issue with my brand new G6.
It is in a loop "Your device is corrupt it cannot be trusted and will not boot" , no more recovery available.
What i did:
I unlocked the bootloader and flashed Magisk via TWRP the device displayed that the partition was corrupt and need to be erased.
After that the device was in a loop to twrp, whatever the wipe or ... no system boot.
I read that i had to format the data partition so i adapted a what i found here to my available partitions
https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
the device is now in a constant loop.
Does someone can help me please ?
is there any way to recover it ? download mode ? how ?
Update : I succeed to boot into download mode but LGUP gives me an error while trying to flash
error 0x2000 ... ... cefs::initialize()
Click to expand...
Click to collapse
Can you boot to TWRP?
Did you make a backup and have access to it? Especially the EFS partition? If you do, restore the EFS partition.
If you can boot to TWRP, try the following:
- wipe everything (the option where you have to type 'yes').
- download lineageOS and flash it. If this is working fine, install whatever ROM you want to install.
no access to twrp anymore , no backup , only access to download mode now
is there a way to flash back twrp or stock recovery from download mode ? boot into fastboot ?
(i know... i have no excuses , but made that so many times without issues ...)
thank you in advance
Maybe you should go in download mode and flash stock Rom with LGUP.
LGUP gives me an error while trying to flash the rom error 0x2000 ... ... cefs::initialize()
Can you flash twrp through lgup or fastboot?
For those that could be in the same situation i finally succeed to flash with LGUP last version but without the 8894DLL
the error was probably coming from the dll.
Cheers and thanks all for the answers
docizoc said:
LGUP gives me an error while trying to flash the rom error 0x2000 ... ... cefs::initialize()
Click to expand...
Click to collapse
It's probably a problem with the DLL, try to extract it from the kdz and input it in Lgup folder (I don't remember where and I'm not home, check the main thread for that) and after that retry flashing
EDIT : well you were faster than my phone glad it worked for you.
moms zenfone 5 lte decided to brick itself during an update, it will just stay on the asus logo loading forever.
I tried re-flashing the boot and reovery images worked but didn't do anything towards fixing the boot process.
it will still boot into fastboot flash mode and sd card recovery modes.
attempting todo anything in sd recovery mode spits out multiple errors about not being able to mount the /cache partition (wiping cache, flashing from external card etc)
can't really do much in fastboot mode because the device is not "unlocked" (need to boot OS enable usb debugging and pair with the PC to do anything for "security" hate whoever came up with that)
seems unlocking the bootloader for TWRP and wipe/format the cache via comamnds are not options because of above?
found an unbrick thread but says it dosn't work un zenfone 5 LTE
been trying a few hours kind of stuck and looking for solutions.
any suggestions please ?
Thanks
ps:sorry meant to post this thread in the help section
seems it may be fixable using asus flash tool and flashing a raw image but I am unable to find a raw image for the A500KL model
"sbl1 partition doesn't exist" on Galaxy S5 (SM-G900F) hardware or software failure?
Hi,
I'd appreciate your help on the following problem with a Galaxy S5 (SM-G900F). I bought this phone recently (rather cheap) from some seller of overstock items with the intention of flashing Lineage 15.1 on it and using it as my main phone.
Even before any changes to the system, the phone went off after a couple of minutes, and instead of a reboot, it displayed the following text in the top left corner (without showing the usual "Samsung Galaxy S5 - powered by android" boot splash):
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS
sbl1 partition doesn't exist
ODIN MODE
PRODUCT NAME: SM-G900F
Current binary: Samsung Official
System Status: Custom
REACTIVATION LOCK (KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREF: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC Start
Pressing the power button for 5sec then rebooted the phone as usual, and the existing Android (some 5.x??) worked okay. I think this happened twice within an hour.
Well, I thought this was a software issue and as I wanted to reflash the S5 anyway, I didn't care and went straight to installing Lineage 15.1 (20180709 nightly). I did it as follows.
1. Boot into download mode (Home+Power+Volume Down)
2. Use heimdall v1.4.2 (on my Linux PC, compiled from source) to upload TWRP 3.2.2 to the phone
3. Reboot into recovery (Home+Power+Volume Up) and use TWRP to wipe dalvik cache, cache, system, and data partitions
4. Use adb push on my PC in order to copy the Lineage and the addon-su zip files to /sdcard/
5. In TWRP, install the two zip files, then reboot the phone
The phone went up with Lineage 15.1 as intended, but there are still two major errors:
A) After a couple of minutes, the phone spontaneously reboots.
B) Sometimes it reboots into lineage, but sometime it hangs in "BOOT RECOVERY MODE" with a message similar to the one above. Not surprisingly, these two lines have changed:
Code:
CURRENT BINARY: Custom
...
KNOX WARRANTY VOID: 0x1 (0)
Now I need to find out whether this is a hardware failure or a software problem.
When you google "sbl1 partition deosn't exist", you do find a number of similar error reports for different versions of the Galaxy S5. Usually, someone recommends to flash "a better ROM" to the device, but I never saw any confirmation that this solved the problem. If it did, I'd be interested to know *which* ROM solved the problem. From my experience, I doubt it is as easy as that.
Can anyone recommend a specific build of Lineage 14.1, 15.0 or 15.1 that is know to be rock solid on the SM-G900F so that I can rule out that the involuntary reboots are a lineage problem?
I know Linux quite well (on x86 and amd64). What is the partition "sbl1" and on which device is it located? Is it on the internal 16GB flash? I am worried that failing to find that partition sometimes, but not always points to a hardware error when reading from the internal flash. How do I find out whether that's the case?
Although the box I received was still sealed (you can fix that, can't you?), I don't want to rule out that the seller had already flashed or at least updated the S5 after all these years of collecting dust on the shelf. Is there any chance that they messed it up and left a corrupt partition table or corrupt main boot loader? How can I tell and how can I fix that?
Thanks a lot for your help,
Gloria13
Have you tried repairing the partitions in twrp , my old moto g2 would get stuck on bootlogo and not boot and checking partitions in twrp solved it ,I recently got this used s5 from my uncle and I am running aex 5.7 rom on it and it works good maybe you could try it and see if it helps .
AsopExtended ROM -https://forum.xda-developers.com/galaxy-s5/unified-development/rom-aospextended-rom-v5-4-t3779910
gloria13 said:
What is the partition "sbl1" and on which device is it located? Is it on the internal 16GB flash? I am worried that failing to find that partition sometimes, but not always points to a hardware error when reading from the internal flash. How do I find out whether that's the case?
Click to expand...
Click to collapse
SBL stands for Secondary BootLoader, a part of the phone's firmware.
It's located in the sbl partition on the EMMC device and is booted by PBL (Primary BootLoader) wich is located in the SoC's ROM.
In it's turn, SBL boots aboot (application bootloader) which next boots recovery or boot.img (kernel).
SBL provides Odin mode, as far as I know.
The phone will not work without SBL.
Than was the theory. The practice is that S5's EMMCs get broken quite often.
I'd suggest installing "Dummy file generator" app from the market to test the memory.
Run it and try to fill all memory and see if it crashes.
If you run out of memory just clean the app's cache.
But if the app craches, I'd suggest sending the phone back or looking for a new motherboard.
bbsc said:
SBL stands for Secondary BootLoader, a part of the phone's firmware.
Click to expand...
Click to collapse
Thanks! I did some background reading on the Android/Samsung boot procedure. I understand that the PBL is most likely contained in some ROM (that's where the ARM CPU jumps right after a reset). But the SBL is located in a regular partition X on the internal flash memory /dev/mmcblk0pX/. After SBL apparently there follows "aboot" and only then the boot sequence that's know from the Linux desktop, begins by loading a kernel and initial ramdisk from the partition that's mounted at /boot.
I know that the recovery tools such as TWRP can essentially flash arbitrary content to /boot (e.g. in order to replace the kernel and initial ramdisk). But is it possible to use TWRP in order to access the data of the sbl1 and aboot partitions? Can I verify that the partition table and the binary contents of sbl1 and aboot are identical to the factory settings of the SM-G900F? Since the common flashing activity begins only at a later stage at /boot, every one of us still ought to have the same sbl1 and aboot on their devices, no? I there a way I can verify and compare that content?
Kind regards,
Gloria13
gloria13 said:
Since the common flashing activity begins only at a later stage at /boot, every one of us still ought to have the same sbl1 and aboot on their devices, no? I there a way I can verify and compare that content?
Click to expand...
Click to collapse
This verification is not needed because sbl and aboot are digitally signed and PBL keeps the public key in the ROM
But this periodical bug is a problem and I'd check the memory.
bbsc said:
This verification is not needed because sbl and aboot are digitally signed and PBL keeps the public key in the ROM
But this periodical bug is a problem and I'd check the memory.
Click to expand...
Click to collapse
I see. So I can rule out any data corruption, but quite obviously I do need to worry about read errors from the internal flash memory.
It seems my only option is to return the phone because of defect internal flash memory.
Regards,
Gloria13
gloria13 said:
I see. So I can rule out any data corruption, but quite obviously I do need to worry about read errors from the internal flash memory.
It seems my only option is to return the phone because of defect internal flash memory.
Click to expand...
Click to collapse
Exactly.
I've had an S5 with defective EMMC. And pulling a large file from it (say, 100-200 MB) gave different results every time (I was checking md5 of that file).
I'd return this phone if it costs more than $40.
Hey everyone!
While trying to update LineageOS on my G6 I somewhat messed up and now am out of ideas. I tried to install an OTA update, which sent me into a TWRP-bootloop. I tried to fix this by using the dd-commands described here before seeing the next post, which advised against it and recommended a different one. Unfortunately too late. I did back up both partitions on my external SD card, though.
Since then the phone is in a boot loop continuously displaying this screen (the author of this thread seemed to have a similar problem - but it wasn't resolved there). I can get into fastboot and download mode with the volume buttons. Getting into the reset-menu and trying to open TWRP from there doesn't work, it just goes back to boot-looping.
Do you have any ideas how to recover from this situation? Ideally without a factory reset... although I have most of my data backed up the storage is encrypted and It would be awesome to recover into the old system. I still have a little hope left that I haven't messed up quite that bad. :/
Thank you!
your data is lost because you can not do anything anymore
make full wipe with fastboot because LGUP currently update supports
fastboot format userdata
fastboot format cache
fastboot format system
go into download mode and flash stock with uppercut and LGUP do you get errors check drivers or take another stock rom. !!! you can not flash a US Stock rom to a EU Model (this was an example !) !!! watching exact your model [H870/H872/US997] and rom
For me it has worked successfully H870 with 20c open EU