Related
This afternoon I received my replacement phone from Asurion and like and good Android user, I attempted to root it with the Universal root method that had worked really well on my old phone. For some reason, the root did not work and I attempted to restore the phone to stock using the PC36IMG for 3.70 to go along with the 2.10 hboot. Everything seemed to have gone fine until the phone booted up. After a few minutes, it froze and rebooted itself. On top of that, when it does boot it recognizes neither the sdcard nor usb.
I can get into the bootloader and seem to have access to the sdcard from there but any attempts I've made to adb into it have come up with a "no device found" error.
If I attempt to go into recovery, it reboots then goes to the screen with the evo with the red exclamation point on it.
I have no idea what could be the problem or even where to go to try to fix it. I've tried searching the forums but anything I can find about reboots usually has to do with custom roms and any solutions to the other problems seem to revolve around being to adb into the phone while its booted up which does not work due to the lack of usb.
Check k2buckleys post out HERE n report back.
hgelpke said:
This afternoon I received my replacement phone from Asurion and like and good Android user, I attempted to root it with the Universal root method that had worked really well on my old phone. For some reason, the root did not work and I attempted to restore the phone to stock using the PC36IMG for 3.70 to go along with the 2.10 hboot. Everything seemed to have gone fine until the phone booted up. After a few minutes, it froze and rebooted itself. On top of that, when it does boot it recognizes neither the sdcard nor usb.
I can get into the bootloader and seem to have access to the sdcard from there but any attempts I've made to adb into it have come up with a "no device found" error.
If I attempt to go into recovery, it reboots then goes to the screen with the evo with the red exclamation point on it.
I have no idea what could be the problem or even where to go to try to fix it. I've tried searching the forums but anything I can find about reboots usually has to do with custom roms and any solutions to the other problems seem to revolve around being to adb into the phone while its booted up which does not work due to the lack of usb.
Click to expand...
Click to collapse
When you enter recovery, and get the red triangle screen, adb should recognize the phone from there. Also, if you set the phone into 'fastboot' mode, from the bootloader, does fastboot see the device?(fastboot devices) As blake directed you to another post of mine, you see one of the questions is if you are S on or S off. Whats the result there?
also, not sure if some of this may help or not, because you're phone is freezing up, but see this thread in regards to SD card and USB not being recognized.
Whatever the issue is, Z4root also causes the phone to freeze/reboot almost immediately as I run it. I think the problem is that some files got flashed during the attempted root that are still lingering a causing the issues. By all accounts the phone is restored to stock in that it reads the PC36IMG file just fine and restores everything that needs to be restored. It even says that recovery is restored. The problem is that recovery is not restored at all.
I'm quite baffled by it. If I can't fix it, I was hoping to bring it into Sprint for an exchange since it does show s-on and appears to be completely stock. My concern is that it is in asurion replacement and if they send it off, are they going to discover something when it gets back to them, I don't want to get hit with a large sum of $$$.
hgelpke said:
Whatever the issue is, Z4root also causes the phone to freeze/reboot almost immediately as I run it. I think the problem is that some files got flashed during the attempted root that are still lingering a causing the issues. By all accounts the phone is restored to stock in that it reads the PC36IMG file just fine and restores everything that needs to be restored. It even says that recovery is restored. The problem is that recovery is not restored at all.
I'm quite baffled by it. If I can't fix it, I was hoping to bring it into Sprint for an exchange since it does show s-on and appears to be completely stock. My concern is that it is in asurion replacement and if they send it off, are they going to discover something when it gets back to them, I don't want to get hit with a large sum of $$$.
Click to expand...
Click to collapse
If your phone is S on, you have nothing to worry about. Just don't send it in with a bunch of "root related" stuff on your SD card, and you'll be fine. How did you get s on?
Sent from my PC36100 using XDA App
I reflashed the RUU to get the phone back to stock. And by all accounts, it worked. Except that it didnt.
hgelpke said:
I reflashed the RUU to get the phone back to stock. And by all accounts, it worked. Except that it didnt.
Click to expand...
Click to collapse
So running the RUU seemed successful, but it still didn't work? But it did turn you back to S on? Had you used Unrevoked before?
Sent from my PC36100 using XDA App
I did the autoroot found here:
http://forum.xda-developers.com/showthread.php?t=838448
If I'm not mistaken, it uses some of or all of unrevoked, but I'm not sure.
I have not used the files from the unrevoked website though.
Can you attach the autorootlog.txt file to a post for me to take a look at? If you got a refurb phone it may have had something still messed up by the previous owner.
Sent from my PC36100 using XDA Premium App
I'll get the log file when I get home from work. Hopefully there is something telling in there. It didn't really dawn on me that the phone could have been rooted by a previous owner, thereby doing something to my attempt.
It's pretty rare anymore but definitely not unheard of. When the new hardware came out there were a ton of people bricking them by forcing their hboot to downgrade or trying to root with the old unrevoked. And, you could definitely tell with some of the refurbs.
From my personal experiences with asurion, along with those of quite a few people I've talked to, they don't really fix the refurbs as much as just get them back to a useable state so they can be pawned off on someone. The minute you try to root or flash an upgrade/ota it is going to start acting up again.
Sent from my PC36100 using XDA Premium App
Since I'm getting another Asurion phone, what can I do to avoid it in the future?
Depends on what is wrong with it. Although, if it boots to the bootloader then odds are it is fixable.
Sent from my PC36100 using XDA Premium App
Xhausx, I want you on whatever subforum is my hone forum. when this man speaks, . ... listen.
Sent from my PC36100 using XDA App
So, about a month ago i smashed the screen on my phone, accidentally of course. I called Asurion, got a replacement phone. The box had no battery cover, kind of a small issue, but I paid $130 for a new phone, so I should get a freaking back plate. Called Asurion, got another replacement phone sent out, arrived the next day with everything in the box, minus the packing labels and manuals (I was wondering if they ever actually put everything into a box). Phone works great, its on 2.2, Build 1.22.531.8
Now I want to perm root my phone and put S-OFF like i had on my first one, so that I could put custom roms on it. I went through the guide I used on my first G2, do it flawlessly, I use volume down+power to turn on to check if S-OFF, and it wasn't. So wondering if I had done something wrong that hadn't bricked my phone, I repeated the guide again. Alas, S-OFF would not appear. Questioning the guide's files, i went here to XDA.
Again I followed the guide to a t, making sure everything was absolutely correct (the last thing I want is a bricked phone) and using the files on the site, the latest VisionARY, and Android Terminal Emulator (free in the market). Once again, upon checking the for S-OFF in the recovery boot, my phone was still S-ON. Disappointed i tried about 3 more times, everything was working like the guide explained, and every line was correct and double checked. Still no luck.
Now, I am frustrated and annoyed that this replacement phone will not allow me to S-OFF and perm root it... So, here I am asking, Has anyone had an issue with Assurion's replacement phones before? How can I fix this? Any feedback would be lovely. I would like to get my phone S-OFF and perm rooted.
Thanks in advance, if you need any more information, I will gladly give you it.
I need to bump :3
Use this guide instead http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
It's the most up to date and recommended guide.
Visionary has quite a high brick risk, so don't use it.
-Nipqer
I cant download HTC sync when trying to set up the ADB as said by the guide you gave me... its simply not on the list
Its been forever since I did my dz, but doesn't gfree work anymore?
Sent from my HTC Vision using XDA Premium App
Here's a link to HTC sync software, which includes the drivers http://www.htc.com/nz/SupportViewNews.aspx?dl_id=1073&news_id=918
Gfree is the recommended method.
-Nipqer
Thanks man! i will give your suggested method a go, even though, I question whether it is a method problem, or its just my phone is weird because its a replacement from Asurion
Hey! thanks a bunch, that way worked perfectly!
Glad it went well, enjoy your rooted phone!
-Nipqer
Nipqer said:
Glad it went well, enjoy your rooted phone!
-Nipqer
Click to expand...
Click to collapse
Well there is one thing... Whenever i try to put a rom on, no matter what it is, whether its CM7 Stable build or Xboarder56 's 2.3.4 CM/stock rom, it gets stuck on the boot animation. It does the animation for a little while and then freezes, and then restarts... Any idea whats wrong?
Do you wipe data/factory reset and cache before flashing a rom?
Is it just on the first boot or every boot?
All roms will take a little extra time booting for the first time, and will probably need 2~3 reboots to settle into it.
I normally use Superwipe when flashing a new rom.
-Nipqer
Nipqer said:
Do you wipe data/factory reset and cache before flashing a rom?
Is it just on the first boot or every boot?
All roms will take a little extra time booting for the first time, and will probably need 2~3 reboots to settle into it.
I normally use Superwipe when flashing a new rom.
-Nipqer
Click to expand...
Click to collapse
Yes i wipe, and every boot, it does not finish booting, i knew that they take a little longer the first time, but it was 15minutes of boot animation before i pulled out battery. it does not get passed the boot animation
That's very strange, I have no idea what could be causing it.
Might help to try talking to people in #cyanogenmod irc channel, or posting in the cyanogenmod forums.
Sorry I can't be more help.
-Nipqer
how do i install super wipe?
i downloaded the zip... then what?
Nvm, i figured it out.
superwiped, and installed Xboarder56's Mod
Worked like a charm, thank you so much!!!
Not sure how to start this...
first off, i'm pretty sure my phone now has a fried eMMC chip, but in reality, i don't really know...
the reason i say i think it's fried is because no matter what method i try to flash anything to my phone with...it simply won't do it...most fastboot commands will not work anymore, my computer won't load the devise anymore so no adb commands, bootloader fails everything when trying to flash a stock rom and gets hung up updating the radio_v2....i've tried running official RUU's but it keeps telling me my phone has less then 30% battery life, wich is simply false. and i can't get into my recovery without it crashing the phone and not letting me turn it back on (till battery pull).
i went onto the #g2root and #xda-devs channels on the freenode server in mIRC, and had talked to a couple people there who also think i probably fried the eMMC chip (making it impossible to write or read anything from the phone), but again...i'm really going on word of mouth rather then first hand knowledge here.
but again today, i ran into yet another possible solution and i just want to know if i should bother trying or if i have a chance.
http://forum.xda-developers.com/showthread.php?t=1314629 is the thread, but i think this is for a desire s, so i suppose my question would be...would this method still work if i just used the right files or, again, am i screwed?
i have an HTC Desire Z that i got from Bell in Canada. it has gotten an OTA firmware update, and does not have root or s-off
if i remember right, everything is still stock, completely. minus the now possibly fried eMMC chip lol
thank you in advance and i will try to edit this post as neccessary so as to update any needed info.
please ask me questions as to what i have done and i will try my best to let you know. i know i had followed probably too many guides for rooting with too many methods lol next time, xda-dev's wiki guide, and that's it!
[edit:] i just found this too...lemme know if this helps..... http://forum.xda-developers.com/showthread.php?t=1284196
[edit:] i do know that when i go into my recovery, it does say those things (e: can't mount cache, blah blah) but it crash's out and doesn't actually get me into the recovery console. if so i would be able to envoke some adb commands and just finish this, but that's adding to the issue really...not being able to get into my recovery.
i feel with you.
it happend for me just today morning.
got my desire z on thursday, installed usual apps.
it started to freeze in random app installations. the last softreset threw it into a boot loop with the same problems you stated above.
you can get pre formated desire z emmc's for around 30 - 40 euro i think. but soldering them on your own requires some skill and tools since their contacs are below and not on the side.
this accident threw me back to my old htc touch diamond (with windows mobile 6.1 D: )
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
So, let me begin this tale with this disclaimer: I've worked with modding communities across a whole span of genres, from gaming to building computers. I will begin with the assumption that I am at fault in this case and I'm clearly doing something wrong. I've about reached the end of possibilities that I can explore on my own, so it's not like I tried one thing and gave up.
Once upon a time, I knew more about what I was doing than I do now. I first bought the T800 model several years ago, and the first thing I did was learn how to root it and flash CWM recovery. I went on all sorts of adventures with the device but never fully explored the potential; just installed awesome stuff that I thought I would use forever and got rid of bloatware and other useless crap. Flashforward to a few months ago, when I realized I had a really nice tablet that I had spent money on but didn't use like I had wanted to. I'm working more and more on audio mixing, and I wanted to install an app for the tablet that would allow me to remotely operate a mixing board. To my dismay, the app required an updated version of Android, and I hadn't a clue as to how to do that because the tablet was rooted and such and the thing wasn't going to update (was stuck on stock 4.4.2). I don't remember what I had done with it many years ago - at least not very well - and all I had learned was nearly gone. I refreshed a little, made a backup, checked to see what I had and noticed I still had the CWM recovery up, things were still rooted fine, and I was prime for flashing a new ROM and wiping everything. Found the Lineage ROM, slapped that puppy down, aaaand... Verification wasn't happening. Huh? It didn't even try to install, it just gave up and put the stock ROM back on. Tinkered with it for a second and thought, eh, whatever, I'll just let it update itself now that it's been wiped and everything. Only the device still wouldn't let me update it to Marshmallow or whatever update limit it's got.... Awesome... Did a little more research. Oh, my recovery is probably super out of date. Grabbed ODIN, slapped a brand spankin' new TWRP recovery that was geared for my device on it, and decided that I shouldn't go with Lineage. I'll just go with a stock Nougat ROM (can't post a link, but if it's important I can PM it to you if it's relevant).
Followed instructions to the T (as far as I'm aware) and this time did everything with a fresh new outlook into what I was doing. Flashed it, flashed GAPPS, aaaaaand.... Samsung logo won't go away.... -sigh-... Wiped it again, tried to make sure everything was wiped correctly, made sure everything was up to date. Tried again, but alas... Nothing working right for me.
Perhaps during this tale you've already picked up on something I royally messed up. Perhaps you're thinking, "Wow, how did this doofus not brick his tablet?" Am I getting old and stupid? Was there still research I missed? I started with the low road of easy modding and had to force myself to a higher road of deeper learning and STILL came up empty-handed, so now I'm asking this awesome community for a hand. I know you can't do this for me, but I'd appreciate a guiding light, or at the very least a link to an article that I really should have picked up on. Let me know if there's information I've missed that I should also be putting out, and thanks for reading regardless!
If I reached a point where I don't understand what's going on and I am banging my head against the wall, I would download the latest stock firmware for my device from sammobile and flash it with odin. If I recally it correctly, that would be the November 2016 security release of Marshmallow, the last Samsung provided. This should wipe away everything you have on the tablet. Then, if you need to flash root or alternative ROM, flash TWRP and proceed from there.
Akopps said:
If I reached a point where I don't understand what's going on and I am banging my head against the wall, I would download the latest stock firmware for my device from sammobile and flash it with odin. If I recally it correctly, that would be the November 2016 security release of Marshmallow, the last Samsung provided. This should wipe away everything you have on the tablet. Then, if you need to flash root or alternative ROM, flash TWRP and proceed from there.
Click to expand...
Click to collapse
Much obliged for your response, I've been up for a bit hoping maybe the boot process would just take a while, but no luck there. In the meantime I've been trying a few different Lineage nightly builds and they all seem to result in the same problem; surely they can't all be messed up and it's obviously something I'm doing wrong. My last recourse is to do this terminal fix I found that worked for someone else, but I doubt I'd be that lucky. I will assume that the Nov 2016 Marshmallow release is a google search away (or am I just bad at finding things...), and I'll post back here either within the hour or tomorrow night when I have time to find this build. Again, thank you.
Merancapeman said:
Much obliged for your response, I've been up for a bit hoping maybe the boot process would just take a while, but no luck there. In the meantime I've been trying a few different Lineage nightly builds and they all seem to result in the same problem; surely they can't all be messed up and it's obviously something I'm doing wrong. My last recourse is to do this terminal fix I found that worked for someone else, but I doubt I'd be that lucky. I will assume that the Nov 2016 Marshmallow release is a google search away (or am I just bad at finding things...), and I'll post back here either within the hour or tomorrow night when I have time to find this build. Again, thank you.
Click to expand...
Click to collapse
Download the appropriate MM version from below. Boot to recovery, factory reset, flash with Odin.
First boot will take around 10 minutes.
http://updato.com/firmware-archive-...xact=1&r=&v=Marshmallow(Android+6.0.1)&rpp=15
Merancapeman said:
So, let me begin this tale with this disclaimer: I've worked with modding communities across a whole span of genres, from gaming to building computers. I will begin with the assumption that I am at fault in this case and I'm clearly doing something wrong. I've about reached the end of possibilities that I can explore on my own, so it's not like I tried one thing and gave up.
Once upon a time, I knew more about what I was doing than I do now. I first bought the T800 model several years ago, and the first thing I did was learn how to root it and flash CWM recovery. I went on all sorts of adventures with the device but never fully explored the potential; just installed awesome stuff that I thought I would use forever and got rid of bloatware and other useless crap. Flashforward to a few months ago, when I realized I had a really nice tablet that I had spent money on but didn't use like I had wanted to. I'm working more and more on audio mixing, and I wanted to install an app for the tablet that would allow me to remotely operate a mixing board. To my dismay, the app required an updated version of Android, and I hadn't a clue as to how to do that because the tablet was rooted and such and the thing wasn't going to update (was stuck on stock 4.4.2). I don't remember what I had done with it many years ago - at least not very well - and all I had learned was nearly gone. I refreshed a little, made a backup, checked to see what I had and noticed I still had the CWM recovery up, things were still rooted fine, and I was prime for flashing a new ROM and wiping everything. Found the Lineage ROM, slapped that puppy down, aaaand... Verification wasn't happening. Huh? It didn't even try to install, it just gave up and put the stock ROM back on. Tinkered with it for a second and thought, eh, whatever, I'll just let it update itself now that it's been wiped and everything. Only the device still wouldn't let me update it to Marshmallow or whatever update limit it's got.... Awesome... Did a little more research. Oh, my recovery is probably super out of date. Grabbed ODIN, slapped a brand spankin' new TWRP recovery that was geared for my device on it, and decided that I shouldn't go with Lineage. I'll just go with a stock Nougat ROM (can't post a link, but if it's important I can PM it to you if it's relevant).
Followed instructions to the T (as far as I'm aware) and this time did everything with a fresh new outlook into what I was doing. Flashed it, flashed GAPPS, aaaaaand.... Samsung logo won't go away.... -sigh-... Wiped it again, tried to make sure everything was wiped correctly, made sure everything was up to date. Tried again, but alas... Nothing working right for me.
Perhaps during this tale you've already picked up on something I royally messed up. Perhaps you're thinking, "Wow, how did this doofus not brick his tablet?" Am I getting old and stupid? Was there still research I missed? I started with the low road of easy modding and had to force myself to a higher road of deeper learning and STILL came up empty-handed, so now I'm asking this awesome community for a hand. I know you can't do this for me, but I'd appreciate a guiding light, or at the very least a link to an article that I really should have picked up on. Let me know if there's information I've missed that I should also be putting out, and thanks for reading regardless!
Click to expand...
Click to collapse
Hello, Lineage dev for T800 here.
Did you flash the updated bootloader I link in the OP? Gotta be on the MM one for it to boot past that samsung logo
Can be flashed via ODIN, instructions are on there!
Lemme know if you get it!
DarkExistence said:
Hello, Lineage dev for T800 here.
Did you flash the updated bootloader I link in the OP? Gotta be on the MM one for it to boot past that samsung logo
Can be flashed via ODIN, instructions are on there!
Lemme know if you get it!
Click to expand...
Click to collapse
Just got back from work, about to test it out and will update on both situations (should one not work out). Regardless of the success, I'm genuinely honored that you guys are helping me in this process and I didn't expect such a warm and welcoming bit of support. Too often I see the "well any bloomin' idiot with enough IQ in his head to tie his shoe could have done this" comment, although I'm almost positive I'm going to get this fixed with your help and realize I've done something super stupid.
Welp, I'm a right idiot. I went with the first option, which was to attempt to flash a stock MM ROM. I followed akopps and ashyx' advice and went to that website where I believed I found the appropriate file and downloaded it. For some odd reason it took about 8 hours to download almost 2gb, which is odd because my net is faster than that. Anyway, I let it sit overnight so no issues there. A while ago I attempted to copy it over to my SD card, which was met with a slew of problems thanks to the copy process being cancelled multiple times. Maybe because the size of it? I had plenty of space. At any rate, it wasn't going to be an issue because I knew it was something I was probably doing wrong and would figure out later. I skipped and went straight toward DarkExistence's fix, which was to make sure I had the MM bootloader (I saw this instruction in your thread but at the time wasn't sure what it entailed and thought I was perfectly safe, and this was sadly before I learned more about what I was doing). Went through that process just in case, wiped, flashed the Lineage ROM , flashed GAPPS, rebooted, aaaand...
Bugger me, it worked.
So now I feel like a proper idiot. I hope this ends up in a google search down the line so other doofuses can stumble upon my own mistake and see that sometimes overlooking one simple thing can make all the difference. Will update in the future should anything change and I find myself doomed once more, but so far things seem tip-top. I checked to see if I could install the mixer remote app I had initially begun this journey for, and lo and behold it is now available for me to download! Now all that's left is to figure out how to root it, and voila! Thank you all so much, I am almost as relieved as I am embarrassed.