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
Related
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.
Hi all ... I am working with a Samsung Galaxy Tab 3 7.0 (SM-T210R) and was interested in speeding the device up.
I flashed TWRP 2.6.3 and rooted and then tried to flash the SEAL ROM after watching the video.
During the install. I got a bunch of errors ... I don't have a screenshot, but it said the following:
ASSERT FAILED package_extract_file ("boot.img") ...
E: Error Executing updater binary in zip '/external_sd/ROM/SEAL V2 Official.zip' ....
Error Flashing Zip 'external_sd/ROMS/SEAL V2 ...
Luckily, the backup is working fine and I was able to restore.
I finally was able to flash a debloat script that I saw on XDA to speed it up a bit, but I really wanted to try this rom.
Any ideas are appreciated. Thanks very much.
savidon said:
Hi all ... I am working with a Samsung Galaxy Tab 3 7.0 (SM-T210R) and was interested in speeding the device up.
I flashed TWRP 2.6.3 and rooted and then tried to flash the SEAL ROM after watching the video.
During the install. I got a bunch of errors ... I don't have a screenshot, but it said the following:
ASSERT FAILED package_extract_file ("boot.img") ...
E: Error Executing updater binary in zip '/external_sd/ROM/SEAL V2 Official.zip' ....
Error Flashing Zip 'external_sd/ROMS/SEAL V2 ...
Luckily, the backup is working fine and I was able to restore.
I finally was able to flash a debloat script that I saw on XDA to speed it up a bit, but I really wanted to try this rom.
Any ideas are appreciated. Thanks very much.
Click to expand...
Click to collapse
Try removing any spaces in the zip name.
gr8nole said:
Try removing any spaces in the zip name.
Click to expand...
Click to collapse
Thanks for the suggestion .. I just tried that and got the same errors.
Strange.
FWIW .. I also had issues trying to install the RocketTab ROM as well. Different problem, but still never worked. As I said, I was able to flash a debloat script that seems to have helped with the performance somewhat but still not great.
Thanks again.
savidon said:
Hi all ... I am working with a Samsung Galaxy Tab 3 7.0 (SM-T210R) and was interested in speeding the device up.
I flashed TWRP 2.6.3 and rooted and then tried to flash the SEAL ROM after watching the video.
During the install. I got a bunch of errors ... I don't have a screenshot, but it said the following:
ASSERT FAILED package_extract_file ("boot.img") ...
E: Error Executing updater binary in zip '/external_sd/ROM/SEAL V2 Official.zip' ....
Error Flashing Zip 'external_sd/ROMS/SEAL V2 ...
Luckily, the backup is working fine and I was able to restore.
I finally was able to flash a debloat script that I saw on XDA to speed it up a bit, but I really wanted to try this rom.
Any ideas are appreciated. Thanks very much.
Click to expand...
Click to collapse
I followed these directions (minus the rooting, as the ROM is already Rooted) yesterday and installed RocketTab 3.1 without a hitch:
http://forum.xda-developers.com/showthread.php?t=2660588
tsg2513 said:
I followed these directions (minus the rooting, as the ROM is already Rooted) yesterday and installed RocketTab 3.1 without a hitch:
http://forum.xda-developers.com/showthread.php?t=2660588
Click to expand...
Click to collapse
I've tried RocketTab multiple times ... and after flashing I get a message that the device appears to not be rooted, and offers to install SuperSU ... whether I say install or not, after I reboot ... the tablet freezes on the Samsung opening screen. I have no idea what else to try.
Thanks.
savidon said:
I've tried RocketTab multiple times ... and after flashing I get a message that the device appears to not be rooted, and offers to install SuperSU ... whether I say install or not, after I reboot ... the tablet freezes on the Samsung opening screen. I have no idea what else to try.
Thanks.
Click to expand...
Click to collapse
Did you check the MD5 of the zip, it could be a bad download.
Sent from my SCH-I605
gr8nole said:
Did you check the MD5 of the zip, it could be a bad download.
Sent from my SCH-I605
Click to expand...
Click to collapse
I did .. it matched. I think I'll try downloading again just in case though. Not sure what else to try at this point.
Thanks.
So I re-downloaded the SEAL ROM files and this time it installed without any errors, but I still got the not rooted message when I tried to reboot the device in TWRP. Again, whether or not I choose to install SuperSU, it hangs on the Samsung Galaxy Tab screen and I need to boot back into recovery and restore from backup to get working again.
For some reason, the root in the ROMs is not taking or something? Is that what is causing the problem? Does that make any sense?
Any other ideas? Thanks again!
savidon said:
So I re-downloaded the SEAL ROM files and this time it installed without any errors, but I still got the not rooted message when I tried to reboot the device in TWRP. Again, whether or not I choose to install SuperSU, it hangs on the Samsung Galaxy Tab screen and I need to boot back into recovery and restore from backup to get working again.
For some reason, the root in the ROMs is not taking or something? Is that what is causing the problem? Does that make any sense?
Any other ideas? Thanks again!
Click to expand...
Click to collapse
Sound like the system is not flashing correctly. Maybe try a different recovery.
Sent from my SCH-I605
Try the normal CWM coz touch-based are allergic to my device too....no worries you can still still scroll down the menu list of options using your finger tips
Sent from my SM-T211 using XDA Premium 4 mobile app
So here is the latest update in my custom rom saga ...
I downgraded TWRP to 2.6.1 .. and attempted to re-flash both SEAL and RocketTab. Both installs seemed to complete without any errors this time, but after rebooting, my device froze on the Samsung Galaxy Tab logo screen .. before the boot animation. This happened for both the SEAL and RocketTab roms. I also no longer got the not rooted error message, so it looked like it was fine.
Any thoughts on why these custom roms are not booting? I appreciate the help.
I restored back to my de-bloated stock backup, and it works fine. A little faster definitely, but not speedy by any means.
Thanks again.
Try philz touch recovery. I also had problems with cwm and twrp. But philz touch does the charm for me.
Sent from my SM-T210R using xda app-developers app
Hello Everyone:
I'm having a problem flashing a ROM. I'm currently on CM 11 from the N7105 forum but would like to revert back to 4.3. I'm trying to flash Skynote Air, the vanilla version. I follow the steps provided and when I try to install the zip, im being given a system 7 error and an error on the zip file. I'm using philz touch CWM by the way. Is it because im on CM11 from the N7105 or is it the zip file? When trying to download the zip file from the ROM thread, it was coming up blank and I downloaded a mirrior. Before the CM11, I was running seanzscreams Sky Note 4.3. Any and all help would be greatly appreciated.
Jestic said:
Hello Everyone:
I'm having a problem flashing a ROM. I'm currently on CM 11 from the N7105 forum but would like to revert back to 4.3. I'm trying to flash Skynote Air, the vanilla version. I follow the steps provided and when I try to install the zip, im being given a system 7 error and an error on the zip file. I'm using philz touch CWM by the way. Is it because im on CM11 from the N7105 or is it the zip file? When trying to download the zip file from the ROM thread, it was coming up blank and I downloaded a mirrior. Before the CM11, I was running seanzscreams Sky Note 4.3. Any and all help would be greatly appreciated.
Click to expand...
Click to collapse
Are you using 5.15 version of Philz ? If so, try updating it.
dicksteele said:
Are you using 5.15 version of Philz ? If so, try updating it.
Click to expand...
Click to collapse
I'm using the 6.19.3 t0lteatt version.
Jestic said:
I'm using the 6.19.3 t0lteatt version.
Click to expand...
Click to collapse
Ahhhh.. Sorry I read but didn't read. Long day.
I read it again and saw the failed downloads.
A hosed zip is probably the case.
Go here
http://forum.xda-developers.com/showthread.php?t=2589891
Try getting back to just 4.3
dicksteele said:
Ahhhh.. Sorry I read but didn't read. Long day.
I read it again and saw the failed downloads.
A hosed zip is probably the case.
Go here
http://forum.xda-developers.com/showthread.php?t=2589891
Try getting back to just 4.3
Click to expand...
Click to collapse
I wonder if anyone has a working zip then.
Jestic said:
I wonder if anyone has a working zip then.
Click to expand...
Click to collapse
Did you download from the copy.com or skynote.com?
I'm grabbing off of the Skynote.com.. Pulling Sky_Note Air Vanilla F1.zip with no problems.. Still have 5 minutes to download.
I'll know if 15 minutes if it's good.
dicksteele said:
Did you download from the copy.com or skynote.com?
I'm grabbing off of the Skynote.com.. Pulling Sky_Note Air Vanilla F1.zip with no problems.. Still have 5 minutes to download.
I'll know if 15 minutes if it's good.
Click to expand...
Click to collapse
Im getting the rom from here :
http://skynote.camattin.com/)?
It downloads with no problem. The problem is when I try to install it from recovery.
Jestic said:
Im getting the rom from here :
http://skynote.camattin.com/)?
Click to expand...
Click to collapse
Same place I just downloaded from.. Copying to phone, flashing in 5.
Only difference is I'm using TWRP as my custom recovery.
Only because personal preference... My fat fingers press buttons on Philz by mistake. I hit reboot 80% of the time before I even do anything.
EDIT: I had a copy of Philz on my phone, philz_touch_6.07.9-t0lteatt.zip. My download flashed fine.
I gotta hit the sack... Good luck
http://www.androidfilehost.com/?fid=23329332407583259
Here's what I used
dicksteele said:
Same place I just downloaded from.. Copying to phone, flashing in 5.
Only difference is I'm using TWRP as my custom recovery.
Only because personal preference... My fat fingers press buttons on Philz by mistake. I hit reboot 80% of the time before I even do anything.
EDIT: I had a copy of Philz on my phone, philz_touch_6.07.9-t0lteatt.zip. My download flashed fine.
I gotta hit the sack... Good luck
Click to expand...
Click to collapse
Interesting. Thanks for the help.
Jestic said:
Interesting. Thanks for the help.
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23329332407583259
Here's what I used
See my post #2361 in seanZscreams SkyNoteAir thread here: http://forum.xda-developers.com/showthread.php?p=50682717
I had same Status 7 error. In PhilZ Touch Recovery ( in version 6.19.3 which is actually 6.19.2) in Install menu, make sure you UNCHECK "Don't allow old binary update" then flash rom. You may have a corrupt data partition (I did). If so, you'll have to wipe /data/media partition. Read my post and reference links. Has to do with the change from CWM base 6045 to 6047 .
DoctorQMM said:
See my post #2361 in seanZscreams SkyNoteAir thread here: http://forum.xda-developers.com/showthread.php?p=50682717
I had same Status 7 error. In PhilZ Touch Recovery ( in version 6.19.3 which is actually 6.19.2) in Install menu, make sure you UNCHECK "Don't allow old binary update" then flash rom. You may have a corrupt data partition (I did). If so, you'll have to wipe /data/media partition. Read my post and reference links. Has to do with the change from CWM base 6045 to 6047 .
Click to expand...
Click to collapse
Thanks for the help. I just installed the latest TWRP and it flashed fine. Thanks.
Jestic said:
Thanks for the help. I just installed the latest TWRP and it flashed fine. Thanks.
Click to expand...
Click to collapse
Glad you're back up and running. .. btw, PhilZ just posted an updated CWM Touch Recovery [6.25.0] for our Note2 [t0lteatt device tree] which now automatically determines if what you're flashing has older binary code embedded in its binary-script to avoid the dreaded Status7 errors.
I had no problems rooting my s3 and putting custom recovery but when I attempt to flash either cyanogenmod or resurrection remix I get the status error 7. Then if I delete the Assert portion I either get status 6 error or it goes into a boot loop and I have to reinstall stock again with odin. I have also downloaded notepad++ as recommended to no avail.
You need to be on at least MD5 bootloader/firmware.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
You need to be on at least MD5 bootloader/firmware.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I just looked on the firmware I flashed on my phone whenever it wouldn't boot and it is md5.
So are you saying you tried to flash MD5 and it would not boot? What were you running before flashing? Did you factory reset?
DocHoliday77 said:
So are you saying you tried to flash MD5 and it would not boot? What were you running before flashing? Did you factory reset?
Click to expand...
Click to collapse
I have tried multiple roms and sometimes got error 7 sometimes error 6 and sometimes unable to boot, at which point I would then flash the stock firmware with odin on it and then it would work again, but I want to be able to put a firmware with kitkat on it.
Youd probably be best off updating to 4.3 firmware if you haven't already. If you're out of warranty there is little reason not to update imo.
Then use twrp 2.7.0.0 for your recovery. Some have had recent problems flashing with cwm.
If you still have issues, let us know exactly what steps you followed and exactly what you were trying to flash.
Sent from my SGH-T999 using Tapatalk
It came with 4.3, that's not the issue, I have tried both twrp and cwm to flash a cyanogenmod kitkat rom and I get the status error 7 at first, if I do what is said to get rid of that and delete the lines at the start then it gets a status error 6. At which point it no longer boots then I need to flash it back to the stock firmware.
Did you try the latest version of either Recoveries ? If its not the latest version you'd get error.
With the 4.3 firmware, you do not have to remove any Assert Lines from the updater Script. Just in case go back to the last stable release of CM 11.
27a
Just updated to a newer cwm to no avail, still getting status 7 error.
What CWM Version is that ?
6.0.4.5
Please post the Recovery Log. Its present in /cache/recovery
62453634 08
I don't see a cache folder
deadly8123 said:
I don't see a cache folder
Click to expand...
Click to collapse
You need a Root Explorer with Root access. Remount System as R/W in your Root Explorer.
Finally was able to do it I flashed a d2lte rom instead of a d2tmo rom.
today all of my apps started crashing and i couldn't do anything but try to get into recovery and flash the dn4v2 rom. but couldn't due to the flashing getting stuck at updating partition details and then error 7 appearing and the flashing failed.
please help me out guys.
Aditya#714 said:
today all of my apps started crashing and i couldn't do anything but try to get into recovery and flash the dn4v2 rom. but couldn't due to the flashing getting stuck at updating partition details and then error 7 appearing and the flashing failed.
please help me out guys.
Click to expand...
Click to collapse
Try using a TWRP recovery, and flash with it.
If still the same, try going back to stock, and then start over.
no success
i was on twrp itself and then switched to cwm and i don't even have my stock backed up so i guess there's nothing that can be done here. but if there is a way then do help.
and i also needed the zip file to get back to twrp.
please help.
Aditya#714 said:
i was on twrp itself and then switched to cwm and i don't even have my stock backed up so i guess there's nothing that can be done here. but if there is a way then do help.
and i also needed the zip file to get back to twrp.
please help.
Click to expand...
Click to collapse
You don't need stock backup to get to stock!
You can boot into download mode, and flash the stock ROM with Odin using PC, that's it.
What is your phone Model number?
So i can give you TWRP link.
yeah. please gimme the link to a twrp zip file and yes i downloaded a stock rom for my samsung note 2 gt n7100 and i even got odin but when i'm trying to put the md5 file in the AP section it stops for some time and then an error message pops up.
the screenshot is attached of the error message that popped up
Aditya#714 said:
the screenshot is attached of the error message that popped up
Click to expand...
Click to collapse
The error is because the stock ROM md5 file is corrupt.
If you want TWRP to flash with odin, then here you are.
https://dl.twrp.me/t03g/twrp-3.0.2-0-t03g.img.tar.html
If you want Stock ROM, then here you go:
https://androidfilehost.com/?fid=24499762636004468