Related
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Chegger said:
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Click to expand...
Click to collapse
Not the solution, but maybe a cause... did you root your device?
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
harddisk_wp said:
Not the solution, but maybe a cause... did you root your device?
Click to expand...
Click to collapse
Yes I did.
I also thought that was the problem.
delox88 said:
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
Click to expand...
Click to collapse
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Chegger said:
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Click to expand...
Click to collapse
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
harddisk_wp said:
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
Click to expand...
Click to collapse
At least you know this stuff that's half way trough.
I will post this in the original root thread since I already posted the issue there and they are now replying ( I will mention you).
http://forum.xda-developers.com/general/rooting-roms/root-achieved-cat-b15q-t2822015/page11
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've witten you a PM - please send me your original ROM - or could you send me a link where i may download it.
huedlrick said:
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
Click to expand...
Click to collapse
Another one here! Were you able to use link2sd after rooting the phone? Link2sd gave me a mount error when I tried to mount my sd card's 2nd ext3 partition.
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile
1.1019.000 Recovery
Original 1.1019.000 update
Scatter file
To flash the phone you only need the bootimg, recovery,android and scatterfile.
(Edit: I dont have google drive anymore)
bigal1337 said:
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile https : // drive . google . com /file/d/0ByVAMsMZdC8bdEIxWlpBeXBHNUE/view?usp=sharing
1.1019.000 Recovery https : // drive . google . com /file/d/0ByVAMsMZdC8bVXU2RzBGalV0S1U/view?usp=sharing
Original 1.1019.000 update https : // drive . google . com /file/d/0ByVAMsMZdC8bbWQ4dmhSZWVxZVE/view?usp=sharing
Scatter file https : // drive . google . com /file/d/0ByVAMsMZdC8bSkRhREEwakNhUWc/view?usp=sharing
To flash the phone you only need the bootimg, recovery,android and scatterfile.
Click to expand...
Click to collapse
Thank you very much - but how can I determine if my phone is E01/B01 without being able to boot it?
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Great and congrats.
Could you, please, describe the process and which files did you use.
Thanks.
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Can you give some hints how you unbricked it? What tools and commands have to be entered?
Best regards,
Doggy77
Uploads are not done yet. But you can prepare until I'm done... grab the driver package, spFlashTool and the 1.022 RAR from http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774.
You will need a win7 x86 machine for this to work (64-bit systems will need to disable the driver signature enforcement, but this is unreliable), and latest(!) WinRAR for unpacking.
The full backup of your device will take up ~1.5 GB, so you will need at least 3GB free and another 2GB if you also want to backup your userdata (HIGHLY RECOMMENDED).
"PMT changed for the ROM; it must be downloaded"
I'm trying to flash the files of harddisk_wp with his instructions but i keep getting the error "PMT changed for the ROM; it must be downloaded", right after I connect the phone and SP Flash Tool finishes "Download DA". I am trying with the 64bit drivers since I do not have a 32bit system, with digital signature verification disabled.
After some search, I saw in the log files that SP Flash Tool is reading the partition table on the phone and comparing it to the scatter file. There is a mismatch there and throws this exception. Now either the driver is not working correct and does not report the partition table right or there is something else going on. Anybody tried this on a 64bit system? Any ideas?
BTW the scatter file is correct for my phone. I had downloaded it myself also before the bricking and I compared it with harddisk_wp's one. They are identical.
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
walckenaerius said:
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
Click to expand...
Click to collapse
SPFT worked for me good to resurrect the phone with files from 1010 version (first firmware) raw partitions.
Phone came back to last user backup and booted fine.
I applied newer and suggested 1019 update that had bricked the phone even further into the loop of the booting logo stuck and rebooting.
SPFT tool memory scan showed that there is no NAND present. I assume that there is PRELOADER damaged. By trying to flush raw PRELOADER that was a no go area. Connection made red line on 100% and nothing happens after that.
SPFT stopped making connection via USB. Inserting the battery, power on - it didn't came back at all.
Phone is now dead black brick that on Linux shows: as MediaTek Inc. MT6227 phone.
In any case do not try to make the same mistake like me.
I will check if it works on some other Windows machine.
Not being Windows user I cannot tell if it is in USB driver or not.
Used W7 without admin pass, with MTKUsbAll driver.
Eh.
Hello everyone,
I want to share my experience with rooting (n00b). So for the first time ever, I managed to root my g900t and my p-600 note --needless to say, I was very excited. When everything checked out and Root Checker told me that I was indeed rooted, the first thing I did was going to Youtube to see what I could do first.
The very first thing that came up was to create a Custom Recovery...fair enough. I watched multiple videos that guaranteed to install the CR "easily". Well, I think I'm an idiot because I couldn't get anything to work.
I tried TWRP, CWM, Philz Touch and TWRP and Philz both loaded on my recovery boot but I still kept getting messages on Rom Manager that I didn't have a custom recovery. At times I also got a lot of errors. I not only tried to get information from the forum but their respective sites and matching my device, installing it through flash & Odin--no luck.
Anyways, I soft-bricked both my g900t and my p600 and after reading hundreds of posts here and other forums and spending all day, I managed to get them running again.
Right now, I'm thankful that I have both devices running and rooted but I still don't know if I have a custom recovery and frankly, I'm scared to try it again. How important is it to get a CR?
By the way, is it bad that all those bad CRs that I installed are still there (if they are)?
I read the rules and also a a lot of forum posts with different variations of CRs for my devices with no luck.
For reference:
Galaxy s5 (5.1.1) Rooted SM-G900T
Samsung Note 10.1 (5.1.1) (Wi-fi) Rooted SM-P600
Thanks guys!
Flashing TWRP through ODIN is very simple - lots of guides out there, but here are some steps:
- Install Samsung Mobile Driver
- Download and unzip ODIN 3 (e.g, 3.1.0.7) to a directory
- Download twrp-2.8.7.0-klte.img.tar from twrp.me
- Boot phone into Download Mode (Vol Down - Home - Power), follow instruction to get to the download mode
- Connect phone to PC, wait for the drivers to be ready
- Start Odin, wait for "Added" message to show up
- Click AP and choose the TWRP tar file
- Go
Sometimes a trick is to uncheck "auto reboot", then flash it twice. That is, flash once, when completely done ("success" on Odin), disconnect and remove/replace battery, power up to boot mode again, then flash again. This is rarely needed but I've had to do this for modem flash once or twice in the past.
Alternatively, you can flash it on the phone from a terminal/cmd shell (lots of apps to choose from on Google Play), and if you have twrp.img extracted to /sdcard, you can do this (again, on the phone):
> su
# dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
The dd method is also doable from ADB shell, but that requires ADB to be set up on the PC.
Hope this helps - I wrote the steps the above from memory but others can correct me I stated anything inaccurately.
EDIT: there are also apps that can install custom recovery, such as Flashify, TWRP manager, ROM Toolbox, Nandroid Manager, etc. Of course, root is required.
many thanks
lost_ said:
Flashing TWRP through ODIN is very simple - lots of guides out there, but here are some steps:
- Install Samsung Mobile Driver
- Download and unzip ODIN 3 (e.g, 3.1.0.7) to a directory
- Download twrp-2.8.7.0-klte.img.tar from ]
- Boot phone into Download Mode (Vol Down - Home - Power), follow instruction to get to the download mode
- Connect phone to PC, wait for the drivers to be ready
- Start Odin, wait for "Added" message to show up
- Click AP and choose the TWRP tar file
- Go
Sometimes a trick is to uncheck "auto reboot", then flash it twice. That is, flash once, when completely done ("success" on Odin), disconnect and remove/replace battery, power up to boot mode again, then flash again. This is rarely needed but I've had to do this for modem flash once or twice in the past.
Alternatively, you can flash it on the phone from a terminal/cmd shell (lots of apps to choose from on Google Play), and if you have twrp.img extracted to /sdcard, you can do this (again, on the phone):
> su
# dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
The dd method is also doable from ADB shell, but that requires ADB to be set up on the PC.
Hope this helps - I wrote the steps the above from memory but others can correct me I stated anything inaccurately.
EDIT: there are also apps that can install custom recovery, such as Flashify, TWRP manager, ROM Toolbox, Nandroid Manager, etc. Of course, root is required.
Click to expand...
Click to collapse
Thank you lost_,
my issue wasn't rooting the devices --they both are, it's getting a custom recovery installed. Neither TWRP nor CWM can find a recovery for my device (g900t). I've looked at countless posts with the same luck. At one point at recovery I had TWRP, which from what I was reading, it meant that I had a custom recovery, right? but again, TWRP and CWM say that I don't have one installed and when I tried to reboot out of recovery it would go into a boot loop forcing me to re-root my device. Basically, I'm stuck at this point and all I really want is to backup all my apps so that they run from my SD card, no coding, no custom roms but it gives me issues. Thanks again.
molotovgod said:
Thank you lost_,
my issue wasn't rooting the devices --they both are, it's getting a custom recovery installed. Neither TWRP nor CWM can find a recovery for my device (g900t). I've looked at countless posts with the same luck. At one point at recovery I had TWRP, which from what I was reading, it meant that I had a custom recovery, right? but again, TWRP and CWM say that I don't have one installed and when I tried to reboot out of recovery it would go into a boot loop forcing me to re-root my device. Basically, I'm stuck at this point and all I really want is to backup all my apps so that they run from my SD card, no coding, no custom roms but it gives me issues. Thanks again.
Click to expand...
Click to collapse
No offense intended, I think you're lost and confused. My post was never about rooting. I did understand you were rooted already. I was outlining how to install a custom recovery, which TWRP and CWM are. Yeah, if you're having a hard time sorting things out based on what I outlined, I don't know how else to get you going. Perhaps start over with your research and read up again on some basic Android 101 (not a HOWTO but an explanation on what is what). Good luck!
ps: this thread should be on the Q&A forum, but we're all helpful and friendly here and you should ask specific questions on that forum instead.
if you're using stock samsung recovery & its stock android, they will overwrite what you just flashed when they boot
odin->flash twrp WITHOUT reboot option->remove battery->put battery->turn on phone directly into recovery, you should see TWRP & you'll be able to flash whatever you want from here, i have no idea what happens if you boot to stock after this since i use CM
i came from stock 4.4 november 2014, used odin 3.07 & https://dl.twrp.me/klte/ 2.8.7.0
kn00tcn said:
if you're using stock samsung recovery & its stock android, they will overwrite what you just flashed when they boot
odin->flash twrp WITHOUT reboot option->remove battery->put battery->turn on phone directly into recovery, you should see TWRP & you'll be able to flash whatever you want from here, i have no idea what happens if you boot to stock after this since i use CM
i came from stock 4.4 november 2014, used odin 3.07 &TWRP 2.8.7.0
Click to expand...
Click to collapse
I have the same phone and cannot flash custom recovery either, as I am a linux user I used heimdall and here is my output
Code:
[[email protected] Downloads]# heimdall flash --RECOVERY twrp-2.8.7.0-klte.img --no-reboot
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
[[email protected] Downloads]#
I flashed my wife's Samsung Galaxy S3 (GT-i9300) and my Galaxy Tab 2 (GT-P5113) a successfully using the procedure described in each device wiki in cyanogenmod page, but same procedure in my phone fails.
My Samsung Galaxy S5 (GT-G900T) is running Samsung's stock Android 5.1.1 (not rooted btw) and stock recovery.
Can you spot what I am doing wrong? Thank you in advance.
pablomino said:
I am a linux user I used heimdall
Click to expand...
Click to collapse
https://github.com/Benjamin-Dobell/Heimdall/issues/209 i couldnt use heimdall either, but there is a patch in that thread that might work for you, you just have to recompile yourself if they didnt update the linux binary
if that still doesnt work, i think you should just use virtualbox to run windows7 & odin with whatever the option is called to have usb pass-through/direct usb access
kn00tcn said:
if that still doesnt work, i think you should just use virtualbox to run windows7 & odin with whatever the option is called to have usb pass-through/direct usb access
Click to expand...
Click to collapse
I moved to a physical Win7 PC, it didn't work either, same error. Could it be because the device is already on Android 5?
Thank you a lot.
Code:
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
C:\>cd heimdall
C:\heimdall>heimdall version
v1.4.0
C:\heimdall>cd Drivers
C:\heimdall\Drivers>zadig
C:\heimdall\Drivers>zadig
C:\heimdall\Drivers>cd ..
C:\heimdall>heimdall flash --RECOVERY twrp-2.8.7.0-klte.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
C:\heimdall>
---------- Post added at 08:42 PM ---------- Previous post was at 08:13 PM ----------
kn00tcn said:
you just have to recompile yourself
Click to expand...
Click to collapse
Anyway I will try compiling the tool from source, I will update with my results. Thank you lot.
pablomino said:
I moved to a physical Win7 PC, it didn't work either, same error.
Click to expand...
Click to collapse
i said to use odin, i have done it several times already, although some people say a newer odin is needed for lollipop based samsung installations... i mentioned 3.07 earlier, today i did 3.10.7 with the latest G900TUVS1FOL1 complete package from sammobile so i can update my baseband & bootloader easily, then once again odin->flash twrp without reboot->remove battery->boot into twrp recovery->flash CM
heimdall does not have the code update that supposedly fixes the PIT error in the official windows binaries, so heimdall will never work on windows unless you compile the fix yourself
(if using odin, always check the exe on virustotal, always get it from someplace reliable like sammobile or an active thread here rather than google)
kn00tcn said:
i said to use odin
Click to expand...
Click to collapse
This solved my problem, thank you a lot.
I searched up and down, read all the stickies here.
Problem is, in many posts links or images are broken. Other posts assume, the device already has seen custom firmware.
I got a never-touched I9100 and I want to get TWRP running. Once this is achieved, I know the rest. I currently have the stock recovery booting - somewhere this was called 3e. All my attempts to flash TWRP via heimdall resulted in only the old recovery showing up. Somewhere it was mentioned I have to flash another kernel first.
So please, does someone have a tutorial or can leave some notes that WORK?
install Apolo kernel TWRP version
https://app.box.com/s/bp9vm6i0vuq1c0x4d8x3y9253b8i38q6/folder/6395372561
Abels2 said:
install Apolo kernel TWRP version
https://app.box.com/s/bp9vm6i0vuq1c0x4d8x3y9253b8i38q6/folder/6395372561
Click to expand...
Click to collapse
404 - This app.box.com page can’t be found
Exactly my problem - all dead or outdated or for wrong setting.
mad-murdock said:
404 - This app.box.com page can’t be found
Exactly my problem - all dead or outdated or for wrong setting.
Click to expand...
Click to collapse
I just uploaded to my google drive the latest version
https://drive.google.com/open?id=1hXCiQ4TijP3d8nUeC5DsRyo8oBuoANmH
to control BLN, governors and others download the Apolo configurator app from google play
https://play.google.com/store/apps/details?id=com.pedestre.configuratorapolo
Edit: it has preinstalled TWRP 2.6.3
if you want the latest versions TWRP 3.x isorec you should go to MM or N roms
Abels2 said:
I just uploaded to my google drive the latest version
https://drive.google.com/open?id=1hXCiQ4TijP3d8nUeC5DsRyo8oBuoANmH
to control BLN, governors and others download the Apolo configurator app from google play
https://play.google.com/store/apps/details?id=com.pedestre.configuratorapolo
Edit: it has preinstalled TWRP 2.6.3
if you want the latest versions TWRP 3.x isorec you should go to MM or N roms
Click to expand...
Click to collapse
Thanks for helping and taking your time to upload! So I heimdall-flash this kernel and then 3-button-combo brings me into twrp 2.6.3 from where i can flash lineage or something similar?
And the reason for this is - if I understand right - recovery on I9100 is not a standalone partition but part of the kernel partition - so your recovery will always be bound to your kernel. Did I get this right?
Nope, cannot flash this kernel with heimdall:
Code:
heimdall flash --BOOT Apolo-4.15b_ExtrV2-TWRP/zImage --no-reboot
results in an error:
Code:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOT upload failed!
Ending session...
Releasing device interface...
mad-murdock said:
Nope, cannot flash this kernel with heimdall:
Code:
heimdall flash --BOOT Apolo-4.15b_ExtrV2-TWRP/zImage --no-reboot
results in an error:
Code:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOT upload failed!
Ending session...
Releasing device interface...
Click to expand...
Click to collapse
it is installed by means of recovery
the recovery and kernel that are not compatible for all the versions of android therefore if you install some custom rom that already has some recovery or kernel pre installed you will have to
guide for partitions without computer
https://forum.xda-developers.com/galaxy-s2/help/kernel-to-root-lineage-i9100-device-t3748674/post75556909#post75556909
Abels2 said:
it is installed by means of recovery
the recovery and kernel that are not compatible for all the versions of android therefore if you install some custom rom that already has some recovery or kernel pre installed you will have to
guide for partitions without computer
https://forum.xda-developers.com/galaxy-s2/help/kernel-to-root-lineage-i9100-device-t3748674/post75556909#post75556909
Click to expand...
Click to collapse
Unfortuately this wont help. I tried to install it with the Samung 3e recovery via adb sideload, but the 3e fails to verify the signature. So I cannot use your kernel.zip file. Reading the other linked thread now.
Thanks for helping me, btw. I guess everyone owning a S2 already has a custom rom installed and thats why all the guides I find are oudated. My S2 is just for playing around, so I am in no hurry.
I've gone through the process on LineageOS's site and I'm stuck on installing the kernal. When I try to flash the boot.img, it says it fails. I can't figure out why.
Here's Heimdall's log:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOT upload failed!
Ending session...
Rebooting device...
Releasing device interface...
I don't know what to do, help please
I have Samsung Galaxy S4 VZW
Which bootloader are you on? Only the MDK bootloader can run lineage OS.
Oh whoops
StoneyJSG said:
Which bootloader are you on? Only the MDK bootloader can run lineage OS.
Click to expand...
Click to collapse
I just figured out it's on I545VRSGPL1. What can I do with my device then?
Renzari said:
I just figured out it's on I545VRSGPL1. What can I do with my device then?
Click to expand...
Click to collapse
You're on the same bootloader I am on, which is locked. All you can do is root and use a certain version of flash fire to flash custom touchwiz ROMs like stang5litre ROM. Everything else, such as a custom recovery or ROMs based on AOSP will not work at all. With the exception of GPE edition ROMs, I THINK those will work okay.
Hi all,
I try to replace PhilZ Touch 3 by TWRP on my (old) galaxy S2 (GT-I9100) to install LineageOS 16 ( lineage-16.0-20191006-UNOFFICIAL-i9100.zip)
I tried using PhilZ:
1) wipe data/factory reset
2)wipe cache partition
3) install zip from sdcard
but it failed and I read that TWRP should be used to do that.
I have no M$ system, only linux OS, also I get Heimdall 1.4.2 and booting in download mode I did:
Code:
$ sudo heimdall flash --RECOVERY twrp-3.3.1-0-i9100.img
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
But after reboot it's Philz is always the recovery system
Any idea of how to success?
Pierre_ said:
Hi all,
I try to replace PhilZ Touch 3 by TWRP on my (old) galaxy S2 (GT-I9100) to install LineageOS 16 ( lineage-16.0-20191006-UNOFFICIAL-i9100.zip)
Click to expand...
Click to collapse
I also followed https://wiki.lineageos.org/devices/i9100/install guide until step 7 where when I reboot the device into recovery mode I have still Philz CWM instead off TWRP.
Perhaps a solution found within the FAQ of PhilZ Touch 6.59.0
5- CMUpdater cannot flash downlaoded files
If you get a /sdcard/0 error, it means you have /sdcard set as /data/media/0 in recovery
The reason is that CM app doesn't support /data/media/0 and is faking recovery with a /sdcard/0 implementation
You still can alter the setting and force it to /data/media in Advanced menu. This will give full compatibility with cwm, CM roms and CM Updater
6- How to flash a boot.img or recovery.img file?
- Put your boot.img or/and recovery.img files under a subfolder in clockworkmod/backup on sdcards
exp: /sdcard/clockworkmod/backup/cm-10.1-nightly_20130713/boot.img
- Navigate to Backup and Restore / Custom Backup and Restore / Custom Restore Job
- Unselect all partitions except boot and/or recovery
- Select >> Start Custom Backup Job <<
- Browse to your backup location until your cm-10.1-nightly_20130713, and select any file inside it
- You are done
Click to expand...
Click to collapse
I'll try it soon