Related
UPDATE: WOLF HAS RELEASED TW 007.2 THAT INCLUDES THE zKernel.
Thanks to that, the process is much more simpler now. Just flash the files as it says in the Wolf thread.
Mods, please close this. Thanks to all who used this and hopefully this helped you in 007.1
hey thanks for posting this...
i will link up to this from the kernel thread...
btw u should also mention this:
>>
if u have previously used the wifi patch wifi_bt_fix-fxk_froyo_v01.1.zip please remove it using remove_fix_v01.1.zip and try using this test kernel
<<
will do..can i plz have a link to the remove_fix_01.1.zip? Thanks
kantk20111 said:
will do..can i plz have a link to the remove_fix_01.1.zip? Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1077437
Thanks...guide is updated
3.Go to settings-About phone. If, under kernel version, it says anything other than "2.6.29-zKernel-23062011 [email protected]#1", then you will have to do this.
Navigate to system/kernel using root explorer or similar app. DELETE boot.froyo.img, and RENAME boot.img to boot.froyo.img. Restart.
If it shows that kernel version, then skip this step.
Click to expand...
Click to collapse
Thanks a lot for this awesome guide. Im sure it will be very helpful to many users.
I followed ur guide to install custom kernel on WB TW007 with baseband .67.
But Im stuck on step 3. After flashing boot.img in Xrec I couldnt see custom kernel version in About Phone so I navigated to system/kernel using root explorer. There was only just one file named boot.img. So I renamed it to boot.froyo.img, rebooted but still get the stock kernel version in About Phone
Any kind of help will be greatly appreciated
digital_ism said:
Thanks a lot for this awesome guide. Im sure it will be very helpful to many users.
I followed ur guide to install custom kernel on WB TW007 with baseband .67.
But Im stuck on step 3. After flashing boot.img in Xrec I couldnt see custom kernel version in About Phone so I navigated to system/kernel using root explorer. There was only just one file named boot.img. So I renamed it to boot.froyo.img, rebooted but still get the stock kernel version in About Phone
Any kind of help will be greatly appreciated
Click to expand...
Click to collapse
hmm...I'm assuming that you have Stock kernel, right?
First, try re-flashing the boot.img file, but first wipe cache partition and wipe dalvik cache, then do the whole replacement an renaming. If that doesn't work, then try this:
(Thanks Haldi4803)
3. Restart Phone and enter X Recovery: Install first: "chargemon_FXRec_default_CUSTOM.zip" and then "bootloader_bypass_files_v2.zip"
Then, install the kernel on top of that while still in xRecovery. So, you would have installed all 3 files together . Please report back if it works so I can add this step in the OP.
^ Yes! Im on stock kernel. Sorry for not being clear.
Aiight. Im trying what u said right now and will report back.
EDIT: Nope. Nothing worked. Flashing all 3 files didnt work. On the other hand phone started lagging like hell after flashing. Its not responsive at all and Im constantly getting FC on System Process etc
Any thing else??
Hi everyone, dude, I tried follow u tutorial, but this didn't work (ok ok, I'm noob, i tried start this with Stock kernel...). Then I installed TW007.1 with Custom Kernel and didn't appears Custom kernel.. ok, i tried to install Z's custom kernel, following u tutorial and nothing again
What should I do?????
digital_ism said:
^ Yes! Im on stock kernel. Sorry for not being clear.
Aiight. Im trying what u said right now and will report back.
EDIT: Nope. Nothing worked. Flashing all 3 files didnt work. On the other hand phone started lagging like hell after flashing. Its not responsive at all and Im constantly getting FC on System Process etc
Any thing else??
Click to expand...
Click to collapse
u were most probably using xRecovery... flash FreeXperia recovery using FLASHTOOL and then try those files...
BTW if u use "chargemon_FXRec_default_CUSTOM.zip" then u dont need to do any renaming cause that files uses standard boot.img file name
cat /system/kernel/boot.img > /proc/splboot/boot_img
^ For some reason my Xrec is broken and I cant get into Xrec so I tried to install Rec thru Flashtool. It isnt working either
Insall Recovery option is disabled. I click on Ask Permissions, it says allow Superuseraccess on the phone but nothing happens on the phone. I cant do anything on the phone as it keeps FC Process System. It sometimes even doesnt detect USB conncetion
Is the SEUS repair the only option???
digital_ism said:
^ For some reason my Xrec is broken and I cant get into Xrec so I tried to install Rec thru Flashtool. It isnt working either
Insall Recovery option is disabled. I click on Ask Permissions, it says allow Superuseraccess on the phone but nothing happens on the phone. I cant do anything on the phone as it keeps FC Process System. It sometimes even doesnt detect USB conncetion
Is the SEUS repair the only option???
Click to expand...
Click to collapse
sadly, yes. I'm sorry about your phone, I wasn't sure if it would work with the stock kernel. another option could be to install the 3. 52 kernel first before following my instructions, or wait for wolf to officially release a kernel.
again, sorry about causing you to do a full repair
Na u dont need to be sorry. U were trying to help. I might've done something wrong or it was a bad day for me after all. Im repairing thru SEUS right now. Might give it another try in a day or two if WB doesnt officially release a Zkernel supported version of his rom.
But thanks once again for everything and keep up the good work
To those on the stock kernel,
Try to install the 3.51 kernel first, found here, then follow my instructions.
You won't get signal after installing the 3.51 kernel but that's ok, since it's meant for BB52 anyway. Your BB might become unknown as well.
That's what I do on a fresh install
Get baseband .67 first then
1) Fresh install TW007 stock kernel
2) Reboot and check for signal
2) Flash 007.1 update
3) Reboot
4) Flash transparent add-on (Optional)
5) Reboot
6) Flash zKernel_22062011.zip
9) Reboot and you will have the custom kernel but system keep on crashing and no signal
10) So I just reboot and flash this two files by DoomLord
Download link: (boot.img only)
http://www.mediafire.com/?vj9p2xy4p4w24ay
[VIMP NOTE FOR FROYO USERS who do not see any change in custom kernel after flashing the boot.img]
Download link: (wifi.ko module only)
http://www.mediafire.com/?lmh46quh490mzme
VERIFIED WIFI WORKS!
11) Signal is back and system doesn't crash
12) Reboot
13) Flash Contacts_ProSE _FIXED.zip & fb.zip
Thanks to them.
Everything is working. Use cpu master to overclock, it sometime give WLOD though
@gohwh1
u have linked to slightly older files...
i have posted updated kernel 23062011 based on FreeX10 ramdisk... which should work without any issue...
DooMLoRD said:
@gohwh1
u have linked to slightly older files...
i have posted updated kernel 23062011 based on FreeX10 ramdisk... which should work without any issue...
Click to expand...
Click to collapse
If that's working for me, I don't have to change right? Only problem is when overclocking to 1113mhz and playing games, it will WLOD when it's get too hot. Playing games for 3hrs non-stop and only one WLOD is normal right?
The updated kernel will not fix that right?
gohwh1 said:
If that's working for me, I don't have to change right? Only problem is when overclocking to 1113mhz and playing games, it will WLOD when it's get too hot. Playing games for 3hrs non-stop and only one WLOD is normal right?
The updated kernel will not fix that right?
Click to expand...
Click to collapse
thats wht it might!
please do try!
DooMLoRD said:
thats wht it might!
please do try!
Click to expand...
Click to collapse
Is it zKernel_freeX10_aZuZu_23062011.zip?
So I just have to flash it over current? Will flash it tommorrow, it's almost 3am here.
gohwh1 said:
Is it zKernel_freeX10_aZuZu_23062011.zip?
So I just have to flash it over current? Will flash it tommorrow, it's almost 3am here.
Click to expand...
Click to collapse
no this one:
zKernel_23062011 with FreeX10-beta4 ramdisk
http://forum.xda-developers.com/showthread.php?p=15170924#post15170924
This is for a clean install. You can also install straight from Froyo. Just start at the CM7 part below and skip the Odin portion.
FLASH AT YOUR OWN RISK
**If after you get on and are rocking the ICS of your dreams, you wake up one day and get the Encryption Unsuccessful - Reset Android - ICS Issue, see bottom of post for possible solution**
DO NOT HIT RESET repeat DO NOT HIT RESET
It is a bug that is hitting all ICS ROMS (AOSP-Passion, AOKP-Zen/Euphoria, Docmasters, CM9,...) on many different types of phones (Captivate, Vibrant, I-9000) and someone got hit with it in my OG Transformer Tablet (TF101) forums too.
You have been warned.
FLASH AT YOUR OWN RISK
I have made some observations as to how and why the Encryption Error strikes. See this thread starting at page 38 on (my post is #379 and after).
If running CM9 then this may be a work around before the issue strikes. I have not tried this and take no responsibilty if it works or not. Good Luck
USB mode switch for SGS1 on CM
Click to expand...
Click to collapse
What you need. All files can be found in the [Repository] Essential Hard To Find Files
Odin or (AIO ToolBox AND .net files) ***DO NOT PM me for this, I will just delete your PM and not respond. If you want ODIN, use Google and Download it. Sorry for this but my Dropbox account is suspensed b/c of too many downloads***
Gingerbread Bootloaders Go here for instructions.
CM7
Whatever ICS ROM you want to flash
These directions should work with any ICS ROM because the OPs and requirements (i.e. GB bootloaders, CM7 first,...) for all are essentially the same.
Click on Gingerbread Bootloader and ICS to take you to their respective threads.
**Note that this step (Installing Gingerbread Bootloaders) is reported to be optional as the Rainbows seemed to be fixed** Note: ICZenwich does REQUIRE Gingerbread bootloaders for CWM purposes.
If you want to use different Kernels (this is done after you flash the ICS ROM) on Neobuddy89's ICS Passion or Euphoria, Closedcircuit has them all in one place. Check out his thread here and make sure to thank him otherwise you might have to search for them on your own and we all know what a P.I.T.A. that is don't we?
.::IMPORTANT::.
Remember that you have to do this steps before and after update your kernel:
Wipe cache
Wipe dalvik cache
Flash kernel
Fix permissions
Click to expand...
Click to collapse
If for some reason your External_SD card (soon to be called EMMC after you get on ICS) does not mount. See here. Click the link within and flash it in CWR and you should be good to go
Click to expand...
Click to collapse
Standard Disclaimer Applies: This is your choice to do this, not mine. If something goes wrong, ask. If something goes horribly wrong, it is on you.
The video: This was done by DJeddieone and is very informative and helpful. Please watch it and hit his thanks. What follows is generally the same thing but with a few differences and in written form for all those people that need text instructions.
Watch this video, then read the below, watch the video again. Video has Froyo bootloaders and getting into recovery is different key combo, see GB thread below about that.
Just to make sure, I am going to start at the very beginning.
Flash back to stock 2.1 with Odin and the pit/pda files already included in the Toolbox. You should already know how to do this if you are flashing ICS. If not, then use the search to find out how.
Download and put Clockwork Recovery.zip on your internal SD card. Make sure it is labeled Update.zip and is the only .zip on the root of your SD card (should look like this /sdcard/update.zip). Can be directly downloaded from my signature or the Noob Guide stickied in the Q&A sections. Thanks s15274n
On your INTERNAL SDcard create a folder called ICS or something.
Download the CM7 file and put in the ICS folder (doesn't matter about the 911 issue b/c you aren't going to be using CM7 anyways)
Put the ICS ROM version that you already downloaded in the Folder also.
So let's start.
**Note that this step is reported to be optional as the Rainbows seemed to be fixed**
You need to open Odin and boot phone into download mode. Download the Gingerbread Bootloader and put it on your Desktop and in Odin, click on PDA and browse to the GB bootloader and click it. Your option but I do not tick the Auto-Reboot just in case of a bad flash. Once it passed, you are good. Unplug and reboot.
To start the flashing process, you should have 2.1 (stock-Eclair) on your phone as per above directions
Once it is fully booted, turn it off.
Push the Volume-Down + Power until you see the Vibrant come up and let go of the Power but keep ahold of the Volume-Down button. This will boot you into recovery. (If you are on Froyo Bootloaders, then it is Volume Up AND Down + Power) Can be tricky, so try it a couple of times if it doesn't work the first try.
Tab down to Reinstall Packages and click it. Let it run. If it gets back to the Blue Recovery, you might have to do it again. This will install the CWR that you put on your internal SD that you downloaded from my signature earlier. The recovery will go from Blue (stock) to Green (CWR).
Wipe Data/ Factory Reset, Wipe Cache and go to advanced and Wipe Dalvik-Cache, go to "Mounts and Storage" and format /system (if flashing Euphoria you'll need to format /data too), hit Back twice to front page of CWR.
***See Bottom why you need to flash CM7 before.***Also, if coming from a Voodoo Kernel based 2.2 or higher ROM-Disable it before flashing CM7.***
Scroll down to "Install from SD Card" and scroll down to your ICS folder. Find your CM7 file and hit it. Once it finishes, reboot. It will probably bootloop. This is normal. Pull your battery and boot into (turquoise [or red or green]) recovery again, "Install from SD" and reflash CM7.
Once it finishes, reboot. First boot takes longer than normal because it has to build the Dalvik-Cache. It should boot up this time. Let it fully boot up and settle for a minute or two. Hit power on the side and reboot into recovery directly from the Extended Power Menu.
**There is a point in the flashing of CM7 where you will think that the install either aborted or is finished. IT IS NOT DONE. Let is sit and completley boot up. Don't get trigger happy. You will see a toast to install your Google password. Then is when it is fully booted.**
Once you are in recovery, scroll down to your folder and find the ICSv? (or whatever version you are wanting to flash) and flash it. First boot takes a long time just like before on CM7. Might also get into a bootloop like in CM7 too. If so, then do the same as before and reflash ICSv?, but this time you'll have to use the Volume-Down + Power (or if on Froyo Bootloaders the above key combo) to get into recovery. Boot up and you are good to go in you new ICS rom.
**IMPORTANT**
Why do I need to flash CM7 before ICS? Can't i just go from Eclair to ICS? i have seen some people do it this way and it worked for them.
ICS kernels and working recoveries use a MTD based /system (hence the flash to CM7, as CM7 will convert your /system properly) and Eclair/Froyo are either RFS or Ext4 (voodoo). It also converts your Externa_SD into the EMMC partition.
If you get the RANDOM OFFSET error.
Don't freak out. This is an ICS security feature (as posted in Passion's FAQ post). All you have to do is pull your battery and boot back into recovery and reflash ICS over itself (just like you did with the initial CM7 bootloop) and it should push through. You may need to do this multiple times. I have read of people having to do it up to 5x. YMMV though.
If you get the Encryption Unsuccessful - Reset Android - ICS Issue
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Go here in the Captivate Forums.
******************
Couple of things.
Once you are in ICS
*your external sd is now called EMMC
*the GPS is sketchy (although there are new kernels that are reporting this issue fixed-see your respective ICS thread)
* there are some Deep Sleep issues
* when you RECEIVE a call, you will have to hit mute/unmute for them to hear you. (this seems to have been cleared up now)
These are all known bugs and if you ask about them in the thread, you'll get flamed for sure.
Good luck. The whole process should only take a hour or so and most of that is just finding the files and watching the video. Actual flashing should only take 10-20 minutes.
Hit the thanks. Pretty much gave everything needed to flash from 2.1 to 4.0.3
A computer lets you make more mistakes faster than any invention in human history – with the possible exceptions of handguns and tequila. ~Mitch Ratcliffe
Change log:
4/17/12 - I have made some observations as to how and why the Encryption Error strikes. See this thread starting at page 38 on (my post is #379 and after). Put in link to Play.Store for USB mode switch for SGS1 on CM and tag at top of guide re: its use.
4/2/12 - Emphasized the Encryption Bug to make it more visible and warning of hazards.
3/30/12 - Put in section at Top and Bottom about the Encryption Unsuccessful - Reset Android - ICS Issue and a link to the solution/workaround to the Captivate thread.
3/12/12 - Bolded AND in the kernel instructions re: wiping before AND after kernel flash. Put in something about waiting for CM7 to fully boot up and that it may seem like it is aborting or done, however it isn't and you need to wait for a complete boot. Don't jump the gun on this and pre-maturely pull out. This is called CyanogenMod-us Interruptus.
3/8/12 - Explained why you need to flash CM7 before ICS. Put in link to fix External Mounting issue.
2/22/12 - Put in blurb about PMing me for AIO Toolbox and made the Toolbox Secondary to Odin
Included Closedciruit's thread with the ICS Passion and Euphoria Kernels.
Put in blurb about RANDOM OFFSET error and how to fix/bypass it.
2/18/12 - Took out Dropbox links because my account got suspended for TOO MUCH TRAFFIC. You are on your own for those right now until I find another solution. I am not going to register for another file sharing site.
2/15/12 - Put Dropbox links in OP with Froyo and Gingerbread Bootloader. Revised to make this all ICS ROM compatible since the OPs and per-requisites are essentially the same.
2/12/12 - Now AIO Toolbox, .Net and CM7 have direct download links since MultiUpload is down
1/15/12 - Revised to show that you can come from 2.1 OR 2.2
Yea, rainbows are fixed. If you don't flash a gb bootloader you wont see the kernal boot image. That's the only known issue. So its not really needed
Thanks for the nod, good job man.
I'm glad you put the AIO toolbox there. It seems no one knows how valuable that little program is.
thanks woodrube for the simple guide. the video from djeddieone seems to be fairly simple also.
i heard that if odin was used to go back to stock eclair to never use kies mini for a future update or else it would hard brick the phone. I've never odined back to stock however tempting to install cm7 i fell victim to a bootloop so i freaked out and odined back to froyo kb5. the question is now, if i used odin to go back to froyo would it be the same outcome as using odin to stock eclair when tempting to update with kies mini?
the reason why i ask is, i had given up flashing a custom rom, hoping for a stock update. but if thats not possible anymore i will go ahead and flash ics.
i tried my best searching. if i'm asking in the wrong place please redirect me. thanks and be patient with the noob.
lazynoob said:
thanks woodrube for the simple guide. the video from djeddieone seems to be fairly simple also.
i heard that if odin was used to go back to stock eclair to never use kies mini for a future update or else it would hard brick the phone. I've never odined back to stock however tempting to install cm7 i fell victim to a bootloop so i freaked out and odined back to froyo kb5. the question is now, if i used odin to go back to froyo and not eclair would it be the same outcome as using odin to stock eclair when tempting to update with kies mini?
the reason why i ask is, i had given up flashing a custom rom, hoping for a stock update. but if thats not possible anymore i will go ahead and flash ics. thanks and be patient with the nood. i tried my best searching.
Click to expand...
Click to collapse
Couple of things. First DO NOT USE KIES. Kies will hardbrick you device. Not sure why anyone still uses this but don't. Second, you bootlooped in CM7 b/c of an CWR mismatch. This is normal for CM7. What you would want to do it pull the battery and reboot into recovery and reflash CM7, essentially over-top of itself. It should boot up the second time.
Don't give up on flashing custom ROMs. Once you do it, you will love all the cool things that you never knew you could do. Follow my instructions above and you can essentially flash whatever ROM you want from 2.1.
yea figured it out watching some youtube clips. should have reflashed. so what you are trying to say is kies mini in general is dangerous? i have used it sveral times to update when on stock. mine and my wife's vibrant.
last question, if the impossible happens and vibrant gets a stable stock update, will i be able to just odin to stock eclair and update? if not with kies maybe using odin?
thanks for your help. hoping to help those like me in the future. can't wait to start flashing.
lazynoob said:
so what you are trying to say is kies mini in general is dangerous? i have used it sveral times to update when on stock. mine and my wife's vibrant.
last question, if the impossible happens and vibrant gets a stable stock update, will i be able to just odin to stock eclair and update? if not with kies maybe using odin?
Click to expand...
Click to collapse
Kies is bad. Really surprised you haven't bricked it yet. Stick with Odin to do your fresh flash. The Vibrant is not going to get an update, so don't count on that (see the petition in my signature if you want that to change). Fortunately we have an outstanding development community.
If you want a stable 2.2 try Toxic8 (I run this with Gingerbread theme as my "home" ROM when I am not testing), Deranged9, Bionix (no longer supported) and Bionix Fishman's version (this is supported), Bi-winning. All you have to do to flash these is follow the instructions above and when it comes time to flashCM7, skip it and flash the ROM of your choice. All of these have working GPS and 911, so no issues there. Any GB ROM (CM7 included) will not have functioning 911, just an fyi.
Bump (sort of b/c I updated some things on the OP)
Reserved. Good guide here. Thanks for the effort for those who are not so familiar with flashing like me. Gonna flash ICS when i get my Vibrant back. Thanks buddy.
multiupload seems to be done, does anyone have another link or can they send me AIO Toolbox?
Quikster said:
multiupload seems to be done, does anyone have another link or can they send me AIO Toolbox?
Click to expand...
Click to collapse
help? does anyone have this file or another link? PM me
outstanding development community.
I will upload a version of Toolbox and the generic CM7 build sometime tomorrow since multiupload is apparently down.
Woodrube said:
I will upload a version of Toolbox and the generic CM7 build sometime tomorrow since multiupload is apparently down.
Click to expand...
Click to collapse
awesome, i greatly appreciate that
OP updated with Dropbox links to AIO Toolbox, .Net add-on and CM7 7.1 ROM.
Thanks for the Guide, works perfectly. Now im enjoying ICS Passion v13 RC1.
I was in TeamToxic-D9RC3 rom. This is what i did:
- I started from CM7 part.
- Reboot into Recovery
- Wipe Data/ Factory Reset, Wipe Cache and go to advanced and Wipe Dalvik-Cache.
- Locate ICS folder-Install CM7.
- After boot into CM7-reboot into Recovery again.
- Install ICS Passion RC1.
- After finish installation, wait bout 5mins.
- Reboot into Recovery again, flash cleanup patch then reboot.
- That's it.
Thanks to:-
-Neobuddy
-Nelson for the Kernel
-Romanbb for source hack to enable FB sync
-Daniel for the Bootsplash and other graphical enhancements
-CM9/Teamhacksung for the drivers
-Annex for cosmetic upgrades which are really better than Stock ICS AOSP.
psycho for Mods
-Woodrube
Woodrube said:
I will upload a version of Toolbox and the generic CM7 build sometime tomorrow since multiupload is apparently down.
Click to expand...
Click to collapse
Thank you very much
Woodrube ... thanks for the nice tutorial. Couple questions re. the GB Bootloaders.
Woodrube said:
**Note that this step is reported to be optional as the Rainbows seemed to be fixed**
Click to expand...
Click to collapse
When you say "Rainbows seemed to be fixed" ... does this mean:
a) GB Bootloaders are still REQUIRED - ie. it's the GB Bootloaders that "fix" the rainbows?
b) Or ... GB Bootloaders NOT required - ie. some type of fix has now been incorporated into the ICS ROM packages?
Sorry for asking for noobish clarification, but I wanted to avoid any possibility of turning my phone into a paper weight.
Woodrube said:
Your option but I do not tick the Auot-Reboot just in case of a bad flash.
Click to expand...
Click to collapse
This is a great suggestion. Thanks for the tip.
Woodrube said:
Gingerbread Bootloaders
Click to expand...
Click to collapse
adyscorpius' link for his modified JFD ODIN file is down (ie. Multiupload is down). Wondering if anyone has this particular file or a fresh link to download it? It'd be nice to not have to worry about whether a JFD package has the proper boot.bin / sbl.bin combo or not.
Ok so I started out with an x5 running an oxygen ROM ( unsure what one as its been awhile) with a full battery.
1. I then went to install the Aurora ICS 2.0.5 after doing all the wipes needed went to load and all i got was a system that fuctioned but not network service and no battery charging and the device showing 1% battery (it was full to start with).
2. I also tried the Elite.SX.Second.Release-FIXED.by.TerraMino.2012-03-29 ROM (all wipes done) just to get the same things happening
also tried to install and older Oxygen ROMs , oxygen 2.2.2 - 2.3.2 all wipes done) but the device didnt boot.
3. So then I tried a stock ROM via the dload method by puting this [11.07.28]_U8800_V100R001C17B162CUSTC17D001_(China_Unicom)(also another stock ROM I dont remember which) UPDATE.APP on the SD card (Cant put the UPDATE.APP on to internal memory as it is to large) then went to boot into the "pink screen" but nothing happened (both ROM's). Also tried many methods to try to get it to work.
4. After that I thought I would try Miui Prime v3 - by LegoLaSH (done all wipes and formats needed) once it booted I got no network service and battery at 0% although it is Full before starting. Also no battery charging while device is on.
5. I figured Id try ( althoug I guessed it wouldnt work)to install an Oxygen ROM first then install Elite.SX.Second.Release-FIXED.by.TerraMino.2012-03-29 ROM streight after it without wipes , still the same problems as installing the elite ROM alone.
So now Im here and stuck. Is there no flasher for Hauwei phones? oranother way I can get a ROM on the device? Its not my Phone its my partners.
Also its not the First Phone I have ever installed a custom ROM on although seems to be the hardest.
If any idea or more info needed please post.
thanks alot.
Confrontation
You need to install the official 2.3 rom before installing any of those roms.
FlashTH said:
You need to install the official 2.3 rom before installing any of those roms.
Click to expand...
Click to collapse
I know , But as in put 3 , that is an official ROM and the method to install it will not work.
confrontation said:
I know , But as in put 3 , that is an official ROM and the method to install it will not work.
Click to expand...
Click to collapse
Are you sure you put the UPDATE.APP inside the dload folder which is in the root of the sdcard? I never heard of this not working.
I am not sure which files the official 2.3 rom updates, but wouldn't it be possible to copy them from an updated U8800?
FlashTH said:
Are you sure you put the UPDATE.APP inside the dload folder which is in the root of the sdcard? I never heard of this not working.
I am not sure which files the official 2.3 rom updates, but wouldn't it be possible to copy them from an updated U8800?
Click to expand...
Click to collapse
I had a freshly formated SD card with no other files or folders and I had the UPDATE.APP in a folder named dload on the SD card.
Is that not the right way?
You need to update to OFFICIAL 2.3.5 (you were updating to 2.2). You can get it here:http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDQzNTg=
This is porbably most repetead sentence in this forum and is also written in every ROM thread. Oygen was working beacuse its .32 kernel and the newer ROMs are .35 kernel and need to update to OFFICIAL 2.3.5 before flashing. If you would search a little you would find it in less than a minute.
Here is guide how to root and install recovery on official 2.3.5:
http://forum.xda-developers.com/showthread.php?t=1420728
All the instructions for updating with dload method are in the pdf that is in the zip you downloaded from huawei page.
yannn007 said:
You need to update to OFFICIAL 2.3.5 (you were updating to 2.2). You can get it here:http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDQzNTg=
This is porbably most repetead sentence in this forum and is also written in every ROM thread. Oygen was working beacuse its .32 kernel and the newer ROMs are .35 kernel and need to update to OFFICIAL 2.3.5 before flashing. If you would search a little you would find it in less than a minute.
Here is guide how to root and install recovery on official 2.3.5:
http://forum.xda-developers.com/showthread.php?t=1420728
All the instructions for updating with dload method are in the pdf that is in the zip you downloaded from huawei page.
Click to expand...
Click to collapse
The problem is that he can't update to the official 2.3.5, the update doesn't start.
confrontation said:
3. So then I tried a stock ROM via the dload method by puting this [11.07.28]_U8800_V100R001C17B162CUSTC17D001_(China_Unicom)(also another stock ROM I dont remember which) UPDATE.APP on the SD card (Cant put the UPDATE.APP on to internal memory as it is to large) then went to boot into the "pink screen" but nothing happened (both ROM's). Also tried many methods to try to get it to work
Confrontation
Click to expand...
Click to collapse
The UPDATE.APP file is only around 300 megs so will easily fit on your internal 2Gb memory so sounds like your trying to copy it to the pink screen memory which is wrong!
yannn007 said:
You need to update to OFFICIAL 2.3.5 (you were updating to 2.2). You can get it here:http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDQzNTg=
This is porbably most repetead sentence in this forum and is also written in every ROM thread. Oygen was working beacuse its .32 kernel and the newer ROMs are .35 kernel and need to update to OFFICIAL 2.3.5 before flashing. If you would search a little you would find it in less than a minute.
Here is guide how to root and install recovery on official 2.3.5:
http://forum.xda-developers.com/showthread.php?t=1420728
All the instructions for updating with dload method are in the pdf that is in the zip you downloaded from huawei page.
Click to expand...
Click to collapse
If you had read my post properly you would see I already know. thanks for you unhelpful post.
Also the Huawei link is giving me an Service Temporarily Unavailable message , and has since the other day , if you can upload it somewhere or anybody , I can download it then.
I think the problem is that he has a custom partition layout for the internal emmc, that needs to be reset to the default before installing the update.
look here for instructions:
http://forum.xda-developers.com/showthread.php?t=1112857
dzo said:
I think the problem is that he has a custom partition layout for the internal emmc, that needs to be reset to the default before installing the update.
look here for instructions:
http://forum.xda-developers.com/showthread.php?t=1112857
Click to expand...
Click to collapse
Do I use the return-to-stock partition file or the 1.2G DATA + 1.46G INTERNAL SD file? Thanks
Ok I have tried both return-to-stock partition and 1.2G DATA + 1.46G INTERNAL SD file , I still cant get the internal SD to show on 2 computers.
I really hve no idea now.
The same problem after installing Aurora. Installed 2.3 first. Now can't install official update, just a pinkscreen, nothing happens. All custom ROMs easily installs with CWM.
Sent from my U8800 using xda premium
thank you very much!
confrontation said:
Ok I have tried both return-to-stock partition and 1.2G DATA + 1.46G INTERNAL SD file , I still cant get the internal SD to show on 2 computers.
I really hve no idea now.
Click to expand...
Click to collapse
Dzo is probably right about the partition layout of your internal mmc. But probably you cannot fix it with geno's method. I would suggest you to check this post http://forum.xda-developers.com/showthread.php?t=1579366
Also it seems to me that you have the imei=0 problem when you updated from 2.2.2 to 2.3.5 (no network - battery 1% or 0% are common problems)
And try not to flash different kernel based roms without upgrading/downgrading to the appropriate kernel, as this probably has damaged your phone.
Hope that helps
halman said:
Dzo is probably right about the partition layout of your internal mmc. But probably you cannot fix it with geno's method. I would suggest you to check this post http://forum.xda-developers.com/showthread.php?t=1579366
Also it seems to me that you have the imei=0 problem when you updated from 2.2.2 to 2.3.5 (no network - battery 1% or 0% are common problems)
And try not to flash different kernel based roms without upgrading/downgrading to the appropriate kernel, as this probably has damaged your phone.
Hope that helps
Click to expand...
Click to collapse
Thanks will try after dinner.
the Huawei site would let me download the 2.3.5 ROM , can somebody upload it to or link me to a download? Cheers
confrontation said:
the Huawei site would let me download the 2.3.5 ROM , can somebody upload it to or link me to a download? Cheers
Click to expand...
Click to collapse
Check this post http://forum.xda-developers.com/showthread.php?t=1546883
Well well well , I found my other SD card ( better quality SD card ) and BAM! dload works 1st time.
Thanks for all the help from the people who posted here , I have learnt alot from all this.
Thank you thank you.
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
you custom flashed??
what do u mean u custom flashed??
Get a rom with bootloader in it. Don t use repartition. Make sure you flash the bootloader.
Sounds like you wiped from a stock Samsung kernel, which is a big no no. The only way to fix this is to repartition your phone with a .pit file that has been designed not to use the the corrupted sectors of your internal storage. If you search hard enough, you'll find a thread about it. I successfully recovered a phone I bricked way back with the first LP1 ICS kernel. It does work! You'll lose some space though.
http://forum.xda-developers.com/showthread.php?t=1667886
And there's the thread I was talking about.
tibosee said:
Get a rom with bootloader in it. Don t use repartition. Make sure you flash the bootloader.
Click to expand...
Click to collapse
Can you send me a link with a rom which has this please?
Here i had the same problem when I tried to flash my first rom. Just tried to flash on another computer and guess what... Successfully done!
Sent from my GT-I9100 using Tapatalk 2
smalmagal said:
Sounds like you wiped from a stock Samsung kernel, which is a big no no. The only way to fix this is to repartition your phone with a .pit file that has been designed not to use the the corrupted sectors of your internal storage. If you search hard enough, you'll find a thread about it. I successfully recovered a phone I bricked way back with the first LP1 ICS kernel. It does work! You'll lose some space though.
http://forum.xda-developers.com/showthread.php?t=1667886
And there's the thread I was talking about.
Click to expand...
Click to collapse
Yes I factory reset a STOCK ICS ROM .. please can you assist in what I need to do.. Which PIT file and which ROM Shall I try to flash with.. please assist.. Many thanks..
Thanks for your help guys .. followed the german dudes tutorial and downloaded the .PIT file and managed to re flash stock ICS .. Now the only issue is my internal memory is showing 8.24 GB.. what happened to the other approx 8GB? I thought the Note was 16GB? Before windows used to show it as 11GB but now showing 8.24 GB is there a fix for this or is the bad or do I have to live with it.. ?
read the whole tut again it tells you why since you have to move partition tables.
Yes...it's a rather small deal anyway...there are 64gb SD card after all.
mkohman said:
Thanks for your help guys .. followed the german dudes tutorial and downloaded the .PIT file and managed to re flash stock ICS .. Now the only issue is my internal memory is showing 8.24 GB.. what happened to the other approx 8GB? I thought the Note was 16GB? Before windows used to show it as 11GB but now showing 8.24 GB is there a fix for this or is the bad or do I have to live with it.. ?
Click to expand...
Click to collapse
My advice is "live with it". Coz what the "German dudes" pit files do is avoid the "locked" sectors in your internal card. While you can try different pit files or try create new partitions via adb -- you probably wont gain much.
Or you could send it to Sammy for a warranty claim, after resetting the flash counter and then bricking it again via odin using the original pit file. Basically what you need to do is erase all evidence that u tampered with it. This is a risky option... (You can tell them phone got messed up in kies upgrade). This happened to me (on an almost new note, so i kinda did the same, except that i went a step further and deleted the boot-loader as well = hard brick. However i dont recommend it). And they replaced the phone.
I emphasize again this is risky -- and do more research before if you do this.
Problem as of now is since you've modified the pit -- and also the phone is working, you cant claim now.
nipuna said:
My advice is "live with it". Coz what the "German dudes" pit files do is avoid the "locked" sectors in your internal card. While you can try different pit files or try create new partitions via adb -- you probably wont gain much.
Or you could send it to Sammy for a warranty claim, after resetting the flash counter and then bricking it again via odin using the original pit file. Basically what you need to do is erase all evidence that u tampered with it. This is a risky option... (You can tell them phone got messed up in kies upgrade). This happened to me (on an almost new note, so i kinda did the same, except that i went a step further and deleted the boot-loader as well = hard brick. However i dont recommend it). And they replaced the phone.
I emphasize again this is risky -- and do more research before if you do this.
Problem as of now is since you've modified the pit -- and also the phone is working, you cant claim now.
Click to expand...
Click to collapse
Thanks for your assitance bro.. I will live with it. .I don't mind loosing 3 gb .. Already got 32GB SD card so no issue. Just happy its all back up and running really.. Big thanks to the German brother you the man
Its Forest1971 who first wrote this workaround and it was hg42 who rewrote the pit file and it was Dr null who proposed this way, Its all XDA members who helped you out of this brick. Not some German sites. Google throws up German results first
I am not harsh by anyway saying this. Just want to write it as it happened.
Was witnessing all the issues.
I am writing a guide for Noobies for bricks. Guess I get some help ....
prabhu1980 said:
Its Forest1971 who first wrote this workaround and it was hg42 who rewrote the pit file and it was Dr null who proposed this way, Its all XDA members who helped you out of this brick. Not some German sites. Google throws up German results first
I am not harsh by anyway saying this. Just want to write it as it happened.
Was witnessing all the issues.
I am writing a guide for Noobies for bricks. Guess I get some help ....
Click to expand...
Click to collapse
I actually followed his guide and repartioned manually and only lost about one Gbyte vs using the pit file and losing over 3 G bytes. Took a lot of trial and error though
Sent from my GT-N7000 using Tapatalk 2
RE:
mkohman said:
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
Click to expand...
Click to collapse
hi! i was in the same state as you! now, listen very carefully. Now, all you have to do is to use another PC and run ordin. Everything should work fine! My note was soft-bricked yesterday night and i had tried endless counts of tries just to get it up and running. Just earlier today,I saw someone who posted a comment in a similar forum and suggested that you should try a different PC it worked. AND IT worked for me now, just use this pit file that i had upload and download any (G-N7000)stock firmware that has (code.md5, modem.md5 and csc.md5). just place the pit file in ordin. ( do note you will lose 3gb of your internal memory) and click start hopefully it worked for you
-yours truly-
zairui from Singapore
can you contact entropy before sending your unit to samsung??
entropy is looking, if im not mistaken, for a purely stock bricked note... kindly pm him
zairui said:
hi! i was in the same state as you! now, listen very carefully. Now, all you have to do is to use another PC and run ordin. Everything should work fine! My note was soft-bricked yesterday night and i had tried endless counts of tries just to get it up and running. Just earlier today,I saw someone who posted a comment in a similar forum and suggested that you should try a different PC it worked. AND IT worked for me now, just use this pit file that i had upload and download any (G-N7000)stock firmware that has (code.md5, modem.md5 and csc.md5). just place the pit file in ordin. ( do note you will lose 3gb of your internal memory) and click start hopefully it worked for you
-yours truly-
zairui from Singapore
Click to expand...
Click to collapse
Not necessary to use the 3gb regain patch.
There's a 1gb or 2gb regain patch also. And it's enough.
WJ
Sent from xda-developers Galaxy N7000 ICS 4.0.4 LRK / CriskeloROM v.11.1 / Speedmod K3-12
---------- Post added at 11:34 PM ---------- Previous post was at 11:26 PM ----------
mkohman said:
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
Click to expand...
Click to collapse
Though so many ppl told u alrd, i just want to say, in any case, when u r in ICS alrd, it is totally prohibited to do factory reset through CWM with samsung ICS original kernel.
When u need to wipe or factory reset, make sure u r on a safe kernel like speedmod or notecore.
If u want to recover ur note, just use the pit file method. It works.
Make sure u use the correct patch of 16gb or 32gb, depends on ur note.
Always try from the smallest patch, so u won't loose so many storage.
Anyway, latest CriskeloROm with speedmod is the best for battery life nd performance.
WJ
Sent from xda-developers Galaxy N7000 ICS 4.0.4 LRK / CriskeloROM v.11.1 / Speedmod K3-12
I'm having the same issue now.
I did wipe data / factory reset with stock ICS kernel and I think, I bricked the Note.
I didn't know there were such issue.
I couldn't find a ROM with 3 files (code.md5, modem.md5 and csc.md5).
Please kindly guide me where to find such ROM.
i bricked mine last week and used the patched pit files to restore i went through a few pit files b4 i found one that worked i now have about 9 gb nand left but my phone works and has jb on it now
anubis1126 said:
i bricked mine last week and used the patched pit files to restore i went through a few pit files b4 i found one that worked i now have about 9 gb nand left but my phone works and has jb on it now
Click to expand...
Click to collapse
So we dont need 3 files ROM?
Hi Guys
I have a Samsung Galaxy s i9000 slim bean Rom the base band & IMEI unknown I can't seem to use it to sms or call a guy from the Slimrom site told the Rom has no modem, so how do i add one ? I realy like the Rom its much faster than the one I had before I had Cyanogen mod Helly bean before and about 2 weeks ago it got into a boot loop so I got a friend of a friend to root it for me twice and still have this no network issue! I can't ask him to do it again. So I am trying to find a solution here. How do I add a modem ? The wifi works fine but Whats app tells me that tablets are not supported... but this is not a tablet its a Samsung Galaxy s i9000 , will adding a modem fix the network issue and make Whats app work? Or do I need a new Rom? Please keep in mind that I'm not a Android Developer in any sense of the word!!
Thanks Reigncpt!!
try the latest Slimrom
Reigncpt said:
Hi Guys
I have a Samsung Galaxy s i9000 slim bean Rom the base band & IMEI unknown I can't seem to use it to sms or call a guy from the Slimrom site told the Rom has no modem, so how do i add one ? I realy like the Rom its much faster than the one I had before I had Cyanogen mod Helly bean before and about 2 weeks ago it got into a boot loop so I got a friend of a friend to root it for me twice and still have this no network issue! I can't ask him to do it again. So I am trying to find a solution here. How do I add a modem ? The wifi works fine but Whats app tells me that tablets are not supported... but this is not a tablet its a Samsung Galaxy s i9000 , will adding a modem fix the network issue and make Whats app work? Or do I need a new Rom? Please keep in mind that I'm not a Android Developer in any sense of the word!!
Thanks Reigncpt!!
Click to expand...
Click to collapse
..Hi,please try the latest slimrom, the thread is here
http://forum.xda-developers.com/showthread.php?t=2060374
..try a clean install just to make sure.
How do you do a clean install?
wilvic said:
..Hi,please try the latest slimrom, the thread is here
http://forum.xda-developers.com/showthread.php?t=2060374
..try a clean install just to make sure.
Click to expand...
Click to collapse
I followed the instructions on the slim bean site cleared cache partition and wiped dalvik cache and installed the latest version : Slim-I9000-4.2.1.stable.1.0-OFFICIAL .... but still the same issue IMEI and Baseband are unknown and I get no network. Did I do it wrong?
How do I do clean install? Do I need special software to do a clean install? If so where do I get it ?
I read somewhere on this forum that I need to flash the original rom to it to get it to find its IMEI and modem settings then flash the rom I want! Is the true? If so where do I get the original rom from as I got the phone with Cyanogen Helly bean on it so I don't even know what the original rom was??
Will really appreciate any help thanks!!!
Reigncpt
Try this
Reigncpt said:
I followed the instructions on the slim bean site cleared cache partition and wiped dalvik cache and installed the latest version : Slim-I9000-4.2.1.stable.1.0-OFFICIAL .... but still the same issue IMEI and Baseband are unknown and I get no network. Did I do it wrong?
How do I do clean install? Do I need special software to do a clean install? If so where do I get it ?
I read somewhere on this forum that I need to flash the original rom to it to get it to find its IMEI and modem settings then flash the rom I want! Is the true? If so where do I get the original rom from as I got the phone with Cyanogen Helly bean on it so I don't even know what the original rom was??
Will really appreciate any help thanks!!!
Reigncpt
Click to expand...
Click to collapse
Hi,
We can't be sure what the original ROM for your phone was, probably they we're referring to Eclair because that's the default. I have Galaxy S too so I wanted to help you. So here's what we will do, we might need to install an official stock ROM for it, we will not use froyo, instead this tutorial will let you install the latest GB for GT-i9000,GingerBread 3.6.
Here's the link (please hit thanks on the one who posted that if it will help you): http://forum.xda-developers.com/showthread.php?p=22555425
(You have to follow that tutorial up until this line only:
• When the phone reboots into the rom, wait for the setup wizard to appear and then just use the 3 key combo into the download mode again.
Close Odin and open it again> press PDA button and browse for CF-Root…file> Press START button and wait for the green pass notification in Odin.
**Lines after that, you don't need to do, since you will be flashing Slim rom. After that, your phone will reboot and you will be in the latest Gingerbread for Galaxy S, and a rooted one so you have a CWM)
After doing that, we will have to install Slim ROM. (a clean install, or fresh install, a clean install is this - wiping everything out, as in fresh install)
Here's what you need to do (straight from Slim Rom's website)
From another JB or ICS Rom to SlimBean
Download device_x.x.zip, slim_gapps.zip.
Enter CWM, wipe data, format system ( in mounts and storage)
Flash Device_x.x.zip***, then MUST flash slim_gapps.zip (other files optional)
*** - If the flash is too quick ( < 5 seconds or so), reflash device before flashing common or other zip files.
(So that's what you need to do, just download the latest rom and the gapps for galaxy s i9000,
put it in the root of your internal sd card
Go to Clockwork mod (Turn off, then press DOWN, POWER, HOME simultaneously)
wipe data, format system ( in mounts and storage)
Install zip from sd card and you will have the latest Slim rom and hopefully you get your IMEI back)
Please reply if you have more questions or clarifications needed, you can also message me, i will reply as soon as i can.
Slimbean IMEI unknown fix i9000
wilvic said:
Hi,
We can't be sure what the original ROM for your phone was, probably they we're referring to Eclair because that's the default. I have Galaxy S too so I wanted to help you. So here's what we will do, we might need to install an official stock ROM for it, we will not use froyo, instead this tutorial will let you install the latest GB for GT-i9000,GingerBread 3.6.
Here's the link (please hit thanks on the one who posted that if it will help you): http://forum.xda-developers.com/showthread.php?p=22555425
(You have to follow that tutorial up until this line only:
• When the phone reboots into the rom, wait for the setup wizard to appear and then just use the 3 key combo into the download mode again.
Close Odin and open it again> press PDA button and browse for CF-Root…file> Press START button and wait for the green pass notification in Odin.
**Lines after that, you don't need to do, since you will be flashing Slim rom. After that, your phone will reboot and you will be in the latest Gingerbread for Galaxy S, and a rooted one so you have a CWM)
After doing that, we will have to install Slim ROM. (a clean install, or fresh install, a clean install is this - wiping everything out, as in fresh install)
Here's what you need to do (straight from Slim Rom's website)
From another JB or ICS Rom to SlimBean
Download device_x.x.zip, slim_gapps.zip.
Enter CWM, wipe data, format system ( in mounts and storage)
Flash Device_x.x.zip***, then MUST flash slim_gapps.zip (other files optional)
*** - If the flash is too quick ( < 5 seconds or so), reflash device before flashing common or other zip files.
(So that's what you need to do, just download the latest rom and the gapps for galaxy s i9000,
put it in the root of your internal sd card
Go to Clockwork mod (Turn off, then press DOWN, POWER, HOME simultaneously)
wipe data, format system ( in mounts and storage)
Install zip from sd card and you will have the latest Slim rom and hopefully you get your IMEI back)
Please reply if you have more questions or clarifications needed, you can also message me, i will reply as soon as i can.
Click to expand...
Click to collapse
Guys. I have used Slim bean firmware on 2 i9000 with no issues but my third had imei unknown. I tried all options. Basically it would be there from 2.2 to 2.3 but once rooted and CWM added, and I installed Slim I would loose imei. Tried imei backups- no good. Fix was easy. Install Hellybean instead. Just worked. I suspect there is an issue in slim unfortunately...
This is a known issue with i9000 losing its IMEI... It was always recommended to have an EFS backup if it arose...
i've tried copying efs from backup using shady file root free but i still can't get my network back on infuse 4g
Clean Install Of Slim Rom
Hi Guys
I'm new to this whole rom experience, and want to up date my Slim Bean 4.2.1 -> the new 4.2.2 the slim rom site says I need to do a "Full wipe" goes on to say : "Means full data wipe and manual format of system partition."
So can any one please help me with a step by step walk through as how to do this on a GT i9000 with Semaphore Kernel?
Thanks so much you Guys!!!!
Reigncpt!!
Reigncpt said:
Hi Guys
I'm new to this whole rom experience, and want to up date my Slim Bean 4.2.1 -> the new 4.2.2 the slim rom site says I need to do a "Full wipe" goes on to say : "Means full data wipe and manual format of system partition."
Reigncpt!!
Click to expand...
Click to collapse
Full wipe means "wipe data/factory reset" in CWM recovery.