[Q] tab 8.9 upgrade problem. Please advise. - Galaxy Tab 8.9 General

I need a bit of urgent advice if possible. Having waited patiently for Samsung to release ICS for the P7310 which has never appeared in the UK, I'm trying to flash to JB (latest AOSP version) from the stock 3.2.
I've installed CWMOD 5.5.0.4 ok, and copied the update rom and gapps to the root of the tab. I've gone into CWMOD recover mode, wipe/reset and then selected the rom to install. It starts the install, then fails with the system error 7 message (seems to be fairly common). It obviously started the install but now I don't seem to be able to boot the tab into 3.2 anymore, it just sits at the boot logo and doesn't get any further. I'm happy to try another ROM (maybe CM10), but I need to transfer it to the device first, and ofcourse I can't do this within windows at the moment. Odin still runs and can talk to the tab, but I'm a bit lost at the moment.
I'm a bit new to all this, so could really do with some help.

Flash the stock Rom.with Odin. You can find it at sammobile.com. it'll bring you back to stock.and.you can start over again. You're soft bricked right now.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

Cool. Thanks for that. I guess I just select the PDA option in Odin, and let it do its thing.
Any idea why this happens? I'd read a couple of threads about going from HC to ICS first, then to JB. Is this a requirement, or optional?

I'ver had similar problems finding a Rom that works on my i957. Never did find an ics that worked. I'm running jb from nrvate, but I think its specific to the i957. And, yes, flash just like you did the cm recovery.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

Really appreciate the replies. I've managed to get the tab back working under 3.2 (stock rom downloaded from SamFirmware), so that's a start. I still want to upgrade to JB if possible (or ICS if not). Am I likely to experience the same problem again? Is it worth going to ICS first? I've downloaded the stock US ICS rom, which i can flash using Odin. I can't see why this wouldn't work on a UK spec 8.9 wifi, but can anyone confirm if it does?
So, I'm back at square one, but really want to try and get this sorted.

Did you do a clean install when you tried to flash the jb Rom? I.e. factory reset, format/clear system and data. If not that probably is the problem. There should not be any benefit of flashing ics before jb. The one difference between the two is you most likely will have to flash a gapps (Google apps) package after the the jb flash. Not sure where you got the Rom, but the developer should have the gapp they recommend and instruction on how to do the flash. Every jb to Rom I've flashed has the gapps package flashed after the Rom and before rebooting.
I'd stick with a Rom specific for your device. I hard bricked my phone with the wrong Rom once. The US Rom probably does not have the correct radio for.you in the UK. I only use WiFi so don't care too much if I have the right radio or.not.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
Did you do a clean install when you tried to flash the jb Rom? I.e. factory reset, format/clear system and data. If not that probably is the problem. There should not be any benefit of flashing ics before jb. The one difference between the two is you most likely will have to flash a gapps (Google apps) package after the the jb flash. Not sure where you got the Rom, but the developer should have the gapp they recommend and instruction on how to do the flash. Every jb to Rom I've flashed has the gapps package flashed after the Rom and before rebooting.
I'd stick with a Rom specific for your device. I hard bricked my phone with the wrong Rom once. The US Rom probably does not have the correct radio for.you in the UK. I only use WiFi so don't care too much if I have the right radio or.not.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
I've just tried again, and have hit the same problem, and have tried the AOSP rom and the CM10 rom this time. I did a wipe/factory reset beforehand, but the installer starts then just aborts with 'symlink: some symlinks failed' E:Error in /sdcard/<rom file name> (Status 7). Obviously the tab 8.9 doesn't have an sd card slot, but I thought the rom must be aware of this.
Where am I going wrong?

You might try to flash a different version of cwm I don't remember now how I found this link, but here is a link for Overcome_CWM_Recovery_v5.1.2.6_P73xx.tar
http://www.sendspace.com/file/507gjv
just flash in Odin, like the ROM itself (in PDA section)
I use twrp but don't know where to find a version for your p7310.
Have you tried a different Rom
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

You have a /sdcard directory despite the fact you have no physical external sdcard.
I had the same problem. Found this solution:
http://forum.xda-developers.com/showthread.php?t=1973712
tman24 said:
I've just tried again, and have hit the same problem, and have tried the AOSP rom and the CM10 rom this time. I did a wipe/factory reset beforehand, but the installer starts then just aborts with 'symlink: some symlinks failed' E:Error in /sdcard/<rom file name> (Status 7). Obviously the tab 8.9 doesn't have an sd card slot, but I thought the rom must be aware of this.
Where am I going wrong?
Click to expand...
Click to collapse

harry_fine said:
You have a /sdcard directory despite the fact you have no physical external sdcard.
I had the same problem. Found this solution:
http://forum.xda-developers.com/showthread.php?t=1973712
Click to expand...
Click to collapse
If reading that reply right, one specific stock rom does what's necessary, trouble is, that's a US stock rom, and I'm in the UK. Already had it confirmed that it wouldn't be good to install a US rom on a UK tab. Loads of people has flashed their tabs, so it can't be that difficult! I've just tried Overcome CwM v5.2.1.6 with the same AOSP and CM10 roms, but same error

Ok, silly question time, but does the tab need to be rooted to install these new roms successfully?

You don't need to be rooted, just the recovery installed. Not sure why you're having problems now other than I had a hell of a time getting a Rom installed too. I'd try a different Rom. I tried some yesterday and didn't get any of them to work well. At least you've learned how to recover from a soft brick. I've learned that lesson too, to many times!
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

I'd try to download CM10 again. As i see in the error message there is a problem with the zip, maybe caused by error in downloading?

tman24 said:
If reading that reply right, one specific stock rom does what's necessary, trouble is, that's a US stock rom, and I'm in the UK. Already had it confirmed that it wouldn't be good to install a US rom on a UK tab. Loads of people has flashed their tabs, so it can't be that difficult! I've just tried Overcome CwM v5.2.1.6 with the same AOSP and CM10 roms, but same error
Click to expand...
Click to collapse
Hi, dont know if this will help, but I have flashed the US ICS rom on my Swiss Tab 8.9, with no problems. There should be no issue with worrying about the wrong radio as stated previously, as the 7310 is the WIFI only model, so there should be no issue with 3G. The only thing which causes some issues is the screen flicker issue. If you flash the US gingerbread first, then the ICS, it seems to solve the issue. For mor info check out this thread http://forum.xda-developers.com/showthread.php?t=1573548&page=50
Good luck!

Aaarrgggh! Frustrating, now I'm just getting 'hardware id not found' when I connect the tab to the PC!!! I can browse the device in Windows, but of course, Odin won't connect. How difficult can this really be!
I've already uninstalled and re-installed the Samsung USB drivers, tried a different USB port etc, but same result.
As it stands, the tab is working, but on that horrible v3.2.

I might be getting somewhere, but nothing's easy! I have moved everything over to a laptop we have, and have gone through the whole process again. I installed CwM ok using Odin, copied over the AOSP beta13 for the 7310, and this time when I installed the ZIP, it said completed ok. Good so far.
I then rebooted, and while I see the Samsung logo, the screen then goes black and stays that way. I've left it ages, but it doesn't seem to get anywhere. I can still reboot it and get into download/recovery, so that's ok. Am I doing anything wrong? I did the wipe/reset beforehand, so It's not obvious why this is not working.

Quick update. I can get ICS running (CM9 works), so that's good. It does look like any JB rom (AOSP/CM10) just cause a blank screen on reboot, which is wierd. I've re-downloaded the ROM's just in case, but no dice. Install completes ok, and gapps reports no problems.

I often don't get a boot animation, just the black screen. Every once in awhile the animation comes back. Seems totally random. I'm using nravates jb Rom on the i957. Other than that it runs great.
Sent from my SGH-I727 using xda app-developers app

Related

Rom

Seen an alpha 3 ICS rom. Can I just download that and flash it over my current rom or does it habecto be done certain way. I've flashed before on my evo but this seems a little bit more complicated
Sent from my SPH-P100 using XDA App
I'd rather go the full procedure they describe within their thread - imho especially you have needs for clockworkmod. Found that to be a quite safe way for me.
I would I just don't have access to a pc. Does ICS run fine on your tablet. Is it worth it
Sent from my SPH-P100 using XDA App
Once you have CWM Recovery installed, getting the ICS Alpha on your tab is not difficult if it's listed as supported in the thread.
Only thing: This is an ALPHA build. That means many things are not functional. The build is aimed at developers/testers.
Having given a shot at it, this build is surely not a daily driver for someone who needs its tab to be functional and reliable. Many of those problems have work arounds however but since the tablet is not mostly used by myself, I did not take the risk of having it be unreliable...
In short: it should work and not eat your hamster... But it is not a fully functional rom yet, be prepared for some trouble... Be sure you know how to go back in case of trouble... and read instructions carefully
If you want a good ICS rom here ya go. FYI!!! THIS IS FOR CDMA TABS!!!
Get rooted and CWM'd via Rodderick's thread in our Development section.
From there do the following (all credit to JT from here on out)
Download http://k.22aaf3.com/jt1134/vzwtab/cwm-recovery-5.0.2.7.tar
Extract the contents. You will have two files zImage and recovery.bin
Odin these two files to your tab while your tab is plugged in to the PC and in Download mode. This will bring your clockworkmod up to 5.0.2.7 which is a must to install the rom I'm about to link.
Next go to this thread
http://rootzwiki.com/topic/11697-rom-cdma-aosp-ics-cm9-build-31-0104-x-2/
At the bottom of the first post download the 3.1 ROM the 3.1 Patch and the gapps files.
Once those are downloaded boot your tab up to normal operations and plug it into your PC again. Now transfer those three files to your tab.
Boot up into clockwork recovery wipe the cache, dalvik, and do a factory data reset. Then flash the 3.1 file first, then flash the 3.1 Patch, then flash the gapps files.
If everything says it installed correctly the only things that won't be working are camera (which it does work in panorama mode) and possibly 3G. (Never tested 3G as I only use wifi).
Can you please post pictures and how can I check which cwm I already have? If I already have 5.0 can I just go ahead and flash? One more thing is this a whole new ICS or the ones going around. Thank you much
So I checked and I got 4.0 cwm. With that said. I don't have access to a pc. Is there any other way to upgrade to 5.0 cwm? PLEASE someone reply with yes. I'm getting bored with this andcwpuld like to try ICS. Thanks
rjumawan said:
So I checked and I got 4.0 cwm. With that said. I don't have access to a pc. Is there any other way to upgrade to 5.0 cwm? PLEASE someone reply with yes. I'm getting bored with this andcwpuld like to try ICS. Thanks
Click to expand...
Click to collapse
Without access to a PC I think you are making life very difficult for yourself.
You do not state what Tab you have; below I linked to the install for the P1010 only...I did this for reference because you will see it required Odin to flash it i.e. access to a PC.
http://forum.xda-developers.com/showpost.php?p=20195348&postcount=1
Thank for the reply. Yeah I know it makes it, harder just seeing if there was a way around it. I'm playing with the sprint galaxy tab. Not much to play with out there for it.

Tried going from 2.2 Andrometa3 to ICS ROM 4.0.3. Houston we have a problem.

I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.
LOL OOPS thought i was in the dev section.... ignore..help below.
xCaptivateRx said:
I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.
Click to expand...
Click to collapse
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.
TRusselo said:
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.
Click to expand...
Click to collapse
Very good responce...however after odin3 one clicking back to stock 2.1 eclair, I lost my clockwork mod folder that was on the internal SD, of course. Rookie mistake, I should've definately copied it on to the external SD card. Thanks for informing me of proper terminology. Also, after downloading rom manager and flashing, booting recovery, I can only access cwm through the rom manager, the three button fix doesn't work.
Why was this moved? I posted in general..
because you have a question/problem
rom manager is only used with 2.1 (for captivate). doesnt work on 2.2 or 2.3.X or 4.0.X
in all newer versions of android we "bake" cwm into the custom kernels we package into the custom roms. so there is no stock recovery and you dont need the update.zip.
dunno why you would flash all the way back to 2.1... EWWW.
in the dev section there is a sticky called odin master collection. use a newer stock rom. the master collection also has stocks versions, pre-packcaged with a custom cwm kernel so you can skip a step of getting it after going back to stock.
Do we know why this happened in the first place? Incompatible kernel? Is there a guide somewhere for moving from GB to ICS?
Sent from my SGH-I897 using XDA App
I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.
Do you not have to flash back to 2.1 after having these problems? Right now my phone is at the soft brick screen, no button combo working. Not recognized by the computer either. I'm heading out to radio shack and make a USB jig in a bit. I'd love to just flash straight up to a gingerbread ROM if I can possibly get this thing in download mode. Anybody help a brotha out!
Edit: the sim is not activated, I just run it off Wi-Fi because big red is my carrier. This is my development phone. So I can't just KIES update to whatever the newest is.
Sent from my DROID X2 using XDA App
Any firmware should work, no need to go all the way to eclair...just flash gingerbread.
Don't think its been mentioned yet but when going from 2.2 to ICS, you have to flash the rom twice to get out of the bootloops. Sounds like you were at that point but when you flashed your nandroid instead of the ICS rom again, your phone must not have liked it.
aww.W.T.F? said:
I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.
Click to expand...
Click to collapse
Not all ICS ROM's require GB bootloaders. I ran THS, and am now on vibranturk's AOKP and I came straight from 2.1
I think the issue was you're supposed to flash them twice. Well that fixed it for me. I dkbhave the gingerbread boot loaders now though
Sent from my SGH-I897 using xda premium
I went from bone stock Froyo 2.2 straight to THS ICS with no problems whatsoever. So some ICS Roms doesn't need GB bootloaders.
Sent from my SGH-I897 using xda premium
I'm on the same situation as the original poster: I'm on andromeda3 and now I want to upgrade to ICS. Right now my captivate has cwm 2.5.1.2 can I flash any ICS mod from there or do I need to do something else?
See this.... TRusselo's "Guide..." that is a Stickied Thread in the Q & A Forum.
I believe u will need the Gingerbread Bootloaders...
Sent from my SAMSUNG-SGH-I777 using xda premium

SGH-T849 updated to a GT-P1000 and now ?

I hope someone can help me please.
I have my SGH-T849 (America T-Mobile) updated to a GT-P1000. Firmware version: 2.3.3 Build number: Gingerbread. XXJQ1
Now I want to go to Overcome_7_Series_v 4.1.0.
But when I transfer the file to my tap, and I get my usb out to go to cwm to the file Overcome_7_Series_v 4.1.0, the file is no longer to be found on my GT-P1000.
So can anyone tell me what I'm doing wrong?.
Have been a few days working on it , but cant get it to work.
Hope you forgif my pour english i think its the age. :crying:
I use translating from dutch to english.
elvis3
The easiest is to put your file in an external SD card.
It is so cheap nowadays.
Sent from my GT-P1000 using xda app-developers app
In any case, thanks for the comment, I am very happy with it.
I now that I am very close, but need that little help.
I thought it could only work from the internal sd.
I did what you said, but now the tab in the startup screen hangs, and a voice says restore operation.
Is that oke?.
The voice was only in flashing overcome kernel 4.0 , was never when flashing Rom.
Not sure what happens in your case. Redo it again?
Sent from my GT-N7100 using xda app-developers app
Back to firmware version: 2.3.3 Build number: Gingerbread. XXJQ1
After overcome_Kernel_v4.0.0.tar ,the tab is hangging and not continue booting
up.
(page 11 from installation guide)
After installation from Overcome_7_Series_v 4.1.0, the tab is booting and then the voice is there again.?
I have read in one of your comment's on this forum. that it also possible that the internal sd card is broken, if he restore the old settings every time.
What is the best I can do?
Thanks for trying to help
Back to firmware version: 2.3.3 Build number: Gingerbread. XXJQ1
After overcome_Kernel_v4.0.0.tar ,the tab is hangging and not continue booting
up.
(page 11 from installation guide)
After installation from Overcome_7_Series_v 4.1.0, the tab is booting and then the voice is there again.?
I have read in one of your comment's on this forum. that it also possible that the internal sd card is broken, if he restore the old settings every time.
What is the best I can do?
Thanks for trying to help
Hmm. No sign of retaining your old data.
Could it be bad download?
Would you like to try one of the latest Rom?
Now that you have cwm, just get cm/AOKP or any Rom, and it's corresponding gapps, then flash the Rom using cwm 3 times, then flash gapps.
Reboot.
If that works, all good.
Sent from my GT-N7100 using xda app-developers app
"Would you like to try one of the latest Rom?"
Of course I want to try everything, but I don't know which rom is suitable for this tab.
"just get cm/AOKP or any Rom, and it's corresponding gapps"
Is this the latest rom?
Where can I find this rom?, you may have a link?.
I'm going to definitely try.
I really appreciate that you make time for my problem.
Two weeks ago, we where trying to restore the tab to factory settings .
This didn't work.
The tab kept coming back with the last settings. (not factory)
I report this only for your information, maybe with this information you have a better view of the problem or a different approach.
gr elvis3
Hmm... if factory reset and old settings still there, yes, seems like your NAND chip is failing afterall....
latest rom... hmm.. each dev has their latest rom.
Just don't assume they are Samsung official rom.
Yes, there is a latest CM9.1, there is a latest cm10.1, and the latest experimental cm10.2, and the latest AOKP SGT7.
Pick which latest you want to try.
But with the NAND issue, it may be difficult.
There Is nothing at all to do to the NAND story?
I'm going to at least try with the 3 time flash via external sd card.
If it workes then I'll let you certainly now.
I have one last question for you.
Have you ever heard of a super reset with the digit combination
*2767*3855#
Makes you feel good, if someone on the other side of the world is prepared to help you
For all the help so far, thank you very much.
Never heard of it yet. But I guess a flash with pit file is clean enough.
Sent from my GT-P1000 using xda app-developers app
I am still working on it, but no success.
grtz elvis3

Tab reboots before BML/MTD can even get started. Then no recovery

Ok guys,
I am not new to Android but this is really really starting to give me the sh!ts. I have no f#*%ing idea how many times I have gone and restocked this POS tab.
I follow the guide to a T for Overcome etc etc. I know all that.
I can flash CM10 through recovery from there and it completes oddly enough. However it does not boot at all. I have done this maybe 10 times. No boot. Just constant re-install of the kernel and Cyangen Bootanimation. I also have no recovery as soon as that happens and then I have to start ALL OVER AGAIN!!!!
Ok so I decide to try CM 9.1.0 stable. Surely this will allow something. Guess what? It doesn't even install. YES I have removed the lines from the updater script. I mean how stupid. If you don't even have a system for a getprop to querey of course it is going to fail.
Remove the lines, gets to BML/MTP and starts to process for maybe about 10-15 seconds and then reboots and becomes a brick
What in gods name am I missing here that isn't in the million and 1 guides I have already read and the conflicting opinions of people say 'flash CM10 straight after Overccome kernel' and 'No no no you need to be onn CM9 first' and I have even read 'No you need to flash CM7 first then from there you can flash CM10'
Like WTF?
Cant there just be a 100% true guide. For starters Overcome ROM guide only gets you to there, nothing more. There is no steps in between. There are only guides that assume that you have done the steps to get to Overcome ROM.
I am about to scour the internet now and see if I can find CM7 cause I am sick to death of restocking and starting from scratch on this stupid POS. I mean FFS I thought that this would be straight forward like when I updated my i9000 Galaxy S to ICS, but noooooooo nothing I have done gets the results of what people claim in the guides.
These are my steps
Odin
PIT = gt-p1000_mr.pit
PDA = GB_Stock_Safe_v5.tar
Modem = modem.bin (JK3 as per the guide)
reboot download - it does boot otherwise
Odin
PDA = CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
reboots into Gingerbread
reboot download again
Odin
PDA = Overcome_Kernel_v4.0.0.tar
Sexy voice does her sh!t (I thought that this was where we did BML to MTD but it's not its rfs to ext4 - thought I'd add that for anyone that has in the past like me had experience with doing this stuff before and needs a refresher).
Reboot into recovery and from here is anybodys guess?
I need the EXACT EXPLICIT DETAILS FROM THIS POINT!
Everything I try from here completely messes the P1000 and I have to start again.
CM10 - Flashes but doesn't boot - recovery updates but flashing anything else obviously kills it and I start again
Overcome ROM wipe - Flashes but exists the script before completing
CM9.1.0 - Flashes, gets to BML/MTD and quits - note Recovery is completely screwed after this point
CM7 - Yes I am about to try this. Please tell me why this is wrong and explain and I will listen. Please also advise all the other people out there with guides that are wrong to update them and include the important details that they have overlooked for people like myself.
Thanks
Overcome kernel converts rfs to ext4 but still in BML.
When you flash cm9 or cm10, flash it 3 times.
That is by selecting the zip. Flash it, it reboots to recovery (a new recovery, no longer overcome).
Flash zip again. Now it converts to MTD. It then reboots to recovery. (Many people think it is bootlooping. )
At this point flash zip again. Now it does the longer install.
Screen says a lot of thing about /system and stuff.
Let it finish and reboot to cm.
The weakness of most guides is that they never say 3 times.
The noobs thinks it is a bootloop without reading what the recovery is doing.
Sent from my GT-N7100 using xda app-developers app
priyana said:
Overcome kernel converts rfs to ext4 but still in BML.
When you flash cm9 or cm10, flash it 3 times.
That is by selecting the zip. Flash it, it reboots to recovery (a new recovery, no longer overcome).
Flash zip again. Now it converts to MTD. It then reboots to recovery. (Many people think it is bootlooping. )
At this point flash zip again. Now it does the longer install.
Screen says a lot of thing about /system and stuff.
Let it finish and reboot to cm.
The weakness of most guides is that they never say 3 times.
The noobs thinks it is a bootloop without reading what the recovery is doing.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
You may have missed the point where Recovery becomes unreachable the minute I flash CM9 the first time. After that I can no longer get recovery and device becomes a brick.
Jarmezrocks said:
CM9.1.0 - Flashes, gets to BML/MTD and quits - note Recovery is completely screwed after this point
Click to expand...
Click to collapse
If you can provide a link to a known 100% certain to work version of CM9 or any CM I would be greatly appreciated! I believe there is much confusion (and to be honest I got lost with so many different opinions about changes made to CM in their thread) as to what version is best to flash. I personally tried the latest CM of version 9.1.0 and the stable (to which there were two and I tried one but not the other?) and did not have any luck with either.
Look forward to hearing from you
Thanks for your reply mate :good:
Not sure why your cm9 gone bad.
Make sure you download the p1 variant and check the md5 sum of the file.
It has always been on with me.
Restock. Overcome kernel. Then flash cm 3 times.
Unless there is a hardware issue?
Sent from my GT-N7100 using xda app-developers app
priyana said:
Not sure why your cm9 gone bad.
Make sure you download the p1 variant and check the md5 sum of the file.
It has always been on with me.
Restock. Overcome kernel. Then flash cm 3 times.
Unless there is a hardware issue?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thats the thing though, I believe that CM 9 has changed several times since the beginning. Both the latest and stable didn't work. There is another stable version but really got put off the whole ordeal because I was reading so many posts of people confused as to which version they should be flashing and which one they made the stable version in the end.
Something else also thrown in was that some guys where flashing Overcome and not allowing conversion to ext4 and then upgrading to CM10?
Should flashing Overcome kernel over the top of standard Gingerbread allow the device to boot and run stock GB with ext4? How would this be different to running stock and using OCLF4 on stock kernel with CWM Recovery? Say CF root Recovery?
Sorry for all the questions but the device isn't mine and I am now looking for the simplest solution to making it run normal and stable. Seems like normal GB is so unstable its not funny! Is it normal to get random reboots on stock Gingerbread?
It is not normal for GB to reboot by itself. There must be something not right.
About overcome kernel on top of normal GB with ext4, yes that is possible to run it that way.
About allowing overcome kernel to convert to ext4, or not to allow that, it doesn't matter.
CM kernel will repartition the internal storage and everything will dissappear once a new partition scheme is in.
My suggestion is usually for people to not wait for overcome kernel to convert since it is not needed.
Sent from my GT-N7100 using xda app-developers app
Hey I got some good news!:good:
And....I will need you @priyana to update your OP for the Overcome ROM thread too, this will apply to all Australian P1000 Tabs I guess...well at least the Optus ones anyway.
Essentially the GB_Stock_Safe_v5.tar and gt-p1000_mr.pit are NOT safe like we are lead to believe....well not for the tablet I have just repaired. It is now running CM10 no problems!
I have created a new firmware package that incorporates a new PIT and various combos of files from the old GB_Stock_Safe_v5.tar and the standard firmware package.
What I found was flashing the completely stock firmware the device would not boot or function what so ever, which is really strange as most people would expect that standard firmware would at least be stable enough to use. Not even with the stock PIT or the gt-p1000_mr.pit.
You can down load the files here >>> GB_Stock_AUST_Jarmezrocks+P1.pit
This will have a firmware package and pit file combination that is suited to Australian P1000 TABS
Containing
GB_Stock_AUST_Jarmezrocks.tar
P1_add_hidden.pit
These are the ONLY files that will allow the Tab to boot, run and function normally. Before the thing was just so unstable you could barely do anything with it.
So from here Australian user who are having issues/problems with the Overcome ROM guide and getting continual reboots or bootloops should flash this package.
I will start a new thread in the dev section where it will be seen by others who are wanting to salvage their device.
That is good to hear.
BTW, the new overcome thread is sos_sifou's, not mine ?
Regarding the stock ROM, I remember that Stimpz0r, one of the great devs here, used to own a P1000 from optus and have no issue with overcome GB stock safe v5.
Makes me wonder if there are different variant of optus P1000.
Sent from my GT-P1000 using XDA Free mobile app
priyana said:
That is good to hear.
BTW, the new overcome thread is sos_sifou's, not mine ?
Regarding the stock ROM, I remember that Stimpz0r, one of the great devs here, used to own a P1000 from optus and have no issue with overcome GB stock safe v5.
Makes me wonder if there are different variant of optus P1000.
Sent from my GT-P1000 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry yeah you are right, you're just the heavy promoter of it (with good reason too eh?)
I will PM him and see if he can include it in the OP?
All I know is that without a doubt there was no way that package was saving this Tab, and that the one I posted most certainly did....so it would suggest to me that there is a difference between some models...I mean why else would they create a different firmware with a different .pit file? It makes no sense to do it without reason when really it is much easier to maintain the status-quo...don't you think?
Thanks for your valuable input too by the way. I really appreciate it :good:
can you re-upload ? i cannot download it

[Q] VERY worried about flashing miui rom and new bootloader.

I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Jeffril said:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Click to expand...
Click to collapse
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
NoDze said:
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
Click to expand...
Click to collapse
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Jeffril said:
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Click to expand...
Click to collapse
Okay, This is SFSP by @sgspluss which is a pretty fast, stable and battery-friendly slimmed down version of stock ICS. It is available for both Old and NewBL, so you might want to try that first. This is AIO Toolkit. I know that you've used it and bricked your phone, but try again, and for the love of God install the nvflash drivers because most people skip that part. You have to do it manually and if you're running Windows 8 you need to disable Driver Signature Verification. But yeah, you switch bootloaders with this.

Categories

Resources