Develop Bugs

Roms n themes downloaded straight to phone doesn't work

Thought I'd throw this question out there because it's driving me nuts.
twice now when I download Culk's ROM straight from the epic and flash the ROM I'm forever stuck at the yellow triangle screen.
Same thing if I download a theme from the phone.
Kind of driving me nuts because I've never had this problem on my Evo.
Anyone have any ideas?
Also let me get the obvious out of the way, I use reformat all and clear all caches before flashing anything.
If I download the same zip files onto a computer first then transfer, I have no issues
Sent from my SPH-D710 using Tapatalk

Did you install a file manager ?
Download Astro and click the box to allow internet downloads when downloading files.
Sent from my SPH-D710 using XDA App

After downloading, always check the MD5 of the file to see if it matches what the dev posted for it (if it was posted).
I generally don't have an issue with currupted downloads. It either downloads good or it fails to download (some file sharing sites just won't work from the phone).
However, not long ago, i downloaded a ROM (strong steves actually) and it said successful. After flashing, I was stuck at logo and had to use odin to get back to where I was. I checked the MD5 of what I downloaded and it was indeed wrong. Downloaded it again, via the phone, checked the MD5 (correct this time) and flashed fine.
So weather you download on phone or pc, it's ALWAYS a good idea to check the md5. If the dev doesn't post the MD5, then download it, rename it and download it again and compare the two. That's much easier than having to go back to odin to fix a problem caused by a currupted download.

I have never had good luck trying to download themes or roms from the phone. They always come out corrupt. Best way is to download it from the computer and transfer it via usb cable never wireless. That has also caused me allot of problems.

Trucking, yes. Sometimes you get lucky and the download on the phone isn't corrupted. Don't know how bad it is or if it's easily fixable. I had to start all over again, many times, with Odin flash.

[Q] SM-T217s - my first ever brick.

Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.

joshuaerda said:
Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
Click to expand...
Click to collapse
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.

joshuaerda said:
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
Click to expand...
Click to collapse
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.

254336992952
​
joshuaerda said:
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
Click to expand...
Click to collapse
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.

IAMRUDYT said:
​
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
Click to expand...
Click to collapse
same here, I have the rom, but hesitated on the firmware, waiting to see if someone gets the wifi working, not to many developers here for this tablet.

sm t217s
Ok guys. Heres my deal with this TAB. Ive rooted... Unrooted. wipe wipe wipe wippty wipe . WiFi not working. Fixed it with NB8. So here now I sit with:
----NB8 Wifi works---
----TWRP-----
Yup, pathetic i know. I cant even get the supersu to flash. TWRP wont move it over to flash off external sd card. Im not hip to abd plus i heard you leave yourself wide opento visitors when using that.
Ive eye hustled a thread on here that some friends are getting back together to rock it on a custom rom so my fingers are crossed. This tab is so neglected i mayjust go get the 210r. But i really dont want to. So my question is....
Can someone please give me links to files that work with the NB8 stock firmware. Some of the links are outdated after sprint uploaded the new bootloader. We are a small community on this tab so lets stick together on this. I dont think cynogen isgoing to do anything for it. As they concentrate on thier new phone which looks pretty sweet by the way. K im done. Going to wait for help and play with this htc one s
thats been collecting dust.

Rooted
Sent from my SM-T217S using XDA Premium 4 mobile app

[Q] Problem is beyond me

Ok so i bought a phone from a guy on craigslist a couple months ago and everything was fine its a sprint lg g2 that was running a tmobile rom he said never had an issue with it.. today i was working on my motorcycle and i must have hit system update in my pocket :/ well i have been trying to fix this phone for about 8 hrs now and im not having much luck.. first i tried to flash a new rom but couldnt get the drivers to be recognized by any computer i tried.. so i resorted to the flash tool and thinking i had a sprint g2 i downloaded the stock sprint .tot and dll. files the flash tool thinks my phone is a d801at so i downloaded the appropriate files and flashed again and it worked flawlessly i thought now the phone just force shuts down and reboots and if you lock the screen it reboots i have tried flashing it again and again and also preforming a factory reset from the phone im lost and dont know what to do if you could lead me to water i will drink lol but im lost and dont even know where to begin please help as i need my phone

someone please help...

if the build.prop was edited to make it think it was a different phone other then the sprint lg g2, you would have to fix the build.prop then re use the flash tool and tot it back to sprint stuff. You may have to flash a zip in recovery (if you have custom recovery), to fix the build prop. Make sure you have the latest drivers installed on the computer and try different usb ports and cords as well if the drivers aren't installing.

jcwxguy said:
if the build.prop was edited to make it think it was a different phone other then the sprint lg g2, you would have to fix the build.prop then re use the flash tool and tot it back to sprint stuff. You may have to flash a zip in recovery (if you have custom recovery), to fix the build prop. Make sure you have the latest drivers installed on the computer and try different usb ports and cords as well if the drivers aren't installing.
Click to expand...
Click to collapse
I have the drivers installed now i dont really know how to edit the build prop but could probably figure it out but the problem is i dont have a custom recovery and I only have a maximum of 45 sec to root and install one lol If i press to many buttons on my phone it reboots or says error

brickedg2 said:
I have the drivers installed now i dont really know how to edit the build prop but could probably figure it out but the problem is i dont have a custom recovery and I only have a maximum of 45 sec to root and install one lol If i press to many buttons on my phone it reboots or says error
Click to expand...
Click to collapse
Post your issue on this thread. XxZombiePikachu is real helpful there. http://forum.xda-developers.com/showthread.php?t=2692223
Sent from my XDABBEB VS98024A v1.2.1 using XDA free mobile app

You had a Rom called "Justin's Rom" on it. Many people had this issue. Take your SIM card out, go back to stock using the flash tool, root with auto rec, then flash cloudystock.it works for tmobile out of the box.
http://forum.xda-developers.com/showthread.php?t=2661866
Also read my post
http://forum.xda-developers.com/showthread.php?t=2729370

[Q] Rooted Note 4 can't copy roms to phone

I rooted my note 4 and noticed it was really laggy so I planned to flash a new rom. Went into Twrp and did a full wipe and when I went to load my new rom onto the mounted phone (in Twrp) I got the error message in windows saying Cannot copy file "Its file size is larger than the device limit". I did some research and this seems to happen when a file is larger than 4 GB but the file I am trying to load isn't. I have 3 potential roms all around 1.2 GB and all give the same message when trying to put them on my SD card or the internal storage. Anyone know a fix for this. I tried going to the backup I made before trying the new roms and I get a boot loop so my 2 day old phone is partially bricked at the moment. I can still get into TWRP and I still can use Odin but I can't copy and past roms onto the phone. Any help would be appreciated thanks in advance.

This is still an issue but I found a workaround, a rather obvious one that in my panic I didn't think of. I just used my SD card reader and put the roms I wanted on my SD card then put it back in my phone and installed through twrp. This worked well but now the google play store isn't working for some reason even though I am using a mostly stock rom. I'll look at that roms thread for answers

tonygotskilz said:
This is still an issue but I found a workaround, a rather obvious one that in my panic I didn't think of. I just used my SD card reader and put the roms I wanted on my SD card then put it back in my phone and installed through twrp. This worked well but now the google play store isn't working for some reason even though I am using a mostly stock rom. I'll look at that roms thread for answers
Click to expand...
Click to collapse
Extract the file SDfix.apk from this zip,install and run it. It may solve the problem. This problem happens to me everytime I flash a stock rom and this cures it.

Same Problem Here
jhill110 said:
Extract the file SDfix.apk from this zip,install and run it. It may solve the problem. This problem happens to me everytime I flash a stock rom and this cures it.
Click to expand...
Click to collapse
How do I install SDFix.akp? All I have working is TWRP 2.8. Goal is to install HD Rev 82. Phone has no OS on it right now.

Download and install foldermount from the play store. Then run it and reboot. Should fix your issue.

teebright said:
How do I install SDFix.akp? All I have working is TWRP 2.8. Goal is to install HD Rev 82. Phone has no OS on it right now.
Click to expand...
Click to collapse
Extract it... Transfer to your phone... Tap it. You will get a "install" prompt... Install... Find it in the app drawer... Run it... Look carefully for the check box, it's hard to see... Viola... Your good to go... No need to go to the play store...

Thanks, but...
jhill110 said:
Extract it... Transfer to your phone... Tap it. You will get a "install" prompt... Install... Find it in the app drawer... Run it... Look carefully for the check box, it's hard to see... Viola... Your good to go... No need to go to the play store...
Click to expand...
Click to collapse
My phone is soft-bricked right now lol. I ended up copying the files via ADB with this helpful video:
https://www.youtube.com/watch?v=NaK5OxUeDKM
This line from cmd line w/ Minimal ADB and Fastboot did the trick:
adb push yourRomNameHere.zip /sdcard/.

Need help badly. No OS cannot boot passed twrp/cwm

Hello. Ive been 3 days with no phone now and am at my wits' end. I converted to developer, and in trying to clean install a ROM, messed something up...badly.
I can flash TWRP or CWM both through Odin, but no roms work at all. All of them get stuck at system.img.ext4 for about 10 minutes and then it fails. I cant flash anything through recovery, either, because neither recovery program can read my SD card for some reason. Ive read up on similar issues, but all of the fixes involve formatting the SD card through a functioning ROM, which isnt a possibility for me. I am desperate at this point...very desperate. Also, Ive tried the XDA IRC rooms but i'm not sure if i even join them correctly, as for days i cant get even a single letter response from any of the listed participants. Ive gotta be doing something wrong. Any help would be greatly appreciated. At this point i dont care if i lock my bootloader forever i just NEED a working phone.
Smartswitch doesnt work because it wont recognize my device, and when prompted for a S/N, nothing works...ive tried everything from the IMEI to the SIM s/n from the original package sleeve.

SOLVED:. talked to Samsung reps and confirmed that the note4 in fact has no serial number and that function if the recovery tool doesn't work for them. Did a day or researching on ADB stuff, which was new to me, and got cm13 successfully working via side load. After that, cm formatted the memory card to he readable, and all seems right in my note4 world for now.

8wrlobo said:
SOLVED:. talked to Samsung reps and confirmed that the note4 in fact has no serial number and that function if the recovery tool doesn't work for them. Did a day or researching on ADB stuff, which was new to me, and got cm13 successfully working via side load. After that, cm formatted the memory card to he readable, and all seems right in my note4 world for now.
Click to expand...
Click to collapse
So what exactly did you do been trying to get a rom to work on mine that I did the dev convert on. I was on the latest ota update. Got it rooted and flashed a different kernel got it to boot on stock firmware but can't get any other rom to install and boot.
Sent from my SM-N910V using XDA-Developers mobile app

slowpoke2006 said:
So what exactly did you do been trying to get a rom to work on mine that I did the dev convert on. I was on the latest ota update. Got it rooted and flashed a different kernel got it to boot on stock firmware but can't get any other rom to install and boot.
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah Odin and sd card options all fell flat on their faces for me...I never did figure out the system.img.ext4 hangup I got from odin.
In the end, I used Odin (3.9 iirc) to flash twrp. Flashing two or cwm both never gave me any trouble. From there, I downloaded the cm13 latest build from the thread here and followed this guide (http://forum.xda-developers.com/showthread.php?t=2317986). Sideload failed for me as well, but I was able to push the rom to my phone.
I downloaded a adb/fastboot program (https://androidmtk.com/download-minimal-adb-and-fastboot-tool) and in the x86 program files folder for it, made a new folder called FML lol and moved the ROM zip folder into it. Then did
abd push ___________.zip /sdcard/_________.zip. (note that I don't remember exact adb commands...it had been hours of frustration. Definitely consult the experts (not me) here before trying what I did. In the end it worked great. Good luck.
It was my first experience with adB stuff and tons of trialife and and error but I sure learned tons after all the research and frustration.

8wrlobo said:
Yeah Odin and sd card options all fell flat on their faces for me...I never did figure out the system.img.ext4 hangup I got from odin.
In the end, I used Odin (3.9 iirc) to flash twrp. Flashing two or cwm both never gave me any trouble. From there, I downloaded the cm13 latest build from the thread here and followed this guide (http://forum.xda-developers.com/showthread.php?t=2317986). Sideload failed for me as well, but I was able to push the rom to my phone.
I downloaded a adb/fastboot program (https://androidmtk.com/download-minimal-adb-and-fastboot-tool) and in the x86 program files folder for it, made a new folder called FML lol and moved the ROM zip folder into it. Then did
abd push ___________.zip /sdcard/_________.zip. (note that I don't remember exact adb commands...it had been hours of frustration. Definitely consult the experts (not me) here before trying what I did. In the end it worked great. Good luck.
It was my first experience with adB stuff and tons of trialife and and error but I sure learned tons after all the research and frustration.
Click to expand...
Click to collapse
OK so once you were able to get the rom pushed to your phone it installed fine? I just can't get them to install and boot right. What version were you on and did you do safe updates? Guess I'll have to start a new thread on it
Sent from my SM-N910V using XDA-Developers mobile app

I was/am at PA1. I did the smartswitch emergency recovery to stock PA1 and then redid the developer conversion, before having a hangup and wiping everything with twrp...like everything (BAD idea). That is what caused all my odin and sd card woes to begin with.