Database Develop

[Q] I've rooted my Hero with Universal Androot with Superuser, now what?

I've been looking around different forums but haven't found a dedicated guide for installing a custom rom after using the relatively new Universal Androot the Sprint CDMA Hero.
I'm wanting to install the new CyanogenMod on my Hero since Sprint has made my phone obsolete and hardly usable.
I think the next step is doing a nandroid backup or disabling OTA updates but have been a bit cautious as to I'm new with the Android OS. Can anybody point me to a guide or suggest where I can pick up next? Also can anyone point me to an up-to-date nandroid backup guide?
Thanks.

Make sure you have a custom recovery image flashed on your phone. From there, making nandroid backups and flashing new ROMs is as easy as reading the menu prompts in your recovery image.
You are already rooted so not all these steps will apply to you, but this post here should help get you further along: http://forum.xda-developers.com/showthread.php?t=694572
Also, the "Take Control..." link in my signature will be very helpful for you.

redthehaze said:
I've been looking around different forums but haven't found a dedicated guide for installing a custom rom after using the relatively new Universal Androot the Sprint CDMA Hero.
I'm wanting to install the new CyanogenMod on my Hero since Sprint has made my phone obsolete and hardly usable.
I think the next step is doing a nandroid backup or disabling OTA updates but have been a bit cautious as to I'm new with the Android OS. Can anybody point me to a guide or suggest where I can pick up next? Also can anyone point me to an up-to-date nandroid backup guide?
Thanks.
Click to expand...
Click to collapse
Once you've installed a Custom Recovery Image, just boot to recovery (Hold the home button and press power ... hold home until it vibrates). It will boot to recovery, then you can select "Backup/Restore" and "Backup Nandroid". It will ask you to press Home to confirm, and once you do it will create the backup. Once finished, you can install custom roms.
To do this, download the zip for the rom from the forums for that rom, and save it to the root of your SD card. Boot into recovery, and wipe all traces of the current rom. To do this, select "Wipe", then select ext partition, dalvik-cache, and data (wipe each individually in that order). Then, press back button to return to the main screen. Then choose flash zip, and choose the rom zip you saved. Press home to confirm, and it will install. Reboot, and you have a new rom!

Thanks for the great newbie "how to" below, I just finished rooting, want to go to cm6. I know I can do this, have messed with Windows and Pre, but have one question -
how do I get the zip rom to the card? I have been on Treos too long without using card, can see no way to read, see access, to see what goes on it. With this information, I will try immediately - my goal was tethering, increased speed, and flexibility.

nmoreman said:
how do I get the zip rom to the card? I have been on Treos too long without using card, can see no way to read, see access, to see what goes on it...
Click to expand...
Click to collapse
Plug your USB cable/charger into your phone and PC. After a second or two, you should see a little USB icon show up in your taskbar. Slide your taskbar down and touch that notification -- it will pull up a little menu with 3 or 4 options -- choose Disk Drive mode. That lets you mount the SD card to your PC, just like a flash drive or memory stick would mount. From there you can put files on, remove files, create new folders, etc.
Put the ROM .zip in the root (main) directory of the sd card to be able to flash the ROM from recovery.

Here's another noob question, I just want to make sure since I've only one phone right now and depend on it for work: What exactly is a Custom Recovery Image?

redthehaze said:
Here's another noob question, I just want to make sure since I've only one phone right now and depend on it for work: What exactly is a Custom Recovery Image?
Click to expand...
Click to collapse
The custom recovery allows you to do all sorts of things that you can't do otherwise to your phone,such as installing and using all the cool Custom ROM and update zips,installing different kernals for the processor in your phone to set the CPU to what ever you want it to run, wiping various parts of the device it self or on the sd card with all of the the different types of caches and different partitions after changing to a custom rom and being able to make a different partitions and such that you will need to do this to begin with, being able to back up your data and restoring the phone to it's original state or to a state where it was working with a custom rom before having trouble,like if something you have installed is making it crash or force closed.
In other words it is something you need if you want to do anything with your phone to change it from a paper weight like it is to you in stock form to what they can be once it's unlocked...
Mac

And that's it for todays lesson. Tomorrow we will be discussing "apple" and why they suck so bad.
Sent from my HERO, NOT the HTC E(sucks)VO using XDA App

This is the easyest way to root...
http://forum.xda-developers.com/showthread.php?t=803682

Theres a ROM For The "Hero" That I'm Currently Using, Fresh 2.4!! Works Great, Won't Change Much, But A lot Smoother, With More Features The "Hero" Should of Came With Stock, Try That ROM!!
Sent from my HERO200 using XDA App

cp0020 said:
And that's it for todays lesson. Tomorrow we will be discussing "apple" and why they suck so bad.
Sent from my HERO, NOT the HTC E(sucks)VO using XDA App
Click to expand...
Click to collapse
LMAO LMAO
Root-Hack-Mod-Always™

dude do u have any idea how old this thread is.....
{
"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"
}
epic fail!

[Q] Help Stuck in Clockwork Recover, cannot turn off nc, 1.1.0

i rooted my NC with 1.1.0 and everything was perfect. installed and backup with CWR v 3.0.0.5. I have been stuck in the two screens of cwr. I CANNOT TURN off the nc so 8 aborted on/off s do not work. I cannot restore from sd card since it boots back into cwr, so i have not been able to use any removal code. the Monster pack is not for 1.1. I think I may be bricked. How do I get out of this clockwork recovery program (i have tried all of the options in it too, including fixing permissions, recoveries and endless useless reboots. HELP!

Hold the power button and it will turn off.

i have done that but it turns itself right back on again. it will not stay off. when it does go back on, it goes right back into clockworkmod recover (orange menu screen, landscape only)

Try going here and see if that gets you out of trouble .. Hope it helps

I can't say for a fact that this will make a difference for you, but it certainly can't hurt. Make sure you plug in your Nook Color to the charger, then do the manual power off (as in hold the power button). That should force it to reboot.
Those were the instructions I was given when CWR froze up on me during a kernel flash and it worked. Good luck.

got any mortar-bricked!
got it tuned off. now totally dead.. does not respond to power switch at all now. beware of CWR!!!

Boot CWR off monsterpack SDcard and restore stock system.img/boot.img. This saved me. This is definitely auto-nooter 3.0.0 related because pre-rooted BN 1.1.0 flashable does not have this problem.
ddd22 said:
got it tuned off. now totally dead.. does not respond to power switch at all now. beware of CWR!!!
Click to expand...
Click to collapse

no can do...cannot be turned on. stone dead

It is not. Trust me, I've has this thing twice today. boot partition on emmc is messed up I guess. You CAN boot from CWR on SD card.
ddd22 said:
no can do...cannot be turned on. stone dead
Click to expand...
Click to collapse

With all due respect, I dont understand how that can be. When I press, or press and hold the power key, nothing at all happens. no screen or light activity of any kind... like someone removed a battery.
After your reply, thinking perhaps my removed micro sd card might make a difference, i put it back in and tried again to power on the NC.. nothing happens still. Are you telling me that somehow if i change the content of my SD card to the Monster Pack that somehow that firmware code is going to turn on the Nook even though i cannot power cycle it at all without that magic? I dont understand how this could be and creating that card is a fairly steep search and discovery mission for me which i am willing to do if it has a chance of working.
btw, the battery is fully charged according to the green N on the usb cable.
Thank you so much for your response.

zdrifter said:
Try going here and see if that gets you out of trouble .. Hope it helps
Click to expand...
Click to collapse
What he/she said.. Happened to me once today. Remove the CWR and you should be good to go

how do i do that when no matter what i do the NC will not power on at all...zero. I can no longer even establish a usb connection to the computer.. it detects something and then tries and fails to install required drivers (which were previously installed and previously working). As much as I wish you all are right and I am missing something, I think I may be the first fool to brick the unbrickable!

You will need to make a bootable SD card and boot off that.

i made a bootable cwr sd from the monster rootpack. same nothing happens. will not power on in any way shape or form. will now remake the card with the full rootpack and pray that i can eat my words.

chomp chomp chomp
(the glorious sounds of words being eaten). you both were 100% correct and trust you i should have even more. I followed your advice despite my doubts and I wrote the rootpack image to the sd card and held the power button for about 15 seconds and alive she came! now i am at least back to my cwr that i cant get out of. i now could use a little more of your wisdom as to the best next steps. should i remove cwr then reflash with say 1.1.0R2 or should i figure out how to use cwr to do that flash, and remove it after the flash is completed. obviously a newbee to flashing this device (less than a week old), but have been following Energy on HTC flashes for long times. There is so much information here, it is almost too much when you first step in and your collective willingness to help this doubting thomas is extremely appreciated. my apologies and my deepest thanks. more reading coming up..

resolved!
i added the zip for 1.1.0 -r2 to the monster sd boot card and installed the rom from there. setting it up now. thanks to all for not listening to my doubt and telling me to continue as instructed. forever grateful

ddd-22 - did you install from CWR after rooting 1.1 using the modified Autonooter, or did you sideload the rooted 1.1?
I installed CWR from a 1.1 that was rooted using Autonooter (modified for 1.1) and ended up in a CWR reboot loop similar to what you had.

Yeah- I attempted to run the OC rom after autonootered to 1.1 and got into the loop. Has anyone had succes in loading the OC rom after autonootering to 1.1? Thanks

Thank you for this thread. The exact same thing happened to me after trying to flash a kernel using CWR and autonooter3.0. Thought I was bricked for sure!
I am back to business and glad not to have an expensive paper weight!

though i am on the way to recovery, not fully there yet. the r2 prerooted version was great except i could not log onto gmail... it kept seeing the NC as a phone and was looking for a cellular network, and gave me the message "a reliable connection with google servers could not be made" or some such verbage.. In the pre rooted 1.1. r2, i followed the directions going through youtube etc, but that did not work. so i decided to try to restore the backup i made when i first got caught in the doloop. which i did again, so it is back to monster to start over again and clear out the NC. I have been scouring other sites and many people have been having this problem. I wish i could remember how i installed cwr (method) but cant. however, what i found fairly consistently, and i believe i made the same mistake, was not restarting the NC before i made the backup. seems that is what got a lot of folks into this doloop crisis. if anyone has a plan of how i should get back to my previous state of bliss, let me know. I am remaking monster pack again and clearing out my machine.

[SELFKANG AOSP ROM] CyanogenMod 7.1 Alpha Release [UPDATE 11/16 PM]

** [UPDATE 11/16] = Minor update adding Droid3Bootstrap / RomManager support for installs. You DO NOT need Safestrap to install CM7 now. Any Bootstrap will work.
[UPDATE 11/10] = Better audio (still debugging why volume will occassionally fall back down -- if it does go into settings -> sound -> volume and drag the media slider up -- will reset it), fixed bluetooth -- 2nd ota patch .zip for 5.7.894 OTA users
It's an OMAP4 optimized AOSP build using CyanogenMod sources. I used some of the published Moto Source (9/18) where I felt it was appropriate to get the low level services running. You will not see any Blur files in this build.
Download Link Here
If you're running the 5.7.894 OTA, you will also want to apply a 2nd .zip afterward to update the few stock binaries that are in the build. It's under the .zip download links.
Changelog Here
For the most up-to-date information / builds check my blog: http://hash-of-codes.blogspot.com
What is working in this build:
Phone dial and recieve calls (10/18)
Wifi
SD Cards
Audio is getting better
GPS
3G data
Bluetooth
lots I can't list
Feel free to flash gapps and test away. To download GApps go here and select the top "universal CM7 link for GB"
What isn't working:
Camera app doesn't soft reset the phone anymore, but it isn't working yet either.
Phone app FC's on the boot. Just close the notification and it'll restart 3G immediately.
Audio is very funky atm. It's getting better. If you lose volume, try opening Setting -> Sound -> Volume and drag the "media" slider down and then back up.
GSM Users:
I reviewed some changes submitted by XDA's coreless88 and for the moment I'm just not comfortable putting them in the main build. They would default the phone to GSM/WCDMA. I WILL absolutely get the native support for both GSM and CDMA working as this build matures. It just may take a while. If you really want a GSM variant of this build let me know and I'll reproduce a version with his build.prop changes. For me personally, this can't be a daily driver till the audio issues are fixed.

Great I need calling so won't try it yet, but thanks for all your work

will test it out tonight o hell more like as soon as i get a chance lol

So if 3G works can I still get texts? I don't need to talk to anyone.

yeah texts works, gapps works. just a few funny things. and not like "ha ha" funny either!
still BA!

Once installed, can I do a backup of this and flash back and forth using Safestrap?
Edit: Backup of stock rom gives an error when generating a md5. Is that a problem?

Thanks for all you hard work on this.

im bricked. i flashed back to monster, cleared, and now i cannot boot into bp tools. i start in recovery, hit bp tools, and it goes back to bootlooping. i dont have the sbf as the link is down. can anyone help? AND i only had about 40% battery

MrJudylicious said:
im bricked. i flashed back to monster, cleared, and now i cannot boot into bp tools. i start in recovery, hit bp tools, and it goes back to bootlooping. i dont have the sbf as the link is down. can anyone help? AND i only had about 40% battery
Click to expand...
Click to collapse
Did you miss a step?
I just booted up for the first time about 5 seconds ago. Working great.
Thanks Hashcode!

i get to step 9 and at the end of the back up it says Error generating md5 sum! trying to make a different backup to see if i get same error.

Androidsims said:
Once installed, can I do a backup of this and flash back and forth using Safestrap?
Click to expand...
Click to collapse
Good Question! Short answer: yes.
For now, you have to run a backup (MotoBlur), then format /system, wipe data/cache and install the CM7 zip. When you're done with CM7, you can do another backup (if you want to save CM7) and then restore your original MotoBlur. Make sure to toggle the "Safe System" setting afterward.
As soon as I fix some things in the CM7 build so that the phone is usable, I'm going to work on Safestrap some more.
The next version of Safestrap will automatically store and load your userdata when you toggle the "Safe System" setting. So there won't be a need to perform all of the backup/restores. It will just be the 1 toggle and then reboot.
And sometime in the future, I'm going to put up a MotoBlur "ROM" .zip which runs in 2nd-system. SO stuff like SteelDroid or other ROMs can be safer to install/run. Devs can use that MotoBlur ROM as a template for doing theming, and other things.
It really depends on how well received Safestrap is and if the community wants to see more of it.

Androidsims said:
Did you miss a step?
I just booted up for the first time about 5 seconds ago. Working great.
Thanks Hashcode!
Click to expand...
Click to collapse
no no i booted into CM7 just fine. it was when i booted back into recovery, flashed monster1.2, cleared cache, then reboot lead me to bootloop

MrJudylicious said:
im bricked. i flashed back to monster, cleared, and now i cannot boot into bp tools. i start in recovery, hit bp tools, and it goes back to bootlooping. i dont have the sbf as the link is down. can anyone help? AND i only had about 40% battery
Click to expand...
Click to collapse
I have fastboots for both 5.5.959 and 5.6.890. I can do a mediafire share of whichever you need.

Hashcode said:
I have fastboots for both 5.5.959 and 5.6.890. I can do a mediafire share of whichever you need.
Click to expand...
Click to collapse
i was on 890 so i figured i should flash 890. it would be awesome if you could

MrJudylicious said:
i was on 890 so i figured i should flash 890. it would be awesome if you could
Click to expand...
Click to collapse
I'm going to put the fastboot files on my site for download. It might take a while. Showing 2 hours for the 420M file. I'll update this post with a link in a bit.
Edit:
Unfortunately the nature of flashing ROMs over your live system on a locked bootloader phone means that the hijiack is broken until you can get into the OS and reinstall some sort of Bootstrap. And this was exactly the reason why I developed Safestrap. :/
That being said, you'll likely be able to just flash your /system using the fastboot files and you'll be fine. And don't forget to wipe userdata when swapping ROMs. I've seen countless bootloops from not wipeing userdata. This is ESPECIALLY important for CM7 vs. MotoBlur.

oostah said:
i get to step 9 and at the end of the back up it says Error generating md5 sum! trying to make a different backup to see if i get same error.
Click to expand...
Click to collapse
I got the same error but proceeded anyways.
Man, I forgot how smooth CM is.... Loving the new lockscreen and built in Screenshot features too.

Hashcode said:
As soon as I fix some things in the CM7 build so that the phone is usable, I'm going to work on Safestrap some more.
The next version of Safestrap will automatically store and load your userdata when you toggle the "Safe System" setting. So there won't be a need to perform all of the backup/restores. It will just be the 1 toggle and then reboot.
And sometime in the future, I'm going to put up a MotoBlur "ROM" .zip which runs in 2nd-system. SO stuff like SteelDroid or other ROMs can be safer to install/run. Devs can use that MotoBlur ROM as a template for doing theming, and other things.
It really depends on how well received Safestrap is and if the community wants to see more of it.
Click to expand...
Click to collapse
thanks hashcode, for CM7 work, safestrap, etc...YOU ARE GREATNESS!!!

Hashcode said:
Good Question! Short answer: yes.
For now, you have to run a backup (MotoBlur), then format /system, wipe data/cache and install the CM7 zip. When you're done with CM7, you can do another backup (if you want to save CM7) and then restore your original MotoBlur. Make sure to toggle the "Safe System" setting afterward.
As soon as I fix some things in the CM7 build so that the phone is usable, I'm going to work on Safestrap some more.
The next version of Safestrap will automatically store and load your userdata when you toggle the "Safe System" setting. So there won't be a need to perform all of the backup/restores. It will just be the 1 toggle and then reboot.
And sometime in the future, I'm going to put up a MotoBlur "ROM" .zip which runs in 2nd-system. SO stuff like SteelDroid or other ROMs can be safer to install/run. Devs can use that MotoBlur ROM as a template for doing theming, and other things.
It really depends on how well received Safestrap is and if the community wants to see more of it.
Click to expand...
Click to collapse
So ultimately this will basically dual boot?
{
"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"
}

Androidsims said:
I got the same error but proceeded anyways.
Man, I forgot how smooth CM is.... Loving the new lockscreen and built in Screenshot features too.
Click to expand...
Click to collapse
OH, I totally forgot that the phone FCs on boot. It reloads 3G data shortly afterward. I have a fix coming for that as well.
You could say.. the OS boots too fast for it.
THe normal boot process for MotoBlur involves the phone coming up as GSM initially, doing a few checks for network, failing and then dropping into a Janky CDMA version of GSM.
CM7 currently boots straight to CDMA.

Hashcode said:
I'm going to put the fastboot files on my site for download. It might take a while. Showing 2 hours for the 420M file. I'll update this post with a link in a bit.
Edit:
Unfortunately the nature of flashing ROMs over your live system on a locked bootloader phone means that the hijiack is broken until you can get into the OS and reinstall some sort of Bootstrap. And this was exactly the reason why I developed Safestrap. :/
That being said, you'll likely be able to just flash your /system using the fastboot files and you'll be fine. And don't forget to wipe userdata when swapping ROMs. I've seen countless bootloops from not wipeing userdata. This is ESPECIALLY important for CM7 vs. MotoBlur.
Click to expand...
Click to collapse
I appreciate it. I have teh file blur_version.5.5.959.xt862.verizon.en.us.zip Is that the fastboot?
nevermind. i found it here http://rootzwiki.com/showthread.php?5103-SBF-Droid-3-Fastboot-files-(5.5.959-and-5.6.890)
i really appreciate you doing that for me though. i just shat a brick (no pun intended)

[Q] Flashing Stock Rom

I'm currently running CM9 on my tab 8.9, and while I'm generally happy with it, now Samsung have (finally!) released stock ICS for the 8.9, I'm tempted to just install this and be done with it (I'd also likely get a working camera!)
As I can't flash using Kies, I'm going to use Odin. I've downloaded the stock rom from SamFirmware, but just want to check on the process for flashing a stock rom using Odin.
I assume I just click PDA, select the .md5 file, and make sure 'Auto Reboot' is checked, but do I need to do anything else in Odin to make sure this works ok?

{
"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"
}
Jusy like this picture and click start....

Finally got round to trying this (! Better late than never).
Using Odin 1.85, the download seemed to work ok, and completed with no errors. The tab then rebooted, and after some screen flashing, the Samsung boot screen appeared, then the logo (which started pulsing). I then left it, and left it, and left it, but I just get the logo flashing on the screen, and it doesn't get any further.
I reset the tab, went back into Download mode, then tried again. Odin completed the download (again), the tab rebooted, but the same thing happened.
Am I meant to clear the cache using this method? I did have CMR 5.5.0.4/CM9 installed before trying this, but I thought this ROM overwrites everything and reverts it back to stock.

tman24 said:
Finally got round to trying this (! Better late than never).
Using Odin 1.85, the download seemed to work ok, and completed with no errors. The tab then rebooted, and after some screen flashing, the Samsung boot screen appeared, then the logo (which started pulsing). I then left it, and left it, and left it, but I just get the logo flashing on the screen, and it doesn't get any further.
I reset the tab, went back into Download mode, then tried again. Odin completed the download (again), the tab rebooted, but the same thing happened.
Am I meant to clear the cache using this method? I did have CMR 5.5.0.4/CM9 installed before trying this, but I thought this ROM overwrites everything and reverts it back to stock.
Click to expand...
Click to collapse
I had the same problem, I cleared CACHE and it worked...

kosmepe said:
I had the same problem, I cleared CACHE and it worked...
Click to expand...
Click to collapse
Ok, thanks. Took your advise, and cleared the cache (had to re-install CWMR first though). I then used Odin to re-install the latest ICS from Samsung, which installed ok this time.
One problem though, when you put the tab to sleep, then resume (using the power button), the screen just goes totally corrupt and unreadable. You can see something is happening on the screen to key presses, but you have to power off using the button. From a cold boot, everything is fine. It's just when you sleep/resume by the looks of it!

tman24 said:
Ok, thanks. Took your advise, and cleared the cache (had to re-install CWMR first though). I then used Odin to re-install the latest ICS from Samsung, which installed ok this time.
One problem though, when you put the tab to sleep, then resume (using the power button), the screen just goes totally corrupt and unreadable. You can see something is happening on the screen to key presses, but you have to power off using the button. From a cold boot, everything is fine. It's just when you sleep/resume by the looks of it!
Click to expand...
Click to collapse
This is a problem others have experienced. Look at the stickies in this section, All 8.9 questions, last few posts.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jd1639 said:
This is a problem others have experienced. Look at the stickies in this section, All 8.9 questions, last few posts.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Mmmm. Being in the UK, I first reset everything, then installed XXKJ4 (3.2). This went fine, and a quick test with the suspend/resume showed no screen corruption. I then did the reset/cache wipe, and installed EULPO (4.04). This went fine, but a quick suspend/resume test showed the same corruption. As EULA3 is for the US only, I think I did the right thing.
I'm inclined to try re-flashing XXKJ4, and see if Kies updates it ok.

tman24 said:
Mmmm. Being in the UK, I first reset everything, then installed XXKJ4 (3.2). This went fine, and a quick test with the suspend/resume showed no screen corruption. I then did the reset/cache wipe, and installed EULPO (4.04). This went fine, but a quick suspend/resume test showed the same corruption. As EULA3 is for the US only, I think I did the right thing.
I'm inclined to try re-flashing XXKJ4, and see if Kies updates it ok.
Click to expand...
Click to collapse
Ok, getting a bit frustrated now. From a stock 3.2 build (with no screen corruption problems), I just did an ICS update from Kies, which worked ok, but STILL had the corruption issue when resuming from sleep!

tman24 said:
Ok, getting a bit frustrated now. From a stock 3.2 build (with no screen corruption problems), I just did an ICS update from Kies, which worked ok, but STILL had the corruption issue when resuming from sleep!
Click to expand...
Click to collapse
Google "tab 8.9 p7300 terribly messed up xda" there's a fix for the boot loader.
Sent from the short bus

...
---------- Post added at 12:35 PM ---------- Previous post was at 12:27 PM ----------
try to flash the ICS bootloader first

jd1639 said:
Google "tab 8.9 p7300 terribly messed up xda" there's a fix for the boot loader.
Sent from the short bus
Click to expand...
Click to collapse
Still working on this if you can believe it!
According to the thread, people who've experienced this say that flashing the stock 3.2 ROM (EULA3), followed by ICS fixes the problem. As I said though, this is a UK model P7310, so I tried flashing the UK 3.2 ROM (XXKJ4) followed by UK ICS (EULPO). I think EULA3 is the US 3.2 ROM, so will there be a problem flashing a UK 7310 with this ROM, and afterwards will I have to flash the US ICS ROM, or can I still use the UK ROM.
The solution sounded simple, but I'm guessing these are all US based forums.

carmobileproject said:
...
---------- Post added at 12:35 PM ---------- Previous post was at 12:27 PM ----------
try to flash the ICS bootloader first
Click to expand...
Click to collapse
Thanks. Where do I get this?
R u saying that I should install HC 3.2, then the ICS Bootloader, then ICS full? Odin's got the option to install a bootloader, but I wouldn't know which one to use or where to get it, unless you mean CWM, but this doesn't have a bootloader file in the archive.
Getting desperate!

I think you have to extract the bootloader.bin out of the correct hc stock Rom. If I remember the Rom was for the Hong Kong rom
I don't know if this will work or will brick your device but out of curiosity I downloaded the P7300 HC rom and extracted the bootloader.cin. You can find it at http:\\d-h.st/8tF
Sent from the short bus

tman24 said:
...One problem though, when you put the tab to sleep, then resume (using the power button), the screen just goes totally corrupt and unreadable. You can see something is happening on the screen to key presses, but you have to power off using the button. From a cold boot, everything is fine. It's just when you sleep/resume by the looks of it!
Click to expand...
Click to collapse
I'm having the same issue. I'm in New Zealand, my guess is that the NZ firmware is based on the UK one.
1) Flashed firmware using odin
2) Wouldn't boot, got stuck at 'Samsung' load screen (the one that kind of pulses)
2) Installed Clock Work Mod recovery mode using odin
3) Booted to recovery mode
4) Reset to factory defaults
When coming out of power save mode the screen is garbled. I've read an earlier post about clearing the cache, do you mean the option in CWM called "wipe cache partition'?
Thanks in advance.

There have been others with the garbled screen issue. Search kalt kaffe and bootloader.
Sent from the long bus, I got mainstreamed

jd1639 said:
There have been others with the garbled screen issue. Search kalt kaffe and bootloader.
Sent from the long bus, I got mainstreamed
Click to expand...
Click to collapse
It must be a bootloader problem. I've tried every combination now, even now I'm running CWM 6.0.0.8 and AOSP 4.1.2, and while everything installs and runs ok, I STILL get the garbled screen after resuming from sleep. Just trying to search the CM10 thread for bootloader, but search is currently down.
I'm just concerned that flashing the bootloader stands a real chance of bricking the tab, but I'm hoping if the loader works on CM10 it will work on AOSP.

I found a mention to it on page 109 of the thread: http://forum.xda-developers.com/showthread.php?t=1777398&page=109
I just found it in the FAQ here: http://forum.xda-developers.com/showthread.php?p=31771837#post31771837
Which links to this page: http://forum.xda-developers.com/showthread.php?t=1867124
"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)"
Let me know how it goes, I'm out of time right now.

Wild_Qwerty said:
I found a mention to it on page 109 of the thread: http://forum.xda-developers.com/showthread.php?t=1777398&page=109
I just found it in the FAQ here: http://forum.xda-developers.com/showthread.php?p=31771837#post31771837
Which links to this page: http://forum.xda-developers.com/showthread.php?t=1867124
"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)"
Let me know how it goes, I'm out of time right now.
Click to expand...
Click to collapse
Jeez, I love this forum. There are some great people here. Thanks to suggestions, I finally have a fully working tab 8.9, that you can put to sleep and wake up without any garbled screen. This is a UK spec 8.9, so I've been very careful on what I flashed
Stock HC always worked fine, but compared to ICS/JB, it's horrible. I got fed up with waiting for Samsung to release ICS for the tab, so tried flashing CM10, but had big problems. Eventually I got CM9 working ok (using CMR5), but this had bugs, and wasn't reliable. Then ICS was released properly, but after flashing this using Odin, I got the garbled screen problem. I went back to stock HC, and this worked fine. Tried re-flashing ICS using Kies AND Odin, but garbled screen. Tried ASOP JB, but still garbled screen!!!!!
Eventually, having nothing to lose, I flashed UELA3 as suggested, but on reboot this went into a boot loop at the Samsung loading screen. Tried re-flashing 3 times (with clear/wipe cache), but no change, BUT, EULA3 does install a new bootloader (I could see this during the Odin flash). So, I then re-flashed stock ICS, and bam, it works.
So, you were right, EULA3, despite the fact it doesn't fully load, was enough to install the correct bootloader, then flashing XEULPO ICS on top fixed the problem. ICS may not be quite as slick as JB, but it's not far behind. Guess we'll never see a Samsung JB for this tab, even though it's easily capable of running it, but for now, I'm ok with this.

Thanks for reporting back. It'll help the next person.
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round

Revert to stock from CM11 keeping the same partition table

Hi there,
so, I've successfully installed CM11 and played with it a little, but I would like to go back to stock 4.3 now. The main reasons are that Podcast addict seems to have issues and the camera crashes on launch. To be fair, I don't mind the stock version at all. The only thing I love about CM11 is the partition table, which gave me much more storage space for apps.
The question is, is there a way to flash the stock ftf without reverting to the old 2 GB of storage space? I know that I can repartition everything after flashing (I have already done so once), but I'd like to skip this step if possible.
Any suggestions?
Cheers!
P.S. If you have good arguments on keeping CM or going to CM12, I am all ears.

prodeguerriero said:
Hi there,
so, I've successfully installed CM11 and played with it a little, but I would like to go back to stock 4.3 now. The main reasons are that Podcast addict seems to have issues and the camera crashes on launch. To be fair, I don't mind the stock version at all. The only thing I love about CM11 is the partition table, which gave me much more storage space for apps.
The question is, is there a way to flash the stock ftf without reverting to the old 2 GB of storage space? I know that I can repartition everything after flashing (I have already done so once), but I'd like to skip this step if possible.
Any suggestions?
Cheers!
P.S. If you have good arguments on keeping CM or going to CM12, I am all ears.
Click to expand...
Click to collapse
Give my CM12.1 a shot and I'm 99% sure you won't regret it.
You might even upgrade without wiping data. Just backup first

WhiteNeo said:
Give my CM12.1 a shot and I'm 99% sure you won't regret it.
You might even upgrade without wiping data. Just backup first
Click to expand...
Click to collapse
Sounds like a plan. I think the issues I'm having are due to the fact that the apps can't write to the SD card. What do you think?

prodeguerriero said:
Sounds like a plan. I think the issues I'm having are due to the fact that the apps can't write to the SD card. What do you think?
Click to expand...
Click to collapse
My ROM fixes the storage permissions during installation, so this problem will be gone for sure. :good:

Installing it right now! [emoji41]
Sent from my iPhone using Tapatalk

prodeguerriero said:
Installing it right now! [emoji41]
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Alright, let me know how it worked out ?

WhiteNeo said:
Alright, let me know how it worked out [emoji16]
Click to expand...
Click to collapse
Ok, I'm playing with it now, it seems pretty smooth. Podcast addict seems to have the same issue though. The camera also tells me to "Insert an SD card". Maybe I should format it?
On a side note, when in the Storage settings I see only two partition: internal storage (which I'm guessing is sdcard0) and the actual SD card, which is clearly mounted but doesn't seem to be accessed correctly: the graph bar stays grey and it doesn't identify the card content. I'll try to post some pics.
Any suggestions?
{
"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"
}
Sent from my iPhone using Tapatalk

I booted to recovery and am installing everything from scratch. I noticed that the Internal storage was in exfat2 and converted it to exfat4. Let's see what happens.
On a side note: when I try to reboot from recovery, everything hangs and I have to force shutdown with power+volUp.
Sent from my Nexus 7 using Tapatalk

prodeguerriero said:
I booted to recovery and am installing everything from scratch. I noticed that the Internal storage was in exfat2 and converted it to exfat4. Let's see what happens.
On a side note: when I try to reboot from recovery, everything hangs and I have to force shutdown with power+volUp.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Internal storage should always be EXT4 file system with an uid of 1023:1023

WhiteNeo said:
Internal storage should always be EXT4 file system with an uid of 1023:1023
Click to expand...
Click to collapse
That did the trick. Now I have two internal storages plus the external SD card (which is still grey btw) and the camera seems happy now. I'll keep playing with it and keep you posted, but this looks great! One note though, when the phone asks if I want to recover settings from old Android devices during the setup process, I am given the option to not import some app, by opening the list and un-ticking them. In this page, the DONE and CANCEL button don't seem to work. I can only go back with the system back/triangle button, undoing my custom selection.
One extra question: I have a problem with the mic, which was the cause of my first flash to begin with. Do you know if there is some kind of hidden engineering setup where I can increase the mic gain?
Cheers

prodeguerriero said:
That did the trick. Now I have two internal storages plus the external SD card (which is still grey btw) and the camera seems happy now. I'll keep playing with it and keep you posted, but this looks great! One note though, when the phone asks if I want to recover settings from old Android devices during the setup process, I am given the option to not import some app, by opening the list and un-ticking them. In this page, the DONE and CANCEL button don't seem to work. I can only go back with the system back/triangle button, undoing my custom selection.
One extra question: I have a problem with the mic, which was the cause of my first flash to begin with. Do you know if there is some kind of hidden engineering setup where I can increase the mic gain?
Cheers
Click to expand...
Click to collapse
I guess that's some kind of native CM12.1 issue that still has to be fixed.
My ROM has built-in FauxSound support. With this awesome app (or any other app that supports its kernel sound parameters) you can tweak all audio related stuff to your liking :good:

WhiteNeo said:
I guess that's some kind of native CM12.1 issue that still has to be fixed.
My ROM has built-in FauxSound support. With this awesome app (or any other app that supports its kernel sound parameters) you can tweak all audio related stuff to your liking :good:
Click to expand...
Click to collapse
A little update: the ROM seems to work fine, but my phone has become now useless. Let me explain. My microphone started acting up a month ago, and people wouldn't hear me anymore. I had to either use headphones or put it in loudspeaker to work. Having two phones, I took them apart and narrowed down the problema to the logic board. Sony tells me I need to replace the logic board for a whopping 200$. So I thought "you know what, I'll just use the headphones". Now that it is not under warranty, I can even root it and play with it! So as soon as I got the phone back, I rooted and flashed.
For some reason, I now have the mic not working in any conditions. Not even with the headphones. I am going to flash back to stock to see if that changes anything. Do you have any insights on what might the issue be?
Cheers and thanks!

prodeguerriero said:
For some reason, I now have the mic not working in any conditions. Not even with the headphones. I am going to flash back to stock to see if that changes anything. Do you have any insights on what might the issue be?
Cheers and thanks!
Click to expand...
Click to collapse
I am not too familiar with the audio and microphone related changes between CM11 and 12, so I can't tell if it might be rom related.
Did the stock rom help?

It seems better now. I'm going to flash your rom again and see what happens. About this, here's how I did it last time:
- root access
- install a custom recovery (see here)
- use the recovery to wipe and install your rom.
Here is my question: before going back to stock to check the mic, I did a backup of your ROM on micro SD using the recovery that came with it. Can I recover that backup instead of a clean flash? Can I use the custom recovery I linked above or should I use the one that came with your Rom?
Thanks!

prodeguerriero said:
It seems better now. I'm going to flash your rom again and see what happens. About this, here's how I did it last time:
- root access
- install a custom recovery (see here)
- use the recovery to wipe and install your rom.
Here is my question: before going back to stock to check the mic, I did a backup of your ROM on micro SD using the recovery that came with it. Can I recover that backup instead of a clean flash? Can I use the custom recovery I linked above or should I use the one that came with your Rom?
Thanks!
Click to expand...
Click to collapse
Sure, restoring the backup will work fine
If you face the microphone issue again after restoring the backup, you can try a clean flash.
EDIT: I recommend the included recovery for restoring. :good:

WhiteNeo said:
Sure, restoring the backup will work fine
If you face the microphone issue again after restoring the backup, you can try a clean flash.
EDIT: I recommend the included recovery for restoring. :good:
Click to expand...
Click to collapse
Damn, the headphones' mic is still not working after a clean install. It's too bad, because it is the only way I can communicate given that my Xperia mic is acting up. I really love your ROM though. Have you tested your headphones with it?
By the way, thanks for the help

prodeguerriero said:
Damn, the headphones' mic is still not working after a clean install. It's too bad, because it is the only way I can communicate given that my Xperia mic is acting up. I really love your ROM though. Have you tested your headphones with it?
By the way, thanks for the help
Click to expand...
Click to collapse
It's been more than 9 months since the release of my ROM, and I haven't received any reports about issues with microphones. However, haven't tested it myself.
You might also try my NeoWave ROM, maybe the mic works fine there as its KK based

WhiteNeo said:
It's been more than 9 months since the release of my ROM, and I haven't received any reports about issues with microphones. However, haven't tested it myself.
You might also try my NeoWave ROM, maybe the mic works fine there as its KK based
Click to expand...
Click to collapse
The mic problem is not the ROM's fault, it started when I was OEM still. About the headphones, I don't know. I tried to install CM11 again, but still no luck. Might it be a kernel based issue? I'm going to keep on trying and see what I come up with. Cheers!