Database Info

I can no longer get into clockwork recovery...

I am on brainmasters miui rom, and whenever I try to go into recovery the phone just gets stuck on the Google logo and doesn't move, forcing me to pull the battery. I have tried reflashing the recovery numerous times and idk what to do from here. Any help would be greatly appreciated.
Sent from my Nexus S

Tried flashing another version of the recovery?

The K-Zoo Kid said:
I am on brainmasters miui rom, and whenever I try to go into recovery the phone just gets stuck on the Google logo and doesn't move, forcing me to pull the battery. I have tried reflashing the recovery numerous times and idk what to do from here. Any help would be greatly appreciated.
Sent from my Nexus S
Click to expand...
Click to collapse
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.

simms22 said:
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.
Click to expand...
Click to collapse
+1
I also made the experience that flashing recovery through rom manager doesn't always work...had the same problem, also using brainmaster's MIUI rom.

simms22 said:
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.
Click to expand...
Click to collapse
How would i go about doing this?

Check the rooting guides for the directions.
Sent from my Nexus S 4G using xda premium

I tried looking for directions on how to do it and for some reason I can't seem to find them.
Sent from my Nexus S

You obviously didn't try very hard
http://forum.xda-developers.com/showthread.php?t=1067813
[REF] Complete List of Roms | Kernels | Rooting/Other Guides for Nexus S (GSM)
I am not linking you to the direct directions, but I hope you will find your answer by finding a root guide from the first post.................
Sent from my Nexus S 4G using xda premium

I got the same problem after flashing the Clockworkmod 5.0. Then I flashed the 4.0x version (found in the rooting guide on XDA) and it's now working smoothly

zenithz said:
I got the same problem after flashing the Clockworkmod 5.0. Then I flashed the 4.0x version (found in the rooting guide on XDA) and it's now working smoothly
Click to expand...
Click to collapse
You should make sure you are erasing the old recovery before flashing a new one. This can be done as a fastboot command or through the advanced options in rom manager.
Sent from my Nexus S 4G using xda premium

HELP, Clockwork Recovery Loop!

I was trying to flash a eaglebloods ginger bread on my g2x... however every time the phone boots up it immediately goes into Clockworkmod Recovery and doesn't boot the OS. I've tried formatting and reinstalling the rom but i still get the same problem of the phone going directly into recovery instead of booting. Please help!

have you ever dropped the phone? Maybe the hardware button (volume down is stuck)is failing? I've never heard it automatically rebooting to recovery unless selected from the recovery to do so.

no i haven't dropped it or anything... the last thing i remember doing to the phone before it started doing this was clearing the cache and davilk cache...then it goes immediately to recovery...i just got the phone too, i hope i didn't brick it or something

you didn't "brick" it look up what that means in Urban Dictionary, before using it. If anything reflash the recovery with NVflasher or try a different rom.

tried reflashing clockwork and still have the same problem

tried a new rom? maybe use the clean up tool from in the dev section.

Re nvflash cwm. This has happened to me several times. Do not try to flash anything else until you nvflash cwm again. If that don't work use the rom for recovery in nvflash that is in the dev section.
Sent from my Galaxy Nexus using xda premium

kwes1020 said:
Re nvflash cwm. This has happened to me several times. Do not try to flash anything else until you nvflash cwm again. If that don't work use the rom for recovery in nvflash that is in the dev section.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Two post above yours he said he re-nvlashed.
Sent from my LG-P999 using xda premium

Im going to try to reflash a different version of CWR and hope that works... crossing my fingers

MAN.... i flashed the latest touch cwm and still no luck... tried new rom (hellfires gb) no luck...!!! just got this phone man! any suggestions welcomed

Try using this NVFLASH technique. It should restore your ROM & recovery to stock.

mt3g said:
Two post above yours he said he re-nvlashed.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
But the question is did any part of the flash fail. Just like flashing a rom. You can get bad flashes. Happens to me lots of times.
Bottom line flash the rom for recovery through nvflash and it will solve it. I've softbricked myself wayyyy too many times and got it back the same way. If it turns on and shows any graphic its not hard bricked.
andrewNY said:
Try using this NVFLASH technique. It should restore your ROM & recovery to stock.
Click to expand...
Click to collapse
This will resurrect it unless its not actually a g2x.
Sent from my Galaxy Nexus using xda premium

Thank you! this helped a lot!

andrewNY said:
Try using this NVFLASH technique. It should restore your ROM & recovery to stock.
Click to expand...
Click to collapse
you sir, are a gentleman and a scholar! THANK YOU!!!

djmeistro said:
no i haven't dropped it or anything... the last thing i remember doing to the phone before it started doing this was clearing the cache and davilk cache...then it goes immediately to recovery...i just got the phone too, i hope i didn't brick it or something
Click to expand...
Click to collapse
Make sure when you flash you wipe everything too, not just cache and dalvik cache
Sent from Narnia

[Q] after update to JB, not able to downgrade

Since upgrading to JB 4.1.2, I am not able to downgrade to ICS. After the flashing ICS via odin or for that matter mobile odin, is complete, it goes into a boot loop. Only way way out was again flash Jelly bean, it worked. Is there any firmware with full components like pda separate file, CSC separate file and phone separate file? I have heard that we need to flash these separate files via odin to downgrade. can anybody give a download link for the same?

Do you have a CWM back-up from a previous ROM?
Sent from my GT-P6210 using xda app-developers app

unfortunately no
Sent from my GT-P6200 using xda premium

seking said:
Since upgrading to JB 4.1.2, I am not able to downgrade to ICS. After the flashing ICS via odin or for that matter mobile odin, is complete, it goes into a boot loop. Only way way out was again flash Jelly bean, it worked. Is there any firmware with full components like pda separate file, CSC separate file and phone separate file? I have heard that we need to flash these separate files via odin to downgrade. can anybody give a download link for the same?
Click to expand...
Click to collapse
you must go to stock ricovery ( with power + volum up ) and then wipe data
( your data are remove ( factory riset )
sorry for my bad ENGLISH

But I have heard that if one wipes factory reset through stock recovery, I am afraid one is liable to get bricked devices.
Sent from my GT-P6200 using xda premium

I would research the factory reset option. It shouldn't brick your device.
Sent from my GT-P6210 using xda app-developers app

deleted

S-AJAD said:
don'd worry
if you wipe in stock recovery your divice aren't break
if you wip in cwm or other castom recovery with stock row your tab are breaked
Click to expand...
Click to collapse
I thought it was the opposite... (at least for ICS)

Alway wipe in cwm
S-AJAD said:
don'd worry
if you wipe in stock recovery your divice aren't break
if you wip in cwm or other castom recovery with stock row your tab are breaked
Click to expand...
Click to collapse
NO! Wipe data in STOCK recovery brick your device, but if you wipe in CWM you are safe.
For downgrade use this guide:
http://forum.xda-developers.com/showthread.php?t=1777003

skurys said:
I thought it was the opposite... (at least for ICS)
Click to expand...
Click to collapse
i do this work when i have this tablet
i had the cyanogen mod 10 and 10.1 and paranoid.
when i want back to stock rom i need to do this work and my tab doesn't break
but in JB i dont sure. i think other member are better than me.
sorry for my english

S-AJAD said:
don'd worry
if you wipe in stock recovery your divice aren't break
if you wip in cwm or other castom recovery with stock row your tab are breaked
Click to expand...
Click to collapse
Just to make it clear.. wiping from stock is Safe IF you are in HC or JB ( someone said its safe ) but a big NO in ICS because it causes the tab to be bricked.. wiping from CWM on all roms is SAFE.. pls.. get your facts right..
Sent from my GT-P6200 using XDA Premium HD app

If you want to downgrade from official JB to official ICS, you have to have .pit file
You can search pit file for P6200 in XDA and using odin to flash official ICS with option re-partition checked
First time, when my friend downgrade without .pit file, tab got stuck at SS logo even wipe everything fully. With .pit file, it succeeded

goodwellbest said:
If you want to downgrade from official JB to official ICS, you have to have .pit file
You can search pit file for P6200 in XDA and using odin to flash official ICS with option re-partition checked
First time, when my friend downgrade without .pit file, tab got stuck at SS logo even wipe everything fully. With .pit file, it succeeded
Click to expand...
Click to collapse
Is it necessary to have three different files ie pda, phone and csc when using pit file eith repartition checked?
Sent from my GT-P6200 using xda premium

No, just ICS Stock Rom with .pit file
P6200 pit file in this thread (http://forum.xda-developers.com/showthread.php?t=1667886) works fine

You can downgrade to HC, do wipes and flash ICS.

i usually do encounter this on my 7.7 when i flash hc from ics...what i did was wipe the device using cwm after flashing the older firmware to fix the bootloop...
my friend have tab 7 plus and i'm planning to flash jb on it...is the stock JB recovery free from the brickbug?

JAYZE said:
i usually do encounter this on my 7.7 when i flash hc from ics...what i did was wipe the device using cwm after flashing the older firmware to fix the bootloop...
my friend have tab 7 plus and i'm planning to flash jb on it...is the stock JB recovery free from the brickbug?
Click to expand...
Click to collapse
I guess it is safe becoz someone did it already and it did not got brick.. if i were you.. after flashing jb.. flash the CWM.. then from there do the wiping
Sent from my GT-P6200 using XDA Premium HD app

goodwellbest said:
No, just ICS Stock Rom with .pit file
P6200 pit file in this thread (http://forum.xda-developers.com/showthread.php?t=1667886) works fine
Click to expand...
Click to collapse
I used the pit file and the ics stock and flashed using odin, the flashing went off smoothly with odin saying success. But after booting mine stuck at the samsung animation for eternity. Again I had no other alternative than flash jb back again.
Sent from my GT-P6200 using xda premium

seking said:
I used the pit file and the ics stock and flashed using odin, the flashing went off smoothly with odin saying success. But after booting mine stuck at the samsung animation for eternity. Again I had no other alternative than flash jb back again.
Sent from my GT-P6200 using xda premium
Click to expand...
Click to collapse
Did you check option re-partition in Odin?
By the way, stuck at SS logo is quite often happened if you did not wipe. You should try to perform full wipe.
There is an issue related to wipe using ICS stock recovery, you should use Odin to flash CWM recovery (without .pit file) and use CWM recovery to wipe.

seking said:
I used the pit file and the ics stock and flashed using odin, the flashing went off smoothly with odin saying success. But after booting mine stuck at the samsung animation for eternity. Again I had no other alternative than flash jb back again.
Sent from my GT-P6200 using xda premium
Click to expand...
Click to collapse
when you are stuck in bootloop flash cwm recovery and do a full wipe..that will fix it...avoid full reset using stock recovery to prevent brickbug

[Q] CM Stuck on logo animation while booting

Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
- Rooted it using the following guide (it now has ICS)
- SIM Unlocked it using the following guide (now it works on other networks)
- Updated to CWM 6.0.3.8, since JB roms needs it
- Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.

TINGEA said:
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
-Rooted it using the following guide (it now has ICS)
-SIM Unlocked it using the following guide (now it works on other networks)
-Updated to CWM 6.0.3.8, since JB roms needs it
-Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
Click to expand...
Click to collapse
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk

Somcom3X said:
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!

TINGEA said:
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
Click to expand...
Click to collapse
No boot loaders man. This is before Samsung's complications.
Recovery is here.
http://d-h.st/AFu
Sent from my SAMSUNG-SGH-T769 using Tapatalk

Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

TINGEA said:
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.

Somcom3X said:
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?

BTW - when I was flashing via Odin my upload phone screen was showing that I have a custom rom and the counter was 1.... do I need to fix that?

TINGEA said:
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
Click to expand...
Click to collapse
SOLUTION:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Good Luck and Happy Tweaking.
Click to expand...
Click to collapse
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk

Somcom3X said:
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but I'm not sure this is needed for my case. I read the original blog post and my recovery does not get overwritten. I actually rebooted multiple times into CWM recovery and each time it is the same 6.0.4.4.
I also went into the /system/etc folder and there is no install_recovery.sh file.
to clarify, here is where I'm stuck now:
- when I use CWM 6.0.3.8 CM install completes successfully, but then CM will not boot, and will keep on cycling on the boot logo screen.
- when I use CWM 6.0.4.4 I can't start to install CM as it complained that my phone is not t769.
in all cases I'm using CM 10.2 nightly for T769.
Thanks for the help.

You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk

I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

TINGEA said:
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk

Somcom3X said:
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but this is more trouble than what I wanted to put in - I'll stick with the rooted stock ROM I have. I was hoping the process was a little more straight forward, similar to my SGS3.
thanks for all your help thus far!

Somcom3X said:
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!

TINGEA said:
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
Click to expand...
Click to collapse
Hmm. Go back to stock ics, flash a 10.2 recovery, then flash whatever you desire.
Sent from my SAMSUNG-SGH-T769 using Tapatalk

What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

TINGEA said:
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It would be cwm 6.0.2.7
You can flash the img through a zip or by terminal on the phone.
Odin needs a tar'd recovery img
Sorry been very busy.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2577265
Sent from my SAMSUNG-SGH-T769 using Tapatalk

Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.

TINGEA said:
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
Click to expand...
Click to collapse
I'm very sorry for the delay. Been very very busy.
https://www.dropbox.com/s/awp1zy4u3x34a2v/CWM-cm-10.2-Recovery-t769.zip
That is my personal 10.2 recovery. Works fine for me.
The author is me, but I was too lazy to change the lines.
Sent from my SAMSUNG-SGH-T769 using Tapatalk

[q] please help

Hello everyone i currently flashed my sph-d710 or sprint gaxy s2 to a kit kat rom. now first i tried flashing back to other roms, nothing lower then jb and i cant. so i was thinking of flashing a rom and tried backing up through rom manager and it brought me into recovery with an error. My a.d.d. having ass deleted the villumanti by accident b4 the error and i wiped/reset everything including cache during the error,and couldnt flash anything (i tried 3 roms). IN THE END I REBOOTED ALL WAS THERE.I think i have an idea of what happened. I think it could be due to a modem issue e.g. downgrading from kit kat to jb. Should i flash a custom kernel thru mobile odin and get the recovery from there(IM RUNNING THE LATEST CWM I BELIEVE)or should i boot into recovery wipe all data cache reboot recovery and flash the modem, reboot into recovery again proceed as normal. Also what modem should i use. If ive been to vague or you need any more info let me know. P.s. I ASK THAT ANY MOD WOULD APPROPIATELY PLACE THIS THREAD IN THE RIGHT SECTION SHOULD IT BE IN THE WRONG THANK YOU

Try to flash official firmware with odin
Sent from my GT-I9300 using XDA Premium 4 mobile app

Perfektas said:
Try to flash official firmware with odin
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey thanks man. I ended up using the one click root with Odin flash software from my computer while in bootloader mode then installed the mobile Odin app I placed on the SD and flashed agats recovery then immediately flashed cm10.1 with the gapps everything runs smooth not that it didn't before on kit kat that's another story
Sent from my SPH-D710 using xda app-developers app

I now ask that this thread get placed in an appropriate place until a better solution is brought up or deleted to avoid taking up valuable space sorry and thank you
Sent from my SPH-D710 using xda app-developers app