ARCHIVED: [DEAD ROM] ThundeROM V1.8.3 4/5/2011

Status
Not open for further replies.
U do it the same was as on the pc... its an emulator. I personally dont mind the bs update nag. I told it to instal and it failed and hasnt come bak yet. Oh and mad props on the rom. Epic rom.
 
So just to be sure....even though we are getting the nag for the system update, we should not do it until you guys update this rom?

And will the above fix (for stopping the nag from popping up) work without killing my battery?

One last question (getting them all out while I have the chance) at first when I flashed this rom my battery was doing awesome but in the past several weeks it seems to get worse....do you suggest putting the thundeRom kernal on or is that what I already have when I downloaded the rom to my sd card and booted from it?

I guess I'm confused what is the difference between the ROM and the Kernal or are they the same?

Thanks...and if I havent mentioned it awesome ROM.

Im getting the update to but keep hitting install later until I get a definitive solution. But as far as your last question goes my phone was experiencing the same issue I solved this by redownloading and re-flashing thunderom 1.6.2 and nowt my battery life is alot better than it was.

I would give that a shot.


Sent from my LS670 using Tapatalk
 
How do I do the fixes from Terminal Emulator on my phone? I cannot connect to PC to do these changes.
Here is what I did from terminal emulator...

su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mv /system/etc/security/otacerts.zip /system/etc/security/otacerts.zip.bak
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system

Then I cleared the sprint alerts and rebooted. I haven't had an alert since. To clarify I rooted with z4root and am running ThundeRom 1.6.2

Hope this helps!
 
Hello.

I was wondering if anyone has tried this in ThundeRom? If so, does it make a difference? Either good...or bad? I'm interested in hearing some feedback on the benefits or disadvantages.

Thanks everyone.
yes i have. i wouldnt suggest you try it. i dont have proof that it caused all the problems im having as i am just now going to switch, or anyway to get proof, but while i was using it, many of the native android apps would slow down extremely and be very buggy, and the screen absolutely refused to rotate in any application......
 
@ Everyone

Sorry,must of forgot to change up that so ota's wouldn't bug you. In the meantime you can do the following in a terminal(command prompt) you will probably still get a notification but even if the update downloads it will not install.

Code:
adb remount

Code:
adb shell

Code:
mv /system/etc/security/otacerts.zip  /system/etc/security/otacerts.zip.bak

If you want to double check that it worked run this command after

Code:
ls /system/etc/security

It should show

otacerts.zip.bak

instead of

otacerts.zip

I'm getting "adb: not found"..... What am I doing wrong?
 
I'm getting "adb: not found"..... What am I doing wrong?

on a mac? if so, type "./adb" instead of just "adb". otherwise, make sure you're in the folder where the adb command is located. probably in the tools or platform-tools folder of all the files you downloaded for the sdk. just type "cd" and the path to that folder. should work then.

also, if you're on pc, you're gonna have to download the drivers for the phone. i think you can get them off lg's site. mac's already have the drivers built in, so you don't have to do anything beyond downloading the sdk (which you'd have to do in either case anyway..)
 
I was using terminal emulator.... Will that not work?

if that's the case, then you don't need to do adb at all.. that's just the computer-side command to send further commands directly to the phone. so you should be able to just run 'mv /...." (whatever the actual command is) without doing adb at all. just be sure to type "su" at the start to get root permissions within the terminal. then reboot once you're done.

EDIT: You might be better off just flashing one of the updated buildprops from the legorom thread. Pretty sure it does the same thing, but probably a bit easier to just flash a zip than to type these commands. either way should work, though..
 
if that's the case, then you don't need to do adb at all.. that's just the computer-side command to send further commands directly to the phone. so you should be able to just run 'mv /...." (whatever the actual command is) without doing adb at all. just be sure to type "su" at the start to get root permissions within the terminal. then reboot once you're done.

EDIT: You might be better off just flashing one of the updated buildprops from the legorom thread. Pretty sure it does the same thing, but probably a bit easier to just flash a zip than to type these commands. either way should work, though..

you might find mv isn't mapped... (not sure if the guys did that or not)... plan B is to use busybox directly (eg "busybox cp file dest" or "busybox mv file dest")
 
OTA Update ls670zvc

Hi, got a message of an ota update availble for my phone. Ofcourse I did not do it. Will you be doing an update for the rom or do we have to revert phone back to stock and perform update then reroot? Thanks for your help.
 
Got the message to update my phone too. I must have hit "more info" because my only option was to restart and install. Been trying to read the threads to see how I can avoid installing and when I connected to my laptop, the phone froze. Was unable to do anything. I dreaded having to do a battery pull for fear of it installing the update.

So I did the battery pull and booted into custom recovery and let it sit there LOL I gave up reading what I could do to prevent the update from installing since it's almost 3am, so I rebooted the phone and just hoped for the best. It never did update and I'm still on TR 1.6.2 :D

Have yet to see the update notification again. Maybe I got lucky?
 

@Everyone


First, i will post a little update.zip for everyone to flash that will replace the build.props and rename the otacerts.zip for everyone.The reason i posted the command is that's the best way to avoid the ota from just installing without you know or someone accidentally installing the update.

Now to address the questions about the update. As everyone can see by just looking around the forum that this update is not just one of those that you can apply and jump right back to root. It's being worked on by several people. At this time i would say it's best for everyone to sit back relax and enjoy others taking the risk of figuring out the best way possible for everyone to get the update.The reason behind why we can't just work in the files and post a update is there is a new radio in the update this radio is not that much of a improvement it's a whole 3kbs bigger then the radio we currently have. We have to figure out the best way for everyone to get that radio you have to have it or you will get error's.The problem with that is none of the custom recovery's will flash a radio.One of them will brick your phone the other will just not write it. Once there is a more sure fire way to go about updating that is safer and easier then we will make sure to let everyone know what they will need to do. I have sacrificed two phones for testing so we are testing everything possible.Thank you to everyone for understanding and hanging in there while everything gets sorted out.

Cheers,
 
Guys preciate the roms/kernals/themes/support/everything else. When I get home this evening you'll be getting a donation from me.

Can't wait to see how you work your magic on incorporating the new update.
 
New Build Props

if that's the case, then you don't need to do adb at all.. that's just the computer-side command to send further commands directly to the phone. so you should be able to just run 'mv /...." (whatever the actual command is) without doing adb at all. just be sure to type "su" at the start to get root permissions within the terminal. then reboot once you're done.

EDIT: You might be better off just flashing one of the updated buildprops from the legorom thread. Pretty sure it does the same thing, but probably a bit easier to just flash a zip than to type these commands. either way should work, though..

And those are located here.
 
Flash the attached zip in recovery to disable OTA's from popping up and being able to install!!!!!!!!!!!!!!!!!!!!

Thanks smccloud and m3rp for testing.
-----------------------------------------------------------------------------
@ ANYBODY!!!

I need one person to download the attached zip and flash it. It will replace you build.prop,all the build.prop's on sd,and rename the ota security check so that it cant install even if it sneaks back in.

One person please post saying "testing" then come back and say if it flashed without issue.Then everyone else can flash and i can add to first post.
There's not really any risk of anything going wrong i just want to double check it flashs without problems. Whoever is nice enough to do this if you have any problems just flash thunder on top,sorry i would but don't have a phone yet.lol
 
Last edited:
Status
Not open for further replies.

Trending Posts

Forum statistics

Threads
957,725
Messages
6,974,204
Members
3,163,891
Latest member
tedswoodworks