Related
Hi, I am a new user on the xda forums (although I have read countless threads). I am a little confused as to what I should do with my captivate. I am debating between flashing 2.3 (to which I see only one drawback: there are not many stable roms out there and flashing them can be a struggle as my recovery image is not very functional in 2.3), or sticking to 2.2 and finding a nice rom that I enjoy (only drawback: it's 2.2 and not 2.3! ) So can anyone advise what to do? Thanks in advance!
My opinion: If you're new to flashing, flash a 2.2 rom. There's less chance of things going truly wrong (less true brick chances). Then, once you feel comfortable flashing (and know a little more), make the jump to 2.3.
I'd say go with 2.2, unless you are feeling brave. CM7 and MIUI (both 2.3) have pretty short battery life. Some people talk about having good battery life, but I think those people are in the minority.
thanks for the quick responses. Well I have flashed roms before (not really new to it), it's just that I haven't done it through the clockwork mod recovery because I am not able perform functions in recovery mode when running 2.3 (which is what I am currently running). Is there a stable 2.3 recovery image for the captivate out there? (none of the options in rom manager seem to work for me...) Have others been able to successfully use rom manager on a Captivate running 2.3?? If so, could someone please provide detailed instructions on how to do so?
What are you NOT able to do in recovery mode for 2.3 that you CAN do in 2.2? I mean I have been from 2.1>2.2> 2.3.4>2.3.3>2.3.4 via clockworkmod without any issues.
What exactly are you trying/wanting to do? If you are just trying to change roms? A little more info might be helpful.
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
well yea basically I can't use rom manager to flash a clockwork mod recovery that is functional on my captivate. This hampers me from flashing roms through recovery. Could someone just walk me through the installation of rom manager on a 2.3 stock captivate and then the flshing of a recovery image (chosing the proper model etc.)? (I think the issue may have something to do with unsigned packages or something like that?)
sharma_akarsh said:
well yea basically I can't use rom manager to flash a clockwork mod recovery that is functional on my captivate. This hampers me from flashing roms through recovery. Could someone just walk me through the installation of rom manager on a 2.3 stock captivate and then the flshing of a recovery image (chosing the proper model etc.)? (I think the issue may have something to do with unsigned packages or something like that?)
Click to expand...
Click to collapse
pretty sure there is a ton of info on here about that exact error.......in fact there is a freakin sticky on it.
you cant use ROM manager to flash recovery on 2.2 or 2.3....without getting around that error
hint: that error makes a really good search
Pirateghost said:
pretty sure there is a ton of info on here about that exact error.......in fact there is a freakin sticky on it.
you cant use ROM manager to flash recovery on 2.2 or 2.3....without getting around that error
hint: that error makes a really good search
Click to expand...
Click to collapse
okay well I found a method a while back involving the replacement of the recovery in the system/bin folder with a moded 3e recovery.... (not to change topic) but would you recommend soing that and then using cwm, or should i try this new bootloader stuff with Odin (or whatever is needed to flash roms through odin)?
sharma_akarsh said:
okay well I found a method a while back involving the replacement of the recovery in the system/bin folder with a moded 3e recovery.... (not to change topic) but would you recommend soing that and then using cwm, or should i try this new bootloader stuff with Odin (or whatever is needed to flash roms through odin)?
Click to expand...
Click to collapse
you have some reading to do.
pick a rom that you want, flash it
2.2 and 2.3 will come with android recovery 3e. to get around signature verification error, you need to replace the recovery as you indicated
if you are flashing from 2.1/2.2 to 2.3 (excluding CM7 and MIUI) you will be required to flash bootloaders first before you can flash the 2.3 rom
aside from going from 2.1/2.2 to 2.3, there is no reason to flash bootloaders....
if you stick with 2.2 roms, as long as you take care of the 3e recovery, you use CWM....always
if you go to 2.3 roms, flash the bootloaders ONE TIME, then you can flash as often as you want,
Pirateghost said:
you have some reading to do.
pick a rom that you want, flash it
2.2 and 2.3 will come with android recovery 3e. to get around signature verification error, you need to replace the recovery as you indicated
if you are flashing from 2.1/2.2 to 2.3 (excluding CM7 and MIUI) you will be required to flash bootloaders first before you can flash the 2.3 rom
aside from going from 2.1/2.2 to 2.3, there is no reason to flash bootloaders....
if you stick with 2.2 roms, as long as you take care of the 3e recovery, you use CWM....always
if you go to 2.3 roms, flash the bootloaders ONE TIME, then you can flash as often as you want,
Click to expand...
Click to collapse
Ohhhh I see.... I don't think I clarified this, but I am currently on stock 2.3 using this method mentioined by: nakedninja42
I personally always remove my external memory and sim card before using odin. It is not needed as people will post but neither is doing master clear. I do these steps just to make sure I eliminate any possible issues that can occur during flashing.
1) Download Firmware from http://www.samfirmware.com/WEBPROTECT-samsungusa.htm
2) Flash back to stock JF6 w/ odin one-click and did a master clear.
3) Flash Gingerbread KF1 using Odin (see image in post link for reference) http://forum.xda-developers.com/show...9&postcount=75
4) Flash fugu kernel http://forum.xda-developers.com/show....php?t=1010141 Look for the step two that says download odin or heimdall, select the ODIN (well the version your going to use).
5) Flash stock kernel (see post link) credit to lownox for helping me on that http://forum.xda-developers.com/show...&postcount=116
6) Settings>Applications> enable Unknown Sources (AT&T finally got something right)
7) Install busybox from market
8) ENJOY!
Click to expand...
Click to collapse
So from here, do I need to do anything additional with bootladers in order to flash other roms - how exactly do I flash roms from this point? Thanks!
if you are already on 2.3, then you already have the bootloaders. you dont need to do anything with odin or bootloaders to get a new rom on. bypass 3e recovery and use CWM... NOT ROM MANAGER, to flash your rom
Pirateghost said:
if you are already on 2.3, then you already have the bootloaders. you dont need to do anything with odin or bootloaders to get a new rom on. bypass 3e recovery and use CWM... NOT ROM MANAGER, to flash your rom
Click to expand...
Click to collapse
Sorry to sound extremely noobish... but I thought cwm was through rom-manager?? How do I go about flashing solely through cwm?
on the samsung galaxy s line, cwm is an update.zip file. all rom manager does is put an update.zip of itself on the /sdcard/
you dont need rom manager, just that update.zip. if you have bypassed 3e recovery, it will work.
Pirateghost said:
on the samsung galaxy s line, cwm is an update.zip file. all rom manager does is put an update.zip of itself on the /sdcard/
you dont need rom manager, just that update.zip. if you have bypassed 3e recovery, it will work.
Click to expand...
Click to collapse
o okay, that makes sense. I did see that update.zip file when using rom manager. So as I think you have said I already bypassed the 3e recovery because I am now on 2.3? So just find that update.zip file and everything will work through my recovery?
sharma_akarsh said:
o okay, that makes sense. I did see that update.zip file when using rom manager. So as I think you have said I already bypassed the 3e recovery because I am now on 2.3? So just find that update.zip file and everything will work through my recovery?
Click to expand...
Click to collapse
no. any time you use 'official' firmware and not a custom rom, you will get 3e recovery back to defaults. you will need to bypass it again
Pirateghost said:
no. any time you use 'official' firmware and not a custom rom, you will get 3e recovery back to defaults. you will need to bypass it again
Click to expand...
Click to collapse
yea okay that is what i have been trying to do with the replacing of the recovery... but that method does not seem to work. Do you have any other suggestions?
Nevermind I think I got it...
sharma_akarsh said:
yea okay that is what i have been trying to do with the replacing of the recovery... but that method does not seem to work. Do you have any other suggestions?
Click to expand...
Click to collapse
Do you just want to get CWM recovery somehow? If you already have GB BL flash a custom kernel using ODIN which has CWM. For how to flash GB try to see installation instructions from Apex
got it-thanks!
I have tried lately to flash ics rom on my rooted captivate which was running 2.2 stock froyo but I made two mistakes that made me fear that it was bricked
- I removed the CWM recovery folder from the internal sd card. As a result, when I reboot the phone, it starts as usual but get stucked in the Samsung galaxy S screen.
- Trying to fix that, I tried to install a custom recovery image using Heimdall suite and with the download mode, but after flashing it, the situation worsened (may be because it was destinated to android 2.3.) and when I rebooted the phone, I get tha At&t logo and then the screen becomes an assembly of colored lines.
The only good news is that I still can access the download mode. I did nothing else to not complicate the situation.
So do you think the phone is hard bricked now? And is there a solution to relieve it? Thank you in advance
medcast said:
I have tried lately to flash ics rom on my rooted captivate which was running 2.2 stock froyo but I made two mistakes that made me fear that it was bricked
- I removed the CWM recovery folder from the internal sd card. As a result, when I reboot the phone, it starts as usual but get stucked in the Samsung galaxy S screen.
- Trying to fix that, I tried to install a custom recovery image using Heimdall suite and with the download mode, but after flashing it, the situation worsened (may be because it was destinated to android 2.3.) and when I rebooted the phone, I get tha At&t logo and then the screen becomes an assembly of colored lines.
The only good news is that I still can access the download mode. I did nothing else to not complicate the situation.
So do you think the phone is hard bricked now? And is there a solution to relieve it? Thank you in advance
Click to expand...
Click to collapse
Basically, you get that screen cause you don't have the right bootloaders. Get stock KK4 with Odin (or Heimdall) one click. You'll find the sticky in the Dev section.
From there, you can flash Corn kernel to get root and after flash w/e ROM you'd like to run.
BWolf56 said:
Basically, you get that screen cause you don't have the right bootloaders. Get stock KK4 with Odin (or Heimdall) one click. You'll find the sticky in the Dev section.
From there, you can flash Corn kernel to get root and after flash w/e ROM you'd like to run.
Click to expand...
Click to collapse
I am sorry I was on travel the last two days
So, is this the thread that I need "[GB][2.3.5][KK4] Heimdall One Click Stock w/ or w/out BL's"? I am having some doubts because my original rom is a 2.2 stock rom. If not, could you please guide me to the right one?
medcast said:
I am sorry I was on travel the last two days
So, is this the thread that I need "[GB][2.3.5][KK4] Heimdall One Click Stock w/ or w/out BL's"? I am having some doubts because my original rom is a 2.2 stock rom. If not, could you please guide me to the right one?
Click to expand...
Click to collapse
Yes, that's what you need. You don't have the right BLs to run the ROM you flashed so you'll need to flash them (KK4 with BLs).
Sent from my SGH-I897 using xda app-developers app
Today I tried to update my phone to a new custom rom.
I followed the instructions of the threads and tried to get it to work.
Of course it didn't work or else I wouldn't be here right now asking for help.
Here's the current situation.
I am able to boot into download mode + recovery mode and also boot into cwmr and install a different kernel.
I used pc odin to install it each time and it does pass and the rom (i've tried installing a gingerbread rom so that I can try everything again) does install.
the problem is that it is currently stuck in a boot loop at the "Samsung galaxy note gt-N7000" screen.
I have looked up dr.ketan's posts and tried some too.
currently i am booting abyss note kernel 42cwt touch original. (I know for sure it is a workable kernel because I've been using it this whole time.
here's what i've done. please tell me what i've done wrong and the possible ways to reverse it.
1. backed up everything
2. went into recovery
3. factory reset/cache clear
4. use pc odin to install new kernel (since I was looking into switching to another kernel anyways)
5. use pc odin again to install gingerbread rom (I do get the green light saying it did get installed
6. phone auto reboots
7. it gets stuck at the boot loop like i have mentioned above
i will try to attach a few pictures of my note as soon as I can so you can see what's going on with it.
What rom is there on the phone now ? if you boot into recovery .. what recovery do you get now ? CWM or stock ardroid 3e recovery ?
nokiamodeln91 said:
What rom is there on the phone now ? if you boot into recovery .. what recovery do you get now ? CWM or stock ardroid 3e recovery ?
Click to expand...
Click to collapse
Right now it reboots to 3e recovery.
The rom that I tried to inject to it is currently a the stock gingerbread rom from dr. Ketans thread.
The rom that I had on it is the official ics rom for the hk region.
The rom that I wanted to inject to it was a custom jb rom that uses hydracore as a kernel.
Thanks!!
try installing a prerooted Gb rom or an ICS stock rom using PC odin.. if you choose ICS, after flash install a safe kernel..
nokiamodeln91 said:
try installing a prerooted Gb rom or an ICS stock rom using PC odin.. if you choose ICS, after flash install a safe kernel..
Click to expand...
Click to collapse
If I do a stock ics update can I just do it through kies or do I have to do it through pc odin? Also. Would abyss or hydracore considered as a safe kernel???
yes if kies can do it then good but at this situation i dont think. its better to use PC odin for now. yes both are safe kernels
nokiamodeln91 said:
yes if kies can do it then good but at this situation i dont think. its better to use PC odin for now. yes both are safe kernels
Click to expand...
Click to collapse
I've tried your suggestions...and it didn't seem to work out too well.
I am able to flash to different kernels and get in and out of different recovers and such, but ya...still no luck with running a rom.
Well I am not sure but I soft bricked my phone when I tried that Abyss Kernel. In my view Hydracore is safe. Philz is super safe.
Flash ICS which matches your region using Odin. If phone boots flash Philz, If not, then be ready to read a lot of stuff or get phone repaired.
asian_boi said:
I've tried your suggestions...and it didn't seem to work out too well.
I am able to flash to different kernels and get in and out of different recovers and such, but ya...still no luck with running a rom.
Click to expand...
Click to collapse
instead of flashing kernels. flash a complete rom using PC odin.
nokiamodeln91 said:
instead of flashing kernels. flash a complete rom using PC odin.
Click to expand...
Click to collapse
You have so much patience
Sent from my Amazon Kindle Fire using Tapatalk 2
the only thing i have...
Hey guys. my note seems to have cooperated and allowed me to flash a new rom and also a new kernel. Here's the catch though, now it's stuck in the samsung logo and won't boot beyond that. Any suggestions of what to do? I am continually searching on the forums to find a solution.
At least I'm happy to know it's not a brick that can't be fixed.
Thanks nokiamodeIn91 for your help so far. I really appreciate it.
which rom did you flash and which kernel? how?
He spent a lot of time helping you. Be sure to hit thanks button
Sent from my GT-N7000 using Tapatalk 2
I currently flashed the abyss note kernel 42 cw touch and I downloaded an old gb rom from sammobile .
Here's what I did.
1. Put my phone into download mode
2. Run as admin on PC Odin
3. Selected the Abyss kernel then flashed it.
4. Boot into the cmw, wiped cache then booted the phone into download mode again.
5. Then I installed the old GB Rom on to my phone and restarted it.
6. Phone starts, loads past the GT-N7000 logo and goes into the samsung boot logo.
7. Phone repeats the animation of the samsung logo a time or two then restarts on its own. This loops until the phone is completely drained. I know that the rom works because that was the rom that I used to root my phone. I definitely don't mind downloading another rom if I have to.
my current goal, if we can fix this, is to quickly just update to the official jb rom for n7000 and not play around with the rooting and such until I have even more time to learn more.
at least I know for sure my phone isn't hardbricked, I would imagine I have either missed a step or something that caused the problem.
I have read through the forum and I did come across one post talking about checking my phone's partition and such.
I got to be honest, I'm really not technically skilled enough at this point in time to dare to mess around with that type of thing yet especially with so much coding to make sense of it. (I know this is kind of dumb to say especially when I rooted my phone and screwed up this bad). More importantly, I don't even know for sure if I need to do a partition or not.
Please let me know what I did wrong and how I can fix it.
I got a question though (out of curiosity), how come there's no toolkit for the n7000 like the S3 and also the note 2???
this is the name of the old gb rom that I tried flashing.
N7000ZSKJ6_N7000OZSKJ6_N7000XXKJ6_HOME.tar
I actually have tried several other roms as well (from GB-JB, official and custom) and all of them so far has gotten to the samsung boot logo
I have read on the forums to try using Philz-cwm 6 kernel but I don't know if it'd solve my problem.
let me show you one of the threads I have read, if I dived into the wrong material let me know and I won't consider using it (or learn how to use it) for my current situation
http://forum.xda-developers.com/showthread.php?t=1661590&highlight=samsung+logo+bootloop&page=2
like I was saying before, I really have no experience in coding so all the things that really made near no sense to me. I understand the basic concept of what its trying to do it's just seems like a very unsafe method for me to try especially when I lack the necessary knowledge in this area of expertise.
did you flash the GB rom using the standard PIT file ?
also you could try with the 5 file flashing method from this thread
http://forum.xda-developers.com/showthread.php?t=1530501
Hello..
Why are you only wiping cache.
You should have done a factory reset on that step.
Sent from my GT-N7000000000 using Tapastalker 2
asf58967 said:
Hello..
Why are you only wiping cache.
You should have done a factory reset on that step.
Sent from my GT-N7000000000 using Tapastalker 2
Click to expand...
Click to collapse
Yeah true... should also format system..
**** if you can boot into recovery , do a facotry wipe now
Hi, I have trouble while installing 2.1 update with CWM recovery (can not install .zip file). I hear that we must use Stock Recovery to install Nokia update; I've installed many apps + been lazy for backup all their data files so I don't want to flash the Stock Rom. Is there any way to flash Stock Boot Recovery only?
I've found some .img files in RM-1013 Rom folder, their names are "user_boot.img" and "user_recovery.img",do these files handle Stock Boot + Stock Boot Recovery?
<sorry for my English>
kienbb said:
Hi, I have trouble while installing 2.1 update with CWM recovery (can not install .zip file). I hear that we must use Stock Recovery to install Nokia update; I've installed many apps + been lazy for backup all their data files so I don't want to flash the Stock Rom. Is there any way to flash Stock Boot Recovery only?
I've found some .img files in RM-1013 Rom folder, their names are "user_boot.img" and "user_recovery.img",do these files handle Stock Boot + Stock Boot Recovery?
<sorry for my English>
Click to expand...
Click to collapse
Yes, you can use user_recovery.img and flash it to your phone using fastboot.
I need your help
Dom3616 said:
Yes, you can use user_recovery.img and flash it to your phone using fastboot.
Click to expand...
Click to collapse
Thanks man :good:, I've updated to 2.1 but my X2 is unrooted now :crying: so I'm planning to update a custom file by modifying the 2.1 patch downloaded from Nokia. Although I've read many threads about modifying/creating a flashable .zip file (use Stock Boot Recovery to flash), I'm not be able to do it; it requires coding knowledge (editing scripts in META-INF, binary... blah blah) :crying:
Can you help or suggest me anything about this?
The link to patch file can be found in a catalog.xml file which would be deleted after update; I found this file in both phone memory and sd card while downloading patch file by using phone updater, it is attached below.
Here is the link to my patch file (signed with my product code)
h--ttp://download.update.nokia.com/public/p/d/fds_swupdate/1408/1518/4030/145209948/RM-1013_FOTA_2.0.0.11_2.1.0.11_059W0W0_001_001.diff.zip
My wish is I could install google apps and (maybe or not) keep the su binary to keep Device rooted by this method.
Sorry for bothering you, I'm just a curious user wants to understand my Android device and I know you're master at this :good:
Wating your reply Dom.
kienbb said:
Thanks man :good:, I've updated to 2.1 but my X2 is unrooted now :crying: so I'm planning to update a custom file by modifying the 2.1 patch downloaded from Nokia. Although I've read many threads about modifying/creating a flashable .zip file (use Stock Boot Recovery to flash), I'm not be able to do it; it requires coding knowledge (editing scripts in META-INF, binary... blah blah) :crying:
Can you help or suggest me anything about this?
The link to patch file can be found in a catalog.xml file which would be deleted after update; I found this file in both phone memory and sd card while downloading patch file by using phone updater, it is attached below.
Here is the link to my patch file (signed with my product code)
h--ttp://download.update.nokia.com/public/p/d/fds_swupdate/1408/1518/4030/145209948/RM-1013_FOTA_2.0.0.11_2.1.0.11_059W0W0_001_001.diff.zip
My wish is I could install google apps and (maybe or not) keep the su binary to keep Device rooted by this method.
Sorry for bothering you, I'm just a curious user wants to understand my Android device and I know you're master at this :good:
Wating your reply Dom.
Click to expand...
Click to collapse
I can help you with that. But why don't you update and then try the same method again to root? That'll be quite easy, my friend.
Because there is noway to root a 2.1 X2 now :crying:
Dom3616 said:
I can help you with that. But why don't you update and then try the same method again to root? That'll be quite easy, my friend.
Click to expand...
Click to collapse
I'm waiting for new root method and want to do some thing this time
It is so boring for me looking at a non-(saved)game X2 xD
I'd better downgrade to 2.0 and wait, ty Dom. :good:
kienbb said:
I'm waiting for new root method and want to do some thing this time
It is so boring for me looking at a non-(saved)game X2 xD
I'd better downgrade to 2.0 and wait, ty Dom. :good:
Click to expand...
Click to collapse
There is a much easier way. Flash CWM Recovery for X2 and flash any superuser recovery zip from the internet. Try it.
Thank you Dom but there is no hope for this 2.1 update
Dom3616 said:
There is a much easier way. Flash CWM Recovery for X2 and flash any superuser recovery zip from the internet. Try it.
Click to expand...
Click to collapse
Thers is a CWM Recovery works well on X2 2.0 but it doesnt work on 2.1 update.
I've tried to use adb to flash .img file but adb cant find my device :v. I've installed all X2 drivers, the phone is detected well, all components are installed but adb usb composite driver is not listed in device manager, I'm using Windows 7 Ultimate 64 bit.
I've tried connecting my device to a Windows 8 PC, after installing driver pack used on Win7 my X2 is detected well but adb usb composite driver is still not installed, Win 8 detects 1 new device more than in Win 7 but there is no driver for it in driver pack
I used Google Usb Driver pack (downloaded by SDK Manager) and Nokia X usb driver pack.
No hope for this 2.1 update :v
Now I'm reading about .zip files usable with Stock Recovery :crying:
kienbb said:
Thers is a CWM Recovery works well on X2 2.0 but it doesnt work on 2.1 update.
I've tried to use adb to flash .img file but adb cant find my device :v. I've installed all X2 drivers, the phone is detected well, all components are installed but adb usb composite driver is not listed in device manager, I'm using Windows 7 Ultimate 64 bit.
I've tried connecting my device to a Windows 8 PC, after installing driver pack used on Win7 my X2 is detected well but adb usb composite driver is still not installed, Win 8 detects 1 new device more than in Win 7 but there is no driver for it in driver pack
I used Google Usb Driver pack (downloaded by SDK Manager) and Nokia X usb driver pack.
No hope for this 2.1 update :v
Now I'm reading about .zip files usable with Stock Recovery :crying:
Click to expand...
Click to collapse
I know that issue. Basically, Nokia drivers havent been updated.
But there is a way. Send me the link to the device drivers for X2.
Next, Open Device Manager and you'll see a yellow exclamation mark beside your device name.
Open your device and click properties. Then goto Detail and search for Compatible IDs something.
Send me those IDs and I'll update the drivers for you.
Feel free to PM me.
U're sweet Dom
Dom3616 said:
Open Device Manager and you'll see a yellow exclamation mark beside your device name.
Click to expand...
Click to collapse
As I said my PC OS installed all components from driver pack (as it can) and doesn't see any new device (there's not any symbol in the device list manager :crying. I might switch to Windows 8 if want to see it (Win 7 sucks :v).
I thought about this way to root 2.1 X2:
1. Root it at 2.0
2. Back up Supersu with ZIPme (app from who creates Busybox + Rom Toolbox, I think it's safe :v) so I can use it with Stock Recovery
3. Unroot
4. Update to 2.1
5. Recover Supersu
Do you think it works?
If I could use adb, it wouldn't be this complex. Ty again Dom :good:
kienbb said:
As I said my PC OS installed all components from driver pack (as it can) and doesn't see any new device (there's not any symbol in the device list manager :crying. I might switch to Windows 8 if want to see it (Win 7 sucks :v).
I thought about this way to root 2.1 X2:
1. Root it at 2.0
2. Back up Supersu with ZIPme (app from who creates Busybox + Rom Toolbox, I think it's safe :v) so I can use it with Stock Recovery
3. Unroot
4. Update to 2.1
5. Recover Supersu
Do you think it works?
If I could use adb, it wouldn't be this complex. Ty again Dom :good:
Click to expand...
Click to collapse
I wouldnt advise you to try that. Many users have reported bricking when trying to root on 2.1.
I gonna do it
Dom3616 said:
I wouldnt advise you to try that. Many users have reported bricking when trying to root on 2.1.
Click to expand...
Click to collapse
I think it will work if files location doesn't change.
Gonna tell you later if I success
kienbb said:
I think it will work if files location doesn't change.
Gonna tell you later if I success
Click to expand...
Click to collapse
Sure do.
Hello Everyone,
I know this is an old tablet and mine works fine but there are so many apps i cannot run on it because it's so old.
For some reason when I go to recovery (power plus volume down) it only gives me options to install from cache or to install from SD card. My Tab doesn't have an SD card slot and I've tried many different things like putting the Google Apps file in an /sdcard folder but no luck. Maybe I need a better recovery that will allow me to install from OTA USB or from Internal storage, or directly from the PC.
I have never rooted a phone before or unlocked a bootloader, and maybe I'm missing a step, but no matter how many forum posts I check people seem to be able to run it from /sdcard which is simply not working for me.
Please help!
I've got the same issue here, and tried everything, from what you've said you've done to using command lines in adb fastboot, and nothing seem to bring me closer to write on the root of the device. Maybe with both of us asking here someone pops up to bring some light to this.
@saitar
Install the TWRP Recovery 2.8.7.0 or higher.
bescalan said:
Hello Everyone,
I know this is an old tablet and mine works fine but there are so many apps i cannot run on it because it's so old.
For some reason when I go to recovery (power plus volume down) it only gives me options to install from cache or to install from SD card. My Tab doesn't have an SD card slot and I've tried many different things like putting the Google Apps file in an /sdcard folder but no luck. Maybe I need a better recovery that will allow me to install from OTA USB or from Internal storage, or directly from the PC.
I have never rooted a phone before or unlocked a bootloader, and maybe I'm missing a step, but no matter how many forum posts I check people seem to be able to run it from /sdcard which is simply not working for me.
Please help!
Click to expand...
Click to collapse
I don't know if this is still an issue for you, but I went further as nobody seemed to see the post.
I used this TWRP recovery, then flashed the lollipop rom here. But I stopped at the gapps... the only one I was able to flash was this one, but the keyboard isn't showing up. I tried the complete compilation and the flashing failed due to lack of space, although the device was plenty of it...
bierma32 said:
@saitar
Install the TWRP Recovery 2.8.7.0 or higher.
Click to expand...
Click to collapse
Thanks for replying. Yes, this is what I found out reading in xda and other forums, as the recovery I mentioned above is the 2.7.1.0, but is there a 2.8 recovery for the Tab 8.9, or should we be able to update the 2.7 to 2.8 without problems? Edit: I noticed in your post signature you got a 3.0 version on your device... how?
@saitar
Here are the link for TWRP https://forum.xda-developers.com/ga...ev-testing-twrp-galaxy-tab-8-9-p7310-t3469987
You can update your TWRP with the ZIP file from your existing Recovery or with Odin and the *.Tar file.
bierma32 said:
@saitar
Herr are the link for TWRP https://forum.xda-developers.com/ga...ev-testing-twrp-galaxy-tab-8-9-p7310-t3469987
You can update your TWRP with the ZIP file Form your existing Recovery or with Odin and the *.Tar file.
Click to expand...
Click to collapse
You're the man! th tar file didin't work, but I was able to flash the 3.0 TWRP, then flashed the Nougat version and the Gapps. Everything is working fine.
Thanks again!
Nougat update for i957?
Great to see the efforts here, kudos.
A naive question, whether this is going to work on my i957 currently on 4.0.4 ICS? If no, any recommendations for any latest ROM for i957? Being on 4.0.4, a number of apps have started causing issues, support not being available.
If there's another thread I should post on, pls suggest the same.
Thx
Mads
Recover using ODIN n with official firmware
bescalan said:
Hello Everyone,
I know this is an old tablet and mine works fine but there are so many apps i cannot run on it because it's so old.
For some reason when I go to recovery (power plus volume down) it only gives me options to install from cache or to install from SD card. My Tab doesn't have an SD card slot and I've tried many different things like putting the Google Apps file in an /sdcard folder but no luck. Maybe I need a better recovery that will allow me to install from OTA USB or from Internal storage, or directly from the PC.
I have never rooted a phone before or unlocked a bootloader, and maybe I'm missing a step, but no matter how many forum posts I check people seem to be able to run it from /sdcard which is simply not working for me.
Please help!
Click to expand...
Click to collapse
DEAR FRIEND,
recover your Tab using ODIN apk in PC.
install the Odin 1.13 or upto u at odindownload. COM
enter the recovery mode - Downloading
insert this firmware At NERDSCHALK WEBSITE using keyword on google ROM SAMSUNG TAB 8.9 FIRMWARE
follow the step of using ODIN ,
u will your phone flashed into that ORIGINAL version.
I HOPE IT WILL HELP YOU.
REGARD JIU-JITSAN