Hellow guys
Here's my background, I rooted my Tab by using z4root which works fine. I flash zImage using Odin with 20% battery (I think this cause the problem D:
After it says "PASS" I immediately pull it from the pc and boot em up. In the first "Galaxy Tab" logo it has Funky rainbow lines,and on the second logo which is "Samsung'' it stops there and vibrates then it repeats all over again. When I try to boot it on recovery mode rainbow lines appear then go back to First logo screen. Download mode works fine but Odin wont recognize it .
After one week of searching on the internet, I cant find my situation. So, I was thinking to post it here on forums. Thanks in advance!
Weird. I recall reported funky rainbow lines when people who have GB bootloader, which doesn't need to be patched, but people go ahead and patch them.
But you flash zImage, not bootloader.
But since it appears in place of the logo, I would still say your bootloader is the one damaged.
Sent from my GT-P1000 using xda app-developers app
priyana said:
Weird. I recall reported funky rainbow lines when people who have GB bootloader, which doesn't need to be patched, but people go ahead and patch them.
But you flash zImage, not bootloader.
But since it appears in place of the logo, I would still say your bootloader is the one damaged.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Umm, Yea I saw that in forums too. That's why I couldn't find my exact situation, I don't know what exactly I would do
Btw I flash it with my galaxy tab in 10-20% battery,Did it cost the problem? I also immediately pulled it from the usb cable even if not boot up completely, but the odin says PASS. What do you think?
Please give me exact detail what would I do. I appreciate your fast response,Thank you!
I assume you were on froyo?
After z4root, you should immediately check if you have a protected boot loader. And patch it if so.
Now in this state, it is unsure if you have a protected bootloader.
What were you trying to achieve by flashing a zImage?
Actually I can't think of why except to root, but you have already done that?
Anyway, best you can do is charge fully, go to download mode and flash a stock rom.
If on the off chance your bootloader is not protected, you can use overcome method which can be found at my signature.
Sent from my GT-N7100 using xda app-developers app
priyana said:
I assume you were on froyo?
After z4root, you should immediately check if you have a protected boot loader. And patch it if so.
Now in this state, it is unsure if you have a protected bootloader.
What were you trying to achieve by flashing a zImage?
Actually I can't think of why except to root, but you have already done that?
Anyway, best you can do is charge fully, go to download mode and flash a stock rom.
If on the off chance your bootloader is not protected, you can use overcome method which can be found at my signature.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Yes Im on froyo 2.2 (I think)
Btw, I already charge the tab and go to download mode. The odin couldn't detect my device
I always saw you saying to use overcome method, the problem is I don't know how. I only saw some download links there. I don't know what exactly to do and to download.
Do you have a guide which I could follow?
I hope my tab will fix soon. Thanks!
Well. The link is the forum thread.
The thread has all the files including PDF guide.
But all useless without Odin detecting.
Sent from my GT-P1000 using xda app-developers app
priyana said:
Well. The link is the forum thread.
The thread has all the files including PDF guide.
But all useless without Odin detecting.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
What do you mean? Is there no chance of getting it fix?
Do I need to fully charge my device? I charge it maybe only 80-90% battery.
Do I need to wait 20 minutes till Odin will detect it? Please answer :crying:
Btw How do I know if my boot loader is protected or not?
Might be a solution
Karl Legson said:
What do you mean? Is there no chance of getting it fix?
Do I need to fully charge my device? I charge it maybe only 80-90% battery.
Do I need to wait 20 minutes till Odin will detect it? Please answer :crying:
Btw How do I know if my boot loader is protected or not?
Click to expand...
Click to collapse
Hey connect your tab for about 10 minutes or more 25 minutes max it will detect and then load odin with the stock rom files and flash! after it says pass your tab is ready. Make sure your tab has 70- 100% charge :good::good:
please help me, even i tried to update from froyo using odin and now i see rainbow lines.. when i start downloading mode, odin recognizes the tab, what to do?
rainbow lines? I thought that happens to people who upgrade to GB, then tried to patch the bootloader (unnecessarily)?
Is that what you did?
Related
So i tried to root my phone using one of the tutorials and ended up with a padlock screen on my phone. after researching i ALOT i decided on hard reseting my phone from the recovery menu. but all i see now is the google logo i believe i have deleted the 2.3.4 while reseting. can someone guide me from here. i am a n00b and i have had this phone for just 2 days. thanks in advance
anyone who can help?
youngballer said:
anyone who can help?
Click to expand...
Click to collapse
Please be more specific.
What tutorial did you use?
Did you download clockwork recovery?
Do you have the superuser zip?
If you can enable fast boot and fastboot flash recovery you should be able to mount your usb storage in CWM and then install a ROM and the su zip.
stuck on the nexus s boot screen
Babydoll25 said:
Please be more specific.
What tutorial did you use?
Did you download clockwork recovery?
Do you have the superuser zip?
If you can enable fast boot and fastboot flash recovery you should be able to mount your usb storage in CWM and then install a ROM and the su zip.
Click to expand...
Click to collapse
i used the one mentioned in addictive tips website (http://www.addictivetips.com/mobile/how-to-root-nexus-s-with-a-single-click-using-superboot/). i basically followed what these guys had mentioned.
since this failed i read that the other option is to go through fastboot > recovery > and clear everything but this did not change anything.
can someone give me a step by step guideline on how to continue. i dont mind going back to the stock 2.3.4 android. i just bought the phone yesterday
Which version do you have? The sprint or t mobile? Check if you can go into fast boot hold down volume up and then powerbutton. If not you may have to Odin it if not. That super one click looks old..
Sent from my Nexus S 4G using XDA App
chewbz said:
Which version do you have? The sprint or t mobile? Check if you can go into fast boot hold down volume up and then powerbutton. If not you may have to Odin it if not. That super one click looks old..
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I am in Canada but the model is 19020 A. I can get to the fastboot mode but don't know what to do after that.
I have the 4g so I don't want to give you the wrong information and never encountered this situation so sorry dude. Hopefully a more experanced user can help you out.
Sent from my Nexus S 4G using XDA App
Btw if all fails you can Odin it
Sent from my Nexus S 4G using XDA App
its all good thanks for trying to help
If your ROM flashed incorrectly, it would lead to your phone being in a state where it just shows a GOOGLE with a Padlock; kind of like turning on a computer without an operating system.
You would have to read the instructions on rooting your phone, which involves using fastboot and flash recovery from fastboot (All this is in the rooting guide). Simply reflash the recovery so you boot up back in recovery and try flash the rom again.
The same happened to me, I fixed it buy flashing a stock boot.img
Sent from my Nexus S using XDA App
thanks for the replies. how do i flash from the fastboot mode? when i plug it in to my computer i cant see the drive but my computer can detect the nexus s is plugged in
Set up adb first, they have the guides in the dev section, I used wolverines guide, you'll have to look for the software img, I don't know where it is at for the GSM model. Good luck
Sent from my Nexus S 4G using XDA App
Sounds like you're rooted and have recovery installed, but your OS is hosed.
Flash a ROM.
thanks for the replies guys. i have the adb setup on my laptop. i took it to one of the stores and he said he cant reflash it for some reason. he said he needs to get some software off samsung and it will take him a day. my phone is brand new and i didnt wanna trust him. do u guys think i should use odin? one of my friend has a galaxy s and he said odin should work fine on my phone.
Can you get into the ClockworkMod recovery menu? Turn the phone completely off then hold VolUp and Power until you get into Recovery.
If you get there, you're golden. Just download a ROM (I recommend Deck's) and away you go.
i can get into recovery but it gives me option like wipe everything and i selected that. but when i reboot the phone the same locked screen pops up. anyone from toronto here who i can contact?
youngballer said:
i can get into recovery but it gives me option like wipe everything and i selected that. but when i reboot the phone the same locked screen pops up. anyone from toronto here who i can contact?
Click to expand...
Click to collapse
Basically with those wipe commands you make the Rom unuseable. You have to flash a new one or apply it via Odin. There are various guides on this forum section. Odin requires less technical knowledge but is a bit more risky then flashing via recovery. Odin and the Roms for that method can be obtained from samfirmware.com. Zipped roms can be found in the development section here.
Sent from my Nexus S
I have a client's Atnt galaxy s4 that will not boot up normally and will not boot into recovery also.
when i try to boot into recovery i get the blue lettering in the top left and it just sits there i have let it sit for sometime like that with no change.
this is not my first go around with flashing android devices so please even give me Dev only options if that is what you think will fix it. i feel bad because he just bought this phone 2 weeks ago and cant use it. not sure what the other guy that tried to root it did and neither does he so i am shooting in the dark so any help would be great.
I have tried flashing the stock Odin package with no luck.
Also tried Kies Firmware upgrade with no luck
Most of the custom recovery for this phone from what i read are not flashed threw odin anymore, but if i am wrong please link me and i will give it a shot.
Dose anyone have any ideas someone told me to use the .PIT file and re-partition the device and reflash the stock odin package. but i have had no luck locating the .pit file for the I337 galaxy S4 could anyone grab it from there phone and upload it for me or any ideas on how i could possibly fix this issue.
Thanks in advance
Since you already tried ODIN, why don't you try KIES.
I tried that allrdy just forgot to add it to the list updated first post
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
C13v3r0n3 said:
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
ok i will have him give it a try
and yes it goes into downloading mode with no issues at all.
if the os isnt hosed just download goomanager and install the recovery then download a touchwiz rom that has an extended reboot menu, you can then just boot into recovery from the OS.
C13v3r0n3 said:
if the os isnt hosed just download goomanager and install the recovery then download a touchwiz rom that has an extended reboot menu, you can then just boot into recovery from the OS.
Click to expand...
Click to collapse
The OS wont boot that is why we are having such a issue cause we have to get into the recovery to fix the phone
thanks thou
If you can get into download mode and odin it should wipe everything, it should work. Maybr its hardware?
Sent from my GT-I9505 using xda app-developers app
In addition to letting go of the power button after the vibrate, here are a couple of other things that appear to have worked for other forum members. I didn't discover any of these fixes, I just did a lot of reading and saw where others have had similar problems and found ways to solve them. That is what makes the XDA community great:
Uppercuticus said:
I've had this happen to me several times while playing around with flashing. Basically (without fail in my experience), hold power+volume up+home as you'd normally do until you see the booting recovery message and let go. It will do one of two things - boot into recovery- or - restart and vibrate-. If it restarts and vibrates, immediately hold power+volume up+home until the booting recovery message pops up again and let go. It should then boot into recovery and you shouldn't have trouble in subsequent attempts.
It took me a while to figure this out and I actually thought I had permanently bricked my phone as the phone wouldn't boot and I couldn't get into recovery. Hope this helps.
Click to expand...
Click to collapse
RiNo808 said:
Those trying to boot into recovery mode, dl quick reboot from the play store. That's what I use and it works great.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Just flash a different custom recovery tar in odin. If ur using CWM, then flash TWRP, or vice versa.
C13v3r0n3 said:
If you can get into download mode and odin it should wipe everything, it should work. Maybr its hardware?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
After using ODIN, make sure to do a software (factory reset) to get rid of any data and settings that stayed behind. The firmware packages that we have for Odin, do not wipe everything on their own.
C13v3r0n3 said:
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Thanks - was having the same problem. At last somebody explains it properly. It worked.
(Why on earth is the script on the stock recovery screen so small. You need a microscope to read it. I am going to install CWM right away....)
Cheers LJ
S4 on veriozon only boots into download mood
Im having the same problem. I can ONLY get into download mood! Everytime I go and try to reboot all it does is vibrates. I was installing a rom before and it was installed fine then it says I lost my root and turned off. Now i can't turn my phone back on. I try to the NAND erase all but that does not work. Is my phone bricked? I have Verizon BTW. Could some body please help me ASAP!
Yankeetim92 said:
Im having the same problem. I can ONLY get into download mood! Everytime I go and try to reboot all it does is vibrates. I was installing a rom before and it was installed fine then it says I lost my root and turned off. Now i can't turn my phone back on. I try to the NAND erase all but that does not work. Is my phone bricked? I have Verizon BTW. Could some body please help me ASAP!
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=2316
any luck? im having the same problem after enabling the t-mobile aws bands on my i337. i could only get into odin mode, recovery boot sits there on end and i have no access to the phone settings. ive tried the odin with stock firmware but nothing.
xBeerdroiDx said:
http://forum.xda-developers.com/forumdisplay.php?f=2316
Click to expand...
Click to collapse
you are not playing fair sir...but a good one.
TheAxman said:
you are not playing fair sir...but a good one.
Click to expand...
Click to collapse
My unrooted s4 phone gets stuck with the blue colour legend Recovery booting with any mentioned method. I am unable to enter safe mode, any ideas? been surfing google for 6hrs with no proper answer. Thanks!!
C13v3r0n3 said:
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Thanx bro, This is solve my problem.
Having allmost the same problem with my S4...
http://forum.xda-developers.com/showthread.php?t=2498285
continuation of SGH_1337 will not boot into recovery
norml said:
Just flash a different custom recovery tar in odin. If ur using CWM, then flash TWRP, or vice versa.
Click to expand...
Click to collapse
here are all the details;
Rooted ATT Galaxy S4 MK2 with Busybox. all went well until I tried to flash and boot into recovery. Installed ClockworkMod Recovery, tried to reboot into recovery...permission error. Installed Team Win Recovery, same problem.
investigated... Superuser.apk for some reason is NOT present in app directory. hmm. checked for root, have root.
installed ClockworkMod Superuser from play store... asks to update superuser... fails with signature error.
There seems to be no way to flash this phone. I have the original backup I made with ClockworkMod but restore fails with signature error.
The phone works fine, has root but I am concerned I will not be able to update to 4.4 when it's available. I am also NOT able to flash any alternative ROM. frustrating.
I see there are relatives to this issue all over xda but as far as I can tell after a weekend of trying is there's NO WAY to boot into recovery with write permissions being allowed.
Rooting my Galaxy S4 has been one of the biggest pains in my rear ever and now I'm bricked and need a bit of help.
Normally, when I want to root a phone, I come here, to XDA, and follow a nice well written up-to-date thread on how to do it and it works. For the S4 however, I can't find any such threads that are not either old, out-of-date, or they use so many abbreviations for things I have no clue what they are talking about.
I started out with a totally stock Samsung Galaxy S4, was a VPUAMDL.
I used ODIN to push TWRP tarball. I then used TWRP to install the CWM SuperSU zip file.
I noticed when it started up that I had no root, I had the SuperSU program however, it nor another program I got on the marketplace, could confirm root.
Bit of looking I found this: galaxys4root (DOT) com/galaxy-s4-root/sprint-vpuamdl-firmware-update-root-fix/
(sorry, can't post full links yet)
Which basically informed me that VPUAMDL needs a new kernel to remove the SetUID restrictions.
I downloaded that file, and put it on my SD card. Booted into TWRP and installed. now my phone is bricked. gets to the "Samsung Galaxy S4" startup splash screen on black background
I am looking for a kernel that will work, either the stock kernel or not.
I am also looking for a good tut on rooting the S4, as all the tuts I have used have been utter wasted time.
I have ODIN, and can boot TWRP, ODIN mode, etc on my phone.
have no clue where to go from here and Im afraid to start trying to download random files and get everything mixed and confused.
Thanks for any help at all.
CF Auto Root
http://forum.xda-developers.com/showthread.php?t=2291827
Sent from my SPH-L720 using xda app-developers app
FanOfSkynyrd said:
CF Auto Root
http://forum.xda-developers.com/showthread.php?t=2291827
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I followed that page, pushed it, installed fine, 100% no errors.
still bricked at GS4 startup splashscreen.
It did finish successfully and I saw the screen with the red android.
It removed TWRP and replaced it with the stock recovery as it should have.
I am actually surprised myself that it is still bricked at the GS4 splash.
Odin stock everything. See if it boots. Then try to root after that.
Stealyourface said:
Odin stock everything. See if it boots. Then try to root after that.
Click to expand...
Click to collapse
I am failing to find stock everything to push.
I think I stated that, not sure... hmm
none the less. I do not have a stock kernel or recovery on hand. I can not find one either as there seem to be a plethora of kernels and threads and pages all for different files and downloads. Sifting through trying to find something is becoming harsh. Thus this thread.
You are not bricked if your phone can turn on and go to download mode or recovery.
Sent from my Sprint Galaxy S4 using Tapatalk 2
GiantJay said:
You are not bricked if your phone can turn on and go to download mode or recovery.
Sent from my Sprint Galaxy S4 using Tapatalk 2
Click to expand...
Click to collapse
Well then its whatever you want to call it when it wont boot the operating system and is totally un-usable as a phone or mobile device.
I would go HERE
That is the thread for stock MDL stuff.
Download and flash the kernel and full wipe rom for MDL.
Then upgrade to MF9.
+2 ^^^^ to what he said :edit:
Nice tut on rooting the s4 thanks to mudavo here http://forum.xda-developers.com/sho...to Full Stock [MF9] w/ Root & Custom Recovery
There is also a video tutorial stickied in android devolpment
Sent from myself SPH-L720 using xda app-developers
Thanks guys, going to try some of the stuff from there. Hope i get it going. Need mah phone back! lol
Wooo, those links where just what I needed. Thanks a lot.
Got my phone back on and now I have a stock file in case I muck things up again.
Just make a nand back up and restore when something bad happens ive mucked up alot and it has always saved me
Sent from my SPH-L720 using xda app-developers app while smoking
A little background info:
ATT GS4, rooted and on stock firmware
Had TWRP 2.6.0.0 on my phone
Tried to flash Illusion 7|15 or 7|16?
---------------------------------------------------
In the past, I've tried to flash illusion, with some success. I was able to get to the homescreen, but when I flashed my data backup. The phone wouldn't boot, so I reverted to stock. A few weeks later, I decide to take another spin at the rom and get it working. I wiped the data/cache/dalvik, and flashed the rom with gapps, rebooted the phone, and nothing happens. The phone keeps vibrating, but there is nothing happening past that.
After a significant amount of research, I've found a few tools/advice. I've downloaded ODIN and the (disgustingly large) tar file, but it doesn't have any use if the phone cannot be recognized by the computer since I am unable to enter download mode or recovery mode.
I found another tool that is supposed to "resurrect" the phone provided by legija. The only unfortunate part is there are no instructions provided, and once again, my computer isn't recognizing the phone as a device, as if it wasn't plugged in to the usb port at all. The application asks for a port number, but I have no clue what relevance a port number has, or at least that a usb port has a numerical value.
Anyway, is there anything left for me to do or is this a fancy new paperweight?
Excuse me for any poor grammar, I'm a little antsy about this
Gfrt94yn said:
A little background info:
ATT GS4, rooted and on stock firmware
Had TWRP 2.6.0.0 on my phone
Tried to flash Illusion 7|15 or 7|16?
---------------------------------------------------
In the past, I've tried to flash illusion, with some success. I was able to get to the homescreen, but when I flashed my data backup. The phone wouldn't boot, so I reverted to stock. A few weeks later, I decide to take another spin at the rom and get it working. I wiped the data/cache/dalvik, and flashed the rom with gapps, rebooted the phone, and nothing happens. The phone keeps vibrating, but there is nothing happening past that.
After a significant amount of research, I've found a few tools/advice. I've downloaded ODIN and the (disgustingly large) tar file, but it doesn't have any use if the phone cannot be recognized by the computer since I am unable to enter download mode or recovery mode.
I found another tool that is supposed to "resurrect" the phone provided by legija. The only unfortunate part is there are no instructions provided, and once again, my computer isn't recognizing the phone as a device, as if it wasn't plugged in to the usb port at all. The application asks for a port number, but I have no clue what relevance a port number has, or at least that a usb port has a numerical value.
Anyway, is there anything left for me to do or is this a fancy new paperweight?
Excuse me for any poor grammar, I'm a little antsy about this
Click to expand...
Click to collapse
Do you have AT&T insurance? Maybe the phone can have an accident? I would know of no other way to fix it if Odin isn't recognizing it. ):
Gfrt94yn said:
A little background info:
ATT GS4, rooted and on stock firmware
Had TWRP 2.6.0.0 on my phone
Tried to flash Illusion 7|15 or 7|16?
---------------------------------------------------
In the past, I've tried to flash illusion, with some success. I was able to get to the homescreen, but when I flashed my data backup. The phone wouldn't boot, so I reverted to stock. A few weeks later, I decide to take another spin at the rom and get it working. I wiped the data/cache/dalvik, and flashed the rom with gapps, rebooted the phone, and nothing happens. The phone keeps vibrating, but there is nothing happening past that.
After a significant amount of research, I've found a few tools/advice. I've downloaded ODIN and the (disgustingly large) tar file, but it doesn't have any use if the phone cannot be recognized by the computer since I am unable to enter download mode or recovery mode.
I found another tool that is supposed to "resurrect" the phone provided by legija. The only unfortunate part is there are no instructions provided, and once again, my computer isn't recognizing the phone as a device, as if it wasn't plugged in to the usb port at all. The application asks for a port number, but I have no clue what relevance a port number has, or at least that a usb port has a numerical value.
Anyway, is there anything left for me to do or is this a fancy new paperweight?
Excuse me for any poor grammar, I'm a little antsy about this
Click to expand...
Click to collapse
I've seen the repeated vibrating issue before from flashing the wrong file. Download mode was still accessible. Try again by hooking up the phone to the USB slot without the battery in it. Hold Vol Down + Home while inserting the battery. See if download mode will come up. If it does, Odin may not fix it, and you may end up using KIES, and that's if it does go into Download mode.
Phone is toast, fortunately the phone is still under warranty and they couldn't even get it to turn on so they replaced it
Still lost data, but it's not the end of the world. Thanks for the help though!
Gfrt94yn said:
Phone is toast, fortunately the phone is still under warranty and they couldn't even get it to turn on so they replaced it
Still lost data, but it's not the end of the world. Thanks for the help though!
Click to expand...
Click to collapse
Good deal man, glad you got a new one.
I have another question for somebody knowledgeable in rooting/rom flashing:
I think this was because the s4 bootloader is locked (through an update), would this cause the phone to hard brick? I've had nasty experiences in the past with locked bootloaders!
If it is locked, is there a way to unlock it? Or does it even need to be unlocked to flash a rom?
Thanks!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Gfrt94yn said:
I have another question for somebody knowledgeable in rooting/rom flashing:
I think this was because the s4 bootloader is locked (through an update), would this cause the phone to hard brick? I've had nasty experiences in the past with locked bootloaders!
If it is locked, is there a way to unlock it? Or does it even need to be unlocked to flash a rom?
Thanks!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
The bootloader is locked yes, but Loki is there to workaround that. What is the build version on your replacement?
JDQ39.I337UCUAMDL
Is Loki on xda? I haven't found anything like that yet, although I've heard many references to that
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Update:
Maybe I should open my eyes lol, found it in about 30 seconds
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
One more update:
I ran the casual root and now have my root and recovery. A couple of questions:
Does this also unlock the bootloader?
Somebody said that twrp flashes roms as if the bootloader is unlocked, so it wouldn't matter if it was or not. Is this true?
I guess really my question is, once I run casual root, is my phone ready to flash?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Gfrt94yn said:
One more update:
I ran the casual root and now have my root and recovery. A couple of questions:
Does this also unlock the bootloader?
Somebody said that twrp flashes roms as if the bootloader is unlocked, so it wouldn't matter if it was or not. Is this true?
I guess really my question is, once I run casual root, is my phone ready to flash?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Your phone is ready to flash, just make sure the ROM you flash has been Lokied or you'd have to flash a Loki kernel/LokiDoki after flashing the ROM (but before rebooting).
Gfrt94yn said:
One more update:
I ran the casual root and now have my root and recovery. A couple of questions:
Does this also unlock the bootloader?
Somebody said that twrp flashes roms as if the bootloader is unlocked, so it wouldn't matter if it was or not. Is this true?
I guess really my question is, once I run casual root, is my phone ready to flash?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
If you are going to use TWRP, make sure the ROM has LOKI applied, and if it doesn't, flash the Loki_Doki patch last before rebooting.
If you use OUDHS recovery, it will Auto-Loki whatever you flash.
Ladies and Gentlemen, I am proud to announce that I've successfully flashed a rom without bricking my phone! *applause*
I thank(ed) you all for the help!
GS4 running slimbean and kanged key lime pie theme.
GiantBallSack said:
If you are going to use TWRP, make sure the ROM has LOKI applied, and if it doesn't, flash the Loki_Doki patch last before rebooting.
If you use OUDHS recovery, it will Auto-Loki whatever you flash.
Click to expand...
Click to collapse
What happens if one accidentally reboots before flashing Loki? Just need to reboot back into recovery and flash it?
godefroi said:
What happens if one accidentally reboots before flashing Loki? Just need to reboot back into recovery and flash it?
Click to expand...
Click to collapse
Yes
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
i have the VZW G2 (VS-980) and its stuck in fastboot mode. ive tried all the different methods listed in these forums and nothing has worked. i cant get into download mode as everytime i try, download mode shows for a second then goes into fastboot mode again. PLEASE HELP!!
simon_lefisch said:
i have the VZW G2 (VS-980) and its stuck in fastboot mode. ive tried all the different methods listed in these forums and nothing has worked. i cant get into download mode as everytime i try, download mode shows for a second then goes into fastboot mode again. PLEASE HELP!!
Click to expand...
Click to collapse
How the hell did you brick it? Give us some more background on what tweaks, root methods, flashing recovery methods did you use or else its hard to diagnose the issue.
ericdabbs said:
How the hell did you brick it? Give us some more background on what tweaks, root methods, flashing recovery methods did you use or else its hard to diagnose the issue.
Click to expand...
Click to collapse
ok. i was on stock. rooted with the IO method. wanted to flash a ROM (clean rom). downloaded ROM, wipe dalvik/cache/data. after reboot, phone booted into recovery mode. tried going into download mode to revert back to stock and LG FlashTool failed. said phone was the wrong model number (D802). the ROM i Downloaded said it was for VZW G2. obviously it wasnt. so i finally ended up using fastboot to push boot image and it booted, but in about phone, it says it D802 model (i just got it to boot, where as before i was stuck in fastboot mode). now i need to return to stock, but dont know how. any ideas?
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2517649&highlight=bricked
Gnarfsan said:
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2517649&highlight=bricked
Click to expand...
Click to collapse
well, i actually was able to restore a backup i had of my stock rom and that fixed the model number prob, however now i cant get into download mode so i can do a reflash :/
simon_lefisch said:
well, i actually was able to restore a backup i had of my stock rom and that fixed the model number prob, however now i cant get into download mode so i can do a reflash :/
Click to expand...
Click to collapse
Even following the steps posted in that thread?
Gnarfsan said:
Even following the steps posted in that thread?
Click to expand...
Click to collapse
yes. not sure why its doing that. is there any way that download mode can be deleted from the phone? also, how do you get into fastboot mode?
EDIT: nevermind. i finally got it into download mode!! (thank god!!) flashing right now. damn that was a pain in the ass. i was starting to freak out that i messed up my phone. this is my first LG phone so this process is a little new to me (been on moto for the last few years) thanks for trying to help me out. this was def a learning experience.
Phew, I'm glad to hear that. Some day I will be in the same situation
Sent from my LG-D802 using XDA Premium 4 mobile app
Just a quick question. Why would you even need to go into download mode to flash a Rom? Never once have I done that. Really, just curious.
Thanks Devs. From my VZW G2.
trickster2369 said:
Just a quick question. Why would you even need to go into download mode to flash a Rom? Never once have I done that. Really, just curious.
Thanks Devs. From my VZW G2.
Click to expand...
Click to collapse
I was thinking the same thing. It's best to stay out of those modes. Get a recovery installed ASAP and do everything that you need to do from there. I recommend TWRP Recovery.
Sent from my LG-D802 using XDA Premium 4 mobile app
Maybe because when flashing stock rom download mode is needed (atleast in my old sammy phone, maybe same in moto phones)
What's wrong with restoring the backup of the stock rom that should have been made before wiping and flashing a different rom? Not sure what I'm missing here.
Sent from my Nexus 10 using XDA Premium HD app
Download mode is useful to flash the entire phone back to stock using the OEM tools. It's not just for the stock ROM. It's everything. It's useful if you get a bit carried away in TWRP and wipe partitions you really shouldn't be touching. Or if you somehow manage to bork your recovery, or at least can't get into it. It's also good if you want your phone to be completely stock to sell it or to send it in on warranty. I'm sure someone could come up with other scenarios where it's useful.
But yes, it is a good idea to keep a backup of your stock ROM. And as always, know what you're flashing, make sure it's for your phone and check md5s. And be mindful of what you're doing in recovery. You should be able to avoid most issues. Download mode is indeed something you shouldn't be using often but as I said above there are situations where it is useful or necessary. It's actually something I suggest you know how to use. I say it's always a good idea to know how to get back to complete stock for warranty stuff, selling, or if something just goes majorly wrong.
The Rom I was trying to flash was apparently for a different model number, yet it was under the Verizon thread. There was no md5 to cross reference. In the end I ended up finding the proper boot image/twrp files and pushed them via fastboot (since I was unable to use adb) which then allowed more to restore a backup of the original Rom. Just took me all night to finally get back to stock. Then I decided to restore to out-of-the-box stock just to make sure all files weren't corrupted our anything.
Sent from my VS980 4G using Tapatalk
Not for nothing, but I ran the LG flash tool without putting the phone in download mode and it worked fine.
Semantics said:
Not for nothing, but I ran the LG flash tool without putting the phone in download mode and it worked fine.
Click to expand...
Click to collapse
Hmm.....interesting. I may try that next time I have to flash to stock.
Sent from my VS980 4G using Tapatalk
Same Problem
simon_lefisch said:
The Rom I was trying to flash was apparently for a different model number, yet it was under the Verizon thread. There was no md5 to cross reference. In the end I ended up finding the proper boot image/twrp files and pushed them via fastboot (since I was unable to use adb) which then allowed more to restore a backup of the original Rom. Just took me all night to finally get back to stock. Then I decided to restore to out-of-the-box stock just to make sure all files weren't corrupted our anything.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Can you fill me in on how you used fastboot to install twrp? I am in the same boat right now...
i'm stuck as well in Fastboot and can't figure it out
emmur0 said:
i'm stuck as well in Fastboot and can't figure it out
Click to expand...
Click to collapse
I sent you a pm
You can you adb side load which is the same for flashing rom, pushing, or pulling file from the phone which is the first thing to learn before flashing anything to the new device that you got and know nothing about.
Sent from my LG-LS980 using xda premium