Hi i've been reading alot of from the other threads in galaxy 2 and galaxy note regarding the super brick bug.
I just experience a boot loop issue yesterday was afraid that i was affected since according to the Got Brick and eMMC brick bug check our chip is also affected. I ran the check memory test for 10 minutes and it passed.
I wonder if were affected and what needs to be done to prevent the super brick bug.
thanks.
{
"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"
}
We are in fact plagued by the same ICS brick bug that other Galaxy devices have been experiencing. Correct me if I'm wrong, but the brick bug seems to affect devices flashed with *UNOFFICIAL/LEAKED* firmware. Officially supported ROMs seem to be the only exemption, although, I would still exercise caution in anything you flash. Keep in mind there's always a risk with flashing, and this brick bug just adds more to that risk. The issue has been looked at ever since it was discovered, but I don't think much has been found as to what causes it yet.
Sent from my SPH-L710 using xda premium
So, till then it's better not to flash i think? Untill this is sorted out?
Verstuurd van mijn GT-P6210 met Tapatalk
hmm what about us who already flashed our tabs to ICS(open austria)?
do we need to downgrade to HC for the time being and wait for the official ICS thru Kies?
or can we still go on using ICS?
aperture said:
hmm what about us who already flashed our tabs to ICS(open austria)?
do we need to downgrade to HC for the time being and wait for the official ICS thru Kies?
or can we still go on using ICS?
Click to expand...
Click to collapse
Just don't use ICS recovery (Recovery 3e) to wipe data/factory reset.
Everything will good.
Sent from my GT-P6200 using Tapatalk 2
I'm gonna wait, i got ICS already installed trough Odin and it works well so far. Think i was lucky that it worked. I don't really need to flash any other rom (for now) until there is a fix i guess.
Verstuurd van mijn GT-P6210 met Tapatalk
And how's the news that the problem for Galaxy Note's is caused by temp touch CWM ?
That's good news, now we know what the problem is. But how do we fix it? I'm still in "danger"
Verstuurd van mijn GT-P6210 met Tapatalk
giangp1 said:
Just don't use ICS recovery (Recovery 3e) to wipe data/factory reset.
Everything will good.
Sent from my GT-P6200 using Tapatalk 2
Click to expand...
Click to collapse
As far as i remember i reflashed to ICS thrice and did wipe data/factory reset thrice also under ICS recovery.
Do these hard bricks happen immediately or in a certain amount of factory resets in ics recovery?
aperture said:
As far as i remember i reflashed to ICS thrice and did wipe data/factory reset thrice also under ICS recovery.
Do these hard bricks happen immediately or in a certain amount of factory resets in ics recovery?
Click to expand...
Click to collapse
They seem to just randomly happen. Could be the first wipe, could be the 5th wipe, there's no exact number. These "wipes" corrupt certain partitions on our device, which is what leads to the hard bricks.
Sent from my SPH-L710 using xda premium
Ceelos09 said:
They seem to just randomly happen. Could be the first wipe, could be the 5th wipe, there's no exact number. These "wipes" corrupt certain partitions on our device, which is what leads to the hard bricks.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Trust me, it can happen the first time.. I found out the hard way, but it only seems to happen on the ics 3e recovery, I believe hc is fine
Sent from my myTouch 4g via Tapatalk
Check this post from Entropy:
http://forum.xda-developers.com/showthread.php?p=27074278
Enviado de meu GT-P6210 usando o Tapatalk 2
So if I understand correctly, only the stock recovery is affected, and possibly the temporary CWM. So, if I'm on the permanent CWM, I shouldn't have to worry, correct?
big Bro is watching...
giangp1 said:
Just don't use ICS recovery (Recovery 3e) to wipe data/factory reset.
Everything will good.
Sent from my GT-P6200 using Tapatalk 2
Click to expand...
Click to collapse
wait.. what? are u talking about the stock ICS recovery? bcos ive done factory reset like 5 times now.. i havent had any issue so far regarding the bug. im running ICS (open austrian) version.
Well I am totally confused. Now :/ I guess we are also affected as the d brick is related to exynos chip. Its still unclear how to avoid this problem.. I used the app by chainfire tto check vulnerable emmc Chip and it says mine is also under risk.
Sent from my GT-P6200 using xda app-developers app
Well there's no "fix" from samsung as they won't recognize this because they say that wiping from stock recovery with no modifications and or root its safe.. That said they won't modify the MMC_CAP_ERASE command to only perform an insecure erase when wiping that's the way it was in gingerbread and honey comb. (Google made mandatory to perform a secure erase command starting from ics)
The thing it's that emmc chip can't handle the secure erase commands and while samsung keeps sending the secure erase command through MMC_CAP_ERASE procedure we will be in risk of super bricking the device.
Custom kernels (including cm9 kanged) should HAVE the MMC_CAP_ERASE command disabled in order to be safe and wipe all the times we want as by disabling MMC_CAP_ERASE the system won't performs any kind of formats or deletions...
I think that the only way to be really safe its either getting back to HC or flashing MMC_CAP_ERASE disabled kernels but seems like there's not much development for this device...
I haven't read/tried the CM9 kang but I guess I'll ask the developer if he can or in fact did disabled MMC_CAP_ERASE from the kernel.
Sent from my GT-P6200 using Tapatalk 2
msedek said:
Well there's no "fix" from samsung as they won't recognize this because they say that wiping from stock recovery with no modifications and or root its safe.. That said they won't modify the MMC_CAP_ERASE command to only perform an insecure erase when wiping that's the way it was in gingerbread and honey comb. (Google made mandatory to perform a secure erase command starting from ics)
The thing it's that emmc chip can't handle the secure erase commands and while samsung keeps sending the secure erase command through MMC_CAP_ERASE procedure we will be in risk of super bricking the device.
Custom kernels (including cm9 kanged) should HAVE the MMC_CAP_ERASE command disabled in order to be safe and wipe all the times we want as by disabling MMC_CAP_ERASE the system won't performs any kind of formats or deletions...
I think that the only way to be really safe its either getting back to HC or flashing MMC_CAP_ERASE disabled kernels but seems like there's not much development for this device...
I haven't read/tried the CM9 kang but I guess I'll ask the developer if he can or in fact did disabled MMC_CAP_ERASE from the kernel.
Sent from my GT-P6200 using Tapatalk 2
Click to expand...
Click to collapse
So were stuck on danger bug for now. I hope somebody can create a safe kernel for this. I'm getting problem's with more force closes on apps but i don't dear to do a factory reset or wipe for clean install. Don't know what to do
Verstuurd van mijn GT-P6210 met Tapatalk
Terrandroid said:
So were stuck on danger bug for now. I hope somebody can create a safe kernel for this. I'm getting problem's with more force closes on apps but i don't dear to do a factory reset or wipe for clean install. Don't know what to do
Verstuurd van mijn GT-P6210 met Tapatalk
Click to expand...
Click to collapse
Flash jelly bean/CM10 the CWM and the cm9/CM10 kernels has he MMC_CAP_ERASE disabled.. So you can wipe all you want safely
Enviado desde mi GT-P6200 usando Tapatalk 2
In order to flash cm 9 it clearly says perform factory wipe and clear cache.. I am using aaorths CMW 6.0.10 which he claims is safe. But is d combination of stock ics rom and cmw safe is the doubt.
Sent from my GT-P6200 using tapatalk 2
Related
Since I see this is the most annoying thing people keep complaining about. Yet I dont know why anyone shutdown there phone and cares.. Just saying
Common ICS leak bug: shutdown/Reboot "stick"
Fixes: try whatever you want
1. Pull battery after first boot
2. Superwipe before installing my superlite
3. After install take a nandriod backup and reload that backup
4. Using adb
adb shell rm /system/app/shutdown.apk
OR
Using Root Explorer:
Set RW and remove /system/app/shutdown.apk
Reboot(even if you have to pull battery)
I see some willy-nilly thank you's but nobody responding to say if it worked for them or not.
Didn't work for me
sgh-i727r
{
"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"
}
---------
---------
---------
---------
I tried. I really did.
you make me laugh
<installing android source> bbl.
So does this work or not?
Didn't work for me. After the leak was installed, my phone would shut down just fine. It was only after I rooted it that it would not shut down.
Just make a tibu backup of the app then un install it. I'm running mhx's ics rom and I don't have the issue anymore. I couldn't reboot on my previous 3 flashes so MHX must be doing something right.
Swyped from my Galaxy S2 Skyrocket using XDA premium
Well whatever the fix does or doesn't do with other ROM's, it appears to be working great [already built in] on MHX's ICS ROM found here:
http://forum.xda-developers.com/showthread.php?t=1573621
Did not work for me
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2 Beta-5
bts0uth said:
Just make a tibu backup of the app then un install it. I'm running mhx's ics rom and I don't have the issue anymore. I couldn't reboot on my previous 3 flashes so MHX must be doing something right.
Swyped from my Galaxy S2 Skyrocket using XDA premium
Click to expand...
Click to collapse
CZ Eddie said:
Well whatever the fix does or doesn't do with other ROM's, it appears to be working great [already built in] on MHX's ICS ROM found here:
http://forum.xda-developers.com/showthread.php?t=1573621
Click to expand...
Click to collapse
I'm confused.. you're saying this didn't work but mhx is doing something right with his rom. mhx is the op..
I am on 4.2 ICS-Superlite and i still have the issue on SGH-I727R :/
The issue went away for me with 4.2 Super lite. I even went all the way back to GB on 2.3.5 to get rid of that blasted thing on my i727. What process are you using?
Sent from my SAMSUNG-SGH-I727 using xda premium
btm fdr said:
I'm confused.. you're saying this didn't work but mhx is doing something right with his rom. mhx is the op..
Click to expand...
Click to collapse
It isn't working for some other peoples custom ICS ROM's, but MHX's custom ICS ROM isn't having any shutdown problems.
CZ Eddie said:
It isn't working for some other peoples custom ICS ROM's, but MHX's custom ICS ROM isn't having any shutdown problems.
Click to expand...
Click to collapse
I guess i'll have to retry a flash then :/ it's still doesn't work for me even if I am on ICS-Superlite 4.2
I'll post back the results!
chokesmaster said:
I guess i'll have to retry a flash then :/ it's still doesn't work for me even if I am on ICS-Superlite 4.2
I'll post back the results!
Click to expand...
Click to collapse
I reset factory data/ wiped cache & davlik three times each..
Then wiped all the mounted devices except EMMC.
Then ran Dark's Super cleaner thingy wipe.
Then ran a kernel cleaner.
Then flashed 4.2.
Then flashed ROMracer's exploited kernel twice.
Then reset to factory data, cleared cache & davlik again.
Then booted up and left it alone for five minutes before touching anything.
Hope that works for you!
It's how I flash all my ROM's these days.
Though I just started wiping factory data afterwards.
CZ Eddie said:
I reset factory data/ wiped cache & davlik three times each..
Then wiped all the mounted devices except EMMC.
Then ran Dark's Super cleaner thingy wipe.
Then ran a kernel cleaner.
Then flashed 4.2.
Then flashed ROMracer's exploited kernel twice.
Then reset to factory data, cleared cache & davlik again.
Then booted up and left it alone for five minutes before touching anything.
Hope that works for you!
It's how I flash all my ROM's these days.
Though I just started wiping factory data afterwards.
Click to expand...
Click to collapse
Which kernel cleaner are you using? I remember using one for my Captivate that said something about being compatible with all Samsung devices. I've only used darkside's superwipe so far though.
Sent from my SAMSUNG-SGH-I727 using XDA
CZ Eddie said:
I reset factory data/ wiped cache & davlik three times each..
Then wiped all the mounted devices except EMMC.
Then ran Dark's Super cleaner thingy wipe.
Then ran a kernel cleaner.
Then flashed 4.2.
Then flashed ROMracer's exploited kernel twice.
Then reset to factory data, cleared cache & davlik again.
Then booted up and left it alone for five minutes before touching anything.
Hope that works for you!
It's how I flash all my ROM's these days.
Though I just started wiping factory data afterwards.
Click to expand...
Click to collapse
Which kernel cleaner did you run? Do you have a link?
Duh, q's been asked already....I was good until I cleared cache then I got the shutdown lockup. Now I'm looking for a fix because I got everything the way I like it. Not a big deal though but would be nice to fix.
EDIT: SUCCESS
This is the darkside wipe:
http://forum.xda-developers.com/showthread.php?t=1487706
And this is the kernel cleaner:
samsung_ultimate_kernel_cleaning_script_by_lippol94.zip
I don't remember exactly where I got it from. But I think it was this thread:
http://forum.xda-developers.com/showthread.php?t=1166954
The filename is the same as what I'm using.
And it's mentioned in seanszreamz thread.
http://forum.xda-developers.com/archive/index.php/t-1377087-p-11.html
Got it fixed with NexusMod ICS Beta 3 + Dark side super wipe
Apologies for not actually being a helpful contributor to the actual problem of unlocking the Verizon Galaxy S3 bootloader, but I came across this one time after booting my phone after replacing the battery
{
"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"
}
The Samsung logo, with an icon of an unlocked padlock, and the word "Custom" (this is the very first boot screen, before the boot animation and the Galaxy S3 logo), so it's the bootloader screen.
The only way I can replicate this is by taking out the battery and replacing it. Simply rebooting the phone does not show the icon. I suppose this could have been due to one of three things:
(all as directed by http://forum.xda-developers.com/showthread.php?t=1756885 for reference )
flashing the rooted boot image using Odin
installed custom Clockworkmod recovery
flashed custom boot image
Everything still boots properly, I don't have a brick. Is anyone else experiencing this that perhaps didn't follow these three steps?
A lot of people have been reporting this. Sometimes its completely random, sometimes can be replicated. Seems to be related to recovery image afaik, however some have reported being 100% bone stock and getting it. Its absolutely nothing to worry about.
Sent from my Galaxy S3 using Tapatalk 2
I wasn't worrying about it, as I said, the phone still boots completely fine, I was wondering if it was indicative of something unusual with the bootloader (such as the impossible chance of it actually being unlocked) or if it was reported by a large number of users.
I literally just saw that on my phone for the first time about 2 hours ago..... im having major issues right now from deleting busybox i guess the "wrong way"... this is my first time posting on this site, though i have read it for years, anyones help or advice would be appreciated......
I came across this image when i would hold the power button then hit restart and that image came up.... only after i attemped to install chainfire 3D and deleting busybox...
Please help me out my brothers n sisters
http://forum.xda-developers.com/showthread.php?t=1830457
RealMuphukkinG said:
I came across this image when i would hold the power button then hit restart and that image came up.... only after i attemped to install chainfire 3D and deleting busybox...
Click to expand...
Click to collapse
Mm, if you're having issues booting, then I think that's something different. I wouldn't know exactly how to fix that.
I have it also.
- Installing VRALG1 rooted alone won't trigger it--in fact, I wipe, flash that, reboot to clear the "Custom" tripwire
- Installing NoSympathy VRALG1 deodexed triggered it for me, twice
- Installing blueui with metamorph triggered it (cf. http://forum.xda-developers.com/showthread.php?p=30085423)
- Installing BlueICSFull.zip (http://forum.xda-developers.com/showthread.php?t=1775235) plus some other action (like configuring/using e-mail, not sure, installing some normal app) triggered it for me
Other than giving VZW an [illegal] excuse to void your warranty, I haven't seen an issue with it.
I just started getting this last night during a reboot .
My device showed this screen right out of the box!
I've seen this after a battery pulls. I'm on my 2nd GSIII and I was worried they wouldn't refund the amount to me if that showed up.
I rooted and flashed the Synergy Rom on my GSIII, as well as my fiancee's and my brothers. My phone was the only one to display this custom lock icon (randomly). I'm pretty sure it had something to do with flashing the cwm touch, then the cwm6. To fix it, I read users gained success just by wiping cache and dalvik, but it didn't work. So I tried flashing the stock recovery instead (hearing it's a recovery issue that 'throws' some sort of flag). It didn't fix the issue. I even ODIN'd back to stock, and it still didn't fix the issue. Everything I tried didn't work.
However, after I went ahead and re-rooted using the root66 method, then installing cwm touch, and then booting into recovery, wiping system, data, cache, dalvik, performing a factor data reset, and then installing the Synergy rom (I used 1.6), (ASSUMING I was just going to have to deal with the custom lock icon forever).... it somehow magically fixed itself.
Hope that helps. Ever since then, it's worked just fine, no custom lock icon. Since then, I've booted into cwm touch, wipe cache/dalvik, and have even updated to the newest Synergy (1.7), and it's remained just fine.
Hope this helps.
I froze the SysScope process. I don't get the custom padlock at boot, but because that process can no longer communicate with the phone I do have phone status as modified.
Sent from my SCH-I535 using xda app-developers app
I found that I triggered it by changing cpu settings, doing a recovery or basically changing any system setting. I cured it by flashing stock recovery, wiping data and cache. Then I rooted again but didn't change anything and still no padlock.:thumbup:
Sent from my SCH-I535 using xda app-developers app
Broadley1 said:
I found that I triggered it by changing cpu settings, doing a recovery or basically changing any system setting. I cured it by flashing stock recovery, wiping data and cache. Then I rooted again but didn't change anything and still no padlock.:thumbup:
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem as well. By any chance was everyone here with the problem running TWRP as their recovery?
I'm bone stock and have gotten that, from time to time during reboots since release day.
Apologies for bumping an old thread....
I never had this screen before until I bought an extended battery from Gorilla Gadgets and as soon as I started using it I started getting that screen...
I did flash the Verizon stock (with root) but even then it never showed this screen until the moment I used the battery.
Does this void the warranty?
Casual root
I just did the casual ver. 795b root last night so I could stay on 4.1.2 for right now and I have this custom and unlock pic on the Samsung screen not sheer if I should do something or not?????? help if you have any ideas
Broadley1 said:
I found that I triggered it by changing cpu settings, doing a recovery or basically changing any system setting. I cured it by flashing stock recovery, wiping data and cache. Then I rooted again but didn't change anything and still no padlock.:thumbup:
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How did you flash stock recovery?
Sent from my SCH-I535 using XDA Premium 4 mobile app
XXDroidZillaXX said:
How did you flash stock recovery?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Seems like he have to root again so he probably used ODIN.
I get this and then my phone has a yellow triangle of death... I still can't figure out how to fix this as I've tried JOdin on my macbook pro with stock flash's and pit files that are corrupt apparently. Anyone else know what I can do to debrick this? I've checked the other brick posts and nothing ;\
I believe this is caused by KNOX Security being triggered - which is irreparable
I think this indicates KNOX security was triggered and therefore your phone is no longer "pure". I don't know exactly what KNOX does, but I believe it burns a fuse in your phone that locks to either a 1 or a 0 - and once it's triggered, it can't be undone.
All of this is speculation though, I suggest looking up KNOX security and see what the experts say. This happened to me a few years ago and at the time, there was no fix. I'm sure someone found a way around it by now - or at least a way to prevent or remove it completely.
please how to fix wifi. I tried many roms and kernels and every modem but the wifi still doesn't work.
how do you guys make it work? please someone answer me bcoz in my other posts nobody helped
manzifa45 said:
please how to fix wifi. I tried many roms and kernels and every modem but the wifi still doesn't work.
how do you guys make it work? please someone answer me bcoz in my other posts nobody helped
Click to expand...
Click to collapse
Give us some more info.
What rom are you currently using?
Did you follow the directions and do a factory reset before/after flashing the rom?
What else are you flashing or doing?
bhundven said:
Give us some more info.
What rom are you currently using?
Did you follow the directions and do a factory reset before/after flashing the rom?
What else are you flashing or doing?
Click to expand...
Click to collapse
CM9 with KJ6 padded modem
I followed all the instructions and now I flashed CM7 everything
work well even the wifi but I would like to have ICS thanks
Jeffsf did help you in your other post he gave you all the info needed.
That's pretty rude to say you weren't helped.
jeffsf said:
CM9 works just fine for WiFi. It is only the T-Mobile WiFi Calling feature that does not work on any ICS ROM for the SGS4G.
Changing the modem has nothing to do with the Wifi driver. It sounds like a bad flash or the way data was restored.
I'd read the Q&A thread - http://forum.xda-developers.com/showthread.php?t=1729121 and post any unanswered questions there.
Posted from my SGS4G, thanks to Team Acid development
Click to expand...
Click to collapse
There is several of your posts that where answered as well based on this same topic.
And this is what you said not long ago
i thought this phone was a good deal and now i m deceived and
this coming month i m looking to get a sony xperia, samsung is a real s*** dont
even know why people continue to compare it to the greatest iphone.
Click to expand...
Click to collapse
Shortbus-Driver said:
Jeffsf did help you in your other post he gave you all the info needed.
That's pretty rude to say you weren't helped.
Click to expand...
Click to collapse
i have tried everything, flashed every rom,every kernel,every modem given here and the wifi doesnt work except on GB roms
and i was surprised that there is zero "0" videos on youtube about this phone!
i was thinking make one and post the link here where i flash CM9 from stock kj6 2.3.6 with CWM 5.0.2.8
and u will tell me if i did something wrong
manzifa45 said:
i have tried everything, flashed every rom,every kernel,every modem given here and the wifi doesnt work except on GB roms
Click to expand...
Click to collapse
I think it is interesting that you say you have tried everything, but I don't know what everything means, because wifi works for me on every rom. So you did not try everything, you are doing one thing wrong that no one else is having a problem with.
manzifa45 said:
and i was surprised that there is zero "0" videos on youtube about this phone!
Click to expand...
Click to collapse
Considering we are here on XDA, and this is a forum, we usually write text (you know... this stuff) and you have to read it. If I or any other developers for this phone took the time to make a video on how to do something that is better explained in text format, we would never get time to dev anything (and you would hear my wife constantly yelling at me while I'm making a video... I don't need to expose you to that world!).
manzifa45 said:
i was thinking make one and post the link here where i flash CM9 from stock kj6 2.3.6 with CWM 5.0.2.8 and u will tell me if i did something wrong
Click to expand...
Click to collapse
How about instead, you do things one step at a time. At each step, write down what you did and the results. Be as detailed as you can. Use correct english, so we understand what you are saying. (you instead of u, because instead of bcoz, etc...)
When you get all done, post to this thread and we will help!
bhundven said:
you do things one step at a time. At each step, write down what you did and the results. Be as detailed as you can
Click to expand...
Click to collapse
thank you i really apreciate
ok i was running CM7(which is smooth and work great, thanks to team acid) but decided to try again...and here is what i'm doing:
- i returned to stock 2.3.6 via Odin and CWM is 3.0.2.8 in Red (don't know why, but you probably do)
- to have CWM 5.0.2.8 i flashed a kernel (Basic with a Twist SGS4G KJ6 1.1.3)
- then after rebooting twice i get into cwm 5.0.2.8 and i did wipe data/factory reset,wipe cache partition,wipe dalvik cache
- then install zip from SD card...then flash "cm-9-20120830-UNOFFICIAL-galaxys4gmtd" (that i downloaded twice to make sure the package is good)
- reboot and flashed Gapps and reboot again and flashed the "kj6_padded_modem"
- i rebooted twice and entered cwm and did wipe cache partition,wipe dalvik cache, fix permissions
after a reboot when i turn on wifi it tells me "wifi turning on" and didn't detect any signal but all other stuff work.
hope its clear than before
Tried getting closer to the router? Your wifi is accessible with other devices? You HAVE wifi?
Sorry if that sounded mean, but like Bryan said, there are no problems with wifi an any rom I have used either.
Sent from my SGH-T959V using xda premium
sunsurfer42 said:
Tried getting closer to the router? Your wifi is accessible with other devices? You HAVE wifi?
Click to expand...
Click to collapse
Of caurse i do!! the router is in my room signal is excellent with stock 2.3.6 and CM7. only on CM9 it shows "wifi turning on" and least forver
let me try to attach pictures. i will stay on 2.3.6 stock or cm7.:crying:
{
"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"
}
I think you might be missing a key step.
Go back to stock.
Flash basic with a twist to get the right recovery.
Wipe data/factory reset.
Wipe cache.
Wipe dalvik cache
Go to mounts "WIPE SYSTEM"
Flash rom.
Let it do is thing and reboot you into cm9.
Then reboot into recovery flash gapps.
you shouldn't need to flash the radio if you already had kj6 before, I never do. But what I like to do is repeat the wipes and fresh install of cm9 after the initial install from gb just to be on the safe side though I'm sure it's over kill, then flash the gapps. restart and let the phone settle in before I mess with it. Works for me every time.
Sent from my SGH-T989 using xda app-developers app
Hey all,
I'm a long time lurker and just recently registered because of my issue with my Nexus 5. I've owned several Androids I've rommed, rooted etc with no issues until now...
My newest Android is a Nexus 5, I have not modded it in any way. It was totally factory 4.4.2 with no issues. Love the phone.
Until today; I pulled it off the charger at 100% used it to check twitter, instagram then google search unexpectedly quit, and the phone goes dark.
When I try and reboot I'm stuck at the Google screen, and it boot loops every minute or so.
I searched and found no one with a similar issue. I can get into stock recovery, I started by clearing cache, factory resetting but it made no difference. I also tried pulling and retrying the SIM card.
I then followed these guides and everything went exactly as it should, but no boot past the Google logo, and my bootloader is now unlocked and secure boot enabled...
http://forum.xda-developers.com/showthread.php?t=2513701
http://forum.xda-developers.com/showthread.php?t=2507905
In the past anytime I've experienced bootloops its been due to roms or botched flashing and I was able to correct it with TWRP backups, but in this case because I'm essentially 100% stock I have no idea what direction to go!
Any help is appreciated as I'm at a total loss right now
Thanks for your time!
EDIT: Just realized when flashing the stock rom I get the error during "writing system"
FAILED (remote: flash write failure>
Then it asks me to hit any key to exit... would this mean I have a hardware issue?
I also got
Archive does not contain 'boot.sig'
Archive does not contain 'archive.sig'
Archive does not contain 'system.sig'
EDIT2: Installed TWRP and wiped using it.
Still no changes
dollabill202 said:
Hey all,
I'm a long time lurker and just recently registered because of my issue with my Nexus 5. I've owned several Androids I've rommed, rooted etc with no issues until now...
My newest Android is a Nexus 5, I have not modded it in any way. It was totally factory 4.4.2 with no issues. Love the phone.
Until today; I pulled it off the charger at 100% used it to check twitter, instagram then google search unexpectedly quit, and the phone goes dark.
When I try and reboot I'm stuck at the Google screen, and it boot loops every minute or so.
I searched and found no one with a similar issue. I can get into stock recovery, I started by clearing cache, factory resetting but it made no difference. I also tried pulling and retrying the SIM card.
I then followed these guides and everything went exactly as it should, but no boot past the Google logo, and my bootloader is now unlocked and secure boot enabled...
http://forum.xda-developers.com/showthread.php?t=2513701
http://forum.xda-developers.com/showthread.php?t=2507905
In the past anytime I've experienced bootloops its been due to roms or botched flashing and I was able to correct it with TWRP backups, but in this case because I'm essentially 100% stock I have no idea what direction to go!
Any help is appreciated as I'm at a total loss right now
Thanks for your time!
EDIT: Just realized when flashing the stock rom I get the error during "writing system"
FAILED (remote: flash write failure>
Then it asks me to hit any key to exit... would this mean I have a hardware issue?
I also got
Archive does not contain 'boot.sig'
Archive does not contain 'archive.sig'
Archive does not contain 'system.sig'
EDIT2: Installed TWRP and wiped using it.
Still no changes
Click to expand...
Click to collapse
The reason it's failing is because you may have misplaced some files on the flash-all folder
it should look exactly like this
{
"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"
}
Code:
Archive does not contain 'boot.sig'
Archive does not contain 'archive.sig'
Archive does not contain 'system.sig
'
Click to expand...
Click to collapse
all of these missing files are in the winrar zip file (image-hammerhead-krt16m zip) you don't need to extract them just put the zip along with the other files as they are in the picture
92885245
GUGUITOMTG4 said:
The reason it's failing is because you may have misplaced some files on the flash-all folder
it should look exactly like this
mine looks like this:
HTEETEEPEE://i.gyazoDOTcom/8cfac3bb195e640edaf346319d185d91.png
should be okay no?
I'm also going back to 4.4.0 would that be an issue considering I was on 4.4.2 before?
I'd even be open to flashing a custom rom, but i'm unsure of how to get the rom onto the device as there is no sd card slot and I can't boot into anything to let me transfer files. On my note I always used an sd card to get gapps and the rom onto the device to begin with...
Thank you very much for your input!
Click to expand...
Click to collapse
dollabill202 said:
Hey all,
I'm a long time lurker and just recently registered because of my issue with my Nexus 5. I've owned several Androids I've rommed, rooted etc with no issues until now...
My newest Android is a Nexus 5, I have not modded it in any way. It was totally factory 4.4.2 with no issues. Love the phone.
Until today; I pulled it off the charger at 100% used it to check twitter, instagram then google search unexpectedly quit, and the phone goes dark.
When I try and reboot I'm stuck at the Google screen, and it boot loops every minute or so.
I searched and found no one with a similar issue. I can get into stock recovery, I started by clearing cache, factory resetting but it made no difference. I also tried pulling and retrying the SIM card.
I then followed these guides and everything went exactly as it should, but no boot past the Google logo, and my bootloader is now unlocked and secure boot enabled...
http://forum.xda-developers.com/showthread.php?t=2513701
http://forum.xda-developers.com/showthread.php?t=2507905
In the past anytime I've experienced bootloops its been due to roms or botched flashing and I was able to correct it with TWRP backups, but in this case because I'm essentially 100% stock I have no idea what direction to go!
Any help is appreciated as I'm at a total loss right now
Thanks for your time!
EDIT: Just realized when flashing the stock rom I get the error during "writing system"
FAILED (remote: flash write failure>
Then it asks me to hit any key to exit... would this mean I have a hardware issue?
I also got
Archive does not contain 'boot.sig'
Archive does not contain 'archive.sig'
Archive does not contain 'system.sig'
EDIT2: Installed TWRP and wiped using it.
Still no changes
Click to expand...
Click to collapse
I`am afraid you`re phone is gone atm, flash write failure usualy indicates a flash memory issue, thats why it doesn`t boot for instance. Its a hardware failure and you need to have the motherboard replaced. Better turn it in for repair or RMA. Good luck and hope you have it fixed soon
gee2012 said:
I`am afraid you`re phone is gone atm, flash write failure usualy indicates a flash memory issue, thats why it doesn`t boot for instance. Its a hardware failure and you need to have the motherboard replaced. Better turn it in for repair or RMA. Good luck and hope you have it fixed soon
Click to expand...
Click to collapse
Yeah, this is what I was scared of, luckily it's only 1 month old. But i'm now going to have to lock my bootloader now that i've unlocked it trying to reflash...
How would I go about doing this if I cannot write to the memory? The guide states that I need to use the script from http://forum.xda-developers.com/showthread.php?t=2239421
I would also have to get rid of TWRP right?
dollabill202 said:
Yeah, this is what I was scared of, luckily it's only 1 month old. But i'm now going to have to lock my bootloader now that i've unlocked it trying to reflash...
How would I go about doing this if I cannot write to the memory? The guide states that I need to use the script from http://forum.xda-developers.com/showthread.php?t=2239421
I would also have to get rid of TWRP right?
Click to expand...
Click to collapse
There is nothing you can do at the moment, just return it as it is. You can maybe lock the bootloader but it will remake flagged.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
---------- Post added at 02:26 AM ---------- Previous post was at 02:25 AM ----------
gee2012 said:
There is nothing you can do at the moment, just return it as it is. You can maybe lock the bootloader but it will remaine flagged.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Click to expand...
Click to collapse
Verstuurd vanaf mijn Nexus 5 met Tapatalk
If you can`t boot neither can Google/LG
gee2012 said:
There is nothing you can do at the moment, just return it as it is. You can maybe lock the bootloader but it will remake flagged.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
---------- Post added at 02:26 AM ---------- Previous post was at 02:25 AM ----------
Verstuurd vanaf mijn Nexus 5 met Tapatalk
If you can`t boot neither can Google/LG
Click to expand...
Click to collapse
mhmmmm
I tried flashing 4.4.0 again and I got the following, looks successful but it still bootloops
HTEETEEPEE://i.gyazoDOTcom/49abe2444ff0df446a8e906b5e488409.png
Would this mean the hardware could still be okay?
dollabill202 said:
mhmmmm
I tried flashing 4.4.0 again and I got the following, looks successful but it still bootloops
HTEETEEPEE://i.gyazoDOTcom/49abe2444ff0df446a8e906b5e488409.png
Would this mean the hardware could still be okay?
Click to expand...
Click to collapse
Go into recovery if you can and data Factory reset and reboot.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
---------- Post added at 03:57 AM ---------- Previous post was at 03:48 AM ----------
gee2012 said:
Go into recovery if you can and data Factory reset and reboot.
Can't see the picture so can't tell mate. I am off to bed if you don't mind. You do the same, tomorrow will be better ☺
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Click to expand...
Click to collapse
Verstuurd vanaf mijn Nexus 5 met Tapatalk
gee2012 said:
Go into recovery if you can and data Factory reset and reboot.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
---------- Post added at 03:57 AM ---------- Previous post was at 03:48 AM ----------
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Click to expand...
Click to collapse
Thank you so much for your time and help!
The image is basically everything being 100% okay in flashing the oem rom
I also managed to lock my bootloader.
So it seems my hardware works, but just will not boot past the Google logo
One fishy thing I noticed is when factory reset/wiping in the stock recovery I get some odd errors as well as when I wipe the cache...
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_install
It does say Data Wipe Complete, but repeats the above three lines each time...
I just started to get the same Google boot loop issue. Thing is, I'm completely stock and never rooted or anything. My phone seems to be fine now. But it boot looped twice today. Had the phone since December, do you think I need to RMA or just wait and see?
Sent from my Nexus 5 using XDA Premium 4 mobile app
I know that you can't get into the phone to enable USB, but you can still get into the recovery right? Like TWRP/ClockWork Mod? If so, then in there (CWM atleast, I'm nearly positive you can too in TWRP), you can enable USB via recovery and then put a ROM on the internal storage. You then must reboot into the recovery to be able to flash it.
Just look for an option to enable USB in the recovery.
logicrulez said:
I just started to get the same Google boot loop issue. Thing is, I'm completely stock and never rooted or anything. My phone seems to be fine now. But it boot looped twice today. Had the phone since December, do you think I need to RMA or just wait and see?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you bootloop or did the device reboot itself? Different issues lol.
snappycg1996 said:
I know that you can't get into the phone to enable USB, but you can still get into the recovery right? Like TWRP/ClockWork Mod? If so, then in there (CWM atleast, I'm nearly positive you can too in TWRP), you can enable USB via recovery and then put a ROM on the internal storage. You then must reboot into the recovery to be able to flash it.
Just look for an option to enable USB in the recovery.
Click to expand...
Click to collapse
You can't get USB recovery via recovery. That's called ADB.
The second part about archive does not contain means nothing, it always says that. The flash write failure unfortunately means it's borked. Nothing to do but send it back to Google.
exb0 said:
Did you bootloop or did the device reboot itself? Different issues lol.
You can't get USB recovery via recovery. That's called ADB.
Click to expand...
Click to collapse
Oh! I guess that's a special kind of service? I remember that now, I have an Inspire that I did this on, I couldn't get into the phone and so I just went into CWM and loaded up USB and stuck a ROM on there. c:
logicrulez said:
I just started to get the same Google boot loop issue. Thing is, I'm completely stock and never rooted or anything. My phone seems to be fine now. But it boot looped twice today. Had the phone since December, do you think I need to RMA or just wait and see?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There can be many other issues also which can make the phone bootloop. Most of the Time phone bootloops due to the 3rd party apps and their data. Whenever this happen start ur phone in safe mode and since this happens rarely, I doubt there is an issue with the internal memory.
You can also try factory reset through stock recovery and even just clearing the cache helps in such cases
dollabill202 said:
Hey all,
I'm a long time lurker and just recently registered because of my issue with my Nexus 5. I've owned several Androids I've rommed, rooted etc with no issues until now...
My newest Android is a Nexus 5, I have not modded it in any way. It was totally factory 4.4.2 with no issues. Love the phone.
Until today; I pulled it off the charger at 100% used it to check twitter, instagram then google search unexpectedly quit, and the phone goes dark.
When I try and reboot I'm stuck at the Google screen, and it boot loops every minute or so.
I searched and found no one with a similar issue. I can get into stock recovery, I started by clearing cache, factory resetting but it made no difference. I also tried pulling and retrying the SIM card.
I then followed these guides and everything went exactly as it should, but no boot past the Google logo, and my bootloader is now unlocked and secure boot enabled...
http://forum.xda-developers.com/showthread.php?t=2513701
http://forum.xda-developers.com/showthread.php?t=2507905
In the past anytime I've experienced bootloops its been due to roms or botched flashing and I was able to correct it with TWRP backups, but in this case because I'm essentially 100% stock I have no idea what direction to go!
Any help is appreciated as I'm at a total loss right now
Thanks for your time!
EDIT: Just realized when flashing the stock rom I get the error during "writing system"
FAILED (remote: flash write failure>
Then it asks me to hit any key to exit... would this mean I have a hardware issue?
I also got
Archive does not contain 'boot.sig'
Archive does not contain 'archive.sig'
Archive does not contain 'system.sig'
EDIT2: Installed TWRP and wiped using it.
Still no changes
Click to expand...
Click to collapse
same problem, any news?
andrelg3 said:
same problem, any news?
Click to expand...
Click to collapse
Sorry for the late response,
But yeah, apparently I had some sort of flash memory writing issue... I couldn't get anything to write or flash other than the recovery. So I ended up spending over and hour on the phone with google troubleshooting (rebooting it 10+ times in a row) then I locked the phone back up and sent it in. Got a new one so there seemed to be no working around my issue
So, I unlocked bootloader of my N5. Flashed CWM Touch. Didn't make any kinda backup (I know I'm stupid) and flashed paranoid android. Now I'm not getting any signals on it. Please, I'm in need of desperate help. Any solutions?
EDIT:
Flashed stock image, good as new This should help people who are as stupid as me
Do the usual flash cache.img first. Failing that, reflash all stock images
Sent from my Nexus 5 using Tapatalk
Hello,
Did you wipe data/factory reset, cache, dalvic cache before flashing PA rom.zip?
IF not, then head over to recovery and wipe everything.. Now flash pa.zip and gapps.zip and finally reboot...
Just flashing the pa rom won't touch the efs...
rootSU said:
Do the usual flash cache.img first. Failing that, reflash all stock images
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Trying this
vin4yak said:
Hello,
Did you wipe data/factory reset, cache, dalvic cache before flashing PA rom.zip?
IF not, then head over to recovery and wipe everything.. Now flash pa.zip and gapps.zip and finally reboot...
Just flashing the pa rom won't touch the efs...
Click to expand...
Click to collapse
But, I did not wipe data/factory reset..I went into mounts and storage and wiped everything except sd-card
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
7alvi said:
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
Click to expand...
Click to collapse
Not yet, flash the factory image. That'll get you to a like new condition.
Sent from my Nexus 5
7alvi said:
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
Click to expand...
Click to collapse
Go to your custom recovery and wipe everything (data/cache/dalvic)... Now flash the rom.zip and gapps.zip and finally reboot and see whether you're able to get a signal or not?
OR
You could use this guide to return to full stock and check... http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
jd1639 said:
Not yet, flash the factory image. That'll get you to a like new condition.
Sent from my Nexus 5
Click to expand...
Click to collapse
I'm flashing the stock image as of now. But, how will it restore my efs partition? By wiping everything in recovery in mounts and storage, didnt i wipe it too?
7alvi said:
I'm flashing the stock image as of now. But, how will it restore my efs partition? By wiping everything in recovery in mounts and storage, didnt i wipe it too?
Click to expand...
Click to collapse
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
rootSU said:
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
7alvi said:
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
Click to expand...
Click to collapse
The 2 lines is are normaly
Try again with admin rights
7alvi said:
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
Click to expand...
Click to collapse
That could be because you extracted the image-hammerhead xxxxx.zip file. dont extract it. it should be there like it is on this picture
{
"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"
}
rootSU said:
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I officially pronounce this phone as un-brickable. Yes it's fixed. IMEI, baseband siganls everything is back... @rootSU I owe you a beer man. I can't emphasize how ****lessly scared I was...thanx a lot!
No worries
Sent from my Nexus 5 using Tapatalk
Just pumping this thread.
I've gone through a few steps but have ran into a snag.
Heres the synopsis;
My device was randomly shutting down while charging so I decided to factory reset to see if that helped.
When I did the the device entered a boot loop and when I went into recovery it would say can't mount cache etc.
I tried re flashing 5.0.1 Lrx22c but again it got stuck in a boot loop.
I managed to flash 4.4.4 and the device finally turns on.
The only problem is that the phone appears to be without any network connection. Google playstore cannot open and crash's and so does the camera and gallery applications. Adding a sim card does nothing to help.
I'm not sure how to fix this problem and I'm at a point where I need to ask for help. I'm Canadian and bought the device through one of our providers, Rogers, and am starting to think that there is a specific set of 'roger' img's that I need to flash and not the ones from the developers site.
Any input would be much appreciated.
Bump bump ^^
There is no such thing as carrier specific factory images. Did you try reflashing the radio, or a different radio? Remove and reinsert Sim? Might be hardware issue otherwise ..
Sent from my Nexus 5 using Tapatalk
At my wit's end.
I realize it's been 2 weeks since you posted but, in the hope that you are subscribed still Radioman66, I'm curious if you did ever manage to fix/reinject your IMEI; I'm Canadian too btw, though I bought my Nexus 5 through Google Play. I've tried flashing stock everything: bootloader, radio, boot, system, cache, userdata via fastboot; only then did my phone reboot properly, but it still has a habit of crashing/rebooting every so often. No IMEI & no cellular reception thus far, so I can only conclude that there is some data corruption at play here. Fortunately it was easy to find my unique IMEI via a sticker on the inside of the back cover of my Nexus 5, for those who aren't aware.
So I'm in the opinion that the issues of bootloops and my IMEI corruption (dialling *#06# on the dialer calls up a bold IMEI header but no number whatsoever) first occurred when my battery drained to zero. I was using a custom rom at the time, Optipop Dark Deodex with f2fs formatted data and cache partitions, + Multirom & multirom compatible TWRP. I'm at a loss for why the EFS partition and thus IMEI would even be accessed by the phone for writing/reading or how a corruption of the partition could even occur. Perhaps I was receiving a text message right at that very moment it turned off? Perhaps f2fs is to blame, who really knows...main thing is my IMEI is corrupted and I'm left with a smart brick, it being no longer a smart phone.
Anyway, long story short it's been like 2 days of searching around but I think this free tool "Setup DFS 15.01.17.0.zip" at cdmatool dot com (can't post link as a newbie so replace dot with a period) may be the real deal; it's possible to download it without registering i.e. demo mode ( which makes you wait tens of seconds between operations). Despite my general comfort with adb, fastboot, cmd tools in general, the CDMAtool's manual is full of stuff and acronyms I don't really know about yet, like COM Ports and what not but I'm hoping to soon understand this tool and will report back my failures/successes. If anyone would be kind enough to perhaps walk me through what I would need to do, I'd be super thankful!!!t
Welp, cheers to not even knowing about the existence of ESN/EFS/IMEI before this unfortunate juncture LMAO--I will definitely make sure to backup my EFS partitions before flashing custom roms from now on...