• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [S-OFF] LazyPanda S-OFF for LTEvo[Locked or Unlocked devices]

Rxpert83 said:
Download links suspended due to soft bricks.

This is part of what we signed up for by running the software. It sucks when bricks happen but you have to know its a possibility when you try it.
Click to expand...

I followed the LazyPanda development thread watching it unfold from various unworking Linux iterations to a working one to the working Windows one.

Don't know if they "fixed it" until broken again or not or the risk remained inherent, but one thing I do applaud is that they suspended the downloads while they sort it out.

pwrmedia, all I can say is glad you got it sorted out - you were lucky at being unlucky.

I'm going to hang a warning in the OP in case the links go live for their testing purposes but still aren't ready for prime time. I think that's fair enough, but I'm open to other suggestions, just let me know.
 
Awe darn, and just when I was about to give this another shot. Although it's probably a good thing it was taken down. Given my lack of skill there's a good chance I could have bricked my phone.
 
I just got home this evening and I couldn't download it. Oh well. They'll put it back up once they fix it. :)

I'm really glad you got another phone pwrmedia, it would have sucked to have a brick on your hands.
 
Was browsing over at the thread and saw where a bunch of folk had problems of one sort or another.

They say they have a fix now using Linux. Haven't updated the tool or explained what went wrong as of yet.

Also, some confusion was encountered by the command to restore S-ON. Someone ran it after running the RUU but he had also, previously, flashed the zip which removed the red writing warning we saw at boot up. This 'borked' his phone as it needs to be run from the stock bootloader, if I read that correctly. In any case, don't issue that command if you have flashed zip that removes the red warning print. Not sure if whatever s-on tools eventually come out will take that into account, so WE better, for ourselves.
 
Regaw told us in the s-on thread over here that if you didn't flash your stock bootloader it would mess you up
 
Glad you got your replacement, but that sucks for BB and HTC. They didn't force you to that, lol. The one click method is perfectly fine and it's safe. IJS
 
Glad you got your replacement, but that sucks for BB and HTC. They didn't force you to that, lol. The one click method is perfectly fine and it's safe. IJS
Click to expand...
It's not unheard of for things to not quite be work right the first time it is released. It's self evident in the first few posts of this thread: whose gonna be the guinea pig?

That's why there's the warning at the top of the page with every rom/kernel/mod you flash... it has the potential to brick your device.

For me, the ability to have complete control of the device I've purchased is worth the gamble, and it worked out for me this time. Next time...who knows? It's easy to realize the part of the OP you're reading is just a warning and skip that part, but its there because this happens.
 
Hey guys I just saw a post over at XDA by globatron, it seems they have found the fix for the bricked devices. See post:
xda-developers - View Single Post - [S-OFF] LazyPanda S-OFF - Sprint HTC EVO 4G LTE

Also the I/O page now has a link for the unbrick tool with instructions and downloads.

Evo 4G LTE Unbricker | Unlimited.IO

Please we still haven't had the time to reserarch and see if it indeed works yet. I'm still reading the 50 something pages over at XDA.


I've read of successes using the unbricker tool. You'll need a native Linux machine, a live CD or a live USB for the unbrick tool.
 
So the download links are live, some reports of success seem to be coming in.

The red block at the top here is going to stay in effect for a little bit, let's be sure we don't have another false start.

We'll also be needing a new thread.

It ought have all step by step instructions along with known prerequisites (wifi must be on?) (a particular root is better?), and known issues and solutions (for sms, etc etc), brick warning with brick recovery, loss of sd card warning , etc etc.

Kanging the LazyPanda site will be erased, but repeating clear warnings about setup are the goal here.

Ok for anyone to begin assembling that here, I can move the pieces into the new thread.

We'll be making sure that we have solid ground this time.
 
EarlyMon said:
So the download links are live, some reports of success seem to be coming in.

The red block at the top here is going to stay in effect for a little bit, let's be sure we don't have another false start.

We'll also be needing a new thread.

It ought have all step by step instructions along with known prerequisites (wifi must be on?) (a particular root is better?), and known issues and solutions (for sms, etc etc), brick warning with brick recovery, loss of sd card warning , etc etc.

Kanging the LazyPanda site will be erased, but repeating clear warnings about setup are the goal here.

Ok for anyone to begin assembling that here, I can move the pieces into the new thread.

We'll be making sure that we have solid ground this time.
Click to expand...
I've been holding off rooting until JoelZ updates his ROM so I don't have to keep setting up my phone the way I want.:p

I guess I should just root and start flashing things, but new rooting techniques keep popping up while I've been waiting.:D
 
nullspace said:
I've been holding off rooting until JoelZ updates his ROM so I don't have to keep setting up my phone the way I want.:p

I guess I should just root and start flashing things, but new rooting techniques keep popping up while I've been waiting.:D
Click to expand...

Well, this is just the s-off, not root.

I suggest using Regaw's one click (see the sticky guide) to get full root.

It's stable, it's complete and it does everything you want and need except for this step. (It will wipe your phone, that's the difference in waiting to do the s-off and piecewise root.)

Anyway, never a need to rush root, there's always time. :)
 
I'm making myself wait at least a few days before I run this. I did the Zedomax root procedure just so I could run root apps and gain access to the system folders so I'm good, but man this is tough putting this off. If possible, I'm going to avoid the htcdev root to keep my phone out of their database but I'll run it if it looks like that is the preferred root method to make this work better.

In the mean time, I'm holding off on too much setup to the phone and installing just the bare minimums to try to keep the phone as clean as possible before the procedure seeing as how right now they don't know exactly what is causing it to work for some and brick for others. I never launched wallet before root and now when I try I get the unsupported device error so hopefully that protected my phone from blowing the wallet up. Looks like I won't be able to set it up anyway so it should stay intact.

By the way, I have to admit that this is the phone htc has been trying to make since they launched the evo series. I'm really enjoying it so far and the list of my favorite devs that are joining the party is going off the chains. Here's looking forward to a good ride!
 
Looks like they are at least making some progress...


globatron at XDA said:
We may possibly have found a mitigating factor that can reduce the likelyhood of getting stuck in download mode. We need to do more work on it but for now we are recommending the following.

1. Stock ROM ( and I mean RUU stock not stock pre-rooted) This doesn not mean custom ROMs cannot work, but there is a specific items that we are looking may or may not affect some custom ROMs.
2. Rooted ( superuser/super su )

Locked/unlocked/relocked and/or use of a custom recovery should not matter.
Click to expand...
 
Well - couldn't stand it any longer so held my breath & took the plunge.
Win 7 64 bit
stock ELTE
Rooted with zedomax.
installed drivers from LazyPanda instructions (checked to make sure no HTC Sync installed)
Backed up onboard sd card
backed up and then erased sd card 2
did NOT turn on wifi (forgot actually)
unzipped FeedPanda-RELEASE-Jewel-WIN to desktop (downloaded June 30th)
right clicked on exe and select run as administrator
took about 5 minutes
voila!
easy as pie.
Restart - hands free activation - pri/prl update. Canceled firmware update.
 
I know that most, if not all things I want to do with my LTEvo can be done with the Regaw One-click method of rooting.

I can't describe the draw, force, pull, etc. that I'm experiencing with completing the lazypanda s-off. I've read every post on the xda thread and it seems there is no rhyme or reason to the soft-bricking.

I did not experience any problems at all with Regaw's root method where other users were having issues. I'm pretty sure those are the same drivers needed for lazypanda s-off.

I'm considering trying on Wednesday (day off). I'm thinking of starting with the stock RUU. I'm currently on MeanROM .06.

Can someone point me in the direction of how to install a RUU? I have no experience with adb/terminal, etc. I've only flashed within recoveries and from bootloader (using xxx.img) I believe.

I other question. If I have to run the unbricker, can someone help me out with the Linux stuff? Never experienced that OS.

Thanks
Skid
 
I did it while on MeanROM.

I thought they fixed the softbricking issue? If it is still occuring there is a fix for the softbrick out. I'll admit I haven't kept up with the thread since I got S-OFF.


If you want to run an RUU you just run it from the computer. If you do this you will lose root and you'll need to do the one-click method because LazyPanda requires root to run.

You may have to be locked to do an RUU, but theres instructions here:
How to Relock the HTC EVO 4G LTE Bootloader - YouTube
 
Skid71 said:
I know that most, if not all things I want to do with my LTEvo can be done with the Regaw One-click method of rooting.

I can't describe the draw, force, pull, etc. that I'm experiencing with completing the lazypanda s-off. I've read every post on the xda thread and it seems there is no rhyme or reason to the soft-bricking.

I did not experience any problems at all with Regaw's root method where other users were having issues. I'm pretty sure those are the same drivers needed for lazypanda s-off.

I'm considering trying on Wednesday (day off). I'm thinking of starting with the stock RUU. I'm currently on MeanROM .06.

Can someone point me in the direction of how to install a RUU? I have no experience with adb/terminal, etc. I've only flashed within recoveries and from bootloader (using xxx.img) I believe.

I other question. If I have to run the unbricker, can someone help me out with the Linux stuff? Never experienced that OS.

Thanks
Skid
Click to expand...


I understand completely and am experiencing the same draw to do this. I just got my phone last week and if I had gotten it near launch day I would have done the htcdev unlock but now that a full s-off solution is here I'd rather do it this way before I do any updating at all and do it right from the start.

I've also been reading until I'm blue in the face and there are a few hints from those that bricked at first and kept trying until they finally got it. The last one ended up using a new sd card and finally got it to work. Another found out his worked when wifi was turned on, etc. I think my best chance is to use a freshly formatted in the phone backup sd card and then make sure wifi is on, and possibly a factory reset. The unbrick seems easy enough to do and I haven't heard one person have it not work yet once they figured out their way around ubuntu.

Speaking of ubuntu, I did get mine running off of a flash drive and it seems really solid to me. I tried linux a long time ago and got it working and then bailed on it and never ran it again. This newer version seems a lot more user friendly and I actually like it. I've been trying to use it for everyday stuff just to get used to it a little and get ready for the unbricking process should the need arise.

I got my ubuntu iso from here: Desktop | Ubuntu Be sure to get the 32bit version. They said they made it in the 64bit version but never tested it. All of the test subjects were using the 32bit version and that's good enough for me.

And used this software to make the bootable usb drive and read the iso: http://www.linuxliveusb.com/en/download

I do see they are recommending another program on their website though: Create a USB stick on Windows | Ubuntu and I couldn't tell you what led me to use the one I did but I must have found a guide or something that went that way. Regardless, it worked just fine for me. After setting up the usb I booted from it, selected try ubuntu and it booted right up. I was able to install chrome, run it and import all of my bookmarks into it and it worked great for me.

I'll probably take the plunge tonight, possibly in a few minutes and see how it goes. I don't want to start too late just in case I get the brick so I won't be up all night. I have to work in the morning. :)
 
Keep us posted ovrrdrive and good on ya!

We'd already decided that our new guide for this would include ensuring that a working Linux was available before the s-off attempt rather than waiting until after it's required when more can go wrong (I recently learned that my optical drive had failed in one of my laptops making a live CD worthless, for example).

The latest edition of s-off states clearly that being stuck in Qualcomm Download mode is a condition that could happen, requiring the un-bricking, but that there's no way to determine ahead of time if it will hit or not.

Being prepared - priceless.

It does make me wonder though - I wonder if we ought to recommend running s-off only in Linux, so if trouble occurs, one simply goes over to the next step. Hmmmmmm.
 
Well, that was interesting. :)

I could not get my computer to boot from the usb drive no matter how I formatted it even though it worked fine yesterday. I'll have to figure that one out later. I burned a liveCD and booted into ubuntu and went off to figure out how to run the unbricking tool. For those like me that love Google Chrome, do yourself a favor and just use Firefox like in the video unless you know how to "do" linux. I don't and finally figured out just to use FF and copy everything he did in the video. This worked and I was soon in the right folder and copy/pasting the commands from the webpage.

I will also give another word of advice, use the bathroom, get a drink, turn on the fan and get comfortable before you start because you can't do any of that once you begin. :)

I went through the 11 cycles and sat in amazement at the skill of the guys that wrote this and at the same time wishing that I could actually see what was going on during this whole ordeal. After 11 times I went through the 12th and it was done, the device booted and everything was back up. I went right back to the FeedPanda page and downloaded the linux version and ran it like the unbrick page said to, but rather than going through that and getting s-off failed, it actually worked this time.

I still have to play with it to see what other residual bugs I have but the device apears to be s-off and working fine now.

EarlyMon I think you're right. This should be run in ubuntu. No drivers to worry about and no worries about getting your ubuntu distro to work because you're already in it. I was prepared to do it 4 or 5 times in a row to try to succeed but I got it the first try after the unbrick.

Because of all of the reading i did I actually kind of expected the first brick so I never got worried or scared. It was fun now looking back. I'm glad i went through with it before the hole got patched. :)
 
Ovrrdrive,
Congrats on getting it done. Nice work
My belief in my own use of Linux isn't strong.

If I may ask...
Concerning your SD card you used.
What size, brand? Did you format it with the phone?

Downloaded the RUU... 1.13.xx...
Although I'm not entirely convinced that will make a difference.
I think it will work or it won't. Getting ready to flash MeanROM .7, not sure if I'm going to try the RUU first with the S-Off attempt or not.

Can anyone suggest a tutorial of sorts on Linux for a complete n00b?

Thanks
Skid
 
You must log in or register to reply here.
Back
Top Bottom