Develop Bugs

[Q] One V cdma boot problem. please help

Hey guys my buddy asked me to root rom and install a kernel on his one v from virgin mobile. being as i have done this before to multiple phones i was happy to help. i unlocked the bootloader, rooted it. everything was smooth up til there. i did not put a rom on it yet because he urged me to install a kernel so he could overclock his one v. i was aprehensive but i did it anyway. now his phone wont work. im not surprised but i need to fix it. ive tried installing roms to make it work because the backup ive created in twrp wont boot. so im thinking its a kernel problem. no matter what rom i use it will either not boot it will freeze at the screen that says htc and with the red wording below it. or it will boot into the rom and then freeze or run for about 30 sec then restart and it will repeat this until it dies. ive looked everywhere for ways to get it back to stock ive flashe countless roms none work ive flashed many kernels and none work as well. please help. i would like to get it working on a rom with a working kernel but i will put it back to stock if i have to. any help is greatly appreciated. thank you for your time.

You could flash a ruu ....but the problem is you don't have your software number ...or you have to go to another Rom ...which will make the phone boot normally .but don't forget to flash its specific kernel ...if you don't so that the Rom won't boot

What he said. I recommend using the RUU to restore back to stock.
Re-reroot/unlock it, then read more on which kernel to use. You most likely are using the wrong kernel.
What rom are you using currently - ?
What Kernel did you flash - ?
What error do you get with TWRP - ?

ive only been able to get a couple roms to actually boot. the one that is on it now is Amazing Sense. there is no kernel to flash with this rom and no boot.img for it either. i believe it is included. i have decided to RUU and try everything from the beginning. however i cannot find the RUU for HTC One V in the USA on Virgin Mobile. if you could post a link to that i would be very grateful. i dont see any errors on TWRP and i believe it is the stock rom i flashed last. but like i said with the rom im on it is included, so whatever is on there. thanks again for your help guys.

just curios would the sprint ruu work on the virgin mobile one? it may sound dumb but i have seen people use the recovery.img from it. was just wondering if it would brick the device or not. because i still havent found an RUU for virgin mobile one v in the US.

Nazz45 said:
ive only been able to get a couple roms to actually boot. the one that is on it now is Amazing Sense. there is no kernel to flash with this rom and no boot.img for it either. i believe it is included. i have decided to RUU and try everything from the beginning. however i cannot find the RUU for HTC One V in the USA on Virgin Mobile. if you could post a link to that i would be very grateful. i dont see any errors on TWRP and i believe it is the stock rom i flashed last. but like i said with the rom im on it is included, so whatever is on there. thanks again for your help guys.
Click to expand...
Click to collapse
Nazz45 said:
just curios would the sprint ruu work on the virgin mobile one? it may sound dumb but i have seen people use the recovery.img from it. was just wondering if it would brick the device or not. because i still havent found an RUU for virgin mobile one v in the US.
Click to expand...
Click to collapse
Ok. That's good. You use the same ICS kernel with the same ICS roms. No need to keep reflashing. I wouldn't flash a JB rom using a ICS kernel though.
Use this zip - http://androidfiles.org/uploads/index.php?dir=PrimoC/Kernels/ics
1. Extract the Boot.img from that zip and Fastboot flash boot boot.img in Bootloader
2. Wipe everything. Factory Reset, Dalvik, and System.
3. Flash an ICS based rom, Sense, or CM9.
4. Flash this after rom to get wifi working the zip above or below to fix Wifi.
http://androidfiles.org/uploads/index.php?dir=PrimoC/Kernels/ics

Just ran the RUU and it did work everything is back to stock. the sprint RUU worked. i ran into a snag installing the Android SDK it wouldnt recognize that i had my Java JDK. even after messing with my registry it still wouldnt work so i just downloaded the x86 jdk and it worked. its unfortunate cuz now i have a jdk in x64 and x86 and its taking up space on my ssd. oh well i hope it doesnt mess with eclipse. i am now going to unlock the bootloader again and re root it and install probably cm9. thank you for all your help i will post again after i attempt to re unlock reroot and rom. thanks again

[Solved] [Q] SGH-T999 Rooted bad, phone stuck on start screen

Hello xda,
I tried rooting my SGH-T999 and it took a while so I unplugged the USB and restarted the phone. Phone keeps saying it has encountered a problem with the current firmware, connect to KIES and select recovery. Kies does not connect to the device. I read on xda to reflash using ODIN. I have ODIN v1.85 from trying to root, is this the right version to use because I also found the ODIN3_v3.07? As far as USB driver, is there separate drivers for ODIN or are people referring to the Samsung Kies drivers (I just installed KIES). I read to do it on this screen and I also read to try to go into the recovery mode (holding vol down, home, power) and then reflashing; which should I do?
Also, I found this link on xda for the T-mobile firmware ( http://forum.xda-developers.com/showthread.php?t=1949687 ). No idea which one to choose, why are there so many, I am currently downloading the latest one
"UVDLJA
PDA: T999UVDLJA
CSC: T999TMBDLJA
Version: 4.1.1 JB
Date: Nov. 14, 2012
Sammobile Link
Samsung-Updates Link"
If I want to use the pre rooted file do I need to fix my problem first and try flashing with stock firmware or can I try to fix the issue directly with the pre rooted firmware?

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.

Aerowinder said:
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Click to expand...
Click to collapse
I used this guide to root.
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Before I try to flash with mrRobinson's stock rooted rom which I just finished downloading, I will uninstall Kies and install the USB drivers first?
Thanks for your response Aerowinder.
I got USB drivers earlier today that was a newer version but I will be using the files from your sig since it works :good:
Another question I had was, does the phone need to be in download mode or can I do it in the screen where it says "encountered problem with current firmware. Connect to KIES and select recovery" screen when I flash with Odin? I know normally I would have to be in the download mode but I'm wondering if it is the same when I am getting this error.

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.

Aerowinder said:
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Click to expand...
Click to collapse
Awesome thanks!
So I am watching the root video on your sig, so in my case I would choose the rom I want for the PDA instead of the cwm-touch-6.0.2.3-d2tmo right? Should I extract the rooted firmware or just load the zipped file onto ODIN PDA?

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.

Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.

Aerowinder said:
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Click to expand...
Click to collapse
Okay I don't care about the counter, I just want my phone to work and I'll be happy.
But now I'm getting a little confused about the cwm recovery.
So just to be clear, you are saying I need to flash a recovery (cwm-touch-6.0.2.3-d2tmo in my case since I don't care about the counter), BUT do I flash the recovery before or after I flash with Root66 firmware? That part I am confused about. And do I flash one right after another or do I need to restart my phone or ODIN first?
Thank you so much for helping me out. I was freaking out this morning and I am very grateful for your help and knowledge. I hope I am not being too much of a pain or hassle with these questions. Sorry that I am quite new to this

Woody said:
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Click to expand...
Click to collapse
Woody, I went to the link you posted. What are the 4 files for?

Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.

buzzking00 said:
Woody, I went to the link you posted. What are the 4 files for?
Click to expand...
Click to collapse
Top one is TWRP version 2.3.0.0
Second is 6.0.1.2 CWR touch version
Third is TWRP version 2.3.1.0
Fourth is Stock recovery.
Do not flash all of them. Are you a TWRP or CWR kind of person? Instead of re-typing it out, go here and I come in on post #20 on the 2nd page. Read that to the end and let us know if you understand it. Pretty easy to follow but I understand your Panic Mode, so take your time.
Aerowinder said:
If still having problems, only thing left to do is flash a full stock image, link also in my signature.
Click to expand...
Click to collapse
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.

Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
Awesome. Thanks Aerowinder!
I will try this when I get home (assuming I can go into download mode...) and post what happened

Woody said:
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Click to expand...
Click to collapse
I will take a look at the link Woody.
I am really hoping this will work on the first try!
Okay so from reading your post Woody I can use EITHER the TWRP and CWR, but I want to use the one that is easiest to use. Which one do you guys think is easier to use?
Also, SU3.3 or SU1.04 which one should I use? Aerowinder, your sig shows both now but earlier I didn't notice the SU1.04. I just realized I only need the SU file IF the prerooted file doesn't work but just in case it doesn't I guess it is better to know.

Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.

Aerowinder said:
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Click to expand...
Click to collapse
I am going to try it in an hour.
Wish me luck!
1. Download mode
2. Flash CWM
3. Flash Root66
4. Hopefully no problems

:good:

Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
OMFG OMFG OMFG
OMFG OMFG OMFG
OOOOOOH MYYYYYY FOOOOOOOOKIN GOOOOOOOOOOOOSH
AEROWINDER AND WOODY
I LOVE YOU SO MUCH
IT WORKED AND NOTHING GOT ERASED. I THOUGHT PUTTING THE NEW FIRMWARE WOULD'VE ERASED EVERYTHING WITH THE NEW ROM BUT NOPE.
Uninstalled KIES and USB drivers.
Installed USB drivers from Aerowinders sig
So the Odin 3.07 didn't work either so I ended up using ODIN 1.85
Turned off auto reboot and left f reset on (no idea what f reset does lol)
Flashed CWM
Flashed root66 rom
Restarted phone and it was back to normal with all the data saved, but no SU (wasn't unlocked)
So reflashed CWM
Then restarted in clockwork recovery and ran super user and now the phone is rooted
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
:good::good::good: 3 thumbs up to the knowledge members above Aerowinder and Woody!
THANK YOU!
Panic mode TRANSFORMMMMM! *Panic mode has now transformed into excitement mode*

buzzking00 said:
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
Click to expand...
Click to collapse
So, ahh, are you excited? Haha. Great. Glad you got it up and running.
I hope that you do learn more about Android and share it with someone who needs help someday. When I first came, that is what someone did for me and I have tried to do it ever since. We are all still learning, including Aero and myself, so there will never be an end but rather more.
Good job and now you should make a Nandroid backup just in case you ever get in a bind again.

Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums

buzzking00 said:
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
Click to expand...
Click to collapse
That's the attitude, with Android you have to be a sponge and try to learn as much as you can. A single Google search will give you the answers you seek and making a backup is pretty much universal no matter what Rom, phone you have. Good luck
Sent from my SGH-T999 using xda app-developers app

cannot flash new AOKP (error 7)!!!!

hi guys,
I have a galaxy s3, in Canada, and cannot flash the newest AOKP (aokp_d2att_ota-eng-task650_7.20.2013b), I downloaded the I747MVLDLK4_aio.tar.md5 file and flashed it with odin as per instructions, then did a format,cache wipe/dalvik wipe, then try and write the new ROM, and all i get is error 7! ive tried it a few times! All i can say is im sure glad i did a NAND backup before i tried.
i dont understand whats wrong? i wasnt sure if i did the bootloader file right, but i followed directions, i put the phone in write mode, opened odin, clicked PDA, chose the file, and it wrote fine.no errors or anything. is there something i maybe missed?
can someone help me out?
TIA,
GINNZ

Maybe check to see if you have the latest recovery installed
Sent from my SGH-I747 using xda premium

ginnz said:
hi guys,
I have a galaxy s3, in Canada, and cannot flash the newest AOKP (aokp_d2att_ota-eng-task650_7.20.2013b), I downloaded the I747MVLDLK4_aio.tar.md5 file and flashed it with odin as per instructions, then did a format,cache wipe/dalvik wipe, then try and write the new ROM, and all i get is error 7! ive tried it a few times! All i can say is im sure glad i did a NAND backup before i tried.
i dont understand whats wrong? i wasnt sure if i did the bootloader file right, but i followed directions, i put the phone in write mode, opened odin, clicked PDA, chose the file, and it wrote fine.no errors or anything. is there something i maybe missed?
can someone help me out?
TIA,
GINNZ
Click to expand...
Click to collapse
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app

KorGuy123 said:
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Ok, thanks, I had an older version of AOKP running, which was released in December or so, and the recovery flashed was "RecoveryGalaxyS3USCanada.tar", I thought the new I747M4LDLK4 file was all i needed to flash this newer rom?
What exactly do i need? Im sorry for so many questions, but this just isnt making sense to me.... I managed to root the phone initially last year, and havn't done anything with it since.
so what is the newer I747M4LDLK4 file that i flashed with Odin for? Is the recovery initially flashed not the right one? if not, which one is needed, and how do i flash it? Id imagine with Odin, if so, do i just flash it the same as the I747M4LDLK4 file (PDA)?
im almost there, i just need a small push in the right direction....
Thanks for all your help so far, and please bare with me. I was an Apple jailbreaker for years, so this stuff is pretty foreign to me still.
---edit---
ok, so i went to twrp and found 2 recovery's, one is "openrecovery-twrp-2.6.0.0-d2att.tar" and one is "openrecovery-twrp-2.6.0.0-d2can.tar", this is where im confused, should i flash the "d2att", or the "d2can"? I mean, im in Canada, on MTS, and flashed the I747M4LDLK4, which was meant for Canada already....
also, can someone please clarify what the I747M4LDLK4 file is? it clearly states that canadian users MUST flash this before flashing the new AOKP, as it wont wont flash without it.... I did that, and still get Error7, now im looking at a new "recovery" as well, as i hope this will fix my error 7 issue. No where in the massive AOKP thread did it say that a different recovery would be needed as well, only the new I747M4LDLK4_aio.tar.md5 file!
so, anyways, if i flash a new recovery, (all i need to know is which one at this point), then i should be able to flash the new (AOKP) rom? i really dont wanna brick this thing, and i wish there wasnt so much confusion with the d2att/d2can files. it would seem completely logical that i would need the d2can file, but who knows, .... there was some sort of error on my phone when i tried to flash the ROM last night and d2att was in it somewhere......
im assuming the I747M4LDLK4_aio.tar.md5 is the bootloader, if so, i have the most recent one flashed now, so i must be getting the error because my recovery is out of date? i think im almost there, all i need is to know which recovery to flash, and i should be golden! the original recovery that is on the phone now from my first AOKP flash is "RecoverygalaxyS3USCanada.tar"
Ginnz.

ginnz said:
Ok, thanks, I had an older version of AOKP running, which was released in December or so, and the recovery flashed was "RecoveryGalaxyS3USCanada.tar", I thought the new I747M4LDLK4 file was all i needed to flash this newer rom?
What exactly do i need? Im sorry for so many questions, but this just isnt making sense to me.... I managed to root the phone initially last year, and havn't done anything with it since.
so what is the newer I747M4LDLK4 file that i flashed with Odin for? Is the recovery initially flashed not the right one? if not, which one is needed, and how do i flash it? Id imagine with Odin, if so, do i just flash it the same as the I747M4LDLK4 file (PDA)?
im almost there, i just need a small push in the right direction....
Thanks for all your help so far, and please bare with me. I was an Apple jailbreaker for years, so this stuff is pretty foreign to me still.
---edit---
ok, so i went to twrp and found 2 recovery's, one is "openrecovery-twrp-2.6.0.0-d2att.tar" and one is "openrecovery-twrp-2.6.0.0-d2can.tar", this is where im confused, should i flash the "d2att", or the "d2can"? I mean, im in Canada, on MTS, and flashed the I747M4LDLK4, which was meant for Canada already....
also, can someone please clarify what the I747M4LDLK4 file is? it clearly states that canadian users MUST flash this before flashing the new AOKP, as it wont wont flash without it.... I did that, and still get Error7, now im looking at a new "recovery" as well, as i hope this will fix my error 7 issue. No where in the massive AOKP thread did it say that a different recovery would be needed as well, only the new I747M4LDLK4_aio.tar.md5 file!
so, anyways, if i flash a new recovery, (all i need to know is which one at this point), then i should be able to flash the new (AOKP) rom? i really dont wanna brick this thing, and i wish there wasnt so much confusion with the d2att/d2can files. it would seem completely logical that i would need the d2can file, but who knows, .... there was some sort of error on my phone when i tried to flash the ROM last night and d2att was in it somewhere......
im assuming the I747M4LDLK4_aio.tar.md5 is the bootloader, if so, i have the most recent one flashed now, so i must be getting the error because my recovery is out of date? i think im almost there, all i need is to know which recovery to flash, and i should be golden! the original recovery that is on the phone now from my first AOKP flash is "RecoverygalaxyS3USCanada.tar"
Ginnz.
Click to expand...
Click to collapse
Okay, first thing first. You are reading WAY TOO MUCH into this, You need to slow down and do some reading on what is what for your phone.
There is no confusion about d2can and d2att in here. Here it is as simple as I can explain.
You live in Canada (as do I) our phones are SGH-I747M when you install a custom recovery (Clockworkmod or TWRP) The phone is registered as a Canadian model. The developers on this forum build ROMS for d2att only. They just happen to work on our phones as they are identical. To be able to flash these ROMS on our Canadian phones you have to flash the d2att recovery (Clockworkmod or TWRP)
So my suggestion was to make sure you have flashed the d2att recovery to your phone. You can get the Odin files from the websites or a quick search here would get you the flashable .zip files you would flash in recovery like a ROM (no wiping needed though)
Anything on THIS FORUM ONLY will not brick your device. Anything labelled under anything outside this forum ie. i9300 (International S3) or the other carriers will cause harm to your phone and you'll be a sad panda.
I747M4LDLK4 is your bootloader.
What Is A Bootloader?
In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. As the bootloader kicks off before any piece of software on your device, it makes it extremely processor specific and every motherboard has it’s own bootloader. This is one reason that all Android phones have different Custom ROMS developed due to high variance of processing hardware present on the device.
Click to expand...
Click to collapse
If you were to flash a US bootloader on your phone you'll be a sad panda.
The newer ROMS are requiring an updated bootloader to work properly. The newest Canadian bootloader MF1 still won't work for most of these ROMS so don't update it that far.
I don't know what else to suggest.
There are 2 main reasons for status 7 (3 if you're on a Canadian carrier which you are)

@KorGuy123
Nice job on the explanations. Many Users (none of which are obviously in this section of course ) would see that he was running a version of Task's ROM from December and jumped all over him. Keep up the good work.
OP ~ KorGuy123's last post points out to what a Status 7 recovery error is. Most of the times Status 7's are mainly due to Recovery issues. Bootloader issues will usually throw a [getprop ro.bootloader] error instead of a Status 7 just for future reference.

KorGuy123 said:
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for bearing with me guys!!! I got it. as was stated, i was overthinking the whole thing! i flashed a new recovery .d2att, and all went fine!
you guys are awesome!
ginnz.

ginnz said:
Thanks for bearing with me guys!!! I got it. as was stated, i was overthinking the whole thing! i flashed a new recovery .d2att, and all went fine!
you guys are awesome!
ginnz.
Click to expand...
Click to collapse
Glad it worked out for you. Enjoy!
Sent from my SGH-I747 using xda app-developers app

[Q] faild update

hey everyone , excuse my english iam still beginner.
i have i747 ATT and i was running on 4.2.1 , but i decide to get updated with 4.3 , i did download it and flash it but after doing all that the phone stops at setup screen showing nothing except apps has stop working example. unfortunately Samsung cloud data relay has stopped
please help and what i should do , thanks to you all

salahddine said:
hey everyone , excuse my english iam still beginner.
i have i747 ATT and i was running on 4.2.1 , but i decide to get updated with 4.3 , i did download it and flash it but after doing all that the phone stops at setup screen showing nothing except apps has stop working example. unfortunately Samsung cloud data relay has stopped
please help and what i should do , thanks to you all
Click to expand...
Click to collapse
Did you mean 4.1.2 or were you running a custom ROM as there is no official 4.2.1 for the i747? How did you download and flash the 4.3 ROM?
Can you try booting into recovery and doing a hard wipe/reset from there? If this doesn't solve it, then you may need to restore the system image via custom recovery.

Larry2999 said:
Did you mean 4.1.2 or were you running a custom ROM as there is no official 4.2.1 for the i747? How did you download and flash the 4.3 ROM?
Can you try booting into recovery and doing a hard wipe/reset from there? If this doesn't solve it, then you may need to restore the system image via custom recovery.
Click to expand...
Click to collapse
yes sorry i mean . 4.1.2 , i can boot to recovery mode and download mode too , i did wipe cash i did wipe data too but nothing works ,
Stock OTA Update 4.3 I747UCUEMJB 623.1MB , i did download that rom , if you need to know anything else please ask i really need your help

salahddine said:
yes sorry i mean . 4.1.2 , i can boot to recovery mode and download mode too , i did wipe cash i did wipe data too but nothing works ,
Stock OTA Update 4.3 I747UCUEMJB 623.1MB , i did download that rom , if you need to know anything else please ask i really need your help
Click to expand...
Click to collapse
You updated to 4.3 by going over the air or via Odin?

audit13 said:
You updated to 4.3 by going over the air or via Odin?
Click to expand...
Click to collapse
The 623mb file sounds like the stock image for (official) OTA updates. Most likely it was downloaded and flashed as a zip via recovery. I'm not quite sure it works that way.
Salahddine, since you can get into download and recovery modes, your best option now may be to do a complete stock restore via custom recovery. See the thread below for instructions. You may need to first flash custom recovery although I'd guess you probably have custom recovery installed already.
http://forum.xda-developers.com/showthread.php?t=2658486
Download the relevant file posted in the link to your phone's internal SD card or to an external micro SDHC card and place in your phone. Boot into recovery mode and flash the zip. Hopefully, this should fix it.

Larry2999 said:
The 623mb file sounds like the stock image for (official) OTA updates. Most likely it was downloaded and flashed as a zip via recovery. I'm not quite sure it works that way.
Salahddine, since you can get into download and recovery modes, your best option now may be to do a complete stock restore via custom recovery. See the thread below for instructions. You may need to first flash custom recovery although I'd guess you probably have custom recovery installed already.
http://forum.xda-developers.com/showthread.php?t=2658486
Download the relevant file posted in the link to your phone's internal SD card or to an external micro SDHC card and place in your phone. Boot into recovery mode and flash the zip. Hopefully, this should fix it.
Click to expand...
Click to collapse
audit13 said:
You updated to 4.3 by going over the air or via Odin?
Click to expand...
Click to collapse
thank you all for your support and caring , i did downgrade it to 4.0.4 , then i did face some problems like messaging stopped working and other things , then i did install RCWM 6.0.4.3 via odin , then i did install custom rom , then i did install d2att_I747UCUEMJ2_root_noknox and now everything works fine . i thank you all again for your caring
and about your question iam from morocco i cant get ON THE AIR , i did try it many times but didnt work so i did download that stock ROM 623 mb and i did flash from sd card

salahddine said:
thank you all for your support and caring , i did downgrade it to 4.0.4 , then i did face some problems like messaging stopped working and other things , then i did install RCWM 6.0.4.3 via odin , then i did install custom rom , then i did install d2att_I747UCUEMJ2_root_noknox and now everything works fine . i thank you all again for your caring
and about your question iam from morocco i cant get ON THE AIR , i did try it many times but didnt work so i did download that stock ROM 623 mb and i did flash from sd card
Click to expand...
Click to collapse
Sorry, my initial assessment was wrong. The 623MB zip you flashed was not the OTA file but the stock ROM which should have been flashed along with the modem and kernel zips at the same time. The reason for the initial failure was likely because you did not flash the kernel (and modem) zips. Glad to know it's working fine now.

[Q] Ace 2 stuck on Samsung Logo - won't go in recovery mode

Hey everyone
I have a huge problem with my ace 2, it is stuck on the Samsung logo and it won't go in recovery mode. Please, let me explain, I was fed up with my rooted 2.3 GB ace 2 and I decided to flash CM 10.2. I downloaded the .zip and flashed it along with the suitable gapps. After booting, I realised it did not have any signal and wifi was not available. After searching online for a while with not any results, I decided to flash CM 11. After that, wifi was back but still no signal. I said sc**w it and downloaded the official JB firmware for my phone from sammobile. After flashing it with odin, the phone won't boot. It stays in samsung screen. It won't even go in recovery mode in order to erase cache etc. I tried downgrading to the stock GB, ADB, KIES, DROID EXPLORER, the phone is recognised only in ODIN.
Can anyone help ?
-Thank you for your time

First Try odin with newest custom stocked rom. I got this "brick" couple times. And this think if working every time.

tsosmi_GR said:
Can anyone help ?
-Thank you for your time
Click to expand...
Click to collapse
Any (!!) CM needs JB FW at first...
I suggest to begin from scratch! Let the Phone boot completely after each FW flash.
1) Flash 3-Parted FW (see my sig) - Be sure you pick the correct one for you Phone (8160 / 8160P / 8160L)
2) Flash stock JB for your Phone and country
3) Flash CM11 and Gapps

fluffi444 said:
Any (!!) CM needs JB FW at first...
I suggest to begin from scratch! Let the Phone boot completely after each FW flash.
1) Flash 3-Parted FW (see my sig) - Be sure you pick the correct one for you Phone (8160 / 8160P / 8160L)
2) Flash stock JB for your Phone and country
3) Flash CM11 and Gapps
Click to expand...
Click to collapse
Hey man you saved me! Thank you very much! The three part rom did the trick! I bought an lg g3 this morning though thinkin my phone was totaled but Im gonna give my old (but thanks to you, working) ace 2 to my sister ..

Maybe this thread gonna help my prob.
Im accessing the thread by tapatalk and cant see what is your signature @fluffi444
Im suffering the same problem, the phone only able to enter downloadmode, i've tried install russian gingerbread with 3 file csc pda, and pit. But it doesnt work.
Maybe i need something else.
Sent from my Moto G using Tapatalk