Related
Hello, xda! I'm such a noob here and maybe this question will be stupid. I rooted my Htc One X two days ago and now cann't update firmware up to 1.29.401.11 from 1.29.401.7. Tried to goodle it, but didn't find anything helpful.
Here is what i tried to do:
1) In settings- update os
2) It said that here is a new one
3) Download it
4) Press "Install"
5) Phone is rebooting
6) ClockworkMod Recovery v5.8.2.7 opened
7) Error in the bottom of screen:
Code:
"Finding update package..."
"E: unknown volume for path [INTERNALSDCARD:Download/blah-blah-blah.zip]
"E: Can't mount INTERNALSDCARD:Download/blah-blah-blah.zip"
"Installation aborted"
8) I tried to install it manually, choose "install zip from sdcard" and click on file->Yes, install
9) Errors again:
Code:
Installing /sdcard/Download/blah-blah-blah.zip
Finding update package...
Opeing update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
What should i do to update my firmware? Thx.
You need to flash stock recovery and make sure you haven't deleted any system apps or flashed any system mods for the ota to work.
Or you could update using a ruu, it wipes your phone data but you get a fresh install
Sent from my HTC One X using Tapatalk 2
bogfather said:
You need to flash stock recovery and make sure you haven't deleted any system apps or flashed any system mods for the ota to work.
Or you could update using a ruu, it wipes your phone data but you get a fresh install
Click to expand...
Click to collapse
Flash stock recovery? can u give instruction, please?
I don't wanna ruu in this case.
Have a look at this program http://forum.xda-developers.com/showthread.php?p=25656320
Put your phone in fastboot usb, run the program and pick the option for flash stock recovery. Then pick the recovery of the version your on, hit enter and jobs done
Sent from my HTC One X using Tapatalk 2
can someone give step-by-step instruction? I can't get it ><
Download the program in my last post to your pc
Put your phone into fastboot then connect to pc
Double click the run me file on your pc and wait for the program to pop up
Pick the option that says flash stock recovery
Then pick the option to flash 1.29 recovery.
Reboot your phone then try the ota
Sent from my HTC One X using Tapatalk 2
ketron said:
can someone give step-by-step instruction? I can't get it ><
Click to expand...
Click to collapse
If you do not know even the basic steps to unlocking, flashing etc... then I suggest you stop right now before you end up with a $800 paperweight on your desk.
There are a number of threads in the Dev section that give you step by step instructions on what to do, just search. If you still don't understand then read again. If you still don't understand after reading again then stay clear of rooting, it's not for you.
dr9722 said:
If you do not know even the basic steps to unlocking, flashing etc... then I suggest you stop right now before you end up with a $800 paperweight on your desk.
There are a number of threads in the Dev section that give you step by step instructions on what to do, just search. If you still don't understand then read again. If you still don't understand after reading again then stay clear of rooting, it's not for you.
Click to expand...
Click to collapse
I unlock it and it's working good. I flashed some programms, but i just don't know how to update, cuz in ClockworkMod there is nothing about firmware update.
I tried to search, but didn't find exactly what i need.
ketron said:
I unlock it and it's working good. I flashed some programms, but i just don't know how to update, cuz in ClockworkMod there is nothing about firmware update.
I tried to search, but didn't find exactly what i need.
Click to expand...
Click to collapse
I guess you did not relock your bootloader.
You should follow this tutorial.
http://forum.xda-developers.com/showthread.php?t=1660807
Hi Guys,
I ahve the same problem. I unrooted my phone, flashed stock recovery, locked my bootloader and resetted to factory default. It still won't update and gives a "warning" logo and then resets as if nothing happened.
I had the same errors.
I could't recovery - it just keept rebooting to fastloader.
I send it to be repaid but was told that the phone was parallel import and it would cost me the same as a new phone to fix it bcos of new "motherbord"...
It seems reasonably. The box did't have any danish manuals and the firm closed down few weeks after I bought it (danlet.dk). The repair guy said it was ment for Germany...
ketron said:
Hello, xda! I'm such a noob here and maybe this question will be stupid. I rooted my Htc One X two days ago and now cann't update firmware up to 1.29.401.11 from 1.29.401.7. Tried to goodle it, but didn't find anything helpful.
Here is what i tried to do:
1) In settings- update os
2) It said that here is a new one
3) Download it
4) Press "Install"
5) Phone is rebooting
6) ClockworkMod Recovery v5.8.2.7 opened
7) Error in the bottom of screen:
Code:
"Finding update package..."
"E: unknown volume for path [INTERNALSDCARD:Download/blah-blah-blah.zip]
"E: Can't mount INTERNALSDCARD:Download/blah-blah-blah.zip"
"Installation aborted"
8) I tried to install it manually, choose "install zip from sdcard" and click on file->Yes, install
9) Errors again:
Code:
Installing /sdcard/Download/blah-blah-blah.zip
Finding update package...
Opeing update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
What should i do to update my firmware? Thx.
Click to expand...
Click to collapse
You could try one the custom roms based on 1.29.401.11 which is flashable in clockwork recovery along with the kernel via fastboot.
salvadk said:
I had the same errors.
I could't recovery - it just keept rebooting to fastloader.
I send it to be repaid but was told that the phone was parallel import and it would cost me the same as a new phone to fix it bcos of new "motherbord"...
It seems reasonably. The box did't have any danish manuals and the firm closed down few weeks after I bought it (danlet.dk). The repair guy said it was ment for Germany...
Click to expand...
Click to collapse
If you have Clockwork Recovery installed you cannot update over the air. You have two options:
1) Flash back to Stock recovery, update OTA and then flash Clockwork again
2) Flash a custom ROM that is already based on .11
thanks man
bogfather said:
Download the program in my last post to your pc
Put your phone into fastboot then connect to pc
Double click the run me file on your pc and wait for the program to pop up
Pick the option that says flash stock recovery
Then pick the option to flash 1.29 recovery.
Reboot your phone then try the ota
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
a very good info , it was useful for me, a had same problem, i did what you wrote, it's working 100%.
Thanks a lot , :good::victory:
I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:
Improper recovery.
samelaryan said:
I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:
Click to expand...
Click to collapse
BAM1789 said:
Improper recovery.
Click to expand...
Click to collapse
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers
xBeerdroiDx said:
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers
Click to expand...
Click to collapse
I did that and it worked thank you :good:
samelaryan said:
I did that and it worked thank you :good:
Click to expand...
Click to collapse
thats what we're all here for, buddy
Status 7: installation aborted.
xBeerdroiDx said:
thats what we're all here for, buddy
Click to expand...
Click to collapse
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.
perceptorz said:
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.
Click to expand...
Click to collapse
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot
xBeerdroiDx said:
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot
Click to expand...
Click to collapse
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.
perceptorz said:
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.
Click to expand...
Click to collapse
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.
xBeerdroiDx said:
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.
Click to expand...
Click to collapse
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)
perceptorz said:
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)
Click to expand...
Click to collapse
I would take up this situation in the correct forum. The more we discuss your device issues the more likey you are to download the wrong file or use a procedure not designed for your device software.
If you came from stock, flashed a rom and are stuck at the samsung logo, boot into recovery, wipe data and cache. Reboot to see if that helped. If not, seek advice in the N7000 forum. Cheers
Thanks for the guidance.
Can someone please let me know what I'm missing. I'm rooted, and have even flashed a couple ROMs successfully but most of them will fail to install withan error saying "E: No MD5 file found for [insert whatever ROM]. I'm running TWRP recovery (v.2.3.3.1)
Sprint Galaxy S III
esco_three said:
Can someone please let me know what I'm missing. I'm rooted, and have even flashed a couple ROMs successfully but most of them will fail to install withan error saying "E: No MD5 file found for [insert whatever ROM]. I'm running TWRP recovery (v.2.3.3.1)
Sprint Galaxy S III
Click to expand...
Click to collapse
In the settings (either in "advanced" or on the install menu) on TWRP you can choose to verify the MD5 sum. I believe that if you uncheck that option it should work.
Let me know if this works!
topherk said:
In the settings (either in "advanced" or on the install menu) on TWRP you can choose to verify the MD5 sum. I believe that if you uncheck that option it should work.
Let me know if this works!
Click to expand...
Click to collapse
I have tried that, for multiple ROMs, but still fails.
esco_three said:
I have tried that, for multiple ROMs, but still fails.
Click to expand...
Click to collapse
Are you on the latest version of TWRP? If not, try updating and see if that fixes it
And what rom is it thats failing?
CNexus said:
Are you on the latest version of TWRP? If not, try updating and see if that fixes it
And what rom is it thats failing?
Click to expand...
Click to collapse
I will try the latest version of TWRP and see if that works.
The fail has been happening on multiple ROMs. AOSPA 3.15: Hybrid Mode, MIUIAndroid v4.1 & Avatar ROM to name a few. All the same issue.
No MD5 file found
I am having the same issue! this happened on multiple ROMs from various developers, I have tried every thing suggested and verified rooted.
Badfish63 said:
I am having the same issue! this happened on multiple ROMs from various developers, I have tried every thing suggested and verified rooted.
Click to expand...
Click to collapse
It's not really an error, TWRP just checks to see if there's a corresponding md5 file with the md5 checksum for whatever it is that you're flashing
You can flash any rom perfectly fine without it, but I would make sure that you check the md5sum against the one that the ROM thread or ROM download site gives you
No MD5 file found
CNexus said:
It's not really an error, TWRP just checks to see if there's a corresponding md5 file with the md5 checksum for whatever it is that you're flashing
You can flash any rom perfectly fine without it, but I would make sure that you check the md5sum against the one that the ROM thread or ROM download site gives you
Click to expand...
Click to collapse
Thanks! But I can't seem to even do my first flash! I noticed in any of the ROMS I download for some reason it does not pull the MD5 file. I have downloaded from here XDA and other sites, and android forums. I don't get it. this should be fairly easy according to all the research I have done even before my first attempt.
no md5 file--please help
can someone help me. I am fairly new at custom rom work, but I rooted my galaxy note 3 (Verizon) using kingo, and installed safestrap (latest version) and attempted to install cm11 but while installing it does a md5 file check and says no md5 file found. when I reboot, the Samsung screen comes up and then it goes and stays black. I have to pull battery and go back to stock rom. I have tried reformatting my ext. storage and reinstall..no go. please help. thank you very much in advance.
west1986 said:
can someone help me. I am fairly new at custom rom work, but I rooted my galaxy note 3 (Verizon) using kingo, and installed safestrap (latest version) and attempted to install cm11 but while installing it does a md5 file check and says no md5 file found. when I reboot, the Samsung screen comes up and then it goes and stays black. I have to pull battery and go back to stock rom. I have tried reformatting my ext. storage and reinstall..no go. please help. thank you very much in advance.
Click to expand...
Click to collapse
You might have a better chance at an answer in the forum for your specific carrier and device, this is the forum for the Sprint Samsung Galaxy S3.
topherk said:
In the settings (either in "advanced" or on the install menu) on TWRP you can choose to verify the MD5 sum. I believe that if you uncheck that option it should work.
Let me know if this works!
Click to expand...
Click to collapse
I'm experiencing the same issue.
L710 currently Slimbean, updating to Slimkat 4.4.2 I get the fail for the MD5
I have TWRP 2.6.0.0
I don't see any uncheck MD5 option only in settings and these are already unchecked.
When flashing back to Slimbean 4.3 I get the error
E: error opening '/data/lost + found'
E: error no such file or directory
But it still passes and I'm on 4.3
Reivaj1803 said:
I'm experiencing the same issue.
L710 currently Slimbean, updating to Slimkat 4.4.2 I get the fail for the MD5
I have TWRP 2.6.0.0
I don't see any uncheck MD5 option only in settings and these are already unchecked.
When flashing back to Slimbean 4.3 I get the error
E: error opening '/data/lost + found'
E: error no such file or directory
But it still passes and I'm on 4.3
Click to expand...
Click to collapse
It finally worked!
I updated TWRP to the latest 2.6.3.1 and Slimkat flashed with no problems.
This new setup took me for a loop, wasn't expecting it. After all said and done, I am running. :good: :good:
Reivaj1803 said:
It finally worked!
I updated TWRP to the latest 2.6.3.1 and Slimkat flashed with no problems.
This new setup took me for a loop, wasn't expecting it. After all said and done, I am running. :good: :good:
Click to expand...
Click to collapse
I was going to suggest that you should try flashing over the new TWRP recovery. Best of luck!
Dolby
CNexus said:
Are you on the latest version of TWRP? If not, try updating and see if that fixes it
And what rom is it thats failing?
Click to expand...
Click to collapse
I am trying to flash dolby. The flash is successful but the app icon doesn't appear on the screen. In the recovery log it says md5 file not found. I've tried flashing viper too but the condition is the same. Please help.
Mr. Struck said:
You might have a better chance at an answer in the forum for your specific carrier and device, this is the forum for the Sprint Samsung Galaxy S3.
Click to expand...
Click to collapse
1. Installed Stock ROM, using Odin3_v3.11.2 (Run as Adminstrator)
N900XXUEBPB1_N900ODDEBPB1_N900DDUEBOB1_HOME.tar.md5
My "Samsung Galaxy Note 3 SM-N900" Running on 5.0 lollipop
2. I have rooted my "Samsung Galaxy Note 3 SM-N900" using followiing file using Odin3_v3.11.2 (Run as Adminstrator)
CF-Auto-Root-ha3g-ha3gxx-smn900
3. Later I've installed TWRP recovry, using Odin3_v3.11.2 (Run as Adminstrator)
twrp-3.0.2-0-ha3g.img_safe.tar
Now when I try to install MIUI for "Samsung Galaxy Note 3 SM-N900" port ROM, either getting Failed or If it is success my phone does not startup hung at SAMSUNG logo (Waited for nearly 2 hrs).
miui_n900_lushengduan_6.5.27_19d567b4f3_4.4.zip
miui_n9005_bhflower_6.5.27_e7133a52f8_4.4.zip
- Tried above method after wiping the cache and internal drive still the same.
- Tried to install from external card same error
- Tried to install from internal card same error
PLEASE HELP.I HAVE STRUGGLING FROM LAST 1 WEEK WITH ALL THE TRIEL AND ERROR METHOD.
Is there any solution to this problem? im also experiencing today.
my unit is galaxy n3 international im running with the rom cm 14.1 cyanogenmod using TWRP 3.0.2-1 and i want to install different rom's but i always got stuck whenever i swipe to flash the new rom it say's no md5 after a minute my system is restarting and nothing's happen.
ken041387 said:
Is there any solution to this problem? im also experiencing today.
my unit is galaxy n3 international im running with the rom cm 14.1 cyanogenmod using TWRP 3.0.2-1 and i want to install different rom's but i always got stuck whenever i swipe to flash the new rom it say's no md5 after a minute my system is restarting and nothing's happen.
Click to expand...
Click to collapse
Turn off md5 verification in twrp settings
I also have this problem on my galaxy alpha sm-g850f I'm running TWRP 2.8.7.0 it says "no Md5 file found" can someone help me
This method has been proven by me to work on Mac OS X, Windows 7, 8, and 8.1, plus Linux (whatever heimdall works on).
If you are reading this, you should already be frustrated as all HELL like I was the other night. No need to fear. When Odin doesn't work, Heimdall is here to rescue you. Heimdall and I stayed awake until 3 am the other night so I could throw these quick TUTs your way. Sometimes the gods don't answer, but their watchers will guide you...
There really shouldn't be a need to say this, but....
I take absolutely no responsibility for what happens to your phone. At this point you were probably already messing around with it, then Odin decided to be a prick and error all day long. If you so happen to feel that you messed up your phone more than you already had it, sorry, but still, not my fault.
Thanks:
Benjamin Dobell for Heimdall - http://forum.xda-developers.com/showthread.php?t=755265
DeezNutz1977 - Original 4.3 Build
allenjthomsen - KK Build files
Phil5739 - Philz CWM Advanced Recovery
bigbiff - twrp always in progress
dragonstalker - for his ROMS and contributions.
ghibli3 - for this guide which allowed me to pull and edit the KK pit file successfully.
There were a ton of threads I read through, I cant remember them all, but thanks pretty much goes out to all who contribute here. The XDA community is great!
Bootloop Recovery Heimdall Guide
The above guide will help you to recover your phone using heimdall. This is not a heimdall tutorial. For those instructions please see the heimdall website and read their instructions. I am posting this to help those that may be stuck in a similar situation as I was. Plus the presentation counts towards my "communications" class. The text guide is below...
Download 4.3 JB Recovery Zip Here
Upload for 4.4.2 in progress
1. Put phone in download mode
2. Open Heimdall
3. On utilities tab “check device” If your phone cannot be read, it may be far worse than expected.
4. Click on flash tab after successfully detected.
5. In the pit section, choose the pit file I provided.
6. Click add in the partitions box to the right > Select BOOT
7. Select the boot.img file provided
8. Click add in the partitions box again to the right > Select CACHE
9. Select the cache.img.ext4 file provided.
10. Click the add in the partitions box again > Select RECOVERY
11. Select the recovery provided (you can probably use any recovery, but provided is twrp 2.6.3.7) <-- this will trip knox if you haven't already done so.
12. Make sure no reboot is checked
13. The phone may flash all the way to the end and error out. If this is the case, proceed with steps 14 and 15. If not, proceed to step 16.
14. **Pull battery
15. **Replace
16. Boot to recovery, and re-install your backup (or another ROM, whatever).
If anyone has a mirror, feel free to share as necessary.
Stock Restore Heimdall Guide
The above guide will help those restore to stock MI7 via Heimdall. If you were in the same situation I was in, this will help tremendously as odin would not help me out in the least.
Download Stock JB MI7 here.
1. Put phone in download mode
2. Open Heimdall
3. On utilities tab “check device” If your phone cannot be read, it may be far worse than expected.
4. Click on Load Package tab after successfully detected.
5. Click browse and choose the file (tar.gz) you downloaded.
6. After the package loads, click the "load/customize" button on the bottom right corner.
7. Click on the flash tab afterwards.
8. Ensure repartition, no reboot, and resume checkboxes are not checked.
9. Click on the "start" button in the lower right hand corner... Profit?
** Continue here only if phone does not take the first time.
10. If you receive a libusb error, consult Heimdall instructions for fix... try, try again.
Again, mirrors and sharing are encouraged.
noobtoob said:
This method has been proven by me to work on Mac OS X, Windows 7, 8, and 8.1, plus Linux (whatever heimdall works on).
If you are reading this, you should already be frustrated as all HELL like I was the other night. No need to fear. When Odin doesn't work, Heimdall is here to rescue you. Heimdall and I stayed awake until 3 am the other night so I could throw these quick TUTs your way. Sometimes the gods don't answer, but their watchers will guide you...
There really shouldn't be a need to say this, but....
I take absolutely no responsibility for what happens to your phone. At this point you were probably already messing around with it, then Odin decided to be a prick and error all day long. If you so happen to feel that you messed up your phone more than you already had it, sorry, but still, not my fault.
Bootloop Recovery Heimdall Guide
http://youtu.be/-huMP5ZaMiw
The above guide will help you to recover your phone using heimdall. This is not a heimdall tutorial. For those instructions please see the heimdall website and read their instructions. I am posting this to help those that may be stuck in a similar situation as I was. Plus the presentation counts towards my "communications" class. The text guide is below...
Download this First: https://www.dropbox.com/s/oc534gzr5usbivi/BootLoop Recovery.zip
1. Put phone in download mode
2. Open Heimdall
3. On utilities tab “check device” If your phone cannot be read, it may be far worse than expected.
4. Click on flash tab after successfully detected.
5. In the pit section, choose the pit file I provided.
6. Click add in the partitions box to the right > Select BOOT
7. Select the boot.img file provided
8. Click add in the partitions box again to the right > Select CACHE
9. Select the cache.img.ext4 file provided.
10. Click the add in the partitions box again > Select RECOVERY
11. Select the recovery provided (you can probably use any recovery, but provided is twrp 2.6.3.7)
12. Make sure no reboot is checked
13. The phone may flash all the way to the end and error out. If this is the case, proceed with steps 14 and 15. If not, proceed to step 16.
14. **Pull battery
15. **Replace
16. Boot to recovery, and re-install your backup (or another ROM, whatever).
If anyone has a mirror, feel free to share as necessary.
Stock Restore Heimdall Guide
http://youtu.be/hXtZDUD7MYQ
The above guide will help those restore to stock MI7 via Heimdall. If you were in the same situation I was in, this will help tremendously as odin would not help me out in the least.
Download this First: https://www.dropbox.com/s/m9dpb7ya0umvrzl/Stock_SM-N900T_MI7.tar.gz
1. Put phone in download mode
2. Open Heimdall
3. On utilities tab “check device” If your phone cannot be read, it may be far worse than expected.
4. Click on Load Package tab after successfully detected.
5. Click browse and choose the file (tar.gz) you downloaded.
6. After the package loads, click the "load/customize" button on the bottom right corner.
7. Click on the flash tab afterwards.
8. Ensure repartition, no reboot, and resume checkboxes are not checked.
9. Click on the "start" button in the lower right hand corner... Profit?
** Continue here only if phone does not take the first time.
10. If you receive a libusb error, consult Heimdall instructions for fix... try, try again.
Again, mirrors and sharing are encouraged.
Click to expand...
Click to collapse
Won't download right now...too much traffic. It looks like almost everyone wants to download this lol...
kuroy301 said:
Won't download right now...too much traffic. It looks like almost everyone wants to download this lol...
Click to expand...
Click to collapse
Seriously? I just put this up. Any mirror suggestions? I don't really post/share much since I started school a year ago.
Edit: Only 3 views, must be from the youtube videos...LOL. I will search for a mirror.
Dropbox sharing has been denied due to bandwidth usage. Uploading to mediafire now. Should be up in about 2 hours. Sorry everyone.
EDIT: OP Updated, new links added. Hope you all get the help needed.
Heimdall install
Hello
I use windows8.1 and I amunable to instal lHeimdall. I installed the C++ and yet still giving msvcp110.dll Anyoneexperiencing this?I really need this solution. My GN3 is loopboot many days. My knox this 0x1 and I cannot flash a rom that in no loopboot.
help
Fates_Warning said:
Hello
I use windows8.1 and I amunable to instal lHeimdall. I installed the C++ and yet still giving msvcp110.dll Anyoneexperiencing this?I really need this solution. My GN3 is loopboot many days. My knox this 0x1 and I cannot flash a rom that in no loopboot.
help
Click to expand...
Click to collapse
Have you tried installing both the 32 bit and 64 bit visual c++ applications? I installed both because i want sure which one heimdall would use.
Sent from my SM-N900T using Tapatalk
Thank you. was missing install the 32-bit. :good:
The problem is now being with the cache file. It hangs at 52% and not flash. Any ideas, my friends?
What are you flashing? The entire stock ROM, or are you doing the recovery?
Sent from my SM-N900T using Tapatalk
i tried using this and got this "ERROR: Failed to access device. libusb error: -12, can you pls send me a link where i can find out what to do next? i'm not very computer literate
jboy619 said:
i tried using this and got this "ERROR: Failed to access device. libusb error: -12, can you pls send me a link where i can find out what to do next? i'm not very computer literate
Click to expand...
Click to collapse
In the files you downloaded when you got heimdall, there is an .exe that allows you to replace the USB driver for you device. You have to follow the directions in the read me file they gave you.
You have 3 driver choices to replace the one to flash for yours. There is a windows driver, a libusb driver, and a libusb (k) driver. One of these will allow the phone to flash.
noobtoob said:
What are you flashing? The entire stock ROM, or are you doing the recovery?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
My problem is when I try to flash the file cache.ext4 in the early stages by heimdall .
Fates_Warning said:
My problem is when I try to flash the file cache.ext4 in the early stages by heimdall .
Click to expand...
Click to collapse
Need a few questions answered.
1. Are you flashing with a libusb driver from the drivers package provided by heimdall?
2. can you get into recovery as of right now? What version is it?
1a. If you are flashing without using the drivers that were provided, experiment a bit. My particular phone likes the libusbk one that is provided. See the heimdall readme file for details.
2a. If you can get into recovery right now, try to wipe cache, data, and dalviche. The try to reflash.
I don't know what kind of boot loop you are stuck in. This method may not work for you depending on what I was just asking. You may need to explore a different method to get your device up and running.
Sent from my SM-N900T using Tapatalk
noobtoob said:
Need a few questions answered.
1. Are you flashing with a libusb driver from the drivers package provided by heimdall?
2. can you get into recovery as of right now? What version is it?
1a. If you are flashing without using the drivers that were provided, experiment a bit. My particular phone likes the libusbk one that is provided. See the heimdall readme file for details.
2a. If you can get into recovery right now, try to wipe cache, data, and dalviche. The try to reflash.
I don't know what kind of boot loop you are stuck in. This method may not work for you depending on what I was just asking. You may need to explore a different method to get your device up and running.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Many thanks for the help.
The heimdall can communicate with my GN3. I can flash the boot file and the recovery usually, but not of cache.ext4. I have attached a photo of the error and heimdall. After flashing my recovery is TRWP sign that is heimdall flash and other files that not only the cache.
About My bootloop error:
My phone stock by odin installs normally. And then starts the android is giving the error "process system is not responding" and loops .. I already gave wipe with all available recovery. Have several flash stock (uk, zto, international, etc. ..) and the problem persists with any rom. Any idea?
Do not proceed from here! I just noticed you are trying to flash a sm-n900t to a sm-n9005. That is why it is not working. The recovery you are trying to flash is not meant for your phone model.
Sent from my SM-N900T using Tapatalk
Fates_Warning said:
Many thanks for the help.
The heimdall can communicate with my GN3. I can flash the boot file and the recovery usually, but not of cache.ext4. I have attached a photo of the error and heimdall. After flashing my recovery is TRWP sign that is heimdall flash and other files that not only the cache.
About My bootloop error:
My phone stock by odin installs normally. And then starts the android is giving the error "process system is not responding" and loops .. I already gave wipe with all available recovery. Have several flash stock (uk, zto, international, etc. ..) and the problem persists with any rom. Any idea?
Click to expand...
Click to collapse
See above post.
Sent from my SM-N900T using Tapatalk
Hi!
Thanks for your work!
Does it trigger KNOX please ?
noobtoob said:
See above post.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
true .. the problem is that my shows the same bootloop problem are you trying to solve?
"Local and device PIT files don't match and repartition wasn't specified!"
What's wrong ? Should I click on "repartition" ? I have also an MI7 version of the ROM. n9005 too... ????? :/
WHat about KNOX ??
Thank you
EDIT : Just saw that the open post doesn't even say it is for N900 !!!!! Please, fix this!!
thank you found the file but now i got a new challenge "ERROR: Failed to initialise protocol!"
---------- Post added at 12:54 AM ---------- Previous post was at 12:41 AM ----------
thanks found it but now i got a new challenge "ERROR: Failed to initialise protocol!" ?
Nemorensis32 said:
"Local and device PIT files don't match and repartition wasn't specified!"
What's wrong ? Should I click on "repartition" ? I have also an MI7 version of the ROM. n9005 too... ????? :/
WHat about KNOX ??
Thank you
EDIT : Just saw that the open post doesn't even say it is for N900 !!!!! Please, fix this!!
Click to expand...
Click to collapse
Do not click on repartition. Do not proceed from here if you do not have the sm-n900t. This forum is posted under the "T-Mobile Samsung Galaxy Note 3" which is the sm-n900t. It is possible for you to have this device on a different network, but you should already know what model you are trying to fix.
The .pit file in my recovery zip will not work for you because the phone is not the same. Please go to your respective forum, and look for the files there.
Knox will trip if you flash the recovery I provided.
Sent from my SM-N900T using Tapatalk
jboy619 said:
thank you found the file but now i got a new challenge "ERROR: Failed to initialise protocol!"
---------- Post added at 12:54 AM ---------- Previous post was at 12:41 AM ----------
thanks found it but now i got a new challenge "ERROR: Failed to initialise protocol!" ?
Click to expand...
Click to collapse
Try using libUSB, and libUSBk drivers. Mine specifically likes the libusbk. But every phone is different. I believe I had the same error when trying to use the win32 and the libusb drivers.
Other than that, it may be a heimdall issue that I am unfamiliar with.
EDIT: Also I should mention, when mine did all of this, I had to use the recovery zip first, then move onto the stock restore portion. I can't necessarily say why I had to, but I did. If you already have knox tripped, I recommend doing that. While in recovery, I performed an advanced wipe. Wiped system, cache, dalvik and internal storage. The internal storage part may not be necessary, but I wanted to start fresh.
Sent from my SM-N900T using Tapatalk
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.