Related
Today I decided to power cycle my Dinc and all hell has broken free. Basically I'm stuck in a never ending boot loop and I am lost on how to get my ICS back. I have tryied restoring preview 7, reflashing p7, restoring p8 and reflashing p8. I would consider my phone may be broken but I can flash anyother rom and can restore back to stock ( which I mite add really sucks but) what choice do I have. I really could use some sugestions, I am not a noob and know my way around adb just need someone to point me in the right direction. Thanks in advance
Editt: I'm a dumb one I forgot to factory reset....lol
Sent from my Xoom using Tapatalk
Hi everybody!
I figure we should have a thread dedicated to telling horror stories about flashes gone wrong. Whether it's because of power failures, bad USB cables, poorly labeled packages, or pure user error, we've all had that moment of worry: "Did I just turn my device into a paperweight?"
It's my hope that, by sharing these stories, we can help each other realize that we're all human, we all make mistakes, and most mistakes can be recovered from. Don't be afraid to share your stories; we can't learn from each other's mistakes if nobody talks about them!
_____________________________________________
My first story is from my Telus SGS3 (I747M, you'll see why that matters in a moment) and is definitely a user-error kind of story.
I've been playing around with CM10 and its derivatives for the past month or two (got my SGS3 on release day and it wasn't running Samsung software 3 hours later) and I'm not new to Android, having run XDAndroid on my HTC Diamond, and bouncing between CM7 and CM9 on my Milestone. The first thing I did when I got my SGS3 was a full block device backup using DD from the command line, which is the only reason I don't have a paperweight today.
I decided to try out Paranoid Android over a week ago and I've been loving it, so I haven't been flashing much lately. But, when I got back from vacation and saw that CM10 had gone into nightly builds, I couldn't resist the temptation to try a clean install. I've got folders on my SD card for ROMs, GApps, kernels, recoveries, and anything else flashable just to make my life easier. Apparently at some point I downloaded an AT&T (I747, no M) modem, stuck it in a "/modems/" folder with the rest of my flashables, but realized that it wouldn't work on my device, so I never used it. I then promptly forgot that I had put it on the SD card, and it had a fairly cryptic filename. Away I went, flashing CM10, GApps, a nice bootscreen, and... the modem.
Dammit. :crying:
At this point, I was running the newest CM10 build, but with a borked modem. I thought I had fallen victim to the IMEI bug that's been going around, but then I remembered something about that modem file not being usable on a Telus device... And had no idea how to get back to a working state. I already knew that none of my nandroid backups would have the modem in them, and the only "stock" flashables I could find were rooted kernels and a nearly-700MB "stock" package that wouldn't download any faster than 10 kb/s. I couldn't wait 20 hours for a download, I wanted my phone now! I tried using Odin with a few of the TAR packages I found, but that only made my situation worse to the point of failing to boot entirely, even restoring a nandroid wasn't helping anymore.
I started digging through the forums in the hope that someone had ripped the Telus modem into a CWM flashable zip, but had no luck. I tried both the Rogers and Bell modems with the same results. That's when I remembered that I had done a block backup, but I had no idea which block device was the modem, and my phone wouldn't even boot up to let me MTP the files over. I was left with CWM recovery as my only option, and had to ADB push 2.5 GB of .img files to the SD card, and DD them one at a time through the ADB shell.
Somehow, it all worked out, and I was back to running Stock Touchwiz with root, and was then able to restore a nandroid from yesterday and amazingly enough Paranoid Android booted up, happy as ever, and in came my emails and text messages. I know I'm lucky that my IMEI didn't get lost in that mess, but it just goes to show that there's no such thing as a backup being "too extensive". You never know when "mmcblk0p99" needs to be replaced with a known working copy.
I do believe im going to flash a stock/rooted ROM and then do a dd backup.
What options do you set for your backups?
Sent from my SGH-I747M using xda premium
I did as follows:
Code:
cd /dev/block/
ls
(get the list of mmcblk devices from here)
dd if=/dev/block/mmcblk0p1 of=/sdcard/dd/blk0p1 bs=4096
...
dd if=/dev/block/mmcblk0p99 of=/sdcard/dd/blk0p99 bs=4096
Obviously you shouldn't have 99 partitions... but you get the idea. I ran each line manually.
Then just move the /dd/ folder off your /sdcard/ and onto some safe storage.
I bought my device off someone from Craigslist 2 nights ago. Went home with device working great. Decided to update from ICS to JB, downloaded everything on the ol gaming machine, go to update using Kies, then BAM! Hung update, bricks phone immediately. Woo....great experience after dropping $400 on phone lol. Contacted Samsung support who told me my update wouldn't work until I registered? I told him it bricked my phone and it wasn't being picked up by computer anymore and I wanted to go back to ICS, he apparently thought waiting 24 hours would fix driver issues. Found JB official rom and learned about Odin. Worked at it until 2-ish am, never worked, woke up, did ICS instead same method, worked immediately, then update worked.
Moral of story? Don't trust Samsung apparently, go with 3rd party everything....
Can we share from other devices? Because I've had a serious one with my nitro HD lol.
Sent from my SGH-I747 using xda premium
After having my phone on stock rooted touch wiz since day one I was tempted to go jellybean... So months later I'd say Octoberish I finally said f**k it I'm going aokp... So I ran the task and k toonsen romantic for a while until they started porting the t mobile jelly bean stock tw rom... It made me miss tw and it's awesome camera app... So I flashed it after a week or so upon its release... First thing I noticed was the phone would get txts and phone calls rarely (keep in mind I'm in an lte area) and it became un bare able after about an hour. So I reverted back to my aokp nandroid and just figured I'd call it a day... But when I restored my nandroid my service was still messed up.. So after a bit of gooogling I checked my phone status to find my imei to be 0!!! I was beyond upset... So I tried re flashing stock in Odin and everything else I could find (unfortunately the imei restorer wasn't existent yet) and it came to the point where I left it stock and went to the att repair center down the road... The guy didn't know what was wrong with it and I just played dumb... After about 30 mins he came to the conclusion that my sim card slot was broken and I got a new phone...
After getting this one back home I instantly rooted it again
I've been staying away from those ported tmobile roms ever since
Sent from my SAMSUNG-SGH-I747
[/COLOR]
rani9990 said:
Can we share from other devices? Because I've had a serious one with my nitro HD lol.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I dont see why not. All stories are interesting lol
Sent from my SAMSUNG-SGH-I747 using xda premium
No bad flashes .... Yet?
Sent from my Nexus 7 using xda app-developers app
Alright then,
It was my first day with the LG Nitro HD. My first smartphone (don't comment xD) and I was prepared to root and flash the living crap out of it. Done with rooting, now to install CWM. Simple enough, right? WRONG. This was the one time where google was not my friend. I followed a horribly misleading guide, and ended up with a paperweight. Turns out I flashed the recovery image to the secondary bootloader partition, thereby bricking my phone completely and utterly, irreparably. Had to ship it off to LG, and they fixed it, no questions asked. Thank God for that...
I had an HTC Touch Pro on Sprint. You had to flash a stock ROM before flashing a new custom ROM or the phone would stop working properly after almost exactly an hour. The file system would become completely messed up but the OS would keep running from RAM. It would fail to reboot after that. It was such a pain that I updated my phone every ~3-4 months.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
This one actually just happened this weekend.
So I finally got bored of having stock ICS on my i747 (Rogers), and since I loved cm 7/9 on my SGS2, I figured I'd go with the latest (15 dec) CM10 nightly.
downloaded to phone, rebooted in recovery, wiped data and cache, and installed the new firmware.
booted up and I've got no (or inconsistant) cell service. Figure it's a bug that hasn't been fixed, so no biggie, I backed up a week ago, so I decided to revert back to stock for the time being.
go through the process, and discover I still only have EDGE data.... WTF?
So I do some reading *AFTER the fact, hur dur...* and discover the IMEI wipe issue, and surprise surprise, I didn't do an NV backup, since I didn't know it'd get wiped.
Spent a couple hours keeping the phone / computer away from the 13 month old while I replace the IMEI NV data.... Still stuck on EDGE.... at least my IMEI is showing up though.
Nick
Odin back to stock worked for me when that happened to me.... YMMV.
Sent from my SGH-I747 using xda premium
The night I got my phone, I rooted via odin and when it booted, I'd get a framework FC every 90 seconds or so. It took me almost two hours to get cwm recovery on my phone to flash AOKP. Not a brick, but since I hadn't even activated it, yet....not happy.
Sent from my SGH-I747 using xda app-developers app
Each Phone an Adventure
I can completely relate to all of you. Though I'm new as a member (thought I already had an account but apparently I didn't), I've been using the forum for a long time. I have rooted four phones to date, each with its' own disaster story and happy ending. My latest was the AT&T S3. While not a disaster entirely, the no flash counter guide ended up not working out for me. So I paved my own trail so to speak and I found all the root dependencies (Recovery, ROM, the works) by myself. The entire process took me about a day. I also used TriangleAway which threatened explosions if anything went wrong and thankfully nothing did. I'm glad I never had to send a phone back, I've always been very cautious about any type of flashing and always read the forum before doing it.
When I was on the captivate, I really wanted JB so I thought I could grab the Nexus S JB ROM cause the devices were so close to each other. Flashed it via Odin. Good God was that a mistake. I couldn't get back to download mode using the button combo since the button mapping was all switched up. I had this one cable that would give me bad connection, so I jiggled that around in the port for 35 minutes trying to get download mode. Finally, I got it and flashed the stock package. Learned my lesson, will never flash something from a different phone or anything that won't work 100%.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
goobs408 said:
When I was on the captivate, I really wanted JB so I thought I could grab the Nexus S JB ROM cause the devices were so close to each other. Flashed it via Odin. Good God was that a mistake. I couldn't get back to download mode using the button combo since the button mapping was all switched up. I had this one cable that would give me bad connection, so I jiggled that around in the port for 35 minutes trying to get download mode. Finally, I got it and flashed the stock package. Learned my lesson, will never flash something from a different phone or anything that won't work 100%.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
The thing about the Captivate was, no matter what ROM you flashed, the jig ALWAYS worked. It saved my ass quite a few times, until that is, the memory in the phone decided to die. I could flash through Odin as much as I wanted and it would pass everytime, but never go past the boot animation.
Dave the Knave said:
The thing about the Captivate was, no matter what ROM you flashed, the jig ALWAYS worked. It saved my ass quite a few times, until that is, the memory in the phone decided to die. I could flash through Odin as much as I wanted and it would pass everytime, but never go past the boot animation.
Click to expand...
Click to collapse
Flash stock GB with forgot name of kernel baked in. After that in cwm recovery partition external SD card.. then reflash in Odin then install whatever ROM u want
Sent from my SGH-I747 using xda premium
Trying to use Kies to flash anything. That's always a bad story for me
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Don't attempt to explain to a friend of little flashing knowledge how to root their phone. He hard bricked my phone. Odin is easy if you read but he turned it into rocket science and yeah.. Had to wait for another phone
Sent from my SGH-I747 using xda app-developers app
Well let me begin by saying I have a Galaxy Nexus and have been flashing roms, etc like it's going outta style. It's very simple to me and I am no newb. So with this logic in mind, I got a brand new GS3 the other day and proceeded to do the same. First, it took my a while to realize there are so many variants of our phone, then when I did a search I saw that there was a i9305 that is LTE....you already know where this is going. I figured that was the correct variant, spent like an hour trying to install a recovery because of the auto wipe feature and thus increasing the flash counter to 10+ (wtf!). Finally I download a rom, flash it. Freezes half way through (knew that wasn't good) and when I pull the battery, BAM, bricked phone.
After some more reading, not only did I find out the correct way of flashing to not increase the counter but also that the Canadian versions are the i747! Luckily it happened a day after I got it and I switched it out for a new one. Moral of the story: If you are flash happy and think all phones are like the Nexus, that's your biggest mistake! lol
Hello,
When I woke up a few moments ago I noticed that a system update icon was in my notification bar, which I assume is the new ZVD update and right now my phone is on ZVC and is stock rooted using ioroot25 and I have TWRP 2.7.0.0 AND download mode both working thanks to AutoRec and everything is working fine but it was a difficult getting to this point because I was one of the early adopters of the AutoRec method and I had to to go back to stock and re-tot my phone numerous times to get root, recovery, & download mode all 3 working on my phone without issue.
Now that the ZVD update is waiting to be downloaded on my phone I do not want to have to go through all this stuff again nor do I want to lose anything I have on my phone currently so I would like to ask what is the recommended / safest way to install this update so that I can keep root, recovery, and download mode all 3 and not lose any of my data at the same time ?
Of course, I want to also make sure that this does not mess up my phone like the white screen issue some people had when using AutoRec on the Sprint version of the G2 or other issues so what are my choices and thanks in advance for any and all replies.
MTCell
You won't be able to until they fix the update. Even just root will lock the system on the update.
Only safe way right now is to tot back to stock zvc, take the update. Root with ioroot25. If you want recovery, you can use auto-rec and then flash dorimax kernel. Which has the zvd knock code in it.
Sent from my LG-LS980 using Tapatalk
secret.animal said:
You won't be able to until they fix the update. Even just root will lock the system on the update.
Only safe way right now is to tot back to stock zvc, take the update. Root with ioroot25. If you want recovery, you can use auto-rec and then flash dorimax kernel. Which has the zvd knock code in it.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I also have a similar issue as the OP. I am currently rooted, stock rom. ZVD update has downloaded and is ready to install. However, what would be the nessesary steps to take prior to updating my phone? I dont care if I have to re-root again. I rooted me device using IOroot25. How can I unroot?
Thanks!
Supersu has the option to unroot permanently. Doing a full unroot. Weather the system accepts that, I'm not sure.
Sent from my Nexus 7 using Tapatalk
secret.animal said:
...Only safe way right now is to tot back to stock zvc...
Click to expand...
Click to collapse
But, reflashing the ZVC tot will erase all data, correct?
jlv3 said:
But, reflashing the ZVC tot will erase all data, correct?
Click to expand...
Click to collapse
Yes, complete everything. Data, pictures, documents, downloads.
Sent from my Nexus 7 using Tapatalk
mtcellph said:
Hello,
When I woke up a few moments ago I noticed that a system update icon was in my notification bar, which I assume is the new ZVD update and right now my phone is on ZVC and is stock rooted using ioroot25 and I have TWRP 2.7.0.0 AND download mode both working thanks to AutoRec and everything is working fine but it was a difficult getting to this point because I was one of the early adopters of the AutoRec method and I had to to go back to stock and re-tot my phone numerous times to get root, recovery, & download mode all 3 working on my phone without issue.
Now that the ZVD update is waiting to be downloaded on my phone I do not want to have to go through all this stuff again nor do I want to lose anything I have on my phone currently so I would like to ask what is the recommended / safest way to install this update so that I can keep root, recovery, and download mode all 3 and not lose any of my data at the same time ?
Of course, I want to also make sure that this does not mess up my phone like the white screen issue some people had when using AutoRec on the Sprint version of the G2 or other issues so what are my choices and thanks in advance for any and all replies.
MTCell
Click to expand...
Click to collapse
From what i understand , you will need a stock ZVC recovery and boot loader to apply the update. if you have any modification done in ROM (debloat/deleting/modifying system files) then the update might not complete.
So flash stock aboot(bootloader), recovery and kernel and then only apply the update.
TOT reflash is too cumbersome process and requires lot of restoration of apps setting etc.
I have same situation and am searching for stock files from ZVC. Please if any one has these stock file please do share.
Cheers
Phuq! I wish I read these forums more frequently.
Hey all,
Okay now, let me begin this horror story by say what I think needs to be said first and foremost.
"No matter your level of knowledge, there is always something new for you to learn."
With that being said, I phuqed up!!
I had my dream setup running almost perfectly. I mean heavily modded. Stock kitkat 4.4.2. from Sprint so I didnt have to upgrade anything. I rooted via .apk file. I autorec'd TWRP recovery. I first flashed a furnace kernel that gave me 2.49GHz overclock. And added in xdabebs cam mod. And loved it. I kept reading and researching. I found more goodies to play with. I install xposed framework and some useful add-in's. I find some old apps I love, like hide softkeys, and several quick launchers like pie control, and gestures. I eventually find D's kernel and was elated! 2.8GHz, whoopee! (although I have seen someone @3GHz.)
After about a weeks worth of additions, and stupid auto-updates from google play (omfg they take up so much room) I got that dreaded icon in my notifications bar that Im out of room!!!! Stupid phuq'n non Korean model phones! (I feel that is hella racist of LG to show their people love and phuq us over with no external memory support. We should arrange a class action law suit. Thats purposely shaping the market favorably in your region, and selling obsolete hardware to the rest of the world. "shameful behavior LG")
So to remedy the space issue, I go through my most painful, and totally ridiculous ritual of removing "my" bloatware. All the launchers that I dont really NEED or use OFTEN. The apps that are convenient to have , but that convenience is never utilized. Or its rarely needed. And that helped me out about say, oh 200mb.
DAMN IT! need more room! Need room now!! Ahhhhhhhhhhh!
Okay so a few Big boys had to go. So I dumped a game or two, and the 2nd OS I forgot about on my device, Kali Linux. That gave me the much needed room. I gained about 4GB back. Cool beans, I figure before I do any new major changing of this phone I will force myself to make room for backups, ON device! :angel:
Well that didnt pan out. Instead I did one better, (I thought) I chose to back up on device, then rip it to my PC. Cool , it has the space for storing crap like that..
"ahh, life and its inevitable bullshnikeys"
BAM!! a day or so later, my PC froze, in the middle of a gnarly drift. Crap, restart, checks disk , fixes one error, bam froze again, "ah shiz, I need to back up my back ups!" checks disk, a few errors , I have seen worse. I got it up and running then, ZZZzzzzrrrrttt! NOOOoooooooh! So the PC goes down hard. No HDD found style.
So I reach for my G2 to take a much needed brake on the throne and plan somethings out. I sit down, hit the pwr button, and my phone was in TWRP! Odd I think to myself, and proceed to reboot. TWRP! look through settings, look for anything new on the sdcard (internal) nothing. So I power it down and turn it back on. TWRP! Furious!
Now Im at defcon5 using my LIVE OS, BT5r3 KDE, and decided to hear back into the XDA jungle to see what might have happened.
I got the update for ZVD it would seem. And it bit me in the ass at the worst time. I do not have the Android drivers that the phone installs to the PC installed and configured because I cant cycle into Android OS. Im seriously stuck in TWRP mode. I managed to get into download mode once after trying for 20minutes to do so. ( I need to practice that) But for no avail, I couldnt configure/install/set anything up that would have allowed me to communicate with the phone.
Im so very tired and stressed. Normally I would throw this crap away and go back to my trusty and (IMO) more stylish motorola RZRv3, but its battery is like a joke with its 3 minute, PERIOD life time. SMH
So now I come before you, alone, tired, confused, and depressed, (I do not, like reinstalling anything, ever, in anything.) I just really dont want to hit that brick wall (pardon the pun) an know I have to, ahem, configure, so many apps that I enjoy using. All because I lost my recovery.
What is it about the recovery file that makes the option for keeping your user installed apps, achievable, versus the wack (not even an option at all) choice of having to wipe everything and start over? Because (IMO) that is in no way, a recover. Thats a fumble, oh, interception. Thats dropping the ball. If you waste all the space for "backing things up" then something happens, and you still have to completely wipe the IMPORTANT stuff!! Whats the point?
I have found and installed on this VB PC running windows 7 non sp1, x86-
LG Flashtool 1.8.1.1023
LG-Mobile-Driver v 3.8.1
adt-bundle-windows-x86-20140702
adbpush
LG PC Suite (that just serves no purpose other than to annoy me by not working WITH my phone)
I have downloaded the .dll for MY phone for Flashtool
I found and downloaded the 45475791e80904201311e1051ea628c3b98eef87.LS980ZVC_12-LS980ZVD_19_update from sprint
I have downloaded CloudyG3_1.2 and cm-11-20140623-nightly-ls980
What can I do to attempt to simply boot back into my android.
and if there is no option for simply restoring the functionality of the devices previous state,
what ROM/OS do you suggest I shove in this brick or what method should I use to punch the life back into my phone?
Im dyin ova eeeah!!!
Thanks in advance,
Orcinus
ZVD bit me too-not sure how, NEVER told it to install
adamant_orcinus said:
Hey all,
Okay now, let me begin this horror story by say what I think needs to be said first and foremost.
"No matter your level of knowledge, there is always something new for you to learn."
With that being said, I phuqed up!!
I had my dream setup running almost perfectly. I mean heavily modded. Stock kitkat 4.4.2. from Sprint so I didnt have to upgrade anything. I rooted via .apk file. I autorec'd TWRP recovery. I first flashed a furnace kernel that gave me 2.49GHz overclock. And added in xdabebs cam mod. And loved it. I kept reading and researching. I found more goodies to play with. I install xposed framework and some useful add-in's. I find some old apps I love, like hide softkeys, and several quick launchers like pie control, and gestures. I eventually find D's kernel and was elated! 2.8GHz, whoopee! (although I have seen someone @3GHz.)
After about a weeks worth of additions, and stupid auto-updates from google play (omfg they take up so much room) I got that dreaded icon in my notifications bar that Im out of room!!!! Stupid phuq'n non Korean model phones! (I feel that is hella racist of LG to show their people love and phuq us over with no external memory support. We should arrange a class action law suit. Thats purposely shaping the market favorably in your region, and selling obsolete hardware to the rest of the world. "shameful behavior LG")
So to remedy the space issue, I go through my most painful, and totally ridiculous ritual of removing "my" bloatware. All the launchers that I dont really NEED or use OFTEN. The apps that are convenient to have , but that convenience is never utilized. Or its rarely needed. And that helped me out about say, oh 200mb.
DAMN IT! need more room! Need room now!! Ahhhhhhhhhhh!
Okay so a few Big boys had to go. So I dumped a game or two, and the 2nd OS I forgot about on my device, Kali Linux. That gave me the much needed room. I gained about 4GB back. Cool beans, I figure before I do any new major changing of this phone I will force myself to make room for backups, ON device! :angel:
Well that didnt pan out. Instead I did one better, (I thought) I chose to back up on device, then rip it to my PC. Cool , it has the space for storing crap like that..
"ahh, life and its inevitable bullshnikeys"
BAM!! a day or so later, my PC froze, in the middle of a gnarly drift. Crap, restart, checks disk , fixes one error, bam froze again, "ah shiz, I need to back up my back ups!" checks disk, a few errors , I have seen worse. I got it up and running then, ZZZzzzzrrrrttt! NOOOoooooooh! So the PC goes down hard. No HDD found style.
So I reach for my G2 to take a much needed brake on the throne and plan somethings out. I sit down, hit the pwr button, and my phone was in TWRP! Odd I think to myself, and proceed to reboot. TWRP! look through settings, look for anything new on the sdcard (internal) nothing. So I power it down and turn it back on. TWRP! Furious!
Now Im at defcon5 using my LIVE OS, BT5r3 KDE, and decided to hear back into the XDA jungle to see what might have happened.
I got the update for ZVD it would seem. And it bit me in the ass at the worst time. I do not have the Android drivers that the phone installs to the PC installed and configured because I cant cycle into Android OS. Im seriously stuck in TWRP mode. I managed to get into download mode once after trying for 20minutes to do so. ( I need to practice that) But for no avail, I couldnt configure/install/set anything up that would have allowed me to communicate with the phone.
Im so very tired and stressed. Normally I would throw this crap away and go back to my trusty and (IMO) more stylish motorola RZRv3, but its battery is like a joke with its 3 minute, PERIOD life time. SMH
So now I come before you, alone, tired, confused, and depressed, (I do not, like reinstalling anything, ever, in anything.) I just really dont want to hit that brick wall (pardon the pun) an know I have to, ahem, configure, so many apps that I enjoy using. All because I lost my recovery.
What is it about the recovery file that makes the option for keeping your user installed apps, achievable, versus the wack (not even an option at all) choice of having to wipe everything and start over? Because (IMO) that is in no way, a recover. Thats a fumble, oh, interception. Thats dropping the ball. If you waste all the space for "backing things up" then something happens, and you still have to completely wipe the IMPORTANT stuff!! Whats the point?
I have found and installed on this VB PC running windows 7 non sp1, x86-
LG Flashtool 1.8.1.1023
LG-Mobile-Driver v 3.8.1
adt-bundle-windows-x86-20140702
adbpush
LG PC Suite (that just serves no purpose other than to annoy me by not working WITH my phone)
I have downloaded the .dll for MY phone for Flashtool
I found and downloaded the 45475791e80904201311e1051ea628c3b98eef87.LS980ZVC_12-LS980ZVD_19_update from sprint
I have downloaded CloudyG3_1.2 and cm-11-20140623-nightly-ls980
What can I do to attempt to simply boot back into my android.
and if te youhere is no option for simply restoring the functionality of the devices previous state,
what ROM/OS do you suggest I shove in this brick or what method should I use to punch the life back into my phone?
Im dyin ova eeeah!!!
Thanks in advance,
Orcinus
Click to expand...
Click to collapse
Sorry Dude, I was in the same spot, maybe I can save you hours of reading. This is what I had to do:
http://forum.xda-developers.com/showthread.php?t=2432476 it's the dreaded tot to zvc
Whenever I try to download anything it says it failed and when I open lecture notes it says "this app needs a directory at the media/shared/external storage (SD card) to store the notebooks." I previously flashed the CM lollipop ROM for p600, but reverted back using my complete nandroid backup (every option checked and restored). What can I do to fix? This tablet is an essential tool for school for me. Thanks
Just an update. I re-flashed the p600 CM Lollipop ROM and am now working again. I'm guessing something gets restructured when flashing this ROM that isn't reverted when restoring my old ROM via nandroid? Maybe if i reflashed 4.4 via odin all would be good? Dont really care at this point as the tablet sucks. Doesn't matter I suppose. Really really fighting the urge to unload this thing for dirt cheap and get maybe $200 for it so I can buy a Surface Pro 3....
supremekizzle said:
Just an update. I re-flashed the p600 CM Lollipop ROM and am now working again. I'm guessing something gets restructured when flashing this ROM that isn't reverted when restoring my old ROM via nandroid? Maybe if i reflashed 4.4 via odin all would be good? Dont really care at this point as the tablet sucks. Doesn't matter I suppose. Really really fighting the urge to unload this thing for dirt cheap and get maybe $200 for it so I can buy a Surface Pro 3....
Click to expand...
Click to collapse
you went from stock firmware to CM and then you nandroid'd back to touchwiz? you should odin back to stock and then reflash a rom. even after a full wipe, some residual files can stay there and mess with the system. highly recommend ODINing back to stock if your jumping between android versions.
if your still looking to sell for dirt cheap, send me a PM and we'll figure it out over swappa. I personally love this tablet.
moabizzi said:
you went from stock firmware to CM and then you nandroid'd back to touchwiz? you should odin back to stock and then reflash a rom. even after a full wipe, some residual files can stay there and mess with the system. highly recommend ODINing back to stock if your jumping between android versions.
if your still looking to sell for dirt cheap, send me a PM and we'll figure it out over swappa. I personally love this tablet.
Click to expand...
Click to collapse
You know of any good guides to ODIN back to stock? Bought the Surface Pro 3, but would like to compare and contrast the two before deciding to sell.... Thanks
supremekizzle said:
You know of any good guides to ODIN back to stock? Bought the Surface Pro 3, but would like to compare and contrast the two before deciding to sell.... Thanks
Click to expand...
Click to collapse
Follow this Root guide to get through odin. instead of using the CF autoroot file, you use the stock firmware file.
http://forum.xda-developers.com/galaxy-note-10-2014/development/root-cf-auto-root-t2905495
I saw somewhere that there some similar event happened with the S5 to where Tmobile locked bootloader. How long does it take to find a workaround? Reason I ask is because I do not want to go throught the whole process of installing everything and entering credentials if it is something that happens fairly quickly. I have the nandroid backup ready to flash via odin whenever i can get to that point.
Just would like to hear some of the pros experience with something like this.
No exact science. I'd go ahead and set it up. You can titanium back up after root before you go flash happy. With the S4 I think it only took a few weeks and I skipped the 5. It really shouldn't be long though since this is a popular phone and has lots of Debs on it
Sent from my SM-G925F using XDA Free mobile app