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.

[Q] Sandvold freezing at boot

I am using Sandvold's ROM but, starting from some days ago, I encountered a big problem: during startup, my Desire freezes and cannot terminate the boot sequence. Even a nandroid restore is not able to fix it: I have to factory reset the device and, after that, restore works. I haven't changed anything, I don't know what could cause this problem, which is very annoying.
I use the latest version, 0.18.2.1.
What could I do?

I'm using the same version of the ROM and for a while now it has been randomly freezing up and I have to physically remove the battery to be able to restart it, after which it resets the date back to January 1980.
Today it froze up and it is also stuck in a boot loop. Tried wiping the dalvik cache and that didn't work so I'll do the factory reset like you suggest. I don't really want to have to switch back to a GB ROM though as I really like ICS.

Same problem here, the problem started when I rebooted today. Running sandvold 0.18.1.
After some digging I could identify a rough source of the problem, but I'm not Android guru, so it will take somebody more experienced than me to figure this out. Essentially, what happens, is that the system_server goes into a loop and keeps on crashing and getting restarted. I've attached the logcat for the gurus.
I'll try reinstalling and possibly wiping to see if that helps.

Just a quick followup, I had to do a full wipe to get back to working order. Attached is a comparison logcat. I don't really understand how Android boots, so I would kindly ask the more knowledgeable devs to have a quick look. Thanks!

After setting the phone up and rebooting, the problem is back again. Seems like there is a time/date-related bomb in sandvold 0.18.

The same problem at 0.18.2.1.
As much as I found it works (is able to survive reboot) until any soft from Google Play was installed.
After that it has a bootloop on reboot.
Actually I didn't try to install anything from .apk so it can be related to the installation process itself.
Also the same problem has 0.17.1.1 (I don't сheck all versions, just the last ones of majors).
---------- Post added at 09:47 AM ---------- Previous post was at 09:20 AM ----------
0.16.1 - the same problem.
Steps to reproduce:
1. Wipe and install ICS
2. Add google account (at that point the phone still survives a reboot nicely)
3. Install any soft from Play
4. Reboot and enjoy the bootloop
Add: update of an existing soft from Play still causes a bootloop.

dietwice said:
The same problem at 0.18.2.1.
As much as I found it works (is able to survive reboot) until any soft from Google Play was installed.
After that it has a bootloop on reboot.
Click to expand...
Click to collapse
Someone with posting privileges should report this problem in the developer's forum...

roberto.zanasi said:
Someone with posting privileges should report this problem in the developer's forum...
Click to expand...
Click to collapse
SOLVED there:
http://forum.xda-developers.com/showthread.php?t=1355660&page=1661
Briefly:
0. Make sure you have adb and phone drivers so you can connect to the phone from computer via "adb shell"
1. Google for Vending-3.8.15.noupdate.norestrictions.apk, download it, rename to Vending.apk, place to sd card
2. Reboot into Recovery mode, use menu to mount "system" and "sdcard"
3. Run "adb shell" on computer
# cd /system/app
# ls
You should see Vending.apk somewhere in the list
This will delete the broken Play Store app
# rm Vending.apk
# rm -r com.android.vending
# rm -r com.android.vending.updater
Settle the correct Play Store app (assuming you placed the downloaded Vending.apk to the root folder of sd card)
# cp /sdcard/Vending.apk /system/app/
4. Clear Dalvik cache
5. Profit!
Now reboot and enjoy the regular booting.
Also you can use the Play Store to install applications.

dietwice said:
SOLVED there:
http://forum.xda-developers.com/showthread.php?t=1355660&page=1661
Click to expand...
Click to collapse
Thank you!
I was trying to see if the same method could be performed with the terminal emulator (I haven't installed the sdk, so I don't have adb), when I realized that the superuser app is broken, too. The "su" command in terminal isn't working, as the superuser app stops.

roberto.zanasi said:
Thank you!
I was trying to see if the same method could be performed with the terminal emulator (I haven't installed the sdk, so I don't have adb), when I realized that the superuser app is broken, too. The "su" command in terminal isn't working, as the superuser app stops.
Click to expand...
Click to collapse
I also tried to do this via Terminal, and my "su" is ok.
But it doesn't work.
It looks like commands are being executed successfully, but it in fact they aren't.

Same problem for me...I'll try to fix it following your help!!! I let you know!!
It work, but I'm not able to "install" the edit Play Store downloaded!!! Reboot work, but no Play Store present among my applications!!!
I find com.process.vending in my application list, but it's a grey icon whit the small sd symbol!
I'll try again to uninstall it!

I have the same problem but, when I tried to use the dietwice's method, I found only the Vending.apk on /system/app folder. So I removed it, replaced with the Vending.apk file downloaded and I continued to follow the method and then I rebooted the phone.
The boot loop is present also after this, so I'd like to know if the fact that I didn't found com.android.vending and com.android.vending.updater is a signal that something was wrong even before applying the dietwice's method.
Someone can answer to my question, please?

I have the same problem as freakymonkey. Any Ideas?

gartenriese said:
I have the same problem as freakymonkey. Any Ideas?
Click to expand...
Click to collapse
I have flashed the ROM again from ClockworkMod recovery and, first to make the reboot, I used the dietwice's method and everything went OK! :good:
On the first boot something went wrong with synchronization with my gmail account, but after a reboot (without boot loop) everything worked fine.

I restored everything but sd-ext and it (re)booted fine, so it has something to do with that. Maybe some Google Play Store data is still on there? How can I get rid of these?
EDIT: Ok, I found some files, will try to delete them tomorrow.

Following the main Sandvold discussion, I've FIXED it!!!!
At the end of the procedure, I needed to do "adb uninstall com.android.vending" and then reboot.
I've Play Store back! )))
dietwice said:
SOLVED there:
http://forum.xda-developers.com/showthread.php?t=1355660&page=1661
Briefly:
0. Make sure you have adb and phone drivers so you can connect to the phone from computer via "adb shell"
1. Google for Vending-3.8.15.noupdate.norestrictions.apk, download it, rename to Vending.apk, place to sd card
2. Reboot into Recovery mode, use menu to mount "system" and "sdcard"
3. Run "adb shell" on computer
# cd /system/app
# ls
You should see Vending.apk somewhere in the list
This will delete the broken Play Store app
# rm Vending.apk
# rm -r com.android.vending
# rm -r com.android.vending.updater
Settle the correct Play Store app (assuming you placed the downloaded Vending.apk to the root folder of sd card)
# cp /sdcard/Vending.apk /system/app/
4. Clear Dalvik cache
5. Profit!
Now reboot and enjoy the regular booting.
Also you can use the Play Store to install applications.
Click to expand...
Click to collapse

matteo.rek said:
Following the main Sandvold discussion, I've FIXED it!!!!
At the end of the procedure, I needed to do "adb uninstall com.android.vending" and then reboot.
I've Play Store back! )))
Click to expand...
Click to collapse
I have been unable to get the Play Store back on my HTC Desire. I have followed the above steps exactly but no shortcut appears on the applications screen.
I have tried wiping the dalvik cache, even did a fresh install of ICS Sandvold Rom but no luck.
Could it be because of the default a2sd?
Any assistance much appreciated guys

[Q] Nexus 4 - SU not working anymore but binary present

Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...

I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
skyraven83 said:
Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...
Click to expand...
Click to collapse

it seems in the end that it was all in xprivacy problem....
solved and now it is functional
skyraven83 said:
I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
Click to expand...
Click to collapse

Just so you know
The reason you probably did not get responses to this is because you posted it in Galaxy Nexus section and not Nexus 4 forums

EFS Partition Missing in SM-T217S

When I look in my device, T217S, I don't see any files under /efs and looks like it's corrupted or not sure why it is missing. I just go a refurb tablet last week and probably, that has something to do with it.
I rooted it and have TWRP 2.7.0 installed and removed all the Sammy bloatware including the ever annoying Knox
My question is would it be possible to copy the /efs partition files from another device to mine? If that is the case, can any of you please zip it up and post it here?
I tried Kies, Kies3, SmartSwitch and all of them are not letting me get into emergency recovery as it complains that my device doesn't support "initializing" or something to that effect.
How can I get /efs working and because it's missing, the Factory mode is always ON but, the data (FreedomPop) and wifi works fine although I have to turn on wifi after every reboot. Not a biggie but a hassle, nevertheless.

R,
try opening a terminal and running
su -c ls -al /efs/*
it may be /efs is not readable by normal user, which is good, should not mess with /efs.
it's also likely selinux is preventing read access, in which case you need to disable selinux as even
running a root command will not get around selinux while it's enforcing.
m

Fire TV 2 - stuck at b/w boot logo after flashing prerooted 5.2.1.0

Hi folks,
I having some problems here while I try to flash the latest prerooted rom from rbox. So here is the situation
FireTV was on Stock Rom 5.0.5.1
- I followed the Guide on aftvnews to install TWRP Recovery link
- everythink looked good, prerooted rom was installed without any errors
- reboot system -> stuck at black&white "amazon" logo
- I noticed that the LED completly turned off after 30 seconds (i guess) so might be looping
- back to twrp I did wipe /cache, then reboot -> same behavior
- tried over adb shell : mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache
-> same result
- tried factory reset -> guess what, same as before of course
so what the hell can I do to reset it in some way?
One thing I also noticed is that when I open a local terminal or an adb shell I'm already root. Is this normal for prerooted rom?
And another thing is the supersu binary. I could remember that the bin was installed to /sbin/su ,but this is not the case here.
'which su' gives no result back
'find / -name su' give me /system/xbin/su
Is that the way it should be? I ask because adblink gives me an error when I try to run FS R/W
"root requiered"
Thats explainable cause adblink will run 'su' first.
I would be really happy if someone could give me some advice. I dont know what else I could try

!! Problem solved
It was the god damn HDMI cable -.-
Behind the boot logo it was waiting for paiing the remote
Maybe it could help some of you guys too
Kind regards

Thank you, had the same issue, never would have tried a new cable, as i was getting video from it.