Database Info

Samsung SCH-R910 MetroPCS problem

Hello all
i,ve samsung SCH-R910 MetroPCS phone , so i install CWM on it and backup everything , and then tried to install custom rom , and i get epic 4g cyanogenmod rom and when it begin to install the phone is rebooted into CWM and never get back my old OS i tried to reboot many times but still booted into CWM also i restore the original OS that i backed up before and it completed successfully but when rebooting the phone still booted into CWM ,
can anyone please help me just to return to the original rom or any custom rom
i need my phone just to work now i really stuck here please help me
thanks

where can i find official ROM for this model ??
please help me to restore my phone

I have a similar problem install CWM and make a backup, install CyanogenMod uns as not connected to the network restore the backup, now does not start and not let me get into Recovery, only stays on the screen for samsung mobile, please help.

There isn't cyanogen for the indulge, best I've found for this device is was a custom rom and kernel made by Konane posted on android forums all things root subsection for the indulge. Seems dev is dead for the device tho as it was posted last year and no new updates to it which are needed because it seems metro found a way to void some of the great improvements made.
Sent from my SCH-R720 using Tapatalk 2

Can I Odin back to a stock rooted rom?

My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?

eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
the files that you use to odin with are a different extension (.tar) than what you flash with (.rar)...so you can only use cwm/twrp to use that rooted image. I recommend using odin to get back to stock, then using the root one click method that was recently stickied...that will get you up in running and able to use roms quickly

Yes its possible but first try to install a custom recovery. Download goomanager and then install open recovery script from the menu options. Then you should be able to boot into twrp and flash a new rom
Sent from my XT912 using xda app-developers app

eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
If you are Verizon Stock rooted and have SU and busybox installed without disabling updates, that will occur whenever Verizon rolls out an OTA. if you want the update, ODIN back to stock and take the updates before rooting. If you don;t want updates then find the thread on disable Verizon OTA and that will stop the update request.

Android Noob.

Hello everybody at xda. My name is George and I'm fairly new to android hacking and such. It's been a month since I rooted my first phone (Samsung galaxy y) I found there was very limited custom ROMs but nevertheless was proud of what I had done. Since then, I have rooted a galaxy s gt I 9000 and have installed CM 11 nightly. It was fairly simple. I rooted my dad's lg optimus 4xhd p880. When I tried to install CWM recovery my dad's phone got an error report when trying to boot. (On the lg logo it had tiny red writing at the top.) After researching I discovered we hadn't unlocked his boot loader and trying to flash CWM had soft bricked. We ran the phone in SW mode by holding vol down with the battery out and connecting a USB to the computer. Then with lg tools flashed the stock recovery back. After that we unlocked the boot loader with a BL unlock .exe found on xda and BINGO!! I flashed CWM 6.0.4.4 touch on (because it's the only one that will flash 4.4+ kitkat ROMs in this device) and now it's flashed with beanstalks 4.4.2 ROM. It's totally amazing. I've also rooted a galaxy s3 mini gt I 8190n and flashed dmod on it witch is an OK rom. As much as I love rooting and stuff I don't have any more devices so I was hoping for some feedback and ideas of what I can do next!
Sent from my GT-I9000 using xda app-developers app

Galaxy S4 i9500 rom written to i9505 device!!!NEED HELP.

Hi guys.I am new to forum so i didn't know where to open this thread.Also i have checked internet for a solution but never seen a dumb thing like this before in my life.So even google search engine couldn't help me about that.
One of my friend has purchased a device from dubai.it is an original device of i9505 with snapdragon 600 processor.I am personally using an i9500 octa version btw.my friend told me to check his device after he had problems with gsm service+wifi for 3g doesn't connect(or connect and drops fast) so i went to check his device.i have used some system info tools and benchmark softwares to identify the device is ok.but NO IT WAS NOT OK.all of the system info tools says that the device is i9500 but it has snapdragon processor.some idiot somehow managed to write i9500 rom to i9505 and it is working with problems.i have checked camera both ok frontal and rear.and other device properties working good as well.i should expect that it should even fail to boot but somehow working with great deal of no phone service+3g problem(phone service sometimes work i really don't know how it works or how it fails).
So i decided to make things right.Which is put the right original galaxy s4 i9505 rom to that device.i have checked sammobile and found germany version of kitkat.
general info : device is rooted.it says it has Wanamlite rom 4.2.2.
My Try list:
1)downloaded odin 3.09 and followed the instructions.(used the official rom given from sammobile.)and put the mobile to download mode(i couldn't do it with volume down+home+power button cos it is not working)but i thought i was lucky cos that custom rom had an option when i push the power button/restart/ it says there is a download menu so i choose that to put the device to download mod.after that i was hoping odin will do the job.but it FAILED DUE TO WRITE PROTECTION ENABLED on device.
2)i tried to setup cwm recovery to device(which i figured out later it was already on device but i didn't know it was there).downloaded rom manager from playstore.and i thought it would work.rom managers says i had 2 recovery programs or rom managers on the phone 1 is cwm and other is teamwin recovery.also rom manager asks me to update or upgrade cwm but it does't recognise the device cos it is i9505 with i9500 rom and rom manager couldn't identify the device as it should be.so cwm update doesn't work.also i couldn't get to the user interface of cwm which is already on the device no matter what i do.also i know old version of cwm will not make it happen for what i need to do if i was able to get in the user interface as well.i think teamwin is blocking cwm.
so on rom manager i decided to use the team win cos there is no other option for me there which puts the phone after a restart to recovery mod,the user interface works ok there but teamwin also FAILED TO WRITE THE ROM(i think it is an old version too)i couldn't say the exact version of cwm cos the device is not with me and i forget the version but team win i asked to my friend just yet and he said TWRP 2.6.00 is on it.
3)CWM i can't even get to user interface,i really don't know how to with team win there.So yeah i couldn't even give a try.
4)I am stuck.and i don't know what to do.
general user profile about me: i have a general understanding of computers,but i haven't written any rom to galaxy s4 before yet i found myself in a situation i can't handle.someone screwed up an i9505 with a i9500 rom.
ANY HELP FROM ANYONE will be very appriciated.

i have managed to upgrade tw recovery with flashify to final version but in odin still write protection is enabled in the download mod.so odin again failed.btw after upgrading tw with flashify i lost my ability to get into operating system.i just have tw recovery on the screen atm.
the rom file i tried is this one I9505XXUFNB8_I9505VFGFNB3_I9505XXUFNB8_HOME.tar.md5 which i have downloaded from sammobile.
I9505XXUFNB8_I9505VFGFNB3_VOD.zip vodafone version it says for uk.
now i have a screen of tw recovery when the device opens.strange thing is i have 2 versions of tw recovery installed at the same time.when i press volume up+home+power tw version 2.6.00 loads.
or when i open the device with only power button tw recovery 2.7 loads.no operating system yet.
i tried I9505XXUFNB8_I9505VFGFNB3_VOD.zip with tw. it gave me an error of md5 not found and failed.
what now?
anybody around there to help?
another note : i don't know if it is important or not but it says the product name is sghi337.checked google it says at-t network.is this a useful information or what to identify the problem?
all i want is any rom to make the device work again with fully functioning.

after having twrp 2.7 i tried some roms had md5 error,so after a search i wanted to try wanamlite rom wanamlite-xxufnbe-v2-4-android-kitkat-4-4-2-xposed.after installing wanamlite rom it has asked me to reboot.so i did reboot it.it had adam kernel 2.1 version.
i was expecting the device will reboot but thanks to at&t for making odin useless + making twrp useless as well.it had a message on the screen and it was written ''samsung custom'' with a locker logo open.i thought i have to wait for the first boot and be patient and after waiting about half an hour still nothing.(on the left up of the screen written red : kernel)i checked more than maybe hundreds of threads to find an answer about at&t sghi337 galaxy s4 and some ppl say i have to change the kernel.and some say i have to change it to at&t kernel i searched again for an at&t kernel i found a file name KT-SGS4-TW-JB-ATT-06-06-2013.zip.then i gave a try to that.but suddenly i realized i have lost the ability of booting to twrp 2.7.all i have left with is twrp 2.6.00 when i press volume up+home.still lucky to have it.i used that kernel reboot and got a message on the screen ''system software not authorized by at&t''.then i started searching again ppl say about loki doki.downloaded the file and flashed it on at&t kernel this time it showed samsung logo appeared and the boot sound which you know all of us familiar with and samsung led was blue.the led was like it is a pounding heart coming on and off.this should be the first load of the rom i thought again and waited and got no result.it didn't load again.failed failed and failed many times.
i also tried this file named MDOB-KERNEL2STOCK-LIB.zip.flashed it no result again.failed.this result was another strange thing.it was showing samsung custom logo boot it with sound and then turn the device off after 10 seconds.and repeats the process.reboots sounds and reboots again and again.
questions :
1) do i have a bootloader locked device?since i can't use odin to flash anything.(odin version 3.09) and if i have what can i do to fix it?
2)since i only have twrp 2.6.00 how can i upgrade it to 2.7 back with twrp.i mean twrp update using twrp.
3)with twrp 2.6.00 i used wanamlite rom kitkat version.and it says it has flashed it.but can it flash roms succesfully enough like 4.4.2?if it says it flashed everything is ok? or it misses some important features to make the rom work.what is the maximum capability of twrp 2.6.00.Do i have to try roms like 4.2.2?
4)about kernels with at&t i337 galaxy s4 what can i do?what should be the reason preventing the rom load successfully?if i have access to twrp does it mean i don't have to mess with bootloader cos i have already passed that step and got an interface for loading roms?i mean everything is ok with bootloader if i have twrp installed user interface? and after flashing a rom do i have to use the specific kernel coming with the rom or can i use any kernel for the device like stock kernels(doen't allow me to load) with loki doki or some kernels with loki doki?
i am so helpless,please enlighten me with your knowledge.any moderators or any developers can answer me?or help me?
stuck in the middle of nowhere.please help.

Getting some progress at the end!!!
Since twrp 2.6.00 is the only option i have,or i can say ''was the only option i had'' i knew i had to get an android user interface for upgrading my recovery.after a bit more search i found slimroms for android version 4.2.2 just to make the device run,and it is already loki patched.so yeah that rom flashed as lightspeed and loaded extremely fast!that worked!!! i have downloaded aptoide market since it was lacking google apps.and downloaded flashify to upgrade the version of twrp to 2.7.01.from now on i believe i can find my way to whichever kitkat rom that is loki patched would work with this recovery support.
THANKS TO SLIMROMS for making downloadable and flashable small sized roms and tnx for the guy whoever found the loki way to make it possible.Also great thanks to TWRP team!!!
PLEASE NOTE THAT : Why did i write this after no reply or no help or no messages to this thread?Because i have figured out my way reading,trying and hard pushing after failing a lot but i found my way with xda developers threads out there even no one ever replied for help.I mean thanks anyway :cyclops:

When in doubt, flash to stock ROM and proceed from there.

you mean to tell me u cant enter download mode? ask someone to press the 3 buttons together to enter it and flash the firmware specified for that S4.

[Q] GT-N8010 stuck in logo and won't enter recovery

Hi folks,
I've seen other threads where people report similar but perhaps not quite the same issue I am having with my GT-N8010. For context, I installed 4.4.2 a while ago (February?). This was one of the Omni nightlies, omni-4.4.2-20140210. In preparation for this I had installed twrp-2.6.3.1-n8000. All was well and I much enjoyed kitkat until a few weeks came back from a trip and noticed the device had run out of juice. Connected it to the charger and then...
Symptoms:
* Seems to be stuck displaying the Samsung logo
* Download mode works
* When trying to enter recovery (Power+VOL_UP) it briefly shows the Team Win screen logo and then just reboots
Things I've tried:
* Reinstall twrp, using Odin and download mode; Odin succeeds, the device reboots, same symptoms as before
* Install some other recovery (HighOnAndroidv1CWMRecoveryGTN8000), same result; it is as though NOTHING gets flashed???
* Install stock (4.0.4 or 4.1.2, I don't remember) Samsung ROM; Odin succeeds (it takes a few minutes), device reboots but HECK I'm going insane NOTHING has changed, symptoms as before
Please please can one of you ninja dudes help me out as this is such a precious tablet and hopefully not just a brick now .
Among the things I haven't tried, but heard can do wonders, is to re-partition. So if you happen to have a PIT file from your N8010 then would you mind sharing it through a PM please.
Also am currently downloading the "official" 4.4.2 release for the N8000. I've heard this is NOT for the N8010 but as a last resort, I might flash it??
Many thanks in advance for all the help!
Matt

matt_9010 said:
Hi folks,
I've seen other threads where people report similar but perhaps not quite the same issue I am having with my GT-N8010. For context, I installed 4.4.2 a while ago (February?). This was one of the Omni nightlies, omni-4.4.2-20140210. In preparation for this I had installed twrp-2.6.3.1-n8000. All was well and I much enjoyed kitkat until a few weeks came back from a trip and noticed the device had run out of juice. Connected it to the charger and then...
Symptoms:
* Seems to be stuck displaying the Samsung logo
* Download mode works
* When trying to enter recovery (Power+VOL_UP) it briefly shows the Team Win screen logo and then just reboots
Things I've tried:
* Reinstall twrp, using Odin and download mode; Odin succeeds, the device reboots, same symptoms as before
* Install some other recovery (HighOnAndroidv1CWMRecoveryGTN8000), same result; it is as though NOTHING gets flashed???
* Install stock (4.0.4 or 4.1.2, I don't remember) Samsung ROM; Odin succeeds (it takes a few minutes), device reboots but HECK I'm going insane NOTHING has changed, symptoms as before
Please please can one of you ninja dudes help me out as this is such a precious tablet and hopefully not just a brick now .
Among the things I haven't tried, but heard can do wonders, is to re-partition. So if you happen to have a PIT file from your N8010 then would you mind sharing it through a PM please.
Also am currently downloading the "official" 4.4.2 release for the N8000. I've heard this is NOT for the N8010 but as a last resort, I might flash it??
Many thanks in advance for all the help!
Matt
Click to expand...
Click to collapse
There is a n8010 release of 4.4.2 for your Device. but Do NOT Flash the n8000 rom on it..
I think you should odin the 8010 rom from Sam mobile and you will be ok . If not browse the forum and find a pit file for that device.. also some have reported Issues flashing with latest odin. try i think verson 2.9 ?

erica_renee said:
There is a n8010 release of 4.4.2 for your Device. but Do NOT Flash the n8000 rom on it..
I think you should odin the 8010 rom from Sam mobile and you will be ok . If not browse the forum and find a pit file for that device.. also some have reported Issues flashing with latest odin. try i think verson 2.9 ?
Click to expand...
Click to collapse
Thanks, have just flashed the 8010 4.4.2 stock fw. Symptoms remain. I'd be very grateful for a PIT file as I've waded through the other threads and not too sure about the links to PIT files there. PM, anyone, please please .

I've got the N8010 PIT file from here:
http://forum.xda-developers.com/showthread.php?t=2363703
Sadly, this didn't change a thing. I'm still stuck at the Samsung logo, and still cannot enter recovery mode which still briefly shows the TeamWin logo and then reboots.
This N8010 is just over a year old. Bought in Germany, I wonder whether Samsung would repair under warranty. I guess they won't as it's been fiddled with. I've heard about JTAG repairs but something tells me this isn't going to help as I have a feeling that I just can't flash the darn thing. Eeek, faulty flash memory??

matt_9010 said:
I've got the N8010 PIT file from here:
http://forum.xda-developers.com/showthread.php?t=2363703
Sadly, this didn't change a thing. I'm still stuck at the Samsung logo, and still cannot enter recovery mode which still briefly shows the TeamWin logo and then reboots.
This N8010 is just over a year old. Bought in Germany, I wonder whether Samsung would repair under warranty. I guess they won't as it's been fiddled with. I've heard about JTAG repairs but something tells me this isn't going to help as I have a feeling that I just can't flash the darn thing. Eeek, faulty flash memory??
Click to expand...
Click to collapse
search for this file in the forum: Note10_PIT.zip (dunno0 where was it)
the if u can enter to download mode try to flash one of the latest 4.1.2 stock roms with odin 3.07....
if u succeed write here....:laugh:

karaern said:
search for this file in the forum: Note10_PIT.zip (dunno0 where was it)
the if u can enter to download mode try to flash one of the latest 4.1.2 stock roms with odin 3.07....
if u succeed write here....:laugh:
Click to expand...
Click to collapse
Sadly not. Others have reported that having gone with one of the Omni 4.4.2 builds they cannot get the official 4.4.2 release from Samsung installed, at least not with desktop Odin. They do succeed with mobile Odin but yeah, that's not an option here as I don't get past the Samsung logo and no recovery. This is really frustrating.....

matt_9010 said:
Sadly not. Others have reported that having gone with one of the Omni 4.4.2 builds they cannot get the official 4.4.2 release from Samsung installed, at least not with desktop Odin. They do succeed with mobile Odin but yeah, that's not an option here as I don't get past the Samsung logo and no recovery. This is really frustrating.....
Click to expand...
Click to collapse
Try to reinstall the latest rom u had before installing kk! Exact same version with same recovery.

matt_9010 said:
Hi folks,
I've seen other threads where people report similar but perhaps not quite the same issue I am having with my GT-N8010. For context, I installed 4.4.2 a while ago (February?). This was one of the Omni nightlies, omni-4.4.2-20140210. In preparation for this I had installed twrp-2.6.3.1-n8000. All was well and I much enjoyed kitkat until a few weeks came back from a trip and noticed the device had run out of juice. Connected it to the charger and then...
Symptoms:
* Seems to be stuck displaying the Samsung logo
* Download mode works
* When trying to enter recovery (Power+VOL_UP) it briefly shows the Team Win screen logo and then just reboots
Things I've tried:
* Reinstall twrp, using Odin and download mode; Odin succeeds, the device reboots, same symptoms as before
* Install some other recovery (HighOnAndroidv1CWMRecoveryGTN8000), same result; it is as though NOTHING gets flashed???
* Install stock (4.0.4 or 4.1.2, I don't remember) Samsung ROM; Odin succeeds (it takes a few minutes), device reboots but HECK I'm going insane NOTHING has changed, symptoms as before
Please please can one of you ninja dudes help me out as this is such a precious tablet and hopefully not just a brick now .
Among the things I haven't tried, but heard can do wonders, is to re-partition. So if you happen to have a PIT file from your N8010 then would you mind sharing it through a PM please.
Also am currently downloading the "official" 4.4.2 release for the N8000. I've heard this is NOT for the N8010 but as a last resort, I might flash it??
Many thanks in advance for all the help!
Matt
Click to expand...
Click to collapse
Did you ever find a solution ?

chappatti said:
Did you ever find a solution ?
Click to expand...
Click to collapse
Err well I ended up bringing the tablet to a Samsung service store where it was repaired under warranty, free of charge. Dunno what they did to it but it works and has the latest 4.4.2 firmware on it. Glad I have it back.

I have exactly same problem with N8005!... Can't reinstall twrp or any other recovery with Odin. ( "failed")... Can't enter twrp... Can't boot... I guess my tablet decided to suicide.