Develop Bugs

ROM Manager Help

I have an issue with ROM Manager not installing the ROM I just downloaded. I downloaded the Fresh 0.2 ROM and after it finished I chose to Backup Existing ROM & Wipe Data and Cache. I hit OK and nothing happens.
Isn't the phone supposed to automatically turn off and do it's thing? If you can help me I'll send a Google Voice invite your way. I'm dying to install this ROM but I want to know what I'm missing. Do I have to flash a new radio with this ROM?
MrDSL.... anyone help

I'm no expert..make sure youre fully rooted and have the latest copy of clockwork installed..
Sent from my EVO via Tapatalk

I have version: 1.8.2.1 DSL. I did the trick mentioned in another thread where you choose and older version and revert back to the current.
My question is when I run ROM Manager and flash is it supposed to automatically restart my device and do the whole process? Do I have to put it in recovery? Thanks.
By the way I payed for the ROM Manager 3.99 since it includes more options.

Do this: http://forum.xda-developers.com/showthread.php?t=699100&highlight=reboot+chmod

I tried that and I'm stuck at the last 2 commands. It's saying:
# chmod 755 reboot
Unable to chmod reboot: No such file or directory
# chmod 755 reboot
Unable to chmod reboot: No such file or directory
# chmod 755 reboot
Unable to chmod reboot: No such file or directory
# chmod 755 /system/bin/reboot
Unable to chmod /system/bin/reboot: Read-only file system
#
The Evo is in debugging mode and plugged in for charging only. What am I doing wrong. I placed the file in the right spot. By the way I used this rooting method:
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/17766-how-full-root-evo-4g-mac.html

The fact that /system is read-only means that you are not doing these commands from within recovery. /system is read-only when the device is booted in to the OS.

Ok so I put it in recovery, plugged it in and opened terminal. Ran commands and everything seemed to go find although it didn't reboot on it's own.
/system/bin # chmod 755 reboot
/system/bin # chmod 755 /system/bin/reboot
/system/bin # exit
new-host:tools gQ$
I chose the option for reboot now and the phone turned back on. Tried to flash rom and still won't reboot on it's own and flash the ROM. What did I do wrong? What is the exit command?

exit just exit's the shell.... I don't know man, looks like you've done it right, maybe it's a problem in ROM Manager? Go grab QuickBoot from the market; That's what I use. When I want to flash, I just hit the 'reboot recovery' option, and then select the ROM from within recovery.
Sorry I can't be more help!
cent

One last question:
When I downloaded the ROM from ROM Manager where did it store it? If I use Quickboot will it see the ROM I already downloaded in ROM Manager? The ROM that I downloaded was Fresh.
Sucks that I paid for it and it doesn't work.

I believe they are stored in /sdcard/clockworkmod/download.
Flipz's recovery will only look in the root of the sdcard for ROM zips. So you'll have to move it to the root.
And actually, now that I think about it, that may be your problem... The method you followed installed Flipz's recovery image, whereas ROM Manager was intended to be used with ClockworkMod's recovery image...
Maybe this thread will address your issue? http://forum.xda-developers.com/showthread.php?t=702214&highlight=clockworkmod

Its hard to say what you did wrong really. ROM Manager does everything for me just by clicking inside the app. The only time I had problems with it was because of the ROM.
It stores the downloaded files on your SDCARD under clockwork/download/
If you can get into recovery then flash from a zip and flash the fresh rom and try rom manager again.
If you're fully rooted you can do this also.
http://forum.xda-developers.com/showthread.php?t=702214
Like I said though the problems you're having could be your rom cause when I had a older rom it didnt work right either..When I switched to the newer ones like fresh it worked fine.
with rom manager i can backup/restore try new roms in a matter of minutes and it does the work for me.

I'm taking the easy way out. I found the ROM, moved it to root of SD, flashed from zip. I'll work on flashing the correct recovery tomorrow. This is crazy but I'll eventually get it down. Thanks for your patience both of you. PM me CENT & DSL I'll send you a Google Voice invite if you need one.

Already have a GV account, but I sincerely appreciate the offer!
This is what it's all about man; Testing, tinkering, and learning!
Personally, for what it's worth, I keep it simple and download the ROMs myself and flash them myself. Let's be honest, flashing ROMs can turn your $500 phone in to a shiny paperweight. I don't like having extra steps, and relying on a middle-man application that could possibly have a bug in it and result in a dead device. I'm not saying it's not a proven reliable method for flashing, I just personally don't want to rely on a piece of software when I can do it myself.
And you're learning, you've asked questions, gotten answers, and now have a rooted device and are already flashing ROMs in a day or two. Keep it up man!

I'm good here to thanks..
I normally download the rom on my own end to avoid any corruption but use the program for everything else.

Just woke up and looked at my Evo. The phone just keeps rebooting at that Sprint 4G animation. It won't boot up at all. I can still get it in Recovery mode. What do I do?

gqstatus0685 said:
Just woke up and looked at my Evo. The phone just keeps rebooting at that Sprint 4G animation. It won't boot up at all. I can still get it in Recovery mode. What do I do?
Click to expand...
Click to collapse
you probably didnt wipe your cache..do that and reflash

Ok weird fix. I'm sorry I'm being such a pest by the way but anyway I fixed it!!
I did some searching on google for infinite reboot because it would keep playing that 4G splash screen over and over. I did a hard reset on the phone and all of a sudden it turned back on and I see my new ROM!!
The crazy part is that after I hard reset I'm able to use Clock recovery and I don't seem to have that bug that everyone else seems to have. I even updated to the new version of fresh's rom from within ROM Manager and it worked perfectly.
Thanks guys for the help.

Remove files from system

I'm trying to remove some preinstalled apps from /system/app folder. My phone is rooted.
When I'm trying this over adb it says that I only have Read permissions. What am I doing wrong?

Put the phone into recovery mode then do the adb commands.
You only have read access while booted. R/W access while in recovery.

Mh I tried this but I couldn't even open the shell, said something.sh is missing.
You mean the normal recovery and not Clockworkmod or something, right?

You have to put it in the custom recovery. Clockworkmod or whichever one you use.

Ah okay, thank you, I will try that.
Though I need to use the normal recovery.

I tried it with clockwork now. It works but when I do "cd system" and do "ls" it's empty...so I can't see any app-folder?!
Edit: Oh I forgot - do I need to mount system first using the partitions menu?!

Eggcake said:
I tried it with clockwork now. It works but when I do "cd system" and do "ls" it's empty...so I can't see any app-folder?!
Edit: Oh I forgot - do I need to mount system first using the partitions menu?!
Click to expand...
Click to collapse
Code:
mount /system
At the adb shell.

Oy, thanks now I finally got it
Remove worked, pull didn't (or it took >5min for a simple apk file and I aborted it too early).

Accessing the internal storage from recovery? No ROM installed or backup available.

I downloaded a ROM for the wrong nexus phone (there's so damn many I forgot to check carefully) and I've already wiped system and moved my nandroid backups to my computer because I wanted to wipe the SD card.
Is there any way to get into the phone's internal storage from recovery and load a new ROM manually?
With my older phones I would just pull the micro SD card and put the ROM on it from my PC, this doesn't seem to be possible with the nexus.
EDIT: I also have the Galaxy Nexus Root Toolkit v1.3. I think I can load a ROM using this right?
Thanks!

Check my faq section in my siggy.

Jubakuba said:
Check my faq section in my siggy.
Click to expand...
Click to collapse
Pulled:
adb push NAMEOFZIP.zip /sdcard/
from your FAQ. Thank you very much! Should work perfectly.

I got:
C:\Program Files\Android\android-sdk\platform-tools>adb push update-cm-9-20120314-NIGHTLY-toro-signed.zip /sdcard/
error: device not found
in my device manager I have:
SAUMSUNG Android Phone
-> Android ADB Interface

I assume typing "adb devices" brings nothing up?
Are you in the fastboot menu?
Do you have the drivers installed (I'd assume so, if you're rooted)

Jubakuba said:
I assume typing "adb devices" brings nothing up?
Click to expand...
Click to collapse
Brings up a blank list with an empty entry:
C:\Program Files\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files\Android\android-sdk\platform-tools>
Jubakuba said:
Are you in the fastboot menu?
Click to expand...
Click to collapse
Held down the vol up and vol down buttons while holding power.
Android guy has his chest open with a 4x4 blue square pattern inside of him.
Says FASTBOOT MODE in red and LOCK STATE - UNLOCKED also in red.
Jubakuba said:
Do you have the drivers installed (I'd assume so, if you're rooted)
Click to expand...
Click to collapse
Add / Remove programs says 'SAMSUNG USB Driver for Mobile Phones' 45.5MB version 1.4.6.0
EDIT: Changing to 1.4.8.0 didn't help
EDIT: Seeing Fastboot Command Read Error -2147382647
EDIT: Installing new naked drivers from here didn't work either, same read error sometimes, other times adb devices returns blank
http://forum.xda-developers.com/showthread.php?t=1379875

Okay got into the phone when I used recovery instead of boodloader to talk to it with ADB. I'm pushing the ROM but CWM doesn't see the ZIP after it has been pushed when I choose 'install ZIP from sdcard'
Final edit: Couldn't find the ROM when I pushed it using ADB. I think I was using the command wrong because the file never showed on the SDCARD after pushing it. So what I did was push it as 'update.zip' and then used CWM's 'load update.zip' from SDCARD function and got Cyanogenmod installed and everything is gravy again.

advocat3 said:
Okay got into the phone when I used recovery instead of boodloader to talk to it with ADB. I'm pushing the ROM but CWM doesn't see the ZIP after it has been pushed when I choose 'install ZIP from sdcard'
Final edit: Couldn't find the ROM when I pushed it using ADB. I think I was using the command wrong because the file never showed on the SDCARD after pushing it. So what I did was push it as 'update.zip' and then used CWM's 'load update.zip' from SDCARD function and got Cyanogenmod installed and everything is gravy again.
Click to expand...
Click to collapse
this didn't work for me. adb devices shows serial number recovery (that's the only thing I can boot my phone to)
when I adb push update /scard it eventually says it successfully did so with xxxxx amounts of data.
When I apply update.zip card from CWM menu it tells me can't open /sdcard/update.zip (no such file or directory)
I also renamed latest cm.zip and pushed it to /sdcard/0/Download - even when it says OK I can't find that file in that directory.
Am I royally screwed?
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
advocat3 said:
Okay got into the phone when I used recovery instead of boodloader to talk to it with ADB. I'm pushing the ROM but CWM doesn't see the ZIP after it has been pushed when I choose 'install ZIP from sdcard'
Final edit: Couldn't find the ROM when I pushed it using ADB. I think I was using the command wrong because the file never showed on the SDCARD after pushing it. So what I did was push it as 'update.zip' and then used CWM's 'load update.zip' from SDCARD function and got Cyanogenmod installed and everything is gravy again.
Click to expand...
Click to collapse
this didn't work for me. adb devices shows serial number recovery (that's the only thing I can boot my phone to)
when I adb push update /scard it eventually says it successfully did so with xxxxx amounts of data.
When I apply update.zip card from CWM menu it tells me can't open /sdcard/update.zip (no such file or directory)
I also renamed latest cm.zip and pushed it to /sdcard/0/Download - even when it says OK I can't find that file in that directory.
Am I royally screwed?

Bronyr said:
this didn't work for me. adb devices shows serial number recovery (that's the only thing I can boot my phone to)
when I adb push update /scard it eventually says it successfully did so with xxxxx amounts of data.
When I apply update.zip card from CWM menu it tells me can't open /sdcard/update.zip (no such file or directory)
I also renamed latest cm.zip and pushed it to /sdcard/0/Download - even when it says OK I can't find that file in that directory.
Am I royally screwed?
Click to expand...
Click to collapse
Sorry but this is really really old. You should try doing a flash-back-to-stock if you can using the Nexus Root Toolkit.
I haven't had my Galaxy Nexus for well over a year.

advocat3 said:
Sorry but this is really really old. You should try doing a flash-back-to-stock if you can using the Nexus Root Toolkit.
I haven't had my Galaxy Nexus for well over a year.
Click to expand...
Click to collapse
thanks. Finally got philZ.zip pushed via ADB to internal, rebooted, all gravy! Pushing didn't work cause my battery was weak.

You van also flash a ROM via recovery from your PC with adb sideload. Its awesome.
Sent from my Galaxy Nexus using XDA Premium HD app

[Solved] Deleting a unseen file with ADB

I've got this weird problem, its not who knows what but, i had cm10.2, since they're all nightlies i decided to do a full wipe,
Installed 4.2.2 takju factory image, then before i even start to boot the phone i installed cm10.1.2, the way i put cm10.1.2 after the full wipe was
from the tutorial on the cyanogenmod wiki. This command:
Code:
adb push YOURROMZIP.zip /sdcard/
Which in my case is cm-10.1.2-maguro.zip
I did the same with the gapps that go with the cm.
Now the problem is that when i get into CWM v6023, And i, for example select choose zip from sdcard i see the two zip files in there, in /sdcard/
but i can only install them from the cwm ofc... when i boot into the rom and use root explorer or file manager, both with root permissions, i cannot
see the files in the /sdcard/, i tried with
Code:
adb pull cm-10.1.2-maguro.zip /sdcard/
But all i get is "remote object does not exist"
I tried with shell rm, it still does not exist.
But i can see it taking space, usually i get around 500 mb used with a clean install + my apps, but now i get 750mb because of those two files
Is there any way i can remove them?Because the only thing that sees they're there is CWM..

Uhm i was just wondering around file manager when i ran into /mnt/shell/emulated, it seems all the files go there after you put them in the /sdcard/
I dont know the reason for that but anyways, solved the problem..

IceVip said:
Code:
adb push YOURROMZIP.zip /sdcard/
Which in my case is cm-10.1.2-maguro.zip
I did the same with the gapps that go with the cm.
Code:
adb pull cm-10.1.2-maguro.zip /sdcard/
But all i get is "remote object does not exist"
I tried with shell rm, it still does not exist.
Click to expand...
Click to collapse
Of course it don't exist.. It exists under /sdcard/cm-10.1.2-maguro.zip

Question about TWRP and SuperSU

Yesterday I reinstalled stock 7.1.2 from Google, recovery and everything. I was trying to get rid of the /supersu directory in my phone's root directory. I think I got rid of it, because I didn't see it using "adb shell" and listing all files in my root directory. I went ahead and reinstalled TWRP and booted to it, and the /supersu directory is back. This makes me think TWRP is creating that directory by itself, without asking. Can anyone confirm this? And is there anyway to make TWRP NOT create that directory, or is SuperSU integrated into TWRP?

Ok so, I just rebooted into TWRP again and the /supersu directory was there. I didn't delete it from TWRP, and rebooted into the ROM, and used "adb shell" to list the files in root, and /supersu is not there. So does TWRP temporarily create /supersu for some reason, then delete it before you exit?