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.
Hi, I flashed the above ROM (but not the newer UNOFFICIAL one) and have lost CWM. A BOOT.IMG file has been posted in the forums and the instructions to flash with Heimdall. I am not familiar with the procedure to do this but I have installed the correct drivers. Can anyone give me any pointers to flash this boot.img file? Thanks!!
imgettingold said:
Hi, I flashed the above ROM (but not the newer UNOFFICIAL one) and have lost CWM. A BOOT.IMG file has been posted in the forums and the instructions to flash with Heimdall. I am not familiar with the procedure to do this but I have installed the correct drivers. Can anyone give me any pointers to flash this boot.img file? Thanks!!
Click to expand...
Click to collapse
Ok, Put phone in download mode and connect USB, Loaded frontend, selected "Flash", loaded my PIT file, Clicked ADD, selected "RECOVERY" from the drop
down menu, Clicked "START" 100% successful flash but still no CWM Recovery mode. Just a black screen if recovery attempted.
Have I missed something? Really miss CWM
you have to flash it as kernel
iurnait said:
you have to flash it as kernel
Click to expand...
Click to collapse
Thank you my good man. I shall try this and get back to you. <Tips hat>
Everything's copacetic. 100% A-Okay.
So I flashed TWRP onto my phone the other night, wouldn't flash with fastboot. Found a TOT file and flashed that which worked, however I can only get into recovery by using adb commands. I can't do it from the phone at all. And whenever I try to flash a ROM I just get error 7. I don't know what's going on with this, but I feel like my TWRP install was probably done wrong or it was a bad file or something. But I was looking all over to find out how to do it. My phone's on stock 6.0 currently. I guess what I'm looking for is a way to flash everything back to stock first, then go about flashing a recovery and a ROM from there.
Check this guide.
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
DopeShotz said:
Check this guide.
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
Click to expand...
Click to collapse
thanks for the link! I'll give it a try as soon as I can.
I unlocked bootloader (critical aswell) today and installed twrp on my A3. The device is NOT rooted
Weird thing is I can't use my wifi anymore, anytime I try to toggle it on it just jumps back.
Anyone knows what caused this and how I can fix it?
felloguard123 said:
I unlocked bootloader (critical aswell) today and installed twrp on my A3. The device is NOT rooted
Weird thing is I can't use my wifi anymore, anytime I try to toggle it on it just jumps back.
Anyone knows what caused this and how I can fix it?
Click to expand...
Click to collapse
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
It seems your boot.img corrupted. If you format data and wipe dalvik cache data and flash stock rom you will succeed i think
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
https://c.mi.com/oc/miuidownload/detail?device=1900372
download official xiaomi mi a3 rom here. and flash it via pc and you will have brand new stock rom. Try it if you fail i will help you when i have free time
garylawwd said:
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
Click to expand...
Click to collapse
I was stupid and thought I did it without a boot image untill I checked all of my commands again.
I used fastboot flash boot twrp-3.3.1-15-laurel_sprout-mauronofrio.img .
My phone was on V10.3.9.0 EUropean. But that image file is for twrp or is it also a boot.img? Not sure if this caused the problem? I'm very new to all of this so how can I find a stock boot.img of that version and how do I flash it again? I feel kinda lost right now.
Anyone can help me out with this?
felloguard123 said:
Anyone can help me out with this?
Click to expand...
Click to collapse
This phone has the recovery inside the boot partition, this is why you need to flash the boot partition, you do not need to flash it again normally, you just flash it to the other slot, boot twrp, go back on the original slot, flash twrp using the .zip file, idk where you should get the boot.img file, but lok online for it, maybe you will find it.
EDIT: https://github.com/AndroidDumps/xia...KQ1.190416.001-V10.3.9.0.PFQMIXM-release-keys
antoine62 said:
This phone has the recovery inside the boot partition, this is why you need to flash the boot partition, you do not need to flash it again normally, you just flash it to the other slot, boot twrp, go back on the original slot, flash twrp using the .zip file, idk where you should get the boot.img file, but lok online for it, maybe you will find it.
EDIT: https://github.com/AndroidDumps/xia...KQ1.190416.001-V10.3.9.0.PFQMIXM-release-keys
Click to expand...
Click to collapse
But what was the my fault here? What did I wrong? Was it the .img file of the twrp or did I install it wrongly? I am very new to this and don't understand why there are 2 slots etc. Sorry for the confusion.
felloguard123 said:
But what was the my fault here? What did I wrong? Was it the .img file of the twrp or did I install it wrongly? I am very new to this and don't understand why there are 2 slots etc. Sorry for the confusion.
Click to expand...
Click to collapse
You installed it uncorrectly, you need to switch slot (because this device have an A/B partition type), flash twrp, boot it, switch to the og slot, flash twrp using the .zip file (so it modify your current boot.img), and done.
This phone will be my first A/B phone, i cant wait to receive it.
But what you didnt is still correct, just not perfect.
antoine62 said:
You installed it uncorrectly, you need to switch slot (because this device have an A/B partition type), flash twrp, boot it, switch to the og slot, flash twrp using the .zip file (so it modify your current boot.img), and done.
This phone will be my first A/B phone, i cant wait to receive it.
But what you didnt is still correct, just not perfect.
Click to expand...
Click to collapse
So twrp has to be installed on both partitions?
I'm not sure if really twrp installed on only one partition could cause Wifi problems.
I would assume that my .img for twrp was faulty.
a
garylawwd said:
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
Click to expand...
Click to collapse
and how to do that:{?
i have same problem as yours and searched too many videos on youtube but then i have decided to remove the twrp from the device and no one yet has told me that how to flash twrp in another partition rather i dont know what is the another partition
Hey guys,
I've tried to update my Nord 2 to the newest software (A.12) but every time I try it, it just reboots after a couple seconds and displays an error message:"Verification error". I've tried rebooting it multiple times, without any success. It is rooted with magisk and the bootloader is open, but I don't have TWRP installed. Could you guys hook me up with a solution?
Regards
Take a look: https://forum.xda-developers.com/t/...rooted-nord-2-any-incremental-update.4347813/
Thanks for your reply, I really appreciate it! I've looked at it, but I haven't found a specific update from a.11 to a.12, I just didn't want to take the risk to update with the indian variant from a.11 to a.13.
AdamBarath said:
Thanks for your reply, I really appreciate it! I've looked at it, but I haven't found a specific update from a.11 to a.12, I just didn't want to take the risk to update with the indian variant from a.11 to a.13.
Click to expand...
Click to collapse
No need to download the update file from third parties. If you downloaded it from settings, you can find it in your internal storage at android/data/com.oneplus.ota/files
For the boot file instead, you can find boot files both for indian and Eu in that post
Raygen said:
No need to download the update file from third parties. If you downloaded it from settings, you can find it in your internal storage at android/data/com.oneplus.ota/files
For the boot file instead, you can find boot files both for indian and Eu in that post
Click to expand...
Click to collapse
Thank you, I really appreciate your help! I'm going to try it as soon as possible, do I have to flash the vbmeta.img, if I use my own update.zip file? (Sorry, I have literally zero knowledge)
AdamBarath said:
Thank you, I really appreciate your help! I'm going to try it as soon as possible, do I have to flash the vbmeta.img, if I use my own update.zip file? (Sorry, I have literally zero knowledge)
Click to expand...
Click to collapse
Yup, the order is:
Backup EVERYTHING.
Flash stock boot image for your current version (A.11)
Flash update.zip via recovery
Flash patched vbmeta via fstboot
Re flash TWRP via fastboot
Reflash magisk:
Flash the .zip it via recovery (not reccomended). OR,
Download and flash an already patched boot image for the updated version (A.12). OR,
Extract your stock updated boot image (A.12) with adb shell and dd (or download it), boot into system, patch the image with the magisk app, flash the patched boot image in recovery.
If during one of these steps you get back the stock recovery, just boot into fastboot and reflash twrp. Without magisk installed the rom tends to restore the stock recovery by itself.
Thank you for your help!
Worked like a charm!