Related
Hi. Sorry if there are grammar errors but I'm swyping on my phone.
I have att d800 unlocked for T-Mobile. I was rooted and unlocked running aeonflex. Wanted to go to kitkat but twrp was giving failed errors. I flashed CWM and was able to successfully flash a kitkat ROM.
Decided to try a newer version of TWRP because cwm took too long to format cache. I flashed It in cwm and now my recovery is corrupt somehow. I want to say it went to a white screen that had rows of 3 digit numbers and said secure boot error or something like that.
No biggie I'll just use flashify or goomanager to flagSh another one. Well this ROM did mention I may lose root and will have to flash SU. So I lost root and flashify is out. Goomanager said No recoveries were found for my device.
OK I'll just return to stock. I followed rootjunkies YouTube video but seemed to get an error when it was about to flag. I believe it had to do with the big 2gb file I downloaded Was for jellybean and now I have kitkat.
Im currently downloading a file LGD800AT-01-V20c-2.zip and following another restore to stock video on YouTube.
I was unable to get root using ioroot24. It said....damn. Now I keep getting a blue screen with windows 8.1 when I try and root with ioroot. But it did say device not compatible or something... post model number and firmware on main xda forum.
So I can't seem to root it. I going an lg utility program to recover the phone but it won't recognize the phone even though drivers are installed (maybe a win 8.1 problem)?
I'll send $5.00 PayPal to whoever can point me in the right direction. Sorry it can't be more I'm poor right now
Thanks
D800 lg g2
can you still get to download mode(power off phone, hold volume up while connecting to pc) if the answer is yes then grab the jellybean installer from here http://forum.xda-developers.com/showthread.php?t=2663369 and go to 4.2.2 then follow this guide http://forum.xda-developers.com/showthread.php?t=2672931 for kk+root+recovery and also a few notes kk is not rootable through ioroot as of yet, 2)philz is the best recovery for stock kk because its the most compatible as of now, and if the above works you can save your money for a rainy mainly because I haven't got a paypal
Thanks... Yes I can get into download mode. I'll try this when I get back home
I was attempting following a thread like one posted. I think because I was on a windows 8 machine I was having issues. Tonight I'll go to my friends house who has a win 7 machine and give it a shot
Thanks...that link about the restore worked. That was actually one of the things I tried when I was searching for my problem originally. It failed because of the dll. I used the alternate DLL and it worked! Back in business.
So it all started today when I tried to flash Cloudy G3, it didn't work, it soft bricked I restored backup, all good. After this, my phone started acting weird by powering up again after I powered it off, not opening Quick Remote and saying SIM is not ready. So I decided to give Clopudy G3 a try once more but I needed TWRP, I installed the TWRP i needed but I got error status 7 so I used flashify which was recommended to me. Well I flashed TWRP using flashify and, now when I try to get into recovery mode it enters fastboot mode and stays there. I figure the solution to this is going back to stock, and I found that the best method is from a dude called Hyleton in XDA But that falishify thing left me without a download mode! No recovery, no download... is there even a fix for this?. Now my phone is the international version (D802) but this guy has trillions of firmaware for lots of different D802s and I don't know which one to download and use! I downloaded the one in the folder that says "D802 tot" and selected the 32GB one. Can somebode PLEASE, FOR THE LOVE OF GOD HELP ME, my knowledge on rooting is pretty basic, and a lot of the things in that thread, like for example the word "TOT" I don't understand! http://forum.xda-developers.com/showthread.php?t=2432476&highlight=d802
Now can somebody please explain this guide to me? I am wanting to do the second method (the TOT method). I would really appreciate this, REALLY REALLY APPRECIATE IT.
well
I wont be much help, but maybe i can simplify for people who come accross this thread. Ive read it a few times and im quite confused.
You said you flashed cloudyG3, had problems, then went back to stock.
What recovery did you use to backup, restore, and flash cloudy g3?
No i want to flash stock, after trying to flash Cloudy G3 I used flashify to flash TWRP and it went nuts and and now my phone is working strangely. I'm currently trying to go back to stock in the hope that it'll fix my problems and I'm using Hyleton's guide, as I have no download mode I'm gonna use a .kdz file but in his guide there's lots of KDZ files and I don't know which one to use! Any idea on that? http://forum.xda-developers.com/showthread.php?t=2432476 here's the thread and if you look at the stock firmware files you'll see there's tonnes of .kdz for the D802, could you help me find the correct one for my phone? My phone is simply D802, no other letters like the ones in that list have (which confuses me as to which file I have to use to flash stock) and I bought in the US, but I live in Argentina....
Alright, so, I'm not a huge modder, but I do like to remove the stock OS once things start slowing down (as they always do).
When I upgraded my LG G2 D800 to Cyanogenmod 11, I noticed the Accelerometer was no longer working. No big deal, I thought, it would eventually be fixed. So I just used a manual control app in the meantime.
Well, Yesterday I got a ColorCross VR headset, so I want that Accelerometer to work again. I've tried nearly everything. short of going back to stock. I think I know the solution but can't find a reliable download/get TWRP to work with my downloads. I had cm-11-20140504-SNAPSHOT-M6-d800 Installed
I found this thread http://forum.xda-developers.com/showthread.php?t=2705509 stating that a modified Kitkat Modem/baseband is needed, but the files are gone.
Then, I found this thread: http://forum.xda-developers.com/showthread.php?t=2451426 with these downloads http://downloads.codefi.re/autoprime/LG/LG_G2/G2_modems it had two modems or the LGD800, "10D_Radio" and "10O_Radio" neither worked when trying to flash the zip as downloaded using TWRP. I tried both wiping data/Cavik and flashing it right before and right after a fresh install of Cyanogenmod, both Lollipop and Kitkat versions but no luck. Couldn't open the zip file TWRP said.
So I tried a few 5.0 ROMS, CM 12 (second to latest nightly and a few others), Cloudy, Vanir, but none of them turned on my Accelerometer.
So, what I need, is an explanation on how to flash those modem files or if I was doing it correctly, a link to valid modem files. Preferably one that works with an Android 5.0.x ROM, but if I have to go back to KitKat, I can live with that, I just want my sensors to work.
Failing that, I guess I can revert all the way back to stock. But let me ask one question: Can I just flash a .zip file using TWRP if I'm not worried about making it appear completely stock (not planning on returning or selling it) without having to do the extra stuff in the guide intended for a complete return to stock? I don't need recovery to be reverted, just the original stock ROM (I tried to flash just the ROM, but either the download was damaged or I can't simply flash the stock LG G2 AT&T ROM).
I have five bucks in bitcoin I can tip whoever helps me out, either a custom ROM that installs the right modem/baseband by default and is KitKat or above or some instructions on how to get the right modem files to install + a link to them.
If a new build needs to be compiled to get the accelerometer working again, I might be able to donate a little more than that.
Right before posting this I tried downgrading to CM11-20140210-SNAPSHOT but while it installed, it still says there is no accelerometer (and doesn't auto-rotate, even when on). I also tried downgrading to CM10 (the only LG d800 CM10 on the official site) but TWRP didn't want to open the zip.
Thanks!
Neverminc, figured it out, sorry for the noob questions
*I flashed a CM12.1 nightly on top of one that was a couple days old, and the new one had all kinds of force closes. This was through CM's internal update function, which sets a recovery script and reboots into recovery to install it (which BTW failed).
So I went into TWRP and flashed the backup I made not a couple hours earlier. But now I have kind of a bootloop. Most of the time, the LG logo shows up, then it just reboots back into recovery. One time it got stuck on the logo, and I was able to see it with ADB but it told me init.sh was missing when I tried to adb shell into it.
I have three backups I tried restoring, which had /boot, /recovery, /system and /data, plus I wiped the Dalvik cache and /cache, but nothing I've tried will kick this thing loose. I've even tried formatting it back to EXT4 from F2FS, and erasing and recreating the partitions in fastboot. It seems like there's a flag somewhere telling it to reboot into recovery, but I can't find anything pertinent online. I'm really at a loss as to how to fix it, and out of ideas now.
Have you tried using the lg support tool to bring the phone back to stock?
audit13 said:
Have you tried using the lg support tool to bring the phone back to stock?
Click to expand...
Click to collapse
Yeah, I was going to edit the OP to say I've also now tried to flash back to stock, using the 20a KDZ and the LG Flash Tool 2014. When it gets to the point where it's actually about to flash, it says "USB is not connected". I have all the latest drivers, and have tried different cords, to no avail. It has been transferring files while connected in TWRP, so I'm not sure what that's about.
What about using the lg support tool to flash stock?
LG Mobile Support Tool is what LG Flash Tool calls to actually flash the ROM (otherwise you have to depend on what LGMST decides to download). It saw the phone the last time I used it, but wouldn't show LP 5.0.2 as being an available update, even though it had been released.
This thread has the instructions I've been working off of, which was posted around the time the ROM was released. It "should" work, it just doesn't. If I'm not mistaken, there may be another tool you can use, but I haven't been able to find it.
There's one other way I suppose I could go about this, but it would be delicate. I could push all the individual IMG files from a ZIP archive I have of the KDZ, but I don't know what all the partition names are, and there are like 10 of them, including laf, aboot, etc. For example, the /data partition is actually named "userdata" when you use fastboot flash.
I didn't know about the difference between the LGMST and Flash Tool.
All I know is that the LGMST was able to download the correct LP ROM for my phone, install it, and get me back to stock after I screwed things up when trying to get root.
i have same problems , here is my solutions
- use SKR tool -> 4 .fix utility -> 5.unbrick ,
if u want go back to stock, try use TOT file to go back JB
cant use kdz way
Dễ.Thương said:
i have same problems , here is my solutions
- use SKR tool -> 4 .fix utility -> 5.unbrick ,
if u want go back to stock, try use TOT file to go back JB
cant use kdz way
Click to expand...
Click to collapse
+Thanks, I have never even heard of that. But I'll give it a try. By any chance were you using F2FS?
Though I am not sure, but I'm leaning towards some kind of hardware failure -- this is a refurbished phone, so there's no telling what it's been through inside. T-Mobile sent another one overnight, which I should have in a few hours, but I still need to clean up this one if it has to go back.
audit13 said:
I didn't know about the difference between the LGMST and Flash Tool.
All I know is that the LGMST was able to download the correct LP ROM for my phone, install it, and get me back to stock after I screwed things up when trying to get root.
Click to expand...
Click to collapse
Mine told me I had the latest version, which is peculiar. Was your phone rooted at the time? Because I could understand it refusing in that case: I ran into a soft-brick on a D800 because of an OTA once. Otherwise, I'm not sure why one would work, and the other wouldn't.
voxluna said:
+Thanks, I have never even heard of that. But I'll give it a try. By any chance were you using F2FS?
Though I am not sure, but I'm leaning towards some kind of hardware failure -- this is a refurbished phone, so there's no telling what it's been through inside. T-Mobile sent another one overnight, which I should have in a few hours, but I still need to clean up this one if it has to go back.
Click to expand...
Click to collapse
i dont use f2fs , just use SKR tool with luck but i think u need flash a stock rom first
Dễ.Thương said:
i dont use f2fs , just use SKR tool with luck but i think u need flash a stock rom first
Click to expand...
Click to collapse
The reason I ask is that I had a debate in another thread about using F2FS instead of EXT4 for the filesystem. Most people suggested it's buggy and causes problems, so I wondered if that's what happened here.
When I used lgmst, my phone was giving me boot certification errors. I played around some more with it and then it would only go to download mode.
I connect the phone in download mode and the program downloaded and installed the latest LP rom for my 802 from UAE.
audit13 said:
When I used lgmst, my phone was giving me boot certification errors. I played around some more with it and then it would only go to download mode.
I connect the phone in download mode and the program downloaded and installed the latest LP rom for my 802 from UAE.
Click to expand...
Click to collapse
If u can boot your phone ,try to use Tot file , lg flash tool doesnt work anymore
LGMST fixed my 802 so there was no need for a tot file.
audit13 said:
When I used lgmst, my phone was giving me boot certification errors. I played around some more with it and then it would only go to download mode.
I connect the phone in download mode and the program downloaded and installed the latest LP rom for my 802 from UAE.
Click to expand...
Click to collapse
I wish I had a D802 -- it's ubiquitous, and thus has more support on XDA, I think. I'm not sure why T-Mobile chose to have a customized model. Same goes for AT&T, since they both use the same frequencies... and I don't know what the hell Verizon was thinking with those hideous buttons. The only differences I see between most of them is the SAR.
I am not sure that all g2 phones support the same frequencies. My 802 will not connect to LTE in Canada.
audit13 said:
I am not sure that all g2 phones support the same frequencies. My 802 will not connect to LTE in Canada.
Click to expand...
Click to collapse
Well, they don't, especially Verizon and Sprint being entirely incompatible because of CDMA. I looked it up just now, and while there are several variations of your phone, it actually looks like it has a lot less frequencies than the T-Mobile device. I was under the impression it was the other way around, but I dunno exactly -- yours is supposed to be a D803 up there. It depends on the carrier/region, and which LTE bands they're using. It may be that you get LTE somewhere else eventually.
I don't know why the hell they don't just make the phone with all the bands you expect to encounter on a continent, but I'm sure it has to do with lock-in. Because the SoC should already have that stuff baked in.
I actually have an 802 (International version, unlocked) that I bought off a guy on Kijiji. It was an incredibly cheap price because it had some scratches on the screen which are not very noticeable. Once I applied a tempered glass screen protector, you could only see the scratches from an oblique angle. The guy even included an official LG flip case which wakes and sleeps the phone This phone even has a stock LP ROM.
I love the glass protectors! That gel adhesive just melts on the screen and leaves not a single bubble. And yeah, it gets into scratches and improves them, too. I'll never use film ones again. I've personally never broken a screen, but Gorilla Glass can be scratched under the right conditions. Hey, as long as it's working for you, cheap is always good. HSPA+ isn't anything to sneeze about either -- I've had some amazing speeds on T-Mobile with it, for years now. It's a great fallback for LTE.
Okay, I managed to recover the original phone!
Something in my previous build was triggering the boot loop into recovery. This happened when the CyanogenMod updater tried to flash a new nightly, so there's a possibility it set a flag that kept it looping. But it's also possible Xposed went haywire somehow, and/or a module did. I'm not really sure why it decided to fail like this, when I had been using it without issue.
All my backups did the same thing, yet those builds ran okay when I backed them up. And I don't know why I could see the COM41 port, but not use it -- the drivers were perfect, I went to a lot of trouble to uninstall and replace them. That meant no LGFlashTool, and manual restoration (ye olde commande line).
So, what I did was use fastboot to flash every partition I could get my hands on, not just the ones you can format in TWRP. I used the 20c files from here. You basically do:
fastboot erase aboot
fastboot flash aboot.img
fastboot erase laf
fastboot flash laf.img...etc. Then you format the /system partition, and flash a Cyanogenmod nightly into there. I also flashed the /data partition, but left /data/media alone, which saves the internal storage. Then I erased and flashed /recovery just for good measure.
This is a somewhat specific fix, but maybe if someone else comes across it, it can help.
Hi, I need the ROM for this phone, more specifically, the boot.img file, as the current kernel is for the older, Indian revision of the On5, and my revision, the USA version SM-G550T1, seems not to have any copies of its firmware floating around. I'm running an OS for the SM-G550FY, which has no audio or camera support. Even if the version isn't an exact match, if you bought this phone in the USA, new, in 2016, your boot.img will probably work. I need this kernel guys. Please, if someone has an On5 in the USA, can I please get a copy of your boot.img and possibly system.img? I really care about the boot.img.
Thanks guys
-Subsentient
Firstly, did you try the updated ones at these locations:
http://www.theandroidsoul.com/galaxy-on5-stock-firmware-2-86761/
http://firmwarefile.com/samsung-sm-g550fy
Secondly, why exactly do you need the boot.img, what problem do you think it'll solve? Is there any specific issue with your current ROM that you are trying to solve?
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Subsentient said:
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Click to expand...
Click to collapse
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
prahladyeri said:
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Subsentient said:
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Click to expand...
Click to collapse
There you are! I just cannot emphasize enough that why don't you guys backup your existing ROMs before flashing a new one? It hardly takes five minutes with CWM/TWRP recovery.
In any case, what happens when you flash the Indian ROM (5.1.1)? I guess that could be your only option.
Otherwise, you can put a request on the CyanogenMod thread for your particular Samsung model.
For future reference, perform device backups and all the research before flashing a custom ROM, not after the fact.
EDIT
If you can contact Samsung support, see if you can manage to get a stock ROM from them that you can flash using ODIN or something.
I contacted them already, they basically told me to go **** myself. The missing ROM is a result of bad parameters I accidentally put in to Heimdall/ODIN flasher. I wanted to back up, but ironically, my first attempt at installing TWRP is what destroyed my ROM.
I've downloaded the kernel source code from Samsung and I'll try compiling it myself. If I create a working boot.img, I'll post it here.
prahladyeri said:
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
boot.img is where the kernel is stored. I know, I decompressed it.
Subsentient said:
boot.img is where the kernel is stored. I know, I decompressed it.
Click to expand...
Click to collapse
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
prahladyeri said:
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
Click to expand...
Click to collapse
The kernel on this device does not have loadable module support. It's entirely monolithic. And, I'm having one hell of a time building a kernel this thing is willing to boot.
I really would love just to get a ROM from someone else's SM-G550T or SM-G550T1.
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
bandtab said:
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
Click to expand...
Click to collapse
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Subsentient said:
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Click to expand...
Click to collapse
thank you!
however, i can't install twrp to my recovery partition anymore because i got FRP locked, and i can't go into my settings to disable it now. so i think my only option really is via odin. i'll see what i can do with this though, thank you very much. i did have twrp on there before but after i got frp locked i can't go into recovery mode at all.
I've been losing my mind trying to make this work.
I think if I installed the stock recovery.img it may work, but I can't find it in the files you sent. Would you or anyone else be able to make a copy of it for me? I would be eternally indebted to whoever could.
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
holydude92 said:
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
Click to expand...
Click to collapse
unfortunately smart switch is incompatible with this model phone for the time being.
I got four of these from T-Mobile when we switched from Verizon ($120 for 4 lines). Three of our Verizon phones worked well on T-Mobile (after a few APN tweaks), but my dad's old Galaxy S3 barely worked at all, and when it did, only got Edge for data. So I set one of the On5 phones up for him.
Everything was going great. I put the TWRP recovery on it, rooted it, froze all the bloatware, and backed up/restored his apps from the old S3. However, he wanted me to see if I could restore all his SMS/MMS. I tried restoring that, and the stock Messaging app started FC'ing. I installed Textra, which worked (and saw the old messages), but he never received new texts (even though he could send). So I tried removing Messaging and Textra, as well as the SMS cache (which seemed to be in "Dialer Storage (Phone SMS/MMS). I removed it, but now I'm getting an error every five seconds about "com.android.phone" and can't seem to get rid of it. I tried to restore the dialer storage backup again, but it just seems to sit forever without installing.
I've looked far and wide for a stock ROM... hoping I could just put this mess behind me, but I'm surprised to find it is nowhere to be found.
My other alternative would be to fix the com.android.phone error, but nothing seems to fix it.
Which cynogenmod or any custom os suits for Samsung Galaxy on 5.......please tell me guys.....I am bored with this official os
I was really hoping to come back to this forum and finally see stock ODIN files for this phone. I really, really want to get rid of the MetroPCS ROM I used to fix it.
Has anyone been able to find it?