The SM600 works well and has had various version of CM and now Lineage on. The last version to work was the nightly 20170302, which if i install works fine.
Both nightlys since cause the tablet to sit there on a black screen (after you tell TWRP to reboot), with nothing ever appearing. If you turn the tablet off after about 30 minutes , it goes in to a boot loop with a black screen then the samsung logo , then the black screen etc.
Whats changed in the nightlys after 20170302?
I have even tried an advanced wipe, clearing all file systems. Lost for new thing to try , and think it i a fault with the build
many thanks
Any one able to help, Is this the right location to post a question like this , or is the a more appropriate location?
Related
Hi guys, first post here. I read a lot here but never had an account.
So, a couple weeks ago, I borrowed my Nexus 7 2013 Wifi to my stepdad. And today he comes up to me and says that the tablet wont boot. I have had the same issue but managed to fix it pretty easily. I've tried flashing stock, ROM based on stock, CM 13, CM 12.1, based on CM 12.1, 4.3 stock, ElementalX kernel and factory reset. After every single one of these steps, it boots up, i touch the screen, it freezes and reboots.
I've read something about flashing a .FFU but couldn't find any file for the Nexus. My device is rooted, with TWRP.
Thanks for reading the post till this point and I can't thank you enough for your help
It may be the digitizer, if you touch the screen and it reboots, unplug the digitizer and use a otg mouse to test it and see if the issue persists
So the screen works in TWRP but reboots Android?
You say you flashed the factory image (I assume that's what you mean) and it still does this. Makes me think hardware. Take the back off and clean/reseat the ribbon cable connections it might help and is easy.
If that don't work I'd be about out of ideas. Try flashing some of sfhubs ts firmwares. Id do that last though as it shouldn't need a software fix if it worked before.
I have an RK3188 800x480 headunit on which I had Malaysk's 4.4.4 ROM on. I decided to try the 5.1.1 version of his ROM but it was too slow for me so I decided to go back. I downloaded the latest version of the 4.4.4 ROM (from February 18) and flashed it. Everything seemed to go smoothly but when the unit booted up I only saw the homescreen for about 2 seconds and then it rebooted again and didn't go past the 2nd boot logo (the animated one). I left it there for over 1 hour but it wouldn't go past that logo. I restarted the unit and it all happened exactly the same way (I got the homescreen for a couple of seconds, it rebooted and refused to go past the second boot logo). I tried this a few times and always got the same result.
I flashed it again a few times and even downloaded the file again (even on a different PC) but nothing changed. I even tried an older version of the 4.4.4 ROM and still got the same results. I decided to try to flash the 5.1.1 ROM again this morning and it worked perfectly fine.
Anybody has any idea why I seem to be unable to downgrade? For what I've read this shouldn't be an issue but I've had no luck at all.
War-Rasta said:
I have an RK3188 800x480 headunit on which I had Malaysk's 4.4.4 ROM on. I decided to try the 5.1.1 version of his ROM but it was too slow for me so I decided to go back. I downloaded the latest version of the 4.4.4 ROM (from February 18) and flashed it. Everything seemed to go smoothly but when the unit booted up I only saw the homescreen for about 2 seconds and then it rebooted again and didn't go past the 2nd boot logo (the animated one). I left it there for over 1 hour but it wouldn't go past that logo. I restarted the unit and it all happened exactly the same way (I got the homescreen for a couple of seconds, it rebooted and refused to go past the second boot logo). I tried this a few times and always got the same result.
I flashed it again a few times and even downloaded the file again (even on a different PC) but nothing changed. I even tried an older version of the 4.4.4 ROM and still got the same results. I decided to try to flash the 5.1.1 ROM again this morning and it worked perfectly fine.
Anybody has any idea why I seem to be unable to downgrade? For what I've read this shouldn't be an issue but I've had no luck at all.
Click to expand...
Click to collapse
I'm sure you did the flash with wipe, but did you do the clear DATA and CACHE (think the 6th option?)
Yeah, I also tried that. No change.
War-Rasta said:
I have an RK3188 800x480 headunit on which I had Malaysk's 4.4.4 ROM on. I decided to try the 5.1.1 version of his ROM but it was too slow for me so I decided to go back. I downloaded the latest version of the 4.4.4 ROM (from February 18) and flashed it. Everything seemed to go smoothly but when the unit booted up I only saw the homescreen for about 2 seconds and then it rebooted again and didn't go past the 2nd boot logo (the animated one). I left it there for over 1 hour but it wouldn't go past that logo. I restarted the unit and it all happened exactly the same way (I got the homescreen for a couple of seconds, it rebooted and refused to go past the second boot logo). I tried this a few times and always got the same result.
I flashed it again a few times and even downloaded the file again (even on a different PC) but nothing changed. I even tried an older version of the 4.4.4 ROM and still got the same results. I decided to try to flash the 5.1.1 ROM again this morning and it worked perfectly fine.
Anybody has any idea why I seem to be unable to downgrade? For what I've read this shouldn't be an issue but I've had no luck at all.
Click to expand...
Click to collapse
Are you using MCU 2.98? If yes, downgrade to 2.86.
War-Rasta said:
I have an RK3188 800x480 headunit on which I had Malaysk's 4.4.4 ROM on. I decided to try the 5.1.1 version of his ROM but it was too slow for me so I decided to go back. I downloaded the latest version of the 4.4.4 ROM (from February 18) and flashed it. Everything seemed to go smoothly but when the unit booted up I only saw the homescreen for about 2 seconds and then it rebooted again and didn't go past the 2nd boot logo (the animated one). I left it there for over 1 hour but it wouldn't go past that logo. I restarted the unit and it all happened exactly the same way (I got the homescreen for a couple of seconds, it rebooted and refused to go past the second boot logo). I tried this a few times and always got the same result.
I flashed it again a few times and even downloaded the file again (even on a different PC) but nothing changed. I even tried an older version of the 4.4.4 ROM and still got the same results. I decided to try to flash the 5.1.1 ROM again this morning and it worked perfectly fine.
Anybody has any idea why I seem to be unable to downgrade? For what I've read this shouldn't be an issue but I've had no luck at all.
Click to expand...
Click to collapse
When you have a KLD Device, inatall the MCU KLD2.81
I had the same issue.
After u install the Rom and MCU, you can install the KLD9* MCU
I'm in the office right now but I went down to the parking lot and confirmed I do have KLD9 v2.98 so I guess that must be it. I updated my MCU back when I still was in 4.4.4 so I find it weird that it can work with such MCU but it can't be flashed with it.
I have a copy of the 4.4.4 ROM here so I'll try flashing it again with the older MCU when I go home tonight.
Indeed, downgrading the MCU worked like a charm. I flashed the MCU and the ROM at the same time and it all went smoothly. Thank you guys.
War-Rasta said:
Indeed, downgrading the MCU worked like a charm. I flashed the MCU and the ROM at the same time and it all went smoothly. Thank you guys.
Click to expand...
Click to collapse
Are you back on Mcu 2.98?
No, I'm still on 2.81. Is there really an advantage to updating to 2.98? It seems to be working fine and I don't know what the changes are.
Hi All, my redmi 5a auto rotate doesn't work, I don't know why but I've experienced a tragedy that maybe connected with this problem.
I use AOSP Extended ROM for Rolex in my Redmi 5A Device, as long as I use it I don't have any problem, but yesterday I've tried to restore my kernel into this ROM Stock Kernel ( I Use Direwolf Unified Before, Many Times I Try Other Kernel Also But And Never Had Such A Tragedy) After I Restored the original kernel, then I wipe my dalvik and cache as usual, BUT, Suddenly The Boot animation Stucked before it show's the AEX Logo, So I Think It Was A Bootloop Simple Problem, Than I Reinstalled My AOSP Extended OS, Than Something Happened, Even Since The First Boot It's Stucked At The Same Point, Than I Tried To Re-flash it again, and after that it still like that, so I was thinking that my External Memory Data Was Corrupted, So I Tried To Copy The File Directly From My PC To My USB OTG (I copied same AOSP ROM) than I reflash it but it still like before, than i start thinking if this ROM file (in my PC and SD card) is corrupted, so I tried to install PE ROM, But The Result Is Still Same As Before, Stucked At Boot Animation Than Forced Shutdown.
Well after that I think my device is get a serious problem such as hard brick or soft brick, than I tried to do clean flash to MIUI 10 Fastboot ROM With My PC, BUT the time elapsed is more long than usually (About 20 minute) waiting for booting and finally my device is normal, so I immediately install TWRP Custom Recovery (3.2.3-1 by FenFern) And Installing AOSP ROM Again (I Swear I Love This ROM) Everything seems normal no problem, restoring app, rooting, personalization, and etc.
Well the problem with auto rotate is coming when I see some funny videos on YouTube, my devices ONLY CAN ROTATE TO THE LEFT, AND CAN'T ROTATE AUTOMATICALLY AND CAN'T ROTATE TO THE RIGHT SIDE, I tried many game's app and watching some anime's in video player, Even If I Switch to auto rotate mode.
hi, you might have corrupted the persist partittion. check in other thread persist related issue. you can get a solution there. by the way does the other sensors working?
SandipS said:
hi, you might have corrupted the persist partittion. check in other thread persist related issue. you can get a solution there. by the way does the other sensors working?
Click to expand...
Click to collapse
Well yeah it's working, except the auto rotate
Yesterday I did a dirty flash of Oxygen OS 9.0.10 on my OnePlus 5T which was initially running Oxygen OS 5.1.7 with Oreo 8.1.0. After that I flashed latest Magisk zip. After booting into system, then after the final setup of the update, I flashed franco kernel from TWRP.
Everything went smooth. All apps were functioning fine. Today in the evening, while watching YouTube, the touch stopped responding. I restarted my phone, cleared cache, dalvic, still the touch wasn't responding.
I booted in TWRP, the touchscreen wasn't responsive, therefore I used my mouse to decrypt then copied full zip of OOS 9.1.0 zip via adb from my laptop. After clearing cache, dalvic, I flashed the zip file.
After booting into system, my phone is showing the message, "phone is starting" with animated strip below it. This has been since past 45-50 minutes.
The touch is not functioning even now.
What should I do to resolve this trouble?
Has you debloat something from /system/app or priv-app? On my tablet it prevents to boot completely and stucks in this Android update loop.
Also not everytime a good idea to dirty flash to another Android major version (Oreo > Pie)!
Try a fresh install.
OxygenOS 9.0.10
No-Verity v4 (if a decrypted phone)
Boot.
Then back to TWRP
Magisk & Custom Kernel
Boot.
Restore maybe from Titanium user apps only (except Whatsapp/Threema/Telegram.. GCM/FCM notifications problems).
Flash Magisk modules.
Sent with much love and Android.
I have been having persistent problems with the touchscreen on my 5T becoming unresponsive at random times for no apparent reason for a while now (see this This thread for more info there).
I have found that when the touch screen stops responding, the ONLY thing that will get it working again is flashing back to stock firmware - I have been using 9.0.9 (didn't even realise .10 was out). Sometimes it doesn't work the first go, and I have to reflash again over the top (maybe even a couple of times) but I've never failed to get it working after a few goes.
Problem (on my phone at least) is that phone then hangs on the "just a sec" screen at first boot, but once the screen works again I do a clean flash of LineageOS so the setupwizard hanging is not a problem for me per se, except that the touch screen inevitably flakes out again - sometimes it takes a few days, sometimes it happens within minutes, but nothing I have tried has made it go away completely. I'd say it was a hardware problem except that reflashing the stock OOS ROM can bring it back to life... maybe it's some weird hard+firmware combination that is triggering it.
Anyway, reflash stock a few more times and see if that helps.
Hi, I am a noob in flashing ROMs and stuff...
I recently got a Galaxy S9(used) by a family member. It had One UI 2.5, android 10 on it but I missed a couple of Android 11 features that I had on my Galaxy A50
So I decided to get Lineage OS 18.1. I flashed it successfully. When I launched Samsung Wearable app, it said that I had modified the software in "Unauthorized way". So I searched and found that Noble ROM is based on One UI 3.1 so I tried to flash it. I got stuck in a bootloop at first but then flashed again and after some time it booted up in setup screen like select language, etc. then at the data transfer part, the phone screen went black except the status bar, then it lighted up the set up screen went black again, it kept on happening. I rebooted it, tried safemode and also tried factory reset in TWRP. Then the issue still occurs from time to time.
I am ready to go back to stock ROM or should I try flashing newer Noble ROM or something else, please suggest.
Please help me!
I used Odin3_v3.14.4 , twrp-3.5.0_9-1-starlte.img.tar and NOBLEROM1.1_N9_S9_S9P with CAMERAFIX_G960
I didn't install kernel fix as I followed this video .