Hi everybody.. I've been viewing and reading the XDA forums for years, looking for help and tips with various phones.. I just registered today so I could share my recent experience with rooting the Note II (sch-i605 from Verizon) that I bought used.
I was doing my due diligence, researching different methods of rooting, several different websites, which I've concluded are a waste of time because they all link back to the best! Trying to decide if it was worth it with the locked bootloader.. After reading up on several different threads, I figured what the heck.. So I bit the bullet and dove in.. No easy task this, because I don't have internet access at home, other than on my wife's phone with unlimited data.. Downloading the files necessary, saferoot, safestrap, twrp, various versions of drivers, some programs.. All very time consuming over 4g! Lol..
Anyway, having rooted a Motorola Droid Razr, a Samsung Epic 4g, OG Droid, an LG G2, along others in the past, I'm not an expert, but not exactly a n00b at rooting either.. I Odin on my PC from when I did the Epic, and adb was there from multiple devices, so that saved a little time.. So over to the PC I go with my Note 2, wife's G2 and my trusty USB cable..
Saferoot worked beautifully! First time success! Installed jrummy root check to verify.. :good:
I let that be it for while since the bootloader is perma-locked.. But after a couple hours of reading more threads about ROMs, I started feeling the itch again.. So off to download twrp so I can play with some shiny new ROMs.. The twrp website has installation instructions for twrp manager from the play store, upgrading from inside an earlier version, fresh install with Odin, and using "su dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p9".. Since I was on the other side of the room, I decided to try the dd method.. Not having experience with this particular command, I figured some practice was in order.. Read up on what it does, played around with it using some worthless files.. Then I used it in reverse.. Finally I ran the did command for real.. That's when it all went downhill.. When I rebooted I ended up with the Dreaded Yellow Triangle of Doom! Unauthorized software and take the phone to Verizon.. Ask I had was download mode.. :crying:
Fought with the phone and the computer for a while until my wife made me give it up for the night. Studied up some more on the , and jumped right into things first thing this morning.. Downloaded a couple .IMG stock room files, one rooted one not, and a stock recovery .IMG to use with Odin.. Got them into the PC, Windows 7 Pro, hooked up the new brick and fired up Odin.. No joy.. Odin wouldn't see my phone! Time for a smoke break, just had to step back and think about things for a minute or two. After a Google search and some digging, i found a YouTube video describing exactly my problem(Odin or Kies won't recognise download mode). I tried it, and guess what, IT FREAKING WORKED! I don't understand it, but taking the battery out made Odin see my phone!
Now onward we go..Back to trusty old XDA! That's when I found the Android toolkit bySkipSoft.. Talk about a phone saver! Got my phone hooked up, in download mode, tried a few different things in the Unified Android Toolkit, couldn't download anything since the PC has no internet but I already had stock recovery and stock rom images, and the toolkit told me where to stick em! First I tried to use a few adb commands to try to get the data off the phone I wanted to save, but I finally gave up because adb couldn't see the phone since it couldn't see that USB debugging was active, even though I promised it was..
Before I tried flashing the stock rom I thought I'd flash the recovery since that was the beginning of the problem. About 4 mouse clicks, 30 seconds, and a reboot, my phone was alive again! :victory:
Still on the stock mj9 release, rooted with saferoot, and chugging along splendidly.. I may just let it sit this way for a while.. Lol!
TLDR: got a used Note 2, rooted it, b0rked it, and fixed it with the help of the awesome devs and members of XDA!
Unfortunately, I didn't keep track of all the threads, devs, and members I looked at and read that helped me solve my conundrum.. However, the main reason I finally registered was so that I could say a great big THANK YOU to the community here.. It's the best! And you came through for me in my hour of need..
Theude
P.s. as I have time over the next few days I'm going to try to find the posts I used for information, and add my thanks there too.. Also will try to post links, but they'll probably be in text not actual links lol..
Related
Hello folks,
Generally loving my Vibrant, of course hungry for Froyo. I have two Vibrants, the first I've been using and have modded it with root and other enhancements. I gave the other phone to a friend as a gift, but when I wanted to root theirs using the same method I've used on multiple occasions, it would NOT boot into the recovery mode. I use the UP + DOWN push, plus the power button. No dice, just get the cheesy "come together" Tmobile screen, I tried up, down, waited for the Samsung to flash twice, no dice. It was not that complicated on my phone and I can continue to do so. I have looked up threads and there is suspicion that T Mobile disabled this on later vesrions? This version was shipped to me slightly after my own, within a week or so.
It would be disheartening if I couldn't root and make his phone more efficient to deal with the battery hog issues as well as other enhancments. Maybe I'm doing it wrong but I've treid multiple combinations and never get into the utility/recovery screen.
Any thoughts on this? I tried rooting before that with the Ryan one click lag fix, and it seemed to indicate it was done,b ut then Iwhen I opened ROM manager, it said it was not rooted yet. Then when I tried the one click app fix again, it mentioned it couldn't because soemthing about the SD card mounting,etc. I could put the stock PIT file on it via ODIN could I not? But I dont' want to go to all that hassle if it's something else. Is there a another app solution that can root for you? I can mount and drag the update zip there, but can't get tot he screen to reinstall packages.
Hopefully TMobile isn't stripping this down so we can't customize and it's something else but I'm trying all combinations short of doing the hokey pokey.
Thanks in advance!
Kelly
Samsung Vibrant
Apparently either Samsung or Tmobile are having the option disabled via the normal ways to get into recovery. There are numerous other threads regarding this throughout the forums detailing other peoples experiences regarding this.
Take a look here for one:
http://forum.xda-developers.com/showthread.php?t=771247
Join the club. I'm on my third vibrant with this same issue. I am returning it this week for a refund. My first....and last samsung phone.
thank you guys, I was afraid of that. one of the phones greatest assets was it's hackability. Froyo had better do something with battery consumption, speed, etc, or this phone will be a great screen and not much more. boo to hardware lockdowns! let the hackers hack and if you want to void the warranty, do it. I'll see about this ADB mode, I'm wondering if someone can create an app that would successfully root so ROM manager will work. I wonder why the one click fix lag app, which supposedly roots, did not. It seems like an overall lock down on this access?
At any rate, I'll try the other options but it's looking like more and more, my buddy will be a slave to Samsung release timeframe, and thats assuming froyo and updates will fix significant bugs and improve battery life.
thanks again guys! I'll keep trying.
And what about the download mode, can you get in it?
not sure, you mean the little digging android feller? I will try that, I gave the phone to my friend but sent him the page in this thread earlier regarding multiple attempts to get into either / or mode. would that actaully help install the packages aka root the phone? I only used that last time to reinstall via Odin, the T Mobile factory build because it was soft bricked due to a bad lag fix that froze the phone on the Samsung logo.
download mode , can that get it rooted? Or just wanting to know if all hardware access has been blocked?"
not sure, you mean the little digging android feller? I will try that, I gave the phone to my friend but sent him the page in this thread earlier regarding multiple attempts to get into either / or mode. would that actaully help install the packages aka root the phone? I only used that last time to reinstall via Odin, the T Mobile factory build because it was soft bricked due to a bad lag fix that froze the phone on the Samsung logo.
download mode , can that get it rooted? Or just wanting to know if all hardware access has been blocked?
Yeah, that the digging guy. It won't help you to get rooted, but i can't get in download mode, so if you can advise me how can i do that, i appreciate
When I tried to flash cyan fox in cmw it gave me a status 0 error can anyone fix?
We need more info like what did it specifically say. Be as specific as possible
Sent from my Nexus 4 using xda app-developers app
RedJack117 said:
When I tried to flash cyan fox in cmw it gave me a status 0 error can anyone fix?
Click to expand...
Click to collapse
that's "usually" an error you get when the zip is corrupted.
but occasionally you'll get it if your running an i9000 roms (I've had it interchangeably with status 7 before)
I would try re-downloading and flashing the zip again.
if that doesn't work try downloading and flashing fluid kernel
then go to "advanced" and select "reboot recovery".
then try flashing the rom again.
Status 0 error on anything I try to flash using CWM
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
jvrey5 said:
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
I would make sure that you realize that this phone is older and may not be up to the challenge of some of the newer games out there. Based on your PM to me, I understand that this is a secondary phone for you, so if you wanted to play some of the more graphic intensive games, I would do it on your DD.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
After you PM'd me, I started looking around about the Status 0 error being thrown. All signs point to the Updater Script that in the ROMs that you are flashing. My hunch is that once you flashed the CyanAOSP, that changed your build.prop from T959 to i9000 and that is why you are getting the error. I'm pretty sure there is a way to fix it (see below)
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
You should stay as far away from Kies as possible with this specific phone. It had a tendenacy to brick the Vibrants. It worked on my wife's SGS2 back when, but even then I was hesitant to use Kies on it and grinding my teath the whole time.
The zips that you mentioned are probably the standard Root.zip and the CWM zip from s15274n's thread stickied at the top of the Q&A section. Keep those handy.
Click to expand...
Click to collapse
Some answers in-line above.
**********************************
Let's get a few things straight before we start. I am still looking for the Heimdall JFD package, but I think that I know where it is. Pretty sure I put it on one of the external HDDs that I have. I'll try to upload it tonight or tomorrow night, as I am away all weekend with the family. I really don't think that you'll need it, but best to have it and not need it, than need it and not have it.
Theoretically, once you Odin'd back to JFD, I would think that it would've reset your device ID back to T959, but I guess that it didn't. This is what I would do. Odin to stock JFD and then boot it up and let it settle. Root it using the Root.zip that you have already used before. At some point you'll need to pick a ROM to settle on, even if only to get past this hump. (I use Sada's CM11 for my sons' Vibrants. Not that there is anything wrong with any of the others, but I just basically set it and forget it for my boys. I think though that he may have stopped development for it though, so I guess I'll be looking through the dev section myself here in the near future.) Take a look at this thread starting with my post #3 and the response from @nirogu325. I am thinking that if you do the same as he instructed, you will boot past the Status 0 error (since everything that I have seen in searches leads me to believe it is an Updater Script issue). My issue was a Status 7 because of the device ID being changed and the Recovery/Kernel combo weren't letting me flash. I basically opened up the ROM.zip and deleted those line and re-zipped it up and then flashed it (did it all on the phone and no PC, but I'm crazy like that).
Let's let a few of the current device Devs weigh in and see what they think. Already mentioned nirogu325 above, but let's try @epicboy and @dzee206 and @sada23. If they are inclined to come and help, it would be much appreciated.
jvrey5 said:
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
Click to expand...
Click to collapse
As Woody already said, you should odin back to stock 2.1. From there root and go to Jellybean and then KitKat. I'd recommend you stay away from ports that are old and haven't been updated for a while. Not trying to say that the rom I built is the best or anything but so far I haven't ran into any issues and neither has anyone that's used SpiritRom. I say try Spirit Rom 1.5 combined with iyahman's semaphore kernel that was built using linaro 4.9 as it's been stable. If you still run into these issues again I think it may be some software that you use.
The phone only had one major issue before I started messing with it - back & home buttons not working. I honestly can't remember how and what I did to put CyanAOSP on it but I ended up with 2 issues after putting it on. Only the Menu button works (eventhough all 4 lights up) and the USB seems to be grounded. I managed to work with it the past year up until I Odin-ed it back to JFD. When the phone is off and battery still has charge, the loading button would come up followed by the empty batt image at the background. This will loop until the batt dies. The only way to turn it on is by connecting the USB to a power source. Accessing download is easier because all I needed to do is remove batt then press and hold the vol up & down before putting the batt back in. Getting into recovery is a bit trickier. You'll need to wait until you actually see the phone charging before doing the 3-button combo.
Last Saturday, my daughter had a school event and I brought this along because it took better pictures than my S3 knock-off. During the parade, after shooting a video, it would automatically take me to the preview. Since, both back and home buttons were not working, I was stuck. Only option was to reboot it. What makes it interesting is that there is no reboot option on the JFD. It was a good thing that I had my power bank with me. I really did not want to constantly reboot it so I thought of installing one of those virtual button apps. I managed to install ToucherPRO before their presentation which made it much easier. To my surprise, it somehow revived the back button on the device itself - I noticed it when I got home that night to transfer the photos and vids.
I mentioned this so that you guys will have an idea on what I need to go through to get it fixed - somewhat, at least to a more tolerable state. (you won't believe it but the tips of my fingers hurt due to the number of times I have to go into recovery or download)
@Woody
Woody said:
I would make sure that you realize that this phone is older and may not be up to the challenge of some of the newer games out there. Based on your PM to me, I understand that this is a secondary phone for you, so if you wanted to play some of the more graphic intensive games, I would do it on your DD.
Click to expand...
Click to collapse
Yup. I actually find it both weird and interesting - which games work and how they work.
Woody said:
You should stay as far away from Kies as possible with this specific phone. It had a tendenacy to brick the Vibrants. It worked on my wife's SGS2 back when, but even then I was hesitant to use Kies on it and grinding my teath the whole time.
Click to expand...
Click to collapse
Remember I mentioned my hesitation using Heimdall and Bay_wolf's AIO toolkit regarding hijacking drivers and stuff, Kies on this PC is now useless. It won't even recognize the phone after I tried the toolkit - which is good, I guess.
Woody said:
... Take a look at this thread starting with my post #3 and the response from @nirogu325. I am thinking that if you do the same as he instructed, you will boot past the Status 0 error (since everything that I have seen in searches leads me to believe it is an Updater Script issue). ...
Click to expand...
Click to collapse
I read about this when I started going back through the threads. As you mentioned, this is an old phone. Old phone = old threads. What I do is I read everything on page 1 then skip over to the last page, going back. Seems to be more effective specially for DL links.
I was actually reserving this one as part of my 'last option' fix. From experience, editing scripts is far more dangerous than flashing a 'working' one. I managed to root my other DD this way, but went downhill from there - ended up bricking it 3 times.
Anyway, I think I got it - or at least, the correct way of doing it. It took me 3 days....
After day 1, I ended up with 8 update.zips (7 CWM and one ROOT) and at least 2 copies of ROMS, GAPPS, MODEMS, and KERNELS on my SD card - only the update.zips worked, the rest either gave me status 0 or leave me with the 'Vibrant Samsung' bootloop. I had some progress on DAY 2. I read something like what epicboy said:
epicboy said:
As Woody already said, you should odin back to stock 2.1. From there root and go to Jellybean and then KitKat. I'd recommend you stay away from ports that are old and haven't been updated for a while. Not trying to say that the rom I built is the best or anything but so far I haven't ran into any issues and neither has anyone that's used SpiritRom. I say try Spirit Rom 1.5 combined with iyahman's semaphore kernel that was built using linaro 4.9 as it's been stable. If you still run into these issues again I think it may be some software that you use.
Click to expand...
Click to collapse
I tried several JB ROMS listed on the Bible but, the problem was, I can't get into recovery - it was all 'blurry'. When I tried a different JB ROM, it also worked but was still 'blurry' during start up and on recovery. That's when I remembered Woody's post regarding rainbows and bootloaders.
DAY 3: For some reason, everything was flawless. I was able to install JB then KK. EFFORTLESSLY, if I may add.
@epicboy
I'm planning to spend a couple of days more on this Vibrant before I mess with my other phone - a knock-off SGS3. I was drawn to L-Droid because the screenshots and contents of page 1 of their thread was specifically for the T959 and not the I9000. I know it's not really a big deal because the ROM will work and changing the build.prop for 'cosmetic purposes is easy. What really concerns me is the camera. Sadly, the T959 only has only one camera and if the camera app that you're using (stock or otherwise) has a feature to switch from back-to-front and you accidentally press that, it messes it up to the point that you can't use it anymore. I have downloaded the ROM and will try it out in a couple of days. Will send you a PM or reply on the thread regarding my feedback. I've flashed it several times but really haven't been able to do it flawlessly like in DAY 3 - which I find really weird.
Tnx peeps!
Hey, so I've looked through these forums, as well as google search, with every combination of words i could think of to address my issue, and so far nothing has worked. So im posting here, hoping y'all can help me.
My phone is the Lg optimus L9 p769 running FW v20h. I had it rooted, bootstrapped cwm recovery is installed and still accessible. Unfortunately for me, i had disabled usb debugging off. Cant remember why, but I did.
I was browsing around for build.prop tweaks, found a good list, and implemented a few. After reboot, everything was going smoothly, hell, faster and smoother than before, which i assume came from tweaking the build.prop. At that point, i chose to implement 1 more and be done. So i added the line and rebooted my phone. SOFT BRICK!!!!!
Now, as i said, ive done quite a bit of searching for a fix, including the offline fix and basic LG Support Tool restoration, but nothing is working. Offline fix says my phone is not connected. Online recovery says im already at the most recent FW available. Ive tried fastboot, but installing the u boot and x loader wont work. CMD doesnt recognize my phone when i try anything adb related (obviously, because usb debugging isnt enabled), nor does it recognize my phone as a fastboot device even with the phone displaying the mirrored logo and says fastboot v0.5 in the top right corner. Also, the bootstrap CWM wont mount my external SD, which has my build.prop backup on it.
So, basically, that what I've read into. A wall, so to speak. As a side note, my wife has the same phone with an unmodified build.prop. in fact, the only thing that i have done to hers is root it with the LGpwn app.
Now, is there anything i can do with this, other than throwing it against the pavement outside? While i think I'd get a sick satisfaction from that, it hardly solves my problem. Also, i called LG directly, but they won't help me at all without payment. Even with their CS rep saying it was their fault (because, of course, I'm not dumb enough to tell them I broke it by messing with the build.prop). However, the slight bit they did do remotely through the laptop had them going through the LG Service Tool.
Anyway, that's about it. It really is a great phone and i really would like to repair, rather than replace, it, but im stuck. Anyone got any ideas?
Hello,
I had a similar problem, offline method didnt worked for me saying that my device is not connected. Then I faund this tool on forum http://forum.xda-developers.com/showthread.php?t=2797190
Use it with described tutorial (use 3GQCT and DIAG) and you are going to unbrick your phone.
Ok, I'll give it a try when i have access to the neighbors laptop again. I'll post the results here. Fingers crossed, my phone is up and running again soon and I'll be able to post my results from my unbricked phone.
IT WORKED!!!!!
Holy hell, it worked! A week of searching and trying with no success, now my phone is up and running again! Thank you sooooooooooooo much! Can i get a solved tag?
You're welcome. I'm glad I could help
Hey lovely ladies and gents,
So here is the situation: I have an LG Optimus l70 MS323, which until yesterday was with a stock ROM. I banged my head against the wall, trying desperately to follow a guide and root it, along with trying to unlock the bootloader until I watched a video (in Spanish. Thank you high school spanish!) which used flashify to flash a CWM and boot to the custom recovery. I loved it, since that meant that I would be able to finally flash an official Cyanogenmod OS. The first ROM that I flashed was cm-13.0-20160121-NIGHTLY-w5.zip, which worked and made me feel SO HAPPY (I almost yelled Eurika for the sake of historical comedy). I then went ahead and installed an Superuser-SU binary update through the CWM recovery because I wanted to keep on having root. Then I installed a nano gapps package for ARM, Android 6.0 with some minor complications (mostly the "Setup Wizard" crashing every 2 seconds). I rewiped and reinstalled Cyanogenmod through CWM, flashed gapps on the same go, and made a little backup through the recovery menu. I booted up successfully to be met with that buttery-smooth GUI of Marshmallow (ugh, so good.) I decided to go ahead and fetch some apps from the Play Store, such as Messenger and ROM manager. I saw that the Cyanogenmod Update Center had pushed out a notification that the newest nightly snapshot is already downloaded and decided "Meh. What new features have been added? Let's reboot and reinstall." At that point it was 4:40am (keep in mind that I've been trying to get the goddamn phone to cooperate since ~10pm) and I noticed that the boot sequence takes up a lot longer and told myself "It's probably taking a bit longer than usual, it's normal." I put the phone next to my head, hoping that it's going to be ready to use in the morning.
Fast forward to 8:07 am. Bootloader is still going, phone is so hot it can cook an egg.
GNAAAAAAAAAAAAAAAAAAAHHHH. WHY YOU GOTTA DO DIS TO ME PHONE?!??! WHY!?!
SO, the CURRENT situation:
1. Whenever I press the power button, it starts off normally. According to my definition of bootloop, it's stuck in a bootloop.
After hours of staring that goddamn cyanogenmod mascot do you realize that it's going to boot itself into the booting oblivion.
2. I don't have access to CWM. I have tried holding down the power buttons with godknowswhat combinations (I like to call them the Naruto Jutsu of pure despair). Maybe I should hold the buttons for 2 milliseconds longer and it might work. *Sigh*
3. I don't think that I can use fastbood or adb. My computer doesn't see the phone. (GNAAHHAHASDJFLSKDHFSLJHLKJ.)
4. I am totally clueless about what I should do or try. I've basically softbricked my phone and don't know how to unbrick it.
So, now that you see that saying that I'm frustrated is truly an understatement, what do you suggest I do?
In advance, I'd like to thank you SO MUCH for even giving a sh!t about my problem.
Other misc info: I have a 32GB SD card on which I have all the different tools I have used throughout this journey.
I am willing to have it back on stock ROM. My biggest goal is to somehow boot into CWM recovery. From there on, I will be able to deal with it. Until I come back to this forum, begging for mercy.
Have u tried using LG suite or LGUP u need to go to LG 's firmware page I'm not sure about this phone but it worked w my k7 about 100 times also helped unlock it. Check out the LG k7 forum lots of guys on there that use the lgup program and can help
Hi guys. This is the first time I've asked for help here. I have been flashing custom roms for several years now, and go figure, the one device I would be unable to recover is my own beloved Galaxy Tab S .
WiFi 16gb SM-T700.
I have flashed this dozens of times since in the last three years, this issue is TOUGH.
Here is what happened.
Tried to gain root with Kingroot ( First time trying that one. :/ )
Then i pushed TWRP 3.1.* through Odin
Flashed AICP 7.1.2 / GAPPS
Success
Booted the tablet. Play Store worked. Everything worked. I had root. I downloaded a few of my favorite apps and then restarted into recovery to make a backup.
TWRP was asking me something it never did before, something installing the Official App,..I swiped??
Anyways, I never got the backup. Here is where I'm stuck.
When I turn the tablet on, it says "Can't do normal boot, Kernal Length" and shuts off when I let go. I cannot boot into recovery from any method. The OS will not load. I have access to download mode, but absolutely nothing will go through in Odin. I have tried 6 or 7 different versions of Odin/ both with the single AP file and all four separate (BL, AP, CSC, blah) I have tried repairing the bootloader, reinstalling a recovery, new roms, PIT files, nothing at all will PASS in odin. Samsung Kies won't see the device in DL mode. I even donated to the UNIFIED Android Toolkit, which did Sh**. The PRO version. I have spent at least two entire days worth of time and this is beyond me. PLEASE HELP ME!! I can't get it. I paid a pretty penny for this the day it came out, and it doesn't have a scratch on it and I love and care for my devices and respect the software and the dedicated work I see all of you put into this community which makes it easy for people like me. Thank You.
Odin acknowledges it, and I have download mode, and i'm out of ideas.
Does anybody have a good one I can try?
(I'm wrong, I can't help)