Forum Home
Press F1
Thread ID: 127888	2012-11-20 01:33:00	Android Tablet query	linw (53)	Press F1

Post ID	Timestamp	Content	User
1313560	2012-11-20 01:33:00	Wondering if anyone can give me some advice. I have just bought two very keenly priced Samsung Galaxy 8.9 tabs (GT-P7310) that are on Android HC 3.2. There is no official NZ ICS update for these in spite of overseas versions being available. This is pretty pathetic but that's how it is. Everything I read says ICS is much faster/smoother etc than HC but I find mine run as well as I expected. In spite of my acceptance of HC 3.2 as it is, I would still like to upgrade, and have even considered the cm 10 JB rom. I am prepared to accept the risks of unofficial roms but I want a fallback to my current setup if things don't go well. Just can't find the correct NZ approved rom file for that. Perhaps I should just be patient and wait for Samsung to get off their proverbial - dunno. So, anyone got helpful info/opinions? Been there., done that? Cheers and TIA.	linw (53)
1313561	2012-11-20 02:19:00	I think you need something like ROM manager from the Google store to back up your rom. Then you have to root it, if it isnt rooted already. And you'll need the USB cable and you have to select debugging mode on that thing. To do it. I did the same as you (and others). I rooted this smartphone. And installed quite a few roms on it, inc some of the CM mod's. Most of them worked, but some also drained the battery faster (than the stock ROM that was on it). I was lucky, I managed to find the stock ROM online (I didn't know if it had NZ in it or not). But, Once I connected it to the PC, and copied the ROM to the SD card (I'm pretty sure you'll need one of these too). And reset it, the original / stock ROM was back on it	Speedy Gonzales (78)
1313562	2012-11-20 02:34:00	ROM Manager and root isn't required in order to flash a new ROM? I'm unsure if the Galaxy Tabs get flashed using Odin initially to put a custom recovery on it, as you do with the likes of the Galaxy S and Galaxy Nexus, but it probably does. However, there are a myriad of other device-specific guides out there that you can use, no worries. Risks? It's pretty tough to actually brick an Android phone. I've tried to intentionally brick my Galaxy S, couldn't do it, it was always recoverable. I've been there, done that, on a number of devices. Everything from the Asus Transformer, Nexus One, Galaxy S, Acer Iconia, Galaxy Nexus, HTC One X, Motorola Defy, and the Nexus 7, just to name a few ;-) By and large it's relatively painless, pretty much always reverseable back to a "standard" firmware, however usually people simply download an "official" version of the firmware from their respective manufacturer and then copy it across and flash it. The first flash on a device is always the most painful, but after that you can usually flash straight from a custom recovery such as ClockworkMod or TWRP. Jellybean is *well* worth the upgrade, the speed increase is MASSIVE. Give it a whirl, you can always post here if you get stuck :)	Chilling_Silence (9)
1313563	2012-11-20 02:49:00	On this you need both, or clockworkmod which flashes the new rom (once you select recovery mode, it goes to it). On this one, I had to copy whatever mod (in zip format) to the sd card, then point it to it after I had wiped the cache etc. So it'll boot after its installed the new rom According to this, you have to root the phone, before using ROM Manager (www.androidpolice.com)	Speedy Gonzales (78)
1313564	2012-11-20 03:04:00	Depending on the device, and the method for flashing a custom ROM, you *may* need to do those steps, but usually not :) You're also presuming that the only way to flash a ROM is via ROM Manager. You can usually install a custom recovery without root, it's from the custom recovery (CWM or TWRP) that you'll flash your ROM. This itself has no correlation to if you have root or not, as all actions are being performed outside of the OS. Having root access will help if you want a "one push to flash" sorta option, but in many cases it's simply easier to flash a custom ROM that comes pre-rooted.	Chilling_Silence (9)
1313565	2012-11-20 04:36:00	Thanks, guys . Well, it didn't take long to stuff it up! I installed ROM Manager and that went OK, except that it wanted to confirm the device and didn't have the Galaxy 8 . 9 as an option . It did have the 10 . 1 so I chose that . This was probably a stupid option . I ran ROM manager and told it to install CWM Recovery . That seemed to go OK . Next I selected 'Backup current ROM' . It then went black, came up with the Samsung Galaxy name for a short time, went black again and that was it . I can't get into Odin Recovery . I can select that mode but on pressing the Vol up to confirm selection, the screen just blacks out . I can't get it connected to Kies as the tab isn't powered on in any intelligent sense . It will go into Download mode but Kies won't link in that mode . Getting worried now, as with no SD card it is hard to see a force boot from a file on the card . I am googling but haven't found anything likely, yet .	linw (53)
1313566	2012-11-20 04:43:00	Take it back to the store and say its "just stopped working"	DeSade (984)
1313567	2012-11-20 04:56:00	Bit embarrassing! I'll see of there is an 'out' first!	linw (53)
1313568	2012-11-20 05:24:00	Use Odin while in Download mode to flash a good ROM that includes a custom recovery. It'll fix everything, Don't worry, you can pretty much always recover from these things :-) This is why I'm not a fan of flashing via ROM Manager. Not worth it. The original Galaxy S i9000 had similar issues, and I've done the exact same thing on the i9000 and i9000T... But yeah, stay calm and keep Googling :-)	Chilling_Silence (9)
1313569	2012-11-20 07:28:00	This is why I'm not a fan of flashing via ROM Manager. Not worth it. The original Galaxy S i9000 had similar issues, and I've done the exact same thing on the i9000 and i9000T... I tried the SuperNexus on my S3 but wi-fi wasn't working so reverted. What rom do you recommend Chill.	mikebartnz (21)
1 2 3