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?

[NOW PUBLIC!] Team Codefire Presents: Project FreeGee!

Please note, this is not compatible with the JB OTA - use the app in the Play store instead for now. Thanks!
Howdy all! So, it's time for me to dig out my release thread template... you know what that means?
The LG Optimus G is now unlocked.
Both the AT&T Version and the Sprint Version have been successfully unlocked with this method.
(To answer your question, if you're wondering, we're going to work on the Canadian version next, then the Korean version)
First off, I'd like to write a few words to LG:
Dear LG, a product will rise and fall on the shoulders of it's community.
If you lock a device, and shut out your community, you lose the backing of a very vocal group of people. When you lose the backing of your community, they no longer recommend your product, and you lose money. HTC has discovered this recently.
Please support your development community, we understand product security plays a role here, but ensure that you cater to your community still.
The second you try to fight your development community by locking them out of your products is the second that I will cease to recommend your products.
Keep this in mind, and I assure you that you will find yourself on the top of the game.
With all of that said, let's get back to the goodies.
What is this?!
This is Project FreeGee, silly!
Have an Optimus G ? This project will allow you to unlock your bootloader, and install whatever you want.
Click to expand...
Click to collapse
How does this work?
For the moment, that is a trade secret. Suffice it to say that we put some ones and zeros in the right places, and good things happen.
This is also my opportunity to say do not allow any OTAs to install without asking if they are compatible. LG could possibly patch this in such a manner that makes it rather hard to ever exploit it again.
Click to expand...
Click to collapse
I'm a skeptic. I demand proof!
Alrighty, here it is:
Once again, taken with my HTC Vivid, that would rather mute me than let me speak.
Damn "nose elimination"! I am not noise, and I will not be silenced! (mmhmhmhpmhmp!!)
Click to expand...
Click to collapse
Okay, I'm game. Where do I get it?
Version 0.3 has a confirmed bug-- camera app crashes phone after a few seconds!
If you have 0.3 installed, simply download this, extract the .zip, and extract the .tar file. Inside the freegee-working directory, you'll find boot-att-freegee.img .
Boot your phone to fastboot, then fastboot flash boot /path/to/boot-att-freegee.img
I will release a quick fix .zip for flashing in CWM tomorrow.
Current Version: 0.5
Changelog:
New in v0.5 Removed LG Security check. You are now free to remove any and all apps.
http://downloads.codefi.re/thecubed/lgoptimusg/sprint/freegee/FreeGee-0.5_Sprint.zip
Currently, the download is Windows-only. I will make a OSX/Linux/Windows version soon!
Click to expand...
Click to collapse
FAQ
Can I flash an OTA after installing this?
No. Flashing an OTA could contain a new bootloader, and it would replace the one we have put on your device. If you flash the new OTA, and it replaces the bootloader but not the boot.img, you could be left in a situation where you could not boot the phone due to a security error. Once you're in that position, the only thing you can do is LGNPST back to stock-- and even then, it is possible that an OTA could enable an anti-rollback feature which would disable LGNPST.
Does this mean I can flash custom ROMs now?
Yes. However, the custom ROM must be made for your device. We're working on a decrapified stock ROM, and AOSP ROMs as well. Be patient for those to come.
Can I install a Nexus 4 system image and boot.img and have it work?
We've tested that, and the answer is no, not yet. Some work needs to be done, but once we figure it out, we'll have a quick and easy AOSP ROM.
Does this mean that we can use the Nexus 4 sources (kernel and android) ?
Short answer: Yes.
This phone is essentially a Nexus 4, with minor differences in GPIOs, memory address space, and partition table layouts.
Kernel source is iffy, since we've got Eco mode and a few other things that actually make me like the Optimus kernel more than the Nexus kernel.
However, this discussion is best suited for a new post.
How can I uninstall this?
I'm working on an easy-uninstall for this as well. Stay tuned for the links...
Click to expand...
Click to collapse
Important Information
To enter bootloader, hold volume UP and power.
Upon entering the bootloader, you will notice that there is no 'menu' to enter fastboot or recovery. Unfortunately, since the stars didn't align properly, we were unable to tell the new bootloader where to load the images that contain the menu from.
In light of that, you'll have to navigate the menu blind. Use the volume keys to change selection, and the power key to select.
The choices are (in order of pressing volume down):
Start - boot the phone normally [already selected]
Restart Bootloader - reboot into the bootloader
Recovery Mode - enter recovery (CWM)
Power Off - powers the phone off
So, to get to Recovery, you would press volume down twice then power.
If you have trouble with this, watch my video below for a demonstration.
Click to expand...
Click to collapse
Instructions!
Please note: this requires root before you can install this! If you haven't rooted your phone yet, now is the time to do so.
Also, ensure that you have ADB drivers installed. This WILL NOT WORK without them.
Before we begin: please make sure you have USB Debugging turned on, your phone is in "Charge Only" mode, and your phone's screen is on and unlocked.
This will allow you to see the root access prompt if your phone asks for it.
Download the .zip from this post
Extract it somewhere on your hard drive
Ensure your screen is on and unlocked
Run the "freegee.bat" script, and follow the instructions.
Do not run this as administrator! the install will fail if you do so.
Once the unlock is complete, check to make sure you have a "backups" folder now in the folder where you put FreeGee. If not, DO NOT REBOOT your phone.
Even a failed unlock will still show the 'congratulations you're unlocked!' text, read the output to see if you have errors!
You should not see any "adb.exe not found" errors, or "tar: invalid magic" errors. Those would be errors in the script.
An error which you can ignore is "No space left on device" after it says erasing old recovery and boot. That's just a side effect of how we clear the old images out.
Click to expand...
Click to collapse
Contact Information
"Mister Cubed, how do I talk to you?"
That's easy! Hop on IRC and join me on Freenode in #lg-optimus-g . I'm in there as IOMonster (or IOMonster_desk, or IOMonster_work, depending on where I am)
There's also a lot of other cool people in there too!
When you hop in IRC, if you've got a question, just ask it. Don't say "halp! i does brick'd my phone, and i dunno wat to does?!!", but rather "can anyone help? my phone is stuck in fastboot mode, and I can't get out of it. I flashed <xyz> and now I'm stuck here."
Asking your full question (even though it might be a long message) helps us figure out the best way to assist you, without us having to lead the conversation and ask all the questions for you.
Also, on IRC (for those of you who have never used IRC) if you say someone's name, it will 'ping' (also called 'highlight') them. This tells us that someone is talking to us. So, if you pop in IRC and say "IOMonster, it worked!", I'll get a notification, and will probably say "that's awesome!" in response.
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the assistance of the following people:
Shelnutt2
g33k3r
kmdm
synergy
jcase
sextape
xboxfanj
...and the support of the entire #lg-optimus-g IRC channel
A project like this is really only a sum of it's parts, and in our case, we're over 9,000!
Please make sure to tell someone on this list that they're awesome if you see them on IRC or (*gasp!*) in real life.
Click to expand...
Click to collapse
All right, that about sums up my post. Did I forget anything? Let me know below...

Thanks to all of u guys for all your hard work!

Here is some proof, this is fully working...
{
"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"
}
Sorry for the blurry images, took these from my old OG Evo... But can say its fully unlocked!!!
Nice work thecubed, and shellnut2 on this, thanks for keeping our freedom alive!!!

Does the sprint launch OTA prevent this from working?
Sent from my LG-LS970 using xda app-developers app

Tyederian said:
Does the sprint launch OTA prevent this from working?
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I've already run the OTA, and had no issues unlocking, or rooting after the OTA...

I am so excited! I cannot wait to get this thing unlocked! :victory:

Sweet super excited

Awesome! Will be donating to the team on pay day thanks guys!
Sent from my PG86100 using xda premium

That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!

Wow! Many thanks to all the devs for their hard work and to the beta testers for their willingness to let their phones be guinea pigs. Very much looking forward to this!
Sent from my LG-LS970 using Tapatalk 2

jblazea50 said:
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Click to expand...
Click to collapse
$55 they charged me $99 and some tax on top of it. how did you pull that off?

Super sweet you guys are awesome!!

Christmas came early this year.
Sent from my LG-LS970 using xda app-developers app

New build is up!
Fixed a typo in my code haha

awesome job, big thanks to everyone.
And I second that $55 question.

jblazea50 said:
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Click to expand...
Click to collapse
How on earth did you get it for $55?

tabormeister said:
How on earth did you get it for $55?
Click to expand...
Click to collapse
Had signed up for phone freedom to get $50 gift card back in February.

So I just ran this and had a couple little panic moment!!
1. While reading the script, SU poped up and I missed the "Grant SU" button on the phone. I still got the backup folder but nothing was in it. I then thought it worked, rebooted, and nothing.
The second time I ran this, I got to the "Grant SU" button in time and all went GREAT!!! This time I had files in the backup folder.
2. When I rebooted into recovery, I tried to make a backup. I hit the backup button and got some message that said "Can't mount backup path". So i tried the backup to internal SD and it worked.
Figured I'd write this in case anybody else had the same moment's I did.
The files on the backup folder are very differnt from what I'm used to so hopefully I did it correctly. I noticed there was an option in CWM to choose the backup format after I'd made my backup, so I'm not sure which format is correct for Restore. I guess I used the default which is .dup.
Thank you very much dev's for this!!!!!:laugh:
---------- Post added at 05:54 AM ---------- Previous post was at 05:25 AM ----------
DO NOT use the camera!!!! It'll crash your phone!!!
I read about it in the ATT section just now, but it's too late for me. So I guess we have this bug also.
OK...so not quite a crash. Held the volume down button and power together and got it to reboot.
Now we just need to have a way to recover our phones if/and/or when we do crash our phones. I know the devs are working on this, as obviously they are the bomb!!!

Tease: Two things brewing that hopefully will be up today. Both directly related to this

Shelnutt2 said:
Tease: Two things brewing that hopefully will be up today. Both directly related to this
Click to expand...
Click to collapse
I'm sure hoping you're referring to my post above. I get alittle wiggy if I don't have a way to fix my phone myself.

[Q] tab 3 8.0 touch

I bought a tab 3 8.0 recently and which after it got updated through wifi touch was not responding as it should later I restared and it was back to normal. Later after few hours the problem started so I rebooted into recovery to clear the cache it displayed error. The tab works fine sometimes but goes back to touch unresponsiveness when I resume the tab after resumining from sleep mode. Can any please help meand if there are similar problems with tab 3

ansonlarken said:
I bought a tab 3 8.0 recently and which after it got updated through wifi touch was not responding as it should later I restared and it was back to normal. Later after few hours the problem started so I rebooted into recovery to clear the cache it displayed error. The tab works fine sometimes but goes back to touch unresponsiveness when I resume the tab after resumining from sleep mode. Can any please help meand if there are similar problems with tab 3
Click to expand...
Click to collapse
you cannot clear cache from stock recovery.
Only data. (act as reset anyways)
just odin another firmware see if it continues.
Update works most of the time, if you let it sits for around 15 minutes after updating.
Many people got problem after system updates was caused by themselves really.
Rules for updating.
1) let it sits for 15 minutes after update.
2) Do not do manual reboot right after update. (After auto reboot) (Wait for 15 Minutes -- minimal)
3) Do not run/install/download right after update. (Leaving it alone for 15 minutes)
4) make sure nothing is running before tapping system update. (reboot, wait 3 minutes, then press system update) / or clear ram from task manager before tapping system update
*Reasons: update is installed, but it might have to convert/translate certain already existing data. We don't know, but just to avoid data corruption, just leave it alone and do not interrupt the process by doing anything above.

The problem still persist...even after resetting the device through recovery and settings... now when I try to update it says that I have the latest update what do I do. Where do I get another firmware if I wana odin the device. This is really annoying help me please

comscier said:
you cannot clear cache from stock recovery.
Only data. (act as reset anyways)
just odin another firmware see if it continues.
Update works most of the time, if you let it sits for around 15 minutes after updating.
Many people got problem after system updates was caused by themselves really.
Rules for updating.
1) let it sits for 15 minutes after update.
2) Do not do manual reboot right after update. (After auto reboot) (Wait for 15 Minutes -- minimal)
3) Do not run/install/download right after update. (Leaving it alone for 15 minutes)
4) make sure nothing is running before tapping system update. (reboot, wait 3 minutes, then press system update) / or clear ram from task manager before tapping system update
*Reasons: update is installed, but it might have to convert/translate certain already existing data. We don't know, but just to avoid data corruption, just leave it alone and do not interrupt the process by doing anything above.
Click to expand...
Click to collapse
The problem still persist...even after resetting the device through recovery and settings... now when I try to update it says that I have the latest update what do I do. Where do I get another firmware if I wana odin the device. This is really annoying help me please

ansonlarken said:
The problem still persist...even after resetting the device through recovery and settings... now when I try to update it says that I have the latest update what do I do. Where do I get another firmware if I wana odin the device. This is really annoying help me please
Click to expand...
Click to collapse
Samfirmware.com is the place to get firmware.
Sent from my GT-P5210 using XDA Premium HD app

Benzoman said:
Samfirmware.com is the place to get firmware.
Sent from my GT-P5210 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks will check It out

US Firmware
I had trouble finding the US version of the Firmware for the Tab 3 8" until I found this post
http://forum.xda-developers.com/showthread.php?t=2471516
it contains a link to the firmware :good:

ansonlarken said:
I bought a tab 3 8.0 recently and which after it got updated through wifi touch was not responding as it should later I restared and it was back to normal. Later after few hours the problem started so I rebooted into recovery to clear the cache it displayed error. The tab works fine sometimes but goes back to touch unresponsiveness when I resume the tab after resumining from sleep mode. Can any please help meand if there are similar problems with tab 3
Click to expand...
Click to collapse
I'm having the exact same issue that you are, and it is in fact extremely annoying. I'm the one that posted the firmware for our device (linked in the post above this,) and it will not fix our problem.
I've flashed stock rom, modified rom, modified kernel, stock kernel, wiped every single thing possible, and have had absolutely no luck with getting the touch panel (digitizer) working properly again.
It has something to do with the tsp driver being corrupt, or stuck in a constant loop of powering on/off. If you connect to ADB and run "dmesg" you will see over and over again
"[TSP] DVFS On!" and then [TSP] DVFS Off!"
Something to do with "melfas-ts," I think.. As far as I know, it's a Mali chipset, and we need to somehow get the kernel to reinitialize it, or remove it and then reinstall it..
Here's a picture of what I'm talking about:
{
"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"
}

foil said:
I'm having the exact same issue that you are, and it is in fact extremely annoying. I'm the one that posted the firmware for our device (linked in the post above this,) and it will not fix our problem.
I've flashed stock rom, modified rom, modified kernel, stock kernel, wiped every single thing possible, and have had absolutely no luck with getting the touch panel (digitizer) working properly again.
It has something to do with the tsp driver being corrupt, or stuck in a constant loop of powering on/off. If you connect to ADB and run "dmesg" you will see over and over again
"[TSP] DVFS On!" and then [TSP] DVFS Off!"
Something to do with "melfas-ts," I think.. As far as I know, it's a Mali chipset, and we need to somehow get the kernel to reinitialize it, or remove it and then reinstall it..
Here's a picture of what I'm talking about:
Click to expand...
Click to collapse
Dude the problem is resolved.... i went to a samsung servicing center told them about the problem, they said it would take atleast 2 days to check it. Finally the tab is working absolutely ok as it should be. Said they had to change the motherboard. Thats all they said as there was a problem linked with it. Why don't you get it checked and i think thats the only solution rather then hampering the device. Good luck. I also tried almost everything.

ansonlarken said:
Dude the problem is resolved.... i went to a samsung servicing center told them about the problem, they said it would take atleast 2 days to check it. Finally the tab is working absolutely ok as it should be. Said they had to change the motherboard. Thats all they said as there was a problem linked with it. Why don't you get it checked and i think thats the only solution rather then hampering the device. Good luck. I also tried almost everything.
Click to expand...
Click to collapse
I appreciate the input, and I have actually already sent it off to a service center this morning. However, I'm a hardware hacker, and know what I'm doing with it - it's the touch panel controller that needs the firmware reflashed onto it. If I could reflash the firmware myself, I would have much rather done that, and also had a fix for everybody else. I need the device too bad for work at the moment, or I wouldn't have even bothered sending it in.

Phone shuts down abnormally.

Guys I don't know if there's something wrong with my phone or not. Whichever rom or kernel I try, there is an abnormal shut down of my device. Like I'm using it and I leave it for a few minutes or so and it shuts down. I'm not sure if it had something to do with deep sleep or anything, but I need help. Please guys anyone

on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)

YasuHamed said:
on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)
Click to expand...
Click to collapse
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.

promiscuss said:
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.
Click to expand...
Click to collapse
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)

YasuHamed said:
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)
Click to expand...
Click to collapse
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps

promiscuss said:
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps
Click to expand...
Click to collapse
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display

promiscuss said:
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display
Click to expand...
Click to collapse
sir, which custom ROM + kernel + anrdoid version are you on ?

YasuHamed said:
sir, which custom ROM + kernel + anrdoid version are you on ?
Click to expand...
Click to collapse
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.

promiscuss said:
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.
Click to expand...
Click to collapse
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?

YasuHamed said:
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?
Click to expand...
Click to collapse
Thanks for all your effort, the problem seems to have resolved on its own. I'm not sure what it was.

now it's happening to me but it's much more severe. First it started slowly now it's so frequent that the phone might shut down even on boot. This is really frustrating.

I had the same problem with my redmi note 7, flashed stock rom with MI flash tool, fixed everything for me

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)!