Would it be okay to remove the following files?:
hboot_7501a_1.49.0000_100124.nb0
nv_2.11_0103_PRL58005_full.nb
I would just like to know. I'm going to make my own rom...
No would be bad to remove those files. I would suggest you do A LOT of reading here before you attempt a rom.
Well, I wanted to remove them because I see no sense in updating the PRL. Anyways, people could loose their Metro PCS and I don't need to HBOOT file in there anyways...
ummmmmmmm ok. why ask if you have already made up your mind?
I tried removing CIQ files, my samsung tab 10.1 is dead now, it's STUCK at the logo SAMSUNG, i hate seeing it, please help i don't know what to do, can i take it for warranty and stuff? will they fix it? Or will flashing the firmware work, but it's too risky
Related
This may be a stupid question but, I won't know unless I ask.. I recently started playing around with a rom kitchen and have developed a rom using the official 2.1 update from my carrier. I was wondering if there was a way to load this rom without rooting first. I didnt know if there was a way i could replace my rom with the stock rom in the same manner that I extracted it. I simply started the RUU and pulled the zip file from the TEMP folder, and was wondering if i could just do a cut and paste? It almost sounds so simple that it simply wont work. Any ideas? If i have to root i will, but the only method I have got to work is the goldcard method and i would like to avoid all that mess if I could. Thanks.
you need root. goldcard isn't so messy method, in my opinion. if you need help just say.
Thanks, I figured as much. I don't have a problem with rooting, I was hoping there was a way around it because I have a few friends who want to try my rom who are with the same carrier and the word root freaks them out.
I think I will try and convince them to root any. One other question though; if all goes well with the root and we are able create a recovery backup; what are the chances of bricking the phone if my rom sucks? I don't foresee this as an issue as I literally just took the stock and added superuser and a few other things. My main concern is the radio.img, i'm not 100% sure I got that loaded correctly.
Thanks again
Moved to Q&A as not development
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
JJMT said:
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
Click to expand...
Click to collapse
Shouldn't break anything. Most are still waiting for the update. Personally I was impatient and flashed it through ODIN last night.
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
JJMT said:
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
Click to expand...
Click to collapse
Go to the Development section that are a few threads about this. I looks like anyone with a lag fix, or GPS fix (from JI2) where having this issue, plus I have seen stock people having it too.
Or you can go read my blog post here. the post tells the steps I took to get back the JFD, but you could flash JI6 instead.
you will need to flash JI6 with ODIN to restore, you can not just do a nandroid restore, it is an issue with the kernel and nandroid does not restore/backup the kernel.
*facepalm*@Samsung
http://forum.xda-developers.com/showthread.php?t=803492
Anderdroid said:
*facepalm*@Samsung
Click to expand...
Click to collapse
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
dan0zone said:
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
Click to expand...
Click to collapse
So now instead, they get flooded with returns because the phone isn't what people expected.
zephiK said:
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
Click to expand...
Click to collapse
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
camalot said:
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
Click to expand...
Click to collapse
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
zephiK said:
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
Click to expand...
Click to collapse
Well, I know the 2 people that updated stock and got stuck at the vibrant screen were 100% stock because they both called me on what they need to do. one came over and I fixed it with ODIN back to stock (JI6) and the other just said he'd call TMO and get a replacement. they dont even know what rooting is, or that there is a site like that that they can get files to do "one click root"
OK. I'm the OP and I'm back. I was traveling today (with a phone flashed back to stock - that's as far as I got before getting kicked out of the hotel). I've now got the ROM restored and I'm where I was before trying to install the update.
My question is this (probably simple): my phone still wants to do the update. How do I make it go away? I can't install it, and I don't want to have to postpone it every day. Is there a cache I can clear or something?
You could just update it through Odin. I'm on stock with root and JAC's oc/uv kernel and the OTA failed but Odin worked perfectly.
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
JJMT said:
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
Click to expand...
Click to collapse
It will only stop once you are on JI6
camalot said:
It will only stop once you are on JI6
Click to expand...
Click to collapse
OK. I guess I will have to try to push the update through odin. Can someone point me to a link to the files?
I'm kind of irritated by this whole thing. I'm pleased with tmo for pushing the update out, but I mean, really, even Windows allows you to decline to install an update.
http://forum.xda-developers.com/showthread.php?t=798125
chad658eku said:
http://forum.xda-developers.com/showthread.php?t=798125
Click to expand...
Click to collapse
Thanks for the link. It really looks to me that I'm going to need to flash to a stock ROM before flashing JI6. That, as they say, is a bummer.
As I am actually quite content at the moment with Vibrant9, it really seems to me that it would be easier to somehow remove whatever it is on my phone that is requesting that I update. Presumably there is an update.zip file sitting somewhere, that will be copied into sdcard before the updater involves reboot recovery. Any ideas where to look?
I would really rather not do any further flashing until is an official Froyo to flash to.
JWhipple said:
So now instead, they get flooded with returns because the phone isn't what people expected.
Click to expand...
Click to collapse
Flooded with returns by morons who think they are smart.
Hello, I am an ex DX owner and I'm use to just flashing basic stuff, ROMs and themes.
Well, now that I have an unlocked bootloader in my hands, I don't know where to start. I don't know what an RUU is or a .img or a kernel, really. How do I get back to complete stock Thunderbolt, like it came? Is there a way you can fix a bricked phone without looking like an idiot at the VZW store?
If somebody would like to tell me the basics and what I can do to NOT brick my phone that would be great.
A RUU is a full img of your phone basically and that will get you back to stock like how you bought as long as you use the newest RUU right now. a kernel is was sets your mhz/ ghz otherwise ur speed basically. and .img is just a file extension that besides when rooting you wont see much unless u brick your phone or dev. And yes u cant bricked a tbolt as far as we know, the guys at teamandirc tried and still brought it back to life.
unlocked bootloader means you can fully flash a rom, new os with the correct kernel and all files without killing ur phone by removing something you shouldnt.
hope that answers ur questions mostly. answered them simple and short to the point. if you need more i can link you some info to help you out.
Okay thank you! that helped a lot. thanks again!
Hi! I'm a total cell newbie, so pardon.
I want to root my phone just so I can actually put apps on my SD card. There's a few bits I want to understand first:
I've read that I am not going to want to accept OTAs. I've also read that some phones automatically accept OTAs. Since I don't plan to change my ROM (and I am not entirely sure what ROM refers to... is my "TouchWiz" a ROM?), how can I be sure that my default software isn't going to go trying to install OTAs without asking me?
Is a bricked device actually completely worthless? There's no way to get it back into a working state at ALL, or just no way to get it working without help from your carrier? And what is a "soft brick"?
If I manage to root my phone with the CASUAL one-touch program, how do I unroot if I were interested in doing so?
Please either avoid or explain any jargon you may use in your reply. For instance, if you refer to opening an app.... please just do the courtesy of saying it's an app rather than just assuming I know. If you use an acronym, assume I have no idea what it stands for. It took me forever to figure out what an OTA was, and I still don't quite understand what a ROM is... and that's the extent of my acronyms.
Thanks.
Wow, a lot of demands. Why not start here, as it should answer many of your questions. Threads are stickied for a reason.
http://forum.xda-developers.com/showthread.php?t=2024207
Mandolin Bee said:
Hi! I'm a total cell newbie, so pardon.
I want to root my phone just so I can actually put apps on my SD card. There's a few bits I want to understand first:
I've read that I am not going to want to accept OTAs. I've also read that some phones automatically accept OTAs. Since I don't plan to change my ROM (and I am not entirely sure what ROM refers to... is my "TouchWiz" a ROM?), how can I be sure that my default software isn't going to go trying to install OTAs without asking me?
Is a bricked device actually completely worthless? There's no way to get it back into a working state at ALL, or just no way to get it working without help from your carrier? And what is a "soft brick"?
If I manage to root my phone with the CASUAL one-touch program, how do I unroot if I were interested in doing so?
Please either avoid or explain any jargon you may use in your reply. For instance, if you refer to opening an app.... please just do the courtesy of saying it's an app rather than just assuming I know. If you use an acronym, assume I have no idea what it stands for. It took me forever to figure out what an OTA was, and I still don't quite understand what a ROM is... and that's the extent of my acronyms.
Thanks.
Click to expand...
Click to collapse
Touch wiz is a style of ROM if you will.
Touch wiz roms for Samsung.
Motor blur roms for Motorola.
Sense roms for HTC
Aosp roms for nexus phones.
When you have a "touch wiz ROM"
It builds from the stock base code basically. They add freatures and themes and basically ROMs are endless to what they can do.
My phone never tells me about OTAs.
I believe the only time they do this is when on a stock rooted ROM is when something bad could go wrong
Never had any problems on custom ROMs however.
Next,
Bricked devices are very rare and only happen out of stupidity or carelessness in most cases.
Google will tell you how to fix. But I wouldn't worry about it.
As a very frequent flasher of ROMs I have experienced many of times a soft brick. Or a phone in boot loop.
This is when the device powers on but will not boot up. ( stuck on boot animation or splash screen are most common.)
ALL OF THESE ARE FIXABLE.
You can always wipe in a recovery and normally that fixes it.
Soft bricks normally happen from not wiping or bad download.
Also remember you have Odin as a last resort.
Also you can read the sticky threads in android development to figure out how to unroot
They will give you a better explanation on how to do so.
All this is answered by xda and Google.
They are what taught me what I know
They will teach you as well over time.
PM me if you have any other questions
Hit the thanks button so I feel important!
Haha
God bless the American people.
Okay, Im pretty new to XDA forums, and well, android devices in general. I recently purchased a Galaxy Tab 3. Which I was able to root successfully, but to later find out, it somehow got a virus and is now running super slow, even after a Factory Reset. But anyways. This comes to what I need help with.
I have a
Samsung Galaxy S4 AT&T
SAMSUNG SGH-1337
Android Version: 4.4.2
Base: 1337UCUFNB1
Im wanting to root for more performance and just to have alot more access to my device.
Now i have searched on google for hours at a time, but cant seem to find the same exact device tutorial for my phone.
I need this for work, so I want to make sure im doing this exactly right, and don't screw up my phone, or loose any contact data or anything of that sort. Can someone link me to a Simple tutorial that can help me root this device? Im new to the Android community so sorry for asking a stupid question! thanks guys!
tragicMagic2014 said:
Okay, Im pretty new to XDA forums, and well, android devices in general. I recently purchased a Galaxy Tab 3. Which I was able to root successfully, but to later find out, it somehow got a virus and is now running super slow, even after a Factory Reset. But anyways. This comes to what I need help with.
I have a
Samsung Galaxy S4 AT&T
SAMSUNG SGH-1337
Android Version: 4.4.2
Base: 1337UCUFNB1
Im wanting to root for more performance and just to have alot more access to my device.
Now i have searched on google for hours at a time, but cant seem to find the same exact device tutorial for my phone.
I need this for work, so I want to make sure im doing this exactly right, and don't screw up my phone, or loose any contact data or anything of that sort. Can someone link me to a Simple tutorial that can help me root this device? Im new to the Android community so sorry for asking a stupid question! thanks guys!
Click to expand...
Click to collapse
1st off, the Galaxy Tab definitely doesn't have a virus. Malware perhaps, but not a virus. To make sure you completely rid your tablet of any left over issues, it would be recommended to reinstall the whole OS via the Odin program as that rewrites the /system partition too as the factory data reset only clears out /data. After you reinstall, then do a factory reset again. If the issue persists after that, there might be another problem that is not software related. It would serve you well to understand how to use Odin. It is a great tool that can get you out of MOST trouble you can find yourself in when modifying your devices.
http://forum.xda-developers.com/showthread.php?t=2459734
Just make sure you use the corresponding firmware/software for your model as there are a few different Galaxy Tabs and it matters the size and wifi or data+wifi as well.
As far as the rooting of the S4, well, unfortunately you got pretty much the trickiest one to do. Remember Odin ^^^, this will be another reason to get comfortable with it...
http://forum.xda-developers.com/showthread.php?t=2663545
34993329
OH!! Thanks for the advice on the Tab. Hmm The s4 is the trickiest one? Is it even worth the time to root then? I mean, I had the tab for a week rooted. And it was very useful. Would the s4 be the same?
And would there be a video tutorial on this? That way im 100% sure im doing it right?
tragicMagic2014 said:
OH!! Thanks for the advice on the Tab. Hmm The s4 is the trickiest one? Is it even worth the time to root then? I mean, I had the tab for a week rooted. And it was very useful. Would the s4 be the same?
And would there be a video tutorial on this? That way im 100% sure im doing it right?
Click to expand...
Click to collapse
Is it worth it to root it? Only you would be able to answer that. Personally, I couldn't imagine NOT being rooted. I hate not having control over my phone. There are a couple of extra steps here, but nothing some careful reading and well placed questions couldn't get you through. And the chance of you doing something that can't be fixed by Odin, is not impossible, but very unlikely. I've done stuff like this 100s of times and have never bricked one doing these types of things. This thread seems to have broken it down a bit more clearly:
http://forum.xda-developers.com/showthread.php?p=51331630
But read that, and read through some of the comments. Any issue you come across has almost certainly popped up somewhere in those 2 threads with 100s of responses.
Now one thing im not understanding, is the downgrading? And How do ROMS work?
and how would i know what model it is. Example: Mk2,Mk4?
Well, there is currently no method to root 4.4.2 as is, which is why you need to downgrade back to 4.3, since there is a way to root on it, and then it tells you how to update back to 4.4.2 while keeping the root access. Roms (in the phone/tablet world) are basically a package (usually zip format) that contains the operating system. Think of it as a Windows or Linux install disc, in zip format.
Just a quick little beginner's guide to the main terminology you will see:
http://www.androidpit.com/custom-rom-and-root-the-most-important-terms-explained
Okay! Thanks for all of your help! Ill try to root my device. If i have any questions, ill come back here Thanks!
Happy to help, though you might have better luck asking your questions in those threads. I understand how to do this, but haven't had a chance to root one on 4.4.2, so the people who have done it recently probably have it fresh in their mind still.