Related
Hello. I did a clean install of MMuzzy's Jelly Bean 4.1.2 JZO54K on my Verizon gnex. After I flash gapps 20121011(via the download listed in the OP for this ROM) my phone won't boot to the OS anymore (it only boots to recovery). I've re downloaded the gapps install in case it was corrupt but it didn't help.
Does anyone have any ideas? Thank you in advance.
Moved for better assistance, Thank you.
i would try a fresh download of the rom and/or gapps. did you check the md5 sum of each? you can find it on the goo.im download page
v3rk said:
i would try a fresh download of the rom and/or gapps. did you check the md5 sum of each? you can find it on the goo.im download page
Click to expand...
Click to collapse
Thank you. Yes I downloaded them twice and the checksums all matched.
my only other thought would be to try a different recovery. which do you use?
v3rk said:
my only other thought would be to try a different recovery. which do you use?
Click to expand...
Click to collapse
Clockwork latest version. Never trouble with it before.
Thanks again.
sstanfie said:
Clockwork latest version. Never trouble with it before.
Thanks again.
Click to expand...
Click to collapse
Recovery wasn't current version.
Hi, let me first begin if there is any problem with my threads. And I want to thank XDA for letting me ask this question, im pretty much a noob from the start..
So, I recently got a replacement S4 (surprisingly from a faulty device on swappa that had warranty) and it was already updated with 4.3 MK2, I have used chainfire's CF-Auto Root and have gotten root and also have installed a custom recovery (CWM.) My problem lies when I want to flash a Custom 4.3 Rom. I have downloaded HyperDrive RSL12 (Mostly because of the note 3 features) and the required files for it. But when I go into recovery and try to flash the rom, the recovery would take a couple of minutes to do something and then say that I can't flash this rom (I saw something under the line of "bad" but I have tried again and again to redownload the rom, so I honestly don't think thats the issue) but this happens to all of the roms I want to install, and I'm not sure if it has something with the KNOX bootloader that came with the phone, but honestly, any help I get is much appreciated! I would gladly give more info to who will help me and I would do almost everything to either install custom rom or 4.2.2 stock!
Sounds like your not rooted
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
Sounds like your not rooted
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hmm.....i mean that is a possibility, i'll try rerooting again, but say if the problem doesn't lie in rooting, what other problem would be associated this?
I'd try a different ROM. That one was first for the international version I believe.
Also, you could try a different recovery. Twrp or Philz. Or just a different version of cwm. Which is what I use.
Sent from my SGH-M919 using XDA Premium 4 mobile app
You can't install stock 4.2.2 since you've updated to the mk2 bootloader (or any room base on 4.2.2). Did you check the md5 of the download file?
☞ Sent from here☜???
baseballfanz said:
You can't install stock 4.2.2 since you've updated to the mk2 bootloader (or any room base on 4.2.2). Did you check the md5 of the download file?
☞ Sent from here☜???
Click to expand...
Click to collapse
I'll be honest,I have no knowledge about md5 in general, but normally would the mk2 bootloader prevent me from installing a modified stock 4.3 rom or a 4.3 custom rom in general?
Android_Monsters said:
I'd try a different ROM. That one was first for the international version I believe.
Also, you could try a different recovery. Twrp or Philz. Or just a different version of cwm. Which is what I use.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For that rom, I was told I could use that rom for the t-mobile variant, but i had to download the compatible pack for that model, and I Have tried TWRP through Goo Manager, but still no luck...
LancerEvoDrifter said:
For that rom, I was told I could use that rom for the t-mobile variant, but i had to download the compatible pack for that model, and I Have tried TWRP through Goo Manager, but still no luck...
Click to expand...
Click to collapse
What version of TWRP are you using? It may just be me, but I spent all last night trying to flash Hyperdrive, Wicked, AND WarpDrive 4.3 and kept having all sorts of problems. Baseband being reported as unknown, no service, phone app FCing, Settings->About Phone->Status would crash settings, WiFi wouldn't connect for anything in the world. I literally spent about 5 hours wiping, flashing, and wiping again. I couldn't even restore an old backup of HyperDrive I had. I started thinking, I recently updated TWRP to 2.6.3.1 and everything was working fine before. I reverted back to 2.6.3.0 and I could restore my backup; I could now flash the 4.3 TW ROMs and get the correct Baseband to report, it all worked right.
TL;DR
Try using an older version of TWRP.
lordcheeto03 said:
What version of TWRP are you using? It may just be me, but I spent all last night trying to flash Hyperdrive, Wicked, AND WarpDrive 4.3 and kept having all sorts of problems. Baseband being reported as unknown, no service, phone app FCing, Settings->About Phone->Status would crash settings, WiFi wouldn't connect for anything in the world. I literally spent about 5 hours wiping, flashing, and wiping again. I couldn't even restore an old backup of HyperDrive I had. I started thinking, I recently updated TWRP to 2.6.3.1 and everything was working fine before. I reverted back to 2.6.3.0 and I could restore my backup; I could now flash the 4.3 TW ROMs and get the correct Baseband to report, it all worked right.
TL;DR
Try using an older version of TWRP.
Click to expand...
Click to collapse
I think I was using the newest version of TWRP. I don't think I have a previous version of TWRP, should I look it up on google for more info about older builds?
LancerEvoDrifter said:
I don't think I have a previous version of TWRP, should I look it up on google for more info about older builds?
Click to expand...
Click to collapse
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
lordcheeto03 said:
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
Click to expand...
Click to collapse
I have flash TWRP ver 2.5.0.2, but I been getting a error message saying this. BTW, this is what the log says when I try to flash the ROM
"Updating partition details...
Running boot script...
Finished running boot script.
E: Unable to open zip file.
Error flashing zip '/external_sd/Hyperdrive RLS12 S4 Final (1).zip'
Updating partition details..."
LancerEvoDrifter said:
I have flash TWRP ver 2.5.0.2, but I been getting a error message saying this. BTW, this is what the log says when I try to flash the ROM
"Updating partition details...
Running boot script...
Finished running boot script.
E: Unable to open zip file.
Error flashing zip '/external_sd/Hyperdrive RLS12 S4 Final (1).zip'
Updating partition details..."
Click to expand...
Click to collapse
Are you able to browse through the zip file on either your computer or a file browser on your phone? If you can't look through the directories within the zip, you have a bad download and will need to re-download it.
lordcheeto03 said:
Are you able to browse through the zip file on either your computer or a file browser on your phone? If you can't look through the directories within the zip, you have a bad download and will need to re-download it.
Click to expand...
Click to collapse
yea, usually when I have a bad download, Winrar would tell me the archive had a unexpected end, but that is not the case in this situation, the file has worked on my dad's s4, but i guess the problem lies in my own device
Tried to delete but don't know how
---------- Post added at 10:13 PM ---------- Previous post was at 10:10 PM ----------
lordcheeto03 said:
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
Click to expand...
Click to collapse
Thanks for the info about using 2.5.0.2. I was finally to install a custom 4.2.2 ROM without a status 7 error.
David
Background:
Decided to fresh install CM via the fancy new installer and just refresh everything.
This wouldn't complete correctly.
Attempted to manually install 10.2 but get an assert failure.
Reinstalled 10.1.3 and it is currently running.
Current problem; CM10.2 / CM11 will not install correctly.
I'm pretty sure its just a matter of updating recovery or something silly but I can't find any concrete information regarding this.
Running: CWM v6.0.4.5
When I attempt to install either version I get an Assert Failed.
Suggestions?
6.0.4.5 is the latest CWM.
Are you sure you are choosing the CM for YOUR device ?
Perseus71 said:
6.0.4.5 is the latest CWM.
Are you sure you are choosing the CM for YOUR device ?
Click to expand...
Click to collapse
Pretty sure, since if I choose 10.1.3 and install it from the same download page it works.
I've always used d2tmo
It's a Samsung Galaxy S3 from WIND mobile.
Mod: SGH-T999V
I've tried the following CM versions from get.cm
cm-10.2.0-RC1-d2tmo.zip
cm-11-20140104-SNAPSHOT-M2-d2tmo.zip
cm-10.2-20131102-SNAPSHOT-M1-d2tmo.zip
If that's the case then edit the updater script and add your device to the Asserts or remove them alltogether.
Perseus71 said:
If that's the case then edit the updater script and add your device to the Asserts or remove them alltogether.
Click to expand...
Click to collapse
Yeah my baseband is currently T999VVLLH2 when looking at about phone, which I don't see in the list when its failing the assert.
Currently failing looking for;
T999UVDLJA
T999UVDLJC
T999UVDMD5
T999UVUEMJC
T999VVLDLL1
T999LUVAMB7
T999VVLDMF2
T999VVLUEMK5
Vyr1s said:
Yeah my baseband is currently T999VVLLH2 when looking at about phone, which I don't see in the list when its failing the assert.
Currently failing looking for;
T999UVDLJA
T999UVDLJC
T999UVDMD5
T999UVUEMJC
T999VVLDLL1
T999LUVAMB7
T999VVLDMF2
T999VVLUEMK5
Click to expand...
Click to collapse
Updated my baseband to match "T999VVLUEMK5".
Still failing though.
Vyr1s said:
Updated my baseband to match "T999VVLUEMK5".
Still failing though.
Click to expand...
Click to collapse
Updated to the newest bootloader, updated the modem again, finally accepted CM11 snapshot, installed gapps for KK and everything is gravy now.
Vyr1s said:
Updated to the newest bootloader, updated the modem again, finally accepted CM11 snapshot, installed gapps for KK and everything is gravy now.
Click to expand...
Click to collapse
Its not the baseband but the Bootloader that it was looking for. So when you updated the bootloader, it accepted that. Glad its all sorted out.
Vyr1s said:
Updated to the newest bootloader, updated the modem again, finally accepted CM11 snapshot, installed gapps for KK and everything is gravy now.
Click to expand...
Click to collapse
Hi,
I am having the same issue, can you point me the thread that shows the step by step procedure to update my boatloader pls
dealguy007 said:
Hi,
I am having the same issue, can you point me the thread that shows the step by step procedure to update my boatloader pls
Click to expand...
Click to collapse
Try this thread.
I'm trying to help out a friend and update his Galaxy S3 SGH-I747. He originally had cyanogenmod installed but he restored his phone back to stock and flashed a stock recovery back to the phone. When he tries to do an OTA updated it downloads but fails to install? His current android version is 4.1.1 but his baseband is I747UCUFNE4 which if im not mistaken is for android 4.4.2 what would be the easiest way to get his phone updated to the stock 4.4.2 software?
Follow one of enewman17's how to update threads in General.
4.4.2 upgrade stops at 28%
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
Can you be a bit more specific?
Thanks
bmoliver said:
Can you be a bit more specific?
Thanks
Click to expand...
Click to collapse
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
BWolf56 said:
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
Click to expand...
Click to collapse
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
EDIT: One more thing that I observed is when I am trying flash something in the download mode, I get the error and "sw rev check fail fused 3 binary 0" and it fails
Thanks,
CJ
bmoliver said:
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Click to expand...
Click to collapse
jchennuri said:
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
Thanks,
CJ
Click to expand...
Click to collapse
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
BWolf56 said:
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
Click to expand...
Click to collapse
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
BWolf56 said:
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
Click to expand...
Click to collapse
jchennuri said:
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
Click to expand...
Click to collapse
What error did you get when flashing it?
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
BWolf56 said:
What error did you get when flashing it?
Click to expand...
Click to collapse
jchennuri said:
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
Click to expand...
Click to collapse
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
BWolf56 said:
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Click to expand...
Click to collapse
jchennuri said:
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
Click to expand...
Click to collapse
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
BWolf56 said:
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
Click to expand...
Click to collapse
There isn't a NE4 stock for Odin. I just noticed the post hasn't been updated in a while.
I though I could find it on Sammobile.com but they have LK3 as their latest too.
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Thanks Doc!
Hopefully enewman17 can come up with a solution for this.
Just an information which I was not able to completely comprehend but maybe pros like you or Bwolf56 will be able to.
I opened Kies and this is what it says.
Firmware information
This is the latest firmware.
Current firmware version: PDA:LK3 / PHONE:NE4 / CSC:LK3 (ATT)
Any thoughts on how do I get the PDA and CSC updated (not even sure what exactly they are)
Thanks
DocHoliday77 said:
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Click to expand...
Click to collapse
Ok, enewman17 just put this together if you want to try it. This includes the full NE4 stock firmware minus system, kernel, cache and recovery.
So flashing it will preserve your current Rom, kernel and recovery, but will otherwise fully update your base firmware/bootloaders to NE4.
This should be perfectly safe to use, but seeing as it is untested, I cannot make any guarantees that it won't make things worse. (I wouldn't post it if I thought it would, but there is always the possibility)
Flash from custom recovery such as TWRP.
http://www.androidfilehost.com/?fid=23578570567716667
Sent from my SGH-T999 using Tapatalk
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
If you want to fully update your system (rom) to stock NE4, enewman17 has a thread in the development section with stock rooms you can flash via recovery after you update your firmware posted above.
Sent from my SGH-T999 using Tapatalk
I rooted to a 4.4 ROM and have been getting several reboots and I am clueless as to what the problem could be. I have decided that I would like to factory restore my phone and play around with rooting ROMS in the near future, so i tried restoring it today by flashing a zip file in recovery but I got an error in attempting to do so.
I have no idea what to do, and I'm so stumped...thank you for taking your time in reading this post.
EDIT
Current and Previous Rom: CURRENT is Task650's 7.29.2014 KitKat Rom (4.4.4, unified); PREVIOUS is Quantum's 5.2 KitKat Rom (4.4.4)
Current firmware build: Current firmware build is I747UCUEMJB
What did you try to flash? I tried flashing a AT&T I747 UCUEMJB Stock Restore.
What recovery? I have Clockword Mod Touch Recovery 6.0.4.7
What error?
" -- Installing: /sdcard/0/Download/ATT_I747_UCUEMJB_StockRestore_2282014.zip
Finding update package...
Opening update package...
E: Can't open /data/media/0/Download/ATT_I747_UCUEMJB_StockRestore-2282014.zip
(bad)
Installation aborted.
I:using /data/media for /sdcard/0/clockwordmod/.last_install_path.
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1"
Need more info to be able to help.
Current and Previous Rom
Current firmware build
What did you try to flash?
What recovery?
What error?
The best way to revert to full stock though is to flash the firmware with Odin.
DocHoliday77 said:
Need more info to be able to help.
Current and Previous Rom
Current firmware build
What did you try to flash?
What recovery?
What error?
The best way to revert to full stock though is to flash the firmware with Odin.
Click to expand...
Click to collapse
I apologize for the lack of info. I updated the original post with information WITHOUT the firmware build. How may I find that? I'm going to reproduce the error so give me a sec to give you that information as well.
I appreciate your help Doc!
To verify your current firmware/bootloader version, install terminal emulator and enter this:
getprop ro.bootloader
It will depend on what the error is to figure a way to get that particular package to flash. You could also try using TWRP or Philz recoveries.
After it fails, there should be an option to copy log to sd. (Its in the Advanced menu in TWRP, not sure about CWM)
But if it continues to give problems, flashing the firmware via Odin will be the most likely solution. The 4.3 firmware for this is in a thread in the General section.
http://forum.xda-developers.com/showthread.php?p=52006506
DocHoliday77 said:
To verify your current firmware/bootloader version, install terminal emulator and enter this:
getprop ro.bootloader
It will depend on what the error is to figure a way to get that particular package to flash. You could also try using TWRP or Philz recoveries.
After it fails, there should be an option to copy log to sd. (Its in the Advanced menu in TWRP, not sure about CWM)
But if it continues to give problems, flashing the firmware via Odin will be the most likely solution. The 4.3 firmware for this is in a thread in the General section.
http://forum.xda-developers.com/showthread.php?p=52006506
Click to expand...
Click to collapse
I updated the OP with the current firmware build and the error I get.
More explanation on the error: In the thread where I found the zip file, it instructs the zip file to be flashed via TWRP recovery or CWM recovery, so I am stumped as to what I could have done wrong. Thanks Doc!
It may be a bad download. Did you check the md5?
I recommend downloading the stock firmware from the link I posted and flash that with Odin.
I tried getting the md5 verification, but I couldn't get it working. Probably was a mistake on my part in that I misunderstood the directions to check the md5.
Doc, I will use the link you provided me and flash the DL via Odin. I'll get back to you as soon as I do so. Thank you so much for the help, this is definitely a learning experience for me.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app