Hi guys,
I just got a vega today and the first thing I did was install vegarom.
That message that pops up about being ripped off is horrid. Can I remove it?
Thanks
(Please don't flame me)
I don't mind switching it with the logo of the team that built vegacomb, I just don't want that nasty message there
Sent from my Dell Streak using Tapatalk
I would like the same thing on my device too.
Not very appealing everytime I restart it or when someone sees that screen. I know its there to warn people to not get fooled by some Chinese rip off suppliers, but would be good to have some alternative there.
This isn't something that I really want to encourage if I'm being honest. But if you want to do this yourself, I will give one hint:
*.rle - It's in boot
newbe5
Thank you for your hint
Do you have a file, perhaps with your team logo I can replace it with?
You're welcome to pm me
Sent from my Dell Streak using Tapatalk
Bayton said:
Thank you for your hint
Do you have a file, perhaps with your team logo I can replace it with?
You're welcome to pm me
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
Or maybe make it look a little bit nicer?
Or could it be done so that it only comes up for the first say 3 times you turn the Vega on?
It's an all-or-nothing thing I'm afraid. It was made intentionally to be very in-your-face, to stop people from missing it
Zebwen said:
It's an all-or-nothing thing I'm afraid. It was made intentionally to be very in-your-face, to stop people from missing it
Click to expand...
Click to collapse
Thats fair enough, and to be fair, it only lasts for a matter of seconds so I can live with it
Zebwen said:
It's an all-or-nothing thing I'm afraid. It was made intentionally to be very in-your-face, to stop people from missing it
Click to expand...
Click to collapse
Oh, ok. Well though I'd rather replace it with your logo (or something) I can also just remove it.
I appreciate your help!
Sent from my Dell Streak using Tapatalk
Can some one please PM me how to do it ? I am not quite sure where the file is located at and can't search for it using the app I have.
Many thanks
I'm also struggling to find anything. From what I've been reading there's a boot partition named mtd2 and I think, based on my limited knowledge, it could be in there.
I'm not sure if that is or could be writable, or if you have to extract the update.zip and edit it, then having to reflash the vega in order for it to go away. I can donate to anyone interested in figuring it out.
Either way, I'm determined to get it removed, it irritates me every time I turn my vega on.
It certainly doesn't help that when I adb shell into it, all I get are random letters and numbers when entering "ls" so I have no discernible way of telling where I am or what I'm doing most of the time. Oh, and debugging seems to disconnect itself from my laptop every 5 minutes, requiring a reboot to get back into it.
You need to unpack the boot.img, replace the file newbie5 said. Then repack and flash the modified boot.img
I am not going into more detail as newbie5 does not want it to be made to easy, I can see why.
You don't need to, thanks. I read it elsewhere on XDA and assumed it would also work in this case.
Sent from my Dell Streak using Tapatalk
I have sorted it.. much better!
I'm not sure if something went wrong with the repacking, but I've had some random reboots since. Trying to figure out if it is related.
Sent from my Dell Streak using Tapatalk
Scrap that, reboots were unrelated and have stopped
Sent from my VegaComb using Tapatalk
How big a deal is this? I don't get it.
I'm curious - how often do people reboot their Vega's? I boot might maybe a couple of times a month and then, the screen is only visible for a few seconds so it's number 657,391 on my list of things to worry about.
IMHO the value of it far outweighs a few seconds a month.
I turn mine off/on many times during the day.
If it doesn't concern you then that's fine. Move along now, there's a good chap.
Sent from my Dell Streak using Tapatalk
simonta said:
How big a deal is this? I don't get it.
I'm curious - how often do people reboot their Vega's? I boot might maybe a couple of times a month and then, the screen is only visible for a few seconds so it's number 657,391 on my list of things to worry about.
IMHO the value of it far outweighs a few seconds a month.
Click to expand...
Click to collapse
I couldn't agree more. What was your vega like out of the box? What is it like now?
Jesus, small price to pay for the the team trying to protect their VOLUNTARY work.
Good way to get rid of it? Don't use this rom.
Better way to get rid of it? Edit boot.img.
Do you hear that? It's the sound of me having my cake, and eating it too.
Sent from my Dell Streak using Tapatalk
Touche'! And enjoy the cake.
Related
hey guys,
I have a basically new vibrant (no scratches or scuffs) that is stuck in the phone-!-pc screen after using odin to flash a new firmware. I'm kinda new at this and am tired of trying to figure out how to get it working.
I'm willing to sell it for low price.. if there's anyone interested hit me up at [email protected]
Thanks
Ryan
EDIT: Sold. mods you can delete this thread
ryanolson7 said:
hey guys,
I have a basically new vibrant (no scratches or scuffs) that is stuck in the phone-!-pc screen after using odin to flash a new firmware. I'm kinda new at this and am tired of trying to figure out how to get it working.
I'm willing to sell it for low price.. if there's anyone interested hit me up at [email protected]
Thanks
Ryan
Click to expand...
Click to collapse
Pull out the battery.
Wait 30 seconds.
Put USB cable in.
Hold both volume buttons.
Put battery in while holding both volume buttons.
Your in download mode.
Sent from my SGH-T959 using XDA App
you can also pull battery, put battery back in. hold vol+/vol- while plugging in USB, that might work too.
I'll take it off your hands for $100
i dont blame you, but remember the vibrant is almost unbrickable. if you cann see pc screen or charging status icon your good. keep trying then sell it for max profit
Ill send you 110.
Sent from my SGH-T959 using XDA App
Sell it full price dude people r gonna try to scam u but u can fix this in 5 minutes.
Sent from my SGH-T959 using XDA App
well you dont need to pull a battery either... you just hold the up down volume toggle along with the power but and when the screen goes black immediately remove your finger from the power button while still holding up down volume toggle. this will place u back into download mode. don't sell your phone because of frustration. you cant brick this phone.
120 right now. Me me me!
Sent from my GT-I9000 using XDA App
And how is that a scam? Person offers deal, person accepts deal. Sounds more like capitalism to me....
Sent from my GT-I9000 using XDA App
$121.00 . We're going by Price is Right rules, right?
monstah_rain said:
$121.00 . We're going by Price is Right rules, right?
Click to expand...
Click to collapse
**suspense**
**can't take it anymore**
$150!!!!! And that's my final offer!
sent my payment
Hey Ryan - thanks for selling the phone to me for $130.
You received my PayPal payment and I am still waiting to receive tracking information.
Under normal circumstances, a message like this would be more appropriate to send through private channels, but I have tried emailing you for three days and calling you back at your google voice number without success. You were very easy to get a hold of before I paid, but seem to have vanished the moment I requested tracking information.
I hope you are not up to something sneaky. I assume with your online presence on twitter, in your blog, and elsewhere, that you're not trying to deceive me, and that you've simply decided to take a break from the internet and from your phone for a few days.
Hmm, except your twitter account was updated just hours ago?
Further googling shows you're actually an Android Developer. Therefore, you probably pretty much know this phone is permanently bricked, but when we talked you came across as though you weren't familiar with procedures for recovering from a soft brick. I find that difficult to believe given your Android experience.
Send me my brick, or send me a refund.
I bought a bricked phone, yes, but right now I feel like my brain is bricked for buying it.
Due diligence folks, due diligence.
I'm on my third one. Just call tmobile tell them your not sure what happened. It's a known issue and if it's in good physical condition they will send you a new one.
Sent from my GT-I9000 using XDA App
Pancake345 said:
I'm on my third one. Just call tmobile tell them your not sure what happened. It's a known issue and if it's in good physical condition they will send you a new one.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You missed something here man the OP sold the phone to the person above you and is acting like he's going burn him by not giving him the phone he promised to sell. Sad hope OP does what's right.
Sent from my SGH-T959 using XDA App
Pancake345 said:
I'm on my third one. Just call tmobile tell them your not sure what happened. It's a known issue and if it's in good physical condition they will send you a new one.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Do you have to buy it from tmobile to get this privilege?
tonie972 said:
Do you have to buy it from tmobile to get this privilege?
Click to expand...
Click to collapse
Don't mention that you didn't but from tmo. As long as it show you are using a vibrant on there system they will give the replacement.
Sent from my SGH-T959 using XDA App
Don't give up cuz I was in the same position. Plus the best way to learned is from your mistakes. YouTube & Google good tools to learn. YouTube give you visualization & Google the reading understanding part. I believe you can fix your phone no need to sale it. One thing you need to be patient if not you are not going to learn. Without being patient is important in doing all this learning about Android OS. Modifying, rooting & flash customs roms.
Me... sometimes I want to take my hair off cuz it gets to be but I remember to be patient.
Lucky you that he sold the phone to you.
falafelfro said:
Hey Ryan - thanks for selling the phone to me for $130.
You received my PayPal payment and I am still waiting to receive tracking information.
Under normal circumstances, a message like this would be more appropriate to send through private channels, but I have tried emailing you for three days and calling you back at your google voice number without success. You were very easy to get a hold of before I paid, but seem to have vanished the moment I requested tracking information.
I hope you are not up to something sneaky. I assume with your online presence on twitter, in your blog, and elsewhere, that you're not trying to deceive me, and that you've simply decided to take a break from the internet and from your phone for a few days.
Hmm, except your twitter account was updated just hours ago?
Further googling shows you're actually an Android Developer. Therefore, you probably pretty much know this phone is permanently bricked, but when we talked you came across as though you weren't familiar with procedures for recovering from a soft brick. I find that difficult to believe given your Android experience.
Send me my brick, or send me a refund.
I bought a bricked phone, yes, but right now I feel like my brain is bricked for buying it.
Due diligence folks, due diligence.
Click to expand...
Click to collapse
That's what you get for trying to rip him the **** off.
what would happen if i sent my phone back to the manufacture rooted after receiving a replacment phone?
They would probably make you pay full price for it
Sent from my HTC Glacier using XDA App
shadowdroid said:
what would happen if i sent my phone back to the manufacture rooted after receiving a replacment phone?
Click to expand...
Click to collapse
Are you sending it back to HTC or T-Mobile?
Warranty is voided when you root. IF they find it's rooted, I would think there would be a process they would have to go through in order for them to charge you for it. Worst case, if they did catch it, you could say 'I don't know what you are talking about'.
If they push up against you even more, you could concede and tell them to send the phone back to you and then you could unroot and sell it yourself.
Unrooting takes less than 5 minutes. I just did it 2 nights ago and rooting my new phone and unrooting my old phone took a total of 10 minutes.
daryllh said:
Are you sending it back to HTC or T-Mobile?
Warranty is voided when you root. IF they find it's rooted, I would think there would be a process they would have to go through in order for them to charge you for it. Worst case, if they did catch it, you could say 'I don't know what you are talking about'.
If they push up against you even more, you could concede and tell them to send the phone back to you and then you could unroot and sell it yourself.
Unrooting takes less than 5 minutes. I just did it 2 nights ago and rooting my new phone and unrooting my old phone took a total of 10 minutes.
Click to expand...
Click to collapse
Can you help me then?i can't get the stock recovery to flash via terminal and I have no idea how to use fast boot
shadowdroid said:
Can you help me then?i can't get the stock recovery to flash via terminal and I have no idea how to use fast boot
Click to expand...
Click to collapse
So you rooted and have no idea how to recover? Was rooting cool? Did it make you cooler while it worked?
But now you're stuck right? Rooted to be cool but now out in the cold because you have no idea what to do?
And you wanna send the phone back thus driving up manufacturer and carrier costs that are eventually handed down to us consumers? The same people you are now asking for help?
Go figure.
You think maybe he is sending the phone back because of the screen issues? That has nothing to do with rooting a phone.
EDIT: I realize rooting the phone forces mfg to spend time changing back in order to sell it so my question isn't as valid as I previously thought. Considering the amounts of people sending their phones back, this instance hardly makes a dent.
But...
Seriously dude. Stop trying to sound like a tough guy. We get it, you aren't going to help.
CBConsultation said:
So you rooted and have no idea how to recover? Was rooting cool? Did it make you cooler while it worked?
But now you're stuck right? Rooted to be cool but now out in the cold because you have no idea what to do?
And you wanna send the phone back thus driving up manufacturer and carrier costs that are eventually handed down to us consumers? The same people you are now asking for help?
Go figure.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
shadowdroid said:
Can you help me then?i can't get the stock recovery to flash via terminal and I have no idea how to use fast boot
Click to expand...
Click to collapse
What are the commands that you are using also do you have the recovery.img in the root of your sdcard (not in any folders)
Now I haven't flashed anything via terminal since I first rooted my g1 but heres the commands I used in telnet (found in the market)
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
I'm pretty sure you can do these via terminal but not positive on that one.
Sent from my HTC Glacier using XDA App
daryllh said:
You think maybe he is sending the phone back because of the screen issues? That has nothing to do with rooting a phone.
Seriously dude. Stop trying to sound like a tough guy. We get it, you aren't going to help.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Really? Where in this entire thread was the screen mentioned? Seriously!? You need to read yourself.
Tough guy? Get a grip. Stop trying to be an internet commando and police yourself.
Sorry if I somehow offended your sensitive nature. This site is about phones so remove the personal garbage in your posts.
i've returned like 10 phones to t-mobile, g1...mytouch....vibrant....cliq and Mytouch 4G all were rooted and all i did was put a stockish looking rom back on.
they aren't checking for that when the phones come back. they are looking for cracks in the screen and liquid damage, that's it.
I was a manager for t-mobile for 1.5 years...i know the sop on this.
Also did like 5 warranty replacements through HTC (Nexus one) and sent 4 of them unlocked and never had a problem.
you're fine, don't sweat it. Just make it look as stock looking as possible when you send it in.
I edited my post since you responded. However, the reason he is sending it back isn't known so that's a stalemate.
It's not about policing. It's about helping or not helping without oozing elitism. Your condescending answer doesn't do the forum any good.
CBConsultation said:
Really? Where in this entire thread was the screen mentioned? Seriously!? You need to read yourself.
Tough guy? Get a grip. Stop trying to be an internet commando and police yourself.
Sorry if I somehow offended your sensitive nature. This site is about phones so remove the personal garbage in your posts.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
I am surprised by the silliness that I read earlier in this thread. It was more in keeping with the "cheer leading" threads that do not contain any useful information and not at all in keeping the substance of XDA developers - probably the premier how-to tech thread for mobile devices.
It is due to the information contained in this forum that TMo and other vendors sell many of their devices and services in the first place. The proposition that rooting and modifying these devices (an occasionally returning a few) is going to cost other buyers anything is totally absurd.
Fortunately, there were some useful follow-on posts on how to unroot it, and especially the post from the TMo guy.
Getting the best use from your device is what XDA is all about - lets keep it rolling!
Can someone please make a video to demonstrate the random reboot and boot loop problem happening on a completely stock, factory resetted Transformer with no 3rd party apps?
Not saying you guys have to prove anything but if we have this kind of video and post it everywhere, it will garner much more attention and maybe Asus will do something quicker.
Just the fact that you are posting this tells me that NOBODY will be able to create a video that you would accept as "proof". Besides, how are we supposed to videotape a "random" reboot that may take up to 24 hours (or more) to show up (and again, at RANDOM). The video would have multiple cuts and would be impossible to authenticate.
I think we know what a reboot or a bootloop look like... And we've sent lots of logs to Asus as real "proof".
Trust me, Asus knows there is REALLY a problem. We don't need to spend countless hours trying to capture a random reboot on tape.
Give me a break.
And before anyone calls me an anti-asus troll, please don't get me wrong - I love their products and nobody else makes a comparable tablet/dock combo! They release very frequent firmware updates which I also love! However, their response to this particular issue has been less than stellar.
Sure, Ill record a ~78h long video (roughly the frequency of my random reboots so far).
Just buy me a bigass HDD and Ill email the recording to you. Then I want to you watch every second of it in one go, no fast-forwarding or skipping.
... seriously though, a clip of a random reboot doesnt help the developers ONE BIT.
"right, so the device restarted... lets fix it! *searches code for entry "random restart"* oh look at that, no hits..."
There is a reason software uses logfiles. If you'd ever looked at one you'd know they provide a million times more information than a video clip will ever do.
Theres a saying, "a picture says more than a thousand words". But in coding its the exact opposite, a picture is more or less useless.
ASUS knows about this issue. But fixing something thats completely RANDOM and doesnt even happen on ALL devices makes it a ***** to pin-point in the code.
If you want to help asus - send them your logcats. Not a 78h long, useless, video.
Actually, Asus has one (mine) at their repair facility. My Transformer died (endless reboot to the eeepad screen) which nothing would stop, not connecting to ac, not holding the power button, not holding power and volume down. It was rma'd and returned with a factory restored image of ics, nothing on it that didn't come from Asus. I turned it off, and it would not turn back on. This is a completely stock tablet, never rooted, no 3rd party apps, heck I never even entered my Goggle Account. And it was working fine before ICS. They've had it since March 11 and have asked me to describe what happened a couple of times. I told them to fix it, turn it off for an hour or 2, and try to restart it. So, a totally stock tablet, fresh ICS from Asus, no 3rd party apps, and it won't work. If I ever get it back I'll let you know what they claim they did.
jtrosky said:
Just the fact that you are posting this tells me that NOBODY will be able to create a video that you would accept as "proof". Besides, how are we supposed to videotape a "random" reboot that may take up to 24 hours (or more) to show up (and again, at RANDOM). The video would have multiple cuts and would be impossible to authenticate.
I think we know what a reboot or a bootloop look like... And we've sent lots of logs to Asus as real "proof".
Trust me, Asus knows there is REALLY a problem. We don't need to spend countless hours trying to capture a random reboot on tape.
Click to expand...
Click to collapse
Hm what makes you think you would have to record the entire duration.
It can be cut. You can start recording when it's boot looping. Just show your app drawer or list of apps in your settings afterwards.
Hah I can't believe some people in this thread thought you would have to show the whole duration. It can be cut. It can be fast forwarded.
Just needs to show the boot loop or random reboot happening AND show the list of apps afterwards, not before.
I remember seeing a similar video for Prime. Kinda surprises me that nobody posted a video yet and it's been over a month since we got ICS and all the issues.
horndroid said:
Hm what makes you think you would have to record the entire duration.
It can be cut. You can start recording when it's boot looping. Just show your app drawer or list of apps in your settings afterwards.
Hah I can't believe some people in this thread thought you would have to show the whole duration. It can be cut. It can be fast forwarded.
Just needs to show the boot loop or random reboot happening AND show the list of apps afterwards, not before.
Click to expand...
Click to collapse
Yeah, I'll get right on that for you! It serves NO purpose to do this! Go away....
Why do you think people need to (or would even want to) try and prove this to you????
I KNOW there is a problem, I don't need to prove it to you! You would never accept that as real "proof" anyway, and you know it!
Sent from my Transformer TF101 using Tapatalk
jtrosky said:
Yeah, I'll get right on that for you! It serves NO purpose to do this! Go away....
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
lol. why are you so defensive?
DON'T DO IT IF YOU DON'T WANT TO. I was just asking, and not even you specifically.
horndroid said:
lol. why are you so defensive?
DON'T DO IT IF YOU DON'T WANT TO. I was just asking, and not even you specifically.
Click to expand...
Click to collapse
Because it's a waste of EVERYONES time, just like this thread.
Enough said. See ya...
Sent from my Transformer TF101 using Tapatalk
jtrosky said:
Because it's a waste of EVERYONES time, just like this thread.
Enough said. See ya...
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Again, you are being overly defensive for no reason.
There were similar videos for Prime. I just wanted to see one for TF101.
horndroid said:
Again, you are being overly defensive for no reason.
There were similar videos for Prime. I just wanted to see one for TF101.
Click to expand...
Click to collapse
In case you haven't read your own thread, you are the only one who thinks this is a good idea.
Look, as I remember, you said that you reboot your device at least once a day, so how do you even know if you have the problem or not?
My problem is this - you come on here acting like everyone that has the problem, has the problem because they did something wrong. Since you don't believe you have the problem, you assume that everyone who does have the problem is doing something wrong and that full wipe will fix it when some of us have already done that many time to no avail.
Instead of leaving us be to resolve our issues, you ask folks to waste time making videos to prove it to you!
Why are YOU being so defensive? You are the one asking for proof - not me!!
I keep telling myself I'll ignore you, but your reasons are so lame, that I can't help myself!!!
jtrosky said:
In case you haven't read your own thread, you are the only one who thinks this is a good idea.
Look, as I remember, you said that you reboot your device at least once a day, so how do you even know if you have the problem or not?
Click to expand...
Click to collapse
lol I know I am not getting random reboots because I constantly monitor my tablet for random reboots. I run an app that displays uptime on my home screen and I never empty out my recent apps list.
jtrosky said:
My problem is this - you come on here acting like everyone that has the problem, has the problem because they did something wrong. Since you don't believe you have the problem, you assume that everyone who does have the problem is doing something wrong and that full wipe will fix it when some of us have already done that many time to no avail.
Click to expand...
Click to collapse
Nope. I've even said that factory reset doesn't work for everyone. I came to that conclusion long time ago. People are experiencing the problems in different ways. Factory reset is just one of the solutions that have been proven to work for some people. Wakelock is another solution but that also doesn't work for everyone. So what's wrong with suggesting what have been proven to work for the large majority of people who fixed their issues? Sounds like it's the logical step in troubleshooting. People can't know whether it will help them or not before actually trying it.
I suggest it depending on what the person has said in his post. If he said he had tons of apps and did OTA update without wiping, I suggest it because I genuinely believe it will at least alleviate the problems. Pretty sure any reasonable person would think the same.
I do have a hard time believing ridiculous claims though, such as the one by Knoxploration, who says both his and his wife's TFs have random reboots and boot loops even after factory reset, running on stock with no apps. What an amazing coincidence that they both have the most extreme version of the problem.
I think there is already enough attention on the issue from Asus.
There is even a thread created by Asus employee to sort this issue. Its sticky on this very forum.
linuques said:
I think there is already enough attention on the issue from Asus.
There is even a thread created by Asus employee to sort this issue. Its sticky on this very forum.
Click to expand...
Click to collapse
I am aware. But a lot of people have been complaining that Asus isn't giving enough feedback.
horndroid said:
I am aware. But a lot of people have been complaining that Asus isn't giving enough feedback.
Click to expand...
Click to collapse
Luckily I dont have the issue, so I haven't been following the thread.
You can try the new kernel for the tf101 3g (version 9.2.2.3), is said to adress the issue. You can flash guevor kernel test 7 on non-3g TFs.
Just accept the fact that we are quite many who has an RR/SoD'ing TF101 and then accept the fact that we are quite upset with Asus?
Oh crap... I just fed a troll...
Thiesen said:
accept the fact that we are quite upset with Asus?.
Click to expand...
Click to collapse
Im not
Compared to Ainol, Asus are gods
... But the RR/SOD is quite annoying nevertheless.
Video of reboot to freeze
Here is a video of a reboot to a freeze I cobbled together, on an B70 with ICS (4.0.3) :
http://www.youtube.com/watch?v=8LZ5Q-kUSq4&feature=youtu.be
[replaced original video(s) with a more stable video of reboot to freeze].
About the RR and SOD problems, a lot of people solved their issues using the lastest kernel from Asus (9.2.2.3). It was actually release for TF101G.
Its not official yet on TF101, but there is a build from guevor here (test8) http://forum.xda-developers.com/showthread.php?t=1565519
Reportedly is working very good.
They see me trollin'.
Better than a video, would be to show the logs. And there are logcats of the reboot event, there are a team of devs that had those logs.
Hi all, so I went to flash Franco kernel on my n4, and I clicked on nexus 4 kernels, but somehow ended up going to the page with the gnex kernels, and flashed that instead. I didn't realize that till after I bricked my phone when I went on my friends phone and then checked the page. Idk how that happened that I was directed to the gnex kernel page, but I was. So anyway, I hard bricked my phone and wondering if There's any way to save it? It won't even boot up, or go into bootloader mode, or anything. please help?? Thanks!
Try holding volume down and then plugin your usb cable in your pc. Worked for me and mine is still hardbricked! Maybe you can get into fastboot and restore
lowtje said:
Try holding volume down and then plugin your usb cable in your pc. Worked for me and mine is still hardbricked! Maybe you can get into fastboot and restore
Click to expand...
Click to collapse
it doesnt even turn on, and i have a mac :/ i have no way to get into fastboot mode
It doesn't turn on? What did you mean? Do you see the Google logo when you press the power button? Try holding volume keys and power to get to fast boot.
Try downloading the drivers from the pdanets software. I think they have a Mac version which will enable you to use fast boot on Mac. Go to Google factory images page and download the nexus 4 image. Unzip it and use flash the boot image by using the fastboot command : fastboot flash boot boot.IMG
Sent from my Nexus 4 using xda app-developers app
Ieatnoobs said:
It doesn't turn on? What did you mean? Do you see the Google logo when you press the power button? Try holding volume keys and power to get to fast boot.
Try downloading the drivers from the pdanets software. I think they have a Mac version which will enable you to use fast boot on Mac. Go to Google factory images page and download the nexus 4 image. Unzip it and use flash the boot image by using the fastboot command : fastboot flash boot boot.IMG
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
like i mean that no matter how long i hold the power button, the phone doesnt turn on. its just a black screen. no logo, no boot anumation, nothing. i cant even boot into fastboot or recovery, so i cant do any fastboot commands
Maybe the battery is dead? Try charging it?
Sent from my Nexus 4 using xda app-developers app
Melad360 said:
like i mean that no matter how long i hold the power button, the phone doesnt turn on. its just a black screen. no logo, no boot anumation, nothing. i cant even boot into fastboot or recovery, so i cant do any fastboot commands
Click to expand...
Click to collapse
Leave it in the charger overnight. And try to use an high amp charger like the ipad one
Sent from my iPad using Tapatalk HD
lowtje said:
Leave it in the charger overnight. And try to use an high amp charger like the ipad one
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
it was at 95% when i bricked it though, theres no way the battery is dead :/
so i called google about replacing it, they said that they will email the original buyer (my dad) to authorize an exchange, so i might be able to get a new n4
Melad360 said:
so i called google about replacing it, they said that they will email the original buyer (my dad) to authorize an exchange, so i might be able to get a new n4
Click to expand...
Click to collapse
Not to sound like an asshole or anything but to be completely honest, I kinda hope Google doesn't replace that phone of your for free. You messed it up by not double checking everything twice before clicking that confirm button when you went to flash a new kernel. You knew that if you messed up your phone is dead. But now Google has to shell out a new phone because YOU messed up, not Google.
Gonna ruin it for people that actually did get a defected device...
Melad360 said:
so i called google about replacing it, they said that they will email the original buyer (my dad) to authorize an exchange, so i might be able to get a new n4
Click to expand...
Click to collapse
Not cool. You need to fix this yourself.
What were you thinking flashing stuff to your phone but not having the ability to use fastboot and other dev tools? If you're going to intentionally gut out the functionality of your phone, have the tools and willingness to deal with problems! This isn't Google's fault, don't leave them with the bill!
Sent from my Nexus 4
waffleman911 said:
Not to sound like an asshole or anything but to be completely honest, I kinda hope Google doesn't replace that phone of your for free. You messed it up by not double checking everything twice before clicking that confirm button when you went to flash a new kernel. You knew that if you messed up your phone is dead. But now Google has to shell out a new phone because YOU messed up, not Google.
Gonna ruin it for people that actually did get a defected device...
Click to expand...
Click to collapse
how can i double check something that doesnt have a device model on it? it simply says "Franco.kernel nightly r-number.zip", i dont know how i managed to end up on the gnex kernel list, when i specifically clicked on nexus 4 kernels. that was beyond my control, its not like i made a stupid mistake on purpose. i double checked everything, making sure i was on the right xda page, and i downloaded a zip file not an img file, etc, i did everything i could do, yet little things slip
Melad360 said:
how can i double check something that doesnt have a device model on it? it simply says "Franco.kernel nightly r-number.zip", i dont know how i managed to end up on the gnex kernel list, when i specifically clicked on nexus 4 kernels. that was beyond my control, its not like i made a stupid mistake on purpose. i double checked everything, making sure i was on the right xda page, and i downloaded a zip file not an img file, etc, i did everything i could do, yet little things slip
Click to expand...
Click to collapse
Post the url you click that forwarded you to the gnex page. I'd be willing to bet that it says up top in orange, something along the line of "gnex>android development>gnex kernels"
Did you read the comments of that thread?
When you were in TWRP/CWM, the name of the file didn't hint at either gnex or nexus 4? It should have, if I'm not mistaken. There are always few ways to double check the file you downloaded.
Melad360 said:
how can i double check something that doesnt have a device model on it? it simply says "Franco.kernel nightly r-number.zip", i dont know how i managed to end up on the gnex kernel list, when i specifically clicked on nexus 4 kernels. that was beyond my control, its not like i made a stupid mistake on purpose. i double checked everything, making sure i was on the right xda page, and i downloaded a zip file not an img file, etc, i did everything i could do, yet little things slip
Click to expand...
Click to collapse
But this is Google's fault?
Sent from my iPad 4
k everyone calm down. I am sure all of us made that stupid mistake someday. None of us are perfect humans. We learn from mistakes. At least thats what we are suppose to do. Anyway, glad it worked out for OP.
So...it won't turn on at all? Did you someone flash a bootloader or something?
Maybe JTAG it. Hire somebody who knows how to use that technology and you could get it restored.
Melad360 said:
how can i double check something that doesnt have a device model on it? it simply says "Franco.kernel nightly r-number.zip", i dont know how i managed to end up on the gnex kernel list, when i specifically clicked on nexus 4 kernels. that was beyond my control, its not like i made a stupid mistake on purpose. i double checked everything, making sure i was on the right xda page, and i downloaded a zip file not an img file, etc, i did everything i could do, yet little things slip
Click to expand...
Click to collapse
Obviously this isn't the case because the links work just fine..
Sent from my Nexus 4 using Tapatalk 2
I`m calling google to tell them not to give a free phone to that guy! He should be charged every penny for the new phone!
Not to troll the OP, but man I'm seeing these threads all the time now and it's seriously annoying and down right fraudulent!
If you buy a new car, drive it off the lot and wreck it five miles down the road while breaking every traffic law known to man, you can not bring the heap of metal and plastic back to the dealership and demand another.
YOU voided your warranty! YOU flashed third party firmware! YOU improperly flashed third party firmware and bricked your device as a result. Do not blame Google, Franco, or anyone else for YOUR mistake!
Google has no responsibility for your device now, they guarantee that it works from the factory in the condition they sold it in. Once you click 'Yes' in the bootloader to unlock your device, you're on your own should you screw up... That's what that message is telling you!
I, for one, enjoy getting a nice phone at a great price. People like you are the reason carriers and OEMs charge $600+ now! Take responsibility for breaking it... Perhaps next time you should read, then when you think you know enough, read some more!
Spoiled children...
Sent from my Nexus 4 using xda premium
Ok, I've looked around for the answer and from what I've ready, I don't think I can do this but I want to make sure I properly understand what I have read.
My phone came stock with AT&T's MF3, i was able to successfully root and debloat the phone without issues. I was very careful the entire process and everything works perfectly. But then what did I do? I modded the build.prop (it was late and I was tired... I shouldn't have done it) file without thinking "I don't have a recovery method if this fails"... I KNEW there was no MF3 firmware available for recovery in Kies, and I knew no one has found an workable solution in Odin... But these didn't cross my mind that night. So, when I rebooted my phone, it would go past the samsung boot logo but never show AT&T's logo. The screen goes black after the Samsung logo, the remains black. After about 10 - 20 seconds the LED at the top left of the phone will turn on blue and throb. If I plug my phone into a USB port, it will try to install drivers as "MTP USB Device" but fail. The longer I leave the phone the warmer it gets regardless of whether or not it's plugged in.
I can boot into Download Mode and Stock Recovery
I've tested the drivers with my wife's phone and everything works as expected
I can boot into Stock Recovery and sideload files (I tried to flash an OTA file another user hosted here, it was sent via ADB sideload but it failed due to my debloating the /system/apps folder)
I've tried using stock recovery to flash a zip file to replace build.prop, but failed (not signed by samsung)
I've successfully flashed the "MF3_BTL_FIX" file another user created to kick a person out of the yellow triangle, when Kies fails.
I've tried best buy, but the samsung specialist will not even plug my phone into their computer
I have a backup build.prop, I just can't figure out how to get it on my phone without a custom recovery.
So, is there any way to replace the build.prop file with Odin/Heimdall or flashing or sideloading something from stock recovery?
My wife has the same phone, so I can also get files from her phone if I need to.
Any help or advice (even if it's "you have to wait for MF3 to be released in kies") would be greatly appreciated.
I'd find another bestbuy and see if you have better luck there.
jd1639 said:
I'd find another bestbuy and see if you have better luck there.
Click to expand...
Click to collapse
I think this is my best option too, but the next closest best buy is 1.5 hours from this one.... Getting time to go there will be the hardest part for me... that's what I get for living in the middle of nowhere...
dustyhughes said:
I think this is my best option too, but the next closest best buy is 1.5 hours from this one.... Getting time to go there will be the hardest part for me... that's what I get for living in the middle of nowhere...
Click to expand...
Click to collapse
Road trip!
jd1639 said:
Road trip!
Click to expand...
Click to collapse
HAHAHA! seriously! "Come on Kids, we're going on a field trip for science... COMPUTER science!"
But really, I may be heading out there Friday. They actually have 2 full stores there and 2 "mobile" stores.... I guess I'll see if I can get someone in one of those places to help.
Did you try a factory reset in Stock recovery?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
Did you try a factory reset in Stock recovery?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately, yes... It formats /data and /cache... it doesn't touch /system at all (from what I could tell), so the build.prop isn't restored to factory.
What stinks is, I believe ALL i have to do is replace that ONE file! Granted it's a major file... but still, ONE file, keeping me from booting to the OS. I've even been tempted to send it to one of the guys that does the jtag repairs, but to be honest I don't know enough about what they do to know if it would even help or if I could trust them (I assume I could from what little I've read)...
I may just have to go best buy hunting.
dustyhughes said:
Unfortunately, yes... It formats /data and /cache... it doesn't touch /system at all (from what I could tell), so the build.prop isn't restored to factory.
What stinks is, I believe ALL i have to do is replace that ONE file! Granted it's a major file... but still, ONE file, keeping me from booting to the OS. I've even been tempted to send it to one of the guys that does the jtag repairs, but to be honest I don't know enough about what they do to know if it would even help or if I could trust them (I assume I could from what little I've read)...
I may just have to go best buy hunting.
Click to expand...
Click to collapse
I assume you're referring to mobiletechvideos.com and I didn't use them for jtag however I used them to fix a power button and they are awesome!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
HiTideBlastoise said:
I assume you're referring to mobiletechvideos.com and I didn't use them for jtag however I used them to fix a power button and they are awesome!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I know I've heard of mobiletechvideos before, and I know they would be trust worthy, I've heard GREAT things about them... The other place I saw unbricking phones I ran across on youtube, they have a link to an ebay store (if you search ebay for "Unbrick Service Hard Bricked Samsung Galaxy S4 i337" you'll find them). They are actually a whole lot cheaper than mobiletechvideos, which is one of the reasons I looked into them and also why I'm suspicious. Not to discredit them at all, because I personally don't know what kind of work they do.
I don't even know if Jtag will allow them to fix my build.prop file. The ebay place says if the phone doesn't boot normally after doing a repair, they will restore the latest stock ROM and since i'm on MF3, well... They couldn't do much. It also makes me suspicious that in their ebay description it says:
------------------------------------------------------
By purchasing this auction you agree to the following.
1. Jtag service will avoid your warranty.
2. There is no guaranty 100% to fixed your phone, but we do our best.
3. If the phone can not fix, we will refund only $ 30.00, minus $5.80 for shipping cost.
4. If you claim for any problem after successful unbricked the phone, you need to send it back for inspection. Because we tested it before ship.
-------------------------------------------------------
I mean, some of the wording used makes me uncomfortable... I could just be paranoid, the address on the auction IS Carrollton, Texas after all
Just thought I'd update everyone... never found a fix myself, but I did drive to the next nearest best buy with my phone in the yellow triangle mode and the guy said he knew exactly what to do. He was very friendly, knowledgeable, and helpful... He even knew how to get the phone in download mode We talked a bit, he never asked about what I may have done to the phone, but during our conversation I had told him I had backed everything up and he kind of winked and said he would take care of me. It seemed like he knew what happened, but he didn't say anything, and the "head Samsung rep", his boss was right there talking with us too. He did a full restore, and I was up and running in 10 minutes. If you get a friendly and knowledgeable employee it's pretty painless.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
This is great to hear. Glad you got it fixed. That road trip was worth it
jd1639 said:
This is great to hear. Glad you got it fixed. That road trip was worth it
Click to expand...
Click to collapse
Thanks! I'm really glad to get it back. The road trip was well worth it. My wife and I decided to make a date out of it, we went to a nice restaurant while we were out without the kids, something they wouldn't have enjoyed and we wouldn't normally go to with them
Sent from my SAMSUNG-SGH-I337 using xda app-developers app