HC 3.1 – OTA (update.zip) – Galaxy Tab 10.1
http://droidbasement.com/db-blog
Thanks for this, I have the 10.1v and would like to know if this will work. I can't wait to try Will wait for confirmation first though.
Ur my hero today
Sent from my MB860 using XDA Premium App
is it possible to just boot using this 3.1 rom without flashing to test on the 10.1v?
is root intact
The update is a delta update. It doesn't re-flash /system but overwrites applications and updates their parts. This is why removing the stock apps - such as in my case - you cannot complete the update since it's trying to change parts of the apps and not simply drop in a replacement.
You cannot lose root to this update since it doesn't know about Superuser.apk and su.
This is a vanilla system with no su or superuser. It is not a delta. It is a complete system.
Put back su/superuser after flash and after your back up.
Anyone tried this update on the 10.1v model?
I tried it on the 10.1v, but is gives a MD5 sums mismatch
That's sad... Thanks anyway!
GSO said:
I tried it on the 10.1v, but is gives a MD5 sums mismatch
Click to expand...
Click to collapse
That is depressing news Looks like us 10.v users will have to wait for some love.
ill make an update.zip.
ill re-release in this thread. ill try to get it out tonight.
thanks for the lending hand pershoot.
md5 doesn't match.
pershoot said:
ill make an update.zip.
ill re-release in this thread. ill try to get it out tonight.
Click to expand...
Click to collapse
Thanks for all the effort pershoot. It's much appreciated by all.
Will the update.zip work with the 10.1v?
It will flash. Work remains to be seen.
You can try a restore from the tar img provided manually by unpacking it in system via cmd line. Take a nandroid backup first before unpacking, in case of issues so you can roll back.
pershoot said:
It will flash. Work remains to be seen.
You can try a restore from the tar img provided manually by unpacking it in system via cmd line. Take a nandroid backup first before unpacking, in case of issues so you can roll back.
Click to expand...
Click to collapse
Unfortunately my skills are not that great, I am more likely to break something. Flashing something in CWM is about the extent of my knowledge, unless I am following a guide Appreciate you getting back to me though. Thanks again.
pershoot thanks so much for all your work that you've done thus far
edit: It's taking a while on the "Samsung Galaxy Tab 10.1" screen after advanced restore and clearing cache :-/
kentoe said:
pershoot thanks so much for all your work that you've done thus far
edit: It's taking a while on the "Samsung Galaxy Tab 10.1" screen after advanced restore and clearing cache :-/
Click to expand...
Click to collapse
it is rebuilding dalvik. takes some time.
you can monitor its progress with adb logcat.
pershoot said:
it is rebuilding dalvik. takes some time.
you can monitor its progress with adb logcat.
Click to expand...
Click to collapse
Oh okay, well unfortunately adb logcat isn't working I get
"- exec '/system/bin/sh' failed: No such file or directory (2) -"
when I try to execute logcat. It does find the device though in adb devices. Can't do anything on DDMS either. How long should rebuilding dalvik take?
Stock recovery not liking it. Aborts itself after you select the zip from update. Not sure if the zip is corrupted or maybe my tablet doesn't have enough battery.
Sent from my GT-P7510 using XDA Premium App
Related
So I was trying to troubleshoot an SMS issue with AOSP 1.6 so I decided to flash back to Fresh 1.0. I also performed a wipe/factory reset. Fresh would not boot - it would just endlessly loop through the boot process, crashing at various points. I tried Fresh 1.1. Same problem. I re-downloaded Fresh 1.0 to make sure my file was not corrupt, flashed that, and have the same problem.
So I decided to start trying to recover from my various backups. What do you know - every single one is corrupt. From adb I see:
Code:
Verifying backup images...
boot.img: OK
cache.img: OK
data.img: FAILED
misc.img: OK
recovery.img: OK
system.img: FAILED
md5sum: WARNING: 2 of 6 computed checksums did NOT match
On every single one. Even if I make a backup and immediately try to restore it I see this error. I also tried backups of my backups and each of those failed as well. Any way to force these to restore?
So I checked my SD card with various tools - no problems found.
So now I'm left unable to flash 1.5 or restore from or make any backups.
Does anyone have any ideas what could be wrong or what I should do to fix it? What other information could I provide?
honestly I would try to RUU and reroot and then try flashing a backup it may not be that the backups are corupt put that something isnt letting it read that part of the backup correctly.
gthing said:
So I was trying to troubleshoot an SMS issue with AOSP 1.6 so I decided to flash back to Fresh 1.0. I also performed a wipe/factory reset. Fresh would not boot - it would just endlessly loop through the boot process, crashing at various points. I tried Fresh 1.1. Same problem. I re-downloaded Fresh 1.0 to make sure my file was not corrupt, flashed that, and have the same problem.
So I decided to start trying to recover from my various backups. What do you know - every single one is corrupt. From adb I see:
Code:
Verifying backup images...
boot.img: OK
cache.img: OK
data.img: FAILED
misc.img: OK
recovery.img: OK
system.img: FAILED
md5sum: WARNING: 2 of 6 computed checksums did NOT match
On every single one. Even if I make a backup and immediately try to restore it I see this error. I also tried backups of my backups and each of those failed as well. Any way to force these to restore?
So I checked my SD card with various tools - no problems found.
So now I'm left unable to flash 1.5 or restore from or make any backups.
Does anyone have any ideas what could be wrong or what I should do to fix it? What other information could I provide?
Click to expand...
Click to collapse
Have you tried to use the RUU to return to complete sock and then just re-root? The RUU does not depend on your SD card, just in case that is the culprit. There is a link on my sig. If not that would be my next step.
wtphoto said:
honestly I would try to RUU and reroot and then try flashing a backup it may not be that the backups are corupt put that something isnt letting it read that part of the backup correctly.
Click to expand...
Click to collapse
Beat me to it.
But a quick thread hijack real quick. I see in your sig you have a horizontal fresh nexus hybrid bootscreen. care to share the source. Sounds cool.
Back on track after this I promise
rockcrawler said:
Beat me to it.
But a quick thread hijack real quick. I see in your sig you have a horizontal fresh nexus hybrid bootscreen. care to share the source. Sounds cool.
Back on track after this I promise
Click to expand...
Click to collapse
give me a min and I will post a flashable zip in the theme sticky
now back to the helping.
Trying to flash RUU from the Fresh blog now. For some reason it is failing to see my phone when it is trying to flash. Could it be because I am in recovery mode?
gthing said:
Trying to flash RUU from the Fresh blog now. For some reason it is failing to see my phone when it is trying to flash. Could it be because I am in recovery mode?
Click to expand...
Click to collapse
Yes. Boot into whatever ROM you can and then try again.
I assume that you have had the ADB drivers working before?
gthing said:
Trying to flash RUU from the Fresh blog now. For some reason it is failing to see my phone when it is trying to flash. Could it be because I am in recovery mode?
Click to expand...
Click to collapse
no this has been brought up a few times you need to make sure you have the most recent sdk installed then copy and paste the adb.exe, adbwinapi.dll and the fastboot.exe into the ruu file then try again.
wtphoto said:
no this has been brought up a few times you need to make sure you have the most recent sdk installed then copy and paste the adb.exe, adbwinapi.dll and the fastboot.exe into the ruu file then try again.
Click to expand...
Click to collapse
+1 on this,
Someone should update the ruu thread to include this.
Installed the adb driver (no, I didn't have it previously) and copied the files from the latest SDK. No luck still but I'm going to keep trying.
you could also try booting into fastboot and trying it who knows it might be becuase you are in recovery just poer off and hold volume down and power at the same time to get into fastboot and try it that way.
wtphoto said:
you could also try booting into fastboot and trying it who knows it might be becuase you are in recovery just poer off and hold volume down and power at the same time to get into fastboot and try it that way.
Click to expand...
Click to collapse
That did it! Flashing now! Thanks!
EDIT: Maybe I spoke too soon. The flasher is stuck at "erasing user data..." and is showing 0% and the phone is showing the htc boot screen. I don't know if it's safe to cut it off and start over or not.
Windows had to increase virtual memory in the middle of the operation and I think it jacked things up ....
np glad to help.
Yea ... it seems to be getting stuck on "Erasing user data...." not sure what to try next.
unfortunatly thats the extent of the knowledge that I have I would try contacting gbhil or toast or fresh or one of the other devs to see what they say.
Pull battery, do a factory reset (BACK+HOME+POWER) & then attempt to reflash RUU.
gu1dry said:
Pull battery, do a factory reset (BACK+HOME+POWER) & then attempt to reflash RUU.
Click to expand...
Click to collapse
No luck... I give up for tonight...
gthing said:
No luck... I give up for tonight...
Click to expand...
Click to collapse
That really sucks.
same thing
The same thing happened to me when i tried to flash gumbo 1.5c. I flashed RUU and then re-rooted that resolved my issue..
Turns out my problem was that I was trying to flash the RUU from a virtual machine. I'm used to being able to flash WM roms from a Windows VM but apparently it doesn't work with the Android tools. I could also not use the auto-rooter from the VM.
I had to track down a Windows machine () and then was able to get everything flashed and running without too much trouble.
Thanks for everyone's help on this. My phone is now back up and running and I was able to confirm the problem I was having: AOSP 1.6 radio is incompatible with the airave and will cause you to not be able to send SMS messages.
PLEASE READ:
FIRST IF YOU HAVE INSTALLED THE OTA UPDATE(TO 2.2.2) ALREADY AND WERE NOT ROOTED BEFORE THE OTA UPDATE YOU CAN ONLY GET CLOCKWORK RECOVERY THROUGH THE FAST BOOT METHOD BELOW AS ONLY ROOT CAN FLASH CWR THROUGH ROM MANAGER
IF YOU ALREADY HAVE CWR INSTALLED BUT DO NOT HAVE OR TRIED TO INSTALL THE OTA UPDATE YET AND ARE STILL ON VERSION 2.2.1 DO NOT UPDATE!!! DOWNLOAD THE ZIP IN THIS THREAD http://forum.xda-developers.com/showthread.php?t=1008650 AND FLASH THROUGH CLOCKWORK RECOVERY AND YOU WILL HAVE THE UPDATE PLUS IT WILL BE ROOTED (CURRENTLY THERE IS NO WAY TO ROOT WITH THE UPDATE UNLESS IT'S THIS METHOD)
IF YOUR STREAK 7 CAME PRE INSTALLED WITH ANDROID VERSION 2.2.2 YOU CAN ONLY GET CLOCKWORK RECOVERY THROUGH THE FAST BOOT METHOD BELOW AS ONLY ROOT CAN FLASH CWR THROUGH ROM MANAGER
Ladies and Gentlemen,
After over 72 long hours and barely any sleep we now have a working Clockwork Recovery!!! I cant believe I did it! Thanks to everyone in the community that pitched in to make this happen, I couldnt have done it without the help of all of you! Thanks!!
Special thanks to Koush for taking the time to chat with me and Bogdi1988.. one guy on irc told me "You should feel lucky, Koush is even talking to you about this, he ignored me for weeks" hahaha I guess he knew how close we were so we didn't mind helping us get to the finish line! I dont know what exactly he changed for us but he put the finishing touches on it.
AGAIN: YOU CAN FLASH CLOCKWORK RECOVERY MOD BY USING ROM MANAGER(IF YOU HAVE ROOT ACCESS) OR INSTALL MANUALLY THROUGH FASTBOOT
DO NOT PERFORM A FACTORY RESET FROM WITHIN ANDROID YOU WILL MESS UP YOUR PHONE. IF YOU WANT TO DO A FACTORY RESET DO IT THROUGH CLOCKWORK RECOVERY
make sure your phone is connected to the computer and you have entered fastboot mode on the phone by holding down Volume down and the power button at the same time
recovery: http://mirror.kanged.net/recoveries/recovery-clockwork-3.0.1.9-streak7.img
rename this file to recovery.img (or any easy name to type)and place into the same directory as your fastboot executable (usually androidsdkfolder/tools)
open up a command prompt and navigate to the androidsdkdir/tools folder and type this in at the C prompt
fastboot devices
(to make sure you're connected)
fastboot flash recovery recovery.img
Thanks to Koush, Bogdi1988, BinaryBishop, Lou, nledevil , Hellzya, KenAP, Josh (Hellzya:"hey Jo who are you?") hahaha and everyone else that helped us get this done!!!!!
LET IT BEGIN!!!!!!!!!!!!!!
disclaimer: I am NOT responsible if you brick your phone trying to flash recovery. flash at YOUR OWN RISK. This software is not supported (only by the community), has no warranty(will void your warranty) and is AS-IS you use/flash this at your own risk. AGAIN I AM NOT RESPONSIBLE IF YOU FU*K UP YOUR PHONE!!!!
donate if you want to/feel like it but if not no biggie.. I do this for the challenge mostly not for donations/thanks so if you feel like donating to me I wont stop ya but I'm definitely not asking for them.. if you want to click thanks then I thank you for your thanks , but again you dont have to
here is a mirror: http://dl.dropbox.com/u/23637011/recovery-clockwork-3.0.1.9-streak7.img
if fastboot devices returns nothing, do this:
fastboot -i 0x413c flash recovery recovery.img
if you messed up you system because u can not read, do this:
get this http://dl.dropbox.com/u/23637011/system_orig.img
then do a fastboot flash system system_orig.img
or fastboot -i 0x413c flash system system_orig.img
if u were running dj_steve's perf tweak vs 2, then get this:
http://dl.dropbox.com/u/23637011/system_v02.img
thank you koush for bearing with us tonight and fixing it for us!
i can confirm this works since i messed up my system with rom manager and this saved my life and recovered all data back!
**** ya graffix I've got a 12 pack coming ur way.
Sent from Re-Engineered dInc
Hellzya said:
**** ya graffix I've got a 12 pack coming ur way.
Sent from Re-Engineered dInc
Click to expand...
Click to collapse
haha! i think graphix and i wiped out phones at least 10 times tonight... it was a pain in the b***!
I'm without mgt pc. f..k! Why can't we use terminal emulator!
From my CM7 urban themed Glacier
Lol good job though man. You guys killed it.
Sent from Re-Engineered dInc
KenpoAP said:
I'm without mgt pc. f..k! Why can't we use terminal emulator!
From my CM7 urban themed Glacier
Click to expand...
Click to collapse
wait until koush fixed rom manager tomorrow? :-s
i flashed twice and dont see a change
thatruth132 said:
i flashed twice and dont see a change
Click to expand...
Click to collapse
huh? what do u mean?
I hope this attracts more dev. Too grab one of these. Also bogdi you guys did confirm that wiping data and cache through cwr was working? Last build I used was not. Ill test for my self when I get home. Now somebody needs to come up with a stock rom that we can install via cwr to revert back too incase somebody accidently deletes there backup. Instead of fastbooting the system and boot.img I'm stoked this is good. And too think I was about too sell my device. Stupid me
Sent from Re-Engineered dInc
.............
Hellzya said:
I hope this attracts more dev. Too grab one of these. Also bogdi you guys did confirm that wiping data and cache through cwr was working? Last build I used was not. Ill test for my self when I get home. Now somebody needs to come up with a stock rom that we can install via cwr to revert back too incase somebody accidently deletes there backup. Instead of fastbooting the system and boot.img I'm stoked this is good. And too think I was about too sell my device. Stupid me
Sent from Re-Engineered dInc
Click to expand...
Click to collapse
oops! idk about that lol!!! we tested mounts and restore/backup.
btw.... mount boot and mount recovery in cwm do not work and are NOT supposed to work according to koush. they will not mount.
Its cool ill test when I get home. Not worried about mounts and such. Just restore/ backup. And full wiping
Sent from Re-Engineered dInc
bogdi1988 said:
huh? what do u mean?
Click to expand...
Click to collapse
is it suppose to look like CWM recovery or the stock becuase i flashed twice and still stock
You need too select the update.pkg option that will bring you too cwr
Sent from Re-Engineered dInc
Hellzya said:
You need too select the update.pkg option that will bring you too cwr
Sent from Re-Engineered dInc
Click to expand...
Click to collapse
ohhhhh okay that method also after reboot i got 3 google.framework FC's
Id say that's what you get for messing with the frame work lol. Flash the stock system and boot img and start fresh
Sent from Re-Engineered dInc
That's true lol....now time to look into porting
Sent from my Dell Streak 7 using XDA Premium App
Hellzya said:
I hope this attracts more dev. Too grab one of these. Also bogdi you guys did confirm that wiping data and cache through cwr was working? Last build I used was not. Ill test for my self when I get home. Now somebody needs to come up with a stock rom that we can install via cwr to revert back too incase somebody accidently deletes there backup. Instead of fastbooting the system and boot.img I'm stoked this is good. And too think I was about too sell my device. Stupid me
Sent from Re-Engineered dInc
Click to expand...
Click to collapse
I can confirm.. I just did wipe cahce and worked, just did wipe data/factory reset and it worked now I'm restoring
VRBLL2 Jellybean 4.1.2 OTA - Rooted / Deodex
READ FIRST
*** *** *** *** Disclaimer *** *** *** ***
I am not responsible if you break your stuff. READ READ READ
If you DO NOT own a VERIZON Galaxy Tab 2 7.0 SCH-I705 then DO NOT flash this! If you have not verified and flash this on a p3xxx tab, something will break and I will not help you!
If you're already on Jellybean, you DO NOT need to flash anything in this thread.
Features
Jellybean!!
init.d
de-odexed
Custom bootanimation.zip support
Requirements
A *VERIZON* Galaxy Tab 2 7.0 SCH-I705
Unlocked bootloader
CWM/TWRP Recovery
IF YOU DO NOT MEET THESE REQUIREMENTS.. STOP HERE!
Installation
1. BACKUP BACKUP BACKUP!
2. Wipe cache / dalvik cache (if you have issues, wipe data too)
3. Flash
a. TZ - Trust Zone VRBLL2_tz.zip
b. NON-HLOS - Modem VRBLL2_modem.zip
c. RPM - Resource Power Management -OPTIONAL-Some say it helps battery. I can't tell a difference. VRBLL2_rpm.zip
d. ROM OTA_Jellybean-4.1.2_I705.zip
4. Reboot and enjoy some Jellybean
Thanks
Maine_Coon - Thanks for testing all those builds and flashing things until we got one to boot up!
beanstown106 - We both bricked our tabs first time around :highfive:
stranxk - Jellybean bootanimation.zip
All others who've made rooting/modding/unlocking android possible!
If we helped you out, please consider buying us a couple beers for our troubles :good: Of course, it's not expected
mine
How come the downloaded OTA JB file has ..tar.tar extension? Should it be renamed to ..tar.md5?
Maine_Coon said:
How come the downloaded OTA JB file has ..tar.tar extension? Should it be renamed to ..tar.md5?
Click to expand...
Click to collapse
It is .tar.md5. lol I'm not sure what your looking at buddy :good:
MrHyde03 said:
It is .tar.md5. lol I'm not sure what your looking at buddy :good:
Click to expand...
Click to collapse
Well, I clicked on your link for the OTA download, downloaded 1.47GB file, it has a name "OTA-Jellybean-4.1.2_system-boot.tar.tar".
"I might be crazy, but I am not stupid"(c)
I am on Win8, IE10 machine if that matters.
Maine_Coon said:
Well, I clicked on your link for the OTA download, downloaded 1.47GB file, it has a name "OTA-Jellybean-4.1.2_system-boot.tar.tar".
"I might be crazy, but I am not stupid"(c)
Click to expand...
Click to collapse
See attached image. Odd that yours is .tar.tar..? What browser are you using?
Win8/IE10.
BTW, same thing happened with TWRP recovery which was supposed to be ...tar.md5. I ended up flashing it from adb rather than Odin.
OK, I have changed the extension to tar.md5 from tar.tar.
Flashing as we speak. We'll find out soon what happens.
Very odd... I've Win 8 pro on my other laptop that i use to test all my odin images downloaded with Chrome and they all come in with tar.md5. It may be a ie10 thing, thinking the extensions should be different.
Nice thing is, since it's just the boot and system, if it fails (which it shouldn't since it does it's own md5 check) you can just revert to your backup.
MrHyde03 said:
Very odd... I've Win 8 pro on my other laptop that i use to test all my odin images downloaded with Chrome and they all come in with tar.md5. It may be a ie10 thing, thinking the extensions should be different.
Nice thing is, since it's just the boot and system, if it fails (which it shouldn't since it does it's own md5 check) you can just revert to your backup.
Click to expand...
Click to collapse
No go.
The tab reboots itself after the boot animation.
Did wipe cache, Dalvik, then did factory reset, reflashed. Same thing.
Going to restore TWRP backup. Oh well.
Maine_Coon said:
No go.
The tab reboots itself after the boot animation.
Did wipe cache, Dalvik, then did factory reset, reflashed. Same thing.
Going to restore TWRP backup. Oh well.
Click to expand...
Click to collapse
Try downloading with a different browser to see what happens.
MrHyde03 said:
Try downloading with a different browser to see what happens.
Click to expand...
Click to collapse
Will do.
Opera gives the same ..tar.tar extension, so I am going w/Chrome. Chrome gives the correct .tar.md5 extension.
Maine_Coon said:
Will do.
Opera gives the same ..tar.tar extension, so I am going w/Chrome. Chrome gives the correct .tar.md5 extension.
Click to expand...
Click to collapse
That is honestly, the strangest thing I've ever heard. Theory: Opera and IE both thing the MD5 is a mistake and they rename it .tar.tar. Since it IS a .tar with a .md5 extension, it makes sense.
MrHyde03 said:
That is honestly, the strangest thing I've ever heard. Theory: Opera and IE both thing the MD5 is a mistake and they rename it .tar.tar. Since it IS a .tar with a .md5 extension, it makes sense.
Click to expand...
Click to collapse
I think you are right. Both IE and Opera outsmart themselves, they are used to the MD5 files being just a few kbs, and not having double extension, so they "correct" this.
Again, no go.
I did:
- Titanium backup;
- TWRP backup;
- Wipe cache, Dalvik, factory reset;
- Powered off, rebooted into the download mode;
- Flashed w/Odin successfully.,
- rebooted.
The tab keeps rebooting after the start animation.
Maine_Coon said:
Again, no go.
I did:
- Titanium backup;
- TWRP backup;
- Wipe cache, Dalvik, factory reset;
- Powered off, rebooted into the download mode;
- Flashed w/Odin successfully.,
- rebooted.
The tab keeps rebooting after the start animation.
Click to expand...
Click to collapse
Did you flash the modem? It shouldn't make a difference.. but who knows.
Also, after flashing with odin, try wiping cache and dalvik again.
MrHyde03 said:
Did you flash the modem? It shouldn't make a difference.. but who knows.
Also, after flashing with odin, try wiping cache and dalvik again.
Click to expand...
Click to collapse
Yes, I flashed both Modem and the second zip file.
Gimme a few..
No, the same. Wiped cache and Dalvik immediately after the /successful/ flash from Odin.
Keeps rebooting.
You guys MUST have something on your development tablets I don't have.
Oh well. Like you said, it is not bricked and I can restore my TWRP backup.
nothing out of the ordinary... well, i'm putting together a recovery flashable update right now that may work better. I'm pushing it now then will flash and test.
MrHyde03 said:
nothing out of the ordinary... well, i'm putting together a recovery flashable update right now that may work better. I'm pushing it now then will flash and test.
Click to expand...
Click to collapse
I wonder whether anyone /except the two of you, obviously/ successfully flashed the ROM and got the rooted JB.
my replacement tab came with VRALJ1 4.0.4 and I was able to get there :/ grr... let me finish with this zip and we'll see if it's better
Re: [OTA][SCH-I705][2013-03-15] VRBLL2 Jellybean 4.1.2 OTA Rooted
My sch-i705 is also rebooting. Any chance we need a secure boot loader with this version?
Sent from my ADR6425LVW using xda app-developers app
Hey, I bring to you, TeamWin Recovery Project or commonly known as TWRP for your N5100, N5110 and N5120. Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'xperiacle' and 'GSLEON3' for giving me the stock recoveries and kernels for N51XX and Teamwin for creating this recovery. Flash with Odin or via a already installed custom recovery.
Works perfectly now. OP will only be updated with stable releases, everything else will be floating around the thread.
I have provided the stock recovery if you encounter any issues, you can always flash back.
Downloads:
N5100 / N5110
Release #3: ODIN | ZIP
Stock Recovery: http://d-h.st/tHx
N5120
Release #3: ODIN
Stock Recovery: Soon enough
Changelog:
Code:
[I][U]Release #3[/U][/I]
Updated to TWRP 2.6 (re) [cant call it 2.6 as its not complete by its devs yet]
Cache wipe fixed
N5120 support
Backup compression fixed
Code:
[I][U]Release #2[/U][/I]
Updated to TWRP 2.6
Fixed partition names
Attempt to fix compression
[I][U]Release #1[/U][/I]
Fixed external sdcard
Added modem and efs backup
Removed touch event logging
1st stable release
[COLOR="Red"]<-- Experimentals -->[/COLOR]
[I][U]Experimental #7[/U][/I]
swap X/Y axis
flip Y axis
revert gerrit code review (teamwin-600)
[I][U]Experimental #6[/U][/I]
flipped X axis mapping
flipped Y axis mapping
[I][U]Experimental #5[/U][/I]
Boot fix for devices with install-recovery.sh still present in system
[I][U]Experimental #4[/U][/I]
Touch issues addressed (fail)
[I][U]Experimental #3[/U][/I]
Boot fix (again)
touch issue fix implemented from #2 (failed)
[I][U]Experimental #2[/U][/I]
Touch issues fixed (attempt)
[I][U]Experimental #1[/U][/I]
(info: no longer preview release (public))
display issue fixed
Thanks for your hard work sir trying this when i get home
Downloaded and flashed the newest TWRP. Visually it is perfect but the touch did not work properly. I succeeded in wiping my Note data by mistake due to the touch problems. Some of the targets work but some are mixed up. Sorry I can't get you a logcat. Thanks for getting us where we are though. I feel we are almost there. If someone with better adb skills can try it and get you more info think we will all appreciate it. As an aside I did get CWM EX#3 installed, I had a bad download the first time and that is why I didn't get a recovery img. I much prefer the TWRP if we can get the final bugs out.
Sorry about your rom wipe. but thanks for reporting, ill take a look into the touch issues.
for recovery.log, if you'd want to, download the SDK (google it), if on windows then extract the zip and open up tools, then hold shift and right click and hit open terminal window here (may ahve a different title). then connect device to laptop and do this in the cmd window that opened up: adb pull /tmp/recovery.log . Thats about it, you can find the recovery.log in the folder where you extracted sdk/tools
emwno said:
Sorry about your rom wipe. but thanks for reporting, ill take a look into the touch issues.
for recovery.log, if you'd want to, download the SDK (google it), if on windows then extract the zip and open up tools, then hold shift and right click and hit open terminal window here (may ahve a different title). then connect device to laptop and do this in the cmd window that opened up: adb pull /tmp/recovery.log . Thats about it, you can find the recovery.log in the folder where you extracted sdk/tools
Click to expand...
Click to collapse
good job may i ask if you have the partition table for the 5110 and the 5100? i posted in general the instructions on how to get it but no one has replied lol working on a little something for everyone, also the note10.1 currently has the same bugs as he was describing above with twrp
emwno said:
Sorry about your rom wipe. but thanks for reporting, ill take a look into the touch issues.
for recovery.log, if you'd want to, download the SDK (google it), if on windows then extract the zip and open up tools, then hold shift and right click and hit open terminal window here (may ahve a different title). then connect device to laptop and do this in the cmd window that opened up: adb pull /tmp/recovery.log . Thats about it, you can find the recovery.log in the folder where you extracted sdk/tools
Click to expand...
Click to collapse
Emwno, your work on the CWM got everything started and resulted in a working CWM Recovery. I hope you continue to try to get the TWRP working since it has many fans. I set up my Note again and made a nandroid with the Ex#4 CWM which appears to be working well.
I believe I speak for many of us who thank you for your efforts.
beanstown106 said:
good job may i ask if you have the partition table for the 5110 and the 5100? i posted in general the instructions on how to get it but no one has replied lol working on a little something for everyone, also the note10.1 currently has the same bugs as he was describing above with twrp
Click to expand...
Click to collapse
looks like you got your answer.
rfb813 said:
Emwno, your work on the CWM got everything started and resulted in a working CWM Recovery. I hope you continue to try to get the TWRP working since it has many fans. I set up my Note again and made a nandroid with the Ex#4 CWM which appears to be working well.
I believe I speak for many of us who thank you for your efforts.
Click to expand...
Click to collapse
I dont really understand why those touch input issues occur. But yeah now that the n51xx has a wokring recovery. onto cm10.1
Thank you for sharing your hard work, glad to see progress being made.
Sent from my GT-N5110 using Xparent Skyblue Tapatalk 2
EDIT: Nevermind what i said previously. What i need you people to do is:
1. Take a look at the TWRP layout (Dont touch anything yet)
2. Now try tapping on the 'Install' icon and tell me which menu you end up in
3. Reboot to recovery
4. Finally try tapping the icon of the menu, where you were taken instead of 'Install'
5. Check if you now ended up in the 'Install' menu
Click to expand...
Click to collapse
So, found a way to get twrp to work, credits to dees_troy for pointing me in the right direction. Anyways for this to be done, ill be needing the device in hand (100/400) or a full time tester. So if your willing, take your pick
Uploading the New version of TWRP. Universal for 5110 and 5100 (excluded specifics). Try flashing that and let me know if touch works.
EDIT: new version online! test and report.
emwno said:
Uploading the New version of TWRP. Universal for 5110 and 5100 (excluded specifics). Try flashing that and let me know if touch works.
EDIT: new version online! test and report.
Click to expand...
Click to collapse
Sorry emwno,does not boot into recovery,stays stuck on the Samsung Note 8 screen so i flashed cwm recovery back on.
ktmman said:
Sorry emwno,does not boot into recovery,stays stuck on the Samsung Note 8 screen so i flashed cwm recovery back on.
Click to expand...
Click to collapse
State device. Ill try to make a new version when home
emwno said:
State device. Ill try to make a new version when home
Click to expand...
Click to collapse
5110
Uploading new build, if this one boots to recovery, it should most probably fix the touch issues.
EDIT: up
emwno said:
Uploading new build, if this one boots to recovery, it should most probably fix the touch issues.
EDIT: up
Click to expand...
Click to collapse
Flashed the newest TWRP and it booted into recovery but the touch issues are still there, When I touched install it went to wipe. The others did not respond to touch. I had to reflash CWM.
Thanks
Ill build a new version after today's paper. Swapping the touch mappings
I Think for MY Gtab 2 7". Someone had us Touch Several Specific Points In some sort of Diag area of TWRP to get mappIng data. And then took our output and fixed Accordingly. I'll see f i can dig up the Post.
Sent from my GT-N5110 using xda premium
I think ill just wait till I have the device my self. As I have 0-500 values I need to test to check which one will work for this device. (350/400)
I tried it today in my Note 8 Wifi and had the same touch problems... hope you can fix it soon, i really like your work
Hey guys, new to the forum but been lurking around and trying different roms, it's my first time using TWRP and I want to flash back to stock. It seems like every time I try to flash it's telling me it's failed.
pipicalsi said:
Hey guys, new to the forum but been lurking around and trying different roms, it's my first time using TWRP and I want to flash back to stock. It seems like every time I try to flash it's telling me it's failed.
Click to expand...
Click to collapse
Did you try to re-download the file?
meekrawb said:
Did you try to re-download the file?
Click to expand...
Click to collapse
I have and it's still telling me it's failed.
pipicalsi said:
I have and it's still telling me it's failed.
Click to expand...
Click to collapse
try installing twrp again
ReckYoChips said:
try installing twrp again
Click to expand...
Click to collapse
How can I do that?
pipicalsi said:
I have and it's still telling me it's failed.
Click to expand...
Click to collapse
Are you downloading it with your phone? Download to your PC and move it to your phone.
was enticts
meekrawb said:
Are you downloading it with your phone? Download to your PC and move it to your phone.
Click to expand...
Click to collapse
I just did that and did a full wipe. It's still saying failed, I can't seem to find out what's the problem. Only having issue flashing to stock but everything else seems to be fine.
good luck with that. best thing I can suggest is try some different button combos. try a different order of operations some how. in twrp, full wipe, system reset, then reboot back into recovery, another wipe /reset and then flash. that's the extent of my knowledge. you said you redownloaded the stock files to flash...maybe find a different place to download it from, could have downloaded a bad file twice?
Are you using the one from the wiki? I just tried it with TWRP 2.5.0.0 and it worked fine.
meekrawb said:
Are you using the one from the wiki? I just tried it with TWRP 2.5.0.0 and it worked fine.
Click to expand...
Click to collapse
Yeah that's where I downloaded the file and I'm also using TWRP v2.5.0.0
I don't really know how to take a screenshot in recovery but I'll type in what it says.
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/external_sd/uvlg3.flash2sotck.zip'.
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sd/uvlg3.flashtostock.zip'.
Updating partition details...
At this point it'll say Zip install Complete
But the word Failed is written in Red underneath the Home icon.
Hope this helps. Also when I try to flash peach sunrise, it's also giving me the same problem! Is there an alternative way to flash2stock?
Any help would be much appreciated! Thank you for you time guys.
You are probably going to have to use Odin to flash stock. It is in the wiki.
If you do need it, I posted a copy of Odin for our phone in this thread:
http://forum.xda-developers.com/showthread.php?t=2307264
You should probably try to Odin flash TWRP first and see if that fixes it.
http://forum.xda-developers.com/showpost.php?p=41869680&postcount=13
Warning: Odin can damage your phone if used improperly. I will walk you through if you need it.
meekrawb said:
You are probably going to have to use Odin to flash stock. It is in the wiki.
If you do need it, I posted a copy of Odin for our phone in this thread:
http://forum.xda-developers.com/showthread.php?t=2307264
You should probably try to Odin flash TWRP first and see if that fixes it.
http://forum.xda-developers.com/showpost.php?p=41869680&postcount=13
Warning: Odin can damage your phone if used improperly. I will walk you through if you need it.
Click to expand...
Click to collapse
I've flashed using Odin before a while ago when my phone was bricked. I'll have to read this over again and give it a shot. I'll let you know if I need help, thank you so much for your time meek! I appreciate it, I'll let you know how it goes after flashing TWRP with Odin.
Reset your TWRP settings, also, try downloading with a different browser and try under linux. Some browsers and anti-virus have issues with android files and delete them without warning.
Thank you so much for your help guys! I got it to work by flashing using Odin. I'm having a little bit of an issue though, every time my phone dies it starts having problems with the external memory. Like for example, my phone dies and I try to open my camera it'll tell me "not enough space blah blah" and when I try to change the settings through the camera, it just force closes. Not only for the camera, also other apps that need external storage like waze. It won't let me use the GPS because there's no memory. Mind you, I have a 16gb sd card in the phone. Any fix for this situation?
Using AOIP Linaro ROM btw. I couldn't post at the original thread because of my low post count so I'm hoping I get some help here.
Thanks you guys for the help! I really appreciate it.