Database Develop

[Q] Status 7 error on installing CM 10.1

Hi fellows,
I need your guidance and expert advice in resolving a situation, I have ran into recently. I was trying to install CM10.1 on my brother's galaxy Note GT-N7000 international version which was running official ICS 4.0.4.
Since, I had experience in installing different ROMs on my Galaxy S2, Nexus 7 and Xperia Arc so I was not worried about it being a big deal. So, I followed the procedure described in this page http://techgoneinsane.blogspot.com/2012/08/installing-cm10-on-galaxy-note-n7000.html?m=1 and used Odin and file from 'speedmod' to gain root access and flash CWM which was successful. Then, as planned, I tried update zip in the CWM recovery for CM10.1 nightly. But, I came across error 'Status 7' installation aborted. This was new to me, so I tried few things like 'factory reset', wipe data etc and even tried installing stock ROM ICS XXLRK which was previously installed but no avail. I tried several other ROMs like stable CM9 and other nightlies but no success. The phone is stuck on the boot Samsung logo with yellow triangle. However, I'm able to go in the recovery and download mode.
Upon doing couple of Google searches, I came to know, quite a number of people have faced this error by I couldn't understand the fix properly so can anyone of you please guide me for the solution. Thanks.
Your help will be greatly appreciated.

perceptorz said:
Hi fellows,
I need your guidance and expert advice in resolving a situation, I have ran into recently. I was trying to install CM10.1 on my brother's galaxy Note GT-N7000 international version which was running official ICS 4.0.4.
Since, I had experience in installing different ROMs on my Galaxy S2, Nexus 7 and Xperia Arc so I was not worried about it being a big deal. So, I followed the procedure described in this page http://techgoneinsane.blogspot.com/2012/08/installing-cm10-on-galaxy-note-n7000.html?m=1 and used Odin and file from 'speedmod' to gain root access and flash CWM which was successful. Then, as planned, I tried update zip in the CWM recovery for CM10.1 nightly. But, I came across error 'Status 7' installation aborted. This was new to me, so I tried few things like 'factory reset', wipe data etc and even tried installing stock ROM ICS XXLRK which was previously installed but no avail. I tried several other ROMs like stable CM9 and other nightlies but no success. The phone is stuck on the boot Samsung logo with yellow triangle. However, I'm able to go in the recovery and download mode.
Upon doing couple of Google searches, I came to know, quite a number of people have faced this error by I couldn't understand the fix properly so can anyone of you please guide me for the solution. Thanks.
Your help will be greatly appreciated.
Click to expand...
Click to collapse
If you are on Speedmod's recovery (which is safe), you can try this:
1) Download the latest CM10.1 kernel and save it to your SD card.
2) Flash it in Recovery (Install zip from sdcard > choose zip from sdcard), then reboot in the new Recovery (advanced > reboot recovery).
3) Do a full wipe (even format preload and system in "mounts")
3) Flash the latest CM10.1 build
4) Flash the 4.2.2 Gapps
5) Do a data wipe / factory reset
6) Reboot
You got a yellow triangle because you flashed an unofficial kernel through Odin. To get rid of it, use TriangleAway.
Good luck!

Solved
Kortxero said:
If you are on Speedmod's recovery (which is safe), you can try this:
1) Download the latest CM10.1 kernel and save it to your SD card.
2) Flash it in Recovery (Install zip from sdcard > choose zip from sdcard), then reboot in the new Recovery (advanced > reboot recovery).
3) Do a full wipe (even format preload and system in "mounts")
3) Flash the latest CM10.1 build
4) Flash the 4.2.2 Gapps
5) Do a data wipe / factory reset
6) Reboot
You got a yellow triangle because you flashed an unofficial kernel through Odin. To get rid of it, use TriangleAway.
Good luck!
Click to expand...
Click to collapse
Thanks a lot man. Issue has been resolved by following your procedure and phone is working all fine with CM10.1 on it. Xda rocks!!!

perceptorz said:
Thanks a lot man. Issue has been resolved by following your procedure and phone is working all fine with CM10.1 on it. Xda rocks!!!
Click to expand...
Click to collapse
You're welcome. Glad I could help . If you feel like it, hit the Thanks button on Chasmodo's first message in the repository (where you downloaded your CM10.1 kernel). He really deserves it. You may also want to do the same on Entropy's first post in the unofficial CM10.1 thread :good: That way, you'll show your support and appreciation :angel:.

[Q] Unable to start WiFi after flashing CWM 6.0.2.8 and 6.0.3.1 on custom JB ROM

Hello All,
I am on stock v4.1.2, flashed myself.
Now I want to move on to custom ROM.
My current stock ROM is rooted, and I have also unlocked my bootloader.
Now when I want to install custom ROM, I need to flash CWM, and when I do (tried v6.2.8 and v6.0.3.1), and install any ROM, my WiFi becomes unresponsive (failed to turn on). When I flash V20A back, everything turns normal.
I also gone through http://forum.xda-developers.com/showthread.php?t=2180138&page=43, and install the unsecure boot image after installing CWM 6028, but this make my custom rom hang on startup (on bootload screen).
Kindly help me out.
I have search a lot in the P880 forum, and didn't find any help regarding to this problem.

[email protected] said:
Hello All,
I am on stock v4.1.2, flashed myself.
Now I want to move on to custom ROM.
My current stock ROM is rooted, and I have also unlocked my bootloader.
Now when I want to install custom ROM, I need to flash CWM, and when I do (tried v6.2.8 and v6.0.3.1), and install any ROM, my WiFi becomes unresponsive (failed to turn on). When I flash V20A back, everything turns normal.
I also gone through http://forum.xda-developers.com/showthread.php?t=2180138&page=43, and install the unsecure boot image after installing CWM 6028, but this make my custom rom hang on startup (on bootload screen).
Kindly help me out.
I have search a lot in the P880 forum, and didn't find any help regarding to this problem.
Click to expand...
Click to collapse
i dont understand what the recovery has to do with the wifi. recovery is just an interface to easy install something, copy paste , edit , change permissions , etc , things we do using adb commands. it is just an environment. its something else u are doing wrong there.
<EDIT> yea i saw the thread on your link. others seem to have same problem but with the unsecure boot. why do u need unsecure boot if the bootloader is unlocked ? just install teamwin recovery or cwm recovery and the rom u want.

kessaras said:
i dont understand what the recovery has to do with the wifi. recovery is just an interface to easy install something, copy paste , edit , change permissions , etc , things we do using adb commands. it is just an environment. its something else u are doing wrong there.
<EDIT> yea i saw the thread on your link. others seem to have same problem but with the unsecure boot. why do u need unsecure boot if the bootloader is unlocked ? just install teamwin recovery or cwm recovery and the rom u want.
Click to expand...
Click to collapse
Well, I did. And it all went fine, and I am able to install various custom ROMs, and after I install custom ROM, my WiFi becomes unresponsive. I am completely at lost. I also tried MIUI v5 which is non-CM10.2 based, and it also showed the same issue.
Here are my steps to install a custom ROM.
- Currently I am on my V20A stock ROM.
- Root the stock ROM using the All-In-One-Toolkit v1.4.1
- Flush the CWM 6031 using ADB as
Code:
su
cat /mnt/sdcard/recovery.img > /dev/block/mmcblk0p1
sync
- After reboot, my device has the CWM.
- Copy custom ROM zip files to my device, and reboot to recovery
- Wipe out by data and cache
- Install ROM
thats it
And when I boot into the new custom ROM, my WiFi do not work.
Please help.

[email protected] said:
Well, I did. And it all went fine, and I am able to install various custom ROMs, and after I install custom ROM, my WiFi becomes unresponsive. I am completely at lost. I also tried MIUI v5 which is non-CM10.2 based, and it also showed the same issue.
Here are my steps to install a custom ROM.
- Currently I am on my V20A stock ROM.
- Root the stock ROM using the All-In-One-Toolkit v1.4.1
- Flush the CWM 6031 using ADB as
Code:
su
cat /mnt/sdcard/recovery.img > /dev/block/mmcblk0p1
sync
- After reboot, my device has the CWM.
- Copy custom ROM zip files to my device, and reboot to recovery
- Wipe out by data and cache
- Install ROM
thats it
And when I boot into the new custom ROM, my WiFi do not work.
Please help.
Click to expand...
Click to collapse
not exactly.
And here are my steps to install a custom ROM (if currently I am on my V20A stock ROM)
1. Root the stock ROM using the All-In-One-Toolkit v1.4.1
2. Unlock bootloader using All-In-One-Toolkit v1.4.1 or manually like this.
3. Flash the CWM 6.0.4.5 or 6.0.4.4 or TeamWin Recovery
4. Reboot the device in recovery.
5. Enter ADB sideload and install custom rom or using ADB bootloader or using ADB copy the rom in sd card and use install in recovery.
6. Wipe data and cache and reboot system.
<<STEPS DESCRIBED IN HELP SECTION - FREQUENTLY ASKED QUESTIONS>> ( by the way those must be updated too )

kessaras said:
not exactly.
And here are my steps to install a custom ROM (if currently I am on my V20A stock ROM)
1. Root the stock ROM using the All-In-One-Toolkit v1.4.1
2. Unlock bootloader using All-In-One-Toolkit v1.4.1 or manually like this.
3. Flash the CWM 6.0.4.5 or 6.0.4.4 or TeamWin Recovery
4. Reboot the device in recovery.
5. Enter ADB sideload and install custom rom or using ADB bootloader or using ADB copy the rom in sd card and use install in recovery.
6. Wipe data and cache and reboot system.
<<STEPS DESCRIBED IN HELP SECTION - FREQUENTLY ASKED QUESTIONS>> ( by the way those must be updated too )
Click to expand...
Click to collapse
I did wipe the data and cache after installing the custom ROM. But the result is the same; No WiFi response.
However, I always copy my custom ROMs by mounting my phone through USB to my Win8 laptop, and then copy the ROM file through windows explorer. And then install the ROM from the CWN recovery. Thus do not use ADB for copying files, or installing custom ROM as mentioned above. If this is the main issue reason, then advice.
Also I haven't tried TWRP till yet. Will do now. Till then, what else I can do.
Thanks for the quick replies.

i dont know what else you may doing wrong then. one was the insecure boot which is useless since u have unlocked the bootloader and the other that u had flash older version of cwm recovery. maybe compatibility issue with that version of cwm rec ? test and see.

format system also, when installing a new rom, not just data, cache & dalvik

kessaras said:
i dont know what else you may doing wrong then. one was the insecure boot which is useless since u have unlocked the bootloader and the other that u had flash older version of cwm recovery. maybe compatibility issue with that version of cwm rec ? test and see.
Click to expand...
Click to collapse
One piece of detail I missed to mentioned in my case previously was that, I unlocked my phone using the method mentioned in the thread http://forum.xda-developers.com/showthread.php?t=2263627 as I was unable to unlock using the official method.
After I unlock my bootloader, I have flashed V20A KDZ several times, and each time the SW Upd mode show me that my bootloader status is unlocked. Thus after first attempt of unlocking, I never came across need to unlocked my bootloader again as each time when I do the KDZ flash, I get the bootloader status as unlocked. And after each flash of KDZ, I was able to install CWM and custom ROMs, and boot into them successfully.
Is this something causing the issue?

[email protected] said:
One piece of detail I missed to mentioned in my case previously was that, I unlocked my phone using the method mentioned in the thread http://forum.xda-developers.com/showthread.php?t=2263627 as I was unable to unlock using the official method.
After I unlock my bootloader, I have flashed V20A KDZ several times, and each time the SW Upd mode show me that my bootloader status is unlocked. Thus after first attempt of unlocking, I never came across need to unlocked my bootloader again as each time when I do the KDZ flash, I get the bootloader status as unlocked. And after each flash of KDZ, I was able to install CWM and custom ROMs, and boot into them successfully.
Is this something causing the issue?
Click to expand...
Click to collapse
Now, I have repeated using CWM 6.0.4.5 and TWRP, and no breakthrough .... Starting to lose hope ... Help !!!

sorry , personally i dont know what else u may doing wrong there . and no it doesnt matter which way u unlock the phone, but since u unlock it , it stays that way until u lock it.
at least stock rom is working fine ? if that works fine there, then just install only custom kernel, do your tweaks, install another launcher and then delete the default, etc. u can do any modification u like to the stock one to make it look and work the way u want it.

kessaras said:
sorry , personally i dont know what else u may doing wrong there . and no it doesnt matter which way u unlock the phone, but since u unlock it , it stays that way until u lock it.
at least stock rom is working fine ? if that works fine there, then just install only custom kernel, do your tweaks, install another launcher and then delete the default, etc. u can do any modification u like to the stock one to make it look and work the way u want it.
Click to expand...
Click to collapse
Does it help if I installed a custom kernel on my custom ROM (with WiFi issue). My understanding is that the WiFi driver is compiled inside the kernel. So changing the kernel might reduce the issue. What do you think? If yes, then kindly advice me on which kernel should I install on my till now custom ROM MIUI v5 http://en.miui.com/download-79.html.

[email protected] said:
Does it help if I installed a custom kernel on my custom ROM (with WiFi issue). My understanding is that the WiFi driver is compiled inside the kernel. So changing the kernel might reduce the issue. What do you think? If yes, then kindly advice me on which kernel should I install on my till now custom ROM MIUI v5 http://en.miui.com/download-79.html.
Click to expand...
Click to collapse
a developer would never release a rom in public with wifi issues by default and since i have already tested all roms available before i end up to one, i can say that they all worked , but only had small bugs on homescreen. really i dont know what you are doing wrong and not even a teamviewer connection wouldnt help in this case. but on stock your phone works fine ? only in a custom rom u have this issue ?
<<EDIT>> did you also do a full format before going to another rom ? there is a choice in teamwin recovery ( dont know if its in cwm also ) to format data. careful i dont mean to wipe everything you see because you will remove the recovery too and u will have to flash it back. the format option deletes everything besides the recovery. if you dont format before you go to a totally different rom, then you maybe have issues. especially when going from stock to custom, differences are huge. you must format before flashing. and dont forget the gapps, if they are not inluded in rom. ( in your case miui there must have them inside, because i see its 256 mb+)

kessaras said:
a developer would never release a rom in public with wifi issues by default and since i have already tested all roms available before i end up to one, i can say that they all worked , but only had small bugs on homescreen. really i dont know what you are doing wrong and not even a teamviewer connection wouldnt help in this case. but on stock your phone works fine ? only in a custom rom u have this issue ?
<<EDIT>> did you also do a full format before going to another rom ? there is a choice in teamwin recovery ( dont know if its in cwm also ) to format data. careful i dont mean to wipe everything you see because you will remove the recovery too and u will have to flash it back. the format option deletes everything besides the recovery. if you dont format before you go to a totally different rom, then you maybe have issues. especially when going from stock to custom, differences are huge. you must format before flashing. and dont forget the gapps, if they are not inluded in rom. ( in your case miui there must have them inside, because i see its 256 mb+)
Click to expand...
Click to collapse
YES. When I flashed stock V20A, I never had issues with Wifi. Its when I install custom ROM, and any custom ROM.
So I suppose, either there is something wrong in my installing method, or in my stock ROM that won't allow WiFi to work on any custom ROM. But how much influential will be the stock ROM if it is being replaced by a custom ROM?
Well, I haven't formated before I install any custom ROM, as it was not instructed in the forums. But I will do that now, and let you know the results shortly.
Thanks again for the replies.

[email protected] said:
Well, I haven't formated before I install any custom ROM, as it was not instructed in the forums.
Click to expand...
Click to collapse
yea some informations are always missing from the instructions generally , but this is a developer forum , so it doesnt always include informations that are 100% well known to be done. So format and install again and tell me if its everything ok.

kessaras said:
yea some informations are always missing from the instructions generally , but this is a developer forum , so it doesnt always include informations that are 100% well known to be done. So format and install again and tell me if its everything ok.
Click to expand...
Click to collapse
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.

[email protected] said:
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.
Click to expand...
Click to collapse
What?????
Why would wiping your /data folder on internal storage delete your custom ROMs? Surely you keep them on your external SD-Card?

[email protected] said:
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.
Click to expand...
Click to collapse
you dont need to copy it . u can open adb sideload from recovery and on pc use command : adb sideload [path/filename of rom.zip]

SimonTS said:
What?????
Why would wiping your /data folder on internal storage delete your custom ROMs? Surely you keep them on your external SD-Card?
Click to expand...
Click to collapse
So you are saying that, I copy them to external_sd, and then do the data format. Ok ... Will do and let you know.
BTW, I also found V20B. I will start with this stock rom instead of V20A. This might improves some thing.

[email protected] said:
So you are saying that, I copy them to external_sd, and then do the data format. Ok ... Will do and let you know.
BTW, I also found V20B. I will start with this stock rom instead of V20A. This might improves some thing.
Click to expand...
Click to collapse
AT LAST .... FIXED ...
I did two things, V20B, and format /system, /data before installing new ROM. So my steps were:
1) Flush V20B instead of V20A
2) After rooting, and installed CWM 6044 touch, copy custom ROM MIUI to external SDCARD
3) Reboot into recovery, and format /system, /data, and /cache partitions
4) Install custom ROM from external SDCARD
5) Wipe data and cache
6) Reboot into the new world

:good: formatting did the work sorry i didnt think of it earlier.

GT-I9000 Problem with Stock-, Custom-Rom, Kernel and Recovery!

Hello,
I have a big problem with my GT-i9000 (yes its very old!)
I think first I have to explain the situation:
When I was 12 I wanted to learning Android App Development because I can program JAVA and I know that Android is JAVA. So my dad bought me a (used) phone with a Telecom branding from Germany (my home country). The GT-I9000, Samsung's flagship! I began to develop Apps. After a while, I flashed a Custom Recovery and i rooted it to install CyanogenMod 11.2. All went fine! Until i wanted to install TouchWiz over a Mod per CWM. But that went wrong... I don't know how but I was able to flash CM 11.2 again. But everytime when I flashed something, my phone didn't boot right. It always kept in the bootscreen. The cm circle circulated for hours.. But every time it was possible to fix that. I only had to delete my /system folder before flashing anything. But once (now, 2 years after I bought my phone), I wanted to flash Paranoid Android 4.4.4 (I already tested it and all went fine s it wasn't incompatible). I deletd the system folder like everytime and... Status 7... I tried to flash the stock ROM because i cant put another custem rom on my phone without any firmware (remember i deleted /system).
But i dont know my Bseband version and the CSC code... I tried to flash CWM with some Kernels. It was pposible but as i wanted to flash anything, it couldn't find the /sdcard or /sdcard1 folder
What to do? Does anyone know whats my CSC code, and post me a complete package witch all the files I need? :crying:

Hi,
at first there are some things to sort out:
- There's no CM11.2. There is CM11, and there is CM10.2.
- If you install CM11 over a prior version like stock or CM10.2, you will get a Status 7 error to inform you about the changed partition layout and telling you to flash the CM11 zip once more if you really want to install it as your phone will be wiped completely.
- I'm not sure, but just formatting /system isn't sufficient. You should do a complete wipe (don't forget to do a nandroid backup before...)
- If you want to go back to stock, you'll need a 3 files firmware and a proper pit file. Use Heimdall for flashing, and tick repartition.
Sent from my GT-I9000 using XDA Free mobile app

[Q] stucked after a fail with odin

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 :/

Issues with latest official TWRP 2.8.7.0 for Galaxy S3 4G I9305 and how to fix it

Hi everyone,
some who frequently read the forum may know already that there are issues with the latest official TWRP for the Galaxy S3 LTE. The recovery partition on the Galaxy S3 LTE is too small for the latest recovery provided by TWRP. The partitions are messed up, you won't be able to mount /system and /data. Some users couldn't even flash their preferred ROM. As of now the buggy recovery is getting fixed.
I am not responsible for any damage, losing data or weird behavior you encounter while doing one of the following steps. As reported by several users step 1 was the way for them to fix their phone. Be sure of what you're doing. Make sure you know how to boot into recovery/Download Mode to do these things mentioned here and how to use odin. If not, XDA users have provided several guides. Use the search.
If you already flashed the faulty recovery, flashed a custom ROM with it and your phone ends up in a bootloop there are several ways to fix this issue.
1. Via odin and official stock firmware - please note: You might lose all your data you have on your internal storage
Download the latest official Samsung firmware from sammobile or look on XDA for provided stock ROMs by the AMCHA team. Boot your phone into Download Mode and flash the official firmware via odin. If you're done, reboot into stock recovery (which will be provided after flashing the stock firmware), perform a factory reset and let your phone boot up once. First boot might take some time, so be patient. Although the first boot might not be needed, do it anyway to see if your phone is still in a bootloop or suffers from other damage. If the phone boots up fine reboot into Download Mode again, flash TWRP 2.8.5.0 or any other latest custom recovery (preferably the recovery the maintainers recommend in their development threads) and flash your preferred ROM. Your phone should now work as it should.
2. Via stock based custom ROM (if you haven't flashed any ROM via TWRP 2.8.7.0 already - please note: You might lose all your data in this process as well
Some users managed to get their phone working by flashing a stock based custom ROM like AMCHA or N4 Elite. If you only flashed the buggy recovery and didn't flash a custom ROM this way should be the step you should try first. Download any stock based custom ROM and flash it via the faulty one. If your phone boots up fine, boot into Download Mode and downgrade recovery or use any other recovery recommended for the ROM you're using. If you encounter issues or weird behavior with your phone go with step 1.
3. Via flashing a fixed TWRP 2.8.7.0 - please note: You might as well lose data
In this option you can flash a fixed version of TWRP which an user of XDA has provided. Many thanks to StdBarbarossa for his work. Unfortunately in his build you cannot mound your SD card via PC as it's not working at the moment. Make sure you have all the needed files already on your SD card. For some users this way was working for them. Boot your phone into recovery, click on install, change from .zip to .image, choose the Alpha17.img, install it by swiping and reboot your phone into recovery. Perform a wipe (preferably a factory reset, cache and dalvik cache might be working too) and see if your phone boots up fine. Here the same: if you're still facing issues go with step 1.
Link for the TWRP Alpha17 2.8.7.0 https://drive.google.com/file/d/0B-tlso-zNf9NMWlMMFpiYmYwTzA/view
I have gone through the same issue. In my case I only managed to get my phone working again with step one as I had flashed a custom ROM via the buggy recovery and ended up in a bootloop. As stated, others have managed to fix their phone with either option 2 or 3.
Link for the fixed TWRP is provided in the spoiler.
If you're not sure about something ask here first before you might brick your phone. If you know any other way to fix this issue feel free to post it here.