I have been trying to root my Samsung Intercept from Virgin Mobile now for a couple of days.
For the record, I am doing this under Linux, I have access to a Windows Machine but it's not mine so I do this purely under Linux.
Here are the steps I took and what happened...
Followed the tutorial on using ADB under linux to root the phone.
I pushed the kernel I wanted to flash to the correct folder, /DATA/LOCAL/TMP and then also uploaded a recovery to the same folder.
I then attempted to ./KERNEL and after it ran it displayed some weird txt in the bottom, nothing that looked good and from what I can remember the txt sad something about the partition, and it just didn't look like a good root.
I then restarted the phone, the FIRST samsung logo shows up with their website address underneath it and it stays there forever! Well at least for 5-10mins and then it goes to a black screen, it does nothing from their, I've left it run overnight on that screen and no go.
NOW, the only thing I can think of to fix my phone. I can still access download mode, and I can still get into the default recovery.. note that I don't have a custom recovery installed, because with the Intercept you need to install a kernel before the recovery.. so I never got that far because my kernel install messed up.
Anyway I tried using the recovery to wipe all data, and also wipe partition cache, still nothing good or different has come from this.
Really hoping someone can point me in the right direction.. I downloaded a STOCK VM kernel that I found on the SDX forums but it just says that the file isn't verified or doesn't match up.. something like that. Either way I have found no good UPDATE.ZIP to help bring my phone back.
I have also tried using the SWUPGRADE method on my friends Windows XP SP3 computer and it just won't recognized my phone. I tried everything, picking new USB ports in the back, I tried unplugging and plugging the USB in and out at different times. All Windows tells me is that "The usb device is not recognized" so I don't know where to go with this.
I really hope someone can help, I only had the phone for 4-5 days and I don't think I have my receipt anymore, hopefully I can find it cause this isn't looking very good.
I'd perfer a way to fix this on Linux but I can use Windows if I have to.
Hopefully someone knows the answer.. I saw a guy on SDX who had the same problem but no one had a fix for him...
i have tried every method known to man to get the recovery tool to work on this phone with revolutionary. its obvious i skipped a process somewhere. how to i kill all of this and start over from the beginning? it shows a full revolutionary command when i go to recovery but it refuses to upload the recovery. this make zero sence. shows the recovery plain as day on the sd but want upload it. i just want to start over from scratch. how do i reverse this?
reversing it should be easy, simply use a recent ota RUU you can probably find one on the dev forums, id link to one but kinda busy, sorry
RUU list
In case you haven't found it...
http://forum.xda-developers.com/showthread.php?t=884060
I hope someone can help me out.. I have read forums for hours and hours.
Been running various roms for years but did something apparently really dumb.. was having trouble with a newer paranoid android release and was changing my twrp... attemped to install cwm instead but that didnt work.
What I am left with now is ONLY the Firmware update mode.. I can't boot to recovery, it does not go to fastboot, and the system does not load.
When I try to load the recovery or system I will just get a 'secure booting error' and black screen following it.
Tried to access the phone through adb, and fastboot from the computer, as well as the lg support program but nothing seems to see it..whether it is in the firmware update mode or if it is at the black screen.
Im pretty much at the end of my options that I can find on the web for help. Have I actually completely bricked it for good?
Download mode is all you need for this http://forum.xda-developers.com/showthread.php?t=2432476
FIXED
Well ill be damned!
I dont think I could have been more bricked than I was.. Butttttttt yes.. download mode is all you need, you were right Art.. after taking a nap at 5am, I finally dawned on the missing piece of information that I didnt see anywhere!!
And this seems to be important so people might really wanna know this!!
HIDDEN FILES AND FOLDERS.
When you are copy and pasting your files into LGMOBILEAX.... MAKE SURE YOU CAN SEE HIDDEN FILES!!!!!!!
Back up and running!!!!!
Now to reinstall paranoid android.. does that make me crazy or just stupid. hahaha.
Elite thanks in advance. No, seriously, thanks. I'm a broke single parent of 2 kids and I realized my phone is about my only guilty pleasure after giving my kids 200% of my time and money. Any help would be appreciated.
I have an LG G2 that I apparently bricked by using an app to "freeze" the latest OTA software update that was pushed to my ATT LG G2 about a month + ago if not slightly longer. I unfroze the process and the update suddenly appeared and said it would reboot the phone and or apply the update it in 30 seconds. I panicked and held the power button in to turn the phone off.
Once the phone was turned back on I was greeted with tiny white text that said "error: Boot certification verify" From here I was unable to get into down load mode, do a hard reset. I was able to see fast boot mode but wasn't sure what to do with it. I was able to see the phone in Windows 7 Pro Sp1 device manager but it was listed as QHSUSB_BULK
After initially freaking out which lasted about 20 mins, I was able to compose myself and start researching my new seemingly serious problem. After a few hours of reading a dozen or so treads / hundreds of replies it seemed I would have to load into Ubuntu and push some files to my LG G2.
I followed this guide - http://forum.xda-developers.com/showthread.php?t=2582142
I was very careful to follow this guide to the letter and everything went as expected the first, 2nd and 3rd time only the results were worse and worse and worse.
The first time I lost fast boot, the 2nd time I lost the boot certification verify error, After the 3rd attempt I get a split second LG Logo and that's it. What did I do during those 3 attempts? The first time, the 4 files and the recovery as directed. The 2nd time, the same files, plus the boot.img and a different recovery. The 3rd time, all the files and yet a different recovery. All the files were pulled from here - http://downloads.codefi.re/autoprime/LG/LG_G2/D800
The other recovery.imgs were for the correct model, just older, newer variants. I was very careful to push the right files to the right partitions.
I can still see the phone via Ubuntu. I'm scared to do anything else along the lines of what I've been doing. In fact I'm lost as to what to do next.
Can anyone here help me push more / different files via Ubuntu that would help bring my phone back to life? I'm completely dead in the water. Or perhaps an exe package / program that can fix my problem? If I sound stupid, it's because this is all new to me.
Thanks in advance, Tom
@rthefley Go back to the autoprime downloads and get the boot, aboot and laf image. Follow the ubuntu guide and flash those images only.
@art
Thank you for taking the time to stop and help me. I greatly appreciate it. I followed your instructions and pushed those 3 files in the order you gave me. Results were the same, nothing. I still get a very brief LG logo but nothing more. I can get into the hard reset but it does nothing as well.
Here are pics I took of the files and directories from my phone connected via usb through Ubuntu. There are a few wrong commands, ignore them. GF was behind me talking and I wasn't focused. I can assure you the proper cmds were given when it counted.
Well ....... I guess I cannot post links ............. so they are edited out. I wanted to show that my highest number was sbe43 so I had to use sbe
Im using the files from the D800 dir which is the ATT LG G2. Or should I tried another directory or files? I can still access the phone via Ubuntu ... THANK GOD
I am still hopeful.
rthefley said:
@art
Thank you for taking the time to stop and help me. I greatly appreciate it. I followed your instructions and pushed those 3 files in the order you gave me. Results were the same, nothing. I still get a very brief LG logo but nothing more. I can get into the hard reset but it does nothing as well.
Here are pics I took of the files and directories from my phone connected via usb through Ubuntu. There are a few wrong commands, ignore them. GF was behind me talking and I wasn't focused. I can assure you the proper cmds were given when it counted.
Well ....... I guess I cannot post links ............. so they are edited out. I wanted to show that my highest number was sbe43 so I had to use sbe
Im using the files from the D800 dir which is the ATT LG G2. Or should I tried another directory or files? I can still access the phone via Ubuntu ... THANK GOD
I am still hopeful.
Click to expand...
Click to collapse
In that case, you should try to push a recovery image, too!
Raymonf said:
In that case, you should try to push a recovery image, too!
Click to expand...
Click to collapse
I've pushed 4 or 5 different recovery images. Should I try something different than the recovery images suggested? I am willing to try anything at this point.
rthefley said:
I've pushed 4 or 5 different recovery images. Should I try something different than the recovery images suggested? I am willing to try anything at this point.
Click to expand...
Click to collapse
Did you lokify them?
Raymonf said:
Did you lokify them?
Click to expand...
Click to collapse
@Raymonf first let me thank you for taking the time to try and help me sort out my ... what I consider a serious issue. Thank you!
I've not read about lokify. So I am not sure what that is but I can absolutely tell you, I'm a great listener. I've spent 12 or 13 hours reading all over the internet, tread after tread and post after post. So I somehow missed the instructions on lokifying the files.
Tom
rthefley said:
@Raymonf first let me thank you for taking the time to try and help me sort out my ... what I consider a serious issue. Thank you!
I've not read about lokify. So I am not sure what that is but I can absolutely tell you, I'm a great listener. I've spent 12 or 13 hours reading all over the internet, tread after tread and post after post. So I somehow missed the instructions on lokifying the files.
Tom
Click to expand...
Click to collapse
Okay, are you now able to go into download mode?
1127
Art Vanderlay said:
Okay, are you now able to go into download mode?
Click to expand...
Click to collapse
No, I've never been able to get into the download mode.
The only way I can access my phone is via Ubuntu. Hard Reset doest work even though I can get to that screen and initiate the process, it doesn't complete.
One other person that's also trying to help me out asked if I've lokify those img files. No I haven't. I've not come across those instructions yet. Would that make a difference?
I also sent you a private PM with links to pics I took of my directory structure from my ATT LG G2 via usb / Ubuntu
rthefley said:
No, I've never been able to get into the download mode.
The only way I can access my phone is via Ubuntu. Hard Reset doest work even though I can get to that screen and initiate the process, it doesn't complete.
One other person that's also trying to help me out asked if I've lokify those img files. No I haven't. I've not come across those instructions yet. Would that make a difference?
I also sent you a private PM with links to pics I took of my directory structure from my ATT LG G2 via usb / Ubuntu
Click to expand...
Click to collapse
Your directories are fine. But if you successfully flashed those 3 partitions, you should Have a working download mode. Make sure you fully power off the phone, you might have to hold the button down for a while.
Art Vanderlay said:
Your directories are fine. But if you successfully flashed those 3 partitions, you should Have a working download mode. Make sure you fully power off the phone, you might have to hold the button down for a while.
Click to expand...
Click to collapse
Yes I'm pretty sure it's completely powered off. I will try again but I've held the power button in for several several seconds and saw the screen go solid black. I've flashed those 3 files just as instructed. Nothing is working sadly. Maybe I am missing some key procedure others take for granted that I just personally do not know about
Is there anything else I could try doing? I'm going in circles here.
Do your results match the one in the forum when you type gdisk -l /dev/sdb in the terminal.? Also is your fastboot still gone.?
Sent from my LG-LS980 using Tapatalk
LilDemon124 said:
Do your results match the one in the forum when you type gdisk -l /dev/sdb in the terminal.? Also is your fastboot still gone.?
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
No they are different, I actually gdisked all of the different letters but I have an sda,c,b and e, I even have have an sde1. All the numbers follow sde however up to 42 or 43. So when I gdisk -l /dev/sde that's when I see all the files.
I've tried to gdisk sdb but I get a mbr / gpt or something error saying something is corrupted so I just leave it alone.
Should I be looking at a different letter then? If so, I can't seem to get into any of them other than the one I mentioned, sde
Guys, I'm now offering a $40 paypal bounty directly to your pocket or a donation to this web site for help allowing me to get back into my phone.
I will try my best to help you. Im at work, but will be home soon so that I can do some snooping.. From what your saying you MIGHT have a corrupt storage OR you might have a corrupt file.
Sent from my LG-LS980 using Tapatalk
Im going to have to work on this a bit later. Worked all day. I'm still here and around just need to get a little sleep before I even think of trying to dive into this again. Thanks.
I guess I got a little too adventurous by trying to format my SD card to have two partitions, and now …
I'm in a really fast boot loop; adb can't seem to interrupt it, and I can't seem to invoke recovery mode properly.
It says "[FACTORY] : detect recovery mode !" … and goes back to rebooting, or if the battery is low enough, it shuts off.
I ran the battery down to no avail.
So, uh, what's next?
Looks like you're in the same boat as I am! I too have a Nook that appears to be bootlooped; it seems like I overwrote the recovery and boot partitions. I've heard rumors of some sort of tool called "SP Flash Tool" or similar, that works before the device has even fully turned on; I might take a look at it if I get time someday. Or maybe you'd like to give it a try?
saagarjha said:
Looks like you're in the same boat as I am! I too have a Nook that appears to be bootlooped; it seems like I overwrote the recovery and boot partitions. I've heard rumors of some sort of tool called "SP Flash Tool" or similar, that works before the device has even fully turned on; I might take a look at it if I get time someday. Or maybe you'd like to give it a try?
Click to expand...
Click to collapse
SP Flash Tool didn't work for me, because I couldn't create a scatter file. I got it replaced by B&N as a hardware failure, and then I tried to make a scatter file with the new Nook. No dice. Which is unfortunate, because I accidentally deleted some of the stock software. So… I'm trying for a second warranty replacement. :-/
Batshua said:
SP Flash Tool didn't work for me, because I couldn't create a scatter file. I got it replaced by B&N as a hardware failure, and then I tried to make a scatter file with the new Nook. No dice./
Click to expand...
Click to collapse
Sorry for my ignorance, but would you mind adding a bit more detail here so I can follow along (I've never used SP Flash Tool)? So you have a copy of SP Flash Tool that works for this device, i.e. recognizes it and everything, and it asked you for a scatter to flash the recovery? Why did creating a scatter file fail?
Also, regarding getting a replacement: did you just send your Nook back to Barnes and Noble and they sent you a new one under warranty, or was there something else wrong with it?