Database Users

[Q] Removing ripped off message from Vegacomb?

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.

Testing waters replace 8gb with 16gb switch screens

Ok so I am going through a little bit of a problem with my device it seems to be stuck on the google black screen of doom... Been searching and searching but I cant seem to find an answer or a solution as to how to get it to recognize on my pc or just boot up to the bootloader or recovery. I have been checking out a couple devices on ebay and was thinking if I would be able to switch out the screen on my nexus and would it be compatible with a 16gb if I chose to go that route or just get another 8gb cracked and switched them out. Does it sound doable? I am planning on taking my phone to a shop to repair the screen switch out the glass on my vivid. If they do a good job I would seriously consider it but as I said this is wishful thinking down the road. I am hoping I can solve this problem on my device I would hate to be the one to hardbrick his Nexus 7 on such a silly mishap.

anyone think this would work seriously looking into doing this if i can get a 16gb under 100. I am losing hope on getting my device to work.

clago87 said:
anyone think this would work seriously looking into doing this if i can get a 16gb under 100. I am losing hope on getting my device to work.
Click to expand...
Click to collapse
whats when you hold down both volume buttons when turning it on?

Have you tried plugging your nexus into a PC then going into bootloader?
Sent from my Nexus 7 using xda app-developers app

Yea i have tried everything the only thing my pc recognizes is apx on the device. Cant get into the bootloader for the life of me. There is a thread i am hoping can break through on restoring the bootloader but it's on linux.
Sent from my HTC PH39100 using xda premium

[Q] how to save hard bricked nexus 4??

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

[Q] Can I replace build.prop with Stock Recovery or Odin

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

Anyone Figured Out Reviving Nexus 7 Without Blob Files?

Has anyone figured out reviving Nexus 7 without Blob files?

NexusAd said:
Has anyone figured out reviving Nexus 7 without Blob files?
Click to expand...
Click to collapse
I'm not even certain it can be done with them!
Hi, NexusAd...
I generated my own Nexus 7 'blobs' some years ago, and fortunately, I've never had cause to use them. My Nexus 7's bootloader is still good, and the tablet still works, albeit very, very slowly (I blame Lollipop for that!) and which is why I rarely use it these days.
It has always seemed to me, that the 'flatline' procedure, for generating such 'blobs' and then using them to restore a Nexus 7's bootloader, was somewhat experimental and not guaranteed of success. I've never read of any successful attempts here on XDA or anywhere else for that matter, where somebody has actually used 'flatline blobs' to that effect.
----------------------------------------
So anyway... as I understand it, there's really only one way of reviving a hardbricked Nexus 7, and that's via a motherboard replacement.
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs

We should all get together and sue Asus/Google for screwing our 7 year old device

NexusAd said:
We should all get together and sue Asus/Google for screwing our 7 year old device
Click to expand...
Click to collapse
there is a tutorial now