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

Root recovery

thevisitor83

thevisitor83

Well-Known Member
lets just stay on this topic togather. we need feed back on recovery,ideas,thoughts,info on who we should contact to get them on this.
come on people.:)
 
thevisitor83 said:
lets just stay on this topic togather. we need feed back on recovery,ideas,thoughts,info on who we should contact to get them on this.
come on people.:)
Click to expand...


Yeah, i can't believe it's taking this long to get a recovery for this phone. I thought PG would've come through by now. I'm thinking of seeing if GNM can bring over AmonRa for us. He works with a lot of LG phones.
 
I've downloaded all the source and i've compiled stuff on linux before, I just don't program in C so it's a little caveman like. I'm trying to compile the recovery image, but I'm guessing that's not enough. I'd have to find some sort of code to make menu options to do stuff.

I've been trying to get this to work as a start (backing up the stock images):

dump_image boot /sdcard/backup/boot.img
dump_image recovery /sdcard/backup/recovery.img

The problem seems to be that this relies on /proc/mtd and that doesn't show anything.
more info on MTD

So perhaps we need to use DD to dump block devices, not sure yet. DD is easy to mess things up badly if you've never used it so be EXTREMELY careful if you decide to try. They call it "Disk Destroyer" for a reason lol...

Here's some documentation on how it's done for MTD devices, however this isn't the case here so only some things are relevant.
 
kanaida said:
I've downloaded all the source and i've compiled stuff on linux before, I just don't program in C so it's a little caveman like. I'm trying to compile the recovery image, but I'm guessing that's not enough. I'd have to find some sort of code to make menu options to do stuff.

I've been trying to get this to work as a start (backing up the stock images):

dump_image boot /sdcard/backup/boot.img
dump_image recovery /sdcard/backup/recovery.img

The problem seems to be that this relies on /proc/mtd and that doesn't show anything.
more info on MTD

So perhaps we need to use DD to dump block devices, not sure yet. DD is easy to mess things up badly if you've never used it so be EXTREMELY careful if you decide to try. They call it "Disk Destroyer" for a reason lol...

Here's some documentation on how it's done for MTD devices, however this isn't the case here so only some things are relevant.
Click to expand...


Are you trying to start from complete scratch or did you pull the src for CWR off of Koush's GitHub?
 
I'm starting from scratch, with the phone source, sdk, documentation, reading forum info, looking at clockwork type stuff, everything. I'm in the education, and environment setup stage. I want to learn how to make one anyways so I don't always have to wait on someone else. I've read hundreds of lines of code all over the place so i'm starting to get pretty familiar with the dark arts of android, and I use linux mint as my production workstation and some of the servers at work so i'm pretty familiar with the native part of linux within android already.

I'd like to see if i can make a bootable sdcard from the google source as a start so I can experiment without flashing anything first. That will let me know if it's set to boot from sdcard by default in the boot order. If that's the case, like my nook color. Then it will be nearly impossible to brick which is good. I theory I could copy the entire phone's OS into a bootable card and run it from there in case of emergencies. Nook color's run honeycomb right off those alone too so i know it's a possibility.
 
Check the xda-developers LG Revolution forums. When this phone came out a member over there requested and received a dump of the phone. Last I heard they were working on porting over the recovery and possibly some ROMs.
 
I tried to manually install fonts today, by just changing the names of the files in system/fonts just by renaming them with root explorer. When i exited the program, the phone froze, i forced shutdown holding the powerbutton, and it broke... into the reboot loop. Strangely, on factory reset, it would give me the setup wizard, and as i selected a language, it would hot reboot. Over and over. Finally, out of shear desparation, i hit the exit button within the three second framework i had before reboot. It halted the loop. Im on my phone now, stock apps running everything. When i plug in the phone, or go to Android market. Everything starts updating and the phone shuts.down. Will help however i can, but im not a programmer. Should i report the phone lost since rotted it and pay the 150 deductible? Or hold out for you guys? Seems stupid when the phones not BRICKED per se, but it is barely usable. Will charge overnight and jump back on here tomorrow. Thanks in advance. If i go for the insurance claim, this phone is up for grabs if anybody can use it for testing.... Peace!
 
aletheus said:
I tried to manually install fonts today, by just changing the names of the files in system/fonts just by renaming them with root explorer. When i exited the program, the phone froze, i forced shutdown holding the powerbutton, and it broke... into the reboot loop. Strangely, on factory reset, it would give me the setup wizard, and as i selected a language, it would hot reboot. Over and over. Finally, out of shear desparation, i hit the exit button within the three second framework i had before reboot. It halted the loop. Im on my phone now, stock apps running everything. When i plug in the phone, or go to Android market. Everything starts updating and the phone shuts.down. Will help however i can, but im not a programmer. Should i report the phone lost since rotted it and pay the 150 deductible? Or hold out for you guys? Seems stupid when the phones not BRICKED per se, but it is barely usable. Will charge overnight and jump back on here tomorrow. Thanks in advance. If i go for the insurance claim, this phone is up for grabs if anybody can use it for testing.... Peace!
Click to expand...

Dibs on the bricked esteem! :) all u should have to do is pull the original files you tampered with and replace them with root explorer. Or push them with adb.
 
redhook said:
Check the xda-developers LG Revolution forums. When this phone came out a member over there requested and received a dump of the phone. Last I heard they were working on porting over the recovery and possibly some ROMs.
Click to expand...

Well the Revo got thier GB update finally. Could this help at all with getting the ball rolling? Here is the link for the GB Revo manual update. (11.6.11)[TOT]ALL LG Revolution VS910 Firmware V4,V6,V7 *Gingerbread* W/ Instructions - xda-developers I hope this means something good.
 
Hey, can you still access ADB? from recovery or otherwise?
you should just be able to use adb shell, then su, then cd /system and rename the files back to what they were


I'm dumping all the partitions with dd one by one to my sdcard as bin files. Gonna take the hex editor to them to figure out why the hell there's about 20 of em.

it's gonna get hardcore lol. Getting warmer..

f280f.jpg
[/url][/IMG]
 
Interesting read in here:

To boot with a host-side kernel image (and rootfs image)
This command allows you to download a kernel image (and optional root filesystem image) and boot the phone with those, instead of using the kernel and rootfs in the boot flash partition. It is very useful while developing a kernel or modifying the rootfs.
fastboot boot <kernel> [ <ramdisk> ]
Ex: fastboot boot linux-2.6/arch/arm/boot/zImage root-image/recovery.img-ramdisk.cpio.gz
Click to expand...

Fastboot

FastBoot Cheat Sheet
 
Aletheus***Something similar to that happened to me within week 2 of having this $350 phone. I began to sweat. I was stuck on a barely lit black screen after rebooting after trying to change font to ICS fonts. I took it to MPCS and told them that this is what I woke up to after charging all night. Since they couldnt do/or see anything on phone, after the LG startup screen, they gave me a new phone.:D
 
jvillejoe said:
No VZW gave them a GB update see here. http://support.verizonwireless.com/pdf/system_update/revolution.pdf

I think they even have a gb rom built from the VZW update. So sense the phones are so much alike couldn't the cwm work or maybe just tweak the one they have and tweak the rom they have to work on our phone:confused: and we have our rom and recovery?:D
Click to expand...


I believe the Rom and recovery are separate. For example on my tablet I have the same recovery on froyo,gingerbread, and honeycomb. So them getting gingerbread has no effect on us getting recovery.
 
One step forward one step back.... I "unrooted" my phone thinking that might help...but i couldnt get the unrooter to work. So i tried it manually. delete superuser.apk from system/apps then delete su from bin and then delete su from another location...in that order. Then, when i tried rerooting.... Root checker says i have root, but all root access programs crash. Im about to see if i can get to root with adb and just see whats out of the ordinary.... Also Downloading stock fonts and replacing them. Considering wiping system/apps and pushing the stock app bundle. If apps have root, do they register in the manifest? If so, could their presence in the manifest and absence in system/apps be causing a problem? Should i post this problem on xda? If so where? Revolution forum? If they have our boot.img, why dont we?
 
The recovery for the revo could be tweaked to work with the esteem if its dev would shared the src ;). but as is it will brick your esteem as the revo uses ext3 and the esteem uses ext4. A few other small differences as well.
 
PlayfulGod said:
The recovery for the revo could be tweaked to work with the esteem if its dev would shared the src ;). but as is it will brick your esteem as the revo uses ext3 and the esteem uses ext4. A few other small differences as well.
Click to expand...


Welcome Back!

Wow the rev still uses ext3? Linux switched to 4 about 2 or more years ago.
 
You must log in or register to reply here.
Back
Top Bottom