Related
Im an impatient idiot. Lol. I flashed a boot.img through Odin but I flashed a euro img accidentally. Now my phone turns on shows the Samsung screen and then turns off or screen goes black. I think I need to refashion the sprint stock firmware and it'll work. I can find it. Anyone have it and could send it to me please? I tried doing a factory reset already to no avail. Please help!
Thanks in advance.
hopefully over the next few days we'll see the tar ball for stock; course you could always head to your nearest sprint store and have them flash it for you.
Questions go in Q&A
Sent from my PantechP4100 using xda premium
same thing happened to me. Just spent over a hour at my local sprint store. My tech told me they dont have any software for the phone yet but they did order me a replacement s3. The tech just tried to hard reset it but it doesnt even boot recovery.
Does this help?
http://forum.xda-developers.com/showthread.php?t=1725395
If you can get into odin, just flash the tar in PDA mode.
I guess Ill give it a shot. I can still access odin. Just not too sure if I should continue to tinker with it since sprint has already agreed to send a replacement
s3xda said:
I guess Ill give it a shot. I can still access odin. Just not too sure if I should continue to tinker with it since sprint has already agreed to send a replacement
Click to expand...
Click to collapse
You see when you flash a wrong image, instead of the phone working better you will get quite the opposite.
lol ur absolutely right. This heatwave is making me stupid
Yea I have talked with Sprint, no one has the stock firmware. What does that link you sent out contain? I cannot access it yet because I am a newbie. I can access Odin and am able to reflash if I have the correct firmware.
Also, sorry for posting this in the wrong place.
channelzer0 said:
Yea I have talked with Sprint, no one has the stock firmware. What does that link you sent out contain? I cannot access it yet because I am a newbie. I can access Odin and am able to reflash if I have the correct firmware.
Also, sorry for posting this in the wrong place.
Click to expand...
Click to collapse
Basically the link is for rooting your phone; there are 2 threads in the development area concerning it.
If someone did a factory reset; then went into recovery and did a backup.
Could that backup be used by someone else; say this poor soul. To use to restore them back to stock?
I'm thinking if channelzer0 could get their phone to CWM they could use that method to get back to a working state; would that work??
I can get into both recovery or Odin. Whether itll work or not....im willing to find out if I can.
jdelano said:
Basically the link is for rooting your phone; there are 2 threads in the development area concerning it.
If someone did a factory reset; then went into recovery and did a backup.
Could that backup be used by someone else; say this poor soul. To use to restore them back to stock?
I'm thinking if channelzer0 could get their phone to CWM they could use that method to get back to a working state; would that work??
Click to expand...
Click to collapse
You should be able to simply flash the recovery and the phone should work.
But yeah, someone will probably post the stock rom by the end of the day.
channelzer0 said:
I can get into both recovery or Odin. Whether itll work or not....im willing to find out if I can.
Click to expand...
Click to collapse
I can't do it now as I'm leaving and wont be back until mid-night; if there isn't something you can odin or flash by tomorrow morning. then I'll root and backup my phone, then reset it and backup again and post that backup for you to try.
patience is truly a virtue...
---------- Post added at 08:18 PM ---------- Previous post was at 08:08 PM ----------
can boot into recovery now but still no dice
s3xda said:
patience is truly a virtue...
---------- Post added at 08:18 PM ---------- Previous post was at 08:08 PM ----------
can boot into recovery now but still no dice
Click to expand...
Click to collapse
download:http://d-h.st/qi8
adb push boot.img /sdcard/boot.img
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p7 bs=4096
Be patience next time
Fantastic, thanks. I would like to try this. Can I make this .img a tar file and load through Odin? I put the .img on an external sd card but CWM cannot see, only the internal memory.
How do I ABD? Sorry Im a newb.
Thanks again for your help.
channelzer0 said:
Fantastic, thanks. I would like to try this. Can I make this .img a tar file and load through Odin? I put the .img on an external sd card but CWM cannot see, only the internal memory.
How do I ABD? Sorry Im a newb.
Thanks again for your help.
Click to expand...
Click to collapse
Wait for your replacement an dont tinker till qbking77 releases a video so you dont break your phone.
*facePalm* to this whole thread....:cyclops:
adb cant find my device...
make sure usb debugging is checked in developer options....and also usb drivers are installed.
I did a quick battery pull and now whenever I turn the phone on, it keeps trying to update. SOOOO, is there a way to stop this or take it off through PC with ODIN????
I'm not ready to lose root yet....
Anybody have any ideas? Can I flash a custom rom through ODIN?
KappaAce2010 said:
Anybody have any ideas? Can I flash a custom rom through ODIN?
Click to expand...
Click to collapse
You sure you didn't brick your device? I was under the impression doing battery pulls during the update process would mess up your phone.
Someone posted something similar yesterday. Another person suggested pulling the sim card out and then rooting the phone as usual.
Edit: you already have root?
Dr. Cornelius asks you to calm down.
KappaAce2010 said:
Anybody have any ideas? Can I flash a custom rom through ODIN?
Click to expand...
Click to collapse
If the update went through, sorry, you're stuck for now. Here's a link to inform you of the situation.
http://forum.xda-developers.com/showthread.php?t=2359090
Crooke356 said:
Someone posted something similar yesterday. Another person suggested pulling the sim card out and then rooting the phone as usual.
Edit: you already have root?
Dr. Cornelius asks you to calm down.
Click to expand...
Click to collapse
Yes, I already have root. The phone is currently next to me with the battery out.
First off, I'm no expert here. I'm hesitant to offer any advise. Are you able to boot directly to recovery?
Dr. Cornelius asks you to calm down.
Phatdawg said:
You sure you didn't brick your device? I was under the impression doing battery pulls during the update process would mess up your phone.
Click to expand...
Click to collapse
Luckily no, but this is very frustrating. It hasn't fully loaded yet. Trying to figure out if there is a to do a factory reset and have go it go back to what it was in the box.
I would've responded sooner but since I'm a new member.... 5 minute interval responses.
Crooke356 said:
First off, I'm no expert here. I'm hesitant to offer any advise. Are you able to boot directly to recovery?
Dr. Cornelius asks you to calm down.
Click to expand...
Click to collapse
I tried that. It keeps trying to do that damn update.
I've never taken an OTA on a Samsung device. In my experience there is a prompt that verifies you want to install after the download. IF it's the same here, I would THINK your safe to Odin.
If you can get to recovery, throw a ROM on your SD card and flash.
Edit: oh new member
Dr. Cornelius asks you to calm down.
---------- Post added at 10:16 PM ---------- Previous post was at 10:10 PM ----------
By "loading" do you mean downloading? Or is actually installing?
Dr. Cornelius asks you to calm down.
you have to poke a accept after it downloads
then it boots to download mode
if you like
you can revert stock to MDK wipes everything
http://www.sxtpdevelopers.com/showthread.php?t=237
flash to complete stock and re-root ??
Not sure how far out of the way you would like to go..
I downloaded the OTA and let it site on the stock MDK phone for over a day before I rooted and installed ota root keeper to test to see if I can restore root..with out bricking
I could of easily delete the fota cache where it downloaded to and frozen the propitiate file to stop the update
Crooke356 said:
I've never taken an OTA on a Samsung device. In my experience there is a prompt that verifies you want to install after the download. IF it's the same here, I would THINK your safe to Odin.
If you can get to recovery, throw a ROM on your SD card and flash.
Edit: oh new member
Dr. Cornelius asks you to calm down.
---------- Post added at 10:16 PM ---------- Previous post was at 10:10 PM ----------
By "loading" do you mean downloading? Or is actually installing?
Dr. Cornelius asks you to calm down.
Click to expand...
Click to collapse
Its actually installing. Can't get into recovery.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
KappaAce2010 said:
Anybody have any ideas? Can I flash a custom rom through ODIN?
Click to expand...
Click to collapse
no custom roms thru odin.
---------- Post added at 07:35 AM ---------- Previous post was at 07:33 AM ----------
get into recovery and just flash a custom rom.
If you have titanium backup, use it to freeze SDM 1.0 and FWUpdate. This will keep the new software from downloading and keep the software update notification from appearing (provided it hasn't been installed by now).
Sent from my SCH-I545 using Tapatalk 4 Beta
best idea has been said, get that thing into custom recovery where the OTA cant install. try beating the phone as it tries to install and get it into download mode and see if u can flash a custom recovery though ODIN
What you can do at this point depends a lot on what has already been updated on your phone.
If the bootloader is already updated, then there's no way for you to load the older kernel onto it to get it ready to root.
What I'd suggest you do is to go ahead at try the rooting process.
Boot the phone into download mode and try to push the MD2 kernel onto it,
If the install tries to restart, it'll fail since you don't have the expected software, which hopefully will give you a usable system.
Then use motochopper to try to get "su" access.
If ODIN refuses to flash the MD2 software, it's probably the case that you've already gone past the point of no return (i.e. you've got the updated, locked bootloader) and you might as well let the update finish.
If you succeed, then install MDK and Voodoo OTA Keeper and cross your fingers.
Good luck!
Hey all i accidentally hit the OTA update "OK" button when it popped up on my screen. I've been deferring it for the past few months but my finger slipped and hit the "OK" instead of the "defer" and choosing a date to ask again.
I have a looping "Teamwin" logo and it keeps looping.. Cant seem to do anything. I've taken out the battery and then start it up but it still does the same thing.
Any advice, step by step to get out of this loop?
Thanks!
David
you can not OTA update with a custom recovery...time for a date with Odin.
Historical coodsen
droidstyle said:
you can not OTA update with a custom recovery...time for a date with Odin.
Click to expand...
Click to collapse
Would you care to give me a link to do this with a note 2, droidstyle?
yep click the link in my sig...refer to section 1b. you can probably get away with using root66 so you do not have to reroot and unlock BL.
Also when you get back up and running I would recommend freezing SDM1.0 apk with a App such as Titanium back up pro and you will no longer get prompted for OTA updates.
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
hold on a sec, can you boot into recovery? If so you can probably wipe data and re flash the rom you were on.
droidstyle said:
yep click the link in my sig...refer to section 1b. you can probably get away with using root66 so you do not have to reroot and unlock BL.
Also when you get back up and running I would recommend freezing SDM1.0 apk with a App such as Titanium back up pro and you will no longer get prompted for OTA updates.
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
hold on a sec, can you boot into recovery? If so you can probably wipe data and re flash the rom you were on.
Click to expand...
Click to collapse
Whats the key combo to see if i can boot into recovery and ill try it
droidstyle said:
yep click the link in my sig...refer to section 1b. you can probably get away with using root66 so you do not have to reroot and unlock BL.
Also when you get back up and running I would recommend freezing SDM1.0 apk with a App such as Titanium back up pro and you will no longer get prompted for OTA updates.
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
hold on a sec, can you boot into recovery? If so you can probably wipe data and re flash the rom you were on.
Click to expand...
Click to collapse
I just did the Power+home button+volume up and i get a "WARNING!!!!"
a custom os can cause critical problems......
If you want to download a custom OS, etc etc..
stealthrt said:
I just did the Power+home button+volume up and i get a "WARNING!!!!"
a custom os can cause critical problems......
If you want to download a custom OS, etc etc..
Click to expand...
Click to collapse
That's download mode...pull battery and start over.
pwer+home+volume down gets you into recovery.
droidstyle said:
That's download mode...pull battery and start over.
pwer+home+volume down gets you into recovery.
Click to expand...
Click to collapse
Well i just started flashing in odin.... will update when its done.
Doesnt look like obin did anything. after it finished it just rebooted and i still have the teamwin loop.
stealthrt said:
Doesnt look like obin did anything. after it finished it just rebooted and i still have the teamwin loop.
Click to expand...
Click to collapse
And doing the volume down+home+power sends me to the same screen (WARNING!!!... custom os.. etc etc)
Any other advice?
stealthrt said:
Any other advice?
Click to expand...
Click to collapse
he accidentally told you to hit the same button combo. its volume UP home and power. probably still wont boot into recovery though
B_I_N_G_E said:
he accidentally told you to hit the same button combo. its volume UP home and power. probably still wont boot into recovery though
Click to expand...
Click to collapse
Yeah it still does the same teamwin loop doing it that way.
What else can i try?
stealthrt said:
Yeah it still does the same teamwin loop doing it that way.
I tried again to flash and it still is at the loop after a restart...
and also...
What else can i try?
Click to expand...
Click to collapse
did you have the right pda file? for instance was your phone updated to vrall4 or vramc3 and you chose the vraljb file?
B_I_N_G_E said:
did you have the right pda file? for instance was your phone updated to vrall4 or vramc3 and you chose the vraljb file?
Click to expand...
Click to collapse
ive only tried the root66 rom.
stealthrt said:
ive only tried the root66 rom.
Click to expand...
Click to collapse
if you had an updated firmware then that file wouldnt work for you. i also noticed though you put that file in the bootloader field instead of the pda field when you tried flashing it one of those times. that may have been a bad thing. you could try to flash the other file marked vramc from that thread.
B_I_N_G_E said:
if you had an updated firmware then that file wouldnt work for you. i also noticed though you put that file in the bootloader field instead of the pda field when you tried flashing it one of those times. that may have been a bad thing. you could try to flash the other file marked vramc from that thread.
Click to expand...
Click to collapse
Alright i flashed the bootloader and all seems to be fine. I got 2 tutorials mixed up so i though one was using bootloader as the ROM.
All is good now thanks droidstyle and B_I_N_G_E.
B_I_N_G_E said:
if you had an updated firmware then that file wouldnt work for you. i also noticed though you put that file in the bootloader field instead of the pda field when you tried flashing it one of those times. that may have been a bad thing. you could try to flash the other file marked vramc from that thread.
Click to expand...
Click to collapse
root66 works on all devices with the current firmware since it does not contain a bootloader, recovery, or wipe data. Sometimes it will cause a bootloop which all that is needed is to wipe data in recovery.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
stealthrt said:
Doesnt look like obin did anything. after it finished it just rebooted and i still have the teamwin loop.
Click to expand...
Click to collapse
you need to boot into recovery and wipe data...if you can get into recovery the a full odin package will need to be flashed such as stock VRAMC3. However it looks like you figured it out.
Hey guys,
I need a creative solution to restore my phone to stock for warranty claim. My USB does not work so I don't have the usual option of using Odin.
I thought I had found a solution with Mobile Odin but whenever I try to run, it mentions it is not compatible with my device. I am currently on Hyperdrive 17.1 via SS.
Thanks
guyver2077 said:
Hey guys,
I need a creative solution to restore my phone to stock for warranty claim. My USB does not work so I don't have the usual option of using Odin.
I thought I had found a solution with Mobile Odin but whenever I try to run, it mentions it is not compatible with my device. I am currently on Hyperdrive 17.1 via SS.
Thanks
Click to expand...
Click to collapse
If you are on NC5 I have a nandroid backup of a stock NC5 image that only has root. I could give you a link to my dropbox that has the zip and you could flash through safestrap then unroot, etc.... I imagine that would work. Up to you if you want to try it. Just let me know cuz I'm gonna have to boot into it myself and remove all my contacts and everything.
liljoe727 said:
If you are on NC5 I have a nandroid backup of a stock NC5 image that only has root. I could give you a link to my dropbox that has the zip and you could flash through safestrap then unroot, etc.... I imagine that would work. Up to you if you want to try it. Just let me know cuz I'm gonna have to boot into it myself and remove all my contacts and everything.
Click to expand...
Click to collapse
I mean anything is worth a shot...Can you install that via safestrap?
I guess I'm trying to just go back to full stock and even remove the 'custom' message from the boot screen. If only mobile Odin worked..anyone have experience with that and S4?
guyver2077 said:
I mean anything is worth a shot...Can you install that via safestrap?
I guess I'm trying to just go back to full stock and even remove the 'custom' message from the boot screen. If only mobile Odin worked..anyone have experience with that and S4?
Click to expand...
Click to collapse
@joshm.1219 this seem reasonable to do?
---------- Post added at 05:20 PM ---------- Previous post was at 05:19 PM ----------
guyver2077 said:
I mean anything is worth a shot...Can you install that via safestrap?
I guess I'm trying to just go back to full stock and even remove the 'custom' message from the boot screen. If only mobile Odin worked..anyone have experience with that and S4?
Click to expand...
Click to collapse
Yes, you'd be able to flash my NC5 nandroid via safestrap.
liljoe727 said:
@joshm.1219 this seem reasonable to do?
---------- Post added at 05:20 PM ---------- Previous post was at 05:19 PM ----------
Yes, you'd be able to flash my NC5 nandroid via safestrap.
Click to expand...
Click to collapse
Yes it should work, generally you don't want to use nandroids from another phone of course, but if he's just doing it to return to stock for warranty, it should be enough to get it to boot, etc.
guyver2077 said:
Hey guys,
I need a creative solution to restore my phone to stock for warranty claim. My USB does not work so I don't have the usual option of using Odin.
I thought I had found a solution with Mobile Odin but whenever I try to run, it mentions it is not compatible with my device. I am currently on Hyperdrive 17.1 via SS.
Thanks
Click to expand...
Click to collapse
https://www.dropbox.com/sh/bnhwfph6konr7ad/AACqXaf0UTS9pRP8A7GVS6FHa?dl=0
There you go. You should be able to download these files and put the in extsd/TWRP/backup/d.......
And "restore" in safestrap. You will then need to remove safestrap, supersu, and towel root apps and unroot. You may be able to unroot through supersu but I'm not sure. I hope this works for you...keep me posted so I can delete the dropbox folder if it works. Ill be deleting the folder in a day or two anyway just in case. The files are good but I assume no risk if something does go wrong as I've never done anything like this before...you should be OK though.
You may need to flash this https://www.androidfilehost.com/?fid=23501681358539843 for WiFi also.
Great. Well i have downloaded all files onto my SD in the directory mentioned...
When i go into SS to restore, nothing appears. Any idea?
Try making a folder called 'stock' or something in extsd/TWRP/backups/d...... And moving everything to the new folder.
---------- Post added at 10:35 PM ---------- Previous post was at 10:35 PM ----------
guyver2077 said:
Great. Well i have downloaded all files onto my SD in the directory mentioned...
When i go into SS to restore, nothing appears. Any idea?
Click to expand...
Click to collapse
Try making a folder called 'stock' or something in extsd/TWRP/backups/d...... And moving everything to the new folder.
---------- Post added at 10:44 PM ---------- Previous post was at 10:35 PM ----------
guyver2077 said:
Great. Well i have downloaded all files onto my SD in the directory mentioned...
When i go into SS to restore, nothing appears. Any idea?
Click to expand...
Click to collapse
Actually, hold on. I just found an nc5 flashable zip on my extsd. Gimme a min to upload to dropbox. You will def need the WiFi modules I linked to earlier also.
---------- Post added at 11:10 PM ---------- Previous post was at 10:44 PM ----------
guyver2077 said:
Great. Well i have downloaded all files onto my SD in the directory mentioned...
When i go into SS to restore, nothing appears. Any idea?
Click to expand...
Click to collapse
This is an NC5 flashable zip, just install in safestrap as you normally would. It may just be a ROM but I can't remember. https://www.dropbox.com/s/mth9zpmxqg75jgc/VRUFNC5_Rooted_Stock-v2.zip?dl=0
You should be able to unroot and everything. Let me know how it goes.
try replacing usb port
I started fixing phones (mainly iDonts because screens are a LOT cheaper), but I've replaced a usb port on an s4 active and it took me less than 10 minutes start to finish (for your first time I would watch the youtube video a few times and take as much time as needed, and btw fridge magnets work great for not losing screws)
the part should be $10 to $20 with shipping on amazon, and tool kit is less than $5 (the part might come with tools, look in description)
just search youtube "how to replace usb galaxy s4"
the usb port (and attatched flex cable) is not carrier specific, however, it probably differs from the s4 active and mini, and unfortunately don't have one to see if it is, so be sure to look out for that. The procedure IS different between S4 active, S4 mini, regular S4 so be sure you're watching a how to video on the right model
if you need any help with this, reply to this thread or pm and i will help you out.
Unless you have very shakey hands and/or can't see those small screws, I am confident you can do it, for not much has to come apart to replace the usb. The hardest part is the flex cable connection to the motherboard, but if you disconnect it with a PLASTIC tool, you greatly reduce risk of damage, so use plastic. A magnifier may help to see what you're doing, especially when fitting the new cable connection
Good luck!
edit: just looked back n saw the part about warranty. Well, I'm pretty sure you can get away with this, if it is a defective usb port. Those long samsung cables go bad after awhile so try another one (if you knew that already, disregard) and make sure verizon doesn't claim misuse (i.e. forced cable upside down; I used to work for them, they wouldn't replace phones for that reason but that was almost 4 years ago) just maybe try and make it look well taken care of if going warranty route. I am still pretty sure there are no void stickers on any screws, but I can check as soon as I figure out how to get safestrap back after forgetting to flash supersu after Hyperdrive rls19. I miss mdk...wish i didn't break that $180 display, I went with $100 Asurion claim (btw it was a brand new replacement, so any void stickers would be there)
Anyways, hope this helps, reply if need more, and good luck!
liljoe727 said:
Try making a folder called 'stock' or something in extsd/TWRP/backups/d...... And moving everything to the new folder.
---------- Post added at 10:35 PM ---------- Previous post was at 10:35 PM ----------
Try making a folder called 'stock' or something in extsd/TWRP/backups/d...... And moving everything to the new folder.
---------- Post added at 10:44 PM ---------- Previous post was at 10:35 PM ----------
Actually, hold on. I just found an nc5 flashable zip on my extsd. Gimme a min to upload to dropbox. You will def need the WiFi modules I linked to earlier also.
---------- Post added at 11:10 PM ---------- Previous post was at 10:44 PM ----------
This is an NC5 flashable zip, just install in safestrap as you normally would. It may just be a ROM but I can't remember. https://www.dropbox.com/s/mth9zpmxqg75jgc/VRUFNC5_Rooted_Stock-v2.zip?dl=0
You should be able to unroot and everything. Let me know how it goes.
Click to expand...
Click to collapse
Good news. I'm now on a stock rom! Thanks for all your help.
Now to get rid of the custom lock on boot screen and I should be good to go.
guyver2077 said:
Good news. I'm now on a stock rom! Thanks for all your help.
Now to get rid of the custom lock on boot screen and I should be good to go.
Click to expand...
Click to collapse
If I'm not mistaken, that logo can only be removed with an Odin .tar full wipe, for that custom lock shows up when anything to the ROM is changed, which it still may be. Locked bootloader means anything before the safestrap logo is locked (i think). I may be full wiping via odin today for I need to get root again, so I can let ya know if it gets rid of that.
Obviously I'm still a newb to xda, but I've been rooting for few years now, so keep that in mind. Just tryin to get my thx count up so I can actually post things lol. But if I am wrong about ANY of this, I am open to any criticism (so long as not rude and quick explaination why)
Hope this helps
Edit: maybe try flashing that zip again, but wiping system first? But if you lost safestrap I'm not sure how that is possible
guyver2077 said:
Good news. I'm now on a stock rom! Thanks for all your help.
Now to get rid of the custom lock on boot screen and I should be good to go.
Click to expand...
Click to collapse
You can try triangle away from the play store.
Hey folks. I've tried every search here & via Google that I can think of and the answer won't come to me. Here's the weird, surreal, but I assure you very current problem. I screwed around trying to install Jasmine 5.0 and it has bitten me in the rear-end. In order to fix a problem I had with it, I wanted to KDZ back to stock and start over. Unfortunately it won't let me do that. When I try to go into Download mode, it gives me a secure boot error, turns the screen black and flashes the LED at me multicolor-style. The only way to get out of that is a battery pull.
I can boot into Recovery just fine. I'm back on SkyDragon 4.4 as we speak, but not being able to get into download mode is what I'd consider a BIG PROBLEM, considering that's how you fix soft bricks. If I ever have a problem, I'm toast. Thus, my flashing days are pretty well over unless I can get this fixed.
I did find this from @bweN diorD :
bweN diorD said:
well it should be the aboot then. while testing, the only things that gave me a secure boot error were boot (which i just gave you) and aboot.
im not sure how you would install aboot, i dont have a flashable zip. maybe using terminal in twrp, but i have little experience to give advice on that.
Click to expand...
Click to collapse
Does that mean I need to figure out how to get 12B aboot & boot properly restored from the img thread? If so, does anybody know HOW one might do that? I apologize, but I'm VERY much at my wit's end here and can't figure it out right now. Any help at all would be greatly appreciated.
EDIT - FIXED!
annoyingduck said:
Download mode fixed, @hsbadr will be along momentarily with a file to flash the same way you did J-5
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
Go here for download mode fix: http://forum.xda-developers.com/showpost.php?p=59357420&postcount=2237
Don't forget to delete the previous images from your internal sd
Works perfectly, just tested
Click to expand...
Click to collapse
From what I've seen told to other people in the same situation, you need to flash the laf.img, but you'll have to look up how to do that. Probably via adb connected through TWRP? Shrug. Good luck dude, sorry to hear.
Sent from my VK810 4G
There may be a kind person that has a solution. If whatever it is works (he's busy right now), I'll definitely post it here and make it as searchable as possible!
roirraW "edor" ehT said:
From what I've seen told to other people in the same situation, you need to flash the laf.img, but you'll have to look up how to do that. Probably via adb connected through TWRP? Shrug. Good luck dude, sorry to hear.
Sent from my VK810 4G
Click to expand...
Click to collapse
My thoughts exactly, I'll go over that with him, just want to check a few things first.
hokiealumnus said:
There may be a kind person that has a solution. If whatever it is works (he's busy right now), I'll definitely post it here and make it as searchable as possible!
Click to expand...
Click to collapse
How are you going about booting into download mode?
annoyingduck said:
How are you going about booting into download mode?
Click to expand...
Click to collapse
Power off, hold volume up & plug in USB cable.
hokiealumnus said:
Power off, hold volume up & plug in USB cable.
Click to expand...
Click to collapse
Ok, I'm showing the same symptom. Let me test on my device first. give me a few min
annoyingduck said:
Ok, I'm showing the same symptom. Let me test on my device first. give me a few min
Click to expand...
Click to collapse
I've a possible fix... hangouts
just checked to see if i have that issue...ive got everything working fine here...running JasmineROM v5.0 and never had a boot signature error...until...just for the heck of it tried download mode and low and behold my download mode give me that error...
+1 on the secure boot error in download mode. Much appreciated when you guys develop a fix if you could post it here.
jdgesmlls said:
+1 on the secure boot error in download mode. Much appreciated when you guys develop a fix if you could post it here.
Click to expand...
Click to collapse
Working on it with the man himself, just need some testing time...
annoyingduck said:
Working on it with the man himself, just need some testing time...
Click to expand...
Click to collapse
Let me know if you need anyone to test stuff, I am up and running, can get into recovery and restore but again as stated if .tot is required I am in the same boat....
No worries, take all the time you need. Thankfully our devices are working.
We should probably just hold off on our flashing addiction until it's fixed.
hokiealumnus said:
No worries, take all the time you need. Thankfully our devices are working.
We should probably just hold off on our flashing addiction until it's fixed.
Click to expand...
Click to collapse
Yes, definitely... I am fully functional, can make calls and such so your work and expertise is much appreciated!
Download mode fixed, @hsbadr will be along momentarily with a file to flash the same way you did J-5
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
Go here for download mode fix: http://forum.xda-developers.com/showpost.php?p=59357420&postcount=2237
Don't forget to delete the previous images from your internal sd
Works perfectly, just tested
annoyingduck said:
Download mode fixed, @hsbadr will be along momentarily with a file to flash the same way you did J-5
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
Go here for download mode fix: http://forum.xda-developers.com/showpost.php?p=59357420&postcount=2237
Don't forget to delete the previous images from your internal sd
Works perfectly, just tested
Click to expand...
Click to collapse
So I have already restored back to Illusion, and I did that because I was getting an LGSmartCover FC in J-5 once I booted up. Can I flash this in recovery and keep my current setup or do I have to go through the install of J-5 again.
Again, thanks for the quick turnaround on this...
EDIT*** I think nevermind, I thought about it for a minute and just use the same install instructions but replace the contents of FixDownloadMode.zip??
annoyingduck said:
Download mode fixed, @hsbadr will be along momentarily with a file to flash the same way you did J-5
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
Go here for download mode fix: http://forum.xda-developers.com/showpost.php?p=59357420&postcount=2237
Don't forget to delete the previous images from your internal sd
Works perfectly, just tested
Click to expand...
Click to collapse
Works like a charm! Thanks to you both - @hsbadr & @annoyingduck !!!! We would have been in a heck of a bind without your help.
you can flash this on anything....when we were testing J-5 we got a little over protective and decided to upgrade what the new download mode fix script installs to 23b images, which conflict with bumped recoveries. It didn't need to be done, so you should do this repair if you flashed J-5 either way - no matter what current rom your on, it won't effect anything other than download mode. Next J-5 will fix it for everyone. Basically bump requires KK aboot. Download mode requires aboot to match rpm,tz,and laf. Once those get upgraded to LP, download mode fails because of the bumped aboot. Turns out, we didn't need those images to get LP booting, so fixes are in the future.
annoyingduck said:
you can flash this on anything....when we were testing J-5 we got a little over protective and decided to upgrade what the new download mode fix script installs to 23b images, which conflict with bumped recoveries. It didn't need to be done, so you should do this repair if you flashed J-5 either way - no matter what current rom your on, it won't effect anything other than download mode. Next J-5 will fix it for everyone. Basically bump requires KK aboot. Download mode requires aboot to match rpm,tz,and laf. Once those get upgraded to LP, download mode fails because of the bumped aboot. Turns out, we didn't need those images to get LP booting, so fixes are in the future.
Click to expand...
Click to collapse
That worked perfect!
Thanks @hsbadr, @annoyingduck!! as always, great work!!
annoyingduck said:
you can flash this on anything....when we were testing J-5 we got a little over protective and decided to upgrade what the new download mode fix script installs to 23b images, which conflict with bumped recoveries. It didn't need to be done, so you should do this repair if you flashed J-5 either way - no matter what current rom your on, it won't effect anything other than download mode. Next J-5 will fix it for everyone. Basically bump requires KK aboot. Download mode requires aboot to match rpm,tz,and laf. Once those get upgraded to LP, download mode fails because of the bumped aboot. Turns out, we didn't need those images to get LP booting, so fixes are in the future.
Click to expand...
Click to collapse
ok do i have to do a clean flash of jamison5.0 before i flash the fix or can i do a factory reset nd then flash the fix via twrp adb?
nevermind...i just rebooted to recovery and flash...download mode work and didnt have to reflash rom thanks @annoyingduck @hsbadr i was scared here because flashings an addiction
For the download mode fix you shouldn't need to factory reset. Heh, when I used it I was back on KK, booted into recovery, flashed the fix and rebooted straight back into the ROM.