[Q] How to install a ROM on Micromax Canvas Juice A177 using ADB? - Micromax Canvas Juice Questions & Answers

Hi Geeks
Yesterday I kinda soft-bricked(idk but i think that's what its called) my phone(Micromax Canvas Juice A177). I moved my /system/app/ folder to my sdcard and now my phone won't boot. The boot animation runs in a loop. i can access the power_button+volume_up menu. Another big problem is that i cannot use my External sdcard for recovery since i have swapped my sdcard1 with sdcard0. so when i open "apply update from sdcard" it opens my ORIGINALLY-sdcard0(which is now treated as sdcard1) which i cannot remove from my phone. so apply update from sdcard option is terminated.
i want to know if there is any way i can re-copy the /system/app/ folder to my device. i tried doing the same via adb but it always returns an error:closed.
then i thought i would install all those packages manually using adb sideload packagename.apk which would basically put them in the /system/app folder(if i'm not mistaken). but every time i try installing a package it sends the package till 100% but my phone shows "Installation Aborted".
Now i am downloading the stock ROM but i don't think I'll be able to install it using adb sideload.
i have never installed a ROM before.
please help me at least start my device!!!
Thanks

Related

ROM Upgrade Seems to be Impossible!

Hello!
Yes, I am fairly new to this, but not a noob by any means. I've been upgrading ROM's for a long time, albeit Windows mobile.
I have rooted my Hero - confirmed by installing several ROOT only apps from the market, and accessing commands from su, # prompts.
I can't seem to upgrade my [otherwise stock] Sprint hero despite trying different approaches.
Hugely frustrating, a history of my attempts:
I copied the latest backup recovery file 1.5.2 to the root of my SD card.
I have installed ADB tools
So I open a command prompt and go into Android SDK/tools:
adb shell
su
# flash_image recovery /sdcard/ [recovery file name]
I then type 'reboot recovery' the phone reboots and I have the screen with phone image and large triangle with yellow '!' in it.
I hold 'HOME' and 'END' togerther to access menu of system recovery utility and I can only select 3 options:
reboot system now [Home+back]
apply sdcard:update.zip [Alt+S] * see below)
wipe data/factory rest [Alt+w]
At the bottom of the screen I have the error (which I have investigated and found that no-one seems to be able to explain, yet it doesn't seem to hinder most folks in flashing roms):
E:Can't open /cache/recovery/command
I initially expected to have MORE options as the first thing I wanted to do was create a Nandroid backup, but gave up on trying to do this!
*So I rename the fresh 1.1 rom zip to 'update.zip' and copy to the root of my SD card.
I 'reboot recovery' again, my phone restarts, I choose the 'Apply SDCard:update.zip' option and then it begins to install:
Install from sdcard....
Finding update package....
Opening update package....
Verifying update package....
E:No signature (599 files)
E:Verification failed
Installation aborted
I've tried updating different ROM's with similar negative results - and yes, I have checked the MD5 to ensure ROM's are 'good'
Ideas?
BTW - I still also have the error:
E:Can't open /cache/recovery/command
Get the fresh kitchen and run the auto root feature.
I would agree get the kitchen try the auto root because to me it sounds like there was a problem in your root process. screen that you are getting into is just the fastboot also what I have found to make life easier is rename the RA-Recovery-heroc-1.5.2.img to just recovery.img makes my life a whole lot easier as I mess with my phone so much I have had to RUU several times and that just makes rooting manualy a little faster.
As far as installing the Fresh ROM, I know I had an issue because I was using a MAC and when I downloaded the Zip file, the MAC would unzip it. I finally had to download the Zip file right to my phone and it worked fine.
raylusk said:
As far as installing the Fresh ROM, I know I had an issue because I was using a MAC and when I downloaded the Zip file, the MAC would unzip it. I finally had to download the Zip file right to my phone and it worked fine.
Click to expand...
Click to collapse
That's because you aren't supposed to unzip a rom.

Problem with ADB on softbricked Transformer

Hello everyone here at xda-developers.
A few days ago I was watching streams on my Asus Transformer TF101(B70). Suddenly out of nowhere the tablet shuts off and starts an infinite loop which I simply cannot get it out of. I end up restoring the tablet to factory default and load a stock kernel onto my tablet using adb push. Since the tablet doesn't have any rom installed at this point I try to push CyanogenMod 9.0 onto my tablet in order to try and get my tablet to work and this is where the issues begin. First of all I try to push the rom onto /sdcard but that bugs my CWM 5.5.0.4 and will not allow me to access /sdcard and keeps telling me that there are "No files" when I'm trying to access /sdcard. If I restart into recovery it can access my files again but the pushed file is not there.
Afterwards I try again to push the file to /sdcard/download but then it tells me that this archive is Read-Only. I run a the "adb remount" command and it tells me it completed succesfully but when I push again it tells me that the archive is still Read-Only.
I've tried various commands but I can simply not change the archive into read/write. A few times I have succeeded in pushing the rom to /sdcard/download but when I try to locate the file it is simply not there and is not located anywhere on /sdcard despite the process being completed. I have simply no idea on how to get the rom file onto my tablet in order to restore it to normal and I was wondering if any of you have any ideas on how to get my tablet working again?
If you have any questions regarding information needed about just ask and I will provide the necessary information. I am really out of ideas on what to do.
Get a Micro SDCard and copy the ROM onto that from a PC, then put that in the TF and boot to recovery
*Detection* said:
Get a Micro SDCard and copy the ROM onto that from a PC, then put that in the TF and boot to recovery
Click to expand...
Click to collapse
I already have a MicroSD card in my tablet but I am not able to access it from CWM recovery
Try pushing the file to data/media.
Are you pushing the file while in cwm recovery?
baseballfanz said:
Try pushing the file to data/media.
Are you pushing the file while in cwm recovery?
Click to expand...
Click to collapse
I am pushing files while in recovery mode. I have already tried pushing to.other directories than /media/download but the same thing.happen. either it tells Me that the file system is read only or it says that the file transfer succeeded but the file cannot be located anywhere. I read up on the solution of trying to access a rom through microssd. Unfortunately my recovery doesn't support that unless I can change it to use external.memory instead of internal memory.
The only thing I succeeded in was getting a rom pushed to /system. Would I be able to access this directory from my recovery?
baseballfanz said:
Try pushing the file to data/media.
Are you pushing the file while in cwm recovery?
Click to expand...
Click to collapse
I am pushing files while in recovery mode. I have already tried pushing to other directories than /sdcard/download but the same thing happen. either it tells Me that the file system is read only or it says that the file transfer succeeded but the file cannot be located anywhere on /sdcard. I read up on the solution of trying to access a rom through microsd. Unfortunately my recovery doesn't support that unless I can change it to use external memory instead of internal memory but I do not know it that is possible.
The only thing I succeeded in was getting a rom pushed to /system. Would I be able to access this directory from my recovery?
WebberX said:
possible.
The only thing I succeeded in was getting a rom pushed to /system. Would I be able to access this directory from my recovery?
Click to expand...
Click to collapse
It would be better to try than to ask !
How did you get on, any luck yet ?
You could try flashing a new CWM that supports SDCards via NVFLASH
WebberX said:
If you have any questions regarding information needed about just ask and I will provide the necessary information. I am really out of ideas on what to do.
Click to expand...
Click to collapse
If you did a factory reset (and hence data loss is not a problem), your best option is using nvflash/wheelie to restore the device to a clean state with a stock firmware build and then reflash CWM to install whatever custom ROM you want.

Can't write on internal SD card after root

After having rooted (with nexus 10 toolkit v1.3.0) my nexus 10 and flashed AOPK Nexus 10 (WIP) Task650 & Ktoonsez (1-4) rom, I'm unable to upload to, change or move any files or folders on my internal SD card. I installed Root Explorer and changed from Mount R/O to Mounted as r/w. Access is granted by Super SU. I also tried to change permission settings, unfortunatedly without any success. There appeared the following message:
"Warning
Permissions change was not successful. Please note that some file systems (e.g. SD card) do not allow permission changes."
Is there a possibility to change these permissions in order to be able to create and move files and folders on my SD card?
Thanks for taking your time to help me with my issue!
Anzirothu
1. Clear cache
2. Clear dalvik
3. Fix Permissions
forgot something ?
Thank you for your reply, Patrik!
1. done.
2. done.
3. Fix Permissions - How? With cwm? I did fix permissions with cwm recovery, but the problem persists...
Just so we are clear, when you say "upload to, change, or move" are you meaning you cannot copy a file from your computer to your Nexus 10? Or just that you cant arrange stuff through root explorer from within the tablet itself?
Neither copying from PC to Nexus nor arranging stuff through root exlorer from within the tablet itself. I can't even download an email attachment and put it to the SD card. The card seems to be locked.
I had that problem once but I dont remember what caused it or what exactly I did to fix. I think I just did a complete wipe by locking and unlocking the bootloader and then installing a new ROM again.
I think I did this too (unroot, lock bootloader, then root and unlock bootloader) and then installed the same rom again. I will try it this time with another rom.
Isn't there really no other solution to get access to my SD card again??
Thx for your help!
Are you using a toolkit to unlock and root? If so them maybe it is not doing something right and it messing up a permissions somewhere. It could also be a driver problem on your PC with being unable to copy a file to the tablet.
Thank you for your help!
I am using the nexus 10 toolkit V1.3.0. Right now I'm trying to intall twrp recovery with a fully wiped sd card. No easy task fot me being a noob...
In ClockWorkMod, make sure that /data is mounted
Then download the Android SDK: http://developer.android.com/sdk/index.html
I usually put all the files just in C:/android-sdk-windows
Once you have it all there open up the SDK Manager and download all the additional files needed. You probably only need to download "Android SDK Tools" and "Android SDK Platform-tools", but I always download the other files for whatever version of Android I am running, in our case Android 4.2. That way I have them if I need to do something else.
Once downloaded, open the Android-sdk-windows/platform-tools directory. copy:
adb.exe
adbWinApi.dll
adbWinUsbApi.dll
fastboot.exe
to your base C:/Android-SDK-Windows directory.
Now open command prompt from Start -> run
type: cd C:/Android-SDK-Windows
type: "adb devices" and it should list your tablet. It will actually say something with your devices serial number and then "Recovery" after it, showing your tablet is in recovery. If you dont see this then you either dont have your tablet mounted right from in the Recovery, ClockWorkMod is stupid, or you dont have working adb drivers.
Now copy the ROM you want to flash to C:/Android-SDK-Windows
Then type: "adb push blahblahblah.zip /data/media/0"
That should push the ROM to the root of your SD card. Give it time, it takes a while to push a ROM file. Once it is done, flash the ROM.
That *should* put it in the right spot where it looks like it is on your "internal storage" (what you see when navigating files within the ROM). If you dont see the ROM in clockworkMod then keep navigating back to the root of your internal storage and then open up "data", then "media", then "0" and you should see it. If you still cant find the ROM, push it again but just use "/data/media" as the location.
I just did all these steps myself to verify I remembered it all correct and I was able to successfully copy a ROM and find it on my tablet to flash by doing everything I just listed above. SO you should be good to go if you follow all those steps properly. I know it looks like a lot of work, but it really isnt and will go quite fast. Most of it is just the setup for getting ADB and Fastboot ready to use.
For a ROM to install, I would recommend to someone new like you either of these:
http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ That one is pretty close to the stock ROM with a few fixes and a couple extra features
or: http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ This one is pretty much CyanogenMod 10.1, but built by a different guy and not pulling every new thing from CM, just the "cherry picks" of features. It tends to be a bit more stable and less buggy than the real CM10.1 nightly's
And for a kernel you can flash and forget you will want to try this one:
http://forum.xda-developers.com/showthread.php?t=2098157
^^^^^ To flash that you will want to do a similar thing as how you pushed the ROM to your device. Only this time you will copy the kernels' "boot-r4.img" file into your android-adk-windows directory and use the command: "fastboot flash boot boot-r4.img"
While I enjoy the KTManta kernel more, it does require a bit of tweaking to get running perfect. Which is one of the things I like about it because of all the options to tweak. But for someone just learning this stuff that would be a bad thing, so Franco's kernel is much better than stock and doesnt require you to adjust anything once it is flashed to your tablet.

Install Rom on Galaxy S4 internal memory

Hi Guys
I'm so lost and I've been trying to figure this out for 2 days now on my own.
I've rooted my S4 i9505 and installed ClockWorkMod on it but I don't have an SD card and am trying to install a ROM from the internal memory. My question is now how do I put the ROM at "root access level" on my phone? I have a Mac and a PC so instructions for either would be appreciated. When I attach the device via USB, it connects as a media device in Windows but what folder do I put the rom into?
Any help hugely appreciated
I had this problem as well. I ended up just sending the via sideload. Download the Google SDK and install the software toolkit.Place your .zip file in the same place as the adb.exe. Navigate to that folder in command prompt and run these command after selecting sideload in CWM.
ADB USB
ADB SIDELOAD NAMEOFROM.ZIP
Sent from my GT-I9505G using Tapatalk 4 Beta
Thanks for the reply.
I managed to sort out the issues.
What I did was install this:
1) CWM Advanced PhilZ Touch - this gave more options and made everything easier
2) I then downloaded the ZIP Rom I wanted and created a new folder on the phone using "Android File Transfer"
3) I then booted the phone into recovery mode and installed the rom via the "internal SD card" option and selected the zip and it was done in about 2 minutes!
Easy peasy when you know how but took me ages to figure it out!

[Q] Desperate need some help, failure updating 4.4

my nexus 4 was rooted with 4.3 but then i decide to upgrade to 4.4
this is the video i am trying to follow, basically just wipe & install which i did most the time.
youtube title "NEXUS 4: HOW TO MANUALLY UPDATE TO ANDROID 4.4 KITKAT"
it has two files one is mako and one is gapp.
after i did all the wiping in cwm and try to install the mako file, it shows "no file context" or sth similar, and installation is abort (i think there is problem when i transfer the file), but then i continue to install the gapp file (what the hell was i thinking?)
so now i am stuck in the google start up loop, i can only access cwm recovery mode and don't have a valid rom to install in my sdcard.
i tried to adb push another rom to the sdcard with no success (my storage was already very low, any way to remove files in the storage at this point?)
the "mount & storage" also doesn't seem to let me mount the sdcard (but system shows up "unmount").
so now i don't know what to do.
if anything has any idea or suggestion please let us know.
i am quite desperate now with a dead phone and will try anything.
thanks for reading such a long thread.
Dude that vid is old and it installs pa or some other port just flash factory images from google
Sent from my F1 using xda app-developers app
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
any step by step guide to do this?
i am still new to this thing even i install a few roms before.
i will google it now, but any additional info is much appreciate.
thanks
Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?
telly0050 said:
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?
Click to expand...
Click to collapse
after tons of troubleshooting finally got it back to work.
it ends up the reason is i didn't update to the latest cwm at the very beginning.
and sideloading 4.4 didn't work because of that too, i have to install an old 4.2 to have it working.

Categories

Resources