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
Related
** [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)
Hi,
I am from india was updating after i got a push message today, phone is already running the Latest ICS ROM. today it downloaded a 7mb update after which phone restarted for installing the update, the update was installed after which phone restarted again since then phone has the word "SAMSUNG" flashing.. I tried to wait for more than half an hour. But it is at the same point...
I tried to go to the hardreset menu "volup+menu+power" it does not go into that menu too. An android symbol comes later it goes away n finally it comes to the same point of flashing "SAMSUNG"
Please help, lots of data on phone memory
Did you try volume up or volume down + power + home?
Have you tried to get into recovery and just wipe cache and dalvik (not factory reset/data)?
If it doesn't work, you will have to try to Odin (if you can get in download mode). If that doesn't work and you don't have a triangle, take it to Samsung and tell them their OTA update messed it up (which sounds like it did).
You need to enter the recovery ( Volume UP + Home + Power ) and clear cache. Do not select "Wipe Data/Factory Reset" as it may brick your phone. It it doesn't come up, try taking out the battery for a few seconds, and then try again - i see no reason why it wouldn't work.
If it won't work, try entering download mode ( Volume DOWN + Home + Power ) and flash a stock GB ROM via Odin - you can find all stock ROMs in dr. Ketan's guide in Development forum for Galaxy Note. After that you can clear cache and boot. Once back on GB you should do a factory reset, but since you probably need the data on your phone, clearing cache should be enough to boot.
Ah glad that i have company.sad at the same time!! Even i have the same problem after the 7mb OTA update. The andriod process closes often and hangs the phone.
The phone was literally unusable. Hence i tried to install custom gingerbread rom on it. Now its almost completely bricked.
How irresponsible is samsung to roll these things out without testing it thoroughly.
***PLEASE DON'T INSTALL THE 7MB ICS OTA UPDATE***
hopefully we can save some.
I am not sure what to do now. Any idea ?
//Ramith
ramith123 said:
Ah glad that i have company.sad at the same time!! Even i have the same problem after the 7mb OTA update. The andriod process closes often and hangs the phone.
The phone was literally unusable. Hence i tried to install custom gingerbread rom on it. Now its almost completely bricked.
How irresponsible is samsung to roll these things out without testing it thoroughly.
***PLEASE DON'T INSTALL THE 7MB ICS OTA UPDATE***
hopefully we can save some.
I am not sure what to do now. Any idea ?
//Ramith
Click to expand...
Click to collapse
Go to DOWNLOAD MODE try to install official rom through pc odin, this will not produced a yellow triangle. If it still doesnt work then claim your WARRANTY.
"Honey, I screwed my Note"
Till yesterday I had my Galaxy Note on Android ICS official release. It was rooted too and everything was super smooth. Then I got an OTA update available message and I was hesitant at first whether it will remove my root. It didn't look like much of an update since only the kernel version was changed from LP8 to LPA. But after much consideration I went ahead with the update. It looked fine. After the update finished, the phone restarted and updated all apps. I was happy root did not go off too. Then I ran Titanium backup and took a backup of all my apps. Everything was good. But I left my phone at night and morning it was turned off. The battery had drained completely. I recharged it, but now it didn't start at all. I tried removing the external SD card thinking that some problem might have occurred with all the news about ICS and eMMC problem on Note. But nothing worked. The phone would start and Samsung logo would come but it gets stuck there for more than an hour. I read on XDA that I should try flashing to stock GB and I downloaded it and tried flashing with Odin. But it failed too. I removed the USB connection from the PC and now the phone wouldn't even boot, and I mean it's completely off. I tried holding the power button, power+volume_up+home, and power+volume_down+home. I kept holding for two minutes and still nothing. And now when I connect it to charger using the wall outlet charger, it does not charge. And if I connect to USB also, nothing happens. Tried running Odin but it doesn't detect anything.
And to add to my woes, I am currently onsite at USA and since I have the International N7000 model that I had brought from India, they wouldn't service it. I guess I am royally "bricked". :crying:
What I am still wondering is if it's really possible to mess up the phone so bad it wouldn't even show a single sign of life!
I have the same issue .. anyone around the whole of xda know what to do ? I updated to ics then rooted it for the first time. Did not installs any roms nothing. Just rooted to access titanium backup.
Recently I updated the same as it showed up and after that I cannot access my contacts or phone or call list .
Other than that everything works fine, luckily for me it's not bricked.
I tried killing the process still didn't make a difference.
I can call ppl by searching through gesture search though but doesn't give an option to msg.
What should I try ? I don't want it to turn into a brick though, any proper answers would be really appreciated.
IM posting the various screenshots I took after this whole problem started. Hope someone can help......
{
"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 GT-N7000
What I am still wondering is if it's really possible to mess up the phone so bad it wouldn't even show a single sign of life!
Yes it is possible. Sorry man.:crying:
Possible how ? IM ready to buy any fix app. I even tried fix permissions but it doesn't show contacts or phone in the list.. I'd there a way to like restore to an earlier point or earlier update ?
If it is possible what do I do ?
Now IM thinking twice to unroot it and give it to Samsung store.. I Donno if it will unroot and if I can get it replaced..
Sent from my GT-N7000
motionexecuter said:
I have the same issue .. anyone around the whole of xda know what to do ? I updated to ics then rooted it for the first time. Did not installs any roms nothing. Just rooted to access titanium backup.
Recently I updated the same as it showed up and after that I cannot access my contacts or phone or call list .
Other than that everything works fine, luckily for me it's not bricked.
I tried killing the process still didn't make a difference.
I can call ppl by searching through gesture search though but doesn't give an option to msg.
What should I try ? I don't want it to turn into a brick though, any proper answers would be really appreciated.
IM posting the various screenshots I took after this whole problem started. Hope someone can help......
View attachment 1158444View attachment 1158445View attachment 1158447
Sent from my GT-N7000
Click to expand...
Click to collapse
If you know how to use pc odin then you can make new instalation. It will solve your problem.
If you dont know how to use it. Go to samsung service center and let them install it.
I rooted it using Odin, if there is a link on how to make that new installation I can do it. I don't wanna try something on my own and get stuck
In case if I do take it to the service I will have to unroot it won't I ?
Now that's another dilemma, what if it's bricked then :-( ..
IM so damn confused now
Gimme one solid thing to do and I will now..
I tried recovery mode, wiping the cache, no go.. Still gives the error..
Sent from my GT-N7000
motionexecuter said:
I rooted it using Odin, if there is a link on how to make that new installation I can do it. I don't wanna try something on my own and get stuck
In case if I do take it to the service I will have to unroot it won't I ?
Now that's another dilemma, what if it's bricked then :-( ..
IM so damn confused now
Gimme one solid thing to do and I will now..
I tried recovery mode, wiping the cache, no go.. Still gives the error..
Sent from my GT-N7000
Click to expand...
Click to collapse
If already rooted then use mobileodin pro to flash any rom you want. Buy it in google market. Look into youtube type mobileodin for visual tutorial.
Pc odin tutorial. http://androidadvices.com/update-galaxy-note-n7000-with-ics-4-0-3-firmware/
I found this ...
ht tp://techie-buzz.com/android/manually-install-the-official-android-4-0-ice-cream-sandwich-firmware-lpy-on-samsung-galaxy-note.html
Sent from my GT-N7000
motionexecuter said:
I found this ...
ht tp://techie-buzz.com/android/manually-install-the-official-android-4-0-ice-cream-sandwich-firmware-lpy-on-samsung-galaxy-note.html
Sent from my GT-N7000
Click to expand...
Click to collapse
Mate best thing is go to download mode and flash a gb rom in pc odin without wiping anything when on ics..... if ur able to flash gb then u have no probs, if flashing stops at factory img then ur in a soup....
Mate if you are so much scared then just try to copy contacts.apk from any ICS rom into system/app folder and assign correct permission and reboot you will be ok.
---------- Post added at 08:24 AM ---------- Previous post was at 08:22 AM ----------
You can also copy phone.apk from any ics rom just replace contacts.apk and phone.apk and assign correct permission with the help of root explorer
Anybody who has non-rooted, untouched note brick this way?
I guess not....
Sent from my GT-N7000 using xda app-developers app
mine! fixed! i already brought my Note at service center this morning then afternoon samsung texted me they say they change the motherboard...
from now on no more flash firmware... stick to 1 fw DXLP gingerbread not ICS...
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
i already have traumatize with this flashing firmwares... good thing i have a warranty...
---------- Post added at 05:16 PM ---------- Previous post was at 05:14 PM ----------
praetorius said:
Anybody who has non-rooted, untouched note brick this way?
I guess not....
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
yes i have a friend... he is using a Stock Firmware no root. he just go to restore factory settings then! Miracle Happen the Note is Bricked! Miracle from Hell...
---------- Post added at 05:39 PM ---------- Previous post was at 05:16 PM ----------
motionexecuter said:
I rooted it using Odin, if there is a link on how to make that new installation I can do it. I don't wanna try something on my own and get stuck
In case if I do take it to the service I will have to unroot it won't I ?
Now that's another dilemma, what if it's bricked then :-( ..
IM so damn confused now
Gimme one solid thing to do and I will now..
I tried recovery mode, wiping the cache, no go.. Still gives the error..
Sent from my GT-N7000
Click to expand...
Click to collapse
If your Note is Bricked! then it won't open...
You read my Story.
Theres a lot of Samsung Service in Philippines but different owner. I went to Samsung last 2 days. Then they asked me What Happen? Im so stupid i accidentally told them that i flashed it using ODIN. They told my Warranty is Void because of ODIN. They gonna charge me for Changing Motherboard. I said no way i will pull out my Note.
Next Day i went to other Samsung Service Center i prepared myself then They asked me again what happen? This time i'm careful. I told them that i just Restore Factory settings. Then they check my Warranty. Then they said Okay you call us tom if already fixed.
Then that afternoon i received SMS from Samsung that my Note is fixed already ready for pick up. That's it. No payment... One thing i have a 2 costom binaries there. because i rooted it.
If you have a warranty do not say i flash it thru ODIN. ODIN. ODIN.
bhasg1007 said:
Mate if you are so much scared then just try to copy contacts.apk from any ICS rom into system/app folder and assign correct permission and reboot you will be ok.
---------- Post added at 08:24 AM ---------- Previous post was at 08:22 AM ----------
You can also copy phone.apk from any ics rom just replace contacts.apk and phone.apk and assign correct permission with the help of root explorer
Click to expand...
Click to collapse
Yupp tried this now .. just says applications cannot be installed. Gave it all the permissions too.
And another thing I noticed omfg ! The stock file explorer ain't there..
This is getting creepy now..
And even if I do plan to take it to service they will obv know I rooted it..
What IM trying now is flashing another ROM.
Downloading Rocket ROM, will check in awhile now.
Sent from my GT-N7000
Guys ! You have installed the OTA update on a Stock ROM which was rooted.
I think all guys have to cool down and read this !
You are having issues because you have installed OTA on a rooted ROM.
It has most probably nothing to do with EMMC bug or Hard Brick.
I also donot recommend flashing via Mobile ODIN for ICS as someone has suggested.
To solve your problem ,
1) ODIN Method
a) go to Download Mode (Power Button + Vol down + Home)
b) Flash the ICS ROM posted in Dr.Ketan Thread in the PDA
Remember that options are ticked according to this image.
Donot tick repartition.
You can root it by Heading to Dr Ketans thread.
2) CWM Method (Custom Firmware)
a) go to Download Mode (Power Button + Vol up + Home)
b) Flash the ROM close to LPA without any Reset or Wiping.
This will endup with a custom ROM Clea Note (LPA Rooted)
Too late to check that..
I reinstalled the stock ics ROM using mobile Odin pro. Works fine now... Yipee..
I can access the contacts and phone options too ..
And for some reason it does not show the yellow triangle even though it used to everyone before..
But previously I lost the phone and contacts button on the main screen ..
How do I get it back to how it was ?
And why is there no file manager still ?
I see only 3 icons now instead of 5...
Sent from my GT-N7000
Hey guys, I pulled the ICS update.bin from my tab and converted it into a flashable zip file. It must be flashed from STOCK recovery, NOT cwm recovery/TWRP etc. This file basically patches every system file on the tab, so the only way to flash this successfully is to go back to stock and update your way up to stock FE01. It doesn't matter how you get to stock FE01 as long as you are on it and are using the FE01 radios. Once you have reached stock FE01, Flash this file in STOCK recovery: https://dl.dropbox.com/u/20070269/FE01a_to_LP11d_update.zip
Now, place this file: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip on your SD card.
Once you have flashed the update successfully and placed the superuser.zip on your SD card, odin this recovery: http://droidbasement.com/galaxy/recovery/cwm5/p4vzw/5/recovery.tar.md5 and boot directly into recovery right after you odin it so that the tab does not boot fully into the OS and overwrite what you just flashed with the stock recovery. Once you have booted into cwm recovery, navigate to the superuser.zip and flash and then reboot. Congratulations, you're running Official ICS with root. For those that want CWM recovery to persist after reboot, delete /system/etc/install-recovery.sh with a root file manager.
Of course, credit goes to ChainsDD for the superuser.zip used in this guide
And to pershoot for the CWM recovery used in this guide.
Finally!!!
I can confirm that this file does update the VZW to 4.0.4 with baseband LP11. LTE is finally functioning as well as front and rear cameras. The tab has a whole new feel to it. I haven't tried any of the root files here. I first wanted to make sure that its stable/useful before messing around with rooting.
Big thumbs up for posting
Awesome, thanks Kidserious!
Hoping Pershoot's able to pull drivers from this to integrate into CM9/10.
eXiled Killah said:
Finally!!!
I can confirm that this file does update the VZW to 4.0.4 with baseband LP11. LTE is finally functioning as well as front and rear cameras. The tab has a whole new feel to it. I haven't tried any of the root files here. I first wanted to make sure that its stable/useful before messing around with rooting.
Big thumbs up for posting
Click to expand...
Click to collapse
Yea, this is a very nice update. I'm actually very impressed.
muzzy996 said:
Awesome, thanks Kidserious!
Hoping Pershoot's able to pull drivers from this to integrate into CM9/10.
Click to expand...
Click to collapse
That's what I was most excited about...new kernel source and version. Up until now, all AOSP builds for the LTE 10.1 were based on the 2.6.38 honeycomb kernel. This new update brings us 3.1.10 and updated drivers.
Definitely will be cool.
Bah, had to go way back to an older stock image I had but eventually got back to HC 3.1 and upgraded back up.
Definitely an improvement over stock or even overclocked honeycomb 3.2. Going to be nice to get CM 10 someday.
This update is great..I'd say it was worth the wait, but since Jelly Bean is already out and soon to be dated I will not.
Thanks
This worked great! Waiting for a long time to get this on the LTE!
Woot!
Will be working on this today! Can't wait!
Maybe one of the great devs, can pull the modem out into an install file. Maybe the modem and cameras will work with JB!
Do you think we coudl use these files on the ota dowload from VZW?
Also, how did you get back to stock? I know I have Pershoots kernel, rooted and CWM
well, my dumbarse figured it out. for those that are dense like me, I used the Odin file in rylon360's thread on rootswiki.
http://rootzwiki.com/topic/7718-romleakodineg01-factory-stock-odin-image-vzw-lte-tab-101/ to get back to stock, then I did system updates three times. Small one, large one, Small one. to get to stock FE01.
then followed this thread to update.
Thanks so much!!!!
---------- Post added at 11:26 AM ---------- Previous post was at 10:49 AM ----------
anyone else have issue with Tibu restoring apps? I loaded my Tibu folder back onto the device but it wont recognize the apps. Tibu had the latest update too.
Does this wipe the tablet at all?
My fiance's 10.1 is unbearably slow but she's using it for work so I can't root it. Will I be able to run the update from stock recovery and keep everything how it is?
Yes. I updated another that was all stock and it retained everything. My tab however won't see any of the tibu backups I saved to my PC. Sucks
Sent from my SCH-I905 using Tapatalk 2
pickupman66 said:
Yes. I updated another that was all stock and it retained everything. My tab however won't see any of the tibu backups I saved to my PC. Sucks
Sent from my SCH-I905 using Tapatalk 2
Click to expand...
Click to collapse
try going into /data/media/TitaniumBackup with root explorer and change permissions on the titanium backup folder to all checks.
Sent from my Galaxy Nexus using Tapatalk 2
Ill try that tomorrow. It showed the apps with the strike they but no icon and had a ? When I clicked on them. Said no APk found. So sad cause I made the backup b4 flashing.
Sent from my SCH-I905 using Tapatalk 2
pickupman66 said:
Ill try that tomorrow. It showed the apps with the strike they but no icon and had a ? When I clicked on them. Said no APk found. So sad cause I made the backup b4 flashing.
Sent from my SCH-I905 using Tapatalk 2
Click to expand...
Click to collapse
Did you get this working? I did the same -- backup in Titanium, copy folder to PC, ran through the process to upgrade to latest version and then copy Titanium folder back to /sdcard and all was fine. I've done this several times in the past as well.
I need to do some reading and figure out how to get back to 100% stock. I am pretty sure I am just running the OTA rooted HC ROM so i will need to flash the regular stock ROM and then get recovery back.
The tab was sooo darn slow before. Cant wait to see how it does after this.
JewRican said:
I need to do some reading and figure out how to get back to 100% stock. I am pretty sure I am just running the OTA rooted HC ROM so i will need to flash the regular stock ROM and then get recovery back.
The tab was sooo darn slow before. Cant wait to see how it does after this.
Click to expand...
Click to collapse
Thats what I did, wanted to start fresh so what I installed was HC 3.1 and wiped data and all. Then I ran OTA after OTA until I got to ICS. Then I installed CWM from droidbasement (pershoot) and used it to flash superuser. Tab runs MUCH better than before. I'm currently running stock kernel and intend to do a CWM image of my current setup and wait for CM updates with LTE rolled in before doing any further tinkering with the tablet. I don't even feel the need to run an overclocked kernel at this point.
*edited below*
where else can i grab odin? his link seems to be dead.
Do you have it that you can post somewhere? Seen it somewhere else?
*edit* - found it!
http://forum.xda-developers.com/showthread.php?t=1651794
Ectiech. I have flashed my phone so much I can do with eyes closed. I have done tibu this way several times. Something must have happened to the backup I made because I copied the tibu folder from my cell running slimbean jellybean rom and all the apps restored perfectly from there. Sadly I had not played the games on my phone like I did on my tablet.
Sent from my SCH-I905 using Tapatalk 2
{
"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 returned mine to basic Verizon, no root. Took off clockwork when I returned to stock and let it auto upgrade itself a few weeks ago. Figured it needed to be stock
Copied over and then rebooted to standard recovery and let it fly. Didn't wipe anything. Everything is there. Proggies work. Haven't check cameras.
My tab was stripped...so didn't matter if I lost everything.
Hope my pic posts...hit 58 mbs. Download driving last night. I'm town tested speed changing towers, in upper 30s.
I love u guys. THANKS!
Sent from my SCH-I905 using xda app-developers app
From Android Authority
{
"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"
}
The official firmware can be used to restore your tablet to its factory state, which means that it can be used as an escape route if you ever need to revert to stock firmware. For instance, this can be very handy if you stumble upon an bad or misbehaving custom ROM that makes your tablet malfunction.
This guide shows you how to revert the Galaxy Tab 2 7.0 P3113 to Android 4.0.4 ICS build UEBLH2 (stock official firmware).
Warning
The instructions in this guide are intended for use with the Samsung Galaxy Tab 2 7.0, model number GT-P3113. Applying these instructions on another device or model may produce undesired outcomes.
The information in this guide is provided for instructional and educational purposes only. There is no guarantee that these instructions will work under your specific and unique circumstances.
Use these instructions at your own risk. We shall not hold any responsibility or liability for whatever happens to you or your device arising from your use of the info in this guide.
Read and understand the whole guide first before actually performing the instructions.
Requirements
Samsung Galaxy Tab 2 7.0 GT-P3113
A Windows PC
Install your handset’s USB drivers on the PC. You may install the drivers by installing Samsung Kies.
Enable USB debugging on your handset.
Disable antivirus, firewall, and other security software. Also disable Samsung Kies and other software that accesses your phone. Such software can interfere with the procedure in this guide.
Download the following files to your computer:
UEBLH2 firmware update package for Galaxy Tab 2 7.0 GT-P3113 (P3113UEBLH2_P3113XARBLH2_XAR.zip, 785 MB)
Odin 3.04 (Odin3_v3.04.zip, 456.59 kB) (Attatched)
Make sure your device’s battery still has at least 70% power. You don’t want the device to shut down in the middle of the procedure.
Backup all personal data on your phone to make sure you have a copy of your personal data (e.g., contacts, SMS, MMS, Internet settings, Wi-Fi passwords, and the like) in case the procedure in this guide erases such data.
Instructions
Using ZIP extraction software, extract the *.tar.md5 file contained in the UEBLH2 firmware update package.
Extract the contents of Odin3_v3.04.zip to your computer.
Turn off your tablet. Make sure it is not hooked up to your PC.
Run Odin on your computer by double-clicking Odin3 v3.04.exe.
Click the PDA button in Odin and load the *.tar.md5 file contained in the UEBLH2 firmware update package that you unzipped.
Do not change any other setting in Odin. Make sure that the checkbox for “Re-partition” is not ticked.
Reboot the tablet into Download Mode by holding down the Volume Down and Power buttons until you see the warning screen. Press the Volume Up key to continue to Download Mode.
Connect the tablet to your PC via USB cable. You should see an “Added!” message on the Odin window.
Click the Start button in Odin to begin flashing the firmware to your tablet. When installation completes and succeeds, Odin will display a “PASSED” message in one of its boxes. The tablet will also automatically reboot.
If, on rebooting, the screen gets stuck at the Samsung logo, try resolving it by doing the following:
Turn off the tablet.
Boot into Recovery Mode by holding down Power and Volume Up buttons together until the screen turns on. When the Samsung logo appears, let go of the Power button but keep holding down the Volume Up button until the device boots into recovery.
In Recovery Mode, select Wipe data/Factory reset and select Yes on next screen.
Select Reboot system now to reboot the tablet
Congratulations! You’ve successfully reverted your Samsung Galaxy Tab 2 7.0 to Android 4.0.4 Ice Cream Sandwich build UEBLH2.
"Disable my AV/security" before I download from unknown links ?
Cool story bro. :laugh: General tip for PC users , scan everything you download onto your desktop no matter the source with your AV. Especially an ".exe "
Nice guide apart from that.
thank you.. I didnt think of wipe data/factory. I was stuck on samsung logo. i wanted to return to stock since I'm giving the tablet to my nephew and don't want him doing crazy stuff. :victory:
Sean_Seany said:
"Disable my AV/security" before I download from unknown links ?
Cool story bro. :laugh: General tip for PC users , scan everything you download onto your desktop no matter the source with your AV. Especially an ".exe "
Nice guide apart from that.
Click to expand...
Click to collapse
NO, not disable before downloading, disable your AV before using Odin to flash, as IT IS A WELL KNOWN FACT that some AV programs can cause issues with flashing ROM's.
daniel644 said:
NO, not disable before downloading, disable your AV before using Odin to flash, as IT IS A WELL KNOWN FACT that some AV programs can cause issues with flashing ROM's.
Click to expand...
Click to collapse
Did you actually read what the OP posted ? Nah didnt think so . So why exactly do you need to disable AV/Secuirty for a USB file transfer ? Please enlighten me with your facts.....
Sean_Seany said:
Did you actually read what the OP posted ? Nah didnt think so . So why exactly do you need to disable AV/Secuirty for a USB file transfer ? Please enlighten me with your facts.....
Click to expand...
Click to collapse
If you are having issues disabling your antivirus software, then don't disable it. I never disable mine. The only reason I added it to the post is because in rare cases the AV can cause issues for some reason or another.
Sean_Seany said:
Did you actually read what the OP posted ? Nah didnt think so . So why exactly do you need to disable AV/Secuirty for a USB file transfer ? Please enlighten me with your facts.....
Click to expand...
Click to collapse
I think you misunderstand, when flashing files VIA ODIN certain antiviruses have been known to cause issues, personally I never have but it is a standard disclaimer on ANY Device to computer connection, when doing debugging or flashing not file transfers, I see the same disclaimer on all the Droid Razr Utility builds, and most ROM's being flashed via ODIN, it's rare but it could happen.
I think the reason for disabling your AV,is because it and your pc dont know the difference. When you run a program that flashes 'firmware' like Odin,it can be detected as malicious and blocked.HTC recommends the same thing for flashing with their exe files,and thats the same reason why its recommended during most rooting process'.
dude I thank you for this... I bought a gt 3113 3 days ago and it came with jb out of the box, dont get me wrong jb is awesome i run it on my sgs2 only thing is id like to use my tablet for streaming online content and most of the sites i view still use flash which jb no longer supports so i been looking for ways to revert it back to stock ics cause i love the ir function of the stock rom and most custom roms bork the ir blaster as per my research. anyway anymore details i should know before attempting this?? thanks in advance
Edit: do you have another linky for the FW? hotfile keeps erroring out on me thanks again
aj9507 said:
dude I thank you for this... I bought a gt 3113 3 days ago and it came with jb out of the box, dont get me wrong jb is awesome i run it on my sgs2 only thing is id like to use my tablet for streaming online content and most of the sites i view still use flash which jb no longer supports so i been looking for ways to revert it back to stock ics cause i love the ir function of the stock rom and most custom roms bork the ir blaster as per my research. anyway anymore details i should know before attempting this?? thanks in advance
Edit: do you have another linky for the FW? hotfile keeps erroring out on me thanks again
Click to expand...
Click to collapse
Yours came with JB??? Just curious what country are you in? The 3113 is US only no?? Maybe were finally getting our official release any day now...
Sent from my crack smoking SGH-i777
Slavestate said:
Yours came with JB??? Just curious what country are you in? The 3113 is US only no?? Maybe were finally getting our official release any day now...
Sent from my crack smoking SGH-i777
Click to expand...
Click to collapse
Yup usa version. 4.1 android love jb but hate that I can't stream from most sites due to lack of flash and most root methods I can't get to work
Sent from my GT-P3113 using Tapatalk HD
Flash works perfect on every jelly bean rom I have tried just simply sideload it but I suppose thats of topic.
yup sideloaded it and even running the older version of the browser to ensure flash support and its laggy and stutters lovin the tablet though
Yes.... some of these are preloaded with 4.1.1.
I bought 2 of these for my daughters. 1 was defective. When I took it back, the store didn't have anymore so they sent me to a store in another city.
I ended up with one running 4.0.4 and one running 4.1.1.
BuLLitz said:
Yes.... some of these are preloaded with 4.1.1.
I bought 2 of these for my daughters. 1 was defective. When I took it back, the store didn't have anymore so they sent me to a store in another city.
I ended up with one running 4.0.4 and one running 4.1.1.
Click to expand...
Click to collapse
PS:The 4.1.1 that came preloaded is UECLK7.
It can be found here...
http://androidjinn.com/how-to-install-ueclk7-android-4-1-1-jelly-bean-on-p3113-galaxy-tab-2.html/2
---------- Post added at 02:14 AM ---------- Previous post was at 01:54 AM ----------
BuLLitz said:
PS:The 4.1.1 that came preloaded is UECLK7.
It can be found here...
http://androidjinn.com/how-to-install-ueclk7-android-4-1-1-jelly-bean-on-p3113-galaxy-tab-2.html/2
Click to expand...
Click to collapse
Following the instructions there, I can confirm that the versions are the same now. Both of my tablets are 4.1.1. In addition, KIES recognizes it as a valid version.
BuLLitz said:
PS:The 4.1.1 that came preloaded is UECLK7.
Following the instructions there, I can confirm that the versions are the same now. Both of my tablets are 4.1.1. In addition, KIES recognizes it as a valid version.
Click to expand...
Click to collapse
The update was officially pushed out today through Kies.
Sent from my crack smoking SGH-i777
well now
I used this and it worked quite well, but now the drivers won't install right when I plug it into my computer.
any suggestions?
thanks.
Re-enable debugging.
ROCK ON! Nice guide!!! I was on JB4.1.1, but, IMO, not good. i rolled back to 4.0.4
ugh
Thepooch said:
Re-enable debugging.
Click to expand...
Click to collapse
Not only can I not install drivers, I can't find the debugging either.
I'm not totally retarded, but I'm starting to feel like it
OK so got a little ahead of myself this afternoon and thought wth its time to root. Only problem was i did not properly identify my model number. So basically i rooted a n910t with the n915t root i followed this guide
http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993
So after i already flashed it i noticed something was wrong with my screen. Then i realized my mistake (shucks) what s a guy to do except ask an expert.
Basically it was on nk3 and i could only find nk4 so i tried to see if that would help it did not.
To the real issue! So i loaded nk4 on it and it loaded fine but the problem is my screen touch is off. This started after the attempted root with the files for the wrong phone. To give you an idea in order to press a correct button i have to press about an inch or so above the button i am trying to press. However that only when the screen rotation is normal. When i flip the screen rotation landscape it work fine. (in other words when i turn the phone to the side homebutton to the right). I am super mad i just bought the dam thing outta contract so you can imagine how i am feeling right now. If any one can help or tell me if there is a kernel i can download i would appreciate it. I dont have the insurance either cause i never break or brick my phones (ha) thanks guys for reading
Scott
scoeas1982 said:
OK so got a little ahead of myself this afternoon and thought wth its time to root. Only problem was i did not properly identify my model number. So basically i rooted a n910t with the n915t root i followed this guide
http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993
So after i already flashed it i noticed something was wrong with my screen. Then i realized my mistake (shucks) what s a guy to do except ask an expert.
Basically it was on nk3 and i could only find nk4 so i tried to see if that would help it did not.
To the real issue! So i loaded nk4 on it and it loaded fine but the problem is my screen touch is off. This started after the attempted root with the files for the wrong phone. To give you an idea in order to press a correct button i have to press about an inch or so above the button i am trying to press. However that only when the screen rotation is normal. When i flip the screen rotation landscape it work fine. (in other words when i turn the phone to the side homebutton to the right). I am super mad i just bought the dam thing outta contract so you can imagine how i am feeling right now. If any one can help or tell me if there is a kernel i can download i would appreciate it. I dont have the insurance either cause i never break or brick my phones (ha) thanks guys for reading
Scott
Click to expand...
Click to collapse
Ok install twrp wipe everything including the internel... ( not ext )
Reboot recovery...
Pull the battery reboot download mode (odin)
And flash this or a stock K4....
Your stock odin will wipe it back to its original state..
One other thread case you need it.
http://forum.xda-developers.com/showthread.php?p=55968427
http://forum.xda-developers.com/showthread.php?p=55989825
Flash.
Part of the Solution
I would be careful. I would odin back to stock boot it up unrooted and then follow the right thread. I know a few who have wiped system and it was game over as we don't have a pit file. Watch what you wipe.
BAD ASS NOTE 4
i did exactly as you said and its still the same way i havenever came across somethng that was not reversable this way
scoeas1982 said:
i did exactly as you said and its still the same way i havenever came across somethng that was not reversable this way
Click to expand...
Click to collapse
So you flashed a stock odin from download mode and its still showing the incorrect version???
Flash.
Part of the Solution
i have taken a pic to show you guys whats up as you can see where my thumb is versus whats selected on the screen
{
"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"
}
[/URL][/IMG]
its not so much the wrong version as it is the touchscreen calibration being off i posted a pic so that people may better understand what i am saying.
Have you done a factory reset since you odin'd to the correct version of the stock rom?
scoeas1982 said:
its not so much the wrong version as it is the touchscreen calibration being off i posted a pic so that people may better understand what i am saying.
Click to expand...
Click to collapse
Ok now im confused lol..
What model phone did you buy from the store???? You need to flash a rom that 100% matches your device....
Stock.. odin...
Start all over fresh with YOUR EXACT FIRMWARE..
ok.....[emoji16]
Flash.
Part of the Solution
Lately when I Odin to stock. I have to do a factory reset, as well, or the ringtones/wallpapers, etc. that were previously installed haven't reset.
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
Might reset your calibration.
Flashvetrin said:
Ok now im confused lol..
What model phone did you buy from the store???? You need to flash a rom that 100% matches your device....
Stock.. odin...
Start all over fresh with YOUR EXACT FIRMWARE..
ok.....[emoji16]
Flash.
Part of the Solution
Click to expand...
Click to collapse
I knew this would be confusing. I bought the n910t. Tmo version. What i did was accidently flash the 915t root files. This is what messed up the calibration. I have wiped and reinstalled to no avail my theory is that there is a kernel or a patch (dont really know the lingo) to fix the display. Thats what i am looking for. There is no odin fw for 4.4.4 nk3 so i flashed nk4 hoping that would fix the issue. I know what i did sounds noobi, but i am not totally a noob.
i tried that as well hoping for the best it did not work though
scoeas1982 said:
I knew this would be confusing. I bought the n910t. Tmo version. What i did was accidently flash the 915t root files. This is what messed up the calibration. I have wiped and reinstalled to no avail my theory is that there is a kernel or a patch (dont really know the lingo) to fix the display. Thats what i am looking for. There is no odin fw for 4.4.4 nk3 so i flashed nk4 hoping that would fix the issue. I know what i did sounds noobi, but i am not totally a noob.
Click to expand...
Click to collapse
Ahh ok..
just wanted to clarify your Exact model#.
Im puzzled as to why odin is not wiping you clean.
You should be starting over fresh and not having ANY remnents of this pre-existing flash still intact after flashing stock firmware...
Try downloading the completly stock from sams mobile or from the first post.
And just pull the battery and flash the stock firmware again....
Flash.
Part of the Solution
mmm thats an idea i was using my octoplus box the firmware i donwloaded from the support site. Perhaps that is not a full firmware wipe but it was like 2.46 gigs.
scoeas1982 said:
mmm thats an idea i was using my octoplus box the firmware i donwloaded from the support site. Perhaps that is not a full firmware wipe but it was like 2.46 gigs.
Click to expand...
Click to collapse
Lol i was just looking at buying one of those.... [emoji106]
Flash.
Part of the Solution
they are pretty awesome i own a repair shop and use then when people jack up there phone.s. I also do unlocks with it but mostly use z3x. So you can imagine how stupid i feel jacking up my own phone. Thats new none the less
scoeas1982 said:
they are pretty awesome i own a repair shop and use then when people jack up there phone.s. I also do unlocks with it but mostly use z3x. So you can imagine how stupid i feel jacking up my own phone. Thats new none the less
Click to expand...
Click to collapse
Lol so i know in not talkin to a rookie by any means..
i wouldnt try flashing any kernel like you asked about[emoji33]. mix an match that and its game over... [emoji85] i think if you get the odin stock firmware and get back into download mode youll be golden.. [emoji51]
youll be back to square one..
And knox will trip as well.. this im sure you know...
Good luck soldier...
[emoji16]
Flash.
Part of the Solution
im dl it now i am going to give it a try. I just cant really imagine what i messed up that cant be fixed with a fresh install. I know there are phones out there thaat when you root it and odin a kernel it messes up the display,wifi,bt ect. that why i was thinking i would need a kernel to fix it.
After you Odin to stock with the downloaded file from Samsung.
And doing a factory reset.
If your calibration is still screwed up.
You could try flashing a rom.
Maybe firekat or something aosp like cmRemix and see if the rom doesn't overwrite the remnants that are killing you.
---------- Post added at 08:37 AM ---------- Previous post was at 08:36 AM ----------
You can get the stock image downloads from here quicker btw:
http://forum.xda-developers.com/showthread.php?t=2957156
Aren't there hidden codes to reset calibration? I think there might have been on my S3. So there may be one on the note as well. Maybe search around for that also? Just an idea.