So, two nights ago, when I bricked my LG Optimus Regard, I flashed the wrong rom to it. I found the right rom after a day of crawling the LG Website. After flashing the incorrect one, then the right one, I noticed, my Processor is clocked at 1.5Ghz instead of 1.2,
The reason why I am posting this, is to see if there is any demand for an overclock guide for this new device. If there is, I will change this thread to that.
The change appears to not only be stable but permanent
This seems rather interesting, even though i dont have the same phone. Could you post or pm me the method you used and whether it can be modified to be used on other phones?
Sent from my GT-I9100 using xda app-developers app
I dont think it could be utilized on other devices ramnex, the venerability appears in two phones that are almost identical.
You see, the rom I mistakingly flashed to my phone was for the LG-MS770 whereas my phone is the LG-LW770 (Almost exactly the same phone, as such the drivers are the same) LG Released an Update for the MS-770 which either intentionally or unintentionally overclocked the MS-770 from 1.2Ghz to 1.5. When I flashed the MS-770 and then flashed the LW-770 rom the change was kept and everything else works just fine.
I might be able to help you find an exploid that may do the same thing for your GT-I9100?
tlasch said:
So, two nights ago, when I bricked my LG Optimus Regard, I flashed the wrong rom to it. I found the right rom after a day of crawling the LG Website. After flashing the incorrect one, then the right one, I noticed, my Processor is clocked at 1.5Ghz instead of 1.2,
The reason why I am posting this, is to see if there is any demand for an overclock guide for this new device. If there is, I will change this thread to that.
The change appears to not only be stable but permanent
Click to expand...
Click to collapse
cool! Well, write your story, so maybe it could be useful for someone. Write it even if no one asked you to do so... Help people! No need for them asking to you! But be careful, because it seems to me that you only had a bit of luck, and in guides you should never tell to people to flash incorrect rom, because they might end to brick their device...
Part of this exploit is temporarally bricking the device to unbrick it using official LG tools
Related
I'm about to be coming over to the LG Optimus T world here in the next few days. I'm coming from a T-Mobile myTouch 3G 1.2 (the one with the headphone jack). I've been messing with rooting for about 8 months now and have put up two guides in the myTouch section of these forums as well as provide daily help. I've already got rooting and installing a custom recovery on this phone down by reading through the forum and will surely get flash happy with the ROM's over the next few weeks. My question is this: is there anything else I need to know? Such as, are there different radio/bootloader versions for these devices? The myTouch has around 12 different bootloader/radio combinations. Is this the only recovery available? I may have to see if I can get a guy from the myTouch forums to theme it out a little. Either rate. If there's nothing else that I need to know to do, is there anything that should never be done with this phone?
I think Clockwork works, but I haven't tried it yet. I'm afraid of bricking my phone, so I just stick to the recovery you linked to.
Miscellaneous stuff:
- "axis inversion" issues with the touchscreen
- touch screen cpu spike, but already fixed by mik_os (from 100% cpu usage to somewhere less than 30%)
- random sdcard unmounts: haven't had this issue in a long time. this used to be very much talked about a few weeks back.
- there's already a working gingerbread rom (cm7 port) but the gps and camera doesn't work yet. also, ui is a bit slow.
I'll update this when I realize I have forgotten something
is there anything that should never be done with this phone?
Click to expand...
Click to collapse
The only thing I know of is drellisdee's warning of not flashing a radio.img from the recovery
I don't care much for ClockWorkMod so I'll just stick to the one linked. That one is built off of Among Ra's source code ands I'm currently running a themed version of it right now. The SD card issue is going to be annoying but hopefully I won't run into it much.
Sent from my T-Mobile myTouch 3G using Tapatalk
DonJuan692006 said:
I don't care much for ClockWorkMod so I'll just stick to the one linked. That one is built off of Among Ra's source code ands I'm currently running a themed version of it right now. The SD card issue is going to be annoying but hopefully I won't run into it much.
Sent from my T-Mobile myTouch 3G using Tapatalk
Click to expand...
Click to collapse
ClockworkROm has been ported to P500 i have installed it but haven't created any backups or flashed some ROMS
Hi all
I am looking to install CM7 on my phone and have been doing a fair bit of reading before taking the plunge.
I am relatively happy on the steps involved now, the order to do them in and (roughly) how to do them. The only bit which I am a little sketchy on is the RAM issue from unlocking the bootloader.
I am on an Orange UK handset and understand that a side effect of the unlock is ending up with ~300Mb RAM. The details in the fix here don't seem to quite make sense to me.
I guess what I am really asking is, after unlocking the bootloader and installing CM7 will my phone still only register ~300Mb or is that fix just for stock Gingerbread ROMs? The guide refers to Orange FR Gingerbread which I obviously do not want (I am currently running stock 2.2.2 Orange UK firmware).
I apologise as I am sure this has come up before but I want to do this correctly.
Many thanks for any guidance.
surrealjam said:
Hi all
I am looking to install CM7 on my phone and have been doing a fair bit of reading before taking the plunge.
I am relatively happy on the steps involved now, the order to do them in and (roughly) how to do them. The only bit which I am a little sketchy on is the RAM issue from unlocking the bootloader.
I am on an Orange UK handset and understand that a side effect of the unlock is ending up with ~300Mb RAM. The details in the fix here don't seem to quite make sense to me.
I guess what I am really asking is, after unlocking the bootloader and installing CM7 will my phone still only register ~300Mb or is that fix just for stock Gingerbread ROMs? The guide refers to Orange FR Gingerbread which I obviously do not want (I am currently running stock 2.2.2 Orange UK firmware).
I apologise as I am sure this has come up before but I want to do this correctly.
Many thanks for any guidance.
Click to expand...
Click to collapse
I rooted my phone and I never installed the ram fix. I was always sitting on350-400 of ram with like 60 other so apps on there. I installed cm7 and now get 550-600 with the same apps and settings. My phone boots up in 7 seconds top from when you see the bootlogo to the lockscreen. Its so fast
Heres my quad scores oced @1.3
Sent from my MB860 using xda premium
Keep in mind the OP is asking about international Orange versions of the Atrix not USA AT&T, I don't think USA AT&T versions are experiencing this odd RAM problem.
Phalanx7621 said:
Keep in mind the OP is asking about international Orange versions of the Atrix not USA AT&T, I don't think USA AT&T versions are experiencing this odd RAM problem.
Click to expand...
Click to collapse
Ahh good call, I had crap for ram on blur roms lol
Sent from my MB860 using xda premium
Incase anyone else is interested to know, I took the plunge and just went ahead and did it this evening:
1) Unlock bootloader
2) Root phone
3) Installed CM7
After point 1, I only had the ~300Mb available. After point 3, I have the full ~800Mb available...
So, the answer is the RAM restriction is only on Moto ROMs. I presume the obvious answer is this is linked to the kernel so CM7 works just fine.
surrealjam said:
Incase anyone else is interested to know, I took the plunge and just went ahead and did it this evening:
1) Unlock bootloader
2) Root phone
3) Installed CM7
After point 1, I only had the ~300Mb available. After point 3, I have the full ~800Mb available...
So, the answer is the RAM restriction is only on Moto ROMs. I presume the obvious answer is this is linked to the kernel so CM7 works just fine.
Click to expand...
Click to collapse
See. Same thing happened to me lol
Sent from my MB860 using xda premium
Smittyzz said:
See. Same thing happened to me lol
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Cm7 has the ram fix built into the ROM I believe
Sent from my MB860 using xda premium
Alcapone263 said:
Cm7 has the ram fix built into the ROM I believe
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Apparently de-blur ROMs all seem to do that, i'm an international user and flashed Home Base and also the ROM problem is gone and the phone is just saaaaaaaaaa fast!
Only one qualm though, it gets a tad too hot for my liking, next step is to learn more about undervolting to see if i can somehow control the overheating...
crofton said:
Apparently de-blur ROMs all seem to do that, i'm an international user and flashed Home Base and also the ROM problem is gone and the phone is just saaaaaaaaaa fast!
Only one qualm though, it gets a tad too hot for my liking, next step is to learn more about undervolting to see if i can somehow control the overheating...
Click to expand...
Click to collapse
It uses a 1.3 GHz kernel so you should set up profiles to underclock when you don't need all that power
Sent from my MB860 using xda premium
finally found a thread which got some info after searching for a month.i dont own an atrix planning to buy one.i also dont undestand this issue of ram.is it for those who use stock rom.because the fix is using an orangefr.
do other roms contain the fix like cm7.
im planning to use a stock middle east rom
or a custom rom which supports arabic.
its the kernel contained within the CM7 rom, it contains the unified kernel with the ram fix for at&t and international users...
surrealjam said:
Hi all
I am looking to install CM7 on my phone and have been doing a fair bit of reading before taking the plunge.
I am relatively happy on the steps involved now, the order to do them in and (roughly) how to do them. The only bit which I am a little sketchy on is the RAM issue from unlocking the bootloader.
I am on an Orange UK handset and understand that a side effect of the unlock is ending up with ~300Mb RAM. The details in the fix here don't seem to quite make sense to me.
I guess what I am really asking is, after unlocking the bootloader and installing CM7 will my phone still only register ~300Mb or is that fix just for stock Gingerbread ROMs? The guide refers to Orange FR Gingerbread which I obviously do not want (I am currently running stock 2.2.2 Orange UK firmware).
I apologise as I am sure this has come up before but I want to do this correctly.
Many thanks for any guidance.
Click to expand...
Click to collapse
ive had a similar problem after unlocking the bootloader on my tmob uk atrix while still on stock rom. i had ~500 free average before unlocking the bootloaader. after doing the unlock i now have ~100meg free at any time. i tried aliens#4 rom and still encountered this problem
UPDATE
i flashed faux's unified kernal. solved it
ram fix
i got bellgb2.3.6 im d00, everything works great including lapdock
now i have 300mb ram,
did you got any solution?
If I recall correctly, Faux v0.2.3 kernel has the fix built into it.
Sent from my MB860 using XDA App
Not trying to get off topic here but would it be possible with a hack to get all the ram to show up. For example, I want all the ram (1GB) to show up instead of 815MB Available. I understand that the android system allocates ~250MB for the OS but I heard that you can make it so all the ram shows up.
quick question, im running Nottach's wet dream rom with faux's 123 unified 1.3GHz kernal. Im not having any problems with the ram, i get an avg of 500mb. i did have a problem before with was solved with one of faux's kernels. what will happen if i flash the ramfix? nothing or will i get more available?
parkodrive said:
quick question, im running Nottach's wet dream rom with faux's 123 unified 1.3GHz kernal. Im not having any problems with the ram, i get an avg of 500mb. i did have a problem before with was solved with one of faux's kernels. what will happen if i flash the ramfix? nothing or will i get more available?
Click to expand...
Click to collapse
I flashed this ramfix over my wetdream 1.4.4 with the faux gb1.45Ghz kernel and nthing happened i get the same mount of ram i guess it was already built into the kernel
sk8trix said:
I flashed this ramfix over my wetdream 1.4.4 with the faux gb1.45Ghz kernel and nthing happened i get the same mount of ram i guess it was already built into the kernel
Click to expand...
Click to collapse
Thought it might be. I flashed the enhanced stock kernel when i was having ram issues on the Alien rom
Thx so much to the virtuous dev team. My tfp is performing how I like it, smoother and faster. For example, Engadget website loads in ics browser+ faster than my ipad2 (I'm using the performance mode which is at over clock speed of 1.6 ghz). How about that?
Sent from my Transformer Prime TF201 using Tapatalk
Might be off topic, but is there a thread showing exactly how to root and unlock bootloader?
d1ez3 said:
Might be off topic, but is there a thread showing exactly how to root and unlock bootloader?
Click to expand...
Click to collapse
Ask and you shall receive... http://forum.xda-developers.com/showthread.php?t=1427125
d1ez3 said:
Might be off topic, but is there a thread showing exactly how to root and unlock bootloader?
Click to expand...
Click to collapse
Make sure you read thoroughly and know what you are getting yourself into. Not that it is entirely difficult at all, but you would not be the first one to unlock with no idea what they are doing.
Flashed this ROM as well. Running great all around. My first experience with a Virtuous ROM and I am very happy with it. Looking forward to future updates!
I'm running the latest version of this ROM and loving it.
Only.. one bit of feedback for Virtuous (which I've mentioned to Diamondback via IRC) is they need to include a boot image in the next release. This will make switching to other ROMs easier in the longer run. From my understanding, the only reason it was not included is due to lack of proper testing.
Sent from my Transformer Prime TF201 using Tapatalk
Yes. Follow the instructions carefully. The rooting and flashing of the rom went very smoothly. The rom thread has a link to the viper rooting thread too which you have to go through first and it takes care of running the Asus unlock tool.
I've been banging on this rom for several hours now. Even at balanced mode, its still very fast. Seriously a big difference. Web pages just load much more quickly, which was the biggest gripe I had. Now even that department matches my wife's ipad2. I used to hit so many crashes and stalling when there is flash material. Not a problem now. Flash just plays, PERIOD. I feel this rom really let tegra 3 shine. Very very exciting. This just confirms my belief of the potential of tfp and Android. Time to donate
I am holding off on unlocking my bootloader and installing custom ROMs till at least summer when there are plenty of ROMs out (and I have summer breaks). As of now, I am very happy with the stock Prime's performance. Probably the best out-of-the-box Android experiences I have had so far (I have owned a total of 4 Android devices).
I second this, I'm so glad I took the plunge, even though I was skeptical about how unchanged this rom looked from stock. It makes me so excited about what's to come, and just makes the every day operation on the tfp so much more pleasant!
http://forum.xda-developers.com/showthread.php?t=1442441 you need this as well its a perfect theme and awesome boot animation
Waiting
I'm stoked about using it, but I think I'll wait and see if they can come up with a way to unlock the bootloader without voiding warranty. Not a noob, but not a gambler either.
Seems like my GPS is not working like before the unlock. Any chance some tweaking can be done within a rom?
Sent from my SAMSUNG-SGH-I727 using xda premium
The only thing holding me back right now is simply the lack of knowledge regarding bricks. When I modded my Captivate I read for days about the kinds of bricks that can occur and how to avoid the hard bricks along with how to recover from them with loads of stock images. We don't really have that yet here.
hOws the battery life, I'd expect the battery life close to 5 hours if its in 1.6 ghz all the time.
dannb said:
The only thing holding me back right now is simply the lack of knowledge regarding bricks. When I modded my Captivate I read for days about the kinds of bricks that can occur and how to avoid the hard bricks along with how to recover from them with loads of stock images. We don't really have that yet here.
Click to expand...
Click to collapse
Here is a thread with some brick info.
http://forum.xda-developers.com/showthread.php?t=1514088
You're not likely to brick if you follow instructions. Devs who are testing new things out can get bricked. I was testing a kernel flashing method for Diamondback and my device got bricked, but he figured out a new method to unbrick Brick option 3 (in thread)
mtotho said:
Here is a thread with some brick info.
http://forum.xda-developers.com/showthread.php?t=1514088
You're not likely to brick if you follow instructions. Devs who are testing new things out can get bricked. I was testing a kernel flashing method for Diamondback and my device got bricked, but he figured out a new method to unbrick Brick option 3 (in thread)
Click to expand...
Click to collapse
Yeah bricks are certainly possible, but as long as you follow the instructions for flashing the ROM you should be ok. That said between Diamondback's post on fixing/preventing bricks and personal support by him (he's very approachable) you should be ok. I'm on .15 beta 1 of Virtuous and it runs very well.
With the initial sluggishness and then asus locking the bootloader, I almost returned my TFP. Good that asus quickly announced they would unlock the bootloader. Then I knew its a matter of time the TFP will perform well with our talented dev teams. Let's donate
Sent from my PC36100 using Tapatalk
if we have nvflash can't we recover from almost any brick?
Take your time, read directions, and make sure that you put the ROM on your INTERNAL memory root folder and not on the micro SD card. I had no problem doing it. Easiest bootloader unlock yet. I have a HTC EVO3D and it's much more difficult than Virtuous. By doing this it has also fixed my screen flicker when pushing the recent apps button. That was the only real issue(to me) that I was having. Can't wait for more exciting and feature packed ROM's in our future!!! Just my .02
Word. Stellar ROM.
I recently switched from a Droid X (running CM9) to the Rezound, and I am loving it so far. I have read all the stickies on unlocking, rooting, and installing ROMs, and it is very different on this device. I understand the general idea, but I have a few questions...
For one, I am accustomed to being able to SBF back to factory if anything went wrong with my DX. I realize that there is no SBF process for a "bricked" Rezound, and that there are ways to fix your device if something goes wrong. I am wondering if there is a way to actually brick a Rezound beyond repair by just flashing ROMs and kernels. And if this does happen, has anyone had trouble getting a new device from Verizon after using HTCdev to unlock their device? I realize that it may void parts of the warranty, but I was just wondering if anyone has actually been denied a replacement device because of this.
My last question is, does Chrome work on ICS ROMs on the Rezound? I've looked through a lot of threads for the different ROMs in the development section, but I have not even seen it mentioned. On my Tab 10.1 (also CM9) and some other devices I have played with, you could just change the build number in the build.prop to fix Chrome if it didn't work with a ROM. Does this work for the Rezound?
Troider said:
I recently switched from a Droid X (running CM9) to the Rezound, and I am loving it so far. I have read all the stickies on unlocking, rooting, and installing ROMs, and it is very different on this device. I understand the general idea, but I have a few questions...
For one, I am accustomed to being able to SBF back to factory if anything went wrong with my DX. I realize that there is no SBF process for a "bricked" Rezound, and that there are ways to fix your device if something goes wrong. I am wondering if there is a way to actually brick a Rezound beyond repair by just flashing ROMs and kernels. And if this does happen, has anyone had trouble getting a new device from Verizon after using HTCdev to unlock their device? I realize that it may void parts of the warranty, but I was just wondering if anyone has actually been denied a replacement device because of this.
My last question is, does Chrome work on ICS ROMs on the Rezound? I've looked through a lot of threads for the different ROMs in the development section, but I have not even seen it mentioned. On my Tab 10.1 (also CM9) and some other devices I have played with, you could just change the build number in the build.prop to fix Chrome if it didn't work with a ROM. Does this work for the Rezound?
Click to expand...
Click to collapse
Bricking is pretty tough on this phone. I haven't heard of full on bricking yet.
Also haven't heard of a warranty being voided just for flashing ROM's, at least for HTC.
There is a Chrome APK in the Themes forum. Sideload it as the very first thing you do once you flash an ICS rom. After that you are golden.
Good Luck.
Anyone know when ICS is out for Motorola Razr?
What? You aren't going to find to many people in this forum that actually care about an ICS release for the Razr.
http://lmgtfy.com/?q=motorola+razr+ics+release
Kalger said:
Anyone know when ICS is out for Motorola Razr?
Click to expand...
Click to collapse
Try here... http://forum.xda-developers.com/forumdisplay.php?f=1361
Troider said:
I recently switched from a Droid X (running CM9) to the Rezound, and I am loving it so far. I have read all the stickies on unlocking, rooting, and installing ROMs, and it is very different on this device. I understand the general idea, but I have a few questions...
For one, I am accustomed to being able to SBF back to factory if anything went wrong with my DX. I realize that there is no SBF process for a "bricked" Rezound, and that there are ways to fix your device if something goes wrong. I am wondering if there is a way to actually brick a Rezound beyond repair by just flashing ROMs and kernels. And if this does happen, has anyone had trouble getting a new device from Verizon after using HTCdev to unlock their device? I realize that it may void parts of the warranty, but I was just wondering if anyone has actually been denied a replacement device because of this.
My last question is, does Chrome work on ICS ROMs on the Rezound? I've looked through a lot of threads for the different ROMs in the development section, but I have not even seen it mentioned. On my Tab 10.1 (also CM9) and some other devices I have played with, you could just change the build number in the build.prop to fix Chrome if it didn't work with a ROM. Does this work for the Rezound?
Click to expand...
Click to collapse
I am a almost 3 year Motorola user using that root/flashing/sbf process. I haven't went back to unrooting yet on my Rezound, but I can tell you it's a little more difficult to get rooted than the original Motorola Droid and the Motorola Droid X2 (which is what i upgraded from).
First you have unlock the bootloader. I did it the slow way step-by-step through HTCDev.com becuase the noob method wasn't working for me. After you get the files you need from the SDK Android app it's pretty much easy from there to unlock the bastard.
Flashing new roms is pretty similiar, but there's a hitch. Usually when you flash a ROM you have to flash a kernal that is compabitable with the ROM. Which means you have to do it in the bootloader instead of in Recovery. The only time you don't have to do this is when the ROM has a built in kernal (boot.img) and it almost flashes it for you automatically.
I'm very happy with my upgrade from the X2, but then again the original X had a lot more variety as far as development. The X2 wasn't very popular even though for a short while it was the best specced pure 3G device on Verizon when 4G LTE came out.
I've tried a couple ICS ROMs and for the most part they're pretty damn stable with a few bugs in them. Personally I like ROMs very polished with literally almost no bugs so I'm sticking with GB ROMs until something pretty polished comes out. I will be totally happy with my Rezound if we get a full or pretty close to a full AOSP ROM released under Ice Cream Sandwich.
If you have any other questions private message me. I've owned the Rezound for about a week now and have been happy with it.
Chrome shows in the market for ics running rezounds, no need to side load.
Sent from my Rezound using Tapatalk
Hello there to all who have stumbled on to this thread. I know that not many know how to build a custom recovery and many who do are busy. If you could I will at the very least try to reward you somehow. If you need the recovery image since yours is messed up feel free to download. If any other files are needed please ask and I will supply them as soon as possible. Thank you and good luck.
(227)androidfilehost[dot]com/?fid=95864024717067914
Replace (227) with standard www dot
custom recovery would be great
There are many people like myself looking for a custom recovery for the LG vs450pp. These are pretty decent phones and i would like to see a few roms made for it... perhaps a custom viper rom & a kernel retaining the knock-on feature. Paid someone a pack of smokes for this phone and im content with it so far as a stock rooted phone goes but further development would be greatly appreciated.
devonm94 said:
There are many people like myself looking for a custom recovery for the LG vs450pp. These are pretty decent phones and i would like to see a few roms made for it... perhaps a custom viper rom & a kernel retaining the knock-on feature. Paid someone a pack of smokes for this phone and im content with it so far as a stock rooted phone goes but further development would be greatly appreciated.
Click to expand...
Click to collapse
Get the recovery from post #33 in this thread. Start with the first post and read until you get there. Personally tested on both the LS620 and the VS450PP...
A friend is working on a custom ROM, and I hope to test this later tonight or tomorrow. Fingers crossed
fathergweedo said:
Get the recovery from post #33 in this thread. Start with the first post and read until you get there. Personally tested on both the LS620 and the VS450PP...
A friend is working on a custom ROM, and I hope to test this later tonight or tomorrow. Fingers crossed
Click to expand...
Click to collapse
Any update on the custom ROM?
SirDigitalKnight said:
Any update on the custom ROM?
Click to expand...
Click to collapse
I believe stock and debloated stock only so far. Custom recovery has been modified to work from key presses upon boot, but I haven't succeeded on this particular device yet. Look for the LS620 root thread over there.
Sent from my XT907 using Tapatalk 2
fathergweedo said:
I believe stock and debloated stock only so far. Custom recovery has been modified to work from key presses upon boot, but I haven't succeeded on this particular device yet. Look for the LS620 root thread over there.
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Thanks I will check out the LS620 root thread.
The debloated stock rom, does everything still function on the phone with that rom and do you have the link to it so I can give it a try or is it in the LS620 thread?
Thx.
SirDigitalKnight said:
Thanks I will check out the LS620 root thread.
The debloated stock rom, does everything still function on the phone with that rom and do you have the link to it so I can give it a try or is it in the LS620 thread?
Thx.
Click to expand...
Click to collapse
Here's the thread, but please note it is for the Realm (LS620) which is a Boost Mobile (Sprint) device. I've only verified the recovery working on my Exceed 2, but still without access to it via cold booting (button presses). The thread starter (bcrichster) is working with SuperR on modding the boot.img for the VS450PP that I supplied them with.
Once past that hurdle, I'll try the debloated Realm ROM on an Exceed 2. I "had" both devices, but soft bricked my Realm and cannot find the .kdz for this anywhere. Before loss of the Realm, I compared the /system of both and they are nearly identical (other than partition "numbers" as I recall, and several carrier specific apps that aren't needed anyway). At least if I have issues, I'll be able to restore my stock nandroid.
In a nutshell, proceed with caution as this is 'technically' for the Realm and a WIP at that. I'll be back with updated info as things progress. I'm just assisting and testing at this point. I'm about to root a new one later tonight and provide them with some (nearly) virgin images to work with.
Just got a PM that the modded boot.img for the VS450PP may be ready for me to test as early as tonight. If the Exceed 2 is your daily driver, you may want to wait just a bit longer...
fathergweedo said:
Here's the thread, but please note it is for the Realm (LS620) which is a Boost Mobile (Sprint) device. I've only verified the recovery working on my Exceed 2, but still without access to it via cold booting (button presses). The thread starter (bcrichster) is working with SuperR on modding the boot.img for the VS450PP that I supplied them with.
Once past that hurdle, I'll try the debloated Realm ROM on an Exceed 2. I "had" both devices, but soft bricked my Realm and cannot find the .kdz for this anywhere. Before loss of the Realm, I compared the /system of both and they are nearly identical (other than partition "numbers" as I recall, and several carrier specific apps that aren't needed anyway). At least if I have issues, I'll be able to restore my stock nandroid.
In a nutshell, proceed with caution as this is 'technically' for the Realm and a WIP at that. I'll be back with updated info as things progress. I'm just assisting and testing at this point. I'm about to root a new one later tonight and provide them with some (nearly) virgin images to work with.
Just got a PM that the modded boot.img for the VS450PP may be ready for me to test as early as tonight. If the Exceed 2 is your daily driver, you may want to wait just a bit longer...
Click to expand...
Click to collapse
Thank you for the follow up!
I also found that this phone is also just like the LG - L70? here
So it looks like a good chance we will see some ROM soon then?!
I picked up this phone from BB for $15 on sale over the holiday weekend and I had $10 in BB rewards I had to use up before they expired so for $5 plus tax I thought it would be a fun toy to play with and see how it works with my moto 360. And so far I am happy with it. I mounted a 32GB card in it and moved the apps it would let me move to it.
So far the only issue I have with the phone is Bluetooth music payback to my BT speaker. Seems to break up from time to time. Not sure what that is about...
Anyway sounds like you are close to something so I can wait a bit longer before digging into to guts of this device and will just keep testing it out.
I will keep an eye out for updates and let me know if there is anything I can help with... I do have a some virgin phone with only root access now on it and have dropbox access.
Any updates on this? I just got the LG Optimus Exceed 2 phone (lg-vs450pp) for a good price on amazon ($15)! And if I can get something close to stock android on this it would make a wonderful DEV device.
I was able to root it and put twrp on it as per this thread's instructions.
Looking forward to updates!
stipo42 said:
Any updates on this? I just got the LG Optimus Exceed 2 phone (lg-vs450pp) for a good price on amazon ($15)! And if I can get something close to stock android on this it would make a wonderful DEV device.
I was able to root it and put twrp on it as per this thread's instructions.
Looking forward to updates!
Click to expand...
Click to collapse
I just received 2 more from Amazon today (how can you NOT grab these @ $15?), for a grand total of 8 now (actually 7, as my grandson just flipped an untouched one for $40 last night <g>). Working long hours every day thru the end of the year, and spent a bunch of my time recovering, then assisting on the Realm.
No promises, but I intend to do an extreme debloat the Exceed 2, and at least (help) make a nicer stock ROM, with init.d support. Just too little time at this point
As an aside, there is a better recovery available (2.8.6) you may want to look at. Should I succeed in any ROM tweaks, I'll be using this. Unsure if it will actually matter, as I'm not really a "developer" per se'. The latest TWRP I mention gets the file dates right, and that alone (to me) makes it worth installing. I believe he fixed the screen timeout issue on this release too, but haven't verified it yet myself.
I'm playing with 3 different devices at once, and my "old-timers" is adding to my lack of time. Had to unbrick a Moto G last night, and it consumed some 'precious' time. Arrggghh, too many irons in the fire. And I gotta go bowling in a few minutes. FML...
fathergweedo said:
I just received 2 more from Amazon today (how can you NOT grab these @ $15?), for a grand total of 8 now (actually 7, as my grandson just flipped an untouched one for $40 last night <g>). Working long hours every day thru the end of the year, and spent a bunch of my time recovering, then assisting on the Realm.
No promises, but I intend to do an extreme debloat the Exceed 2, and at least (help) make a nicer stock ROM, with init.d support. Just too little time at this point
As an aside, there is a better recovery available (2.8.6) you may want to look at. Should I succeed in any ROM tweaks, I'll be using this. Unsure if it will actually matter, as I'm not really a "developer" per se'. The latest TWRP I mention gets the file dates right, and that alone (to me) makes it worth installing. I believe he fixed the screen timeout issue on this release too, but haven't verified it yet myself.
I'm playing with 3 different devices at once, and my "old-timers" is adding to my lack of time. Had to unbrick a Moto G last night, and it consumed some 'precious' time. Arrggghh, too many irons in the fire. And I gotta go bowling in a few minutes. FML...
Click to expand...
Click to collapse
Awesome, a debloat would be great. I want to tinker with turning this phone into a portable PHP server.
Did anybody ever try this on the LG Exceed 2? Not sure how legit it is.
http://downloads.hostingsharedbox.com/rashed/msm8610/vs450/
Where did you find this?
konradsa said:
Did anybody ever try this on the LG Exceed 2? Not sure how legit it is.
http://downloads.hostingsharedbox.com/rashed/msm8610/vs450/
Click to expand...
Click to collapse
Is this legit?, can someone verify?
I was able to root and install TWRP, supersu. Restarted and the phone is stuck in Verizon logo red screen. I don't remember how to recover (((( Had to reflash again and everything is good now. Phone seems unbrickable.
Any update? And could i use the rom intended for the Realm safely?
Unjust Murder said:
Any update? And could i use the rom intended for the Realm safely?
Click to expand...
Click to collapse
If you are still looking. Let me know.
I recently got my Lg Optimus Exceed 2 (Verizion Pre-Paid) back from repair from Lg. Is there anything I should do to my phone before I load anything on it? Or save anything on it? Thanks in advance for any help.