Develop Bugs

[Q] Rollback of Official Update

I have updated my Galaxy grand witj the official (BNB) update. But it lagging and slow and also hangs. Iwant to rollback to previous version is there any possibility to rollback without rooting the phone or custom rom?

Anish_ca said:
I have updated my Galaxy grand witj the official (BNB) update. But it lagging and slow and also hangs. Iwant to rollback to previous version is there any possibility to rollback without rooting the phone or custom rom?
Click to expand...
Click to collapse
Yes, its possible to rollback to previous version. Download the previous version of Stock ROM from sammobile and flash this ROM via Odin v3.07 then it will roll back to the previous version..
Hit thanks if my post is helpful.
Sent from my GT-I9082 using Tapatalk

Anish_ca said:
I have updated my Galaxy grand witj the official (BNB) update. But it lagging and slow and also hangs. Iwant to rollback to previous version is there any possibility to rollback without rooting the phone or custom rom?
Click to expand...
Click to collapse
No way to rollback into previous version, as no vendor supports downgrading . If u need your old software, just download Original stock firmware (definitely some older version :silly and reflash it with Odin as @Parth2187 mentioned:cyclops:

This is what I did. I had a nand bqckup of my 4.1.2 stock rooted rom.
1. Flashed 4.1.2 stock via Odin.
2. Root3d and flashed CWM recovery.
3. Once in recovery rolled back my original nand.
Please note if u end up in a boot loop. Make aure u go to stock recovery and do data/factory reset and wipe cache and u r good to go.
Hope helps. Worked foe me.
Sent from my GT-I9082 using XDA Premium 4 mobile app

OTA for Rooted Phone
DMJoh said:
No way to rollback into previous version, as no vendor supports downgrading . If u need your old software, just download Original stock firmware (definitely some older version :silly and reflash it with Odin as @Parth2187 mentioned:cyclops:
Click to expand...
Click to collapse
If i root my phone than can i get update from OTA??
If i want to unroot my Phone then how it is possible?

Anish_ca said:
If i root my phone than can i get update from OTA??
If i want to unroot my Phone then how it is possible?
Click to expand...
Click to collapse
If you root your phone, you won't be able to receive OTA updates and it will void your warranty. If you unroot you can get the OTA updates.
To root see this thread
If you want to unroot, see this thread.

Anish_ca said:
If i root my phone than can i get update from OTA??
If i want to unroot my Phone then how it is possible?
Click to expand...
Click to collapse
Try doing factory reset thats best thing possible u can do

abhi0502 said:
Try doing factory reset thats best thing possible u can do
Click to expand...
Click to collapse
I don't think a factory reset can unroot a device. I am not pretty sure about this, if u are successful in that, its okay. But factory reset just formats the internal SD card. It wont do anything with /Root directory. When you are rooting a phone, we flash SU to the /root directory.. Then how come a factory reset can unroot a device. Probably impossible! Correct me if i am wrong

DMJoh said:
I don't think a factory reset can unroot a device. I am not pretty sure about this, if u are successful in that, its okay. But factory reset just formats the internal SD card. It wont do anything with /Root directory. When you are rooting a phone, we flash SU to the /root directory.. Then how come a factory reset can unroot a device. Probably impossible! Correct me if i am wrong
Click to expand...
Click to collapse
+1...factory reset does not unroot...........flashing stock rom through odin and using traingle away ( not in that order ) would unroot the device..we are priviledged that our device has all prequisites for rooting and unrooting...

I tried flashing the old rom with odin but it gives some error :/ maybe my firmware has sm problem :|

XG.Matrix said:
I tried flashing the old rom with odin but it gives some error :/ maybe my firmware has sm problem :|
Click to expand...
Click to collapse
What problem you are getting?

Anish_ca said:
If i root my phone than can i get update from OTA??
If i want to unroot my Phone then how it is possible?
Click to expand...
Click to collapse
yes it is possible to get ota on a rooted phone

Note II (n7100) - Constant freezing and rebooting

Hi,
Have a Note II as an alternative phone. Apparently, the phone worked correctly until last month. It started to reboot, not too much, but it happened. Well, I tried to give a solution changing the ROM (when it started with the problem I was in 4.4.2 OmniROM). My first try was with Omega ROM, cause it was my first custom ROM when I bought the phone with 4.1.2 in, but the problem persist (maybe increment the number of reboots-freezes/day) so I changed it again to Android Revolution HD, but it only increment the reboots/freezes.
It seems that it's not a ROM installation problem or something like that, maybe it's a hardware problem, but I would like to hear your opinions about it.
Now the phone have:
TWRP recovery
Rooted
Android Revolution HD
I am thinking on put the stock ROM and bootloader with Odin. What do you think?
Thanks!

Could you enter recovery, format /system /data /cache and flash clean Omni > reboot >reboot to recovery >flash Gapps> reboot and observe without installing any apps. Until it freezes or reboots anyway.

My dad also has note 2,he had the same problem on many different roms.
He had to give it back to repair. They've replaced power button and something else, after that the phone seems normal.
Sent from galaxy n7105

mat9v said:
Could you enter recovery, format /system /data /cache and flash clean Omni > reboot >reboot to recovery >flash Gapps> reboot and observe without installing any apps. Until it freezes or reboots anyway.
Click to expand...
Click to collapse
Hi mat9v,
Thanks for your reply. I am in the office now, but I will try it as soon as I can. I thought on your suggestion too, so I will give a chance .
In case of it does not working, if I restore to stock ROM, will it restore the bootloader and recovery automatically too?
My actual bootloader if I am not wrong, is MJ5 bootloader (to fix the WiFi problems with custom ROMs in 4.3).
Thanks!
Edit:
jakuburban said:
My dad also has note 2,he had the same problem on many different roms.
He had to give it back to repair. They've replaced power button and something else, after that the phone seems normal.
Sent from galaxy n7105
Click to expand...
Click to collapse
Did you repair it even with custom ROM? Samsung does not accept it, right? Anyway, my phone is not in guarantee time.
Thanks!

Nah, of course I restored it to official 4.1.2 so everything was like new.
If You don't have guarantee, not good
Sent from galaxy n7105

pep0te said:
Hi mat9v,
Thanks for your reply. I am in the office now, but I will try it as soon as I can. I thought on your suggestion too, so I will give a chance .
In case of it does not working, if I restore to stock ROM, will it restore the bootloader and recovery automatically too?
My actual bootloader if I am not wrong, is MJ5 bootloader (to fix the WiFi problems with custom ROMs in 4.3).
Thanks!
Click to expand...
Click to collapse
Yes, it will overwrite both bootloader and recovery, unroot and so on. Be careful with KNOX and look for TriangleAway to reset flash status to factory.

jakuburban said:
Nah, of course I restored it to official 4.1.2 so everything was like new.
If You don't have guarantee, not good
Sent from galaxy n7105
Click to expand...
Click to collapse
Hope I can fix it by other way then . Thanks!
mat9v said:
Yes, it will overwrite both bootloader and recovery, unroot and so on. Be careful with KNOX and look for TriangleAway to reset flash status to factory.
Click to expand...
Click to collapse
Hm, could you explain me a bit? Sorry if my question is stupid.
Thanks a lot.

pep0te said:
Hope I can fix it by other way then . Thanks!
Hm, could you explain me a bit? Sorry if my question is stupid.
Thanks a lot.
Click to expand...
Click to collapse
If you want to return the phone to service center you mast be careful to maintain KNOX status 0 and Software status: Factory or they may refuse to fix the phone (warranty void by messing with software) - it's not such a big deal here in Europe but in US there are some stupid rules like that. So long as you remain on MJ5 bootloader you should have no problem with KNOX when you flash Samsung firmware but Firmware status: Modified vs Factory require using TriangleAway program to reset specific counters. Find it on Playstore and follow the link there to explanation on how to proceed.

mat9v said:
If you want to return the phone to service center you mast be careful to maintain KNOX status 0 and Software status: Factory or they may refuse to fix the phone (warranty void by messing with software) - it's not such a big deal here in Europe but in US there are some stupid rules like that. So long as you remain on MJ5 bootloader you should have no problem with KNOX when you flash Samsung firmware but Firmware status: Modified vs Factory require using TriangleAway program to reset specific counters. Find it on Playstore and follow the link there to explanation on how to proceed.
Click to expand...
Click to collapse
Hi mat9v,
Just fyi, I am from Europe . So this mean that I should check if Firmware status is "Modified" or "Factory" and KNOX = 0. In case of it is "Modified" (most probably right?) or KNOX = 1 or more, I must use TriangleAway to reset the counters.
That's okay, thank you all for your help . I will try and give my feedback asap!

pep0te said:
Hi mat9v,
Just fyi, I am from Europe . So this mean that I should check if Firmware status is "Modified" or "Factory" and KNOX = 0. In case of it is "Modified" (most probably right?) or KNOX = 1 or more, I must use TriangleAway to reset the counters.
That's okay, thank you all for your help . I will try and give my feedback asap!
Click to expand...
Click to collapse
You can't reset KNOX counter if you are on a bootloader newer than MJ5 (it's been tested that on MJ5 you can deal with it by flashing earlier firmware along with older bootloader). More info HERE

mat9v said:
You can't reset KNOX counter if you are on a bootloader newer than MJ5 (it's been tested that on MJ5 you can deal with it by flashing earlier firmware along with older bootloader). More info HERE
Click to expand...
Click to collapse
How can I check my bootloader? I am almost sure that is MJ5 but... better to check.
Thanks!
Edit:
The stock ROM I should install is the 4.3 I choose in sammobile, right? Spain country in my case.
http://www.sammobile.com/firmwares/3/?download=23362
Thank you.

pep0te said:
How can I check my bootloader? I am almost sure that is MJ5 but... better to check.
Thanks!
Edit:
The stock ROM I should install is the 4.3 I choose in sammobile, right? Spain country in my case.
http://www.sammobile.com/firmwares/3/?download=23362
Thank you.
Click to expand...
Click to collapse
To check bootloader install "Info" by Nag from Playstore and look in OS category.
Yes, but it will flash bootloader newer than MJ5 I think (MJ9 if my memory serves me right) and you may not be able to set KNOX to 0. Also you must play with TriangleAway before flashing stock 4.3 because it does not work on stock (root required).
Since you are in Europe, it should not matter too much (according to European law) so if someone makes any heat just say that it a law

mat9v said:
To check bootloader install "Info" by Nag from Playstore and look in OS category.
Yes, but it will flash bootloader newer than MJ5 I think (MJ9 if my memory serves me right) and you may not be able to set KNOX to 0. Also you must play with TriangleAway before flashing stock 4.3 because it does not work on stock (root required).
Since you are in Europe, it should not matter too much (according to European law) so if someone makes any heat just say that it a law
Click to expand...
Click to collapse
Amazing, alright now. Hope I can fix this usual problem...
Thanks for your complete and helpful answers!

mat9v said:
To check bootloader install "Info" by Nag from Playstore and look in OS category.
Yes, but it will flash bootloader newer than MJ5 I think (MJ9 if my memory serves me right) and you may not be able to set KNOX to 0. Also you must play with TriangleAway before flashing stock 4.3 because it does not work on stock (root required).
Since you are in Europe, it should not matter too much (according to European law) so if someone makes any heat just say that it a law
Click to expand...
Click to collapse
Hi again,
My bootloader (Info app) is:
Bootloader: N7100XXDLL7
I think this is the old (4.1.2) right?
Sent from my Nexus 5 using xda app-developers app

pep0te said:
Hi again,
My bootloader (Info app) is:
Bootloader: N7100XXDLL7
I think this is the old (4.1.2) right?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yes, and it is probably the reason for Android Revolution problems. If I remember correctly it is a 4.3 rom and they have compatibility problems with older bootloaders - the results are random reboots and freezes (there is a lot about it in Phoenix rom thread). To comfortably use TW 4.3 rom it's best to update bootloader to MJ5. AOSP roms should not be affected though so I suppose that there was some other cause for this. You can flash 4.1.2 on this bootloader without issue, be mindful to safeguard data from your internal sdcard as you may loose them all.
I would advise testing standard 4.1.2 version and if everything works fine, flashing something new (with MJ5 bootloader for compatibility sake).

mat9v said:
Yes, and it is probably the reason for Android Revolution problems. If I remember correctly it is a 4.3 rom and they have compatibility problems with older bootloaders - the results are random reboots and freezes (there is a lot about it in Phoenix rom thread). To comfortably use TW 4.3 rom it's best to update bootloader to MJ5. AOSP roms should not be affected though so I suppose that there was some other cause for this. You can flash 4.1.2 on this bootloader without issue, be mindful to safeguard data from your internal sdcard as you may loose them all.
I would advise testing standard 4.1.2 version and if everything works fine, flashing something new (with MJ5 bootloader for compatibility sake).
Click to expand...
Click to collapse
Thanks. You suggest to flash 4.1.2 stock from sammobile right? I mean, it should install the same bootloader that I have now.
Thanks again!
Sent from my Nexus 5 using xda app-developers app

pep0te said:
Thanks. You suggest to flash 4.1.2 stock from sammobile right? I mean, it should install the same bootloader that I have now.
Thanks again!
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yes, exactly.

mat9v said:
Yes, exactly.
Click to expand...
Click to collapse
Okay, I will do it then. Thanks a lot! :fingers-crossed:

mat9v said:
Yes, exactly.
Click to expand...
Click to collapse
Hey mat9v,
I am trying to reset the counter but it still shows "1" (before this, it showed "7"). Do you know why can't get to fully reset it?
Thanks!

pep0te said:
Hey mat9v,
I am trying to reset the counter but it still shows "1" (before this, it showed "7"). Do you know why can't get to fully reset it?
Thanks!
Click to expand...
Click to collapse
To fully reset the counter it has to be done in certain order. I do not remember exactly in which order the sequence of events should proceed but it went something like this:
- run triangle away
- reboot
- enter download mode (odin version)
- flash stock rom
If you reboot even once to custom rom (this I'm certain) or even custom recovery (I think) the triangle away effect will be gone and the count returns to 1 because it detects custom rom/kernel.

[Q] N7100 Help Service State: Out Of Service. And More.

Dear all,
Well I dont know where to start. But here is what happened with my N7100 Note 2.
I was on the latest 4.4.2, the phone restarted suddenly one day and it just dont boot stuck at samsung logo,
flashed the 4.4.2 stock from sammobile. and it worked fine everything was perfect for a week, till it happened again
flashed the same rom. and here is where the trouble begins.
The IMEI changed to generic 00499XXX.., Serial No: 000000
i managed to downgrade to 4.1.2 with mobile odin, flashed a lot of stocks and customs as well. And after a very hard work for a week i manage to get back my IMEI and serial number back, now I backed up my EFS learned my lesson
Now i flashed the stock rom 4.1.1, phone is unlocked. cant make calls, or sms or data internet.
Now I have service: out of service, Bluetooth address: unavailable (while its in the efs folder the mac is in the file), Device status modified, And when I connect it to USB it wont recognize the phone until I have to dial *#7284# and change USB from modem to PDA, then save and reset. (EVERYTIME) I need a permanent fix as well for that.
Please I need help with those as i cant make my phone work.
Thanks and regards,
Mohamed Selim.

First and most important:
If you ever were on stock 4.4.x you can't downgrade to 4.1.x because of knoxed bootloader.
What you did with mobile odin was no real downgrade cause your bootloader wasn't touched.
Don't try to flash firmware beyond your current bootloader version.
Install Samsung Phone Info app from play store and look for actual bootloader version.

Androidwizzard said:
First and most important:
If you ever were on stock 4.4.x you can't downgrade to 4.1.x because of knoxed bootloader.
What you did with mobile odin was no real downgrade cause your bootloader wasn't touched.
Don't try to flash firmware beyond your current bootloader version.
Install Samsung Phone Info app from play store and look for actual bootloader version.
Click to expand...
Click to collapse
Well It actually did downgrade to 4.1.2 with Mobile odin and I checked the version and Baseband and everything it was the 4.1.2
Now I am on 4.1.1 stock. rooted and trying to figure out what to do now

onix17_5 said:
Well It actually did downgrade to 4.1.2 with Mobile odin and I checked the version and Baseband and everything it was the 4.1.2
Now I am on 4.1.1 stock. rooted and trying to figure out what to do now
Click to expand...
Click to collapse
As I said before: YOU DID NOT DOWNGRADE firmware to 4.1.2 with Mobile Odin, check with Info app from Samsung:
You will find bootloader between *ND3 and *NI1 and all are 4.4.2 KitKat
So, whatever firmware you try to flash under 4.4.2 is supposed to fail.

Androidwizzard said:
As I said before: YOU DID NOT DOWNGRADE firmware to 4.1.2 with Mobile Odin, check with Info app from Samsung:
You will find bootloader between *ND3 and *NI1 and all are 4.4.2 KitKat
So, whatever firmware you try to flash under 4.4.2 is supposed to fail.
Click to expand...
Click to collapse
I am not trying to argue here, And yes I do agree with you, it failed with i tried to downgrade with windows odin all the time, but acutally never failed with mobile-odin pro latest version. you dont have to believe me, I wont lie to you. I just need a solution for the problem im having now.
Thanks.

onix17_5 said:
I am not trying to argue here, And yes I do agree with you, it failed with i tried to downgrade with windows odin all the time, but acutally never failed with mobile-odin pro latest version. you dont have to believe me, I wont lie to you. I just need a solution for the problem im having now.
Thanks.
Click to expand...
Click to collapse
Mobile Odin does everything but doesn't flash bootloader so it is like flashing a custom rom which also doesn't contain bootloader.
PC Odin flashes complete firmware, so this is the only way to really up- or downgrade. Hope you understand the difference.
The only solution I see for you is to concentrate on 4.4.2 equal or up your actual bootloader version.

Androidwizzard said:
Mobile Odin does everything but doesn't flash bootloader so it is like flashing a custom rom which also doesn't contain bootloader.
PC Odin flashes complete firmware, so this is the only way to really up- or downgrade. Hope you understand the difference.
The only solution I see for you is to concentrate on 4.4.2 equal or up your actual bootloader version.
Click to expand...
Click to collapse
I do Understand the difference, and thanks for explaining more.
But I attached About my device
But any way beside all this points, I need to fix all the problems I am having either im on 4.1.1 or 4.4.2
Thanks.

onix17_5 said:
I do Understand the difference, and thanks for explaining more.
But I attached About my device
But any way beside all this points, I need to fix all the problems I am having either im on 4.1.1 or 4.4.2
Thanks.
Click to expand...
Click to collapse
I really want to help you out and I assure you that I know what I am talking about (take a look into my signature with stock roms and bootloaders).
There is indeed no solution on 4.1.1 and the screenshot doesn't show bootloader version. To believe what I say try to find out what BL version you are on. If it shows XXUFND3 up to XXUFNI1 you have the proof.

Androidwizzard said:
I really want to help you out and I assure you that I know what I am talking about (take a look into my signature with stock roms and bootloaders).
There is indeed no solution on 4.1.1 and the screenshot doesn't show bootloader version. To believe what I say try to find out what BL version you are on. If it shows XXUFND3 up to XXUFNI1 you have the proof.
Click to expand...
Click to collapse
kay my Bootloader is: N7100XXUFND4. Android Version: 4.1.1, you are right, I kinda understand what you were talking about now.
So now im all ears, Please help me solve my problems.

onix17_5 said:
Okay my Bootloader is: N7100XXUFND4. Android Version: 4.1.1
Well now how can I solve my problems, All ears
Click to expand...
Click to collapse
XXUFND3 was the first KitKat firmware for N7100 and yours was the second.
Three options:
1) Flash firmware using PC Odin at least ND4, maybe better NE1 or up
2) Flash through recovery any stock KitKat custom rom provided by wesamothman, cosmyndemeter or me
3) Flash through recovery any KitKat custom rom you like from development section here
4.3 custom roms may work also, but not 100% sure.
Beyond 4.3 I wouldn't recommend.

Androidwizzard said:
XXUFND3 was the first KitKat firmware for N7100 and yours was the second.
Three options:
1) Flash firmware using PC Odin at least ND4, maybe better NE1 or up
2) Flash through recovery any stock KitKat custom rom provided by wesamothman, cosmyndemeter or me
3) Flash through recovery any KitKat custom rom you like from development section here
4.3 custom roms may work also, but not 100% sure.
Beyond 4.3 I wouldn't recommend.
Click to expand...
Click to collapse
Okay, I will flash a stock Kitkat custom rom provided by you, Can you please require one for me. And I will flash it through recovery now.

onix17_5 said:
Okay, I will flash a stock Kitkat custom rom provided by you, Can you please require one for me. And I will flash it through recovery now.
Click to expand...
Click to collapse
Best and fastest one is XXUFNI1, NH2 and NG3 aren't bad either.
Do a clean installation (factory reset) and after setup device go back into recovery to flash SuperSu.zip.:highfive:

Androidwizzard said:
Best and fastest one is XXUFNI1, NH2 and NG3 aren't bad either.
Do a clean installation (factory reset) and after setup device go back into recovery to flash SuperSu.zip.:highfive:
Click to expand...
Click to collapse
Okay I staterd the download for XDA_XXUFNI1.zip and the BL NH2.
I think I got it, no BL just the XDA_XXUFNI1.zip and clean install it
Okay will be back when im done

onix17_5 said:
Okay I staterd the download for XDA_XXUFNI1.zip and the BL NH2.
should I flash the NH2 with odin after the rom? , or just the Rom without the NH2?
Click to expand...
Click to collapse
No need to flash BL cause you already have KitKat BL

Androidwizzard said:
XXUFND3 was the first KitKat firmware for N7100 and yours was the second.
Three options:
1) Flash firmware using PC Odin at least ND4, maybe better NE1 or up
2) Flash through recovery any stock KitKat custom rom provided by wesamothman, cosmyndemeter or me
3) Flash through recovery any KitKat custom rom you like from development section here
4.3 custom roms may work also, but not 100% sure.
Beyond 4.3 I wouldn't recommend.
Click to expand...
Click to collapse
Okay im done with this part flashed and step up, and installed superU.
So what next

onix17_5 said:
Okay im done with this part flashed and step up, and installed superU.
So what next
Click to expand...
Click to collapse
After reboot everything should be fine: Stable, rooted, fast, right?

Androidwizzard said:
After reboot everything should be fine: Stable, rooted, fast, right?
Click to expand...
Click to collapse
Yes rooted fast everything is stable, but all the problems I said in the first post still there

onix17_5 said:
Yes rooted fast everything is stable, but all the problems I said in the first post still there
Click to expand...
Click to collapse
You mean really everything
out of service,
Bluetooth address: unavailable
Device status modified -> that's ok
USB doesn't recognize the phone

Androidwizzard said:
You mean really everything
out of service,
Bluetooth address: unavailable
Device status modified -> that's ok
USB doesn't recognize the phone
Click to expand...
Click to collapse
Yes still out of service
Bluetooth address: unavaliable
USB doesnt recognize the phone until i have to do *#7284# and change USB to PDA, this its okay but once i restarted the phone I have to do it again save and reset.

onix17_5 said:
Yes still out of service
Bluetooth address: unavaliable
USB doesnt recognize the phone until i have to do *#7284# and change USB to PDA, this its okay but once i restarted the phone I have to do it again save and reset.
Click to expand...
Click to collapse
Ok, last one is driver related to your PC (Mac or Windows?), are you running Kies?
For BT I found this APP
For the first issue I think about IMEI lost, pls check

Update Stoped On Galaxy Note II Screen

Hello, I used to be rooted with custom ROMs ect but went back to stock I317ATTALJ2 so I can give the phone to my daughter. Well everything went smooth until an update from AT&T came through and she ran it when the battery was at 21% but I'm not sure it that matter but didn't help in matters... Anyhow it ran the upgrade and on reboot it stayed on the Galaxy Note II screen and wont do anything but sit there. I let it sit for a long time before pulling the battery and booting but it goes to same screen and same thing. I can not get into recovery (Volume Up, Home, Pwr) but I can go into download mode. With the battery being so low I read that it charges while in download mode so for the remainder of the day I put the phone in download mode and plugged into charger.
Suggestions?

After you get it charged up some and you're in download mode. Just Odin back to stock Att firmware should fix the problem hopefully...
You can find the stock firmware here>> http://bit.ly/1HNVFVJ
Guess the phone didn't like that update ?.

Bajanman said:
After you get it charged up some and you're in download mode. Just Odin back to stock Att firmware should fix the problem hopefully...
You can find the stock firmware here>> http://bit.ly/1HNVFVJ
Guess the phone didn't like that update .
Click to expand...
Click to collapse
Ok, Ill give the stock firmware (At&t Firmware I317UCALJ2 Uploaded By-Bajanman) that Bajanman supplys ill let you guys know in an hour or two its downloading now. I did try re installing the stock firmware I had that worked the first time and it was from SamMobile and it too sent me to the Galaxy Note II screen and froze so its not looking good.....
Thanks!

Oxicottin said:
Ok, Ill give the stock firmware (At&t Firmware I317UCALJ2 Uploaded By-Bajanman) that Bajanman supplys ill let you guys know in an hour or two its downloading now. I did try re installing the stock firmware I had that worked the first time and it was from SamMobile and it too sent me to the Galaxy Note II screen and froze so its not looking good.....
Thanks!
Click to expand...
Click to collapse
Ok.
Hopefully everything works out next time around.
Another thing you could try is flashing which ever recovery you previously had installed. Last time I was having issues with something similar, after re flashing my recovery everything started working again. Just just a thought that might work.
I'm monitoring this thread too see what happens ok.

Bajanman said:
Ok.
Hopefully everything works out next time around.
Another thing you could try is flashing which ever recovery you previously had installed. Last time I was having issues with something similar, after re flashing my recovery everything started working again. Just just a thought that might work.
I'm monitoring this thread too see what happens ok.
Click to expand...
Click to collapse
Recovery? can I flash the stock recovery using ODIN? If so where do I get it.... I always have used TWRP I wanted to use custom ROMs never really experimented with anything else.

Oxicottin said:
Recovery? can I flash the stock recovery using ODIN? If so where do I get it.... I always have used TWRP I wanted to use custom ROMs never really experimented with anything else.
Click to expand...
Click to collapse
Yes you can flash a custom recovery from Odin. You just have to use the (Twrp) tar file found here>>>
http://bit.ly/1y0Tyg7
Find your device model and download the tar. And make sure you're downloading the correct file for your device ok!
I to use Twrp and luv it.?

OK, well its not looking good....
1) Flashed the stock firmware suggested...... Still get same results!
2) Flashed TWRP through ODIN and it made it to the same screen and froze. Did a battery pull and button combo and it wont go into recovery.
Is there a application that will force your phone into recovery and download modes? I remember back when I messed with the captivate there was a application someone built that did such a thing.
Any suggestions?

Oxicottin said:
OK, well its not looking good....
1) Flashed the stock firmware suggested...... Still get same results!
2) Flashed TWRP through ODIN and it made it to the same screen and froze. Did a battery pull and button combo and it wont go into recovery.
Is there a application that will force your phone into recovery and download modes? I remember back when I messed with the captivate there was a application someone built that did such a thing.
Any suggestions?
Click to expand...
Click to collapse
Not sure you were on the newer 4.4.2 bootloader or not. If it was on a newer bootloader then you won't be able to downgrade.. This might help you get the phone working again since you just flashed the original firmware.
Go to this thread here>>http://forum.xda-developers.com/showthread.php?t=2502464.
Download
4.3 Param.bin and Tz.img
http://d-h.st/OYC
Step 2 (no bootloader in here)
flash this to bring wifi back
but keep your knox free 4.1.2 bootloader.
Allowing you to freely flash between 4.1.2 roms and the latest 4.3 leak
Without having to one click,Keeping Wifi Throughout and removing Knox
Click to expand...
Click to collapse
Unzip, Boot into Download mode, Open ODIN, put tar file in PDS slot, click Start.
Then you can go here for the latest stock Att firmware. If the above steps don't help you, then you could try flashing one one the rooted stock packages from this thread.

Bajanman said:
Not sure you were on the newer 4.4.2 bootloader or not. If it was on a newer bootloader then you won't be able to downgrade.. This might help you get the phone working again since you just flashed the original firmware.
Go to this thread here>>http://forum.xda-developers.com/showthread.php?t=2502464.
Download
4.3 Param.bin and Tz.img
http://d-h.st/OYC
Unzip, Boot into Download mode, Open ODIN, put tar file in PDS slot, click Start.
Then you can go here for the latest stock Att firmware. If the above steps don't help you, then you could try flashing one one the rooted stock packages from this thread.
Click to expand...
Click to collapse
Ok that worked and it booted!!!! Now im on 4.1.1 with TWRP
Not really sure what I just did? Did I downgrade my bootloader? Also, now how do I get it to the most up to date version without this again?
I downloaded an app and it says im on.....
Bootloader Version: 1317UCUBMK6
Thanks!

Oxicottin said:
Ok that worked and it booted!!!! Now im on 4.1.1 with TWRP
Not really sure what I just did? Did I downgrade my bootloader? Also, now how do I get it to the most up to date version without this again?
Thanks!
Click to expand...
Click to collapse
Ok not is back working again, which is great news ?. Go to the link I posted for the stock firmware, and use the rooted one.
But first make a backup of your working system first ok.

Bajanman said:
Ok not is back working again, which is great news . Go to the link I posted for the stock firmware, and use the rooted one.
But first make a backup of your working system first ok.
Click to expand...
Click to collapse
Ok, Im On 4.3 now and its working great.... Thank You!

Oxicottin said:
Ok, Im On 4.3 now and its working great.... Thank You!
Click to expand...
Click to collapse
You're very welcome glad I could help fix it.
Have a good day...

Ok problem solved so unsubscribing from this thread. If you run into any other problems you can always hit me up thru pm ?.

Question TWRP touch issue

I see that TWRP users have experienced a touchscreen issue, so they need to use an OTG cable with wireless mouse. Does anyone know when will the touch issue be fixed?

NickDeveloper said:
I see that TWRP users have experienced a touchscreen issue, so they need to use an OTG cable with wireless mouse. Does anyone know when will the touch issue be fixed?
Click to expand...
Click to collapse
So, we don't know when will be fixed

NickDeveloper said:
I see that TWRP users have experienced a touchscreen issue, so they need to use an OTG cable with wireless mouse. Does anyone know when will the touch issue be fixed?
Click to expand...
Click to collapse
But you can use the OTG touch twrp

Arobase40 said:
I experimented this no touch TWRP but it is mostly buggy excluding the non touch issue there is a bigger issue which is that once installed you can't get out from it as it bootloops into this recovery mode. Flashing a stock recovery won't change anything.
You will have to totally restock your phone from scratch and then re root it and restore all your apps and data !!! ^^
I found out the twrp tree for A52 4G and was able to build a TWRP but obviously I can't test it.
I'm not able to build a twrp for A52S 5G for now as there are missing many kernel modules and other stuffs so I have to build them from kernel source code. So for now I'm working on the device and vendor config files...
Click to expand...
Click to collapse
But how can I fix my phone if I get a bootloop?

Arobase40 said:
You can't that is why I don't recommend you to use this no touch TWRP !
I was told to use a multidisabler but doesn't seem to work...
Click to expand...
Click to collapse
But it is only a soft brick, there is no need to change the motherboard. Would there be a way to reinstall stock firmware with Odin?

Arobase40 said:
I didn't say it will break your motherboard but if you want to waste your time in restocking your phone it's up to you.
Click to expand...
Click to collapse
Can I reinstall stock firmware with Odin? Will it work?

NickDeveloper said:
Can I reinstall stock firmware with Odin? Will it work?
Click to expand...
Click to collapse
Yes.

Arobase40 said:
As I said if you want to waste your time, YES you can reinstall stock firmware but of course you will lose your no touch twrp...
You will have to choose one or the other but not both...
Click to expand...
Click to collapse
Unfortunately, I have tried to reinstall stock firmware, but it failed. Looks like my bootloader became locked. Odin software showed "FAIL". There was a message that I could barely read, so that was the reason it failed to reinstall the firmware.
What should I do now?

Arobase40 said:
You can't that is why I don't recommend you to use this no touch TWRP !
I was told to use a multidisabler but doesn't seem to work...
Click to expand...
Click to collapse
So you got stuck in a bootloop after installing twrp. Have you tried just extracting the stock boot.img from firmware AP file and flashing it with odin? I really don't get it why you had to reinstall everything to stock. It's not necessary to reflash every partition if you only messed up one

Arm1nas said:
So you got stuck in a bootloop after installing twrp. Have you tried just extracting the stock boot.img from firmware AP file and flashing it with odin? I really don't get it why you had to reinstall everything to stock. It's not necessary to reflash every partition if you only messed up one
Click to expand...
Click to collapse
Nope, I did not make the backup of anything. Unfortunately, my bootloader is now locked and I cannot reinstall stock firmware. What now??

NickDeveloper said:
Nope, I did not make the backup of anything. Unfortunately, my bootloader is now locked and I cannot reinstall stock firmware. What now??
Click to expand...
Click to collapse
While the phone is completely off, press vol up and vol down buttons at the same time and then plug in the usb cable to the computer. I had that happen too, when the device fails to boot it automatically puts you into download mode and it says that the OEM LOCK is on. You just have to reboot to download mode manually.

Arm1nas said:
While the phone is completely off, press vol up and vol down buttons at the same time and then plug in the usb cable to the computer. I had that happen too, when the device fails to boot it automatically puts you into download mode and it says that the OEM LOCK is on. You just have to reboot to download mode manually.
Click to expand...
Click to collapse
But how can I reinstall stock firmware when the OEM is locked? I tried to reinstall with all required binaries, including HOME_CSC and it showed "FAIL".

NickDeveloper said:
But how can I reinstall stock firmware when the OEM is locked? I tried to reinstall with all required binaries, including HOME_CSC and it showed "FAIL".
Click to expand...
Click to collapse
You don't need to unlock bootloader to flash stock fw with Odin.
Your problem is most likely related to something else.
Where did you download your fw?
Have you tried different cables?
What Odin version are you trying?

ShaDisNX255 said:
You don't need to unlock bootloader to flash stock fw with Odin.
Your problem is most likely related to something else.
Where did you download your fw?
Have you tried different cables?
What Odin version are you trying?
Click to expand...
Click to collapse
I don't understand why would it be possible to flash stock firmware with locked bootloader, I thought that locked bootloader won't allow the OS to be reinstalled.

NickDeveloper said:
I don't understand why would it be possible to flash stock firmware with locked bootloader, I thought that locked bootloader won't allow the OS to be reinstalled.
Click to expand...
Click to collapse
A Locked bootloader will prevent you from installing any custom things, like recovery or custom roms. It will allow you to install stock firmware via odin. Use Odin 3.14 to install firmware downloaded from here. Use the AP, Bl, Cp, and CSC_OXM files. That will get you started from scratch, all previous data and stuff will be deleted.