Related
Hi everyone! Sorry if this is a noobish question or troubleshoot
I don't know what's going on but whenever I tried flashing awesome looking AT&T ROMs (JB 4.3 ROMs) onto my SGS3 T-999, I keep getting an error about some build prop thing then it says "Failed" I then try to Wipe Cache and Dalvik Cache, but it fails so I would restart my phone back into recovery then resort to flashing a T-Mobile ROM to get my phone up again. Not sure if I'm wrong or not, but I've read that I'm able to flash an AT&T ROM onto a T-Mobile phone because of something. Anywhere I looked, AT&T and T-Mobile SGS3 forum I've found that it's okay to flash one others' rom besides the modem.
Is it the version of TWRP? Anything other than that?
If anyone could help me troubleshoot this problem, I greatly appreciate all who does :good:
Here's a brief summary for all. SGS3 T-999, read it was okay to flash ROMs, used TWRP 2.6.3.0 to flash AT&T [JB 4.3] ROMs, and only ROMs failed while flashing, don't know why. Google'd for solutions, but I guess that didn't work and took a lot of time.
dinodustin said:
Hi everyone! Sorry if this is a noobish question or troubleshoot
I don't know what's going on but whenever I tried flashing awesome looking AT&T ROMs (JB 4.3 ROMs) onto my SGS3 T-999, I keep getting an error about some build prop thing then it says "Failed" I then try to Wipe Cache and Dalvik Cache, but it fails so I would restart my phone back into recovery then resort to flashing a T-Mobile ROM to get my phone up again. Not sure if I'm wrong or not, but I've read that I'm able to flash an AT&T ROM onto a T-Mobile phone because of something. Anywhere I looked, AT&T and T-Mobile SGS3 forum I've found that it's okay to flash one others' rom besides the modem.
Is it the version of TWRP? Anything other than that?
If anyone could help me troubleshoot this problem, I greatly appreciate all who does :good:
Here's a brief summary for all. SGS3 T-999, read it was okay to flash ROMs, used TWRP 2.6.3.0 to flash AT&T [JB 4.3] ROMs, and only ROMs failed while flashing, don't know why. Google'd for solutions, but I guess that didn't work and took a lot of time.
Click to expand...
Click to collapse
Use AT&T recovery or edit update script to remove d2att asserts. Recommend editing over AT&T recovery.
Aerowinder said:
Use AT&T recovery or edit update script to remove d2att asserts. Recommend editing over AT&T recovery.
Click to expand...
Click to collapse
Just to make sure I undertand. Could I flash an AT&T TWRP recovery on my T-999 without any problems? So like, I got the d2tmo version on my phone, I could just put in the d2att one, right?
I also read in a ROM thread about changing the d2att asserts (maybe to d2tmo?), not removing, will it still work?
dinodustin said:
Just to make sure I undertand. Could I flash an AT&T TWRP recovery on my T-999 without any problems? So like, I got the d2tmo version on my phone, I could just put in the d2att one, right?
I also read in a ROM thread about changing the d2att asserts (maybe to d2tmo?), not removing, will it still work?
Click to expand...
Click to collapse
Correct on both. I don't recommend changing the recovery though. It will work, but I don't think it's a good idea to do it. Also, after flashing, be certain that you change the build.prop back to d2tmo. So things like Mobile ODIN don't brick your phone.
Aerowinder said:
Correct on both. I don't recommend changing the recovery though. It will work, but I don't think it's a good idea to do it. Also, after flashing, be certain you change the build.prop back to d2tmo. So things like Mobile ODIN don't brick your phone.
Click to expand...
Click to collapse
So edit the build.prop by removing the d2att asserts in it, flash ROM in recovery, then edit build.prop again by adding d2tmo to where I removed the d2att asserts? Or I might as well change all the d2att asserts in the build.prop to d2tmo then flash
dinodustin said:
So edit the build.prop by removing the d2att asserts in it, flash ROM in recovery, then edit build.prop again by adding d2tmo to where I removed the d2att asserts? Or I might as well change all the d2att asserts in the build.prop to d2tmo then flash
Click to expand...
Click to collapse
No.
Edit the update-script file to remove (or replace) the asserts.
Edit build.prop to d2tmo
Flash the ROM.
You can edit the build.prop after the flash, but since you're already editing the zip archive... why do it twice.
Aerowinder said:
No.
Edit the update-script file to remove (or replace) the asserts.
Edit build.prop to d2tmo
Flash the ROM.
You can edit the build.prop after the flash, but since you're already editing the zip archive... why do it twice.
Click to expand...
Click to collapse
Okay, here's a screenshot of an updater script from an AT&T ROM (left) and T-Mobile ROM (right).
Do I change the highlighted on the AT&T one to look like the T-Mobile one?
And for the build prop part, am I only changing the d2att to d2tmo?
dinodustin said:
Okay, here's a screenshot of an updater script from an AT&T ROM (left) and T-Mobile ROM (right).
Do I change the highlighted on the AT&T one to look like the T-Mobile one?
And for the build prop part, am I only changing the d2att to d2tmo?
Click to expand...
Click to collapse
That should do the trick.
Aerowinder said:
That should do the trick./QUOTE]
I was a little confused of the build.prop part cos it had some other AT&T information in there that I didn't know if I should change to look like the T-Mobile's build.prop. I'll try it out and come back to let you know how it goes.
Click to expand...
Click to collapse
dinodustin said:
Aerowinder said:
That should do the trick./QUOTE]
I was a little confused of the build.prop part cos it had some other AT&T information in there that I didn't know if I should change to look like the T-Mobile's build.prop. I'll try it out and come back to let you know how it goes.
Click to expand...
Click to collapse
That's true but it doesn't matter. Just the d2tmo and maybe SGH-T999.
Click to expand...
Click to collapse
Aerowinder said:
That's true but it doesn't matter. Just the d2tmo and maybe SGH-T999.
Click to expand...
Click to collapse
Alright, making some changes atm and I'll get back to you to let you know how everything goes.
Edit: so I'm still getting errors ): I got like a "Status 7" error at some point, then a "Status 6" when I tried to flash the edited zip. Any other possible solutions? Maybe extract all the files, edit updater-script and build.prop then re-archive? No?
Aerowinder said:
dinodustin said:
That's true but it doesn't matter. Just the d2tmo and maybe SGH-T999.
Click to expand...
Click to collapse
Solved a while ago, this can be closed. Thank you @Aerowinder for helping me out here and @Danvdh for helping me out in the AT&T GS3 thread :good:
Click to expand...
Click to collapse
Good Evening all,
I have a T-mobile Galaxy S3 that was rooted. That I took back to stock and unrooted using Odin and T999UVALEM_T999TMBALEM_T999UVALEM_HOME.tar......I let the phone sit for about 25-30 min and it never really made it past the pulsing SAMSUNG screen. Now I rebooted into Flashing Mode (Odin) and Flashed CF-Auto-Root-d2tmo-d2tmo-sght999.tar, thinking that would help.......however.....I still seem to be stuck.....How do I get myself unstuck? Thanks so much for any help .....
Mic
Have you tried using stock recovery and perform a factory reset? I also took mine back to stock via Odin, performed the factory reset and worked fine
Sent from my SGH-T999 using Tapatalk
Hellfireworks said:
Have you tried using stock recovery and perform a factory reset? I also took mine back to stock via Odin, performed the factory reset and worked fine
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I did do that.....and was able to update to 4.3 through t-mobile, however, now I have a black block which appears over all screens giving or listing what seems to be the information about my phone, and a warning that the phone is in "Factory Mode" and I need to reset it back to user.....or something like that...it comes and goes kinda fast....I wanted to flash a different ROM but I went back to stock to kinda clean up my internal SD....it was getting kinda bulked down with all the roms I was trying.........but now I am stuck with this......any ideas??
jinx0117 said:
I did do that.....and was able to update to 4.3 through t-mobile, however, now I have a black block which appears over all screens giving or listing what seems to be the information about my phone, and a warning that the phone is in "Factory Mode" and I need to reset it back to user.....or something like that...it comes and goes kinda fast....I wanted to flash a different ROM but I went back to stock to kinda clean up my internal SD....it was getting kinda bulked down with all the roms I was trying.........but now I am stuck with this......any ideas??
Click to expand...
Click to collapse
Did you update to 4.3 while you were in stock? If you did that, maybe Knox is causing you these issues, if you havent been in 4.3 in stock, you shouldn't have that issue.
I would suggest flashing 4.1.2 version via odin, after that enter recovery and do a factory reset, after that reboot and it should start properly
Sent from my SGH-T999 using Tapatalk
Hellfireworks said:
Did you update to 4.3 while you were in stock? If you did that, maybe Knox is causing you these issues, if you havent been in 4.3 in stock, you shouldn't have that issue.
I would suggest flashing 4.1.2 version via odin, after that enter recovery and do a factory reset, after that reboot and it should start properly
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I originally went to Stock 4.1.2....then got tried to root the phone thinking that flashing different Rom would fix the issue.....no dice...So I flashed back to the 4.1.2 Stock. Made my way around the block that pops up telling me I need to set it back to user mode and did the OTA update. After the update it was still saying that I was in Factory Mode....and needed to reset it to User Mode.....In did a hard reset and wipe....and it is still there.....I may be able to change it through root explorer but I need to root my phone again.....and I have no idea where a safe place to start would be for that....
@jinx0117
Sounds like your EFS folder might have been erased. You can root the phone and check with a file explore. If you don't have a backup of it, there is no way to recover it.
If you have updated to official 4.3 don't try to downgrade with odin or you will end up with a full brick.
sswb27 said:
@jinx0117
Sounds like your EFS folder might have been erased. You can root the phone and check with a file explore. If you don't have a backup of it, there is no way to recover it.
If you have updated to official 4.3 don't try to downgrade with odin or you will end up with a full brick.
Click to expand...
Click to collapse
Thank you so much for telling me that.....I was able to root and reset my phones Factory Mode by use of a Emulator. Now I did follow some steps I found here on XDA to get around the Knox Security that T mobile put on the 4.3 update......I am able to flash Roms now with no issues.....thanks so much everyone for all your help!!!!
I will assume that if I want to take it back to stock again I would need to flash a 4.3 stock with Odin???? That way I don't brick my phone? Is that correct?:good:
jinx0117 said:
Thank you so much for telling me that.....I was able to root and reset my phones Factory Mode by use of a Emulator. Now I did follow some steps I found here on XDA to get around the Knox Security that T mobile put on the 4.3 update......I am able to flash Roms now with no issues.....thanks so much everyone for all your help!!!!
I will assume that if I want to take it back to stock again I would need to flash a 4.3 stock with Odin???? That way I don't brick my phone? Is that correct?:good:
Click to expand...
Click to collapse
Yea, Stick with 4.3 odin for now on. The 4.3 Bootloader wont let you downgrade.
sswb27 said:
Yea, Stick with 4.3 odin for now on. The 4.3 Bootloader wont let you downgrade.
Click to expand...
Click to collapse
Thank you so much for that....I have tried to flash a few custom roms but I see there are some issues with certain parts of the phone if they are not 4.3 and above. Do you know of a good ROM that would work on my phone that has alot of customizing.....I'm a chick....so....In like to theme.....lol
I can't use anything from Team Dirt.....my phone won't load it....I have Dandroid on there now....but that is pretty much stock.....Tried StockRom custom.....but it never loaded the Aroma installer......it just sat there saying it was loading it...... Thanks again for all the help. :laugh:
jinx0117 said:
Thank you so much for that....I have tried to flash a few custom roms but I see there are some issues with certain parts of the phone if they are not 4.3 and above. Do you know of a good ROM that would work on my phone that has alot of customizing.....I'm a chick....so....In like to theme.....lol
I can't use anything from Team Dirt.....my phone won't load it....I have Dandroid on there now....but that is pretty much stock.....Tried StockRom custom.....but it never loaded the Aroma installer......it just sat there saying it was loading it...... Thanks again for all the help. :laugh:
Click to expand...
Click to collapse
Aroma is buggy, you just have to keep rebooting into recovery and keep trying, it will go. Some say it seems to work better without the usb plugged in.
As for team dirt I believe it is a aosp rom. If it is you will have to edit the updater script in the zip file so it know's your new 4.3 bootloader. META-INF>com>google>android>updater-script. If your on windows I suggest downloading notepad++ to edit the file. Just delete every thing down to where it
say's mount then save the file.
Update: I edited the updater for you https://www.dropbox.com/s/xucl47rh1wxg9rt/updater-script
Just put it in the zip file where I told you above, save and copy it to the zip and flash away.
sswb27 said:
Aroma is buggy, you just have to keep rebooting into recovery and keep trying, it will go. Some say it seems to work better without the usb plugged in.
As for team dirt I believe it is a aosp rom. If it is you will have to edit the updater script in the zip file so it know's your new 4.3 bootloader. META-INF>com>google>android>updater-script. If your on windows I suggest downloading notepad++ to edit the file. Just delete every thing down to where it
say's mount then save the file.
Update: I edited the updater for you https://www.dropbox.com/s/xucl47rh1wxg9rt/updater-script
Just put it in the zip file where I told you above, save and copy it to the zip and flash away.
Click to expand...
Click to collapse
Wow!!!! Thank you sooooo much....I admit I don't know it all just enough to be dangerous....but I am always willing to learn.....thank you so much for doing that for me....that was really awesome of you......
jinx0117 said:
Wow!!!! Thank you sooooo much....I admit I don't know it all just enough to be dangerous....but I am always willing to learn.....thank you so much for doing that for me....that was really awesome of you......
Click to expand...
Click to collapse
Well, this is the place to learn. We are all here to help each other, that's why i love android.:highfive:
Just use that thanks button to people that help you is all we ask in return.
So basically I rooted my Sprint S6 5.1.1 OFE before I realized there wasn't a stock rom online for it. Two weeks later, fast forward to yesterday night, I end up soft bricking my phone trying to modify some code in "Build.prop" folder. The only thing I can think of that will fix this is a rom running OFE. Could anybody give me a solution or, better yet, a link to a rom to help me and fellow un-rooters? This will be greatly appreciated because right now I have no working phone.
P.S. Me being an idiot, I didn't install TWRP
Saafir said:
You can use the OF7 tar or use TWRP file manager to remove the lines you added to the prop file. Here is the OF7 tar, thank the OP for mirrors. http://forum.xda-developers.com/sprint-galaxy-s6/general/of7-odin-tar-available-donwload-t3154212
Click to expand...
Click to collapse
Will OF7 work for OFE?
Saafir said:
Yeah, you'll just have to take the OTA update since OFE tar isnt available yet. You just can't Odin a lower Android version, say back to OE2 [5.0 from 5.1]
Click to expand...
Click to collapse
I heard it wasn't possible and i just tried it and its safe to say that you sir are my savior. Thank you soo much!!!!
Hello all.
So, as a noob, I rooted my tab S successfully and was playing around with the TWRP recovery settings and accidentally deleted my OS. I was able to flash a stock version of Android but now it is stuck in a loop and I have no way of getting it past the loading screen. I am able to access the download mode but I can get no further than that. Is there anyway that you can help me with resetting my device? Could any of you also link me to a thread which can help me unroot my tab so that I can reroot it using CF auto root with TWRP recovery mode installed?
That would be greatly appreciated. Thanks.
My model number is: SM-T800NZWAXAR
Wipe Data then flash again, wait at least 10 mins for for first boot.
We flashed tamirda's phoenix rom. I can't even explain the whole process because my cousin helped us out with that, but thanks!!!
Zwhlol-Zniper said:
We flashed tamirda's phoenix rom. I can't even explain the whole process because my cousin helped us out with that, but thanks!!!
Click to expand...
Click to collapse
Flash the required custom ROM, or reflash the stock rom
tra_dax
tra_dax said:
Flash the required custom ROM, or reflash the stock rom
tra_dax
Click to expand...
Click to collapse
Now, I flashed the update but it removed my g-apps and my twrp. Is there a way that I can add those while still preserving the rom?
I will post of this issue in the official thread and see if I can get an answer there as well.
Thanks.
Zwhlol-Zniper said:
Now, I flashed the update but it removed my g-apps and my twrp. Is there a way that I can add those while still preserving the rom?
I will post of this issue in the official thread and see if I can get an answer there as well.
Thanks.
Click to expand...
Click to collapse
If u think I helped u then hit the thx button.???
tra_dax
I'm afraid I didn't get an answer from you. I asked for a link but I didn't get one. But you also suggested that I flashed the rom from or custom recovery. Correct me if there is anything wrong in the process that me and my cousin discovered. I probably forgot to mention that I had a T-800 but anyways.
From a prior, we did an ADB sideload of TWRPrecovery. It tooks my cousin a while to find the stuff, but he was able to reinstall the device drivers and sideload it into the system memory. From there, he uploaded the rom installer, which was done through aroma, at that point. Then. we installed, Gapps and customized it to include the services that I want. The rom worked perfectly.
But I messed up when I flashed the OTA through ODIN rather than through twrp. It deleted the custom recovery and a popup saying that gapps could not be located was annoyingly in the way.
So at this point. We were able to root the tablet. then flash the custom recovery. First we loaded the recovery, the actual rom. then gapps, and finally the OTA from the tablet memory. In hindsight, we decided to do this after trying to install straight gapps from the OTA and gapps kept giving an error code 70. After loading everything onto the rom, it worked.
Now I do have a question about xposed. Would I have to flash that in recovery if I wanted to take access of its features? Is there a link on how to use it? Or does that depend on xposed and how well my rom could support it?
Well I won't suggest u to flash xposed since it can give u bootloop problems and I m sure u won't wanna take a risk. But if u really want it then tell me.
And for installing the zip first u will need a deodexed rom installed on ur device
tra_dax
Yeah. I found out the hard way that my device can easily get boot looped with too many modules. I do have a back up ready and a method for wiping and resetting the device.
Zwhlol-Zniper said:
Yeah. I found out the hard way that my device can easily get boot looped with too many modules. I do have a back up ready and a method for wiping and resetting the device.
Click to expand...
Click to collapse
U will need a de-odexed ROM. If u don't get one, i'll find the way to make the firmware de-odexed. Here's the xposed apk and the zip file:
http://forum.xda-developers.com/attachment.php?attachmentid=3333763&d=1432712436
tra_dax
I'll send you a link to the code version that I used with the rom that I ask using.
Sent from my SM-N910V using Tapatalk
tra_dax said:
U will need a de-odexed ROM. If u don't get one, i'll find the way to make the firmware de-odexed. Here's the xposed apk and the zip file:
http://forum.xda-developers.com/attachment.php?attachmentid=3333763&d=1432712436
tra_dax
Click to expand...
Click to collapse
Practically every custom rom in the dev section is deodexed.
ashyx said:
Practically every custom rom in the dev section is deodexed.
Click to expand...
Click to collapse
Yeah u right. A custom too is a deodexed ROM.
tra_dax
This is @tamirda's rom. http://forum.xda-developers.com/showthread.php?t=3222264
And here is the link to the xposed framework. http://forum.xda-developers.com/showthread.php?t=3113463
Zwhlol-Zniper said:
This is @tamirda's rom. http://forum.xda-developers.com/showthread.php?t=3222264
And here is the link to the xposed framework. http://forum.xda-developers.com/showthread.php?t=3113463
Click to expand...
Click to collapse
OK, the ROM is the right one, get the v3 xposed by arter97.
tra_dax
tra_dax said:
OK, the ROM is the right one, get the v3 xposed by arter97.
tra_dax
Click to expand...
Click to collapse
V3? V75 is the latest version.
According to one user, they tried to flash the latest version's framework only to have it stuck in a boot loop. I tried a 71 exynos file because another user recommended it as the most stable framework for the poster with that issue.
Sent from my SM-N910V using Tapatalk
Zwhlol-Zniper said:
According to one user, they tried to flash the latest version's framework only to have it stuck in a boot loop. I tried a 71 exynos file because another user recommended it as the most stable framework for the poster with that issue.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Well then now do u think I helped u? If yes then hit the thx button. I won't force u to do that but it will help me to help more person.
tra_dax
I how do I do it in tapatalk?
Sent from my SM-N910V using Tapatalk
Zwhlol-Zniper said:
According to one user, they tried to flash the latest version's framework only to have it stuck in a boot loop. I tried a 71 exynos file because another user recommended it as the most stable framework for the poster with that issue.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Then they flashed the wrong one. The latest version is working just fine.
I saw some tutorials said modify updater-script to skip model check, but I can't find this file.
I removed build.prop before, is it the reason the error caused?
Is there any way to fix this?
KleinW said:
I can't flash ROMs because I can't pass the model check, get error code "kInstallDeviceOpenError". I saw some tutorials said modify updater-script to skip model check, but I can't find this file.
Is there any way to recover build.prop?
Or is there any way to pass the model check?
I tried to create a new "build.prop" and write "ro.product.model=alioth" in it, but it doesn't work.
Click to expand...
Click to collapse
Restore back to miui and start over again?
keyoke87 said:
Restore back to miui and start over again?
Click to expand...
Click to collapse
I can't flash MIUI. I got "ErrorCode::kInstallDeviceOpenError"
KleinW said:
I saw some tutorials said modify updater-script to skip model check, but I can't find this file.
I removed build.prop before, is it the reason the error caused?
Is there any way to fix this?
Click to expand...
Click to collapse
Have you tried doing a factory data reset?
Otherwise you can try to edit the flash_all.bat (It is inside the package of the fastboot stock rom, unzip and edit) file by deleting the first two lines of code.
RollDload said:
Have you tried doing a factory data reset?
Otherwise you can try to edit the flash_all.bat (It is inside the package of the fastboot stock rom, unzip and edit) file by deleting the first two lines of code.
Click to expand...
Click to collapse
I use MiPhoneAssistant re-install the rom.
Thanks for your answer.
KleinW said:
I use MiPhoneAssistant re-install the rom.
Thanks for your answer.
Click to expand...
Click to collapse
Miflashtool you mean?
Use the official TWRP Recovery found here, I had the same problem when using the version of TWRP by vasishath.