Develop Bugs

ClockworkMod Recovery for Galaxy S (BETA BEWARE)

WARNING: From koush' IRC channel it seems this version may be (permanently?) bricking devices.
At the time of this writing only a single working flash has been reported, and several (full?) bricks.
--Chainfire
I just finished my recovery for Galaxy S. This requires some testing before I do the final release.
{
"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"
}
Recovery/Boot TAR download (do NOT extract):
http://bit.ly/czDrPC
932e5f7a9f09c9bc33b14a527f642933
Initramfs source: http://github.com/koush/i9000-leshak-initramfs/tree/koush
Installation instructions:
Install Odin3 v1.0 (MAKE SURE THIS IS THE VERSION YOU USE)
Start Odin3
Press PDA
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads

Wow!... Looks great!
Wanna try after going back home!

I suppose this only works on stock ROM?
My SGS is on JG5 with the following fix...
http://forum.xda-developers.com/showthread.php?t=724251
I followed your instructions, now it won't boot. If I bring it up in recovery mode, I do see all the new options/settings come with your mod. Any suggestions?

Koush said:
I just finished my recovery for Galaxy S. This requires some testing before I do the final release.
Recovery/Boot TAR download (do NOT extract):
http://bit.ly/czDrPC
Installation instructions:
Install Odin3
Start Odin3
Press PDU
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads
Click to expand...
Click to collapse
Can I assume this kernel wasn't compiled with ext3/4 support?

achio1115 said:
I suppose this only works on stock ROM?
My SGS is on JG5 with the following fix...
http://forum.xda-developers.com/showthread.php?t=724251
I followed your instructions, now it won't boot. If I bring it up in recovery mode, I do see all the new options/settings come with your mod. Any suggestions?
Click to expand...
Click to collapse
I'm guessing, but considering this replaces the zImage that mimocan's fix provides anything you have on moved to ext3/ext4 will not be accessible.
To reverse reflash with the mimocan kernel.

Stickyfied for the time being !
Now if only I understood why we needed it... but apparently we do

Chainfire said:
Stickyfied for the time being !
Now if only I understood why we needed it... but apparently we do
Click to expand...
Click to collapse
Only suitable for those that haven't implemented mimocan's kernel.
Just tried with my 'fixed' ext4 device and it just hangs after the Galaxy S boot screen.

damianarnold said:
Only suitable for those that haven't implemented mimocan's kernel.
Just tried with my 'fixed' ext4 device and it just hangs after the Galaxy S boot screen.
Click to expand...
Click to collapse
I can confirm that, this mod won't work if you have mimocan's kernel applied.

Does it work if you "unapply" it ? Can you get your phone back functional again ?

cos this is also a zImage (aka kernel) update..
flash back mimocan or stock to "unapply" it

raspdeep said:
cos this is also a zImage (aka kernel) update..
flash back mimocan or stock to "unapply" it
Click to expand...
Click to collapse
Screws up a little bit more than a reflash of mimocan's kernel I'm afraid

damianarnold said:
Screws up a little bit more than a reflash of mimocan's kernel I'm afraid
Click to expand...
Click to collapse
Can't get it repaired ? In the IRC channel there are a few folks who think they bricked permanently.

Chainfire said:
Can't get it repaired ? In the IRC channel there are a few folks who think they bricked permanently.
Click to expand...
Click to collapse
Every single app. you've installed will need to be reinstalled, it's as if the device is completely cleared of any settings/config.
Basically you need to restore from backup.

If you see this screen
follow these commands while odin3 is opened.
"SIM+SD out, put the battery in. Plug in USB. Hold down both Volume keys, and then push power. Hold it. From the phone > pc screen, hold vol +/- and power, wait til it goes black then returns to that screen. When it goes black the 2nd time release power. " That should put you in download mode so you can install the recovery again.
Then flash this kernel to fix any slowness
http://android.eugenekay.com/Vibrant/LeshakKernel_9_01b9.tar
Eugenekay couldn't link because he only has 4 posts so I'm doing it for him
This might not apply to i9000 users but I posted it just encase.
Also any flashing done in odin formats everything. That is why recovery is needed in order to try and get zip updates. Zip updates wont allow a whole rom flash just modifications.

@mod, all the warnings etc about bricking your phone are misleading. If you had the mimocan fix kernel, then naturally this (as it is a different kernel) will make your phone unusable until you apply the mimocan kernel back.
In other words, this is workin, just not if you had the mimocan fix, which changes where all the data is located in the device.

so are there gonna be roms in zip ?
or this recovery is gonna handle tars as well?

buddy01 said:
@mod, all the warnings etc about bricking your phone are misleading. If you had the mimocan fix kernel, then naturally this (as it is a different kernel) will make your phone unusable until you apply the mimocan kernel back.
In other words, this is workin, just not if you had the mimocan fix, which changes where all the data is located in the device.
Click to expand...
Click to collapse
Oh really.
Please also reference: #koush @ irc.freenode.net, http://forum.xda-developers.com/showthread.php?t=732139, http://forum.xda-developers.com/showthread.php?t=732138
Just after this was released immediately a bunch of Vibrant and Captivate guys tried it and none of them succeeded. A number of them couldn't do anything anymore, couldn't get out of some screen and couldn't connect with the PC. Koush himself was absent at the time. There was a lot of *****ing and moaning, and the people in the channel asked to put the notice up until there was more info. So, as it was about 6 AM for me I put up the warning, called it a day, and decided to figure it out tomorrow (now today).
An unneccessary warning is IMHO better than having to risk a large number of users bricking. (Tough if you prefer bricks...) I'm still not sure what happens on the unbranded SGS / I9000. At least it certainly causes issues on the Vibrant and Captivate (though I think Koush by now has mentioned in one of the threads he'll have to make a different version for each of the SGS variants)
Get me some confirmation it works as advertised on the I9000, and a step-by-step guide to get everything up and running - even if using those modified kernels - and I'll remove the warning. If not, you'll have to wait 'til Koush looks over his stuff again and modifies his post (my warning is in his post, he can simply edit it out).

not working on JF7, keeping on rebooting

Chainfire said:
Oh really.
Please also reference: #koush @ irc.freenode.net, http://forum.xda-developers.com/showthread.php?t=732139, http://forum.xda-developers.com/showthread.php?t=732138
Just after this was released immediately a bunch of Vibrant and Captivate guys tried it and none of them succeeded. A number of them couldn't do anything anymore, couldn't get out of some screen and couldn't connect with the PC. Koush himself was absent at the time. There was a lot of *****ing and moaning, and the people in the channel asked to put the notice up until there was more info. So, as it was about 6 AM for me I put up the warning, called it a day, and decided to figure it out tomorrow (now today).
An unneccessary warning is IMHO better than having to risk a large number of users bricking. (Tough if you prefer bricks...) I'm still not sure what happens on the unbranded SGS / I9000. At least it certainly causes issues on the Vibrant and Captivate (though I think Koush by now has mentioned in one of the threads he'll have to make a different version for each of the SGS variants)
Get me some confirmation it works as advertised on the I9000, and a step-by-step guide to get everything up and running - even if using those modified kernels - and I'll remove the warning. If not, you'll have to wait 'til Koush looks over his stuff again and modifies his post (my warning is in his post, he can simply edit it out).
Click to expand...
Click to collapse
fair enough.

hkfriends said:
not working on JF7, keeping on rebooting
Click to expand...
Click to collapse
Does the same thing on JG5...
When I first applied it, it rebooted itself twice in a row and booted fine. It ran for a good few hours... restored apps. from titanium backup. Did a reboot again. (just to be safe.) At that point, it kept rebooting itself... and then I pretty much gave up and flashed the stock JG5. (couldn't head to work w/o a working phone, lol) Anyone got it to work so far?

update from AT&T

This morning I received a software update message from AT&T, when I tried to update it, i got this error. My phone is rooted and installed CWM.
Is that the reason why it won't let me install the update? Do I have to unroot the phone back to factory setting ?
Once I download the update and hit install, the phone will restart and goto CWM screen (screen shot). Can someone tell me how to fix that and do the upate ?
{
"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 haven't looked into it myself so i'm not 100% but from what i've read this update is just to comply with apple winning an injunction against android's universal search in a patent lawsuit. So instead of being able to simultaneously search the web, your contacts and your apps. you'll only be able to search the web from the google search bar. I would just avoid installing it at all personally and go with custom roms where the chef can cook in the old universal search.

True.
lungfujinshin said:
I haven't looked into it myself so i'm not 100% but from what i've read this update is just to comply with apple winning an injunction against android's universal search in a patent lawsuit. So instead of being able to simultaneously search the web, your contacts and your apps. you'll only be able to search the web from the google search bar. I would just avoid installing it at all personally and go with custom roms where the chef can cook in the old universal search.
Click to expand...
Click to collapse

I made the mistake of thinking this was the Jelly Bean update and updated...:crying:

You need the stock recovery (3e) to update with ota's.

johnw91498 said:
I made the mistake of thinking this was the Jelly Bean update and updated...:crying:
Click to expand...
Click to collapse
I was hoping it was too ,but I hope you have a backup to go back if you updated.

I too am rooted with CWM and have the notice to update. I know not to update but how do I get rid of the annoying notice, the only options are to postpone for 1, 4 or 8 hours I do not see a cancel option anywhere.

Foolishly Accepted OTA=BRICK
I should have known better than to accept the OTA with the phone rooted! It now only shows the SAMSUNG logo and "Boot Recovery" up at the top briefly before turning off again. After work I'll be attempting to fix it... Any guidance on how would be greatly appreciated. My girlfriend is probably calling and texting about the house being on fire or something and I have no idea lol.
I used the SGSIII toolkit posted somewhere else on this forum to root.

JaguarGuy said:
I should have known better than to accept the OTA with the phone rooted! It now only shows the SAMSUNG logo and "Boot Recovery" up at the top briefly before turning off again. After work I'll be attempting to fix it... Any guidance on how would be greatly appreciated. My girlfriend is probably calling and texting about the house being on fire or something and I have no idea lol.
I used the SGSIII toolkit posted somewhere else on this forum to root.
Click to expand...
Click to collapse
Flash to stock, rinse, repeat.
Then once you root again, install Titanium Backup and freeze the software update app. That will put it to sleep for good without uninstalling it entirely.
-Ryan

Success!
ryandelman said:
Flash to stock, rinse, repeat.
Then once you root again, install Titanium Backup and freeze the software update app. That will put it to sleep for good without uninstalling it entirely.
-Ryan
Click to expand...
Click to collapse
I was able to use the toolkit on the home computer to put the phone in download mode. A wave of relief hit me the moment I saw my phone go from black to the download screen lol... From there, like you said, was able to flash and fix. Thanks! And today I've learned a valuable lesson about OTA updates...
A side note, the house is not on fire and my girlfriend was still asleep where I left her.

JaguarGuy said:
I was able to use the toolkit on the home computer to put the phone in download mode. A wave of relief hit me the moment I saw my phone go from black to the download screen lol... From there, like you said, was able to flash and fix. Thanks! And today I've learned a valuable lesson about OTA updates...
A side note, the house is not on fire and my girlfriend was still asleep where I left her.
Click to expand...
Click to collapse
good thing there wasn't a fire while she was asleep! on another note, i only got a text telling me that there was an updated. i'm kind of intrigued as to why some of you got actual notifications almost making you upgrade vs me only receiving a message. i'm assuming that i must have not noticed that i froze/uninstalled the update app.

JaguarGuy said:
I was able to use the toolkit on the home computer to put the phone in download mode. A wave of relief hit me the moment I saw my phone go from black to the download screen lol... From there, like you said, was able to flash and fix. Thanks! And today I've learned a valuable lesson about OTA updates...
Click to expand...
Click to collapse
Can you please point me to where I can find the "toolkit" or the stock ROM that is safe for AT&T i747? Thanks.

is the "updated app" named update.apk? if not, i would appreciate someone sharing the name of the app to freeze. thanks.

Toolkit
heringcheng said:
Can you please point me to where I can find the "toolkit" or the stock ROM that is safe for AT&T i747? Thanks.
Click to expand...
Click to collapse
The link below is the toolkit I used to root originally as well as fix my SGSIII earlier. It is a great program; make sure to thank the author if you find it useful.
http://forum.xda-developers.com/showthread.php?t=1746665

cortez.i said:
is the "updated app" named update.apk? if not, i would appreciate someone sharing the name of the app to freeze. thanks.
Click to expand...
Click to collapse
I didn't see 'software update app' either - but there is a 'FWUpgrade 1.2.0' that has the same icon as the notification about the OTA update so I'm assuming it's that one - I froze it and rebooted, and nope - the reminder notification is still there.
So...
Searching on the backup/restore tab shows 'AT&T Software update V3_1205_2_2' - and that icon matches the color of the notification, so I'm assuming it's that one and now the notification is gone.
Not sure if I need to unfreeze that 'FWUpgrade' app, but I wouldn't think so. I picture my life with the stock rom to be more of a one night stand rather than a meaningful relationship...

This thread might be useful if you want to apply the OTA from CWM without losing root and without getting the Google Search "upgrade": http://forum.xda-developers.com/showthread.php?t=1768826

'AT&T Software update V3_1205_2_2'
^ that's the app you wanna freeze.
Hope this helps.
- Ryan
Sent from my SAMSUNG-SGH-I747 using xda premium

OTA failure problem.

My Lenovo Vibe K5 Plus (3GB RAM) has OTA update problem.
I'm attaching some Screenshots.
Its not rooted or modified in any way.
{
"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"
}
Phone will reboot normally and show "OTA Update failed".
My question is can I update it to latest build by using Lenovo Update Assistant or should I go in order to avoid bricking?
Can I flash the latest build using "Lenovo Smart Assistant" or QFIL?
Will it create any problem like bricking?
Please help.

Your problem is quite classic, the way to solve it is quite simple, but you'll have to lose your data anyway.
The first way is to check if in your internal storage you have a "/0/carrier" folder. If it's the case, you should flash the file <your_country>.ota.zip (via "apply update from sdcard", if it's not accessible, you should copy this file on your external SD card). It will take some time but then you should download and update your phone
In my latest experience, you can try to use Lenovo tools, but I did not succeed to flash my phone this way (never found the right model)
Personnally, when I want to get back to "updatable stock", I usually do this :
Flash a stock ROM via QFIL, but not the last version (I'm on K5 Plus 2GB, and I flash S042)
Just after success, I reboot to booloader via "Power + Vol -"
Using my PC, I reboot to a TWRP recovery, without flashing it, and without changing the readonly filesystem (via TWRP you can access both internal and external storage) : fastboot boot <path to twrp img file>
Here I flash the /0/carrier/<my_country>.ota.zip
Then I reboot and my ROM is installed, and updatable without the carrier problem
Tell me if you need further explanations.

@adinechin thankyou so much for replying.
I don't need my data because I've already backed up everything.
Can I downgrade to a lower build? For example I have build S051 currently installed, so can I go back to S042 with QFIL without any problems?
Is there any other method which doesn't need TWRP because I'm very much afraid of going custom at this moment, because of my lack of knowledge?
I don't have anything in 0 folder. Its empty even after downloading OTA update.

Apocalypse0 said:
@adinechin thankyou so much for replying.
I don't need my data because I've already backed up everything.
Can I downgrade to a lower build? For example I have build S051 currently installed, so can I go back to S042 with QFIL without any problems?
Is there any other method which doesn't need TWRP because I'm very much afraid of going custom at this moment, because of my lack of knowledge?
Click to expand...
Click to collapse
Did you check if you have your ota.zip file ? If you can find it, you only have to flash it and that's it
Sent from my Lenovo K5 Plus using XDA Labs

adinechin said:
Did you check if you have your ota.zip file ? If you can find it, you only have to flash it and that's it
Sent from my Lenovo K5 Plus using XDA Labs
Click to expand...
Click to collapse
No, that's what the irritation. After downloading OTA completely, I don't get anything in my 0 folder. That folder is completely empty. No OTA.zip or any other files completely empty.

Apocalypse0 said:
No, that's what the irritation. After downloading OTA completely, I don't get anything in my 0 folder. That folder is completely empty. No OTA.zip or any other files completely empty.
Click to expand...
Click to collapse
Ok so you can flash any ROM with QFIL, and if you are not comfortable with TWRP, you can try removing your sdcard after flashing ROM, reboot to recovery and flash the OTA.zip.file.
Be aware that flashing with QFIL will also wipe your internal storage.
Sent from my Lenovo K5 Plus using XDA Labs

@adinechin thank you. I have updated to latest version.
Thankyou so much.
I have few questions.
1. Why we can't flash latest version directly from QFIL?
2. My phone gets shut down automatically if not in use. Is it something hardware related because it was fallen down once and I'm getting this annoying problem even after updating to newer build? Earlier I was thinking it is something software related but now I think its hardware problem. Do you have any idea to share on this?
It gets shut down only after not in use. If I use it for hours it works correctly but as soon I lock the screen it gets switched off and only after removing and reinserting the battery it will on again. No matter how long you press Power button it won't get on. Even recovery combination won't work until I remove and reinsert the battery.
Thanks a ton for helping me.

Apocalypse0 said:
@adinechin thank you. I have updated to latest version.
Thankyou so much.
Click to expand...
Click to collapse
Glad I helped you
Apocalypse0 said:
1. Why we can't flash latest version directly from QFIL?
Click to expand...
Click to collapse
You can, but I personally prefer to update via the phone to be sure all is back to normal stock
Apocalypse0 said:
2. My phone gets shut down automatically if not in use.
Click to expand...
Click to collapse
I have no idea on this subject, but with what you describe, it seems more likely to me that the phone is "stuck" than "off". I know it can happen some times if an app takes much memory, especially when you just installed the ROM, it takes some time to stabilize. Have you tried to wait a little when it was stuck like that and unlock it a bit later ? Another remark, instead of removing battery (which can be very annoying), try holding Power Vol+ and Vol- during around 10 seconds : you should reboot to download mode (black glowing screen like with QFIL), and then do it again, you should reboot your phone.

It was happening even on older build. Yes I waited and tried everything (key combinations) but nothing worked. That's why I feel its a hardware problem because of the fall the device took. No problem if I keep using it, no hanging problems or other things, but as soon I lock the screen it just gets switched off Very irritating.
Anyway, you've helped me a lot and I really appreciate the way you've kept everything simple because these things go really above my head.
Thanks again.

Question Corrupted data error message after December update

Hi! Is everyone else here struggling with Corrupted data error message after December update? Pixel asks to wipe data, but even if you do, it still do the same on the next reboot. There's Reddit thread about that going on:
https://www.reddit.com/r/GooglePixel/comments/rfzz6j

Razviar said:
Hi! Is everyone else here struggling with Corrupted data error message after December update? Pixel asks to wipe data, but even if you do, it still do the same on the next reboot. There's Reddit thread about that going on:
https://www.reddit.com/r/GooglePixel/comments/rfzz6j
Click to expand...
Click to collapse
Did you try out the first posts suggestion?
{
"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"
}

Morgrain said:
Did you try out the first posts suggestion?
View attachment 5483007
Click to expand...
Click to collapse
Yep, didn't work. In the end, safe mode boot worked. Way to fix it:
1. Boot in safe mode (volume down while looking at boot animation)
2. Wifi on in safe mode
3. Open Play Market and update everything
4. Reboot normally.

Razviar said:
Hi! Is everyone else here struggling with Corrupted data error message after December update? Pixel asks to wipe data, but even if you do, it still do the same on the next reboot. There's Reddit thread about that going on:
https://www.reddit.com/r/GooglePixel/comments/rfzz6j
Click to expand...
Click to collapse
Hey! I also experienced this problem. Following the steps about updating Google apps doesn't really help as the error reboot will come again the next time you reboot your phone. Rather, follow Razviar solution that you need to enable airplane mode as soon as your phone boots up and enable wifi. Only after a while you can turn off airplane mode and start using cellular data. That way you'll be able to safely avoid the restart loop.
Never expected such a silly bug on a flagship device. Shame on you, Google!

hafatih27 said:
Hey! I also experienced this problem. Following the steps about updating Google apps doesn't really help as the error reboot will come again the next time you reboot your phone. Rather, follow Razviar solution that you need to enable airplane mode as soon as your phone boots up and enable wifi. Only after a while you can turn off airplane mode and start using cellular data. That way you'll be able to safely avoid the restart loop.
Never expected such a silly bug on a flagship device. Shame on you, Google!
Click to expand...
Click to collapse
I managed to restart the phone once without getting error message, but next reboot failed again. So currently on affected devices we have to do this reboot shaman dance every time we need to reboot.

hafatih27 said:
Hey! I also experienced this problem. Following the steps about updating Google apps doesn't really help as the error reboot will come again the next time you reboot your phone. Rather, follow Razviar solution that you need to enable airplane mode as soon as your phone boots up and enable wifi. Only after a while you can turn off airplane mode and start using cellular data. That way you'll be able to safely avoid the restart loop.
Never expected such a silly bug on a flagship device. Shame on you, Google!
Click to expand...
Click to collapse
Hey guys, I'm also having the exact same problem with my pixel 6 pro December build SQ1D.211205.016.A1. And I can confirm that restarting while airplane mode On prevents the phone from restarting again and crash with "failed to load Android system". I really hope Google acknowledge this problem and fix it in future updates. I posted the issue in google community support and no one replied. I thought I was the only one having this issue. Y_Y

imivantj said:
Hey guys, I'm also having the exact same problem with my pixel 6 pro December build SQ1D.211205.016.A1. And I can confirm that restarting while airplane mode On prevents the phone from restarting again and crash with "failed to load Android system". I really hope Google acknowledge this problem and fix it in future updates. I posted the issue in google community support and no one replied. I thought I was the only one having this issue. Y_Y
Click to expand...
Click to collapse
did you fix your issue? it looks like restarting in safe mode and updating all your google services apps can resolve your issue. if not, flashing the mid-november build can fix it also.

Alekos said:
did you fix your issue? it looks like restarting in safe mode and updating all your google services apps can resolve your issue. if not, flashing the mid-november build can fix it also.
Click to expand...
Click to collapse
I haven't tried restarting with my Internet turned on again. I'll just wait until January or February update by Google and see how it goes. I don't want to do any tinkering with safe mode or flashing of builds because my device is an import set and if I mess up, I'm literally burning the money I've spent on this phone. So, fingers crossed, google acknowledge and fix it in the future. If not, then at least I can still use my phone (if I need to restart, just turn on airplane mode). It's just annoying that such a fundamental bug that causes this kind of OS error happens at Google. Had I known that, I could've applied for a software engineer role there. Probably I'll fix it myself. XD

imivantj said:
I haven't tried restarting with my Internet turned on again. I'll just wait until January or February update by Google and see how it goes. I don't want to do any tinkering with safe mode or flashing of builds because my device is an import set and if I mess up, I'm literally burning the money I've spent on this phone. So, fingers crossed, google acknowledge and fix it in the future. If not, then at least I can still use my phone (if I need to restart, just turn on airplane mode). It's just annoying that such a fundamental bug that causes this kind of OS error happens at Google. Had I known that, I could've applied for a software engineer role there. Probably I'll fix it myself. XD
Click to expand...
Click to collapse
there's a known fix for this. restart in safe mode, enable wifi and update your play services apps (long press on play store icon, my apps, update all). every user I've seen has pretty much fixed it doing this. its an issue with Bluetooth actually.

Alekos said:
there's a known fix for this. restart in safe mode, enable wifi and update your play services apps (long press on play store icon, my apps, update all). every user I've seen has pretty much fixed it doing this. its an issue with Bluetooth actually.
Click to expand...
Click to collapse
Hi, it doesn't work. My apps are all updated. And based on my personal testing, it's not the bluetooth. It's the wifi/mobile network issue. Because when I tested it, my bluetooth was already off. It's the internet (either wifi/mobile network that's causing the restart and crash). I appreciate your help though :'). I'm just always unlucky when it comes to buying hardware. All kinds of hardware I bought always met with issues. I really put such high bar for Google. But unfortunately, it's really a shame and disappointing that such a giant company fails miserably in this kind of thing.

Were you rooted and manually flashed the update? I know of a few things that could cause a similar issue if the update was done manually over fastboot.

NippleSauce said:
Were you rooted and manually flashed the update? I know of a few things that could cause a similar issue if the update was done manually over fastboot.
Click to expand...
Click to collapse
Absolutely not. I don't do such things to an expensive phone

imivantj said:
Absolutely not. I don't do such things to an expensive phone
Click to expand...
Click to collapse
Ahh, gotcha. It's not too risky to do - but is if you know what you're doing / aren't willing to learn before doing it.
Regardless, good luck figuring this out (and Happy Holidays)!

OEM issues

Hello. 3 weeks ago I was testing lineage 19 and had decided to install the gapps. The problem is, when I was trying to start TWRP it did not start from the twrp logo so I tried to flash from odin TWRP 3.4.0 to "try" to fix the recovery. When the phone did not start I decided to reinstall the official rom but I only found a version that worked flashing by odin (mexican version. at&t) the phone started and I decided to wait 7 days for the oem unlock to reappear. The problem is that 8 days have passed and oem unlock is still not available and when I go back to download mode it says rmm prenormal.
Will it have to do with having used a telephony rom when installing stock? I have no idea why it does not appear (it should be clarified. I did not turn off the device or disconnect from the internet in all that time, only when it was already on the eighth day because it was already very saturated) Sorry if I'm posting this wrong, or if you misunderstand what I'm trying to say. It's my first time writing here and I don't speak enough English to write this for myself. So I'm trying to "improve" the google translation changing some words
Thank you very much for reading this post and any help is welcome.

.

right now im waiting the 7 days but its weird, i installed the stock of my country but the boot have a att logo and in my country there is no att company lol i even tried downloading from oficial samsung and same logo... hope it work without problem, so Did you fix your problem?

ShadowDeath said:
right now im waiting the 7 days but its weird, i installed the stock of my country but the boot have a att logo and in my country there is no att company lol i even tried downloading from oficial samsung and same logo... hope it work without problem, so Did you fix your problem?
Click to expand...
Click to collapse
not really. After what I have mentioned, I completely cleaned the phone many times. until a week ago I remembered that I just bought the mobile it took approximately 13 days for the oem unlock to appear. (I suppose that because it is a company it will take longer, I don't know) and a friend told me to wait approximately 300 hours (I have currently 222 hours). I feel that if it does not appear again I will be forced to buy a new phone :/

Camkdls said:
not really. After what I have mentioned, I completely cleaned the phone many times. until a week ago I remembered that I just bought the mobile it took approximately 13 days for the oem unlock to appear. (I suppose that because it is a company it will take longer, I don't know) and a friend told me to wait approximately 300 hours (I have currently 222 hours). I feel that if it does not appear again I will be forced to buy a new phone :/
Click to expand...
Click to collapse
damn that sucks and weird, everyone said they just wait 7+ days without power off the phone and worked... first time i read about waiting more time, are you sure your phone isnt power off in the waiting time?

ShadowDeath said:
damn that sucks and weird, everyone said they just wait 7+ days without power off the phone and worked... first time i read about waiting more time, are you sure your phone isnt power off in the waiting time?
Click to expand...
Click to collapse
I am pretty sure. I do not turn off the mobile at all or disconnect it from the mobile data since I cannot make calls because of the VoLTE that is not available so I always receive calls through third-party applications. It should be clarified that I do not have an automatic restart activated, I also registered the mobile in the updates. At the moment I have 250 hours, I will wait 2 days to see if my theory is true.

Camkdls said:
I am pretty sure. I do not turn off the mobile at all or disconnect it from the mobile data since I cannot make calls because of the VoLTE that is not available so I always receive calls through third-party applications. It should be clarified that I do not have an automatic restart activated, I also registered the mobile in the updates. At the moment I have 250 hours, I will wait 2 days to see if my theory is true.
Click to expand...
Click to collapse
It still appears that the phone has been on for 250 hours in the settings. so I don't think it's because of some reboot or shutdown :/
{
"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"
}

Camkdls said:
It still appears that the phone has been on for 250 hours in the settings. so I don't think it's because of some reboot or shutdown :/
View attachment 5566123
Click to expand...
Click to collapse
If you dint re lock the bootloader when you installed that rom, the bootloader is unlocked right now, but pretty sure you have the samsung rmm in prenormal and thats why to "fix" it we need to wait 7+ days of usage so you should enter in download mode and check your RMM setting again or you should try to install another rom, could be some issue with that one

ShadowDeath said:
If you dint re lock the bootloader when you installed that rom, the bootloader is unlocked right now, but pretty sure you have the samsung rmm in prenormal and thats why to "fix" it we need to wait 7+ days of usage so you should enter in download mode and check your RMM setting again or you should try to install another rom, could be some issue with that one
Click to expand...
Click to collapse
I had thought about that, but there are a lot of problems to find and download the correct version for the binary. I was still doing searches when I updated to android 8 just to install TWRP and they also match the 13 days that I had mentioned before. if it doesn't appear again I'll have to download another rom at 50kbps
When updating use odin since by chance the OTA update did not work. The same thing happened to lose the oem unlock and while I was preparing everything to install TWRP, approximately 20 days passed. but I already had the unlocking after 15 days.

Camkdls said:
I had thought about that, but there are a lot of problems to find and download the correct version for the binary. I was still doing searches when I updated to android 8 just to install TWRP and they also match the 13 days that I had mentioned before. if it doesn't appear again I'll have to download another rom at 50kbps
When updating use odin since by chance the OTA update did not work. The same thing happened to lose the oem unlock and while I was preparing everything to install TWRP, approximately 20 days passed. but I already had the unlocking after 15 days.
Click to expand...
Click to collapse
Yeah that sites with ultra low speed sucks, use Bifrost for your pc, it download the specific and latest rom of your device from the samsung servers

ShadowDeath said:
Yeah that sites with ultra low speed sucks, use Bifrost for your pc, it download the specific and latest rom of your device from the samsung servers
Click to expand...
Click to collapse
I want to thank you for the program. It worked perfectly (although I used it from android because I was too lazy to turn on the PC) Today at dawn I installed the romania version (I used that version the first time I installed TWRP) All the AT&T garbage is gone
Now I only have to wait 7 days to see if the rom had any errors (Curiously when trying to update the available time zones by restarting it never updated. I think that was the problem)
Sorry for the question. But, did the oem unlock appear to you in all this time that passed?
Since you commented approximately 9 days ago until now I thought I'd ask you if the oem unlock appeared even using a rom that had the at&t logo

Camkdls said:
I want to thank you for the program. It worked perfectly (although I used it from android because I was too lazy to turn on the PC) Today at dawn I installed the romania version (I used that version the first time I installed TWRP) All the AT&T garbage is gone
Now I only have to wait 7 days to see if the rom had any errors (Curiously when trying to update the available time zones by restarting it never updated. I think that was the problem)
Sorry for the question. But, did the oem unlock appear to you in all this time that passed?
Since you commented approximately 9 days ago until now I thought I'd ask you if the oem unlock appeared even using a rom that had the at&t logo
Click to expand...
Click to collapse
Your welcome mate right now i have 143h(my fault i restart it lol) so we will see tomorrow if the option appear, still i dont care about the OEM option because it was set ON last time because i was using LOS, but the "RMM state = Prenormal" in download mode its what is locking my phone to be available to change rom, so yeah we will see tomorrow!

Saddly dint work, gonna try installing a old version of my country code or try to get a clean version, not this weird thing with att $ht
Edit:nothing seems to work so i installed the newest update of my country and debloat the rom... it let it to my mom again and she will be using a good amount of time 4 weeks and ill check again.
Edit 2: seems we are out of options now https://forum.xda-developers.com/t/...d-expired-certificate-whats-next-lol.4403393/

Yup. that explains everything. It seems that in the end I will have to change my phone, do you think there is a way to remove the prenormal RMM? I'm not very experienced in mobile development. This really makes me cry

Camkdls said:
Yup. that explains everything. It seems that in the end I will have to change my phone, do you think there is a way to remove the prenormal RMM? I'm not very experienced in mobile development. This really makes me cry
Click to expand...
Click to collapse
There are apps for repair services (like ChimeraTool) that can unlock it. Wouldn't be free, though.

Camkdls said:
Yup. that explains everything. It seems that in the end I will have to change my phone, do you think there is a way to remove the prenormal RMM? I'm not very experienced in mobile development. This really makes me cry
Click to expand...
Click to collapse
Again im in the 7th day with 171+h and OEM is missing so pretty sure the rmm its prenormal i really dont know now, you can search the telegram group and ask its called "A5/A7 2017 ROMS" i asked for help but they just give me this, they say for them works this method and they did it recently.

ShadowDeath said:
Again im in the 7th day with 171+h and OEM is missing so pretty sure the rmm its prenormal i really dont know now, you can search the telegram group and ask its called "A5/A7 2017 ROMS" i asked for help but they just give me this, they say for them works this method and they did it recently.
View attachment 5577843
Click to expand...
Click to collapse
I wonder what is "recent" I also tried this when I had the ATT rom. it didn't work for me anyway. I would try if it works but I'm already tired of flashing stock rom every time I try
I guess I'll wait for it to just unlock or I don't know

Camkdls said:
I wonder what is "recent" I also tried this when I had the ATT rom. it didn't work for me anyway. I would try if it works but I'm already tired of flashing stock rom every time I try
I guess I'll wait for it to just unlock or I don't know
Click to expand...
Click to collapse
Yeah forget about it, I tried today all the tricks again many times and nothing, I'm gonna try a month without power off the phone but right now my hopes are lost.