Root [BIN] VV5 + CWM - Need testers

kiroshi23 · Apr 19, 2013

PlayfulGod said:
kewl, but I see more of a need for root for vv4/5.

agreed

sammyz · Apr 19, 2013

PlayfulGod said:
kewl, but I see more of a need for root for vv4/5.

This is for VV5.......

CossRooper · Apr 20, 2013

Someone who has another daily use phone should try this!

I'd be down, but I can't afford to brick my daily driver.

Thanks for your work on this Sammy. I understand that this has CWM, but does that mean it has root as well?

sammyz · Apr 20, 2013

CossRooper said:
Someone who has another daily use phone should try this!

I'd be down, but I can't afford to brick my daily driver.

Thanks for your work on this Sammy. I understand that this has CWM, but does that mean it has root as well?

Don't know, ask kanaida, he did more work on it than I did

justenjoy · Apr 20, 2013

CossRooper said:
Someone who has another daily use phone should try this!

I'd be down, but I can't afford to brick my daily driver.

Thanks for your work on this Sammy. I understand that this has CWM, but does that mean it has root as well?

He said that in theory it should have Cwm, so all you would have to do is boot into it and flash the superuser.apk through recovery to get root access. I would try it, but I dont wanna root my daily phone, I dont have a backup or money for one.

kanaida · Apr 20, 2013

kiroshi23 said:
agreed

You already do. As far as I can tell. The su binary should still work and so should the superuser.apk (I've never seen an su binary not work, if it's installed). What we didn't have was a way to get root access (an exploit) to get the binaries in the right folders and with the right permissions.

If my file that injected cwm inside the bin works, and it flashes ok. That means you don't *need* an exploit to get those files in there anymore. just boot into cwm (this has root access built in), take the root zip file and flash it.

I didn't exploit things like other files do, I just completely bypassed their security methods by modifying data during transport from LG -> your phone. The oldschool swapparoo lol

kanaida · Apr 20, 2013

But if you like building stuff

:
https://github.com/git-core/su-binary/wiki

This is an alternative implementation of the su binary for Superuser on Android.
This implementation is compatible with the original su binary but differs in
the following:
o it doesn't use the am command for notifying Superuser.
The old C++ code crafting intent body is used instead. The code supports
Android versions up to ICS inclusive.
o it sets LD_LIBRARY_PATH to the value copied from the parent process
on ICS or higher.
o it is linked dynamically.
o it tracks both su.db and permissions.sqlite databases when checking
whether the caller is allowed to call su. Thus, all Superuser versions are
supported.

The implementation is compatible with Superuser 3.1.3 or less.

kiroshi23 · Apr 20, 2013

kanaida said:
You already do. As far as I can tell. The su binary should still work and so should the superuser.apk (I've never seen an su binary not work, if it's installed). What we didn't have was a way to get root access (an exploit) to get the binaries in the right folders and with the right permissions.

If my file that injected cwm inside the bin works, and it flashes ok. That means you don't *need* an exploit to get those files in there anymore. just boot into cwm (this has root access built in), take the root zip file and flash it.

I didn't exploit things like other files do, I just completely bypassed their security methods by modifying data during transport from LG -> your phone. The oldschool swapparoo lol

i think everyone is just scared to try it. i know i am

kanaida · Apr 20, 2013

I hear ya. Hopefully someone steps up that has this phone just sitting in a drawer or doesn't need it steps up. Honorary astronauts. I just build the ships to get you there man.

kiroshi23 · Apr 20, 2013

i was going to do it but someone said not even the cab vv3 cab bring me back so im on the fence

sammyz · Apr 20, 2013

kiroshi23 said:
i was going to do it but someone said not even the cab vv3 cab bring me back so im on the fence

Yea, I'm saying if this fully flashes and it perma-bricks, you are permanently bricked!

So people who have this phone as daily, DO NOT TRY.

kanaida · Apr 20, 2013

Has any LG Connect ever been actually confirmed fully bricked?
Fully bricked = not being able to hold vol- + vol+, and plug in a usb cable, and not being able to enter recovery mode.

To my knowledge, it would just flash over the same nand if you did say VV3 over top of this after it fails so I don't see how it could permanently brick it, if this method is to unbrick bricked devices...

If you've used linux and dealt with partitions, it just goes something like this:

[DISK]
|-Partition1
|-Partition2
|...etc...

the BIN file is basically the RAW disk image, plus minus maybe a header including the list of specific partitions to overwrite.

It's like using the dd command.
in linux flashing would be:
dd if=MyBinFile of=/dev/mmblk0 etc...
My point is that overwriting the contents shouldn't affect the ability to flash, no matter what you write prior to that.

At worst, maybe it will boot up normally, and cwm won't boot
or you boot into cwm by default accidentally because it was the wrong offset
or it just doesn't boot up and can be flashed back to VV3 etc..

jlede · Apr 20, 2013

sammyz said:
Yea, I'm saying if this fully flashes and it perma-bricks, you are permanently bricked!

So people who have this phone as daily, DO NOT TRY.

To have this brick it has to be hard brick hence the hard as in hardware brick which means no coming back at least not with our tech yet soft brick is a software brick which can in most cases be recovered from

sammyz · Apr 20, 2013

jlede said:
To have this brick it has to be hard brick hence the hard as in hardware brick which means no coming back at least not with our tech yet soft brick is a software brick which can in most cases be recovered from

I'm saying this does have the potential to hard brick. I know the difference between hard brick and soft brick. Please listen to my warnings, you CAN hard brick if this isn't done correctly, it may just soft brick but it also has the potential to hard brick. Understood?

If you really think I'm wrong, go ahead and flash away. You don't have to listen to what I'm saying if you don't want to

But let's be clear here:

I am not responsible to what you do to your device!

jlede · Apr 21, 2013

sammyz said:
I'm saying this does have the potential to hard brick. I know the difference between hard brick and soft brick. Please listen to my warnings, you CAN hard brick if this isn't done correctly, it may just soft brick but it also has the potential to hard brick. Understood?

If you really think I'm wrong, go ahead and flash away. You don't have to listen to what I'm saying if you don't want to

But let's be clear here:

I am not responsible to what you do to your device!

I'm not gonna try due the fact I don't even know the first step to flash it

sammyz · Apr 21, 2013

jlede said:
I'm not gonna try due the fact I don't even know the first step to flash it

Read my Unbrick guide that's stickied.. that's how you flash it.

unicyclist · Apr 28, 2013

kanaida said:
I hear ya. Hopefully someone steps up that has this phone just sitting in a drawer or doesn't need it steps up. Honorary astronauts. I just build the ships to get you there man.

*looks in drawer*

I will be trying this some time this week. Probably Thurs/Fri. (Have a calculus test to study for).

I have to use VM on my Mac, but it worked fine to unbrick my Motion (thanks to Sammyz), so it should work on this.

I will report on or before Saturday night.

Lito007 · Apr 29, 2013

kanaida said:
In theory after flashing, you can boot into CWM, then flash the zip that installs root and superuser.apk (i don't have that zip but i know it's in the forum here somewhere, if u have it please link). Since we have CWM at this point, rooting is trivial. If this works then I can do this for pretty much any new firmware that shows up.

Um, can anyone link us to this mystery zip that flashes root and superuser through recovery real quick?

Lito007 · Apr 29, 2013

Aaaalllright.... decided to just go for it and test it out. A few days back the download from Sammyz wasn't working for me, decided to install Google Chrome and besides from it being a pretty awesome browser, my download finally completed

So i made a backup of my phone real quick (just in case i was actually lucky enough to not get hard bricked), shut down the phone, put it in Emergency Mode, and began with it. So i skipped down to step 11 in the Unbrick/Unroot/Update LG Connect guide since the file was already a KDZ file and wasnt necessary to convert and well.... no luck =/ i get an Update Error guys. I attached a pic and a Log of what happened, but yeah... blah

Oh and since the third file of the four total possible combinations was the only one in KDZ form, i wasn't able to try the others.

On the bright side, phone is still running

i was sweating bullets through out this whole thing.... you guys owe me.... like a lot... haha

justenjoy · Apr 29, 2013

Lito007 said:
Aaaalllright.... decided to just go for it and test it out. A few days back the download from Sammyz wasn't working for me, decided to install Google Chrome and besides from it being a pretty awesome browser, my download finally completed So i made a backup of my phone real quick (just in case i was actually lucky enough to not get hard bricked), shut down the phone, put it in Emergency Mode, and began with it. So i skipped down to step 11 in the Unbrick/Unroot/Update LG Connect guide since the file was already a KDZ file and wasnt necessary to convert and well.... no luck =/ i get an Update Error guys. I attached a pic and a Log of what happened, but yeah... blah

Oh and since the third file of the four total possible combinations was the only one in KDZ form, i wasn't able to try the others.

On the bright side, phone is still running i was sweating bullets through out this whole thing.... you guys owe me.... like a lot... haha

Woo! Brave guy! Thanks for doing it man. As for the error; lets wait till Kanaida or Sammyz sees the post. They would know whats going on there.

sammyz · Apr 29, 2013

Try it again.
If you get error again, unplug phone, pull battery, put in battery, plug in USB, DO NOT DO key combo, try it now.

Spec2nirvash · Apr 29, 2013

Can I ask why we're risking a patio block for a rooted VV5? I'd hate to see somebody kill their phone only to have a 4G fix for CM10 come out the next day LOL. ABSOLUTELY no disrespect or offense intended Kanaida, it just seems like a really big risk for a stock Gingerbread ROM that, IMO is not the best one out of the bunch to begin with.

If we could find some more dev help with Connect's CM10, I have a Connect sitting in my drawer that I would happily loan to a dev and/or maybe collect some donation money from the Connect community for the help, IF we can find somebody that is. I kinda hinted around to BobZhome in the Motion forum, he either didn't see my post or is not interested LOL.... Not gonna PM him either, bad feeling about doing that for some reason

kanaida · Apr 29, 2013

Thanks for being brave and trying it out. It turned out I was right about being able to recover via flash. It's their 'recovery' mode after all

If just anything could perma-brick a device, they would have to dump a bunch of of development devices and it would increase their development costs significantly so I was very confident it wouldn't be the case. If your phone was a pc, this would be the equivalent of flashing a bad ghost image, then recovering by flashing a good ghost image.

It would be different if say maybe you flashed a bad baseband from a different device that took similar commands to operate which could set frequencies that a radio isn't supposed to be able to use for example, but that's not what we're doing here.

Were you able to boot the device afterwards? even a cwm backup might be useful if it managed to flash at least that partition + CWM

Can you please pack some of the other offsets into kdz's. It's why I made 4 different files.

justenjoy · Apr 29, 2013

kanaida said:
Thanks for being brave and trying it out. It turned out I was right about being able to recover via flash. It's their 'recovery' mode after all If just anything could perma-brick a device, they would have to dump a bunch of of development devices and it would increase their development costs significantly so I was very confident it wouldn't be the case. If your phone was a pc, this would be the equivalent of flashing a bad ghost image, then recovering by flashing a good ghost image.

It would be different if say maybe you flashed a bad baseband from a different device that took similar commands to operate which could set frequencies that a radio isn't supposed to be able to use for example, but that's not what we're doing here.

Were you able to boot the device afterwards? even a cwm backup might be useful if it managed to flash at least that partition + CWM

Can you please pack some of the other offsets into kdz's. It's why I made 4 different files.

I looked back, Sammyz said he used uptest to pack it. You didn't get ahold of the program Kanaida? Goodluck!

sammyz · Apr 29, 2013

Spec2nirvash said:
Can I ask why we're risking a patio block for a rooted VV5? I'd hate to see somebody kill their phone only to have a 4G fix for CM10 come out the next day LOL. ABSOLUTELY no disrespect or offense intended Kanaida, it just seems like a really big risk for a stock Gingerbread ROM that, IMO is not the best one out of the bunch to begin with.

If we could find some more dev help with Connect's CM10, I have a Connect sitting in my drawer that I would happily loan to a dev and/or maybe collect some donation money from the Connect community for the help, IF we can find somebody that is. I kinda hinted around to BobZhome in the Motion forum, he either didn't see my post or is not interested LOL.... Not gonna PM him either, bad feeling about doing that for some reason

I think he doesn't have time to dev for phones he doesn't own anymore like he used to

kanaida said:
Thanks for being brave and trying it out. It turned out I was right about being able to recover via flash. It's their 'recovery' mode after all If just anything could perma-brick a device, they would have to dump a bunch of of development devices and it would increase their development costs significantly so I was very confident it wouldn't be the case. If your phone was a pc, this would be the equivalent of flashing a bad ghost image, then recovering by flashing a good ghost image.

I'm telling you, it can perma-brick: I once tried doing something similar with my old Optimus V. It only boots now because it is running optimus U firmware where all the partitions are located in different places than the V firmware. With the V firmware and S firmware it will go into E-mode (Download Mode) but won't boot. With U firmware, it will do everything. This is all because of me trying to insert recovery and it was inserted on wrong partition. My Optimus V will never be a V/S ever again. Just a U.
Only reason he didn't perma-brick is because it didn't want to flash.

I'll download the other ones and repack them later, probably tomorrow after school. Not sure if I'll have time today.

Root [BIN] VV5 + CWM - Need testers

Android Enthusiast

LG Whiz Kid

Newbie

LG Whiz Kid

Well-Known Member

Android Expert

Android Expert

Android Enthusiast

Android Expert

Android Enthusiast

LG Whiz Kid

Android Expert

Android Expert

LG Whiz Kid

Android Expert

LG Whiz Kid

Well-Known Member

Member

Member

Attachments

Well-Known Member

LG Whiz Kid

Android Expert

Well-Known Member

LG Whiz Kid

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads