[Q] FRG83D Update Problems - Nexus One Q&A, Help & Troubleshooting

I have a rooted (rage) N1 that I loaded the G2 Launcher2.apk on to. Doing this caused the N1 to fail the update when it tried to apply FRG83D.
Stupidly, I decided that deleting the /system/app/launcher2.apk file was the right idea. And then rebooted.
Now the phone hangs on the boot animation. Attempting to apply with NO launcher2.apk results in the same error.
I have ADB installed, and I can adb shell into the phone and su. I have the old, original N1 launcher backed up on my SD card, but I can't figure out how to:
1) Mount the sdcard while ADB shell'd in from just the boot animation screen so that I can browse the card
2) Move the launcher2.apk backup file into the /system/app directory without getting a "Cross-device link" error when I use mv.
Can someone provide me with the exact commands to get the /sdcard/launcher2 backup/launcher2.apk file on to /system/app while ADB'd in only from the boot animation?
Thanks so much, I'm digging through the forums in the mean time, but it's tricky to track down exactly what to do.

I appear to have fixed everything. I wasn't able to access the SD card through ADB, but I *was* able to mount it using the:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
method.
From there, I copied my backup to my desktop, and I found I was able to ADB push to just the /data/local/tmp directory. Don't know if I could've gone anywhere else, but that worked.
From there, I was about to:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
to mount/make writable the /system/app directory,
and then:
Code:
cat /data/local/tmp/launcher2.apk > /system/app/launcher2.apk
So there's that. All to restore the Launcher to a version that would allow for a somewhat pointless update. Woo!

Related

[Q] I can't boot into recovery!

I rooted using UniversalAndRoot, which worked according to the app. Installed ROM Manager and flashed ClockworkMod Recovery.
This is where I stumble. I've tried selecting Reboot into Recovery, Install from SD, powering up with Vol Down pressed and selecting Recovery. All three boot as far as the X, flash a bit of white at the bottom of the screen then the phone turns off.
Waiting for a minute/pressing buttons or pulling the battery lets me boot back up fine, but I still can't boot into Recovery.
I've tried choosing install AltRecovery and old versions of Clockwork but they both behave the same way.
Any advice guys? Is it because I rooted with UniAndRoot?
top_bunk said:
I rooted using UniversalAndRoot, which worked according to the app. Installed ROM Manager and flashed ClockworkMod Recovery.
This is where I stumble. I've tried selecting Reboot into Recovery, Install from SD, powering up with Vol Down pressed and selecting Recovery. All three boot as far as the X, flash a bit of white at the bottom of the screen then the phone turns off.
Waiting for a minute/pressing buttons or pulling the battery lets me boot back up fine, but I still can't boot into Recovery.
I've tried choosing install AltRecovery and old versions of Clockwork but they both behave the same way.
Any advice guys? Is it because I rooted with UniAndRoot?
Click to expand...
Click to collapse
You probably have SLCD screen. Then you have to use Amon_RA 1.8.0.1 recovery which is only one (as far as i know) intended for SLCD screens.
Ah okay. Is there an easy way for me to flash that? Not really comfortable with the SDK approach...
Thanks for the fast reply btw
If you don't have unlocked bootloader you have to use flash_image binary to flash new recovery because amon_ra 1.8.0.1 recovery don't show up in rom manager.
Download it from here http://cyanogen-files.carneeki.net/flash_image.zip. Put it in root of sdcard as well as 1.8.0.1 img file and in phone terminal type
1) cd /sdcard
2) flash_image recovery 1.8.0.1.img (replace with name of img file)
houmles said:
2) flash_image recovery 1.8.0.1.img (replace with name of img file)
Click to expand...
Click to collapse
I'm getting flash_image: not found
I've double checked the file name is correct
Did you unpack the zip file? There is only one file named exactly "flash_image" so you should not getting not found error if you have that file in root of sdcard and you are at /sdcard in terminal.
Send me output of "ls -la" command from /sdcard.
----rwxr-x system sdcard_rw 17638414 2010-09-10 20:20 gapps-hdpi-20100817-signed.zip
----rwxr-x system sdcard_rw 70864056 2010-09-10 20:22 update-cm-6.0.0-N1-signed.zip
----rwxr-x system sdcard_rw 11818685 2010-09-10 21:05 FRF50-radio-4_06_00_12_7.zip
----rwxr-x system sdcard_rw 4145152 2010-09-10 23:10 recovery.img
----rwxr-x system sdcard_rw 26172 2009-10-03 18:07 flash_image
Try ./flash_image instead of just flash_image.
One more thing: type this as the first command when you enter the Terminal:
su
Then type:
cd /sdcard
./flash_image recovery <insert_recovery_img_name_here>
Jack_R1 said:
Try ./flash_image instead of just flash_image.
One more thing: type this as the first command when you enter the Terminal:
su
Then type:
cd /sdcard
./flash_image recovery <insert_recovery_img_name_here>
Click to expand...
Click to collapse
./flash_image: permission denied
top_bunk said:
./flash_image: permission denied
Click to expand...
Click to collapse
Weird. Try:
1) su
2) cd /sdcard
3) chmod +x flash_image
4) ./flash_image recovery file.img
Well, that's because SD card isn't a good place to put flash_image. Permissions inherited from FAT32 are awkward and aren't changeable. But there's a way around it.
Do the following sequence: run Terminal, enter the following commands:
su
cd /sdcard
cp flash_image /data/local/tmp
chmod 755 /data/local/tmp/flash_image
/data/local/tmp/flash_image <insert_recovery_img_name_here>
houmles said:
3) chmod +x flash_image
Click to expand...
Click to collapse
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.
Jack_R1 said:
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.
Click to expand...
Click to collapse
It didn't work...
Jack_R1 said:
su
cd /sdcard
cp flash_image /data/local/tmp
chmod 755 /data/local/tmp/flash_image
/data/local/tmp/flash_image <insert_recovery_img_name_here>
Click to expand...
Click to collapse
cp: not found
Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.
Jack_R1 said:
Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.
Click to expand...
Click to collapse
I just thought of the same thing
Installing Astro now (it's a new phone no apps!)
Jack_R1 said:
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.
Click to expand...
Click to collapse
ah, didn't know that
Jack_R1 said:
Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.
Click to expand...
Click to collapse
As Jack wrote, you can only copy the file manually with some file explorer.
houmles said:
As Jack wrote, you can only copy the file manually with some file explorer.
Click to expand...
Click to collapse
It won't let me copy it... I've tried Astro and ES.
Lots of complications...
Install Busybox from the Market. Then you'll have "cp" working.
If it still won't work, try "busybox cp" instead.
If you have adb connection you can try this:
unpack zip I sent you and recovery.img to root of c:\ for example .. then:
1) adb push c:\flash_image /data/flash_image
2) adb push c:\recovery.img /data/recovery.img
3) adb shell
4) chmod 755 /data/flash_image
5) /data/flash_image recovery /data/recovery.img
Jack_R1 said:
Lots of complications...
Install Busybox from the Market. Then you'll have "cp" working.
If it still won't work, try "busybox cp" instead.
Click to expand...
Click to collapse
Lots
...but it's done! Thanks a lot for the help guys
I've gotta be up in a few hours so I don't have time to install a ROM and faff about, but hopefully it will be all good from here on in.
Cheers again!!

[Q] Removing Android System Recovery <3e>

I have a verizon Samsung Galaxy tab. I would like to use clockwork recovery. The tab is rooted and I used ROM manager from the marketplace to flash the recovery for a Samsung Tab (Verizon). When I flash the ROM everything is successful. However, when I boot into recovery the Android System Recovery <3e> shell loads which doesn't allow nandroid backups etc... all the neat recovery tools that come with clockwork recovery.
I searched around the forum and saw a thread titled how to replace Android System Recovery with a Custom ROM. These were the commands
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
I went into abd shell I tried the commands but by the time I got to the third line I keep getting permission errors before I can even finish typing the command. I cut and paste the command string from "mount-->" thinking I just wasn't typing fast enough and it still doesn't work.
Is there another way to remove the Android system recovery so that ROM manager will work properly?
Have a look at installing boushh's kernel, it probably going to be the best option around for you.
Sent from my X10i using XDA App
I don't know what that is?
I have also same problem ı tryed many flashes ı coudnt fix it yet.if you allready fixed could you please share thanks.....

CWM 3.0.1.0 issue and solution

make sure to read: http://forum.xda-developers.com/showthread.php?t=971197
the other day I realized that I did not have the OC kernel installed for CM7, so decided it was time to get that on there. I was unable to boot into recovery via ROM Manager or manually (using n+power). ROM manager was telling me 3.0.1.0 was installed, so I was a bit confused about why this was happening. I tried re-installing CWM via adb, that was a no go as well.
I then resorted to irc for help, people explained the proper way to use the key combo and then told me I was lying when I told them I didn't have the "touch the power of reading" splash
video of nook booting: http://www.youtube.com/watch?v=PGScwmoS7HU
so after a bit more poking and questions, found out the splash is within u-boot.bin, and somebody suggested I pull u-boot.bin from stock 1.1 image and push that to /boot.
Code:
1) download and unrar http://www.megaupload.com/?d=D7GFVHCQ
2) adb shell busybox mount / -o rw,remount
3) adb shell busybox mkdir /boot
4) adb shell busybox mv /boot/u-boot.bin /boot/u-book.bin-bak
5) adb push u-boot.bin /boot/u-boot.bin
6) adb shell busybox umount /boot
PROBLEM SOLVED. can boot into CWM after replacing u-boot.bin. I think this was related to attempting to format sdcard within CM7 on nook
So I have the same problem ... "Loading ..." screen and inability to boot into CWM after flashing with ROM Manager.
However your instructions are missing a step. You have the user creating the /boot directory with mkdir but not mounting /boot ... but at the end you have us umount /boot.
I sort of remembered this process from when I installed the HC pre-release, so I found my old bookmark. Following is your instructions with the missing step. Doing this made CWM load for me using power+N
Code:
# download and unrar http://www.megaupload.com/?d=D7GFVHCQ
adb shell busybox mount / -o rw,remount
adb shell busybox mkdir /boot
[i]adb shell mount /dev/block/mmcblk0p1 /boot[/i]
adb shell busybox mv /boot/u-boot.bin /boot/u-boot.bin-bak
adb push u-boot.bin /boot/u-boot.bin
adb shell busybox umount /boot
PS. I'm guessing this still isn't the RIGHT way to fix this issue, as I still can't get the reboot to recovery option working (I'm using CM7 nightly 39). However search function on the forums is offline, I'm very tired, and I'm about to go on a road trip early tomorrow so I'm not going to keep trying to fix it right now. If someone wants to post better info to get CWM 3.0.1.0 and ROM Manager working better for CM7 I'd love to see it. But I got my ALSA update installed so I'm happy for now
I've not been able to use Reboot into Recovery (from holding the power button) for a while now. However, the option from ROM Manager usually works, as does holding the n key while booting.

Deodex failure, need help please.

Hi guys
I'm new to deodexing, following a guide for XUltimate.
I copied my system\app dir to a folder called origi_app, and my system\framework to a folder called origi_frame on my int SD card, then copied these two folders to my PC XUltimate dir.
Ran option 3, then 4, both finished with sucessful.
This gave me two new folders in the XUltimate dir...
done_app & done_frame
I copied these back to my int SD card, then following the guide, ran ADB from cmd prompt..
Typed: ADB Shell
Got a $
Typed: SU
This gave me a Permission Denied ??
So as per the guide, I tried Root Explorer...
Selected All the .apps in done_App, selected copy and then tried to paste into the system\app dir.... this then gave me a failed to copy due to lack of space error and the phone started to vibrate and com.android force closing repeatedly...
Were did I go wrong, why did I get permission denied trying to get the SU cmd?
The full adb guide was as follows:
adb shell
su
stop
mount -o rw,remount /dev/block/mmcblk1p21 /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
mount -o ro,remount /dev/block/mmcblk1p21 /system
reboot
As above, got as far as SU then got permission denied!
So thankfully I did a nandroid backup before and am currently restoring it...
EDIT: My Backup has just finished restoring from CWM... rebooted but it is now on original startup setup and getting force closes for lots of apps???
Had to re add my APN settings to re download MY Backup and am currently restoring apps and data from it now! Fingers crossed. I thought the whole point of a cwm back up was to create an exact image of the whole system, files, date and settings etc?
Well, restored via My Backup, but rom manager and Sky news kept force closing, so wiped the whole thing and flash a custom js8 from from Doc's kitchen... glad I did... just miss the cirlce battery mod I had before.

[Q] /: files lost on reboot?

My phone has been "broken" for the past 7 days, and I'm having troubles uploading any factoryfs.rfs containing the stock /app and /media folders.
A possible workaround would be flashing as much as needed(sh executable; ls, mv etc) to be able to push the rest through adb.
Pushing the /media folder seemed to be working at first. Here's the issue: when I reboot and execute ls trough adb the /media folder is missing.
I also tried replacing the push command with "mkdir test.d". That folder was also lost on reboot.
When creating the "test.d"-folder in /mnt/sdcard it stayed.
Any suggestions are appreciated.
Another quick question that's too simple to find by googling: does your ClockWorkMod show the option to mount /system at recovery boot? I'm a bit worried since mine does. It could be related to the topic.

Categories

Resources