Database Develop

[INVALID] GingerBlur/GreyBlur + ALL AT&T Themes - DEPRECATED

This thread is no longer supported. Please reffer to: this thread

NOTES:
Attempted 3 times total. Working sucessfully for numerous users.
Followed guide above to the letter:
End result = Screenshots below.
Interestingly enough... System version of my phone = 4.1.5.7 Lol.... who knows what version it really is.
Baseband shows as: N_01.87.00R
This just means that the build.prop files was overwritten to display this:
ro.build.id=OLYFR_U4_1.5.7
ro.build.display.id=GreyBlur 2.0
ro.build.version.release=2.2.1
SCREENSHOTS:
Stock GreyBlur - Second Flash
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Honeycomb theme for 1.5.7 deodex - on TELSTRA 1.4.2 - GreyBlured..
D_one said:
I'm all for one atrix community, alot of the mods work on both bell and atrix, I think this is great news but would like more clarity on the specific differences between builds. Why does the factory wipe allow it to work?
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
Click to expand...
Click to collapse
Thats the fun part... XDA community can work together to find this out...
I was willing to put my phone in the fire based on random tips people wrote.
but not only that I went ahead and tested various methods, themes on top of that..
So this is really interesting considering what we thought and knew could not work.

This working on AT&T?

I saw someone saying this worked, I thought it was a fluke, amazing! So all the optimization to SD card speed and memory work? Any chance this would also work on stock bell (.37)?
If your version is matching at&t I wonder what's really happening? Could it just be a custom build.prop file?
That's some hybrid of a system you got there Seven
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!

DannyV94 said:
This working on AT&T?
Click to expand...
Click to collapse
You mean on 1.8.x?
Give it a go dude BE FEARLESS.. lol ionno but i'm freakin stoked because it worked on my Bell ATRIX

Dont try stock... just flash man, you will probably brick so just go 1.4.2 and thats that... either way its not like it matters because once you flash this you'll overwrite Stock and never get it back...

seven2099 said:
You mean on 1.8.x?
Give it a go dude BE FEARLESS.. lol ionno but i'm freakin stoked because it worked on my Bell ATRIX
Click to expand...
Click to collapse
I definitely would try it, but this phone needs to last at least another year, lol.
Don't really wanna brick it.
EDIT: BTW I'm not stock, I'm on GreyBlur 2.1 as of right now.

this is somewhat unnecessary since ken has started on a telstra sbf optimized version anyways, you might as well wait a few days and get a version that isn't quite as risky to install as this.

raybond25 said:
this is somewhat unnecessary since ken has started on a telstra sbf optimized version anyways, you might as well wait a few days and get a version that isn't quite as risky to install as this.
Click to expand...
Click to collapse
Thanks for that update on what ken's doing

raybond25 said:
this is somewhat unnecessary since ken has started on a telstra sbf optimized version anyways, you might as well wait a few days and get a version that isn't quite as risky to install as this.
Click to expand...
Click to collapse
Yeah i suppose you could do this if you were really impatient. We have already been waiting a while anyways so there is no harm in waiting just a couple more days

seven2099 said:
Dont try stock... just flash man, you will probably brick so just go 1.4.2 and thats that... either way its not like it matters because once you flash this you'll overwrite Stock and never get it back...
Click to expand...
Click to collapse
If I brick can't I still flash telstra? I'm pretty sure I can though I'll check first, I think someone did just that.
I'm going to sit tight with stock for the moment
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!

raybond25 said:
this is somewhat unnecessary since ken has started on a telstra sbf optimized version anyways, you might as well wait a few days and get a version that isn't quite as risky to install as this.
Click to expand...
Click to collapse
zero risk... whats wrong witchu..
Do you have any idea what this could mean for DEVs?
The idea that this phone was thought not compatible with ATT sbfs... yet we have managed to get a perfectly working nandroid of it working.
D_one said:
If I brick can't I still flash telstra? I'm pretty sure I can though I'll check first, I think someone did just that.
I'm going to sit tight with stock for the moment
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
Click to expand...
Click to collapse
No brick, both ROMs work 100% flawlessly and yes I re-flashed in between.

seven2099 said:
zero risk... whats wrong witchu..
Do you have any idea what this could mean for DEVs?
The idea that this phone was thought not compatible with ATT sbfs... yet we have managed to get a perfectly working nandroid of it working.
No brick, both ROMs work 100% flawlessly and yes I re-flashed in between.
Click to expand...
Click to collapse
except sbf's still don't work, unless you've gone ahead and flashed a stock AT&T sbf then the fact that this is cross compatible simply means that ken didn't hit any fatal system differences in his pseudo-ROM changes.

raybond25 said:
except sbf's still don't work, unless you've gone ahead and flashed a stock AT&T sbf then the fact that this is cross compatible simply means that ken didn't hit any fatal system differences in his pseudo-ROM changes.
Click to expand...
Click to collapse
yepp and? this means what?
I can now flash any other theme from any other person and have no problem getting it to work on my phone as well as not needing any ports just to have them remake their framework for my phone.
Tested:
Tangerine
HoneyComb
Next in line for test is:
Arc Theme. (LOVE THIS.. can't wait to see how it works out.)
I have only found one bug and this is with swype. This was fixed by restoring old swype back up. This means nothing to me anyways but if a dev wanted to he could make a universal pseudo ROM that would allow people to do their thing instead of flash and find maybe 0 or 1 themes for their crappy framework.
This has the potential to unite a community and not instead keep things seperate and everytime simply get more and more fragmented as we bell users know, we are TINY.. if even numerically tangible on here. So.. give that a thought for a bit.

I'm all for one atrix community, alot of the mods work on both bell and atrix, I think this is great news but would like more clarity on the specific differences between builds. Why does the factory wipe allow it to work?
PS. I was referring to trying it on stock
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!

D_one said:
I'm all for one atrix community, alot of the mods work on both bell and atrix, I think this is great news but would like more clarity on the specific differences between builds. Why does the factory wipe allow it to work?
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
Click to expand...
Click to collapse
Thats the fun part... XDA community can work together to find out why.....
I was willing to put my phone in the fire based on random tips people wrote.
but not only that I went ahead and tested various methods, themes on top of that..
I'd like a DEV to take a look at these results... because this is really interesting. No SBF needed and my phone behaves like 1.5.7.
I have tested, Webdock, mirroring.. all the functions except for swype (easily fixed).. WORKING.
So this is really interesting considering what we thought and knew could not work.
I would like to know from a DEV is how do I find out what I really have on my phone now..?

seven2099 said:
Thats the fun part... XDA community can work together to work this out.
I was willing to put my phone in the fire based on random tips people wrote.
but not only that I went ahead and tested various methods, themes on top of that..
I'd like a DEV to take a look at these results... because this is really interesting. No SBF needed and my phone behaves like 1.5.7.
I have tested, Webdock, mirroring.. all the functions except for swype (easily fixed).. WORKING.
So this is really interesting considering what we thought and knew could not work.
I would like to know from a DEV is how do I find out what I really have on my phone now..?
Click to expand...
Click to collapse
So your telling me that if i install it your way i can use the Webtop files from the AT&T build? i could never.. EVER figure that out for my phone for some reason.

Ratchet556 said:
So your telling me that if i install it your way i can use the Webtop files from the AT&T build? i could never.. EVER figure that out for my phone for some reason.
Click to expand...
Click to collapse
Lol you should check Sograth's thread.
I had that confirmed and working on 0.37 from bell..
Sograth even made a script fix just for us bell users son...
old news.

seven2099 said:
Lol you should check Sograth's thread.
I had that confirmed and working on 0.37 from bell..
Sograth even made a script fix just for us bell users son...
old news.
Click to expand...
Click to collapse
Yeah i tried it a while ago with no luck. ill try it again just for old times sake but im on 1.4.2 now and im not sure if it works with that yet.

Ratchet556 said:
Yeah i tried it a while ago with no luck. ill try it again just for old times sake but im on 1.4.2 now and im not sure if it works with that yet.
Click to expand...
Click to collapse
EDIT: I believe it should work as is atm. It just requires a bit of re-writing in his script.

Droid 3 update help please

just read this thread: http://forum.xda-developers.com/showthread.php?t=1334704 and was really wanting the update. It is critical that I don't ruin my new phone for financial reasons, but I am obsessed with upgrading the damn thing. Can someone walk me through the process of getting the update without bricking it? I really need someone who knows what they are doing, no offense to others that would try to help but might not be as capable.
My Droid 3 (about 2 days old), is one-click rooted with the DARK DROID ROM. Also just downloaded and installed the camera fix (sorry, I looked for the link but couldn't find it). Here are a few screen shots for information. Would you or anyone else that really knows what they are doing help me out with this?
Here are some screen shots, hopefully they can provide info I forgot to mention.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You need to go back to a pure /system to flash the update. And I do not know if our current root methods work for it or not (I haven't read that thread yet).
BTW, you had the fixed camera when you flashed DarkDroid

If you are talking about the leaked OTA update, then you need to get back to the original Motoblur ROM, with all of the bloatware still on it. Then download the update and put it in the root of your internal storage. At that point, (don't quote me on this, im trying it tomorrow) you will power off your phone, and hold x and power at the same time, and the recovery mode will boot up (use the volume keys to make the menu pop up). At that point, scroll down to the install/apply update thing, ( can't remember exactly what its called ) then find the update file.
Im not sure yet if you need to change the file name to update.zip, and make sure your battery is above 70% when you do this.
Any other people that know how to do this, feel free to correct me or add on to what I posted.
Sent from my DROID3 using XDA App

Oh and remember to get a root keeper app. Because the update removes root and moto/verizon removed the root exploit.
Sent from my DROID3 using XDA App

dpwhitty11 said:
You need to go back to a pure /system to flash the update. And I do not know if our current root methods work for it or not (I haven't read that thread yet).
BTW, you had the fixed camera when you flashed DarkDroid
Click to expand...
Click to collapse
Thanks, and that was some nice work on the ROM btw.
ChaoticWeaponry said:
If you are talking about the leaked OTA update, then you need to get back to the original Motoblur ROM, with all of the bloatware still on it. Then download the update and put it in the root of your internal storage. At that point, (don't quote me on this, im trying it tomorrow) you will power off your phone, and hold x and power at the same time, and the recovery mode will boot up (use the volume keys to make the menu pop up). At that point, scroll down to the install/apply update thing, ( can't remember exactly what its called ) then find the update file.
Im not sure yet if you need to change the file name to update.zip, and make sure your battery is above 70% when you do this.
Any other people that know how to do this, feel free to correct me or add on to what I posted.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
ChaoticWeaponry said:
Oh and remember to get a root keeper app. Because the update removes root and moto/verizon removed the root exploit.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks for the advice man. Check in with me tomorrow. Hopefully we'll both have working phones, LOL.

Grimace78 said:
Thanks, and that was some nice work on the ROM btw.
Thanks for the advice man. Check in with me tomorrow. Hopefully we'll both have working phones, LOL.
Click to expand...
Click to collapse
Haha, well I'll keep you updated, hard to screw up with updates though..

ChaoticWeaponry said:
Oh and remember to get a root keeper app. Because the update removes root and moto/verizon removed the root exploit.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I found 2 free apps for protecting an existing root. Voodo OTA and My Backup Root. Not sure if they will do the trick, but I am SO tempted to go ahead and try this update. Probably wait till tomorrow though.

Wish me luck! I can't hold off any longer and am going for it.

Grimace78 said:
Wish me luck! I can't hold off any longer and am going for it.
Click to expand...
Click to collapse
Good luck, I'm in the process of unbricking my phone (not from the update)

ChaoticWeaponry said:
Good luck, I'm in the process of unbricking my phone (not from the update)
Click to expand...
Click to collapse
what happened?

Grimace78 said:
what happened?
Click to expand...
Click to collapse
Installed a Bootstrap ROM on Safestrap. phones okay now, running Mavrick Beta.. lol

ChaoticWeaponry said:
Installed a Bootstrap ROM on Safestrap. phones okay now, running Mavrick Beta.. lol
Click to expand...
Click to collapse
I did the exact same thing, only I can't get past the MM symbol, and for the life of me cannot get into recovery either. The computer won't even recognize the phone. I think I'm screwed unless someone has a solution. The ONLY response that the phone has is to show the Motorola emblem if it is plugged into the wall, and afterwards turning it off is only possible by either letting the battery drain down or to pull it. I can't even turn it off and on.

Use my 5 min unbrick method. AP fastboot should never be broken.
Sent from my DROID3 using XDA App

ChaoticWeaponry said:
Use my 5 min unbrick method. AP fastboot should never be broken.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Found an odd way to "trick" it into CWM, but it won't stay in it. I think this could be a battery issue.

I would be very cautious as you say you have to keep this thing in good shape for financial reasons. There is an sbf but make sure you know how to use it and what you are doing before attempting the update.

pedwards3x said:
I would be very cautious as you say you have to keep this thing in good shape for financial reasons. There is an sbf but make sure you know how to use it and what you are doing before attempting the update.
Click to expand...
Click to collapse
Your warning was a good one, but I believe I got it done correctly (once I unbricked it, LOL). Does the system info look right to you?

[TOOL] HTC Vivid S-Off All-In-One Toolkit v1.0 [6-6-2012]

Post 1 - Information
Post 2 - Downloads and Release / Change Information
Post 3 - Bugs, Future Additions to the GUI, FAQ
Introducing Hasoon2000's New HTC Vivid All-In-One S-Off Toolkit!
This toolkit is here to get the party started to those who are looking to S-Off their devices!
If this helped you out, Please press the thanks button and if you want, you can always donate!
Prerequisites
- Must be on a stock ROM
- Must be HTCDev unlocked
- Must be rooted​
FEATURES​
- Links to a video and instructions to prepare you to S-Off your device
- HTC Drivers
- Command to flash an HBOOT of your choosing (Be sure you know what you are doing!)
- Command to flash a Recovery of your choosing
- Links
Donate to me (Hasoon2000) -> Donating to yours truly for putting time into this!
Juopunutbear S-Off Thread
Juopunutbear Website
PM me if you need a phone unlocked (XDA/AD)
S-Off Toolkit Thread (XDA)
Here is a screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How To Use. THIS IS FOR THE PC ONLY. No plans ever for Mac or Linux. Sorry.
1. Download the toolkit DO NOT RENAME THE FOLDER
2. Download Winrar from here. Install it after you download it
3. Extract the folder anywhere.
4. Run the program.
Credits
- The guys at the AutoIT help forum that helped me learn how to make the script!
- Developers that made ControlBear!
- The community for being awesome!
- HTC for making us the phone so we can be a community!
- To everyone else I may have forgotten!
*DISCLAIMER*​
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given
PLEASE NOTE: S-OFF CAN RENDER THE SD CARD IN OPERABLE! PLEASE USE A SMALL 1GB MEMORY CARD OR AT LEAST BACK UP YOUR FILES JUST IN CASE!!
DONATIONS​​

Downloads - All my Downloads will now be in my Dev-Host Account.
Link to All Available and Future Toolkits
http://d-h.st/users/hasoon2000/?fld_id=2769#files
V1.0 6-6-2012
- Initial Release

Bugs
- Directory has to have one word.
Ex:
Will Work. This will solve any issues if the buttons don't work when you press them.
C:\Users\John\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
C:\Users\John_Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
Will NOT work. Your directory will look something like this and buttons won't work when you press it.
C:\Users\John Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
If you have 2 words, put the folder in Drive C:
Ex. This will solve any issues if the buttons don't work when you press them.
C:\Amaze_All-In-One_Kit_V2.4
Click to expand...
Click to collapse
Looking to add in the future
- S-Off Mods
FAQs
Q - Why Did you make this?
A - To make life easier
Q - You are limited on features. Why?
A- You can always make a request!
Q - Will this work on other devices?
A - NO!!!!!!!!!!!!!!!!!!!!!!!! DO NOT DO THIS ON ANOTHER DEVICE!
Q - Will you support more devices in the future?
A - If people REALLY want, I can make it happen. I just don't want to make anything that nobody would use.
Q - Awesome! Can I make a donation?
A - Of course! Do not feel obligated though. If you would like to make a donation, you can click the button on my toolkit or under my username.

So cool, thanks for your hard work
Sent from my HTC PH39100 using XDA

ki11bert said:
So cool, thanks for your hard work
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
Took a long time to do so I hope you guys truly enjoy it!!!
Sent from my HTC_Amaze_4G using Tapatalk 2

Well the vid from the program is not working. Says its removed and me being a long time flasher. i almost feel like a noob with this guide. where is the hboot.img im supposed to put in the folder? cant find it. and does this method require the wire trick?

saywhat4118 said:
Well the vid from the program is not working. Says its removed and me being a long time flasher. i almost feel like a noob with this guide. where is the hboot.img im supposed to put in the folder? cant find it. and does this method require the wire trick?
Click to expand...
Click to collapse
I guess they removed the video?
I do not provide HBOOTs.
- Command to flash an HBOOT of your choosing (Be sure you know what you are doing!)
Click to expand...
Click to collapse
Since many people do not know what it is, I do not provide them since people will brick their phones since they have no clue what an HBOOT is.
This does require the wire trick. I just made everything simplified.

hasoon2000 said:
I guess they removed the video?
I do not provide HBOOTs.
Since many people do not know what it is, I do not provide them since people will brick their phones since they have no clue what an HBOOT is.
This does require the wire trick. I just made everything simplified.
Click to expand...
Click to collapse
Got it, thank you.

could yoou reup the video? doesnt seem to be working on the program

oneslow5oh said:
could yoou reup the video? doesnt seem to be working on the program
Click to expand...
Click to collapse
They deleted it. I can show you a similar video (it is the same process)
Sent from my HTC_Amaze_4G using Tapatalk 2

hasoon2000 said:
They deleted it. I can show you a similar video (it is the same process)
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Who deleted it? Where did you have the video posted?
Sent from an HTC Vivid via XDA Premium

The op of the s-off wire trick
Sent by my WCX powered Vivid

#Winning
http://www.xda-developers.com/android/easy-s-off-for-amaze-vivid-rezound-and-mytouch-4g-slide/

Good job.

first of, i wanna thank hasoon2000 for all your hard work including this method to s off. bec of all your easy steps, i successfully permroot my htc raider from rogers, canada, and then s offed. however, im currently facing a major problem, and im hoping anyone in this thread could help me out. i recently relocked my bootloader without knowing that i wont be able to unlock it again with the same procedure using the htcdev unlock.bin command after being s offed. can anyone plz plz help me what to do...
is there a special command for this or method i could use; thanks much in advance guys.

JohnL_83 said:
first of, i wanna thank hasoon2000 for all your hard work including this method to s off. bec of all your easy steps, i successfully permroot my htc raider from rogers, canada, and then s offed. however, im currently facing a major problem, and im hoping anyone in this thread could help me out. i recently relocked my bootloader without knowing that i wont be able to unlock it again with the same procedure using the htcdev unlock.bin command after being s offed. can anyone plz plz help me what to do...
is there a special command for this or method i could use; thanks much in advance guys.
Click to expand...
Click to collapse
S-off is an unlocked bootloader. Forget about HTCDev. You never have to use it again once you have S-Off
Sent from my HTC_Amaze_4G using Tapatalk 2

hasoon2000 said:
S-off is an unlocked bootloader. Forget about HTCDev. You never have to use it again once you have S-Off
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
so then, how come im not able to install your cwm again from the vivid all in one v2.2
i thought about that too; once ur s off, you pretty much can do anything. but i cant get the cwm back bec im getting some error from ur vivid 2.2. this happened before the whole s off; i cant use the recovery menu from bootloader if its locked, so i knew i had to unlock it to get it worked.

JohnL_83 said:
so then, how come im not able to install your cwm again from the vivid all in one v2.2
i thought about that too; once ur s off, you pretty much can do anything. but i cant get the cwm back bec im getting some error from ur vivid 2.2. this happened before the whole s off; i cant use the recovery menu from bootloader if its locked, so i knew i had to unlock it to get it worked.
Click to expand...
Click to collapse
Did you install the JB HBOOT?
Sent from my HTC_Amaze_4G using Tapatalk 2

hasoon2000 said:
Did you install the JB HBOOT?
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
yes i did
well i guess if tell u the whole story, u'll know whats goin on. the reason i had to relock the bootloader was coz i was trying to install an official ics ruu (the at&t us ver) from one of the forums here. i was successful of doin it, except one thing was missing: i couldnt use my data to browse the net. i thought if i had my bootloader again locked, it would work. but still didnt.
i wasnt still able to fix that but its not really my main concern right now.
one thing i noticed tho after i installed the jb hboot after s off was successful - the lock/unlock mssg on top of my bootloader was changed w/ jb name. but after i installed the ics ruu and went to my bootloader, it was backed to unlock/lock msg; it was till s offed tho...
so basically thats the whole jits of it. before this whole mess i was able to do a nandroid backup on my sd card with everything on it, including permroot. since then i've been trying to get it backed unlock to get the cwm back and do a restore...

can I get a link to the video pllz...
Thanks in advance.

Messed up screen after ICS update

Hi everyone,
I tried to install the new ICS ROM for my P7310.
Had CM10 installed and first tried to install the modified one via CWM.
Worked like a charm, but after screen was off it became messed up just like this guy had it.
Then I tried to flash the Stock ROM via ODIN. Installed just fine, but now I have the same messed up screen.
Problem is: It is messed up in Stock Recovery, too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can I install an older ROM (which one, tab is from Switzerland) or CWM via Odin?
I think I could hit the download mode without seeing what is on the screen
Thanks in advance!

(Edit: for a solution, scroll to end of this post)
I've heard "garbled screen" a few times regarding the ICS update.
Have you seen these posts? They suggest a solution... (and there's even another reference to Switzerland...)
I don't have experience with the issue, and can't comment beyond what I read elsewhere.
rufree2talk said:
I bought the Tab 8.9 in Switzerland recently... am fairly well informed about working around Android devices... updated the firmware on my stock Honeycomb to the US ICS release via Odin... no issues in the process, and the tablet came up smart and zippy running ICS... even got the Play Movies/Books/Music app which normally doesn't feature in devices sold outside USA... although not much use of them unless I use a VPN service...
the problem is that as soon as I lock the device, or the screen times out, on trying to unlock the device I am met by a garbled unworkable screen... there is no option but to hard-reboot the device to get it working again... somebody is having the same issue here, but I can't post in Development forums... have tried reflashing and all, but its always the same thing... even with stock USA Honeycomb its the same behaviour... is there a region limitation to this firmware for proper functionality?
Click to expand...
Click to collapse
gatt088 said:
Same issue here.. As whit every usa stock based version... I have bricked my tab 2 times, i will appreciate that this issue will be mentioned in new threads as not every xda member is from usa. No problems with jb aosp and cm based version. Waiting for some european stock version
Click to expand...
Click to collapse
rufree2talk said:
I managed to workaround this issue... flashed the P7310UELA3 3.2 via Odin, booted into recovery, performed factory reset/data erase, again flashed P7310UELPB 4.0 via Odin, and this time the Tab has no issue! it works like it should and there is no garbled screen on unlocking... if you want to save your app data before you do these steps, use Titanium...
Click to expand...
Click to collapse
Hurrian said:
If you're not on ICS yet but plan on upgrading, flash P7310UELA3 first. It seems that for some, flashing ICS straight gives you the weird screen strobing.
Click to expand...
Click to collapse
Edit: confirmed solution
by now several people have confirmed that flashing the P7310UELA3 is a working solution to screen flickering after resume from standby. (Flash the UELA3 using Odin, then flash again the ROM you really want to run)
You can find UELA3 ROM via any of these links:
http://forum.xda-developers.com/showthread.php?p=24482346#post24482346 (thx nirogu325 - also linked in post #1 same thread)
http://samsung-updates.com/gt-p7310-galaxy-tab-8-9-wi-fi/
http://forum.xda-developers.com/showthread.php?t=1483168
be kind and hit "Thanks" if this helped you

Thanks a lot!
Installed as supposed, everything is fine now

Glad to know it helped. Good to have that confirmed, for others who may have this...
Click thanks to say thanks

fred_be9300 said:
Glad to know it helped. Good to have that confirmed, for others who may have this...
Click thanks to say thanks
Click to expand...
Click to collapse
Sure

You sir saved my day. Should be posted in the top thread.

Guess the search function will do for most ppl

Back to HC and to ICS again?
I've seen this quote a day late.
" If you're not on ICS yet but plan on upgrading, flash P7310UELA3 first. It seems that for some, flashing ICS straight gives you the weird screen strobing."
Now I have screen problems on ICS when I connect a data cable http://forum.xda-developers.com/showpost.php?p=31410065&postcount=21. If I downgrade via Odin to P7310UELA3 and then go back to ICS via Odin, will data be preserved?
Update after flashing:
I flashed the recommended HC version, Tab couldn't get through bootanimation sequence. I turned the Tab off and started download mode again. Reflashed with ICS and all data was still there. Only the homescreens were empty again. My screen problem is fixed though.

this continues to happen (to small minority?) of people moving from HC to ICS, but seems to be hard to find.
(last case: http://forum.xda-developers.com/showthread.php?t=1895361)
(I've included it a new FAQ I posted here)

thanks
thaks all of u u really save my tablet! I thought it was damaged! I applied the above procedure and everything is perfect now

Hi Everyone
I'm doing something wrong here, hope someone can help.
Every time I install a ROM (Jellybean or ICS) I get the garbled screen after standby.
So, I've tried flashing the P7310UELA3 via Odin and I get a fail, do I just upload it to Bootloader or PDA?
My P7310 is a French version and I have tried flashing the French bootloader too, but still get fail.
I am a noob at this, but I am so close to installing a good rom but fail at the final hurdle. Any help would be fantastic.
Cheers

MikeMcGrathXmen said:
Hi Everyone
I'm doing something wrong here, hope someone can help.
Every time I install a ROM (Jellybean or ICS) I get the garbled screen after standby.
So, I've tried flashing the P7310UELA3 via Odin and I get a fail, do I just upload it to Bootloader or PDA?
My P7310 is a French version and I have tried flashing the French bootloader too, but still get fail.
I am a noob at this, but I am so close to installing a good rom but fail at the final hurdle. Any help would be fantastic.
Cheers
Click to expand...
Click to collapse
flash the full rom as PDA

prince93 said:
flash the full rom as PDA
Click to expand...
Click to collapse
Doesn't seem to work for me, i keep getting fail, maybe because its a French version? I really dont know what else to do!

MikeMcGrathXmen said:
Doesn't seem to work for me, i keep getting fail, maybe because its a French version? I really dont know what else to do!
Click to expand...
Click to collapse
you need to UNCHECK the "repartition" option.. have you already done this ?

prince93 said:
you need to UNCHECK the "repartition" option.. have you already done this ?
Click to expand...
Click to collapse
Yeah, mine is defaulted with repartition unchecked. I really dont understand what I'm doing wrong.

MikeMcGrathXmen said:
Yeah, mine is defaulted with repartition unchecked. I really dont understand what I'm doing wrong.
Click to expand...
Click to collapse
do you get the communication port with a yellow color before flashing?
also, make sure you are using the original USB cable that came with your tablet to flash it

I flashed my 7310 with UELA3 using Odin and then used default recovery to install CWM 6.0.0.8.
But now CWM is rolling very fast, not readable.
I found this solution, but it's for the 10.1 tab. http://forum.xda-developers.com/showthread.php?p=27830023#post27830023
Should I try it on my 8.9?

Need ROM P7310UELA3 - hotfile links brokrn
Hi,
Thank you for sharing this solution.
Unfortunately , I could not find a working link to ROM P7310UELA3, since hotfile was shut down.
Could anyone share this ROM with me ?
Thank you, Jacques.

jfy65 said:
Hi,
Thank you for sharing this solution.
Unfortunately , I could not find a working link to ROM P7310UELA3, since hotfile was shut down.
Could anyone share this ROM with me ?
Thank you, Jacques.
Click to expand...
Click to collapse
I think this P7310UELA3 is android 3.2, and the android ICS 4.0.4 is available
so even if you want an android 3.2, I don't think you'll find anyone who can share it with you
If it is OK to use android ICS there is a link I already uploaded to Dev-Host HERE
this is all I got, and this all I have and can share with anyone

Need ROM P7310UELA3 - hotfile links broken
omarainea said:
I think this P7310UELA3 is android 3.2, and the android ICS 4.0.4 is available
so even if you want an android 3.2, I don't think you'll find anyone who can share it with you
If it is OK to use android ICS there is a link I already uploaded to Dev-Host
this is all I got, and this all I have and can share with anyone
Click to expand...
Click to collapse
Thanks. This whole stream is about the problem with the installation of stock ICS ROM which results in screen flickering on some devices. It happened to me after upgrading with KIES: The tablet becomes completely unusable. The solution suggested and tested above is to flash P7310UELA3 before ICS. Unfortunately, I could not find a working link to ROM P7310UELA3, since hotfile was shut down.
Could anyone share this ROM with me ?
Thank you, Jacques.

[Q] CM 10.1 query

I'm new to the captivate , I just bought a captivate off ebay with cm 10.1 , i just bought it to learn more about android , and i would like to know how i can
Unroot (which way (one click etc) to use? , because i do not know which way was used to root the phone ? )
Reason i ask this is , coz i was reading some of the stickies , i read somewhere that if u are on CM , then when u restore to stock , i have to do something to the root partition?

ALSO , The phone is running CM 10.1 , i would like to downgrade to 2.1 or 2.1 so that i can sim unlock the phone?.. how do i downgrade?

Here is the Stock One Click Master Collection... http://forum.xda-developers.com/showthread.php?p=18370235
The other Stickied threads in the Dev and Q&A forum will prove useful as well.
Sent from my SAMSUNG-SGH-I747 using xda premium

4-2ndtwin said:
Here is the Stock One Click Master Collection... http://forum.xda-developers.com/showthread.php?p=18370235
The other Stickied threads in the Dev and Q&A forum will prove useful as well.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thank you so much for your reply
Just to clarify - can i use the odin one click packages found in this post (am not sure whether i have to use with or w/o bootloader?) ? , if i just flash them to my phone via odin one click , everything will go back to stock? (am on cm 10.1 , internal sd card will be partitioned right?) , and will i lose root too?
On a totally different topic , what if i dont want to go back to stock , unroot , but want to keep the root , and try out different roms on other versions (GB,ICS) (i am currently on cm10.1 jb) , what do i have to do?
Sorry for being a pain , but i read through the threads , im just confused , because i read everywhere about the not to flash gb bootloaders etc , so even if the rom is jellybean , its based on a gb bootloader?

galaxys3lover said:
Thank you so much for your reply
Just to clarify - can i use the odin one click packages found in this post (am not sure whether i have to use with or w/o bootloader?) ? , if i just flash them to my phone via odin one click , everything will go back to stock? (am on cm 10.1 , internal sd card will be partitioned right?) , and will i lose root too?
On a totally different topic , what if i dont want to go back to stock , unroot , but want to keep the root , and try out different roms on other versions (GB,ICS) (i am currently on cm10.1 jb) , what do i have to do?
Sorry for being a pain , but i read through the threads , im just confused , because i read everywhere about the not to flash gb bootloaders etc , so even if the rom is jellybean , its based on a gb bootloader?
Click to expand...
Click to collapse
Bootloader: GB = GB, ICS, JB / Eclair = Eclair, Froyo.
Flashing Odin3 one click downloader will flash the Eclair bootloaders, unroot and bring you back to stock. If you want to root on stock 2.1, simply flash a custom kernel in recovery. From 2.2+, they added the signature verification and you'll have to use Odin 1.87 to flash a custom kernel (to get cwm), which will also root your device.
To get back to GB+, you'll have to flash Odin KK4 with bootloaders. From there, follow this guide to get on whichever ROM you want. Remember to always follow the FULL ROM instructions (I'd suggest to avoid ICS due to the EU bug).
For any JB ROM, you'll have to flash the ROM twice as the first time, it has to repartition. Also, a few JB ROM don't include the Gapps so you'll have to flash them after flashing the ROM.
For any ROM, you can use the kernel that is provided or flash another one, just make sure it is compatible with the ROM you're running (2.1, 2.2, 2.3, 4.0, 4.1.2, 4.2.2).
P.S.: The reason why you see not to flash bootloaders everywhere is cause that's the only way to hard brick your phone, if it goes wrong that is (USB unplugs, bad connections, etc.). Also, you'll notice it fast enough but JB is seriously the best you can do to that phone beside Froyo Firefly with Speedmod kernel (less features of course).

P.S.: The reason why you see not to flash bootloaders everywhere is cause that's the only way to hard brick your phone, if it goes wrong that is (USB unplugs, bad connections, etc.). Also, you'll notice it fast enough but JB is seriously the best you can do to that phone beside Froyo Firefly with Speedmod kernel (less features of course).
Click to expand...
Click to collapse
This pretty much sums up what I was going to say. I can honestly say I'd never want this phone to go back to stock after trying out the JB ROMs. The phone doesn't suffer from speed issues at all, you can OC (depending on hardware, mine really can't but some people have theirs clocked at 1.4ghz/140%). Unless you were selling the phone back to AT&T or taking it in for repair or what not, I see no reason to be on 2.2 not-rooted etc.

x0ne215 said:
This pretty much sums up what I was going to say. I can honestly say I'd never want this phone to go back to stock after trying out the JB ROMs. The phone doesn't suffer from speed issues at all, you can OC (depending on hardware, mine really can't but some people have theirs clocked at 1.4ghz/140%). Unless you were selling the phone back to AT&T or taking it in for repair or what not, I see no reason to be on 2.2 not-rooted etc.
Click to expand...
Click to collapse
Thank you so much!!! This helped me and i can see a lot of other people too , Thank you Great support guys Cheers
P.S : Man! am i an aidiot for buying a captivate , everywhere i look it just seems like i see only one word - BRICK BRICK BRICK! , i should have got someother phone

galaxys3lover said:
Thank you so much!!! This helped me and i can see a lot of other people too , Thank you Great support guys Cheers
P.S : Man! am i an aidiot for buying a captivate , everywhere i look it just seems like i see only one word - BRICK BRICK BRICK! , i should have got someother phone
Click to expand...
Click to collapse
If you read carefully and understand everything you're doing before doing it, you won't brick it. That stands for every devices. The problem is that people are too eager (impatient) to hack it and rush into it without knowing what they're doing. And remember, the only way to actually brick it if something goes wrong while flashing the bootloaders and even then, it's recoverable with JTAG service.

galaxys3lover said:
P.S : Man! am i an aidiot for buying a captivate , everywhere i look it just seems like i see only one word - BRICK BRICK BRICK! , i should have got someother phone
Click to expand...
Click to collapse
What are you talking about? You'll need to do something extremely stupid to hard brick the Captivate. And its still repairable even after hard brick. All ROM change procedures are very well documented, just follow the instructions and your Captivate will live long life. Not too many phones have same great support like Captivate.

I love my cappy, there are so many guides here and people with knowledge there should be no reason you brick your phone other than:
1. If you get lazy and try to skip steps
2. You don't ask when you don't know
Check out the rest of the Q/A section, there are step by step guides on rooting/flashing that are pretty much brick proof if you follow along.

galaxys3lover said:
Reason i ask this is , coz i was reading some of the stickies...
Click to expand...
Click to collapse
Please, read carefully all stickies, not just some of them. Many knowledgeable people here put a lot of time to explain everything about Captivate in an easy to understand way. You'll quickly find all the answers to your questions, including different ways to achieve same results. I got my Captivate with stock 2.3 ROM and 2 days later it was rooted, with CWM and running custom JB ROM. I also managed to soft brick it twice (playing with it and trying almost every ROM available) but recovered for minutes using the great info here on XDA.

Val D. said:
Please, read carefully all stickies, not just some of them. Many knowledgeable people here put a lot of time to explain everything about Captivate in an easy to understand way. You'll quickly find all the answers to your questions, including different ways to achieve same results. I got my Captivate with stock 2.3 ROM and 2 days later it was rooted, with CWM and running custom JB ROM. I also managed to soft brick it twice (playing with it and trying almost every ROM available) but recovered for minutes using the great info here on XDA.
Click to expand...
Click to collapse
This ^
And even if you manage to hardbrick one, you can still recover from that. The only thing that might not be fixable is if you run it over in your car

BWolf56 said:
If you read carefully and understand everything you're doing before doing it, you won't brick it. That stands for every devices. The problem is that people are too eager (impatient) to hack it and rush into it without knowing what they're doing. And remember, the only way to actually brick it if something goes wrong while flashing the bootloaders and even then, it's recoverable with JTAG service.
Click to expand...
Click to collapse
Val D. said:
What are you talking about? You'll need to do something extremely stupid to hard brick the Captivate. And its still repairable even after hard brick. All ROM change procedures are very well documented, just follow the instructions and your Captivate will live long life. Not too many phones have same great support like Captivate.
Click to expand...
Click to collapse
x0ne215 said:
I love my cappy, there are so many guides here and people with knowledge there should be no reason you brick your phone other than:
1. If you get lazy and try to skip steps
2. You don't ask when you don't know
Check out the rest of the Q/A section, there are step by step guides on rooting/flashing that are pretty much brick proof if you follow along.
Click to expand...
Click to collapse
Val D. said:
Please, read carefully all stickies, not just some of them. Many knowledgeable people here put a lot of time to explain everything about Captivate in an easy to understand way. You'll quickly find all the answers to your questions, including different ways to achieve same results. I got my Captivate with stock 2.3 ROM and 2 days later it was rooted, with CWM and running custom JB ROM. I also managed to soft brick it twice (playing with it and trying almost every ROM available) but recovered for minutes using the great info here on XDA.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JUST KIDDING
Yeah i understand , i just thought since everywhere i saw i only read the word BRICK , i must have made a mistake buying the phone , turns out this is one of te few phones that have a lot of solutions if your phone does get 'BRICK'ed , MY BAD ! :cyclops: and also probably one of the few phones , that even after everybodys moved onto other phones , there are so many people giving support to newcomers! Thanks Guys ! :good::good: :laugh::laugh:
x0ne215 said:
This ^
And even if you manage to hardbrick one, you can still recover from that. The only thing that might not be fixable is if you run it over in your car
Click to expand...
Click to collapse
Haha , ! hopefully i dont end up doing that

galaxys3lover said:
JUST KIDDING
Yeah i understand , i just thought since everywhere i saw i only read the word BRICK , i must have made a mistake buying the phone , turns out this is one of te few phones that have a lot of solutions if your phone does get 'BRICK'ed , MY BAD ! :cyclops: and also probably one of the few phones , that even after everybodys moved onto other phones , there are so many people giving support to newcomers! Thanks Guys ! :good::good: :laugh::laugh:
Haha , ! hopefully i dont end up doing that
Click to expand...
Click to collapse
It surprised me too how many people still offer support and help for this phone, it's almost 3 years old now
No problem, and unfortunately I've had the pleasure of doing that to 2 phones I've owned....
Pro tip: Don't wear basketball shorts and put your phone without a rubber case or similar in it....it will most likely fall out and you won't notice

x0ne215 said:
It surprised me too how many people still offer support and help for this phone, it's almost 3 years old now
No problem, and unfortunately I've had the pleasure of doing that to 2 phones I've owned....
Pro tip: Don't wear basketball shorts and put your phone without a rubber case or similar in it....it will most likely fall out and you won't notice
Click to expand...
Click to collapse
Exactly , ! i wasnt expecting even a single reply anytime soon , and i ended up getting so many replies and all of them extremely helpful ! took me by surprise! I Did pick the right phone! 2 phones of yours got run over by carss?!!?! Reallyy?? 2 ? WOw!
Well i m getting the phone with a body glove , so i guess thatll help!

4-2ndtwin said:
Here is the Stock One Click Master Collection... http://forum.xda-developers.com/showthread.php?p=18370235
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
BWolf56 said:
Bootloader: GB = GB, ICS, JB / Eclair = Eclair, Froyo.
Click to expand...
Click to collapse
x0ne215 said:
This pretty much sums up what I was going to say. I can honestly say I'd never want this phone to go back to stock after trying out the JB ROMs. ], I see no reason to be on 2.2 not-rooted etc.
Click to expand...
Click to collapse
Val D. said:
Not too many phones have same great support like Captivate.
Click to expand...
Click to collapse
Hey guys! :laugh::laugh:
JUst got my Cappy , locked with at%t , anybody can help me unlock?.. i tried galaxysimunlock and it keeps sayin unable to read nv_data , am running cm10.1 4.2.2 ... any help guys???

galaxys3lover said:
Hey guys! :laugh::laugh:
JUst got my Cappy , locked with at%t , anybody can help me unlock?.. i tried galaxysimunlock and it keeps sayin unable to read nv_data , am running cm10.1 4.2.2 ... any help guys???
Click to expand...
Click to collapse
I think you have to be on stock to unlock.

BWolf56 said:
I think you have to be on stock to unlock.
Click to expand...
Click to collapse
Crap! alright , so back to stop using odin one click kk4 package without bootloaders , root it using galaxysimunlock and then flash cm 4.2.2 to get back to where i am ? right?

galaxys3lover said:
Crap! alright , so back to stop using odin one click kk4 package without bootloaders , root it using galaxysimunlock and then flash cm 4.2.2 to get back to where i am ? right?
Click to expand...
Click to collapse
Stock with odin kk4 without bootloaders.
Unlock with galaxysimunlock.
Then there's a guide to follow to get back to cm 4.2.2 in the stickied: http://forum.xda-developers.com/showthread.php?t=1350266
【Guide】How To flash ANY Captivate ROM from Stock (including ICS)
Sent from my SGH-I747 using xda app-developers app

BWolf56 said:
Stock with odin kk4 without bootloaders.
Unlock with galaxysimunlock.
Then there's a guide to follow to get back to cm 4.2.2 in the stickied: http://forum.xda-developers.com/showthread.php?t=1350266
【Guide】How To flash ANY Captivate ROM from Stock (including ICS)
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for being so patient and kind God Bless