Hello
I have purchased a second hand Nexus. It is rooted and has got custom rom. Also Teamwinner or so is installed. When i boot into recovery to install some other rom it exits with error 7. Same when i try to update the teamwinner to the newest version.
Any idea what to try?
dosada said:
Hello
I have purchased a second hand Nexus. It is rooted and has got custom rom. Also Teamwinner or so is installed. When i boot into recovery to install some other rom it exits with error 7. Same when i try to update the teamwinner to the newest version.
Any idea what to try?
Click to expand...
Click to collapse
i remember seeing error 7 before on a rom i tried to flash.. i was using CWM so its not the recovery's fault. turns out there was a problem with the rom...
so find another rom to flash would be my answer for now.
The problem is that i get this error whatever i tried to flah. Even cwm or some other rom result in same error
dosada said:
The problem is that i get this error whatever i tried to flah. Even cwm or some other rom result in same error
Click to expand...
Click to collapse
What procedure are you using to flash? What file are you trying to flash and where did you get it from?
I start up the phone using volume down and power. Then in teamwinner i chose install zip and then the file
so far have tried, all downloaded from here or linked from here, those files
CWM-Touch-6.0.2.5-DJ
Hellybean-20130405-crespo
TWRP-2.4.4.0-DJ
jellyshot_crespo-v3.3
nothing works. all of them exist with error 7
dosada said:
I start up the phone using volume down and power. Then in teamwinner i chose install zip and then the file
so far have tried, all downloaded from here or linked from here, those files
CWM-Touch-6.0.2.5-DJ
Hellybean-20130405-crespo
TWRP-2.4.4.0-DJ
jellyshot_crespo-v3.3
nothing works. all of them exist with error 7
Click to expand...
Click to collapse
.....
This is the Galaxy Nexus forums, that firmware aka ROM is for crespo aka Nexus S
Sent from my Nexus
Fair enough about the roms, but why cant i even install cwm? This shows me just the error 7 too
I wouldn't be surprised if your recovery is either not for your device or not even a flash able zip.
dosada said:
Fair enough about the roms, but why cant i even install cwm? This shows me just the error 7 too
Click to expand...
Click to collapse
Where did you get that CWM? http://www.clockworkmod.com/rommanager? If so those are img files, for flashing from fastboot. But I have no idea what "DJ" is for. To flash from recovery it needs to be packaged in a flashable zip.
Or you can install CWM from the ROM Manager app. Or TWRP from GooManager.
quite frankly i wouldnt use CWM. The UI is annoying as hell, and it tends ot be a lot slower, at least from my own experience.
I recommand TWRP, http://www.teamw.in/project/twrp2/90 latest version here for maguro.
if you have adb set up, installing twrp is cake, simply open adb and type:
1) adb reboot bootloader
2) fastboot flash recovery TWRP.img <-----assuming you are in the directory of that img file you just downloaded, and TWRP is just the name of the img file, its usually attached with version, so i would rename it for easier access.
3) after you flashed it just boot into recovery and start flashing your new rom.
If all else fail.....use the toolkit and flash factory image for a fresh start, i havnt failed with factory image yet
Related
Here is the official ClockworkMod Recovery 6.0.4.7 non-touch images and touch images for the Nexus 10 enjoy :cyclops:!
Credit goes to Koush for releasing the official ClockworkMod Recovery images
These are safe to flash via fastboot.
Non-Touch
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-manta.img
Touch
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.7-manta.img
These can be flashed via fastboot using the following commands:
Code:
fastboot flash recovery /path/to/.img
fastboot reboot
Once again enjoy :victory:!
Note: To get the recovery to stick on reboot when Clockworkmod Recovery asks you if you want rename flash-recovery.sh or similar say "Yes", this will allow you to keep Clockworkmod Recovery installed permanently (Unless you flash a different recovery image) when you reboot your phone.
These reboot randomly as well. I've been trying to get TWRP to work, but TWRP is doing the same thing. Nothing in dmesg or last_kmsg to help either. :/
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Dees_Troy said:
These reboot randomly as well. I've been trying to get TWRP to work, but TWRP is doing the same thing. Nothing in dmesg or last_kmsg to help either. :/
Click to expand...
Click to collapse
zedomax said:
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Click to expand...
Click to collapse
Ok that is really bizare, both CWMR and TWRP are not working right and encountering similar issues regarding random reboots and mount issues. Whats odd is other people are experiencing random reboots during regular use even when not in recovery. I'm starting to believe that something Google might have to put out at fix for software wise may be needed.
So I take it no more "booting" the temporary ones posted before for the Nexus 4/Nexus 10? We can go ahead and "flash" these ones right?
zedomax said:
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Click to expand...
Click to collapse
i cant even get the sideload to work to get SU installed. Its driving me crazy. I keep trying it over and over again with the same result. As soon as i go over to recovery it unmounts from the computer then the sideload command fails due to computer losing connection with it. "Device not found"
Tried both CWM versions now .5 and .6
Not my first time around the block with rooting :-/
Used heimdall suite to flash my GS2.. any way to get it to push the .zip file for SU over to the phone? Push the recovery img then push the .zip maybe?
So I never even ended up trying to sideload anything, I just flashed the official recovery, then went immediately to recovery from fastboot, and once there I just flashed the SU zip and now I have root. Of course, CWMR doesn't work (i.e. if I use Quick Boot to boot to recovery it just takes me to the stock recovery, and if I try to go to recovery from fastboot manually, I just get the dead android w/red triangle).
Jayrod1980 said:
Finally got it... helped to just get the supersu on the root of the device. I used the fastboot commands to get to cwm touch and then I quickly installed it through the interface. I couldn't sideload. The device won't recognize adb when I'm in fastboot mode at all. I don't know what I was doing wrong in that instance, but using cwm briefly let me install supersu. Thanks for your help! Surprising this is so buggy considering it's a nexus... and it's not the nexus that's excluded from AOSP. Go figure!
Click to expand...
Click to collapse
I had to do it this way in order to get root. Finally.. been working on this for like 5ish hours now.. what a pain. Hopefully there will be an easier route for everyone else and a CWM that does not reboot in 20ish seconds soon. Good luck to everyone that goes this route.. it takes a lot of trial and error
snunez said:
Hopefully there will be an easier route for everyone else and a CWM that does not reboot in 20ish seconds soon.
Click to expand...
Click to collapse
I'm sure there will be, probably by the end of the weekend, if not sooner
I took apart CWM touch 6.0.1.6 and fixed reboot after 20 sec
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Great work! If you could post the unpacked version I'd appreciate it. I was trying to build a fixed version without success and would like to compare.
So,
Am I right in thinking...
cd to the adb tools folder where the sdk is saved.
I need to unlock the boot loader via fastboot oem.
Then copy your file to the same directory on my Mac
Then type in the command line you suggested with the correct filename?
After that I will be rooted
Swype'd at pace from my Galaxy S2
Here's my working tree
The-Kevster said:
Great work! If you could post the unpacked version I'd appreciate it. I was trying to build a fixed version without success and would like to compare.
Click to expand...
Click to collapse
I used this tool to unpack and re-pack the image: https://github.com/huaixzk/unpackbootimg.git
Attached is my current working tree as a tar.gz
Edit: the tool in that git repo is missing a step to gunzip | cpio the ramdisk... I made a shell script to do that for me when unpacking and repacking
Edit2: I added the wrapper scripts I made for posterity
damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Wow! It worked perfectly... You are a genius. No more random reboots in recovery! Thank you. I have one question... Are you able to do the same for TWRP for the Nexus 10, if possible?
Underworld79 said:
Wow! It worked perfectly... You are a genius. No more random reboots in recovery! Thank you. I have one question... Are you able to do the same for TWRP for the Nexus 10, if possible?
Click to expand...
Click to collapse
I could probably do it to TWRP as well (later today, it's sleep time for me)... however, I don't know where the latest nexus 10 recovery image is from them (considering it's not in this forum).
so can I permanently flash this now instead of fastboot?
damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Well I just flashed your version of the recovery, and after doing "fastboot-mac reboot" and rebooting, I tried rebooting to recovery via adb, and unfortunately it brought me back to the dead android red triangle screen. In fact, I can't even get to CWMR at all. Anyone else??
And to be clear, I have successfully rooted, so at this point I'm just trying to get a functioning version of CWMR on the tablet, if possible.
Did you try holding power and pressing Vol+ when booting recovery? That's how you enter stock recovery.
Randomwalker said:
Did you try holding power and pressing Vol+ when booting recovery? That's how you enter stock recovery.
Click to expand...
Click to collapse
Yeah I know that, but I'm not trying to enter stock recovery, I'm trying to enter the custom recovery (which is the supposed "stable" one by damien) which I've installed. And it only let me access CWMR immediately after flashing it. However anytime afterwards I simply cannot access it again:
1) tried "adb reboot recovery" and it brings me to the dead android w/red triangle
2) tried getting to recovery via the Quick Boot app, and the same thing happens
3) tried getting to recovery via the normal holding buttons down to get to bootloader, then going to recovery manually from there, and a no-go as well.
In the end, all that happens is I have to toggle the buttons once I get to the dead android screen, and the menu for the stock recovery appears, which allows me to reboot. But as for CWMR, it is nowhere to be found. WTF.
Did you reboot after installing CWM? If so, did you remove install.sh, that will restore the stock recovery?
Ok so I am not the greatest when it comes to flashing ROMs but so far I have managed to get by.
I went from MMuzzyROM 4.2.2 to [ROM] [4.3] [JSS15J]. I wiped my data/dalvick/cache, flashed the new ROM and Gaaps and installed SuperuserSU. As of right now SuperuserSU will not install and I get an installation error. And when using Rom Manager I can not reboot into recovery. And there is a bit more, when I try and boot into recovery from the holding the volume and power button down, after choosing recovery the android with the error shows up. From what I understand is that the 4.3 rom I flashed removed the stock recovery, but I am just confused how to get back recovery.
My main question is did I loose root and how can I get the recovery option back.
Thanks, Noel
knoll126 said:
Ok so I am not the greatest when it comes to flashing ROMs but so far I have managed to get by.
I went from MMuzzyROM 4.2.2 to [ROM] [4.3] [JSS15J]. I wiped my data/dalvick/cache, flashed the new ROM and Gaaps and installed SuperuserSU. As of right now SuperuserSU will not install and I get an installation error. And when using Rom Manager I can not reboot into recovery. And there is a bit more, when I try and boot into recovery from the holding the volume and power button down, after choosing recovery the android with the error shows up. From what I understand is that the 4.3 rom I flashed removed the stock recovery, but I am just confused how to get back recovery.
My main question is did I loose root and how can I get the recovery option back.
Thanks, Noel
Click to expand...
Click to collapse
4.3 is buggy with root right now. You can use rom manager to reflash cwmrecovery or you can use goomanager to install twrp
dnewha sees
NyPlaya513 said:
4.3 is buggy with root right now. You can use rom manager to reflash cwmrecovery or you can use goomanager to install twrp
Click to expand...
Click to collapse
I try to reflash but doesn't seem to work.
knoll126 said:
I try to reflash but doesn't seem to work.
Click to expand...
Click to collapse
USE TWRP!
When trying to flash CWR I get an error message. I am pretty sure I am unrooted without an option for recovery and stuck on 4.3?
beekay201 said:
USE TWRP!
Click to expand...
Click to collapse
Ok I guess I am just too confused. Downloading TWRP gives me an image file which I don't understand how to install, because I thought I need recovery to do it? When in fastboot I can select recovery but I get the error android.
knoll126 said:
When trying to flash CWR I get an error message. I am pretty sure I am unrooted without an option for recovery and stuck on 4.3?
Click to expand...
Click to collapse
what error message?
what's the fastboot command you're using to flash recovery.
about loosing your recovery after flashing/boot/reboot OS for the first time, it's probably the same that 4.2 had
/system/recovery-from-boot.p
/system/install-recovery.sh
beekay201 said:
what error message?
what's the fastboot command you're using to flash recovery.
about loosing your recovery after flashing/boot/reboot OS for the first time, it's probably the same that 4.2 had
/system/recovery-from-boot.p
/system/install-recovery.sh
Click to expand...
Click to collapse
The error message is when using the clockwork mod app to install the recovery, once downloaded it states an error has occurred. Then when trying TWRP I am following these steps I get "fastboot is not a recognizable command..." I am pretty lost as you can tell and am thankful for the help.
knoll126 said:
The error message is when using the clockwork mod app to install the recovery, once downloaded it states an error has occurred. Then when trying TWRP I am following these steps I get "fastboot is not a recognizable command..." I am pretty lost as you can tell and am thankful for the help.
Click to expand...
Click to collapse
*facepalm*
WHY you people don't read the frakkin stickies?!?!?
http://forum.xda-developers.com/showthread.php?t=1812959
beekay201 said:
*facepalm*
WHY you people don't read the frakkin stickies?!?!?
http://forum.xda-developers.com/showthread.php?t=1812959
Click to expand...
Click to collapse
Mainly because I thought if I had rooted my device and done all this once, I should remember how to do it again. But through ignorance I thought I could and be able to remember the steps and what not. I'll read through it and figure it out, it was just a moment of panic of losing the option of recovery that I have had for a long time and not being able to use it means (or I think it means) I am just stuck of 4.3 for a bit and hopefully the ROM isn't too bad.
hi,
My phone is soft bricked and stuck at boot logo. I am trying to flash stock recovery/kdz file using flash tool but getting stuck at"low battery" error.
Could you please help how i can bypass this error? I have spend a lot of time online and tried few methods but always getting stuck at this error. I dont have any alternative phone and this is really disappointing.
I am using E988 India model.
CLICK HERE MATE. LET ME KNOW IF IT HELPS. IF NOT USE THE INSTRUCTIONS BELOW
I'm using same phone and have the same problem. I still can't flash stock with the tool but I can tell you how to get out of soft brick. Download madmacks e980 lokified TWRP recovery and also CM 11 latest version. Get in to recovery mode and go to install file (sideload) and flash the recovery first then reboot in to recovery again and sideload CM 11. When I get a definitive solution to flash stock I will let you know mate. If you have problems or don't know what I'm talking about then reply here. You well need adb installed on computer and open a new command window by holding shift and click right noise button at the same time. Make sure you perform this from the same directory as where there files are that your flashing. Once your phone prompts you to sideload type in to the command window adb sideload (the exact file name of the file you want to flash.zip) but without the brackets
uppon2 said:
CLICK HERE MATE. LET ME KNOW IF IT HELPS. IF NOT USE THE INSTRUCTIONS BELOW
I'm using same phone and have the same problem. I still can't flash stock with the tool but I can tell you how to get out of soft brick. Download madmacks e980 lokified TWRP recovery and also CM 11 latest version. Get in to recovery mode and go to install file (sideload) and flash the recovery first then reboot in to recovery again and sideload CM 11. When I get a definitive solution to flash stock I will let you know mate. If you have problems or don't know what I'm talking about then reply here. You well need adb installed on computer and open a new command window by holding shift and click right noise button at the same time. Make sure you perform this from the same directory as where there files are that your flashing. Once your phone prompts you to sideload type in to the command window adb sideload (the exact file name of the file you want to flash.zip) but without the brackets
Click to expand...
Click to collapse
Thank you very much for this help. I have never tried adb. Probably I shall now learn it and then try to do as you suggested. I am not particular about stock ROM. In fact I will be happy if there is stable cm ROM for this phone.
I juts bought this phone two days back. There are too many model numbers n am little scared now about choosing the right ROM. Do you mind sharing link for correct cm11 ROM please?,
Thanks again for your help!
Sent from my GT-I9500 using xda app-developers app
Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
set_metadata_recursive: some changes failed
E:Error in /sdcard/firmware/cm-11-20140619-NIGHTLY-hercules.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Spud37 said:
Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Click to expand...
Click to collapse
"Set metadata recursive" probably means you are using a recovery that is too old.
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
jrc2 said:
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
Click to expand...
Click to collapse
Well there is another issue with my phone that I have actually worked around for awhile now. The MircoUSB on the phone is broken. I bought an extra battery and swap it, I also just use the SD card to copy anything to the phone. Is there a way for me to flash the phone with the new TWRP from the sd card. Why would the older TWRP not install CM 10.2.0 ROM? Do I have to go older perhaps? Thanks though. Knowing is half the battle
EDIT: Going to try and install 10.1.0 and see if it will let me boot. I figure once I can get it to boot, it will be easier to update the Recovery on the phone.
EDIT 2: No problems or errors occured when I installed CM 10.1.0.zip. However it still got stuck in a boot loop. I did however find a file called superwipe for the T mobile S2. I am wondering if that could help
EDIT 3: Okay so the superwipe worked and i am now running 10.1.0, Is it possible to install a Recovery from the phone without using odin?
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
jrc2 said:
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
Click to expand...
Click to collapse
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Spud37 said:
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Click to expand...
Click to collapse
It is a lot more risky if your usb port doesn't work, since you can't flash back to stock in Odin if something goes wrong. I would recommend that you get someone to fix that USB port before you make too many changes.
DISCLAIMER: I am not responsible for anything that happens to your phone. These changes could brick your phone if something goes wrong. Proceed at your own risk!
Okay, now for the tutorial. These instructions are assuming that you are already rooted. Download this file and make sure you check the md5sum. Rename it to TWRP.img and move it to /storage/sdcard. This will make the next steps easier. If you move the file somewhere else, make a note of the location of the file. If you have not already, install the terminal emulator app form the Play Store. Open it and type the following lines in it.
Code:
su
[CLICK ENTER]
Code:
dd if=/storage/sdcard/TWRP.img of=/dev/block/mmcblk0p22
(Change the path to wherever you moved the file to) [CLICK ENTER]
Reboot into recovery and wipe cache and dalvik. Reboot. If recovery says that system recovery will override it on reboot, click fix. This should update your recovery.
Have a good afternoon,
jrc2
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Did you follow the instructions to flash TWRP using Odin?
olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear
bump
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?
N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.
N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post
aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.