Hi,
Previously posted this as a reply in a ROM subthread - however, I suspect it's probably better in it's own thread.
A friend has a Samsung Galaxy Note 2 GSM LTE (NT-7105) phone.
Previously, they flashed an official CyanogeMod ROM for the NT-7100 onto the device - not quite sure how they managed to do this, since I assumed the asserts would have stopped them.
Currently, the Baseband version and IMEI are both listed as unknown - I'm assuming this is possibly related to flashign the wrong ROM?
In Odin Download mode, it still states NT-7105.
However, when I attempt to flash this ROM over the device in CWM, the device asserts fail:
Code:
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "t0lte" || getprop(ro.build.product") == "t0lte" ||...
What's the best way to remedy this? Does the device actually now think it's a NT-7100? Is it safe to remove the asserts from the zipfile, or is there a safer way?
Cheers,
Victor
victorhooi said:
Hi,
Previously posted this as a reply in a ROM subthread - however, I suspect it's probably better in it's own thread.
A friend has a Samsung Galaxy Note 2 GSM LTE (NT-7105) phone.
Previously, they flashed an official CyanogeMod ROM for the NT-7100 onto the device - not quite sure how they managed to do this, since I assumed the asserts would have stopped them.
Currently, the Baseband version and IMEI are both listed as unknown - I'm assuming this is possibly related to flashign the wrong ROM?
In Odin Download mode, it still states NT-7105.
However, when I attempt to flash this ROM over the device in CWM, the device asserts fail:
Code:
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "t0lte" || getprop(ro.build.product") == "t0lte" ||...
What's the best way to remedy this? Does the device actually now think it's a NT-7100? Is it safe to remove the asserts from the zipfile, or is there a safer way?
Cheers,
Victor
Click to expand...
Click to collapse
Hey Im sorry to hear about your Problem. But i know that n7105 roms are compatible with At& and T-mobile Roms I dont think n7100 Rooms are compatible unless they have been ported. I would first flash my Backup of my stock rom and see if the Imei comes back. (I Hope you made a back up) and if that dont work i would search a thread on QPST whichs shows you step by step how to recover you imei
Did you get it sorted?
I've gone and done the same thing
i installed a N7100 rom onto my N7105 note.
and after realising i had no reception and no IMIE, i done a full wipe and installed a different rom which was N7105, but i still have no IMIE number or anything else.
Please help someone!!!
MrLarner said:
Did you get it sorted?
I've gone and done the same thing
i installed a N7100 rom onto my N7105 note.
and after realising i had no reception and no IMIE, i done a full wipe and installed a different rom which was N7105, but i still have no IMIE number or anything else.
Please help someone!!!
Click to expand...
Click to collapse
I did the same thing previously..
Full wipe..
install n7105 rom
install you modem and csc..
everything ok thereafter..
hope it helps
TRY THIS !!!!!!
Hi,
Please try this. Download N7105 ROM you like. Copy it to internal or external card
1) Download modem & CSC file from this thread http://forum.xda-developers.com/showthread.php?t=2031575, Uk based or anyother country ROM based from zip file through CWR.
2) Delete cache, delvik cache & wipe to factory reset
3) Install ROM
TMK
For anyone else who has had this problem, send a PM to aukhan who is on here, the bloke is amazing.
He helped me sort mine out step by step and had it back up and running in no time.
top top bloke.
Related
My deepest apologies if this is not in the right place. I have been fighting with this for two days now with no luck.
I'm trying to install Cyanogenmod in my Samsung Galaxy S 2. I have followed Cyanogenmod's Wiki (erm, I was linking to the guide here but the site won't let me, so my apologies), step by step by step every time, but:
1) This guide is awful. Clockwork recovery can't see my SD card, so I have to put the files in the phone's memory itself.
2) I have tried to do both methods tried there: The first method gives me this error:
assert failed: get prop("ro.product.device" == "click" || getprop("ro.build.product" == "click" || getprop("ro.product.board" == "click"
E:Error in /sdcard/update-cm-7.1.0-click-GalaxyS-signed.zip
(Status 7)
Installation aborted.
And the second one gives me a "File not Found" after a short while. WTF.
I really want to try Cyanogenmod. I have Googled for this problem but unfortunately I have only seen HTC owners with this problem, so I'm afraid their fixes are specific for HTC phones. Any help to install Cyanogenmod will be highly appreciated.
Are you trying to install stable or nightly 116?
An Stable release. There's only stable under the S2's page and lots of Nightlies.
I would link you directly to the page that has the one I'm trying to install, but the forum won't let me until I get around 8 posts. Sorry
Looks like you're trying to install something which is named for Samsung Galaxy S and has an assert check for the HTC Tattoo Click, rather than anything to do with the Samsung Galaxy S II.
Follow the instructions in the first post of [NIGHTLY][ROM][GWK74] CyanogenMod 7 (w/ Gingerbread 2.3.7) for Galaxy SII Q&A if you have an I9100.
Thanks a LOT. That worked. I just hope it's not too unstable or buggy since I am using a nightly build.
I appreciate your help a lot!
Leonne said:
My deepest apologies if this is not in the right place. I have been fighting with this for two days now with no luck.
I'm trying to install Cyanogenmod in my Samsung Galaxy S 2. I have followed Cyanogenmod's Wiki (erm, I was linking to the guide here but the site won't let me, so my apologies), step by step by step every time, but:
1) This guide is awful. Clockwork recovery can't see my SD card, so I have to put the files in the phone's memory itself.
2) I have tried to do both methods tried there: The first method gives me this error:
assert failed: get prop("ro.product.device" == "click" || getprop("ro.build.product" == "click" || getprop("ro.product.board" == "click"
E:Error in /sdcard/update-cm-7.1.0-click-GalaxyS-signed.zip
(Status 7)
Installation aborted.
And the second one gives me a "File not Found" after a short while. WTF.
I really want to try Cyanogenmod. I have Googled for this problem but unfortunately I have only seen HTC owners with this problem, so I'm afraid their fixes are specific for HTC phones. Any help to install Cyanogenmod will be highly appreciated.
Click to expand...
Click to collapse
I'm having this same issue but im using the correct Cyanogenmod.zip file. Here is the steps that i took to get me here...
I have CWM installed and my phone (AT&T Samsung Galaxy S2 SGH-i777) has been rooted
1.) Downloaded the .zip file for Cyanogenmod 7.1 "update-cm-7.1.0-GalaxyS2-signed"
2.) Went into mass storage mode and stored .zip file in usbstorage folder.
3.) Went into recovery mode and wiped data and cache.
4.) Installed Cyanogenmod but did NOT install a second time...the guide i was using at the time did not tell me to do this...
5.) Got stuck in boot mode so i went back into CWM recovery to restore my phone with a previous backup. Restored phone to previous backup. The backup was done after i rooted my phone.
Now when i goto install Cyanogenmod i get the same errors as the user above. I've redownloaded the .zip a couple times and put it back on my phone with no luck...any ideas?
stratdude83 said:
I have CWM installed and my phone (AT&T Samsung Galaxy S2 SGH-i777) has been rooted
<snip>
any ideas?
Click to expand...
Click to collapse
You do not have an I9100, you have an I777.
oinkylicious said:
You do not have an I9100, you have an I777.
Click to expand...
Click to collapse
Yes, completely different phone.
"galaxys2" = GT-I9100
stratdude83, you might want to try here: http://download.cyanogenmod.com/?device=galaxys2att but please verify before flashing anything. Only 20 nightlies, so do some searching to see if it's "stable".
It says that is my phone model "SGH-i777" but it also shows GT-I9100 when it boots up...not the same thing?
stratdude83 said:
It says that is my phone model "SGH-i777" but it also shows GT-I9100 when it boots up...not the same thing?
Click to expand...
Click to collapse
I've never held the SGH-i777; In this section of the forum however the vast majority of people will have the "International Version" of the Galaxy SII, there are some that have an extra letter in the model that are identical (e.g. my phone is (err...was) a GT-I9100M), but aside from the M that the carrier felt they had to add it was the same in every other way, there are others as well. Some phones with other letters following the model number are different; the GT-I9100G for example.
Did/does your phone say GT-I9100 when you're on the stock ROM, or was this just after flashing CM7 and getting stuck on the boot screen? It's just an image and if you're somehow stuck with the incorrect one now (I can't recall whether this is saved in a back up, I don't think it is) you can find the appropriate param.lfs file to get back to normal. I've used Hellcat's K-Tool to replace my boot logo image, I'm not sure whether your phone is supported by that app.
Finally after fiddling with the situation for what seemed like forever ive narrowed it down to the .zip file i downloaded. Still dont really understand why this was the issue since i got it directly from Cyanogenmod.com...perhaps another thread
I used the guide posted GalaxyS2root.com. I can't post the link because im new...but goto GalaxyS2root.com -> AT&T Galaxy S2 ROMs then scroll down to the very bottom and you'll see "CyanogenMod 7.1 ROM for Rooted AT&T Galaxy S2! [SGH-i777]" follow this guide and use the .zip files from here.
Transfer both Google apps (if you want it) and the Cyanogenmod .zip files onto your internal memory and install from CWM recovery mode. Look up "Samsung galaxy s2 mass storage mode" (its easy).
Now follow the guide but you will most likely have to install the Cyanogen .zip file twice. If you get stuck at the Samsung boot image after the first install then install Cyanogen again and everything will work. Don't clear your cache or data again. Only do this the first time you install Cyanogenmod.
There's also instructions at the CyanogenMOD wiki site as well as on XDA.
Here's the nightlies Development thread for the AT&T version in the SGH-I777 forum: http://forum.xda-developers.com/showthread.php?t=1286192
Enjoy CM7, I can't go back to a Samsung ROM now.
mudferret said:
There's also instructions at the CyanogenMOD wiki site as well as on XDA.
Here's the nightlies Development thread for the AT&T version in the SGH-I777 forum: http://forum.xda-developers.com/showthread.php?t=1286192
Enjoy CM7, I can't go back to a Samsung ROM now.
Click to expand...
Click to collapse
You like it that much? I dont know im kindof torn i guess...yea Cyanogenmod has cool stuff but i like the Touchwiz and UI of the stock Samsung more...i guess for me i figured im not really going to utilize the ROM as much as i thought in the first place...or i dont even realize its full capability yet
stratdude83 said:
You like it that much? I dont know im kindof torn i guess...yea Cyanogenmod has cool stuff but i like the Touchwiz and UI of the stock Samsung more...i guess for me i figured im not really going to utilize the ROM as much as i thought in the first place...or i dont even realize its full capability yet
Click to expand...
Click to collapse
If you came from a stock ROM it's a big jump, and you "lose" a lot. CM7 = ~100MB, stock ROM = ~5x that size, a lot is related to system structure, but much is manufacturer app related. I "worked" my way to it. A modified stock ROM removes varying degrees of apps typically. I moved from lighter ROM to lighter ROM ending up at CM7, and even Insanity which is CM7 based but 47MB.
A lot of the stock apps I'd previously missed weren't doing much for me in hindsight, currently my phone does everything I require. I won't dispute that it's not a one size fits all ROM.
stratdude83 said:
It says that is my phone model "SGH-i777" but it also shows GT-I9100 when it boots up...not the same thing?
Click to expand...
Click to collapse
Always follow what it says on the label on the phone underneath the battery. That tells you what hardware it has. Whatever it shows when it boots is just the software version. Someone could easily change the GT-I9100 text it shows at boot to "Your Crappy Phone".
Hi All,
I am facing the same issue with GT-I9100G and flashing the firmware twice does not. Please help me out here
[SOLVED!!]
i have this problem too when i want to install some roms like AOKP and JB 4.2.2 , i get same error !!
just go to recovery mode cwm then
go to mount and storage ---> unmount /system
now format /system and /data
try agian install cm rom , and it'l work :good:
Hey everyone!
This is my first time posting on the forums.
I am attempting to install CyanogenMod 10.1.3 on my S2, using the instructions on the CyanogenMod site. I am using the latest stable build, however, the install keeps failing. It says
assert failed: getprop("ro.product.device") == i777"
a bunch of times and then
E:Error in /sdcard/cm-10.1.3-i777.zip
(Status 7)
Installation aborted.
I have to restore my previous device status to get it to boot up again. Any help would be greatly appreciated! Thanks in advance for your time
from recovery:
factory reset, format /system.
flash firmware.
the existing stuff that's left over in the /system tends to bork up installs for me.
I consider it the real magic behind a true "full wipe"
edit: welcome.
thanks for the quick response!
I tried wiping /system and reinstalling but still got the same error.
nicholasglesmann said:
thanks for the quick response!
I tried wiping /system and reinstalling but still got the same error.
Click to expand...
Click to collapse
Then I'd advise ODIN flashing back to stock ucmd8, then start the process over (root, cwm, full wipe, flash away)
I'm out of suggestions after that one.
Status 7 has nothing to do with recovery, the rom you're flashing is looking for a device specific description. All you need to do is delete all of the GETRO= lines in the build prop and then the rom will flash.
Also, please search before you post; this issue has been covered so many times a new thread is not necessary. There are several posts here that can give you more details on editing the build prop, just spend a few extra minutes to find them.
Sent from the i777
I´m on S3 International and have flashed Philz Recovery with ODIN and flashed Wanam latest 4.3. Works great! I have even flashed the S4 launcher and weatherwidget and all is still well.
However, now I want to try to run MIUI on my S3. After backing up my S3 and started to flash I got Error Status 7. I have read some threads about it and the first I wanted to try was to install another recovery. But even when I flash another recovery I get Error Status 7. I suddenly can´t flash anything at all. Does this have to do with the fact that I ticked the "disable recovery flash" when exiting the Philz recovery after starting this journey when beginning to root and so on? If so... how do I get it "unticked"?
First up...
Will flashing another recovery (CWM for example) help me get past this Status 7 problem?
Second...
If I descide to flash CWM Recovery via ODIN will it reset my current ROM in any way or will everything stay the same?
Third...
I read somewhere that I can modify the updater-script in the META-folder. Is that really a afe way to go about it? It feels kind of wierd when the *.zip´s are made for the right phone, model, version and so on...
Thanx for the help, guys!
Manneman32 said:
I´m on S3 International and have flashed Philz Recovery with ODIN and flashed Wanam latest 4.3. Works great! I have even flashed the S4 launcher and weatherwidget and all is still well.
However, now I want to try to run MIUI on my S3. After backing up my S3 and started to flash I got Error Status 7. I have read some threads about it and the first I wanted to try was to install another recovery. But even when I flash another recovery I get Error Status 7. I suddenly can´t flash anything at all. Does this have to do with the fact that I ticked the "disable recovery flash" when exiting the Philz recovery after starting this journey when beginning to root and so on? If so... how do I get it "unticked"?
First up...
Will flashing another recovery (CWM for example) help me get past this Status 7 problem?
Second...
If I descide to flash CWM Recovery via ODIN will it reset my current ROM in any way or will everything stay the same?
Third...
I read somewhere that I can modify the updater-script in the META-folder. Is that really a afe way to go about it? It feels kind of wierd when the *.zip´s are made for the right phone, model, version and so on...
Thanx for the help, guys!
Click to expand...
Click to collapse
You didn't mention the version of Philz you were using. Anyway, the error 7 can be caused from 2 main reasons:
1- Older recovery version. Flash the lastest recovery available (6.15.4) and try again: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300
2- Corrupted rom download.
To your 2nd question- if it doesn't work with Philz, it will not work with any other recovery.
Well... when I asked about how to go about rooting just a week ago I got links to what I needed. And with that I got a link to Philz Recovery. But now I see that it was an old version (6.07.9)
I´ll try with the latest one and see where that takes me.
Edit:
Flashed the latest Philz and took a new backup just in case. It didn´t work. Still Status 7. So I re-downloaded the ROM just in case it was corrupted but still the same... aborted Status 7.
So... now what? Am I screwed?
I read somewhere that it could have something to do with the fact that I use an external SD-card. Will it really make a difference if I flash it from the internal memory and even if i take the SD out of the phone?
Manneman32 said:
I read somewhere that it could have something to do with the fact that I use an external SD-card. Will it really make a difference if I flash it from the internal memory and even if i take the SD out of the phone?
Click to expand...
Click to collapse
Worth the try
Here 2 relevant threads I found:
http://en.miui.com/thread-6429-1-1.html
Follow galnet post (page 7):
http://forum.xda-developers.com/showthread.php?t=1749392&page=7
Sent from my GT-I9300 using Tapatalk
So... the links refer to downgrading to a really old recovery used for rooting with CF or unticking the "disable signature check" ... feels strange.
Is there anyway to explain why this error occurs?
Last question before giving this up...
If I should downgrade my recovery, is that safe? And how will it work with downgrading from a 4.3 ROM to a 4.1.1 ROM. Is this nothing to be concerned about?
// Manneman
Manneman32 said:
Last question before giving this up...
If I should downgrade my recovery, is that safe? And how will it work with downgrading from a 4.3 ROM to a 4.1.1 ROM. Is this nothing to be concerned about?
// Manneman
Click to expand...
Click to collapse
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
My phone is currently on the stock 4.1 ROM, rooted (unlocked, S-OFF). I've tried both TWRP 2.7.1.0 (both via Fastboot and via GooManager) and CWM 6.0.4.8, and neither detect my ROM and neither can flash any other ROMs (Viper, Cyanogenmod, MIUI...)
The error I get during install on both TWRP and CWM is as follows:
"assert failed: getprop("ro.product.device") == "supersonic" || getprop("ro.build.product") == "supersonic"
E: Error in /(rom location here)
(Status 7)
Installation aborted.
The "supersonic" readout makes me think that for whatever reason, my recovery is incorrectly identifying my device as something else... Every time I try to recover my stock ROM via backup on TWRP, it restores it however when I try to reboot it thinks there is no OS on the phone, and wants to install SuperSU (thinks the phone is unrooted).
Also, on a side note - My phone is not detected by either Windows or Mac (various machines). The only machine that can access my phone storage is my Linux PC at work.
This is incredibly frustrating and I'd really like to avoid buying a new phone if possible... If anyone can help me with this I would GREATLY appreciate it.
EDIT: Also, even when I format ALL partitions on the internal SD (Dalvik, Cache, Factory Reset, etc) the phone actually still boots to a stock install of the stock ROM (wants to run the "first time setup" again). This is making me think that both TWRP and CWM are also not correctly formatting my phone as it should.
The ROM you are trying to flash to your device is for the old EVO 4G, not the EVO 4G LTE.
It's a good thing that assert line was in there; it kept you from jacking up your device .
Get a ROM for this device from the correct forum and it should work fine.
Depending on what ROM you want to flash, you might also need an alternate version of TWRP. CWM for this device isn't recommended.
Captain_Throwback said:
The ROM you are trying to flash to your device is for the old EVO 4G, not the EVO 4G LTE.
It's a good thing that assert line was in there; it kept you from jacking up your device .
Get a ROM for this device from the correct forum and it should work fine.
Depending on what ROM you want to flash, you might also need an alternate version of TWRP. CWM for this device isn't recommended.
Click to expand...
Click to collapse
Thanks, but I get the same error on Viper 4.0 and Cyanogenmod as well. On both TWRP and CWM.
Also, even though on the MIUI website it lists this ROM under just "EVO 4G", the image they're using is for the LTE... I can't imagine them making a 4.0 ROM for an Evo 4G, I'm pretty sure they just mis-labeled the category.
strange world said:
Thanks, but I get the same error on Viper 4.0 and Cyanogenmod as well. On both TWRP and CWM.
Also, even though on the MIUI website it lists this ROM under just "EVO 4G", the image they're using is for the LTE... I can't imagine them making a 4.0 ROM for an Evo 4G, I'm pretty sure they just mis-labeled the category.
Click to expand...
Click to collapse
Viper 4.0 is built for the updated partition layout. You'd still have to use a different TWRP.
CM has updates that require a different TWRP version.
There is no official MIUI build for the EVO LTE. It probably IS for the Supersonic.
Again, stay away from CWM. It's possible your misc partition got hosed depending on how long you've been using it.
So what exactly is your goal at this point? I'd recommend flashing the 3.17 stock rooted ROM, or running the 3.17 RUU (if you want to stay on 4.1 & the old layout), or running the 4.3 RUU which will let you run Viper 4.0.
EDIT: The RUU route is probably the best way to go. It should clean up any issues your device may currently have. Though if your misc partition is corrupted, you'll need to fix that first. There's information on that in the old CWM thread.
Captain_Throwback said:
Viper 4.0 is built for the updated partition layout. You'd still have to use a different TWRP.
CM has updates that require a different TWRP version.
There is no official MIUI build for the EVO LTE. It probably IS for the Supersonic.
Again, stay away from CWM. It's possible your misc partition got hosed depending on how long you've been using it.
So what exactly is your goal at this point? I'd recommend flashing the 3.17 stock rooted ROM, or running the 3.17 RUU (if you want to stay on 4.1 & the old layout), or running the 4.3 RUU which will let you run Viper 4.0.
EDIT: The RUU route is probably the best way to go. It should clean up any issues your device may currently have. Though if your misc partition is corrupted, you'll need to fix that first. There's information on that in the old CWM thread.
Click to expand...
Click to collapse
Thank you; I'll flash my recovery back to TWRP 2.7.1.0. Would I be able to install the RUU 4.3 update however through Windows since my phone is still unable to be read by the machine? I'm not sure if it's a driver issue; I've tried installing/reinstalling HTC Sync.
I'll try flashing the 2.7.1.0B TWRP.
Edit: Using a different Windows PC (at work) I was able to connect my phone. I ran the RUU 4.3 update which (reported) flashing correctly. I'm now going to poke around my phone and see where that left me.
Edit2: I'm on 4.13 now Feels much better than the old version... Thank you for your help. Now I need to decide if Just want to count my blessings and stay on this ROM or try out something else.
Hello everyone,
I'm having problems when I'm trying to install 4.4 roms I keep getting this error
set_metadata_recursive: some changes failed
E:Error in/sdcard/cyanaosp-v3.4.0_2.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
After looking into it most people say it's cause by old cwm version. However I couldn't find a newer version of cwm for my vibrant.
I currently have semaphore cwm recovery v6.0.3.8
Please help
SoulEater- said:
Hello everyone,
I'm having problems when I'm trying to install 4.4 roms I keep getting this error
After looking into it most people say it's cause by old cwm version. However I couldn't find a newer version of cwm for my vibrant.
I currently have semaphore cwm recovery v6.0.3.8
Please help
Click to expand...
Click to collapse
Have you tried reflashing right after that error? Please do so. Worked here.
CWM version doesn't have to do much if at all with this if you are above 6.0.0.0. Sometimes I use a March 2014 kernel (Semaphore) which has an older CWM (still above 6.0) and everything flashes just fine.
@nirogu325
Quick question for you that I didn't want to put in the CM11 thread. I have my old Vibrant that I gave to my son and it has Slim 4.3 build 1, Semaphore and CWM 6.0.3.8 on it. I wanted to put him on CM11 but when I flash it I get a Status 7. Normally, I know how to get around this but for some reason it is not letting me flash it because it says that my device is a I-9000. I've checked Settings>About Phone and it shows T959 and I've even checked my build.prop and nowhere does it say I-9000. The only thing that I have from the I-9000 is the GB Bootloaders.
Any ideas?
Woody said:
@nirogu325
Quick question for you that I didn't want to put in the CM11 thread. I have my old Vibrant that I gave to my son and it has Slim 4.3 build 1, Semaphore and CWM 6.0.3.8 on it. I wanted to put him on CM11 but when I flash it I get a Status 7. Normally, I know how to get around this but for some reason it is not letting me flash it because it says that my device is a I-9000. I've checked Settings>About Phone and it shows T959 and I've even checked my build.prop and nowhere does it say I-9000. The only thing that I have from the I-9000 is the GB Bootloaders.
Any ideas?
Click to expand...
Click to collapse
Status 7 sometimes tends to be the assert lines inside the ROM .zip. Check inside the zip (I use 7Zip on my PC): META-INF > com > google > android > updater-script. Check in that script (I use Notepad++ on my PC) the first lines. In the picture I attached, I show you an example of the assert lines. Delete those if present. If that doesn't yield resuls, it could be the GB Bootloader. Although I could flash the newer CM builds with them by deleting the assert lines I showed you. I no longer have the GB Bootloader, so I had to flash my way through JFD to ICS and then to KK again.
nirogu325 said:
Status 7 sometimes tends to be the assert lines inside the ROM .zip. Check inside the zip (I use 7Zip on my PC): META-INF > com > google > android > updater-script. Check in that script (I use Notepad++ on my PC) the first lines. In the picture I attached, I show you an example of the assert lines. Delete those if present. If that doesn't yield resuls, it could be the GB Bootloader. Although I could flash the newer CM builds with them by deleting the assert lines I showed you. I no longer have the GB Bootloader, so I had to flash my way through JFD to ICS and then to KK again.
Click to expand...
Click to collapse
I just did it in Root Explorer. Anyways what I did was I deleted those Assert lines, rezipped it up and flashed. Got a failure due to partition errors (probably because for some reason it was still reading as an I-9000) and said if I wanted to continue to reflash the package. So I flashed my "rebuilt" package and gapps. Was faced with the Set-Up Wizard FC issue, so I thought that maybe I would try to reflash the unaltered CM11 zip to see if it fixed it (before I searched for the solution). It went through the first time with no errors. Still have the Set-Up FC issue, but once I get in my house where there is wifi (no sim in this phone), I can fix that right up, cause I know how to use the search function.
Anyways, thanks for your help. If it came down to it, I would have flashed the Froyo BLs, but this was just as easy. If the next time the ROM updates and I can't get past that, I may have to flash them but I doubt it since I "sort of" tested that philosophy with my reflash from above.
Woody said:
I just did it in Root Explorer. Anyways what I did was I deleted those Assert lines, rezipped it up and flashed. Got a failure due to partition errors (probably because for some reason it was still reading as an I-9000) and said if I wanted to continue to reflash the package. So I flashed my "rebuilt" package and gapps. Was faced with the Set-Up Wizard FC issue, so I thought that maybe I would try to reflash the unaltered CM11 zip to see if it fixed it (before I searched for the solution). It went through the first time with no errors. Still have the Set-Up FC issue, but once I get in my house where there is wifi (no sim in this phone), I can fix that right up, cause I know how to use the search function.
Anyways, thanks for your help. If it came down to it, I would have flashed the Froyo BLs, but this was just as easy. If the next time the ROM updates and I can't get past that, I may have to flash them but I doubt it since I "sort of" tested that philosophy with my reflash from above.
Click to expand...
Click to collapse
The Setup Wizard FC only occurs if you flash everything at once (ROM + GApps). It's been happening since 4.4.4 was released a month ago. To bypass that you either:
1. Lower the notification panel and press the date on the upper left side. Calendar should open prompting you to enter your Google credentials along with Wi-Fi if not connected. Do so, then tap Back until you go back to the Setup Wizard. No more FC.
OR
2. Flash the ROM alone without GApps. Let it settle for 10 minutes after boot. Then you proceed to flash everything else.