Hi,
I did some work on upgrading a LG P505R and I messed up with some stuff and hardbricked it quite few times but managed to recover it by digging a lot here and there and using the right tools, and I got clockworkmod 6.0.4 working and from there problems with colors began, I managed to use it to install a new ROM (Kitkat 4.4.4) after ( installing an upgrade earlier via kdz method on top of the stock firmware from Rogers so it became AT&T phone and worked fine but of course was very outdated and useless)...
So I installed CM-11-P500-Ver12 by sideloading via cwm and things went fine but all was in low color mode and kept going thinking that once the new OS is setup it will install the drivers for the "gpu" and everything will be fine but now I am stuck again ( I like learning this way and I don't mind if I brick it again )...
I just would like to know if there is a fix for this colors issue or just some more information about why did this happen and how it did spread from the recovery to the OS... I am pretty sure it's not coming from faulty hardware!
Related
Wondering if any of you guys could help me out here?
By the way, if this is the wrong section for this, apologies and feel free to move?
Nexus 7, 16gb, rooted with stock 4.1.2. I have not edited the build.prop, still using the 4.1.2 Keyboard, Gmail etc.
So, nothing changed other than unlocked/rooted.
I have superSU pro and have 'Survival Mode' enabled, which is basically and OTA Rootkeeper (I am sure you already know this...)
When we got the OTA to 4.1.2, it worked no problem, survival mode worked and I kept root and custom recovery.
So this morning I get a notification to upgrade to 4.2, which I done. It restarted, and installed with no errors etc, then comes the Google screen with the unlocked padlock... and it stayed this way for an hour, so I am assuming it is borked?
I restarted it, same again, so rebooted into the bootlaoder menu. Going into recovery shows the android dude on his back, red triangle ! etc, so I gather my custom recovery is gone.
So the question is, where to go from here, and is there a walkthrough I can use to resuce this (I am techy enough minded, but given the state it is in, loathed to make it worse down to sheer stupidity)?
Any help would be much appreciated guys.
BTW - I used Wugs Toolkit to root, so that is all set up with drivers etc, can that be used now to recover?
No ideas?
So I was running a 4.4.x ROM and it was working great...then my company bought me a wifi-only tablet and that's pretty much useless for me without some tethering, and for whatever reason FoxFi didn't work with my ROM. I searched Google for days, tried mods and all sorts of Xposed stuff, but nothing worked. So I gave up and figured I'd try a new ROM. No reason not to switch to Lollipop, while I was at it - especially because the ROMs currently supported are all 5.0. So I flash a stock 5.0 firmware and tried a ROM - tethering didn't work. Tried another. Same deal. So fine - if i'm going to have no tethering capabilities, I'd rather have it with my old ROM and Nandroid backup.
Using Odin, I flashed the stock firmware that I've been flashing for a year now. It has worked every time in the past. But this time, Odin worked, and passed, and everything looked great - but when I booted up the phone, it starts to boot up, gives me the unlocked lock picture screen, then starts to load the Samsung image, stops mid-way through, and ... NOTHING. Screen goes blank and it hangs forever. I re-flashed with Odin a dozen times...nothing. Wiped data, wiped cache...nothing. I'm out of ideas and apparently Google hasn't seen this before, as far as I can find.
The image is where it stops loading the Samsung logo and then it just goes black.
Please. Help.
isellmidgets said:
So I was running a 4.4.x ROM and it was working great...then my company bought me a wifi-only tablet and that's pretty much useless for me without some tethering, and for whatever reason FoxFi didn't work with my ROM. I searched Google for days, tried mods and all sorts of Xposed stuff, but nothing worked. So I gave up and figured I'd try a new ROM. No reason not to switch to Lollipop, while I was at it - especially because the ROMs currently supported are all 5.0. So I flash a stock 5.0 firmware and tried a ROM - tethering didn't work. Tried another. Same deal. So fine - if i'm going to have no tethering capabilities, I'd rather have it with my old ROM and Nandroid backup.
Using Odin, I flashed the stock firmware that I've been flashing for a year now. It has worked every time in the past. But this time, Odin worked, and passed, and everything looked great - but when I booted up the phone, it starts to boot up, gives me the unlocked lock picture screen, then starts to load the Samsung image, stops mid-way through, and ... NOTHING. Screen goes blank and it hangs forever. I re-flashed with Odin a dozen times...nothing. Wiped data, wiped cache...nothing. I'm out of ideas and apparently Google hasn't seen this before, as far as I can find.
The image is where it stops loading the Samsung logo and then it just goes black.
Please. Help.
Click to expand...
Click to collapse
I'm not saying you file that you are using is messed up but I've been using the NCE downgrade file in this thread
http://forum.xda-developers.com/showthread.php?t=3076803. It's in the OP, step 5 in the notes section. Worth a shot.
Hi all,
I have been hammering away at this one, and putting it on the back-burner, but now, it is really getting to me. Samsung Galaxy Tab Pro 10.1 SM-T520
It has been rooted with ODIN, and shows no problem, (things seem much easier now, as I have re-jigged lots of my old phones using so many more tools, I am not an expert, but can read and search without too much problems) I was very careful to choose the correct file, CF-Auto-Root-picassowifi-picassowifixx-smt520.zip, I have rechecked this step several times, as most of the instructions I found ODIN device ID:COM box should become yellow, when on newer versions it is blue I think, I wondered if I was going mad,
Root Checker Root access granted, all fine. I have Root access. n.
Installed CWM ,latest recovery for a Pro 10.1 wifi, recovery 6.0.3.1 Titanium backup-ed, all ready to go and Reboot and flash a new ROM.. No joy. .. Installed TWRP , same.
When it re-starts it ,shows the galaxy logo, flashes off, then back on, and then fails. Android dead with a red warning , standard recovery KOT49H.T520XXUANAE, all I can do is the usual options:apply update. The only thing I haven't tried is to just wipe all the data. I have a backup of my apps with Titanium Backup on the SD card,I am not that bothered really about much other data if its a pain. I just want control of my device and to try a new ,cleaner ROM(SMT520_GraveD_V3.0)
This has been bothering me for ages, I have read so many posts so am now getting really frustrated I have bought triangle away app. today although I think I sorted that issue early on anyway , but just in case...
Super SU seemed to have vanished so that is back installed
I think I searched and found the Mount/system issue and looked into an issue that lead me to the .system folder, but it is hidden, so I could not find the file it related to. I dont have the specifics to hand as I checked it out at work. I wondered if it is because I have ES file manager, not ASTRO as it said in some of the posts I found.but sure this is a red herring.
I have tried everything..I have a Mac at home and PC at work, I have tried ADB and can see &restart the device etc... so I am connected, first I got the error that it didn't recognise the sideload command. Read up on ADB , looked at the help etc. sideload isn't there as a command, very confusing. But I think I got there one I figured out paths, as of course they are different on a Mac, and possibly more so as I have 2 drives in it, which often confuses me ..grr.
I can of course get into the bootloader, with ON+VOL -, it tells me so far the system is : Official and Knox Warranty Void: 1 which I think is fine, but a chap at work suspected this, but after lots of threads I gather this is normal..
Sorry if long, just thought I should be as clear as possible. I have not really come across such an awkward issue as this , my HTC One was a breeze:crying:
*edit* Just worked out through trial and error, that to use the sideboot command I had to select send via ADB and now with the path /Desktop/SMT520_GraveD_V3.0.zip I was able to send the file but with the following messgae : E:footer is wrong and E:signature verification failed, twice.. So some progress
Thanks !
Just to say after being up waay too long on this, I discovered there is a newer firmware T520XXUANI1_T520BTUANI1_BTU which I may aswell upgrade to first, but of course I cannot do this OTA now As it recognises the device is 'tampered with' *sigh* so gun and games with Odin for Mac tonight, or JODIN3 , just to get the firmware upgrade(which seems to be a jungle of fake download links). before a Rom without bloatware..
I am also not completely clear why, as from another thread about KNOX, as I am basically running stock , without custom recovery.. According to this thread , but I am getting a bit confused now
http://forum.xda-developers.com/gal...neral/knox-warranty-void1-otas-t2996067/page2
Click to expand...
Click to collapse
however this is another story from the ROM install. Apologies
Well. No replies, but I did eventually solve this. Hopefully this can help someone. I am a tinkerer, but I really nearly gave up on this..But this was a cheap second hand tablet ( my first) and I want to see what it can do before I test drive one on my mother who is having nightmares with every Windows laptop I give her!
Once I got to a PC , I had access to Odin3, although it is not available online (apparently to Mac) I could not get it to work due to Java issues (JOdin3 online - brilliant idea but no joy for me so far)
I had the Rom I wanted ( GraveDigger- SMT520_GraveD_V3.0.zip ), the firmware update (T520XXUAOD2_T520BTUAOB1_BTU.zip(i think)) and the unlock file (CF-Auto-Root-picassowifi-picassowifixx-smt520.zip) , non of which I could install in any way , due to being locked out of using a custom Rom bootloader!
At this point I factory reset and cleared the cache( as that is the only options in the basic bootloader!) I also has ADB on the PC so attempted to install the files this way (after messing about using some software to produce the .tar and .md5 files needed for Odin. I tried everything to get this into proper 'bootloader mode' all from scrach again, including trying the adb oem unlockbootloader command, which I would never get to work as I could not get there!
With Odin, I was also again able to flash the firmware update, eventually, and of course had to unlock again. I was curious if I could now use the OTA update, and could not. At some point, in repeating this process( as I think it hung up several times and needed a hard reboot) I had at this point fully wiped the device as I know that is another reason to have glitches and an unstable ROM later.
I think I then tried to check and although T520XXUAOD2 seems to still be the firmware, at some point I managed to get online ( I think some superuser app which I have had to try several may have notified me that KNOX was reset:laugh:When I go to About>Software update it said I had the latest update! Good news!
At this point I had installed both CWM and TWRP again , and thought I would try TWRP.I had tried CWM and the same problem, like a double flash of the Samsung Logo , so I know it had reset !!
THIS TIME I used TWRP ( I thought of trying CWM touch, but its either paid, or I would have to find and ABD the file over I guess) , I managed to re-apply the Root file, Root checker confirmed this , as it had throughout this ordeal!, although apart from ACCESS GRANTED I dont really know what the rest means..Anyway although picassowifi , was still in Device name on TWRP I chose an earlier recovery version to install.- twp-2.7.0.0-picassowifi.img. When I re-booted, I was able to get the TWRP recover image, and install the ROM, I cannot remember if I re-rooted as I was so elated.
I had a few , freezing moments, reinstalling most of my apps through Titanium Backup, I think I just tried to reinstall everything which of was unnecessary, after a hard reset, all seems fine. I checked and the TWRP recovery seems to have stuck. I am not entirely sure how to check about the firmware , but for now I feel this is progress.
Good Luck if anyone found this any use.
Just to add, when you search this ( and probably many other models) you seem to get so many sites, offering exactly the same unlock information, in exactly the same way, many of the downloads seem to take you to many weird and wonderful places. So I tended to look here for downloads if possible. But I had to join SamMobile (which seems a useful site for the firmware upgrade) and trawl all over and assume similarities between other Samsung devices to fully check I was not being an idiot. But this was very odd and I could not find any posts or other workarounds that I did not try. But this new ROM feels lovely and smooth so far, and I now want to look into this tablet further
Edit: I solved it by going back to Stock rom, Android 2.2.1 Froyo. It didn't happen anymore, so it must be some software related issue which remained on the phone even after fully wipe including the OS. Now I will just need to root the phone again and flash custom roms on it.
Hi there,
When I bought my Samsung Galaxy S back then it came with Android 2.2 Froyo (or it was Eclair, don't remember), which I updated to 2.3 Gingerbread. Since then I flashed newer Android roms found on this forum. I never had any problems. So I had ICS (various versions), JB (various versions) and KitKat (I think I was on 4.4.0 and later on 4.4.4)
So up to Android KitKat 4.4.0 I used it on daily basis but after I got a new phone I didn't use it much anymore (I would only turn it on to make sure the battery won't die). But recently I turned it on, I can do things on the phone but when I leave the phone on standby it would eventually reboot on its own.
I tried installing an older version of KitKat. I picked one from an older date, which happened to be 4.4.2. The same issue happens there too. I just installed Android 6.0.1. made by Full Advance. and the issue happens there too.
My phone has an SD card inserted but no SimCard, anything else you need to know just ask.
I would like to keep Android 6.0.1 from Full Advance. It seems a fast and stable rom. It feels faster than the KitKat 4.4.4 I had.
I would be glad if the issue on the self reboot would be solved. I want to use this phone as a MP3 player. I really like AudioFX.
Any help appreciated, thanks!
I used to have a rooted Lollipop stock rom and then got the gearvr and it didnt work until I re-flashed the un-rooted firmware again , this caused me to reinstall everything from scratch , now a friend suggested i should try un-rooting option found in KingUser or SuperUser whenever I needed to use Gearvr (untested , just a thought).
so anybody tried this ?
I just dont want to have to reinstall everything once more , its pretty much annoying
Thanks in advance
Gear VR is only usable with MM and up. My S7 is rooted and it works wonderfully
I use it on Lollipop without any trouble , it gives me 3 hours of un-interrupted game play. when i upgraded to MarshMallow i could hardly make it to 40 minutes and it heated up like crazy . so my problem was last time i rooted it got stuck at splash screen .
I couldnt get the oculus software to install on my Note 5 with the first firmware (OI6 maybe?) I was able to use Cardboard etc.
I'm using a MOAR custom MM 6.0.1 ROM (which your phone has to be rooted since it's custom, for people that don't know) and it hasn't stopped me from installing the oculus software and using it. BUT I am having issues with it freezing after calibration, videos not starting etc.
Not sure if it's related to custom ROM or MM, other people seem to be having the same problems. I think I'm having more problems with the USB connectivity, I turned off "USB debugging" and that solved a lot.