Related
ok so noob here, well not so new but with this phone, yes. I downloaded the update and the stock rom from here and first i tried the update alone and failed said something bout assert failed.. then i read more of the thread and so i tried install the stock rom from cwm but it also failed same assert failed error. some help would be highly appreciated
jodady23 said:
ok so noob here, well not so new but with this phone, yes. I downloaded the update and the stock rom from here and first i tried the update alone and failed said something bout assert failed.. then i read more of the thread and so i tried install the stock rom from cwm but it also failed same assert failed error. some help would be highly appreciated
Click to expand...
Click to collapse
Can you be a little more specific about what you did. What have you done to your phone so far?
I belive you can't be rooted to install an ota update
Sent from my SGH-T999 using xda premium
well yeah i only rooted it but ok ill try to unroot then try again
Do this
http://forum.xda-developers.com/showthread.php?p=31278065
Pretty sureroot is ok. But you do have to be stock recovery, system, modem...
No mods no debloating.
And with otas you must be on the correct build to start with. Usually UVALH2.
Sent from my SGH-T999 using xda app-developers app
ok so it went thru and i updated it and everything but when i try to reinstall cwm it doesnt work and for some reason netfix closes when i try to watch a video
jodady23 said:
ok so it went thru and i updated it and everything but when i try to reinstall cwm it doesnt work and for some reason netfix closes when i try to watch a video
Click to expand...
Click to collapse
Do you mean it stays stock recovery? Or does it fail when flashing?
If its the first one, and you're still rooted delete /system/recovery-from-boot.p
And
/system/etc/install-recovery.sh
Then reinstall recovery.
Sent from my SGH-T999 using xda app-developers app
Hi there,
I have a Galaxy SIII SGH-i747 from Virgin in Canada. As for as I know, its the same as Bell and every other SGH-i747. So tonight I tried flashing cyanogenmod 10.1 to no avail. I have rooted and installed CWM. When I try to install any ROM it comes up with the error "assert failed getprop status 7". I have searched around and have tried updating CWM recovery through ROM Manager from the play store, but the app doesn't allow me to select my phone model (says there is no official release of CWM for SGH-i747) and says the current version will do. This ROM does not want to install.
HELP!:crying:
disengage said:
Hi there,
I have a Galaxy SIII SGH-i747 from Virgin in Canada. As for as I know, its the same as Bell and every other SGH-i747. So tonight I tried flashing cyanogenmod 10.1 to no avail. I have rooted and installed CWM. When I try to install any ROM it comes up with the error "assert failed getprop status 7". I have searched around and have tried updating CWM recovery through ROM Manager from the play store, but the app doesn't allow me to select my phone model (says there is no official release of CWM for SGH-i747) and says the current version will do. This ROM does not want to install.
HELP!:crying:
Click to expand...
Click to collapse
Status 7 is an out of date recovery or incorrect recovery.
You need a d2att recovery. The Canadian models are d2can. Same phone but it is a system fail safe.
Flash either one in recovery, reboot back into recovery, wipe and enjoy cm10.1
http://d-h.st/8qP cwm
http://d-h.st/qft cwm touch
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
sending onalond
KorGuy123 said:
Status 7 is an out of date recovery or incorrect recovery.
You need a d2att recovery. The Canadian models are d2can. Same phone but it is a system fail safe.
Flash either one in recovery, reboot back into recovery, wipe and enjoy
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Just to be clear: Load the CWM you linked onto SD. Reboot into CWM, flash new CWM, reboot and wipe?
Also to clarify, I have a Canadian model SGHi747
disengage said:
Just to be clear: Load the CWM you linked onto SD. Reboot into CWM, flash new CWM, reboot and wipe?
Also to clarify, I have a Canadian model SGHi747
Click to expand...
Click to collapse
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Okay thanks, I will try later and reply with results.
KorGuy123 said:
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Also should I flash with ODIN?
disengage said:
Also should I flash with ODIN?
Click to expand...
Click to collapse
No recovery.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
No recovery.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Hi there, I tried flashing from recovery, choosing zip from sdcard, and I got the same exact error assert failed: getprop(" ro.product.device") == "d2att" || getprop( " ro.build.product " ) == "d2att" E:Error in /sdcard/CWM-recovery_ATT-6.0.2.3_2.zip
(status 7)
Installation aborted.
I tried exactly what you said, still nothing.
Bump.
Did you have the most recent stock rom before flashing cyanogenmod? The newer versions of the nightlies require that you have the most recent bootloader. If you had ics, it'll fail to flash until you update your bootloader. The most recent build before the bootloader assert that you can flash is rc2.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
Did you have the most recent stock rom before flashing cyanogenmod? The newer versions of the nightlies require that you have the most recent bootloader. If you had ics, it'll fail to flash until you update your bootloader. The most recent build before the bootloader assert that you can flash is rc2.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I think so. i have no idea how to check, forgive the noobness plz. My stock firmware is 4.1.1
Bump? Does anyone know how I can flash an updated recovery?
disengage said:
Bump? Does anyone know how I can flash an updated recovery?
Click to expand...
Click to collapse
The link I gave you is the most up to date recovery. There is a thread here for most recent stock roms. Quick search will assist you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
The link I gave you is the most up to date recovery. There is a thread here for most recent stock roms. Quick search will assist you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I understand that, but I cannot flash the updated CWM. What am I doing wrong?
Okay, so I see people are trying to help me but it's so vague. Every article or how to, or help page ive read on this site or others, suggest conflicting ways to perform these mods. Why can't anyone just tell me straight up, you do this, then this, then that? I feel it shouldnt be this much of a headache and before I've even started modding, I'm getting very turned off. I am already frustrated beyond comprehension. Like I said, I've searched, and searched and nothing is helping. Everything is too vague.
So my question stands: I flashed an outdated recovery by accident, and I want to flash a new, UPDATED recovery. KorGuy provided me with instructions and a link to a new, updated recovery, however I cannot flash that from my current recovery.
What can I do to flash an updated CWM?
Can someone give me a hand?
You need to flash the most recent STOCK firmware through ODIN so you will have the most recent bootloader, then flash your recovery of choice through ODIN, boot into recovery, not system as the recovery will be overwritten iirc. Then flash cm in recovery
Sent from my SGH-T999 using Tapatalk 2
disengage said:
Okay, so I see people are trying to help me but it's so vague. Every article or how to, or help page ive read on this site or others, suggest conflicting ways to perform these mods. Why can't anyone just tell me straight up, you do this, then this, then that? I feel it shouldnt be this much of a headache and before I've even started modding, I'm getting very turned off. I am already frustrated beyond comprehension. Like I said, I've searched, and searched and nothing is helping. Everything is too vague.
Can someone give me a hand?
Click to expand...
Click to collapse
If you can't follow a guide like this and figure things out, maybe flashing ROMs just isn't for you. I'm not trying to offend, but this isn't for everyone.
danieljordanmaddux said:
You need to flash the most recent STOCK firmware through ODIN so you will have the most recent bootloader, then flash your recovery of choice through ODIN, boot into recovery, not system as the recovery will be overwritten iirc. Then flash cm in recovery
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I understand that I need to flash with ODIN. However, don't I need a .TAR recovery? I can't flash .img through ODIN...
Correct. Find the .tar of the recovery. I think you can find the TWRP .tar on their website
Sent from my SGH-T999 using Tapatalk 2
Root your phone and install a custom recovery. Most root guides will include instructions for flashing a custom recovery. Next buy "ROM toolbox" form android market, I say by because you will love this app so much you will want to buy it eventually anyway.
Open ROM toolbox and select cyanogen mod. ROM toolbox will flash your phone for you! It can also flash the custom recovery if you did not do this when you rooted your phone.
Annnother must have root app is titanium backup.
Hope this helps.
Sent from my Nexus 4 using xda app-developers app
I am trying to upgrade my Virgin ROM to the 9.12 build but get a fail upon trying to flash it. The background.... I'm using TWRP recovery and have tried the chainfire root method. Here are the results:
As you can see you can see some conflicting information... all shots were taken in sequence. I'm thinking the fail in twrp is coming from the system not having root but the info is telling me otherwise....
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Do you have the latest SuperSU version?
I'm a little lost at what you are saying.
You flashed a rom, and it said fail, and you think it has to do with Root?
If you have TWRP installed it doesn't matter if you are rooted or not. It's going to over right the system partition regardless if you have root or not.
So it's either a bad download or bad transfer for it to fail.
Sent from my SGH-M919 using Tapatalk 4
I do have the latest SU version by chain fire. And maybe I'm doing something wrong the because I am running the virgin gpe ROM now and that flashed in twrp with no issues. Now when I go to install (after wiping) and select the 9.12 update that I downloaded it hangs on trying to open the zip and fails... I haven't changed any twrp settings but in the write options of twrp what boxes should be checked because system is not by default... Thanks for the replies!
Sent from my GT-I9505G using xda app-developers app
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
You can give CWM a try, I've been using it for a while without any issues. Out of curiosity what version if TWRP you are using? I think most people recommend TWRP 2.5.0.2. I'm using the latest version of CWM.
Sent from my GT-I9505G using xda app-developers app
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
norml said:
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
Click to expand...
Click to collapse
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
th3h0ff said:
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
Click to expand...
Click to collapse
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
mrvirginia said:
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
Click to expand...
Click to collapse
Im going to give the twrp 2.5.2 a try as it seems most of my troubles keep happening on the 2.6.3 build. Hopefully that works either way its back to CWM for me as well. Thanks again for taking the time to help out and again sorry about hijacking the thread for a page... Your ROM is absolutely perfect so I appreciate the efforts and time!,
Andrew
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
th3h0ff said:
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
Click to expand...
Click to collapse
Good to know you are out of trouble
Sent from my Nexus 10 using xda app-developers app
See you shoulda said you were running 2.6.3 lol
word of advice (and to all who run twrp)
DO NOT RUN ANYTHING GREATER THAN 2.5.2!!!!!!!!!!!!!!
I've been installing custom ROMs on android devices since the very first DROID and never bricked a phone I couldn't fix until now. I've been using custom ROMs on my l900 without any problems at all until the 4.3 ROMs started coming out. I had a lot of trouble trying to get Synergy with the 4.3 update installed on my phone but eventually got it up and working but without root access. Eventually got it rooted but it hasn't really been working right since then. I switched over to Smoothest ROM most recently and ran into a weird problem where I noticed my preferred browser Dolphin was no longer on my system. Tried downloading it and got an error, tried restoring it from a Titanium backup and got an error. Also tried installing Chrome and that wouldn't work.
At this point the 2.3 update for Smoothest ROM was out and so I copied the installer onto my mSD card, booted into recover, wiped data/system/cache/dalvik cache and installed the ROM. This is where my trouble started because I got an error saying it couldn't access part of the internal storage. So I combed the XDA forms (and thank you all for all your amazing contributions) and tried every suggestion I could find including formatting the internal storage partition and trying to install the Stock_MK4_w_Note3_v1.3-tester- signed-20140208_181306 and nothing is working. I still get I/O errors and my phone is totally bricked so I am hoping someone can read this and help me get my baby back :crying:.
RACU73 said:
I've been installing custom ROMs on android devices since the very first DROID and never bricked a phone I couldn't fix until now. I've been using custom ROMs on my l900 without any problems at all until the 4.3 ROMs started coming out. I had a lot of trouble trying to get Synergy with the 4.3 update installed on my phone but eventually got it up and working but without root access. Eventually got it rooted but it hasn't really been working right since then. I switched over to Smoothest ROM most recently and ran into a weird problem where I noticed my preferred browser Dolphin was no longer on my system. Tried downloading it and got an error, tried restoring it from a Titanium backup and got an error. Also tried installing Chrome and that wouldn't work.
At this point the 2.3 update for Smoothest ROM was out and so I copied the installer onto my mSD card, booted into recover, wiped data/system/cache/dalvik cache and installed the ROM. This is where my trouble started because I got an error saying it couldn't access part of the internal storage. So I combed the XDA forms (and thank you all for all your amazing contributions) and tried every suggestion I could find including formatting the internal storage partition and trying to install the Stock_MK4_w_Note3_v1.3-tester- signed-20140208_181306 and nothing is working. I still get I/O errors and my phone is totally bricked so I am hoping someone can read this and help me get my baby back :crying:.
Click to expand...
Click to collapse
Read the last few pages of the thread. I have answered this issue over and over again. If you want help and willing to follow the directions step by step I can help.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Yes please
jlmancuso said:
Read the last few pages of the thread. I have answered this issue over and over again. If you want help and willing to follow the directions step by step I can help.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm not seeing a link to any thread but yes I want help and willing to follow your directions.
jlmancuso said:
Read the last few pages of the thread. I have answered this issue over and over again. If you want help and willing to follow the directions step by step I can help.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Also I tried your suggestion from this thread step by step and it fails when I flash the ROM.
http://forum.xda-developers.com/showthread.php?t=2542036
I get an error when its trying to install the radio that says "Error executing updater binary in zip"
This did work the first time I tried it in that I was able to at least get the stock Samsung boot animation to play but then it just stayed on that animation over night.
RACU73 said:
Also I tried your suggestion from this thread step by step and it fails when I flash the ROM.
http://forum.xda-developers.com/showthread.php?t=2542036
I get an error when its trying to install the radio that says "Error executing updater binary in zip"
This did work the first time I tried it in that I was able to at least get the stock Samsung boot animation to play but then it just stayed on that animation over night.
Click to expand...
Click to collapse
Also I just realized I pasted the title of the wrong file. The ROM I am trying to install is MC2_STOCK_with_COUNT_RESET-20130511.zip
RACU73 said:
Also I just realized I pasted the title of the wrong file. The ROM I am trying to install is MC2_STOCK_with_COUNT_RESET-20130511.zip
Click to expand...
Click to collapse
Can you link that thread? Sounds like it was not for your device.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
Can you link that thread? Sounds like it was not for your device.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here is the thread
http://forum.xda-developers.com/showthread.php?t=2542036
and this is what I tried
1. Boot phone into Odin/download mode
2. Flash twrp or cwmr via Odin.
3. When it reboots pull battery and then boot into recovery.
4. Flash this http://forum.xda-developers.com/show...php?p=36388145 it is mc2 bootloader, firmware, radio, etc...
5. Reboot phone. Things get weird for a few mins but it will boot.
You are now Knox free once again but you are also bone stock.
Sent from my SPH-L900 using XDA Premium 4 mobile app
If everything else has failed it sounds like you need to odin the official stock rom. Did you take the OTA update to 4.3 or just flashed a 4.3 rom on top of 4.1.2? Are you trying to get back to stock MC2 4.1.2 or stock MK4 4.3?
Sent from my Knox Free Galaxy Note2 using SkyBlue Tapatalk 2
RACU73 said:
Here is the thread
http://forum.xda-developers.com/showthread.php?t=2542036
and this is what I tried
1. Boot phone into Odin/download mode
2. Flash twrp or cwmr via Odin.
3. When it reboots pull battery and then boot into recovery.
4. Flash this http://forum.xda-developers.com/show...php?p=36388145 it is mc2 bootloader, firmware, radio, etc...
5. Reboot phone. Things get weird for a few mins but it will boot.
You are now Knox free once again but you are also bone stock.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure what your problem is. In this post it sounds like everything is done. What do you need help with?
Sent from my SPH-L900 using XDA Premium 4 mobile app
srod562 said:
If everything else has failed it sounds like you need to odin the official stock rom. Did you take the OTA update to 4.3 or just flashed a 4.3 rom on top of 4.1.2? Are you trying to get back to stock MC2 4.1.2 or stock MK4 4.3?
Sent from my Knox Free Galaxy Note2 using SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Ideally I'd like to get back to stock MK4 4.3 but what I want most is a working Note 2. I had already switched from MC2 4.1.2 to MK4 4.3 and installed a 4.3 ROM.
Where can I get the Samsung stock 4.3 rom?
towards ndffig
jlmancuso said:
Not sure what your problem is. In this post it sounds like everything is done. What do you need help with?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry for the confusion jmancuso. I followed the instruction you posted on another thread but they only got me as far as the Samsung animation. at the moment the only thing I can run on my phone is TWRP but it can't install anything without running it some kind of error.
RACU73 said:
Sorry for the confusion jmancuso. I followed the instruction you posted on another thread but they only got me as far as the Samsung animation. at the moment the only thing I can run on my phone is TWRP but it can't install anything without running it some kind of error.
Click to expand...
Click to collapse
Sorry got this thread confused with another.
What is the exact error you get?
Sent from my SPH-L900 using XDA Premium 4 mobile app
RACU73 said:
Ideally I'd like to get back to stock MK4 4.3 but what I want most is a working Note 2. I had already switched from MC2 4.1.2 to MK4 4.3 and installed a 4.3 ROM.
Where can I get the Samsung stock 4.3 rom?
Click to expand...
Click to collapse
Here's a link to the MK4 stock odin tar rom. You could try installing the original tar and see if that works. Hope this helps.
http://www.rwilco12.com/downloads.p...sung Galaxy Note II (SPH-L900)/Stock ROMs/MK4
Sent from my Knox Free Galaxy Note2 using SkyBlue Tapatalk 2
occasioned pyirstr
jlmancuso said:
Sorry got this thread confused with another.
What is the exact error you get?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well part of the debug output seems to be getting cut off but here is what I see
Installing Radio...
assert failed: package_extract_file("modem.bin"
E:error executing updater binary in zip '/extern
Error flashing zip '/external_sdcard/MC2_STOCK_w
hoesoc because
srod562 said:
Here's a link to the MK4 stock odin tar rom. You could try installing the original tar and see if that works. Hope this helps.
http://www.rwilco12.com/downloads.p...sung Galaxy Note II (SPH-L900)/Stock ROMs/MK4
Sent from my Knox Free Galaxy Note2 using SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Thanks for the link. I extracted the file, put the phone into Download mode, plugged in the USB cable and this is what I get.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
RACU73 said:
Well part of the debug output seems to be getting cut off but here is what I see
Installing Radio...
assert failed: package_extract_file("modem.bin"
E:error executing updater binary in zip '/extern
Error flashing zip '/external_sdcard/MC2_STOCK_w
Click to expand...
Click to collapse
What version of twrp? Also did ypu check the md5sum of the download for mc2 stock with counter reset?
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
What version of twrp? Also did ypu check the md5sum of the download for mc2 stock with counter reset?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My version of TWRP is 2.6.3.1
according to TWRP the file doesn't have a md5 file.
I'm starting to think I contracted some nasty piece of malware because things seem to keep getting work. Now I'm getting errors saying their isn't a partition table.
RACU73 said:
My version of TWRP is 2.6.3.1
according to TWRP the file doesn't have a md5 file.
I'm starting to think I contracted some nasty piece of malware because things seem to keep getting work. Now I'm getting errors saying their isn't a partition table.
Click to expand...
Click to collapse
Ouch! To fix that you need a new pit for odin. I will see what I can find for you.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
Ouch! To fix that you need a new pit for odin. I will see what I can find for you.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well what's happening is when I try to install any ROM now i get the usual write errors but then I get a few lines that say "Updating partition details..." but that's it. Since I'm not getting a notification that the partition details was successful I'm guessing it means that the their might be something wrong with the partition table.
Also I can't wipe data, cache, and system. I keep getting an error.
RACU73 said:
Well what's happening is when I try to install any ROM now i get the usual write errors but then I get a few lines that say "Updating partition details..." but that's it. Since I'm not getting a notification that the partition details was successful I'm guessing it means that the their might be something wrong with the partition table.
Also I can't wipe data, cache, and system. I keep getting an error.
Click to expand...
Click to collapse
Try wiping with cwm or philz and as I said I will look into getting a pit file tp use in odin.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?
BWolf56 said:
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?
Click to expand...
Click to collapse
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.
BWolf56 said:
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.
Click to expand...
Click to collapse
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's in your System folder. Should be able to navigate to it using your recovery.
BWolf56 said:
It's in your System folder. Should be able to navigate to it using your recovery.
Click to expand...
Click to collapse
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?
donutkidd said:
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?
Click to expand...
Click to collapse
Hopefully it is. And I duno about the command, you'll have to look that one up (or perhaps someone here knows it).
If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk
Ok I will try that when I get home.
Sent from my SM-N900T using XDA Premium 4 mobile app
DocHoliday77 said:
If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Ok I did the getprop ro.bootloader command and it's I747UCDLK3. I have already tried the lk3 Odin but let me try to re download a fresh copy of it.
Sent from my SM-N900T using XDA Premium 4 mobile app
No dice, I even downloaded a 4.1.1 lk3 rom. It flashed and said successful so I rebooted and back to the blue Android. Is it possible NY partitions or whatever are corrupt and if so anyway to fix it?
Sent from my SM-N900T using XDA Premium 4 mobile app
I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.
DocHoliday77 said:
I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.
Click to expand...
Click to collapse
I honestly think I tried what you suggested already but just to triple check I will do so again in the morning and report back with hopefully good news.
Sent from my SM-N900T using XDA Premium 4 mobile app
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
No, nothing for 4.1.1 (LK3).
I don't think that's his issue though. Last time I saw that issue was on the S1 (Captivate) and the solution was to use Heimdall.
If the repartition doesn't work though, I'm not exactly sure what will.
DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.
donutkidd said:
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.
Click to expand...
Click to collapse
Do you have the actual link to that thread? Search is derping on me.
BWolf56 said:
Do you have the actual link to that thread? Search is derping on me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ouff that's one bad issue, it can take a while to figure out which partition got messed up. And sadly, I can't be much help there :/