I have a hardware locked Vibrant, but I don't want to bother to replace it..
If I use Odin to flash a new rom, will it fix this issue? someone did that on I9000 and fix the problem.
If I used Odin and make my phone to be bricked, may I still can ask a replacement?
Thanks!
I've Seen Some People Saying Its A Software Issue, But It's Not.
I've Flashed A Different ROM Through ODIN And It Still Didn't Work
Unless the rom contains a new boot loader. It would not fiz the problem It would be close to flashing a new bios on the computer. The boot loader can ignore hardware keys and that is what is happening now. So it is software just not the operating system rom.
Sent from my rooted Vibrant using XDA App
I have noticed that when I connect a full on charger (as opposed to computer USB) to my phone, I cannot get into download or recovery mode. I wonder if this is similar to the "hardware" locked phones? Also this leads me to ask the question... Are we having a charger detection problem on these "locked" phones?
Related
i told tmobile that i cant use the hardware keys to get in master reset menu. they sending me a 3rd one. but i had to pay for the shipping. i think its gona be the same model and i wont be able to get in master reset menu again..
what shall i do? if that's the case
All newer revisions are hardware lock.
No offense but how many people just read here that hardware locked vibrant's are bad and ask to get new one? Seriously? I just helped a buddy of mine with a hardware locked vibrant yesterday and it took just one extra step to mod his just like mine (which is normal). Just rooted via windows, flashed clockwork and you can boot into recovery from there, flash any roms you want. Now, granted, you have to be slightly more careful but if you make a mistake just get into download mode and flash with odin. Seriously, the hardware buttons just mean you can get into recovery if you get stuck at the vibrant screen, but if you really brick your phone, regardless of hardware lock, both types of phone are at the same level.
Seriously, 3 returns just to get this? By now you could have had your FIRST one modded to hell and back...
You may get lucky and get a Vibrant with the hardware keys working. I just got my vibrant replaced last week and the keys on the new one are operational. Even came with another external sd card.
madgravity34 said:
No offense but how many people just read here that hardware locked vibrant's are bad and ask to get new one? Seriously? I just helped a buddy of mine with a hardware locked vibrant yesterday and it took just one extra step to mod his just like mine (which is normal). Just rooted via windows, flashed clockwork and you can boot into recovery from there, flash any roms you want. Now, granted, you have to be slightly more careful but if you make a mistake just get into download mode and flash with odin. Seriously, the hardware buttons just mean you can get into recovery if you get stuck at the vibrant screen, but if you really brick your phone, regardless of hardware lock, both types of phone are at the same level.
Seriously, 3 returns just to get this? By now you could have had your FIRST one modded to hell and back...
Click to expand...
Click to collapse
There is no way to get in
Dl mode on the locked vibrants so if u messup ur bricked forever,and older model of vibrant you cant brick because you can always get in to download mode and use odin to re flash
Sent from my SGH-T959 using XDA App
As a Galaxy S i9000 owner I am curious, has anyone yet got any idea how updates and general ROM flashing are to be done on the Nexus S? I understand OTA will be likely for the PDA code but how about the baseband? Do Google take care of the modem or do Samsung?
And since we use Odin to re-partition and re-flash the ROM in the SGS I wonder how this is performed on the Nexus line?
I am very happy to see Kies left behind but I also see no software for the Nexus S at all. Even my Motorola Milestone had some sort of desktop connectivity for when things went wonky..
Is there any reason we would not use rom manager to flash new roms since that is how we have been flashing our cw recovery? Seems that would be the easiest solution just like on the n1
generalagony said:
Is there any reason we would not use rom manager to flash new roms since that is how we have been flashing our cw recovery? Seems that would be the easiest solution just like on the n1
Click to expand...
Click to collapse
My Android life has been Milestone > SGS, so I am not familiar with that one, we use Odin over USB on the Galaxy line.
Ok, that is interesting to know. Does that also include the modem code though?
If by modem code you are referring to the radio image; yes. Most all files can be flashed via clockwork recovery. It it all i ever used on n1 to flash roms, kernels, and radio files.
generalagony said:
If by modem code you are referring to the radio image; yes. Most all files can be flashed via clockwork recovery. It it all i ever used on n1 to flash roms, kernels, and radio files.
Click to expand...
Click to collapse
Superb, I will have to have a look into CWR then. Had little cause to so far.
If you are rooted already the easiest thing to do I download rom manager from the market and flash cwr through there. It has been updated to the newest version through rom manager and is completely painless
Fastboot should also work depending on how the file you want to flash is released.
fastboot recovery new_recovery.img
fastboot system custom_rom.img
fastboot modem new_modem.img
etc, etc, etc...
Think of fastboot as sort of Google's version of Heimdall (3rd party Odin replacement)
Thanks all for the input, I need to get the phone next. UK delays and such.
Samsung really went somewhere annoying by forcing a USB update system. Nexus S sounds like a happier time.
nailerr said:
Thanks all for the input, I need to get the phone next. UK delays and such.
Samsung really went somewhere annoying by forcing a USB update system. Nexus S sounds like a happier time.
Click to expand...
Click to collapse
This seems like a world of difference from HTC RUU's
JD
Hi,
Long story short, I've lost use of the USB port on my N4 for anything other than charging. No combination of computer/port/cable will recognise it, and I've tried all sorts of ways to get it to work again. (It's the same issue this guy had http://forum.xda-developers.com/showthread.php?t=2040083)
I've RMA'd it, and got a new unit - other problems too, relating to battery overheating and only lasting ~4 hours, so there's definitely a hardware fault.
Before sending it back, I'd like to unroot and relock it, if this is possible to do without using fastboot.
There are some threads for other devices which can use a flashable zip to flash everything back to stock (including the recovery) and use this app http://forum.xda-developers.com/showthread.php?t=1731993 to relock the bootloader from within Android, but I obviously need to find the files for a N4 since the ones in the other threads are device-specific.
Can anyone help me with this, or am I being too worried that they will deny me a warranty repair since the phone is unlocked/rooted - do they actually care in practice?
Thanks for any help.
So, I searched for it.
And the third result was what you are looking for.
Right there in the second post.
Just an idea:
- flash stock rooted ROM
- flash stock recovery
- lock the bootloader with an app (i have see it somewhere)
- unroot it with an app
But you will need battery for these operation, if its work indeed...
And normally, even if your software is modified, they have too take it for hardware problems
Tapalked with a Nexusâ´
Well, my friend asked to me about this.
He was flashing this G4 plus, the process was done with success but it don't reboot the device, it just shutdown itself and the LED light turns on. after a check on the board it wasn't damaged or something like.
OS version: 7.0
What stock ROM were they flashing, what commands to flash? Does the computer still recognise the device when connected?
Are you able to boot to the bootloader?
echo92 said:
What stock ROM were they flashing, what commands to flash? Does the computer still recognise the device when connected?
Are you able to boot to the bootloader?
Click to expand...
Click to collapse
What stock ROM were they flashing.
-it was the 6.0.1 as he said that it wasn't modified before.
what commands to flash?
-Well he used some kind of program that does it automatically maybe? i don't think that he has some kind of knowledge about commands lines, i am not an exception.
Does the computer still recognise the device when connected?
-Yes, he tried many times but the same kept happening.
Are you able to boot to the bootloader?
-I think yes, maybe, i'll get the phone in my hands tomorrow so i'll made a video to try to make it more easier for all us.
Weserx said:
What stock ROM were they flashing.
-it was the 6.0.1 as he said that it wasn't modified before.
what commands to flash?
-Well he used some kind of program that does it automatically maybe? i don't think that he has some kind of knowledge about commands lines, i am not an exception.
Does the computer still recognise the device when connected?
-Yes, he tried many times but the same kept happening.
Are you able to boot to the bootloader?
-I think yes, maybe, i'll get the phone in my hands tomorrow so i'll made a video to try to make it more easier for all us.
Click to expand...
Click to collapse
The 6.0.1 stock ROM is really old and generally only advisable to flash if you know what you're doing and that you're flashing the correct build of the firmware for your device/region. Do you know if your friend was flashing the firmware over a newer firmware build, and what build version was it? What program did they use (e.g. RSDlite)?
What does the device present as in device manager? Is it coming up as Qualcomm HS-USB 9008 or similar?
My phone suddenly had a momentary display malfunction (some of the text on the screen just turned into garbled pixels) and then entered into a boot loop. I didn't make any changes or updates to the phone recently. It no longer boots normally - just the Samsung logo and some of the Verizon logo animation, then it reboots and starts again. How do I pull my user data off (photos mainly) before trying a factory reset? The phone is totally stock. I haven't unlocked it, rooted it, or installed any custom recovery/ROM/bootloader/whatever. (I sound like I don't know what I'm talking about because I don't, haha.) The touchscreen is fully functional. I'm sure this has been covered here before, but I haven't found anything that totally explains how to do this in this particular situation, so I'd really appreciate any help anyone can provide.
The only time I can get the phone to show up under adb devices is when I boot it in recovery mode and select "Apply update from ADB". But it says "sideload" next to it in adb devices, and the push, pull, and shell commands return errors. I've read that this is normal. Wiping the cache partition didn't solve the boot loop problem.
If it helps, this is what the top of the recovery screen displays:
Android Recovery
Verizon/heroqltevzw/heroqltevzw
8.0.0/R16NW/G930VVRSBCTC1
user/release-keys
I'm no Android expert, clearly. I've heard it mentioned that I need to install a custom recovery in order for this to be possible. To be clear, I want to make sure I don't erase the user data before I have a chance to pull it off the phone. These are the questions that I still have after reading information elsewhere (some of which I'm just asking out of an abundance of caution):
Is it correct that I need to install a custom recovery before I can pull this data off the phone?
Do I need to have it unlocked/rooted/anything else in order to be able to install a custom recovery? Or is there anything else I should do before installing it?
Which custom recovery should I install?
Do I need a custom ROM, if that's a different thing?
Do I need a custom...bootloader, if that's also a different thing?
Should I use Odin or Samsung Smart Switch to install the custom recovery?
(Extra credit: Does it sound from my description of how the boot loop started that this phone has hardware problems and should be replaced ASAP?)
Thank you so much for any help you can provide! Any extra information beyond my questions will be very much appreciated, too, of course. You guys never cease to impress.
You have a B version bootloader like me, and so far no root/custom recovery has been made for our versions of bootloaders. If I were you, I would check if you had maybe like a previous backup, and if Google made an automatic backup of your apps and photos? If you didn't use a 3rd party backup, and if you don't want to wait, you might lose some files. I also think you might be able to flash a certain part of stock firmware to get your phone to boot again, but I'm not sure
Also, if you don't care about files that can't be get through automatic backups, might as well flash a whole stock firmware, which as far as I know, may be the easiest way to get out of one.
Please correct me if I'm wrong
Also to answer your bullet points:
1. I'm not sure if you need a custom recovery, but from my experience from a Verizon s5, that's probably a yes.
2. Since this is Verizon, you would need to unlock your bootloader in order to install a custom recovery, which in where I posted my first reply, the B version of the bootloader is still locked down without any known way to unlock it. You and me are stuck with this, as I also have the B version.
3. If the heavens line up and you somehow unlock the bootloader, try to flash a recovery Called TWRP under the name "Herolqte" (that's what I think). If that doesn't work, try to find one that works with the phone on XDA. If neither of those show up try to use another custom recovery like CWM.
4. If your trying to recover data on a phone, flashing a custom ROM is probably the last thing you want to do. A custom ROM is a modified version of Android, which may mean you'll have to format your device anyways so this is probably not what you want (even though it would be nice :[ )
5. As in post 2, all you would need to get a custom recovery is to unlock the bootloader. I'm not even sure if you CAN get a custom bootloader, as Odin won't even let me flash a stock bootloader to my phone that is the same exact Version >:[
6. You would need to use Odin if you were trying to flash something to your phone. Smart switch I think WOULD let you back up your device, but you would need to be on the home screen on your phone, which in turn, would probably need you to be out of that bootloop.
7. This is probably a software issue. If you don't care to much about the idea, try flashing some parts of a stock firmware. I was personally in a boot loop 2 days ago, but I flash a stock modem file (I think that was the second file slot from the bottom in Oden) and that got me out, but for some reason wiped my phone clean, and I'm not sure why.
Anyways. Goodluck in recovering your data. Also I'm not sure if a factory reset would even fix a boot loop
yaas
yaas