Related
I'm trying to get into the bootloader to flash an older version of TWRP. I'm holding various combinations of buttons down when rebooting but the phone either goes to Recovery, Odin, or normal boot. The "bootloader" boot option in TWRP doesn't work either, it just goes to normal boot. What am I missing? I know for many phones the bootloader is accessed by holding VOL Down + Power when rebooting but that's not working on the Note 2.
Thanks.
slicknick27 said:
I'm trying to get into the bootloader to flash an older version of TWRP. I'm holding various combinations of buttons down when rebooting but the phone either goes to Recovery, Odin, or normal boot. The "bootloader" boot option in TWRP doesn't work either, it just goes to normal boot. What am I missing? I know for many phones the bootloader is accessed by holding VOL Down + Power when rebooting but that's not working on the Note 2.
Thanks.
Click to expand...
Click to collapse
I believe the reason why you can't boot into bootloader is because it has something to do with the Unlock Bootloader method/exploit. I'm going to take a shot in the dark and say the exploit is not the standard unlock method so therefore you can't boot into the bootloader.
Also, you can flash a recovery a different way. Download the Goo.im Manager app in the Google Play Store and when you go in the app, you can search the recoveries and it will flash them from the app for you.
DroidOnRoids said:
I believe the reason why you can't boot into bootloader is because it has something to do with the Unlock Bootloader method/exploit. I'm going to take a shot in the dark and say the exploit is not the standard unlock method so therefore you can't boot into the bootloader.
Also, you can flash a recovery a different way. Download the Goo.im Manager app in the Google Play Store and when you go in the app, you can search the recoveries and it will flash them from the app for you.
Click to expand...
Click to collapse
Hey, thanks for shedding some light on this. And I'm going to try flashing from the Goo.im manager, that sounds easier at this point, too.
slicknick27 said:
Hey, thanks for shedding some light on this. And I'm going to try flashing from the Goo.im manager, that sounds easier at this point, too.
Click to expand...
Click to collapse
No problem, man. Just make sure you flash the right recovery file because if you are broad on your search, it will give you a list of different recoveries for different devices. Search the version of TWRP you want with 'i605'.
DroidOnRoids said:
No problem, man. Just make sure you flash the right recovery file because if you are broad on your search, it will give you a list of different recoveries for different devices. Search the version of TWRP you want with 'i605'.
Click to expand...
Click to collapse
Unfortunately there are no older versions of TWRP in the Goo.im manager app. This is off-topic from my original question but it's the reason I was trying to get into the bootloader in the first place. Do you know of any way to downgrade TWRP to a previous version on this phone other than the flashing from bootloader method?
slicknick27 said:
Unfortunately there are no older versions of TWRP in the Goo.im manager app. This is off-topic from my original question but it's the reason I was trying to get into the bootloader in the first place. Do you know of any way to downgrade TWRP to a previous version on this phone other than the flashing from bootloader method?
Click to expand...
Click to collapse
Hm, you searched with i605, right? Well, I searched and found that on Goo.im, it is actually t0ltevzw.
Here are all the TWRP builds for the VZW Note 2 from Goo.im: http://goo.im/devs/OpenRecovery/t0ltevzw/
EDIT: Here's our device page on the TWRP website: http://teamw.in/project/twrp2/133
EDIT 2: If I were you, try not to flash a recovery using Odin. I wouldn't risk screwing up the unlocked bootloader exploit. Lastly, if you didn't know, do NOT in any way flash a custom rom using Odin. It's bad news for your phone.
Edited again because I forgot fastboot requires bootloader access lol
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
DroidOnRoids said:
Hm, you searched with i605, right? Well, I searched and found that on Goo.im, it is actually t0ltevzw.
Here are all the TWRP builds for the VZW Note 2 from Goo.im: http://goo.im/devs/OpenRecovery/t0ltevzw/
EDIT: Here's our device page on the TWRP website: http://teamw.in/project/twrp2/133
EDIT 2: If I were you, try not to flash a recovery using Odin. I wouldn't risk screwing up the unlocked bootloader exploit. Lastly, if you didn't know, do NOT in any way flash a custom rom using Odin. It's bad news for your phone.
Edited again because I forgot fastboot requires bootloader access lol
Click to expand...
Click to collapse
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
slicknick27 said:
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
Click to expand...
Click to collapse
So the 2.4.0.0 is the version you want, correct? And which file of this recovery version did you download? If you tried downloading and installing using the Goo.im app, try downloading the zip file from your computer and transferring it over to your SD Card. From there you can reboot to the existing recovery, install it, and reboot the recovery.
If that doesn't work either, tell me and I can figure out a different option.
DroidOnRoids said:
So the 2.4.0.0 is the version you want, correct? And which file of this recovery version did you download? If you tried downloading and installing using the Goo.im app, try downloading the zip file from your computer and transferring it over to your SD Card. From there you can reboot to the existing recovery, install it, and reboot the recovery.
If that doesn't work either, tell me and I can figure out a different option.
Click to expand...
Click to collapse
Actually, if I can I'd like to downgrade to TWRP 2.3.3.1, which was the version I installed back when I got the phone in December.
On Goo.im web site it is:
openrecovery-twrp-2.3.3.1-t0ltevzw.zip
It is my understanding though that you can't flash TWRP from within TWRP?
slicknick27 said:
Actually, if I can I'd like to downgrade to TWRP 2.3.3.1, which was the version I installed back when I got the phone in December.
On Goo.im web site it is:
openrecovery-twrp-2.3.3.1-t0ltevzw.zip
It is my understanding though that you can't flash TWRP from within TWRP?
Click to expand...
Click to collapse
You can flash CWM in TWRP, TWRP in CWM, TWRP in TWRP, or CWM in CWM. All you need to do is flash it and then go to the recovery options and hit Reboot Recovery.
Where did you hear that you can't flash TWRP in TWRP?
DroidOnRoids said:
You can flash CWM in TWRP, TWRP in CWM, TWRP in TWRP, or CWM in CWM. All you need to do is flash it and then go to the recovery options and hit Reboot Recovery.
Where did you hear that you can't flash TWRP in TWRP?
Click to expand...
Click to collapse
OK, yeah, I was told in another thread that I couldn't flash TWRP with TWRP.
So, I just want to clarify, I can flash an older version of TWRP over an newer version of TWRP already installed -- as if I was flashing any regular .zip?
slicknick27 said:
OK, yeah, I was told in another thread that I couldn't flash TWRP with TWRP.
So, I just want to clarify, I can flash an older version of TWRP over an newer version of TWRP already installed -- as if I would flash any regular .zip?
Click to expand...
Click to collapse
Yes, you can do that because it's going to completely overwrite the other version of TWRP. It doesn't matter what version you flash because it's going to be all on its own. The previous recovery doesn't benefit from a newer version of a recovery. You're safe to do it
EDIT: When I had my Galaxy Nexus, TWRP was brand spanking new so I had to downgrade a lot because of all the bugs presented in the later releases.
DroidOnRoids said:
Yes, you can do that because it's going to completely overwrite the other version of TWRP. It doesn't matter what version you flash because it's going to be all on it's own. The previous recovery doesn't benefit from a newer version of a recovery. You're safe to do it
EDIT: When I had my Galaxy Nexus, TWRP was brand spanking new so I had to downgrade a lot because of all the bugs presented in the later releases.
Click to expand...
Click to collapse
Phew. OK. Well again I thank you for sticking with me and clearing this up. I suspected I could do that in the first place but was confused by information I was given otherwise. Off I go to recovery!
slicknick27 said:
Phew. OK. Well again I thank you for sticking with me and clearing this up. I suspected I could do that in the first place but was confused by information I was given otherwise. Off I go to recovery!
Click to expand...
Click to collapse
Good luck! Let me know when it's a success.
DroidOnRoids said:
Good luck! Let me know when it's a success.
Click to expand...
Click to collapse
Well, TWRP verified the checksum and the modem installed successfully. But apparently it turns out the problem was not as it originally seemed.
When I downloaded the older version of TWRP, I opened its .MD5 file again just to check, and I noticed that the .MD5 files for the zips on Goo.im (or at least OpenRecovery's ZIPS) omitted the asterisk that precedes the filename:
Code:
d4624c4f8c9427b6137b2b97902e76b3 openrecovery-twrp-2.4.1.0-t0ltevzw.zip
Whereas with other .MD5 files that I've created (including the .MD5 file for the modem zip that was failing verification in TWRP), I've used an asterisk before the filename:
Code:
d4624c4f8c9427b6137b2b97902e76b3 [B][COLOR="Red"]*[/COLOR][/B]openrecovery-twrp-2.4.1.0-t0ltevzw.zip
So after the modem flashed successfully on TWRP 2.3, I decided to try flashing it again (with the asterisk omitted from the MD5 file) on the latest TWRP 2.4.1.0. It flashed just fine. So the issue seems to be TWRP getting hung up on the asterisk that precedes the filename in MD5 files -- though this doesn't happen all the time because I've flashed many MD5 files with the asterisk successfully.
A bug in TWRP? Or maybe I shouldn't be using the asterisk at all. In any case, I'm back on TWRP 2.4.1.0 with the modem flashed.
EDIT: And I learned that you can flash TWRP in TWRP
slicknick27 said:
Well, TWRP verified the checksum and the modem installed successfully. But apparently it turns out the problem was not as it originally seemed.
When I downloaded the older version of TWRP, I opened its .MD5 file again just to check, and I noticed that the .MD5 files for the zips on Goo.im (or at least OpenRecovery's ZIPS) omitted the asterisk that precedes the filename:
d4624c4f8c9427b6137b2b97902e76b3 openrecovery-twrp-2.4.1.0-t0ltevzw.zip
Whereas with other .MD5 files that I've created (including the .MD5 file for the modem zip that was failing verification in TWRP), I've used an asterisk before the filename:
d4624c4f8c9427b6137b2b97902e76b3 *openrecovery-twrp-2.4.1.0-t0ltevzw.zip
So after the modem flashed successfully on TWRP 2.3, I decided to try flashing it again (with the asterisk omitted from the MD5 file) on the latest TWRP 2.4.1.0. It flashed just fine. So the issue seems to be TWRP getting hung up on the asterisk that precedes the filename in MD5 files -- though this doesn't happen all the time because I've flashed many MD5 files with the asterisk successfully.
A bug in TWRP? Or maybe I shouldn't be using the asterisk at all. In any case, I'm back on TWRP 2.4.1.0 with the modem flashed.
EDIT: And I learned that you can flash TWRP in TWRP
Click to expand...
Click to collapse
I would bring that to their attention and see why that's the case on their recovery. Anyway, glad that everything is figured out and running perfectly. :good:
DroidOnRoids said:
I would bring that to their attention and see why that's the case on their recovery. Anyway, glad that everything is figured out and running perfectly. :good:
Click to expand...
Click to collapse
Yes I'm going to report it.
Take it easy.
Any help will be appreciated, i have the HTC One Max 803s.
The device has no OS in it, only can access TWRP v2.7.0.0.
I've downloaded ROMs such as NuSenseSIX, PACT6, CandyKat T6, in this HTC one max forum .. . tried flashing through TWRP with no luck and an error message as below:
"Error executing updater binary in zip ..."
"Error flashing zip ...."
Is there anything else i've missed? What is the problem?
Thanks.
hpl912 said:
Any help will be appreciated, i have the HTC One Max 803s.
The device has no OS in it, only can access TWRP v2.7.0.0.
I've downloaded ROMs such as NuSenseSIX, PACT6, CandyKat T6, in this HTC one max forum .. . tried flashing through TWRP with no luck and an error message as below:
"Error executing updater binary in zip ..."
"Error flashing zip ...."
Is there anything else i've missed? What is the problem?
Thanks.
Click to expand...
Click to collapse
Use TWRP from here, and the try to flash a ROM.
bfisch3r said:
Use TWRP from here, and the try to flash a ROM.
Click to expand...
Click to collapse
Thanks, but looks like i can't flash the new recovery, it gives a message: Failed <remote:not allowed> :crying:
what's the issue now?
hpl912 said:
Thanks, but looks like i can't flash the new recovery, it gives a message: Failed <remote:not allowed> :crying:
what's the issue now?
Click to expand...
Click to collapse
Gonna take a wild guess your boot loader is locked.
Bootloader could be locked. Also, when you tried to change recovery, where you flashing via recovery or using ADB? You should be using ADB.
Solved. thanks guys for the advices, below is what was done:
- unlocked bootloader
- re-flashed new open recovery from the above suggested link
- flashed rom
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 was flashing paranoid android 6.0.2 for my device. I downloaded the zip(from the official paranoid android website) and checked the md5 checksum, which did not match. However, like a total idiot, I flashed it nonetheless. On booting, the phone gets stuck on the boot logo. I tried booting into recovery(TWRP) and performing a factory reset to no avail. I redownloaded the flashable zip for Paranoid, successfully verified the md5 checksum and flashed it again, no avail. Restore a full backup from within TWRP, no avail. My phone still gets stuck on the bootlogo. I have looked all over every forum without any results. Please help me out? I would like to get it back to functional state and flash the rom again. As mentioned, I have access to my custom recovery and can connect to my device via fastboot. I am willing to give any other information you may need.
Thanks!
Shreyas
shreyasminocha said:
I was flashing paranoid android 6.0.2 for my device. I downloaded the zip(from the official paranoid android website) and checked the md5 checksum, which did not match. However, like a total idiot, I flashed it nonetheless. On booting, the phone gets stuck on the boot logo. I tried booting into recovery(TWRP) and performing a factory reset to no avail. I redownloaded the flashable zip for Paranoid, successfully verified the md5 checksum and flashed it again, no avail. Restore a full backup from within TWRP, no avail. My phone still gets stuck on the bootlogo. I have looked all over every forum without any results. Please help me out? I would like to get it back to functional state and flash the rom again. As mentioned, I have access to my custom recovery and can connect to my device via fastboot. I am willing to give any other information you may need.
Thanks!
Shreyas
Click to expand...
Click to collapse
What was your last rom? Did u upgrade ur bootloader?
You probably looking at mega unbrick guide
cva_kabil said:
What was your last rom? Did u upgrade ur bootloader?
Click to expand...
Click to collapse
I was running stock OxygenOS(>3.0.0) ROM.
shreyasminocha said:
I was running stock OxygenOS(>3.0.0) ROM.
Click to expand...
Click to collapse
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
cva_kabil said:
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
Click to expand...
Click to collapse
That said, should I follow a bricked guide before doing the above?
cva_kabil said:
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
Click to expand...
Click to collapse
Also, is there any way I can downgrade my bootloader?
shreyasminocha said:
Also, is there any way I can downgrade my bootloader?
Click to expand...
Click to collapse
Flash any 2.X.X ROM. One way is to fastboot flash old stock recovery and flash safest way I think. The other is to flash with twrp make sure after flashing the ROM to flash old twrp IMG after. Make sure you boot right back into twrp.
shreyasminocha said:
Also, is there any way I can downgrade my bootloader?
Click to expand...
Click to collapse
Assuming you're on OOS3 with TWRP for new bootloader,
- Boot into recovery
- Wipe everything except SD Card
- Flash OOS2 zip
- Boot into it
- Goto settings, unlock dev options, enable advanced reboot
- Then reboot to bootloader
- Flash twrp for old bootloader via fastboot, use this one https://dl.twrp.me/onyx/twrp-3.0.2-0-onyx.img
Done
-Now u hv sucessfully downgraded ur bootloader,flash PA or any supported roms
Used mega unbrick tool because I was unable to unlock bootloader and now I'm stuck at 1+ logo (powered by android disappears quickly), did you solve it?
edit: nevermind, adb sideload with stock OOS fixed it.
TravaPL said:
Used mega unbrick tool because I was unable to unlock bootloader and now I'm stuck at 1+ logo (powered by android disappears quickly), did you solve it?
edit: nevermind, adb sideload with stock OOS fixed it.
Click to expand...
Click to collapse
Tried mega unbrick. (bootloop)
Tried OOS3.1.4.zip via stock recovery and success message apears after installation but still bootloop (previusly it was on CM13)
Tried ADB sideload (but not booting)
i have access to ADB and Fastboot.
please help :crying:
iamsandiprathva said:
Tried mega unbrick. (bootloop)
Tried OOS3.1.4.zip via stock recovery and success message apears after installation but still bootloop (previusly it was on CM13)
Tried ADB sideload (but not booting)
i have access to ADB and Fastboot.
please help :crying:
Click to expand...
Click to collapse
Did you managed to sort it out? How?
Mega unbricked guide?
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.