Related
So I updated the MIUI on my Cappy from whatever I had before to 2.3.30 that is GB 2.3.7 from this location:
http://miuiandroid.com/community/threads/archived-miui-versions-captivate-gb.16558/
I didnt care for it so I downloaded SlimICS. I downloaded the base and the cappy essentials. Put them both on my internal sd. I factory reset, wiped data, cache and system and dalvic, just as i do for every phone i work on. I ran the SlimICS base and now it keeps rebooting and going back into recovery and doing this:
Finding update package...
Opening update package...
Installing update...
Slim ICS
Once Slim ICS pops up, it reboots and does it all over. I can yank the battery and manually go into recovery, but if i try to boot it up normal, it goes back into the loop. I am on CWM 5.0.2.7 also.
So what did i miss?
GB bootloaders most likely missing - flash 'em using Heimdall. And SlimICS doesn't have modem. So. Flash my ROM for a change may be.
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
And you flashed the base and the cappy essentials right? Not just the base
Sent from my SGH-I897 using xda premium
korockinout13 said:
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
Click to expand...
Click to collapse
trying to flash again just put it back in the loop. And I read that that does happen alot going from GB to ICS on the Cappy. But for Slim it didnt work.
Wdustin1 said:
And you flashed the base and the cappy essentials right? Not just the base
Click to expand...
Click to collapse
I never could get that far because it was the base that I started to install and it got bootlooped on, everytime it restarted, it went back into recovery and started to run the base again, and repeated boot loop. I read somewhere that teamhacksung's rom would get me over the GB to ICS bridge. This one here:
http://forum.xda-developers.com/showthread.php?t=1363760
It did the bootloop to, but when i yanked the battery and went back in and installed it a 2nd time, it didnt restart and installed correctly. After that I installed SlimICS. But I dont like it as much as i thought i would and now when i try to reinstall teamhacksung ROM, it errors out during the beggining of the installation. The MD5 is still fine. I dont think it likes the version of CWM recovery that SlimICS installed. I know CWMR went to an older version when i went from teamhacksung to SlimICS.
Flash glitch kernel first. Also, don't use the builds from that thread, it is old. Just flash the latest CM9 nightly
Swyped from my ICS Samsung Captivate
Stuck in A boot loop after flashing paranoid rom to cappy i897
I downloaded all needed files to internal SD just as the (how to upgrade the captivate i897 to Paranoid ROM said to do )
wipe data factory reset,wipe cache,selected install zip zip>package (pa_captivatemtd-1.99-13AUGUST2012.zip, md5sum: cc03bacf0f07a94bf25b482d64b94e63) then it started boot looping / att screen twice then android guy ,, then falling over with exclamation point in the middle of him , let it go considering options of 3 button combo weren't working ,, beside guide said 5-10 min to install then it made it to devil kernel installed gapps >> (gapps-jb-20120726-signed.zip, md5sum: f62cfe4a827202899919fd932d5246d7) now back in the boot loop again>>
i did make a nandroid backup but cant seem to get into cwm recovery or download mode . I did follow that guide to a tee.
any help or suggestions on this i would greatly appreciated if this post in wrong spot sry im new.
Also stuck in bootloop reverting to Gingerbread
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Reply Back.
HG_User said:
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Click to expand...
Click to collapse
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out. ??
---------- Post added at 06:38 PM ---------- Previous post was at 06:27 PM ----------
321321wrick said:
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out.
There also Ginger Bread Boot loaders Needed for it to start up Correctly - i personally don't know that much bout gingerbread rom i didn't like it as much as froyo WiFi issues'' the the stock odin should erase all info on your part thou 'e use Is OCD 1 i897UCJF6>lowercase work every time for me.
cept now because my usb is not able to charge phone or enter download mode or recovery which leaves jig option .
Click to expand...
Click to collapse
HG_User,
U can't go back to GB (or froyo/eclair) from CM, MIUI, ICS, JB, AOSP etc., etc. without using Odin or Heimdall---because of the different partitions used---Stock firmware is bml/rfs and all the AOSP etc etc are mtd/yaffs(2).
And u can only restore a backup when u r back running the base rom where u made the back up.
Use this...Stock i897ucKK4 GB 2.3.5 with or without bootloaders... http://forum.xda-developers.com/showthread.php?p=18370912
This kk4 should get u going. Then u can use Odin to flash Corn Kernel to get a cwm back...:thumbup:
Sent from my SGH-I897 using xda premium
... one step on the way: Back to Eclair
thanks for the advice. Ultimately, I decided I should use Odin 3 1-click to revert back to original (2.1 Eclair) firmware that I found on the first post of thread titled
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
This is a huge step forward because it makes my phone work, but it's also a step back in time to the early Eclair days.
Now my next step is to upgrade back to Gingerbread...
Edit: Thanks to all who pointed me in the right direction. I took the phone back to Eclair then used Samsung KiesMini (twice) to get it back to Gingerbread. After re-rooting and removing the AT&T Bloatware, it works fine again. I might try upgrading again to ICS or JB, but I didn't like Cyanogen 9 at all. Maybe I'm just used to the way AT&T polishes the UI, but Cyanogen didn't appeal at all. Now looking for a relatively polished but lightweight ICS or JB version... Also, it would be nice if when I upgrade it preserves the installed apps and what's on my home screens, but that seems unlikely going from AT&T-branded Gingerbread to an independent ICS or JB.
Hi guys,
I just need some short advise:
My dad flashed CM10 nightly a few days ago.
Before that he had a stock froyo rom (i don't know which version exactly) but with root and CWM.
Flashing CM10 worked but he had same bugs (baseband deleted, reboots every 10 minutes), so he flashed CM9 stable hopeing to get these things right. but it didn't, baseband was still gone. So he decided to restore his nandroid backup and go back to his froyo stock.
but that ended in a total disaster and the phone won't boot anymore. it is stuck at the white "Galaxy S" screen (before boot animation).
My dad said, that he tried to restore his backup a 2nd time. but he got many errors including "unknown volume for path /data"
He is a little bit frightened that he could brick his phone completely so he asked me for help.
Well, I don't know what to do besides flashing a stock gingerbread rom + kernel +baseband/modem with Odin.
Am I right with this? Or do you guys got some other advise for me.
thanks for help
try factory reset must done after restore
are you sure?
shouldn'd this be done before restore?
by doing a wipe, I would need to do 2 restors in order to keep my apps..
As the partition layout of CyanogenMod and stock are different, and thus stock partition layout is needed, you have to flash stock using Odin with pit512 and partition enabled. After that restore should work as well.
Besides: If baseband is missing in CM, try to flash a CM modem.
Sent from my GT-I9000 using xda app-developers app
Knobibrot said:
Well, I don't know what to do besides flashing a stock gingerbread rom + kernel +baseband/modem with Odin.
Am I right with this? Or do you guys got some other advise for me.
thanks for help
Click to expand...
Click to collapse
yes, you need to be on a GB 2.3.6 to upgrade to CM, so use a recovery kit , link below on MY android collections to recover and have a working phone before think moving on to CM
Galaxy S I9000 won't boot after cm10
Hi
Sorry if this is in the wrong place, I've searched, but have no phone now, it won't boot after installing CM10 28/12/2012. It was running, but I wanted to do a nand restore, it said it couldn't find the backup.
It now won't boot, it's stuck on the original Galaxy S GT-I9000 boot screen
This is really urgent (I know... like everything else)... can anyone help me PLEASE??
Thanks
Hello everyone;
I'm all new to this rooting and flashing thing, and I've been reading lots of tutorials and wikis, but still some questions remain:
1. I have a carrier-unlocked i9305t (It came with carrier software and the carrier logo shows up everytime I start the phone, but it is unlocked to any sim-card in my country). Should I flash the device to CyanogenMOD 11 (which is available for i9305, not i9305t), would my phone brick? Or, in other words, what are the main differences between i9305 and i9305t and can I install a custom ROM for i9305 in i9305t?
2. What's the difference between rooting and installing a custom recovery (such as TWRP)? Will installing a custom recovery give me root acces to my phone?
[edit] 2.1. So I've found that I can root my phone through a custom recovery by flashing a SuperSu (super user) file on it. Where can I find a safe SuperSu file for i9305t?
3. I've found this tutorial (can't post the link thanks to forum rules, sorry!) for installing CyanogenMOD 11 in i9305 in which there's no mention to rooting the device: the process consists of installing a custom recovery in the phone and, from there, flash the CyanogenMOD 11 ROM. Is this correct and safe?
Then again, thanks for the help and sorry for the bad english, I'm not a native speaker.
Cheers!
You can flash any i9305 tom on your phone. The t just has to do with the frequency bands your phone uses. All you need to do is flash a custom recovery. Root is included in cm 11 so you only need to flash that
Sent from my GT-I9305 using xda app-developers app
I just got a i9305T too, rooted, downloaded latest CM 11 nightly, when tried to intall zip it gave me Status 7 error, something about my device being a 'm0' and so not compartible.
I somehow wiped the stock system and can't mount USB with the TWRP... Now I'm downloading things so I can flash the stock and get back to square one.
What's going on and what can I do? Will I always have the latest CM Roms? Otherwise I'm somehow giving up this phone. Please help me.
vicastro said:
I just got a i9305T too, rooted, downloaded latest CM 11 nightly, when tried to intall zip it gave me Status 7 error, something about my device being a 'm0' and so not compartible.
I somehow wiped the stock system and can't mount USB with the TWRP... Now I'm downloading things so I can flash the stock and get back to square one.
What's going on and what can I do? Will I always have the latest CM Roms? Otherwise I'm somehow giving up this phone. Please help me.
Click to expand...
Click to collapse
I am a CM i9305T user here. For me, TWRP gives me error codes but then changing to ClockWorkMod recovery (latest version) solved error code 7. I used everything for i9305 for my i9305T phone and I have no problems. Try installing ClockWorkMod and flash CM + GApps.:laugh:
dummiexx3 said:
I am a CM i9305T user here. For me, TWRP gives me error codes but then changing to ClockWorkMod recovery (latest version) solved error code 7. I used everything for i9305 for my i9305T phone and I have no problems. Try installing ClockWorkMod and flash CM + GApps.:laugh:
Click to expand...
Click to collapse
I have an I9305T running CM11, I found I had to use the TWRP for the I9305, as the one for the I9305T (which is not yet updated to 2.7) did not allow me to flash CM. CM works fine for me, and I flashed the modem.bin that I extracted out of the latest 4.3 update from Telstra (Aus) which gives me the same LTE network speeds as I was getting on stock.
1. No you will not brick your phone... difference between 9305 and 9305T is in the frequencies that the phone uses to connect to your mobile operator...95% is the same for all..but for a few countries is not...they use different frequencies to connect the phone to the network...so samsung releases a version of the phone with T at the end.
2. A custom recovery is for installing new ROMs on the phone...installing new mods...and stuff...you have access to internal parts of the device... it has a interface with different option....combo to access it: volume up+home+power
I recommend CWM recovery.
Root access is like administrator on windows...by default you can't access system files on your phone and other stuff...for safety reasons...rooting your phone enables access to that stuff...but if you are a newbie better not to root.
2.1 Here is the package: download.chainfire.eu/supersu - but at the moment i'm writing this the site is dowm.
3. Yes...the order of installing CM11 is:
a) Back-up first in case of failure - i don't do this cause it takes a lot of time and i don't have anything important on the phone...i use cloud storage.
b) Install custom recovery and enter custom recovery
c) do a full wipe - factory reset + cache partition + dalvik cache
d) install ROM
e) install GApps.
Every ROM has it's own install instructions...just follow them.
Hi everybody,
just got an old yet effective SGS and I wanted root and get rid of touchwizz and all the crap from my carrier
I was unable to boot into DL mode, i tried everything, so I had to do it with adb reboot
I never had to use Odin to do my hacking with android so i'm not used to it but short story : I rename my rom.zip into rom rom.tar, it failed and all I have is this now :
https://www.dropbox.com/s/wk42jbmp33a3ftu/IMG_20140715_152917.jpg
Also I need to unsimlock, flashing a new rom will also do the trick right ?
thanks
What you just did is bricking your phone. It it was a zip file you need to install it from the recovery. Renaming it is not the way it works. I'm not sure if now you can fix it. Sorry, man
Sent from my GT-I9000 using XDA Premium 4 mobile app
Do you know what I can at least try?
If you can get into download mode:
Follow sections 2 and 3 in this guide.
If you can't:
Follow this guide and after that do what I sails to do if you have download mode.
Does 3-button-combo not work to get into the download mode?
(power & home & volume down)
tetakpatalked from Nexus 7 flo
so i tried the resistance thing but i was unable to find all of the part required so i bought one of these already done solution thingy
It worked, I'm now able to boot into DL mode
I also succesfully install a random 2.x rom from an unknown european carrier, no root, lots of crap installed, and simlocked
How do i get from that to my CM 11 rom ? (this time it's in .tar format via 7zip ^^')
I tried via Odin in PDA it says fail right away
what can I do ?
thanks fr all the answers guys
@Idealith simlock has nothing to do with the firmware.
You need now any root kernel for that firmware, it has to be compatible with the intiframs of your 2.x version and it will give you a custom recovery.
There you can flash first CM10.2 to get the modified partition sizes and KK ready recovery and after that you can flash CM11
IMHO, the new Mackay ICS 2014 rom based on CM9 is a lot faster than any KitKat and works better on the i9000
tetakpatalked from N7100
my question about the rom still applies cause this one is awful
but with what does it have to do then ?
EDIT : my browser didn't render the end of your answer
I'm afraid i'm not following though :/
I got my 2.3 rom to stop crashing
and I once boot into recovery mod idk how ..
I selected the 10.2 CM rom but it started rebooting over and over again
I'm really not following everything that is happening over here :/
Idealith said:
I got my 2.3 rom to stop crashing
and I once boot into recovery mod idk how ..
I selected the 10.2 CM rom but it started rebooting over and over again
I'm really not following everything that is happening over here :/
Click to expand...
Click to collapse
Hey, could you tell me which country you are at? I could then take a few steps to help you
PFFFFFFFFFFFFFFFFTTT, sent from my i9000
I am currently in France
last news : been able to reboot into CWM, I selected the mackay cm 9 based rom, it rebooted halfway thrugh only to reboot in TWRP (idk how, are both installed or is twrp in the rom too ???)
so i tried from twrp wiping everything before and it wen through, then on bot it told me it needed to factory reset, it never worker though
so now i can boot into CWM but can't access my sd card ...
thanks
Idealith said:
I am currently in France
last news : been able to reboot into CWM, I selected the mackay cm 9 based rom, it rebooted halfway thrugh only to reboot in TWRP (idk how, are both installed or is twrp in the rom too ???)
so i tried from twrp wiping everything before and it wen through, then on bot it told me it needed to factory reset, it never worker though
so now i can boot into CWM but can't access my sd card ...
thanks
Click to expand...
Click to collapse
It was perfectly normal behavior, as after flashing the zip from CM, it will in firat step upgrade your recovery to TWRP 2.2.2.0
As you have wiped already before, it would be perfectly fine to just flash the rom.zip in the new TWRP recovery, and your gapps right afterwards. The recovery upgrade is totally common on the i9000 as first step.
The i9000 can easily be unbricked by flashing a stock image with Odin.
tetakpatalked from Nexus 7 flo
tetakpatak said:
It was perfectly normal behavior, as after flashing the zip from CM, it will in firat step upgrade your recovery to TWRP 2.2.2.0
As you have wiped already before, it would be perfectly fine to just flash the rom.zip in the new TWRP recovery, and your gapps right afterwards. The recovery upgrade is totally common on the i9000 as first step.
The i9000 can easily be unbricked by flashing a stock image with Odin.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
I suppose my phone has been unbricked I made a 2.3 stock rom work
What i do now :
I flash the stock rom, go back to DL mode, flash the recovery, take the battery off, boot back in recovery, wipe everything ( do I really have to wipe system and all ?), select the ROM, nd once I'm in TWRP i reselect than same ROM
for the cm9 based mackay one it keep rebooting over and over again
for CM 10.2 it says the encryption failed and I need to factory reset, then nothing works
Idealith said:
I suppose my phone has been unbricked I made a 2.3 stock rom work
What i do now :
I flash the stock rom, go back to DL mode, flash the recovery, take the battery off, boot back in recovery, wipe everything ( do I really have to wipe system and all ?), select the ROM, nd once I'm in TWRP i reselect than same ROM
for the cm9 based mackay one it keep rebooting over and over again
for CM 10.2 it says the encryption failed and I need to factory reset, then nothing works
Click to expand...
Click to collapse
Yes, that would be correct procedure. To install CM9 you will have to format data, cache and dalvik cache.
If you have never had a JVU or JVZ firmware installed, it is likely that you still have a Froyo bootloader which could be reason of the problems with Android 4.xx
tetakpatalked from N7100
tetakpatak said:
Yes, that would be correct procedure. To install CM9 you will have to format data, cache and dalvik cache.
If you have never had a JVU or JVZ firmware installed, it is likely that you still have a Froyo bootloader which could be reason of the problems with Android 4.xx
tetakpatalked from N7100
Click to expand...
Click to collapse
and how do i get that bootloader set up ?
Idealith said:
and how do i get that bootloader set up ?
Click to expand...
Click to collapse
Either by flashing a whole JVU or JVZ stock firmware, or by flashing a bootloader only.
Check my sticky thread here under the same section (help & troubleshooting), I have described whole the procedure in the OP. I have even attached the files and also video is there: http://forum.xda-developers.com/showthread.php?t=2444308
Right point would be to do it first.
tetakpatalked from N7100
tetakpatak said:
Either by flashing a whole JVU or JVZ stock firmware, or by flashing a bootloader only.
Check my sticky thread here under the same section (help & troubleshooting), I have described whole the procedure in the OP. I have even attached the files and also video is there: http://forum.xda-developers.com/showthread.php?t=2444308
Right point would be to do it first.
tetakpatalked from N7100
Click to expand...
Click to collapse
thanks you so much i have now CM 10.2 running
would you know by any chance how to un simlock it ?
Idealith said:
thanks you so much i have now CM 10.2 running
would you know by any chance how to un simlock it ?
Click to expand...
Click to collapse
Ask your carrier, I assume the phone contract isn't new anymore (or expired) so you'll get unlock code for free. Here in Europe one can obtain the unlock code after 2 years for free.
Otherwise you can ask one of the online unlock services, it costs usually around 15-20$ to get the code
tetakpatalked from N7100
Idealith said:
so i tried the resistance thing but i was unable to find all of the part required so i bought one of these already done solution thingy
It worked, I'm now able to boot into DL mode
I also succesfully install a random 2.x rom from an unknown european carrier, no root, lots of crap installed, and simlocked
How do i get from that to my CM 11 rom ? (this time it's in .tar format via 7zip ^^')
I tried via Odin in PDA it says fail right away
what can I do ?
thanks fr all the answers guys
Click to expand...
Click to collapse
I'm glad that the JIG helped you (I know I'm late )
danielbe said:
I'm glad that the JIG helped you (I know I'm late )
Click to expand...
Click to collapse
yeah that worked like a charm
it was a good idea to buy it, i would have use the resistors so much
is there a more xda way to unlock it ? my carrier wants me to send the phone and have it unlock, they won't just provide the code :/
Okay so, I'm not exactly sure if this is the right place but I'll ask here anyway.
I took my old i9000 out of the closet and started playing around with it as I want to use it on my upcoming travel. To make long story short, I used to have a custom ROM on the phone all those years ago, but I am by no means an expert on the subject.
So what I have done so far today:
1. Returned the phone to stock ROM with Odin (XWJW1 or something, most recent anyway)
2. Rooted with Semaphore 2.7.4.
3. Installed Rom Manager and Superuser to check for CWM updates (which caused some sort of a verification error when I tried to boot to CWM through the app).
4. Downloaded the appopriate Slimkat and gapps and moved them into the internal storage.
But after the last step (and after wipe cache, format system etc) when I try to install the ROM, the bar on the screen progresses only slightly and after "Installing update..." it crashes (just goes black without any error messages) and gets stuck with just "Semaphore" on the screen.
I wish to update the phone to Slimkat 4.4.2. But what causes this problem, any ideas? Am I doing something wrong? If anyone can give any help that would be much appreciated!
PS. If I wanted to install for example Philz recovery, how am I supposed to do it when the file is .img?
Anyone?
I guess no one is using this phone anymore?
Yes, you are doing many things bit wrong.... (and many people use this phone still). I hope following will help you:
*recovery and kernel are sharing the same partition on the i9000 what means that you can't flash recovery separately
*make sure to backup your IMEI if still there
*flash first CM10.2 to get updated recovery for KitKat roms and to resize the system and data partitions to those used by all KitKat roms and reboot once into the system. You will need to flash trice to make it work (1. only warning of resizing to come and data lost- and status 7 abort, 2. only recovery update, 3. successful flashing)
*flash SlimKat and latest SlimGapps (addons) for 4.4.4
*PhilZ touch screen isn't yet working well on the i9000 but if you flash Mackay KK kernel, you can get beautiful TWRP touch recovery
tetakpatalked from Nexus 7 flo