I can't seem to find a thread to help me restoring my nexus s back to a factory state.
I did flash via adb, but I am having issues with my phone, so I want to re flash.
Thanks for your help
Matt
Code:
fastboot oem lock
fastboot oem unlock
(then lock again if you want)
That will erase EVERYTHING. Then you can flash clockwork back. Then flash one of the stock ROMs (found here on the forums somewhere or from ROM Manager). Basically back to stock. (With custom bootloader). Which you can also get rid of, I just don't remember how
Why not just flash the newest stock from samfirmwares via Odin? Semms quicker and easier to me, but ... are there any disadvantages?
fallenguru said:
Why not just flash the newest stock from samfirmwares via Odin? Semms quicker and easier to me, but ... are there any disadvantages?
Click to expand...
Click to collapse
I've always considered Odin to be a last resort kind of thing. You really shouldn't Odin unless everything else doesn't work and your phone is near screwed. The reason being, should anything go wrong during the Odin flashing, your device runs a very high risk of permanently bricking and the past the point of no return. Its probably the only way of permanently bricking your Nexus.
Sent from my Nexus S using XDA App
Hmm, ok.
I've always used Odin for my Samsung i5700 (Galaxy Spica), mainly because there is nothing else for it. It's always seemed extremely stable and lightweight to me, never mind the factory floor look.
AFAICT Odin can only brick your phone if your computer explodes at exactly the right time (i. e. while it's flashing the bootloader) - no idea if fastboot has additional safeguards or something.
An inexperienced user has a much better chance of screwing up in a multi-step restore, so if the objective is to restore to an out-of-the-box state then I'd still rather use Odin, personally. (For modding parts of firmware and comfort, fastboot beats it hands down.)
I came from the Vibrant, so I see where you're coming from. But like you said, an inexperienced user has a better chance of screwing it up. That's why I recommended the non-odin method to the OP. To each his own I guess. Both methods will take you to the same end result, one which is slightly less of a hassle. I just cringe everytime I use Odin in fear of windows crashing or Odin crashing since previous versions were known to be relatively unstable. Or some other mishap like kicking the USB cable while flashing.
Sent from my Nexus S using XDA App
I just used odin and ROM from here
http://forum.xda-developers.com/showthread.php?t=947950
Restore 2.3.1 through CWM
http://forum.xda-developers.com/showthread.php?t=884093
download the nandroid backup in that thread and restore using cwm. then do a factory reset and lock bootloader with "fastboot oem lock". that's what i did.
peeturr said:
I came from the Vibrant, so I see where you're coming from. But like you said, an inexperienced user has a better chance of screwing it up. That's why I recommended the non-odin method to the OP. To each his own I guess. Both methods will take you to the same end result, one which is slightly less of a hassle. I just cringe everytime I use Odin in fear of windows crashing or Odin crashing since previous versions were known to be relatively unstable. Or some other mishap like kicking the USB cable while flashing.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
while i can agree that odin is not very... user friendly in the sense of many errors. it is very slim chance of it causing a brick. and why not just use heimdall? its the open source solution to odin
Check the Q&A section. Yet another nexus S perma-bricked using Odin. In this case he used the wrong files (i9023 instead of i9020) to flash. Anything could happen. If you could avoid it, you really should because Odin messes with very sensitive files.
Sent from my Nexus S using XDA App
peeturr said:
I've always considered Odin to be a last resort kind of thing. You really shouldn't Odin unless everything else doesn't work and your phone is near screwed. The reason being, should anything go wrong during the Odin flashing, your device runs a very high risk of permanently bricking and the past the point of no return. Its probably the only way of permanently bricking your Nexus.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
What permabrick using odin, never happen.
Sent from my SPH-D700 using XDA App
U can't permbrick your phone with odin
Sent from my Nexus S using XDA App
demo23019 said:
U can't permbrick your phone with odin
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Try loading i9023 Odin files onto your i9020.
Sent from my Nexus S using XDA App
peeturr said:
Try loading i9023 Odin files onto your i9020.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
dont do that that'll mess up with the phone's functionality because it'll start acting like a 9023 when its a 9020.
Maybe the procedure here may help you.
http://theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/
Actually, I'm quite sure you can brick phones with Odin, if you try. Flashing the wrong firmware (or any other random bucket of bits) certainly works, as you can see. But I'm curious, how would fastboot have prevented this?
Sorry to the OP, I neither wanted to derail your thread nor start a holy war, just offer another option.
well it goes without saying to not use another phones firmware... but using the correct firmware on the correct phone odin has a small chance at bricking.. and thats only when your flashing boot.img and sbl.bin. he shouldnt be using the pit as odin pulls it from the phone. and there is almost no reason to repartition the device.
nabiladeeb said:
Maybe the procedure here may help you.
Click to expand...
Click to collapse
Thanks, really helpfull!
I have a problem;Do I have a I9020 or I9023?
When I look in settings-about phone it is Baseband version I9023XXKB1, but if I look in the fastboot mode I find Baseband version I9020XXKB1.
Witch one is correct?
Please help,
Thank you
peeturr said:
Try loading i9023 Odin files onto your i9020.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
shame on someone using a rom not even made for there phone but still i dont see how that will perm brick your phone when you can still access download mode
Related
I have locked hardware vibrant should I take the chance of installing clockwork. And flash rom's Cuz what if I get stuck in vibrant screen than I can't do anything. I bricked my last phone. By usin Odin by adb. It just froze on Odin after that there was no going back. So what should I do?
Sent from my SGH-T959 using XDA App
flameinthefire said:
I have locked hardware vibrant should I take the chance of installing clockwork. And flash rom's Cuz what if I get stuck in vibrant screen than I can't do anything. I bricked my last phone. By usin Odin by adb. It just froze on Odin after that there was no going back. So what should I do?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I personally have had no issues flashing at all. I do not have a locked vibrant but I've literally pulled the cable when in the middle of flashing with odin just to try to brick it, which thankfully I've had good luck thus far. However this is up to your discretion. If you feel competent enough to do it, then go for it. Otherwise if you feel that you'd rather not risk another brick then i'd step back.
Good Luck
What is safer for flashing roms Odin or Clockwork?
Sent from my SCH-I500 using XDA App
I feel way more comfortable with odin, but thats just me. Had a brick with clockwork, never any trouble with odin. Just ALWAYS use the pda button only.
Sent from my rooted froyo Fascinate
I like Odin, just don't like having to take my body glove case off each time! If only Odin worked with battery in.
vlucchetti said:
I like Odin, just don't like having to take my body glove case off each time! If only Odin worked with battery in.
Click to expand...
Click to collapse
It does, taking the battery out is just recommended since people will often mess it up their first time. A lot of themes, also, let you reboot straight into download mode as well.
Personally, I feel safer using CWM. CWM might be able to trash all the stuff, but it shouldn't be able to prevent you from being able to get into download mode, leaving Odin as a tool of last resort.
KitsuneKnight said:
It does, taking the battery out is just recommended since people will often mess it up their first time. A lot of themes, also, let you reboot straight into download mode as well.
Personally, I feel safer using CWM. CWM might be able to trash all the stuff, but it shouldn't be able to prevent you from being able to get into download mode, leaving Odin as a tool of last resort.
Click to expand...
Click to collapse
this is the smartest way to do it. power gets cut to the computer while using odin it is likely to brick your device. when I use old in I cross my fingers some idiot don't run into a power pole, mouse chew a wire, roommate turn on a vacuum and trip a breaker.
Rocking dj05 and jt's voodoo 5
Thx
Sent from my SCH-I500 using XDA App
KitsuneKnight said:
It does, taking the battery out is just recommended since people will often mess it up their first time. A lot of themes, also, let you reboot straight into download mode as well.
Personally, I feel safer using CWM. CWM might be able to trash all the stuff, but it shouldn't be able to prevent you from being able to get into download mode, leaving Odin as a tool of last resort.
Click to expand...
Click to collapse
LOL, you must have known I soft bricked my first attempt to root.
I prefer CWM for roms, but WHENEVER I use Odim, it is on a laptop so there is 0 chance of a power loss...
Cwm is safer. ODIN has a higher brick potential, especially if you're sleep deprived or less than sober.
Sent from my SCH-I500 using XDA App
Daswolven said:
Cwm is safer. ODIN has a higher brick potential, especially if you're sleep deprived or less than sober.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I would personally say the opposite. You need to follow instructions on Cwn (wipe this, wipe that, install this, install that, etc) which causes problems for people who doesnt follow instructions 100%. Odin is a lot easier as you just click one button. I guess you shouldnt use odin if you are blind (or drunk) since you may press phone, instead of pda.
Kaze105 said:
I would personally say the opposite. You need to follow instructions on Cwn (wipe this, wipe that, install this, install that, etc) which causes problems for people who doesnt follow instructions 100%. Odin is a lot easier as you just click one button. I guess you shouldnt use odin if you are blind (or drunk) since you may press phone, instead of pda.
Click to expand...
Click to collapse
I agree, CWM IS safer, but if you mess up in CWM you might be forced to ODIN if you didn't backup.
Kaze105 said:
I would personally say the opposite. You need to follow instructions on Cwn (wipe this, wipe that, install this, install that, etc) which causes problems for people who doesnt follow instructions 100%. Odin is a lot easier as you just click one button. I guess you shouldnt use odin if you are blind (or drunk) since you may press phone, instead of pda.
Click to expand...
Click to collapse
how do you go about getting odin?
heimdall is safer than odin and cwm is the safest
Sent from my SCH-I500
yea im with you on this. .i trusted cmr with my old droid but not with my sammy
ziggy484 said:
I feel way more comfortable with odin, b
ut thats just me. Had a brick with clockwork, never any trouble with odin. Just ALWAYS use the pda button only.
Sent from my rooted froyo Fascinate
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
I usually only use Odin after I have messed something up and need to flash a stock rom to get me going again. But other than flashing a modem I usually only use clockwork to install roms.
Okay guys, So lets say you flashed a custom rom on your epic. The rom was crap and you didnt like it. So you boot into CWM or w.e your Custom Recovery is and you restore your backup. After the backup is restore you end up with the Samsung Boot Logo STUCK.! This can be caused by incompatibility within the roms. Nandroid restore dosent always work when reverting back to stock from a custom rom, Unless your nandroid back up is from another custom rom. So this is a tip or flashing you phone back to Stock EB13. Its even better if you have a stock nandroid backup because restoring the backup whilst having this stock rom installed will work.! Go to this site http://www.samsdroid.com/2011/11/samsung-sph-d700-epic-4g-stock-rom.html and download the stock rom of your choice. Place the rom on your SD card. NOTE: Use sdcard in another phone since yours is bricked, or if you have a Micro Sd Reader use that. Boot up into Recovery and flash the rom. Congrats you are now back to stock and can do a Nandroid Restore. No ODIN, NO HARD WORK.! Happy Flashing
LINK FOR SW UPGRADE if the above method dosent work for you: http://ifile.it/8alqt5h/Epic4G_FroyoUpgrade_EB13_Tool.exe
Did you check the links before you posted this? They're all dead.
And they're all links to leaked firmware, not stable ones officially released by Samsung(With the exception of EB13).
The links aren't dead when I check them. If the links didn't help you out. Then google "Sph d700 SW upgrade tool" Its a utility that automatically flashes phone back to stock EB13. Just put the phone into download mode, by holding. "1" button on keyboard and hold power and plug in the pc. Follow the on screen instructions. If you can't find it PM me and ill upload it to 4shared for you to download.
Sent from my SPH-D700 using xda premium
I am by no means an expert but... If you are coming from an MTD ROM, you have to use the victory.pit file to repartition the NAND back to BML. To my knowledge, there is no way to do this from CWM (is the recovery partition rewritten when repartitioning?). If that executable linked at the end of the post can reproduce the partitioning that Odin does, then yes, but you still must have the windows drivers, a good USB cable and be plugged into a good USB port. At that point, why not use Odin.
Sent from my SPH-D700 using XDA App
You are indeed correct. The SW upgrade is the linked .exe for inexperienced user. Not everyone knows how to use Odin. Yes it may be simple to us but a pain to others. Im pretty sure if people are flashing roms, the samsung drivers should already be installed on there computer. The sw upgrade comes with the DOWNLOAD MODE Driver, So that when you plug the phone into the computer whilst in download the drivers are automatically installed. Within a couple of clicks you are back to stock EB13. From there you can re-root using the one click and do Nandroid Restore.
There is already a guide for this
Sent from my SPH-D700 using Tapatalk 2
There are but there all explained in different ways. This is the easy way to explain the method above. Just download and follow the instructions. Alot of people are using odin. And alot of people are struggling when using it because of the lack of knowledge. So Im just putting this method back out there to remind users that this is also possible if you do not understand odin.
AnDrOpErZ said:
There are but there all explained in different ways. This is the easy way to explain the method above. Just download and follow the instructions. Alot of people are using odin. And alot of people are struggling when using it because of the lack of knowledge. So Im just putting this method back out there to remind users that this is also possible if you do not understand odin.
Click to expand...
Click to collapse
I agree with this but 90% of people here are on MTD and will brick by doing this. Also, when recovery works you can just flash another ROM. Still a good guide.
Sent from my SPH-D700 using Tapatalk 2
Thanks, And i actually flash other ROMs if i end up with a brick. But the first time i flashed CM9 i missed a step and bricked, and it wouldnt let me flash another rom without the samsung screen hanging. So i used this utility to get back to stock, root, and restore backup. Great tool for people who still enjoy great ol' BML. Thanks for the compliment. By the way love your theming dude.
AnDrOpErZ said:
LINK FOR SW UPGRADE if the above method dosent work for you: http://ifile.it/8alqt5h/Epic4G_FroyoUpgrade_EB13_Tool.exe
Click to expand...
Click to collapse
http://www.mediafire.com/file/bpgsh6udv1gd8nj/Epic4G_FroyoUpgrade_EB13_Tool.exe
Please give me credit to!
disturb3d1 said:
http://www.mediafire.com/file/bpgsh6udv1gd8nj/Epic4G_FroyoUpgrade_EB13_Tool.exe
Please give me credit to!
Click to expand...
Click to collapse
OP is no longer maintaining this thread and has left the forum.
Mr Glass- may we have a lock, please?
(Hmmm- "glasslock"? Maybe your alter ego?)
Sent from my SPH-D700 using xda premium
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 was updating my mdl s4 to a new build and flashed a rom for t0ltetmo, a T-Mobile note, by accident. I believe it updated the bootloader but not totally sure.
This is the error I get from TWRP when trying to flash a backup:
twrp E: unable ti mount ' /system'
If I go back to stock using kies can I then root with casual? Or will kies change my bootloader to something undesirable (mk1, nb1, etc.)
Any help would be greatly appreciated.
Have you tried flashing the correct firmware in Odin? You may have bricked your device, but it's a good sign you can still get into twrp.
Sent from my Nexus 5
No haven't tried Odin. I only have a Mac, need to borrow a friends PC. Don't think it's bricked. I believe it has the note 2 bootloader, and that's why TWRP isn't flashing the backup
numbere said:
No haven't tried Odin. I only have a Mac, need to borrow a friends PC. Don't think it's bricked. I believe it has the note 2 bootloader, and that's why TWRP isn't flashing the backup
Click to expand...
Click to collapse
If odin doesnt work, check out mobiletechvideos.com they fixed my bricked S4.
numbere said:
No haven't tried Odin. I only have a Mac, need to borrow a friends PC. Don't think it's bricked. I believe it has the note 2 bootloader, and that's why TWRP isn't flashing the backup
Click to expand...
Click to collapse
You could try a Windows vm on the Mac
Sent from my Nexus 5
Will try running odin on windows vm. Do you know if I go back to stock using kies if the bootloader will update to something other than the original MDL?
numbere said:
Will try running odin on windows vm. Do you know if I go back to stock using kies if the bootloader will update to something other than the original MDL?
Click to expand...
Click to collapse
If you use kies it'll force the latest firmware. You want to use Odin.
Sent from my Nexus 5
jd1639 said:
If you use kies it'll force the latest firmware. You want to use Odin.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for all the support! That was a scary situation.
Got Odin to run on parallels. Before using Odin I gave twrp one last try. Factory reset and then flashed a rom I tried previously, but this time without the gapps. Success! Got very lucky on this mistake.
Word to the wise double check your rom before flashing.
numbere said:
Thanks for all the support! That was a scary situation.
Got Odin to run on parallels. Before using Odin I gave twrp one last try. Factory reset and then flashed a rom I tried previously, but this time without the gapps. Success! Got very lucky on this mistake.
Word to the wise double check your rom before flashing.
Click to expand...
Click to collapse
Glad you got it working. It may have been a bad download of gapps.
Sent from my Nexus 5
No I definitely flashed a rom for the note 2.
Makes me think it's a sign that the software in our community is becoming more stable. Meaning that one can flash the incorrect ROM and potentially not destroy their device.
Sent from my SGH-I337 using XDA Premium 4 mobile app
numbere said:
No I definitely flashed a rom for the note 2.
Makes me think it's a sign that the software in our community is becoming more stable. Meaning that one can flash the incorrect ROM and potentially not destroy their device.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, you got lucky. The partitions are different for different devices and that's what will get you. I.e.flash a boot img where system is supposed to be and you'll be hard bricked
Sent from my Nexus 5
Wow, what a coincidence.
I had a similar issue over the last couple of days.
Here: http://forum.xda-developers.com/showthread.php?t=2701379
I used Odin in VMWare Fusion and it would not work at all, except to flash bootloaders and kernels. I finally got it to work through using heimdall using this thread: http://forum.xda-developers.com/showthread.php?t=2374441