Database Develop

[Q] Official Froyo XXJPO Root

Hi all,
Sorry to ask this but with all the various firmware versions I am confused about which is a good Rooting program for the Official JPO Froyo release. Can someone point me in the right direction?
Thank you in advance

search is your friend.
Sent from my GT-I9000 using XDA App

CF root using Odin
Sent from my GT-I9000 using XDA App

Actually I have the same question as was confused about which method to use as well. My phone is JPO/JPP/JP3. I have searched but all the root methods I found were for earlier versions of froyo and users reported problems.

kiwijunglist said:
Actually I have the same question as was confused about which method to use as well. My phone is JPO/JPP/JP3. I have searched but all the root methods I found were for earlier versions of froyo and users reported problems.
Click to expand...
Click to collapse
Thank you glad to hear I am not alone
andrej.marinic:
Search is what started the confusion its hard to read all the threads to find out the end result.
I would also like to know if there is one that you can apply via the recovery method (like copying update.zip to sdcard) so I do not have to use a program like ODIN.
Thank you again in advance,

I did it using the CF method: http://forum.xda-developers.com/showthread.php?t=788108
its very easy and pain free

padlad said:
I did it using the CF method: http://forum.xda-developers.com/showthread.php?t=788108
its very easy and pain free
Click to expand...
Click to collapse
I also saw this but some people have had issues so I am bit reluctant to try it

cf-root works like a charm on JPA. no issues for me.
Sent from my GT-I9000 using XDA App

Cf root but make sure your 3 button download mode works as a failsafe
Sent from my GT-I9000 using XDA App

cenonmin said:
I also saw this but some people have had issues so I am bit reluctant to try it
Click to expand...
Click to collapse
Just make sure you use CF-Root-XX_XEU_JPO-v1.2-Busybox-1.17.1.zip

I have the official Germany Froyo. I will wait for the 3 Button fix and OCLF fix for the official Froyo.
I did tested other things and it made my phone slower and quickly out of memory. So I reset ( all data gone - but I did Backup my apps ) everything and it went normal
Just better wait until they find a solution for the official Froyo and not the unofficial Froyo.

I am using CF-Root-XX_XEU_JPO-v1.2-Busybox-1.17.1.zip flashed via Odin. Took 30 seconds and now I can use stuff like Titanium Backup and other useful apps. All on the official JPO through Kies.

silverstorm said:
I am using CF-Root-XX_XEU_JPO-v1.2-Busybox-1.17.1.zip flashed via Odin. Took 30 seconds and now I can use stuff like Titanium Backup and other useful apps. All on the official JPO through Kies.
Click to expand...
Click to collapse
Did you have any issues with 'un-rooting'??
EDITED:
What I am saying here is Kies totally bricked my phone and as such I won't use it again but instead Odin.
You however mention you are still using Kies. Did you have any issues in un-rooting when using Kies for the next flash... or have you not tried this yet?

Beards said:
Did you have any issues with 'un-rooting'??
Click to expand...
Click to collapse
Erm, not had a reason to un-root yet so haven't tried. But since this is flashed as a Kernel I presume I would have to flash another non-rooted Kernel through Odin in order to un-root. but don't know why I'd want to. If I wanted to upgrade to a newer version of Froyo, the root shouldn't affect it as far as I'm aware, it's only LagFixes really that are required to be disabled.
But to be on the safe side, you could re-flash a stock non-rooted JPO firmware from samfirmware.com through ODIN prior to going ahead with a Kies update, but this will mean you'll lose your data. I always go through this route anyway and then use Titanium backup to restore. (for which you'll require root!)

silverstorm said:
Erm, not had a reason to un-root yet so haven't tried. But since this is flashed as a Kernel I presume I would have to flash another non-rooted Kernel through Odin in order to un-root, but don't know why I'd want to. If I wanted to upgrade to a newer version of Froyo, the root shouldn't affect it as far as I'm aware, it's only LagFixes really that are required to be disabled.
Click to expand...
Click to collapse
Really... I could have sworn you have to take off any root prior to the next flash.

Beards said:
Really... I could have sworn you have to take off any root prior to the next flash.
Click to expand...
Click to collapse
Just lag fixes need to be disabled in order to flash via kies, the last couple of flashes i did had root already on, flashed no problem.

padlad said:
Just lag fixes need to be disabled in order to flash via kies, the last couple of flashes i did had root already on, flashed no problem.
Click to expand...
Click to collapse
Well what do you know...... Something new learned today.
Thanks Guys.
{
"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"
}

To root froyo use simpleoneclick.
Sent from my GT-I9000 using XDA App

tt4079 said:
To root froyo use simpleoneclick.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Links please.

http://forum.xda-developers.com/showthread.php?t=833953
Breaking News: New One Click Root app from RyanZA, the maker of the famous OCLF.

[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?

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] [PROBLEM] Can't get 4G to work again...

Hi guys!
So I have a problem...
It all started a couple of weeks back, when I got my new phone. I booted it up, had 4G connection, rooted it, put in ARHD and still had 4G. I then updated to a new radio found on the forum, 1.29.401.12.
When I did that, I lost my 4G... I then asked around to find a stock telenor norway radio, and "phewBAR" uploaded one to me, in the form of a .img file. ( LINK TO FILE: https://docs.google.com/file/d/0B4j0jjrgwiFwY2VzdDREZ2ZhV0E/edit
I didn't know how to install it, so I asked for that aswell, and "MacHackz" made the .zip flashable file that I've linked here -> https://www.dropbox.com/s/oz8b0mdjlmxotg7/RadioStock-signed.zip
I did the flash, and still no 4G
does anybody know how the hell I get my 4G back? Very annoying without it...
I don't know that much about radio-flashing, so probably shouldn't have done it in the first place...
If anybody needs any screenshots of anything, please let me know! I also went into the menu at *#*#4636#*#* -> phone information -> and set the settings to GSM/WCDMA/LTE Auto.
In norway we use both the 1800MHz and the 2600MHz frequencies.
does anybody know how to help me ?
Thanks in advance people
Here are my screenshots (PS. I always set it to GSM/WCDMA/LTE Auto, but it goes back to only WCDMA as you can see in the 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"
}

I came to think of a thing ... I think it first occurred when I updated to a 4.2.2 radio? Maybe phewBAR sent me his 4.2.2 radio backup?
Sent from my HTC One using xda premium

Bump
Anybody?

what's your radio sw version?
settings / about / software information / more / baseband version.
Sent from a pizza..

millicent said:
what's your radio sw version?
settings / about / software information / more / baseband version.
Sent from a pizza..
Click to expand...
Click to collapse
4A.16.3250.24_10.38.1150.03L
Sent from my HTC One using xda premium

you seem to have the most up-to-date radio out there.
I have switched a couple radios myself, can't say any is perfect, I find my phone to revert quite often to hsdpa or even 3g, on the other hand in better coverage areas such at my work place downtown it stays on solid lte..
Did you try to flash the other 2 radio versions?
in any case, provided neither radio works, I suggest you go back to stock and let your carrier or HTC to deal with this under the warranty.
good luck!
Sent from a pizza..

thanks so far - but one more question though ;
Are there only 3 different radio-types for the international version? Would you mind linking me? If I flash those three and none of them work, then I'll know it's my phone and not software

afaik, the sw versions of the radios are shared on all hw versions (well all except the one cdma radio I think) which is quite fine for us. this said, it might be less useful to try older versions (seeing you're already on latest), however you can give it a try.
there's a thread on this in the general one section, you might wanna try to use the search tool under a desktop browser, otherwise I can leave you a Dropbox link. the latter might take a while as I don't have access to my machine right now,..
so lemme know how you manage to get this to work
Sent from a pizza..
---------- Post added at 08:40 AM ---------- Previous post was at 08:33 AM ----------
I got to find it quite easily by using the query 'HTC one radio' search in title only, the only result..
http://forum.xda-developers.com/showthread.php?p=42612909
Sent from a pizza..

millicent said:
afaik, the sw versions of the radios are shared on all hw versions (well all except the one cdma radio I think) which is quite fine for us. this said, it might be less useful to try older versions (seeing you're already on latest), however you can give it a try.
there's a thread on this in the general one section, you might wanna try to use the search tool under a desktop browser, otherwise I can leave you a Dropbox link. the latter might take a while as I don't have access to my machine right now,..
so lemme know how you manage to get this to work
Sent from a pizza..
---------- Post added at 08:40 AM ---------- Previous post was at 08:33 AM ----------
I got to find it quite easily by using the query 'HTC one radio' search in title only, the only result..
http://forum.xda-developers.com/showthread.php?p=42612909
Sent from a pizza..
Click to expand...
Click to collapse
Yeah, well now I've tried all radios available and compatible, but nothing seems to help... is there anything I can do in build.prop? I saw that someone added/changed some lines for the Nexus4, to enable 4G. I tired adding those lines, but it didn't help; probably need something more spesific for the One?
I've also tried flashing TrickDroid GE, but that didn't help either... I feel hopeless :'(

ipwngeek said:
Yeah, well now I've tried all radios available and compatible, but nothing seems to help... is there anything I can do in build.prop? I saw that someone added/changed some lines for the Nexus4, to enable 4G. I tired adding those lines, but it didn't help; probably need something more spesific for the One?
I've also tried flashing TrickDroid GE, but that didn't help either... I feel hopeless :'(
Click to expand...
Click to collapse
Not sure if this works on international phones, but try dialing *#*#INFO#*#* on your phone keypad. Select Phone Information, then "set preferred network type:" see what it says.

It does work, however it doesn't solve my problem
Sent from my HTC One using xda premium

Maybe I can help, what is your cid and baseband version? Should start with 1.29 or 1. Something
Sent from my HTC One using xda app-developers app

Where do I check that? Do you mean the baseband version in 'about'? If it's that, then it's: 4A.17.3250.14_10.39.1150.04L
If I found the right number, then this is my cid: 2.19.401.1!
Can you help?
Sent from my HTC One using xda premium

Bump? Is there honestly nobody out there that can help? PLEASE?

ipwngeek said:
Bump? Is there honestly nobody out there that can help? PLEASE?
Click to expand...
Click to collapse
You could try flashing the latest version of ARHD (12.0) and see if that solves your problem

No help... Stock ROM is the only thing that gives me 4G. only if I go all the way back to stock, no mods, super kernels, ROM or newer radio... WHY THE FRACK?!

ipwngeek said:
No help... Stock ROM is the only thing that gives me 4G. only if I go all the way back to stock, no mods, super kernels, ROM or newer radio... WHY THE FRACK?!
Click to expand...
Click to collapse
did you try to change your cid to super cid and run stock RUU, I use this method to fixed no 4G signal problem

1. I have no idea how, but I'll search for it around the forum later today!
2. I really want to keep trickdroid and my mods... I can't do that with a stock RUU can I?

ipwngeek said:
1. I have no idea how, but I'll search for it around the forum later today!
2. I really want to keep trickdroid and my mods... I can't do that with a stock RUU can I?
Click to expand...
Click to collapse
Hi ipwngeek,
I've got the same problem as yours. my HTC one Hong Kong ver never switch back to 4g lte network , as HK LTE same as Norway, maybe my solution could help. it's work for me and it's simple.
1. back to stock rom
2. use fastboot flash in the stock recovey.img
3. factory reset in Hboot
4. reboot and see if your phone can get into 4g network now.
5. finish , you can flash your trickdroid back.
good luck

I have no idea how to do that. A guide would be nice, as I don't have access to a a computer for the next 11 days
Sent from my HTC One using xda premium