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

Root thoughts and obsevations on recovery

johnnyl1111

Android Expert
Feb 8, 2012
1,497
545
texas
i noticed that if you kdz to ver c firmware, and then flash a loki recovery and ver f aboot, you can't get into recovery at all. i was thinking that aboot controlled getting into recovery but evidently i was wrong because it doesn't matter what ver aboot or kernel or recovery you use. you still can't get into recovery. so evidently some other partition controls the key combo to get into recovery. because i still have to do the back and home combo to get to recovery but it then freezes on lg logo instead of going to recovery even with f aboot. before flashing the custom recovery i flashed just f aboot and i still had to do the back and home combo instead of volume down and power. so i don't think aboot is the partition causing the data wipe in loki recovery. since the spirit is so close to the motion in hardware, maybe if i figure out which partition causes this, we can use the partition from the spirit to fix recovery since recovery works on spirit. just a thought.
 
Im not going to pretend this is my expertise.. I don't know if this has anything at all to do with recovery but I did notice that if you only rename your boot animation to .bak and not disable it then reboot you'll have a built in animation this stays the same whether on stock or cm.. So the rom has nothing to do with it.. It's pre-written on some other partition which I haven't been able to find.. Maybe that's where the reset partition lays too.. Like I said I really don't know much about that part of the phone though so this is just a thought..

Let me add that I did this on F so I'm not sure if it's the same on all firmwares..
 
Upvote 0
When using the SRM firmware, aboot is the preferred way of booting Linux. It supports:


  • direct booting from various filesystems (ext2, ISO9660, and UFS, the DEC Unix filesystem)
  • listing directories and following symbolic links on ext2 (version 0.6 and later)
  • booting of executable object files (both ELF and ECOFF)
  • booting compressed kernels
  • network booting (using bootp)
  • partition tables in DEC Unix format (which is compatible with BSD Unix partition tables)
  • interactive booting and default configurations for SRM consoles that cannot pass long option strings
  • load initrd images to load modules at boot time (0.7 and later)
The aboot Loader


be funny if it was on a hidden directory or possibly another partition, android phones always reminded me of using sometype of LVM hdd setup, it could just be a bunch of symlinks,.... two different bootloaders ;o


these phones have like 7 partitions I bet
 
Upvote 0
Swain do you still have the broken motion and can you see the screen?


there's a small java program some guy wrote a while ago called droid@screen

it just use to be a standalone .jar which was really convienent, I guess it kinda got blown up these past 2 years or so with more features-- he has his own website now lol

Installation | Droid@Screen

as long as the phone has usb debugging on you can display it on your monitor via usb.

it's pretty good I used it on my old Samsung galaxy when its screen was busted --I cant remember but I think it only displays while in userland after boot
 
Upvote 0
i'm going to unbrick to ver f and copy all the partitions then unbrick to ver c and flash each partition one by one till i find the one that makes it go to factory reset by just volume down and power. then i MIGHT try flashing the spirit version of that partiton to the motion. and see if i can get custom recoveries to work on the motion without wiping /data.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones