Related
I have just updated my nexus s to the latest 4.0.4 update..now i want to bring back root access .. as we all know were going to loose root access if we updated. anyway i previously used this method http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ now im wondering if this also applies to 4.0.4 update and what is the best recovery to flash on this update?
The only thing i did was upgrade to 4.04, dont reboot but flash superuser, all clear, root is back.
[Q](solved) how do i bring back root on my i9023 ics 4.0.4
willemt158 said:
The only thing i did was upgrade to 4.04, dont reboot but flash superuser, all clear, root is back.
Click to expand...
Click to collapse
hmn... what i did was
i went to adb
open cmd
flashed recovery3101.img
after that i installed superuser using CWM recovery . if your using the stock recovery it will only show an error msg. didnt wipe anything ... all is ok and well hehehe cheers!
I have issue with CWM and Root. I've follow the guide here.
I manage to successfully do up to step 4 without error. After that, when I reboot the device, it have a message "android installing update". I installed titanium backup and it says no root access. Superuser is available. When I tried to update on Play "Update for Superuser could not be downloaded due to an error (941)"
I tried to go back to recovery, it is the stock recovery instead of CWM. I've updated my 9023 from 4.0.3 (stock non root) to 4.0.4 using CWM. I've installed superuser using CWM as well. But when I reboot the device, it went back to stock recovery. I've tried fastboot CWM, turn off, then turn back on to go recovery, it is using CWM. But when I reboot, and try to go back to recovery, it goes to the stock recovery.
Appreciate some help. Hope my explanation is clear.
Will
First try flashing the latest Superuser than reboot, then open rootexplorer
Rename "/system/etc/install-recovery.sh" to "/system/etc/install-recovery.sh.bak".
All Stock ROMs replace the recovery on each Boot if it isn't the stock one. Renaming this script stops that. After you do this, flash CWM one more time and it'll stick.
Thanks to harbb who helped me with the same isseu
not sure if this is legit... I found a few sites with the same tutorial but different backup apps same file download though... can anyone varify?
filename: Superuser-3.0.7-efghi-signed, from a mediafire download (/?57iroxlzh8bb5qi)
from tutorial: Root Nexus S with Android 4.0.4 ICS IMM76 Firmware, from androidlot.com
(sorry can't post link)
it just said to do a recovery from bootloader, no other tampering needed... was thinking of using it if it worked as I just did the Nexus S 19023 OTA update 2.3.6 - 4.0.4 found on this forum but wanted to root to use voodoo sound... first timer and dont want to mess around with roms or cwm... figure no harm rooting as Nexus S probably won't get anymore official updates
Signature verification failed
well i have tried to install the superuser from recovery (apply update from SDcard) but every time i try to install the zip file it gives me signature verification error .
Mansuur said:
well i have tried to install the superuser from recovery (apply update from SDcard) but every time i try to install the zip file it gives me signature verification error .
Click to expand...
Click to collapse
That means your not in CWM Recovery. You have to follow the guide and use fastboot to flash a custom recover. Thats why we use a custom recovery, to bypass the signiture check
so wats da final result?
in ics 4.04 how to flash cwm and root and install vodoo?
ended up using m.sabra's one click root and flash cwm tool (/showthread.php?t=1544940) worked a charm, downloaded voodoo sound plus so i didnt have to flash new kernel, putting music back on phone now (had to unlock bootloader) to see how it sounds
also used appbackup&restore, copied backup folder from sd to computer, used the root tool, redownloded appbackup&restore, copied folder back from computer to phone, allowed install from non market, reinstalled all apps
now have superuser and cwm and all my apps back
Hope this may help. it's the way a did it on my Nexus S
Download fastboot for Windows or Mac.
Make sure you have the Android SDK installed.
Download ClockworkMod Recovery.
Download the Rooted Su Binary for 4.0.4
Make sure you have the necessary drivers installed for your device
Put your device into Bootloader Mode (turn your device off, then hold Volume Up + Power).
Once in Bootloader Mode, type the following into your Command Window
fastboot oem unlock
You should now see a couple of lines go through on your Window.
Then Type the following:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Provided this went correctly (it should), you now want to cycle down to “Recovery” on your device using the Volume buttons and press Power to confirm. This should boot you into ClockworkMod.
Select Recovery again, navigate to “Mounts & Storage” and then to “Mount USB Storage”. Once this has been done, your SD Card should appear on your PC.
Copy the Rooted Su Binary you have downloaded to your SD Card, and then Unmount USB Storage on your device.
Navigate back to the main menu of ClockworkMod and select “Install zip from sdcard”, then “Choose zip from sdcard” and select the package you just copied across, and then confirm the installation. This should install the package and root your device.
Hey guys sorry i was on vacation, thats why it took me so long time to come back, anyways... here is the link of the step by step procedure on rooting your nexus s, this is what i followed, http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
but what i did was ;
1. after updating i lost root
2. open adb tool
3. flash new recovery3101.img ( this is to replace default recovery from the stock ics 4.0.4)
4.then installed superuser from the new recovery that i installed ( CWM)
i wont go through all the details since , the link already explained that there....so cheers and hope this works for you , all the needed files is in the link also.
Mrbalders said:
Hope this may help. it's the way a did it on my Nexus S
Download fastboot for Windows or Mac.
Make sure you have the Android SDK installed.
Download ClockworkMod Recovery.
Download the Rooted Su Binary for 4.0.4
Make sure you have the necessary drivers installed for your device
Put your device into Bootloader Mode (turn your device off, then hold Volume Up + Power).
Once in Bootloader Mode, type the following into your Command Window
fastboot oem unlock
You should now see a couple of lines go through on your Window.
Then Type the following:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Provided this went correctly (it should), you now want to cycle down to “Recovery” on your device using the Volume buttons and press Power to confirm. This should boot you into ClockworkMod.
Select Recovery again, navigate to “Mounts & Storage” and then to “Mount USB Storage”. Once this has been done, your SD Card should appear on your PC.
Copy the Rooted Su Binary you have downloaded to your SD Card, and then Unmount USB Storage on your device.
Navigate back to the main menu of ClockworkMod and select “Install zip from sdcard”, then “Choose zip from sdcard” and select the package you just copied across, and then confirm the installation. This should install the package and root your device.
Click to expand...
Click to collapse
wow very detailed cheers man!
Glad to help, and hope you've got your Nexus back to root
HI,
2 of my PC (Windows 7 64) does not see my transformer in USB Debug mode. I installed the 64 bit Dell driver on each PC. Could someone provide me with some options to try.
Is there a way to completely reset the Transformer to stock without USB or being able to load a kernel from SD card?
2 ways to reset -
If you can boot then go into settings --> backup and reset --> factory data reset.
If you can't, hold volume-down then press power, and wait till wipe data appears, use vol keys to select it.
and search for the Universal Naked Drivers, those may help.
Thanks. That seemed to wipe the user settings and data, but not the recovery app "CWM-based Recovery v5.5.04 roach-tf101-r2". As a result the following happened after I reset.
System reboots
System comes up clean and runs setup (wifi, gmail account, etc).
System downloads firmware update.
System reboots to install update
Android appears and runs for a few seconds
Mesages appear: CWM-based Recovery v5.5.04 roach-tf101-r2
Finding update package, opening update package, Verifying update package
E: failed to verify whole-file signature
E:signature verification failed
Installation aborted
At this point the TF still will not install zip from sd card since as you told me before I need a different recover and is not found by the PC with a naked driver.
However, the unit is functional.
Any other options to root and get a new recovery installed and finally a new ROM.
Note: the PC does see the TF if I am in the recovery. However, as soon as boot the TF and enable USB debug the TF us not seen.
To go back to totally stock including stock recovery, download and flash an official ROM from Asus website.
baseballfanz said:
To go back to totally stock including stock recovery, download and flash an official ROM from Asus website.
Click to expand...
Click to collapse
I have no problem doing that, but how do I do it if I cannot connect the TF to PC via USB or load a zip file via recovery? Both of these do not work!
Did you update cwm via ROM manager? That's the issue there, you can run Roach2010's fix to fix that.
If terminal emulator app works you can flash a downloaded and extracted
(through es file explorer) recoveryblob with
Code:
su
dd if=/sdcard/recoveryblob of=dev/block/mmcblk0p4
reboot
Then you have working recovery and can either flash ROM or Stock.
Thanks for all the replies.
I finally got it working. It took me forever to understand that having a recovery that could only read from the internal memory was not a big deal. I created a folder on the internal sd and dropped in the zip for the external version of CWM . I rebooted and loaded the new restore and from then on I could load ROMs from my external uSD card. I am now happily running the latest version of Revolver.
Jerry
. I don't even want a custom ROM. I just want to be rooted and run stock with rooted google play store apps. Am I there?
I just want to run rooted apps with no ROM flashing...oh god why...where is the guide to root and only root?
You'd think this http://forum.xda-developers.com/show....php?t=1652398 would be where to go to do that, but evidently it's sending me down the road to custom ROM flashing. AGHGHGhjkdashbdas. Do not want.
Ok, so here's where I am, I have finished step 8:
1. Download Odin 1.85 .
2. Download(USE FIREFOX!) ClockworkMod TOUCH 5.5.0.4 OR TWRP 2.2.2.0, they are both named "recovery.tar.md5" and will be downloaded as "recovery.tar.md5", DO NOT CHANGE the filename or else it wont install.
3. Extract the contents of odin-185.zip to a folder.
4. Run Odin 1.85.exe from the folder you extracted it to.
5. Prepare Odin: Check "auto-reboot" and UNCHECK ALL OTHER OPTIONS. SEE COMPUTER SREEN PICS BELOW.
6. Only Click "PDA" and select the recovery.tar.md5 file you downloaded. SEE COMPUTER SREEN PICS BELOW.
7. How To Put your device into Download Mode: DO NOT TOUCH THE POWER BUTTON FOR THIS PROCEDURE. - download mode is NOT the same as recovery mode
a. Connect the USB cable to your PC, but NOT to your phone.
b. Remove the battery.
c. Reinsert the battery.
d. ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
DO NOT RELEASE THE VOLUME KEY(S) UNTIL INSTRUCTED TO DO SO IN STEP (f)
e. Insert the USB cable into your device. The phone will turn itself on when usb cable is inserted - DO NOT TOUCH THE POWER BUTTON.
f. You will now see a screen w/a yellow triangle warning you about installing a rom . Now release the volume key(s) - SEE PHONE PICS BELOW
g. Press and release the "Volume Up" key to enter into download mode - SEE PHONE PICS BELOW
h. You should now be at the Download Mode screen w/odin recognizing your phone. SEE COMPUTER SREEN PICS BELOW.
8. Click Start in Odin. It will flash the new recovery and will reboot the phone when completed. Your device will autoreboot into android. You are done using ODIN.
9. UPDATING CWM OR TWRP:
Now you need to udate CWM, download and copy cwm6027touch_v14.4.6_skyrocket.zip file to your sdcard, boot into recovery and choose "INSTALL FROM SDCARD" from recovery, install the file and reboot back into recovery to see if it installed correctly.
sk8erwitskil's CWM thread is here HERE , check to see if above file is the latest or dl the "Flashable zip" CWM file from there.
If upgrading TWRP go here HERE and follow the dev's instructions on using goo app, or you can use the flashable TWRP 2.4.1.0 file HERE and copy that file to your sdcard, boot into recovery and pick "INSTALL" from recovery, install the file and reboot back into recovery to see if it installed correctly.
How to enter recovery read section #2 below.
How to use cwm read THIS, also read Q&A on recoveries
You can upgrade to either CWM OR TWRP from which ever recovery TAR file you used in ODIN in step #2 from above.
10. You're done newbie and soon to be a power user, read and educate yourself as much as you can before flashing, happy flashing.
Click to expand...
Click to collapse
I don't know how to do step 9. Do I even need it? I have no desire to run a custom ROM.
yargdpirate said:
OK so here's the list of instructions I'm using to root my Skyrocket:
I have completed everything through step 4. I completely do not understand what to do after that. So, like I'm a 40 year old soccer mom, can you explain what I'm supposed to do to fulfill step 5? Is it through the odin app on my pc? Is this completed on my phone? The link provided that ostensibly explains to noobs how to do this (http://forum.xda-developers.com/showthread.php?t=1777970) doesn't adequately explain to me what I'm doing and where.
Help, please!
Click to expand...
Click to collapse
Assuming that you have successfully installed your custom recovery you then need to know which recovery you installed before you update it. If you used CWM you can get the updated version from the Skyrocket development thread. Put the updated CWM file on your SD card and flash that zip while in recovery. If you used TWRP you can update it through the app that it installed if it did install one. GooManager (someone correct me if I am wrong on the name) I think GooManager needs suoeruser privileges. So which recovery did you flash?
CodeNameRedNeck said:
Assuming that you have successfully installed your custom recovery you then need to know which recovery you installed before you update it. If you used CWM you can get the updated version from the Skyrocket development thread. Put the updated CWM file on your SD card and flash that zip while in recovery. If you used TWRP you can update it through the app that it installed if it did install one. GooManager (someone correct me if I am wrong on the name) I think GooManager needs suoeruser privileges. So which recovery did you flash?
Click to expand...
Click to collapse
Put the updated CWM file on your SD card and flash that zip while in recovery?
Click to expand...
Click to collapse
It's CWM. How do I
A. Put the updated CWM file on my SD card and
B. Flash that zip while in recovery? Is that through Odin, or what?
Thanks
yargdpirate said:
It's CWM. How do I
A. Put the updated CWM file on my SD card and
B. Flash that zip while in recovery? Is that through Odin, or what?
Thanks
Click to expand...
Click to collapse
i think you should stay on stock, read more b4 you brick your phone, no sense in rooting/installing custom roms when you dont know how to install a file on your scard, im not putting you down but trying to give you friendly advice
Vincom has a point. I taught myself through these forums and Google how to do it back in October of 2011. I flashed many a ROM and many files since then until I bricked mine Thursday. Now I have to pay 60 dollars to get it fixed. But on the upside I now have a Note II to play with.
Edit: She is asking for help though and she did ask in the right thread. Some people need more help than others.
vincom said:
i think you should stay on stock, read more b4 you brick your phone, no sense in rooting/installing custom roms when you dont know how to install a file on your scard, im not putting you down but trying to give you friendly advice
Click to expand...
Click to collapse
Oh. ****. I don't even want a custom ROM. I just want to be rooted and run stock with rooted google play store apps. Am I there?
I just want to run rooted apps with no ROM flashing...oh god why...where is the guide to root and only root?
You'd think this http://forum.xda-developers.com/showthread.php?t=1652398 would be where to go to do that, but evidently it's sending me down the road to custom ROM flashing. AGHGHGhjkdashbdas. Do not want.
Ok, so here's where I am, I have finished step 8:
1. Download Odin 1.85 .
2. Download(USE FIREFOX!) ClockworkMod TOUCH 5.5.0.4 OR TWRP 2.2.2.0, they are both named "recovery.tar.md5" and will be downloaded as "recovery.tar.md5", DO NOT CHANGE the filename or else it wont install.
3. Extract the contents of odin-185.zip to a folder.
4. Run Odin 1.85.exe from the folder you extracted it to.
5. Prepare Odin: Check "auto-reboot" and UNCHECK ALL OTHER OPTIONS. SEE COMPUTER SREEN PICS BELOW.
6. Only Click "PDA" and select the recovery.tar.md5 file you downloaded. SEE COMPUTER SREEN PICS BELOW.
7. How To Put your device into Download Mode: DO NOT TOUCH THE POWER BUTTON FOR THIS PROCEDURE. - download mode is NOT the same as recovery mode
a. Connect the USB cable to your PC, but NOT to your phone.
b. Remove the battery.
c. Reinsert the battery.
d. ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
DO NOT RELEASE THE VOLUME KEY(S) UNTIL INSTRUCTED TO DO SO IN STEP (f)
e. Insert the USB cable into your device. The phone will turn itself on when usb cable is inserted - DO NOT TOUCH THE POWER BUTTON.
f. You will now see a screen w/a yellow triangle warning you about installing a rom . Now release the volume key(s) - SEE PHONE PICS BELOW
g. Press and release the "Volume Up" key to enter into download mode - SEE PHONE PICS BELOW
h. You should now be at the Download Mode screen w/odin recognizing your phone. SEE COMPUTER SREEN PICS BELOW.
8. Click Start in Odin. It will flash the new recovery and will reboot the phone when completed. Your device will autoreboot into android. You are done using ODIN.
9. UPDATING CWM OR TWRP:
Now you need to udate CWM, download and copy cwm6027touch_v14.4.6_skyrocket.zip file to your sdcard, boot into recovery and choose "INSTALL FROM SDCARD" from recovery, install the file and reboot back into recovery to see if it installed correctly.
sk8erwitskil's CWM thread is here HERE , check to see if above file is the latest or dl the "Flashable zip" CWM file from there.
If upgrading TWRP go here HERE and follow the dev's instructions on using goo app, or you can use the flashable TWRP 2.4.1.0 file HERE and copy that file to your sdcard, boot into recovery and pick "INSTALL" from recovery, install the file and reboot back into recovery to see if it installed correctly.
How to enter recovery read section #2 below.
How to use cwm read THIS, also read Q&A on recoveries
You can upgrade to either CWM OR TWRP from which ever recovery TAR file you used in ODIN in step #2 from above.
10. You're done newbie and soon to be a power user, read and educate yourself as much as you can before flashing, happy flashing.
Click to expand...
Click to collapse
I don't know how to do step 9. Do I even need it? I have no desire to run a custom ROM.
For just rooting u have to run the superuser zip through your recovery
Oh and if you are not understanding what the stickies are saying to do then look it up on youtube because there are a lot of step by step instructions there.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
a. put updated file in your micro sd card.... plug ur micro sd card to pc... drag file and drop it in your micro sd card. put the micro sd card back in phone.
b. to go to recovery press power button + vol+ + vol- all at once and hold.
why do u need to unlock play store app? playstore is accessible completely even without root. you can also sideload Amazon appstore and other apps without root. no need to get all bricked up just to run playstore. i'm confused what are you trying to do again?
droidbabyxda said:
a. put updated file in your micro sd card.... plug ur micro sd card to pc... drag file and drop it in your micro sd card. put the micro sd card back in phone.
b. to go to recovery press power button + vol+ + vol- all at once and hold.
why do u need to unlock play store app? playstore is accessible completely even without root. you can also sideload Amazon appstore and other apps without root. no need to get all bricked up just to run playstore. i'm confused what are you trying to do again?
Click to expand...
Click to collapse
im guessing he wants to run apps from play that require root, eg titanuim backup, but he doesnt know how to put a file on his sdcard, but then he has to learn how to install zips from recovery which someones got to teach him since he doesnt want to read/learn/search for the answers. he seems to be impatient and wants it done "now", its a brick waiting to happen, my advice to him was to slowdown and learn
vincom said:
im guessing he wants to run apps from play that require root, eg titanuim backup, but he doesnt know how to put a file on his sdcard, but then he has to learn how to install zips from recovery which someones got to teach him since he doesnt want to read/learn/search for the answers. he seems to be impatient and wants it done "now", its a brick waiting to happen, my advice to him was to slowdown and learn
Click to expand...
Click to collapse
agree and such bad attituted too. i wouldn't want to help anybody who cusses in every conversation geez little respect goes a long way
It you just want to root and not want to flash any custom ROMs or anything related to it,I will tell you how to from total beginning
ALL DATA WILL BE LOST , BACKUP EVERYTHING
In order to root Android 4.2 the following three requirements must be satisfied beforehand:
The Android SDK, which you can download from Google Developers
A custom recovery like ClockworkMod (CWM) or Team Win Recovery Project (TWRP)
SuperSU, which you can download from CF-Root
There are no major differences between the two, but TWRP is more touch-oriented thanks to larger buttons. CWM is also available in a touch-compatible variant, but it has much smaller buttons. It's a matter of personal preference between the two though, but you have to choose one.
Before starting the process I urge you to perform a backup, as all data might be lost afterwards. You can copy the contents of the SD card to a safe external location such as cloud storage service or computer hard drive.
The first step that needs to be performed after all the files are downloaded is to install the Android SDK. Afterwards open the Android SDK Manager and select the following two items:
Android SDK Platform-tools -- it contains the required programs to install Android 4.2 Jelly Bean
Google USB Driver -- it contains the necessary drivers for the Nexus device
Then you should create a folder in an easily accessible location within the command line. In this example I will use a folder named "Root" in my C:\ drive in Windows. The path name will therefore be: "C:\Root".
From the folder where Android SDK Platform-tools is installed (in my case it is "C:\Program Files x86)\Android\android-sdk\platform-tools" copy the following files to the previously created "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
The following files must also be copied to the "Root" folder:
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery that you previously downloaded for your specific device (please see below)
For my 8 GB nexus 7 wifi(codename "grouper" I will use TWRP with the name "openrecovery-twrp-2.3.1.0-grouper.img".
You can easily find the codename for your devoice by looking into Google
The custom recovery file differs for each device, please make sure you download the correct file
In order to make the process smoother for instance the SuperSU file can be renamed to "root.zip" and the custom recovery to "customrecovery.zip". It's a matter of convenience, but for accuracy I will stick to the original naming for this guide.
If the previous steps are completed you must have the following six files in your "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery. In my case it is "openrecovery-twrp-2.3.1.0-grouper.img"
From there, you can proceed to install the drivers for "fastboot mode". To install them, follow these steps:
Power off your Nexus device.
Press and hold Volume Up and Volume Down then press and hold the Power button; the device will now enter "fastboot mode".
Go to Device Manager (Computer -> Properties -> Device Manager in Windows 7/8) and identify the device; for me it shows up as Android 1.0.
Right click Android 1.0 and select "Update Driver Software," then select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer," then click "Next".
From "Have Disk..." option go to the folder where you have Google USB Driver installed (for me it's "C:\Program Files .(x86)\Android\android-sdk\extras\google\usb_driver" and select "android_winusb.inf".
Out of the three options select "Android ADB Interface" and validate any future warning window to install the driver.
Final preparations
Everything is prepared in order to start the installation process, but in order to do so a command window must be opened. Windows Key + R opens "Run"; type in "cmd" and the command window appears. Typing "cd C:\Root" and pressing Enter sets the "Root" folder as the working directory. Pressing the Shift key and right clicking inside the "Root" folder will also deliver the same result.
The device must be turned on in "fastboot mode" which I have explained at step no.2 during the driver installation process, and obviously plugged-in to the computer. You then have to type in the following commands while in "fastboot mode":
fastboot devices -- this is just for verification purposes; if there is no listed device then the drivers have been improperly installed and steps 1 through 7 must be redone.
fastboot oem unlock -> you have to accept the prompt in order to continue -- this command will unlock the bootloader, but it will also erase the data on the device which is why a backup is necessary.
fastboot reboot-bootloader -- this will reboot the bootloader.
fastboot flash recovery openrecovery-twrp-2.3.1.0-grouper.img -- this will flash the custom recovery --please use the specific file and name for your particular Nexus device!
fastboot erase cache -- this will erase the cache -- might not be necessary but it's just as a precaution.
fastboot reboot -- this will reboot the device.
After Android 4.2 is loaded and running the SuperSU file must be copied from the "Root" folder to the internal storage (shows up in Windows Explorer as a Nexus device). A simple copy and paste will do the trick here.
Then you have to power off the Nexus device and enter "fastboot mode" again. Use the Volume Up and Volume Down keys to navigate until you can select "Recovery Mode". After the power button is pressed the device will reboot in the new custom recovery.
Rooting your Nexus device
If you have ClockworkMod installed, you have to perform the following steps:
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "0" (zero) folder
Select "CWM-SuperSU-v0.97.zip"
Select "Yes - Install CWM-SuperSU-v0.97.zip"
Select "Go Back"
Select "reboot system now"
If you have Team Win Recovery Project installed, you have to perform the following steps:
Press "Install".\
Select "CWM-SuperSU-v0.97.zip" -- for me it's in the "0" (zero) folder
Swipe to confirm flash
Press "Wipe cache/dalvik" (just as a precaution)
Swipe to wipe
Press "Reboot System"
After Android 4.2 loads your device can run apps with elevated privileges (meaning it's rooted). A SuperSU app is installed in order to allow root requests, so please use your judgement on which apps you grant access.
If you experiences any problem, please reply and I will look into it.
Sent from my Nexus 7 using xda app-developers app
Sent from my Nexus 7 using xda app-developers app
^^you want him todo that, lmao, he doesnt even know how to put a file on his sdcard to flash it in recovery, theres no way a computer newb is going to be able to follow what you posted
That's why I have not used the word flash anywhere, I know that he does not know how to flash , I have posted the right thing for a total noob,( at least if he knows how to use command in windows or install drivers)
I helped him in the way I could and what he requested
Sent from my Nexus 7 using xda app-developers app
You think that helped. LOL. Your telling him to do things that aren't even required to gain root with this device. Not everything is a nexus bro. Next time you wanna help study up on the phone your giving advice about. lol
Well , thanks for telling me that every android isn't rooted in same manner, I was thinking that all devices are rooted in same ways like for my nexus
Sent from my Nexus 7 using xda app-developers app
naman14, im not putting you down, your step by step howto is admirable, good work, but the problem is that the op is clueless on tech stuff, its not the word "flash" he has a problem with, i could of said "install" and it would lead to same conclusion, he doesnt know how to copy a file to his sdcard, if he cant do that he has no business in modding his phone until he learns more. anyhow the op is long gone by now
I upgraded my samsung skyrocket s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)
With the help of the ever awesome Team Win, and specifically a developer named Dees Troy we now have a working recovery for the I9505G.
[Update 8/22/2013]: Thanks to ClockworkMod developer gweedo767, the official CWM Recovery for I9505/jfltexx/International GS4 is now fully compatible with I9505G/jgedlte/GS4 GPe. Download either the regular or Touch version here (scroll down to "Samsung Galaxy S4 (i9505)"). Also, official CM 10.x and CM 11 nightlies for I9505/jfltexx are now fully compatible with I9505G/jgedlte, without any modifications.
Here is the guide to get both the recovery and CM 10.x/11 onto the GS4 GPe GT-I9505G:
Assuming you are on a Windows machine.
First we need to install the USB drivers:
Download and install Android SDK tools from here.
Run "SDK Manager.exe" from wherever you installed Android SDK in previous step.
Under "Tools" section select "Android SDK Tools" and "Android SDK Platform-tools". Under "Extras" section select "Google USB Driver."
Click the "Install" button and wait for installation to complete.
Exit the SDK Manager program.
Now unlock the bootloader (according to some people this step may not be necessary):
Boot up device normally, skip setup or do minimal setup - NOTE: you will wipe your phone during this process, so don't go nuts yet on config/installing apps.
Go to Settings --> About Phone
Tap Build Number 7 times, go back to Main Settings Menu and under now shown Developer Options enable USB debugging.
Plug into PC and ensure the phone is recognized.
On the phone accept the footprint signature popup - if it DOESN'T appear unplug/replug USB cable.
Under Command Prompt or Terminal on PC type in "adb devices" and press Enter. Ensure it shows the device and doesn't show "Offline" - if it does repeat steps 4-5.
Under Command Prompt or Terminal type in:
Code:
adb reboot bootloader
and press Enter.
Once in bootloader, on your PC Command Prompt type in:
Code:
fastboot oem unlock
and press Enter. Note that in Linux you will need to run fastboot with elevated privileges, i.e.
Code:
sudo fastboot oem unlock
.
Accept unlock using Volume key, and confirm with Power button - device will reboot possibly a few times, once rebooted and in device you can sign into accounts - REPEAT step 2-3 to re-enable USB debugging.
Now we can get down to flashing a custom recovery:
Un-install all existing Samsung drivers from your PC. This includes Kies program. I can't stress enough how important this step is for avoiding issues with flashing images via Heimdall or Odin.
Download the latest version of Heimdall from here and extract the ZIP to a folder on your hard drive (e.g. C:\Heimdall\ )
Download and install Microsoft Visual C++ 2012 redistributables package from here. These are required to have Heimdall work properly.
Download either the latest TWRP recovery from here, or latest official ClockworkMod Recovery for I9505 here and place the .IMG file into the Heimdall folder.
Shut down your phone, disconnect it from USB, and turn it on by holding Home + Volume Down + Power buttons together. This will start the phone in the Download mode. *NOTE: It is very important to get into the Download mode from a switched off phone. If you are coming from a different custom ROM, do not simply reboot into download mode (via advanced reboot option, or via "adb reboot bootloader" command) as that will cause issues with Heimdall and Odin.
Connect the phone to your computer via USB.
Run zadig.exe included in the "Drivers" sub-directory of Heimdall installation. From the menu chose Options -> List All Devices. From the USB Device list chose "Samsung USB Composite Device", or "MSMnnnn" - basically the S4. Press "Install Driver", click "Yes" to the prompt and if you receive a message about being unable to verify the publisher of the driver click "Install this driver software anyway". Your phone should now be recognized by Heimdall.
Open Windows Command Prompt and navigate to the directory where you extracted Heimdall. Now type in the following command:
Code:
heimdall flash --RECOVERY file-name-of-recovery-image-here.img --no-reboot
and press Enter. This will flash the recovery. Disconnect the USB cable, and hold the Power button until the phone vibrates. Now hold Home + Volume Up + Power to boot into the recovery.
Now we can flash the i9505's CM nightly:
Once in Recovery mode, connect your phone to USB. You may need to once again install the USB drivers. Just point it to \extras\google\usb_driver\ folder and select "Samsung USB Composite Device".
Perform a backup if you wish (highly recommended!)
Back on the computer, download the CM nightly build (10.x or 11) for the i9505/jflte from here.
Download the latest GApps package appropriate for the CM version you downloaded in previous step from here. (CM 11 compatible gapps, especially those working with new ART VM are currently in flux, but someone put together images of most used ones here).
Back on the phone in Recovery mode perform a full wipe (system, data, cache, and dalvik-cache.)
Flash the files in the following order: 1) CM nightly 2) GApps zip 3) Any other ZIPs you usually flash.
Reboot.
At this point your phone should be booting CyanogenMod. Should something go wrong, follow instructions in donovanbrock's thread to flash back to the stock GE firmware.
Older CM 10.1 ROMs for jfltexx used an outdated syntax for MOUNT command that required an edit to the updater-script, as described here. However, latest CM 10.x and all CM 11 nightlies converted to using a new mount syntax that does not need any modifications.
Working:
Root (superuser) without having to flash or install other packages.
Wi-Fi
Cell data (with LTE)
GPS
Bluetooth
NFC
Vibration
A/C and USB charging
Voice calls
Notification lights
All sensors
Both cameras
Physical and capacitive buttons
Google Apps (Gmail, Play Store, etc.)
Wi-Fi Tethering.
Not Working:
IR Blaster - CM doesn't have official support for it yet. Only apps that access IR modules via root methods will work (e.g. IR Universal Remote.) The functionality has changed from Android 4.3 to 4.4, so it will take some time for CM team to get it working properly. It should make it into CM eventually.
Sometimes when you simply reboot the phone, it gets stuck on the Google logo and doesn't proceed to boot into CM. This seems to be a known issue for the GS4 models and CM, which might have been introduced with SELinux commits. Experts think this is due to a race condition during initial boot-up phases, and are working on a fix. For now the work-around is manually ejecting the SD Card, and immediately putting it back in.
Untested:
Wireless display.
HDMI-out
Thanks and acknowledgements:
Team Win for TWRP recovery, especially Dees_Troy for making it work on I9505G.
CloclworkMod team for the CWM recovery, especially gweedo767 for getting it to work on I9505G.
CM Team for the ROM.
@donovanbrock for the flashing back to stock guide.
@NPS_CA for the bootloader unlock instructions.
Google for Android, and JBQ for AOSP.
WinZip
I claim no credit or ownership of any of the above. The pieces were already out there, I just put them together.
All the linked files are here.
Android SDK tools
Project page: http://developer.android.com/sdk/index.html
Direct download (Windows): installer_r23-windows.exe
Heimdall 1.40
Project page: http://www.glassechidna.com.au/products/heimdall/
Direct download (Windows): heimdall-suite-1.4.0-win32.zip
Support files: Microsoft Visual C++ 2012 redistributables.
Official TWRP recovery for I9505G/jgedlte
Project page: http://teamw.in/project/twrp2/192
Direct download: jgedlte.img
Official CWM recovery for I9505/jfltexx (fully compatible with I9505G/jgedlte)
Project page: http://www.clockworkmod.com/rommanager
Direct download Regular version: recovery-clockwork-6.0.4.7-jfltexx.img
Direct download Touch version: recovery-clockwork-touch-6.0.4.7-jfltexx.img
CM 10.x or 11 for the i9505 (jflte)
Download page: jflte nightlies
Latest GApps package for 4.2.x or 4.3.x (CM 10.x)
Project page: http://goo.im/gapps
Direct download for 4.2.x/CM 10.1: gapps-jb-20130812-signed.zip
Direct download for 4.3/CM 10.2: gapps-jb-20130813-signed.zip
Latest GApps images for 4.4.x (CM 11)
XDA-developers link: http://forum.xda-developers.com/showthread.php?t=2012857
Bonus: 4.3 Camera with Gallery that preserves Picasa Albums sync
Downloads: jb-43-camera-gallery-picasa.zip and jb-43-camera-gallery-picasa_lib.zip
Instructions: Flash both these files in Recovery AFTER flashing the ROM and GApps packages.
Excellent tutorial, thank you. Really happy to see some progress on custom ROMs for the 9505G. Hopefully we will have some custom kernels soon too!
Been waiting on the final version of TWRP. Just flashed. Good work guys!!! :good:
donovanbrock said:
Been waiting on the final version of TWRP. Just flashed. Good work guys!!! :good:
Click to expand...
Click to collapse
Well, it's not final until it shows up on http://teamw.in/project/twrp2 but it's close enough.
I keep getting error:
Code:
Installing '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip.md5
Skipping MD5 check: no MD5 file found.
line 1 col 93: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
E:Error executing updater binary in zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Error flashing zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Any work need to be done to /META-INF/com/google/android/update-binary
?
Has anybody done a successful restore and backup using TWRP? Also silly questions but will the touchwiz roms work on this phone? I was going to do a backup and attempt flashing different ROMs for 9505 or should I hold off?
Thanks all and very nice work
donovanbrock said:
I keep getting error:
Code:
Installing '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip.md5
Skipping MD5 check: no MD5 file found.
line 1 col 93: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
E:Error executing updater binary in zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Error flashing zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Any work need to be done to /META-INF/com/google/android/update-binary
?
Click to expand...
Click to collapse
Could be pastebin messed up the formatting of the updater-script. I'll upload from my original source in a minute.
Edit: Done. Try the file attached in this post, and if it works I'll replace in OP.
Chahk said:
Could be pastebin messed up the formatting of the updater-script. I'll upload from my original source in a minute.
Edit: Done. Try the file attached in this post, and if it works I'll replace in OP.
Click to expand...
Click to collapse
Yah buddy.. update your OP. The new files worked flawlessly. :highfive:
Worked for me as well. Very happy to see CM on our GE S4's.
I would like to add this, though: I've performed every step successfully without ever performing a "fastboot oem unlock". In other words, I'm currently running TWRP + CM10.1 without unlocking my bootloader. May be worth noting. Either way, good work everyone.
Thanks for this! Subscribed.
Gave this a try and can't get it working at all and now my phone just keeps booting into recovery.
When I trying wiping it takes forver (which I assume is it timing out) then I get:
E: Failed to Wipe dalvik
E: Unable to mount '/preload
Then the recovery ends with Failed
When I try flashing I just get error flashing:
Unable to mount /preload
Then just says failed.
Anyone have any thoughts? I tried re flashing the recovery... No luck.. Should also mention the recovery is prompting me for a password when I first get into it (which I never set) and I'm just hitting cancel...
Not for nothing guys, But why would anyone buy the GE Galaxy S4 when you can just buy the i9505 or the T Mobile variant which is literally what the GE is with a different bootloader. Its also $100 cheaper than the GE. with the GE you are **** out of luck with running touchwiz roms for now and you have to struggle to get CM 10.1 working when its already here and flawless on other variants..
drdingo21 said:
Gave this a try and can't get it working at all and now my phone just keeps booting into recovery.
When I trying wiping it takes forver (which I assume is it timing out) then I get:
E: Failed to Wipe dalvik
E: Unable to mount '/preload
Then the recovery ends with Failed
When I try flashing I just get error flashing:
Unable to mount /preload
Then just says failed.
Anyone have any thoughts? I tried re flashing the recovery... No luck.. Should also mention the recovery is prompting me for a password when I first get into it (which I never set) and I'm just hitting cancel...
Click to expand...
Click to collapse
Are you using the recovery I linked to?
Also, when modifying the ROM zip, make sure you are not editing the updater-script or build.prop files in an editor that will mangle line endings like Notepad. Try an advanced editor like Notepad++ instead.
Chahk said:
Are you using the recovery I linked to?
Also, when modifying the ROM zip, make sure you are not editing the updater-script or build.prop files in an editor that will mangle line endings like Notepad. Try an advanced editor like Notepad++ instead.
Click to expand...
Click to collapse
Yep! Everything from your op. are you not getting a password prompt?
I also didn't edit the files. I just dropped them into the Zip
drdingo21 said:
Yep! Everything from your op. are you not getting a password prompt?
I also didn't edit the files. I just dropped them into the Zip
Click to expand...
Click to collapse
No, no password prompts here. Can you try re-flashing the recovery via download mode again?
I heard the LTE bands are different for the phone because of the locked radio and modem. Only the GE edition can operate on both US carriers.
Sent from my GT-I9505G using xda premium
Chahk said:
No, no password prompts here. Can you try re-flashing the recovery via download mode again?
Click to expand...
Click to collapse
Alright. New computer with windows JUST installed.
When I flash the recovery and reboot it doesn't boot into recovery right away. It sits on the Teamwin splash (which it did before) but a reboot gets me into recovery. I still get the password prompt. I re downloaded everything in the OP. Is there somewhere else I should try grabbing the recovery?
---------- Post added at 09:46 PM ---------- Previous post was at 09:16 PM ----------
So I fixed my problems.
I've had my phone since they day they were shipped. I just tried the how to above with out any kind of wipe before hand.
I reflashed the stock recovery then did a full wipe and then wiped the cache again to be sure. Reflashed the attached recovery and all is well! I assume there was something making twrp think there was a password.
thanks for the tutorial!
Can your tweaked installer be used in the same way to make other 9505 ROMs and kernels work on the 9505G?
i had to change zadigto libusb0 (v1.2.5.0) from the default WinUSB (v6.1.7600.16385)
then everyting worked
i know have twrp on my i9505G.
btw if you boot the file using fastboot the touchscreen dose not work but once you flash it it works.
Heya,
Since there is not enough info on the web regarding the rooting procedure for Videocon A55 HD and custom recovery for this awesomely smooth device, I'm uploading the necessary files and step by step guide. Hope it helps all the users of this device.
Remember rooting would tamper the warranty of the device and should be exercised carefully. The procedures mentioned below have been personally tested by me however I take no responsibility in case you ruin your device although I would be here to help you in such a scenario. Besides this the rooting script was not created by me and all the credit goes to the respective developer.
1. Rooting Procedure
Make sure you have enabled "USB Debugging" under Developer Options on your phone.
Keep your phone disconnected from computer via USB
a) Download and Install the ADB Interface driver for MTK 6589
Link to ADB Drivers
b) Download and extract the rooting package
Link to the Rooting Package
c) Now go to the extracted package and open a command prompt to that location as Administrator.
d) Type run.bat in Command Prompt and a message must appear "Press enter to root your phone..."
e) Press any key
f) Now after a few seconds the message should be " * daemon started successfully *"
g) Now connect your phone via USB to the computer
h) The cmd would automatically start pushing the necessary files onto your phone and when the process completes your phone will restart
Now you are rooted.To check install any Root checker application from playstore. Remember to grant permission while running Root Checker app when a pop up appears. It is suggested to update the SuperSU app from playstore and execute it at least once after that to update the su binary. You can also update the busybox package from playstore because busybox supplied with the rooting package is pretty old.
2. Installing CWM Recovery
Okie, since you are now rooted, most likely you would require a custom recovery to create full nandroid backups or test different ROMs. The CWM recovery provided here was created using MTKDroid Tools and is version 5.x (Non Touch). Again all credit goes to the developer of MTKDroid Tools for making such a powerful piece of software.
a) Download and extract the recovery package.
Link to CWM 5.x and Original Recovery for A55 HD
b) There are two files in the package , one is the custom CWM recovery and the other one is Stock Recovery (Names are pretty self understood)
c) Copy "Custom_Recovery_CWM_A55HD.img" to the root of your SD card
d) Rename it to "recovery.img"
e) Install Mobile Uncle Tools [MUT] from the playstore.
f) Open MUT and go to recovery update
g) Now you must see the recovery.img in a list. Just select it and follow the pop ups.
h) Now your phone would restart.
i) To check if the recovery update was successful, go to MUT and select "Reboot into Recovery" and your phone would most likely start in CWM recovery..
Alternative to get into recovery mode is to Press Power button + Volume Down key together when switched off.
3. Stock ROM for Videocon A55 HD
Okie, here we go, as I mentioned that I had got hold of the stock rom, so here I'm publishing it. The credit goes to Pratap Solunke (psolunke) for providing the Factory ROM zip.
I have just divided it into update.zip and files for SPFT for ease of downloading. Besides I have splitted each section into 4 parts and reuploaded it so you can download them at your ease. I'm providing the link for the whole folder which includes the changelog, update.zip and files for SPFT.
The ROM version is V7 (2013.07.15) which is different from the original ROM which was V5 (2013.06.08).
You can read the changelog for the updates in this ROM.
Link to ROM Folder
If using update.zip to flash this ROM, then
Step 1. Open the update.zip with winrar, Do not extract.
Step 2. Navigate to \META-INF\com\google\android\updater-script and extract this file only, then use "Notepad++" to open the file.Don't use default notepad.
Step 3. Delete assert(getprop("ro.product.device") == "A55HD" || getprop("ro.build.product") == "A55HD");
Step 4. Save the file, put it back to the same location in archive (It will take some time to add to archive)..Done...then proceed as usual.
a) update.zip is for reinstalling Factory Image of the ROM from recovery mode. The zip file is signed.
b) Files for SPFT are to be used with SP Flash Tool and can be used in case your phone is bricked. Do not flash the preloader unless you know what you are doing.
c) To download the files just go to the respective folder and right click on each file and hit download. After all four parts are downloaded, extract Part 1 of the downloaded splitted files and the files would be ready to be used as is.
d) Keep all four parts of the splitted files in a single folder and do not rename the splitted files.
If you have any questions related to A55 HD you can ask them here and I would try to help you the best way I can.
I'm still testing some custom ROMS but none seem to work . So far I've tested LEWA OS and MIUI ROM for xiacoao G6 Youth. However I'll keep trying and update once I have a working Custom ROM.
One more project in mind is to port Custom ROMS to A55 HD if none is available as is on the web.
If anyone of you is able to find a working Custom ROM for A55 HD kindly post it here so that we can have a repository of successful and useless attempts. I'm sure it would help others.
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also. All the recoveries shown in the list are only remote recoveries
nanachitang420 said:
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also. All the recoveries shown in the list are only remote recoveries
Click to expand...
Click to collapse
I forgot to mention , rename the recovery image to "recovery.img" and then put it in root of SD card and it would get detected by MUT...It will get detected instantly...Thankyou for bringing it to notice...Just updating the post...
done but some observations!!!!
DONE.
Some observations:
1. In CWM, cant see internal SD card. While, after mounting usb storage, can see external SD card only. NOTE, CANT SEE INTERNAL SD CARD ONLY WHEN TRY TO MOUNT INTERNAL PHONE STORAGE IN CWM. WHILE NORMAL WORKING NO PROBLEM.
2. Deleted.
3. Deleted.
4. Deleted,
5. Deleted.
6. The font size of Stock and CWM recovery is very small still it can serve the purpose.
Do any body have original/stock update.zip from Company?
Updates:
I think I figured out the problem with touch. Uninstalled an application called "Go Power Master" and the touch is ok even after connecting USB or charger. Thanks man. The phone is working very nice after rooting.
nanachitang420 said:
DONE.
Some observations:
1. In CWM, cant see internal SD card. While, after mounting usb storage, can see external SD card only.
2. After rooting, before even installing CWM, got some irratic behavior with touch. Like, while USB is connected, touch was not working as expected, it took long time to make USB storage active as after touching a specific required operation, like pulling down task bar it was doing something else like opening play store, opening game, or opening date and time settings. While unlocking lock screen, it was just opening any random phone application and is not even allowing to go back with back button or home button. Don't know this is related with what?
3. Irratic application were opening while touching different application but after removing USB, things were working better.
4. Rebooted in CWM and first tried to "fix permissions" to avoid that irratic touch behavior, thinking there was problem with permissions. Took nandroid back up, after fixing permissions. Wiped cache and dalvik cache and restarted.
5. Now, till now phone is not connected to PC with USB cable or connected to charging; it behaves better with touch but it is very troublesome to perform any operation after phone connected to PC with USB or to charger.
May be you have faced these issues or may not! Any suggested solution? Do any body have original/stock update.zip from Videocon?
Updates:
I think I figured out the problem with touch. Uninstalled an application called "Go Power Master" and the touch is ok even after connecting USB or charger. Thanks man.
Click to expand...
Click to collapse
For me the touch works without any problems...and as for detecting internal sd card...that also works flawlessly..i don't have the phone with me right now...Yesterday I was trying something and the nvram got corrupted [No baseband]...so right now it is resting at service center...Hope to get it next week...
One suggestion never install Carliv Touch Recovery on this phone...it messes with the baseband and display...Stick to this recovery until I build a more updated CWM...
Latest V-Store attached
Attached
nanachitang420 said:
Attached
Click to expand...
Click to collapse
Nice...let's make this thread a repository of A55 HD..And I have also got hold of the original update.zip and files for SPFT ...Will split them and upload to my google drive...and then share them..
update.zip
Aaaaanuj1 said:
Nice...let's make this thread a repository of A55 HD..And I have also got hold of the original update.zip and files for SPFT ...Will split them and upload to my google drive...and then share them..
Click to expand...
Click to collapse
The current version of my phone is 08062013. Can I flash this latest version through CWM and upgrade?
Tried to flash update.zip through CWM...
Installing: /sdcard/update.zip
Finding update package...
Opening update package....
Installing update....
assert failed: getprop("ro.product.device")=="A55HD" || getprop("ro.build.product")=="A55HD".
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Restored nandroid backup after this.
nanachitang420 said:
Installing: /sdcard/update.zip
Finding update package...
Opening update package....
Installing update....
assert failed: getprop("ro.product.device")=="A55HD" || getprop("ro.build.product")=="A55HD".
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Restored nandroid backup after this.
Click to expand...
Click to collapse
Okie it is an easy fix...
Step 1.Open the update.zip with winrar, Do not extract.
Step 2.Navigate to \META-INF\com\google\android\updater-script ,use "Notepad++" to open the file.Don't use default notepad.
Step 3.delete assert(getprop("ro.product.device") == "A55HD" ||
getprop("ro.build.product") == "A55HD");
Step 4.Save the file, update to archive..Done
Done
Successful.
Please add in above step 2 "to extract file Updater-script on PC" and then use N.........
Flashed modified update.zip from CWM and phone upgraded to version 15072013. To be strange it is showing v1.0 20130715 in build ie in about phone. All the applications were intact but lost root and also CWM recovery; then managed to root the phone and flash CWM with your fantastic guide.
After booting in CWM, wiped cache and dalvik cache(why? don't know). Phone is working nice. Thanks,
nanachitang420 said:
Successful.
Please add in above step 2 "to extract file Updater-script on PC" and then use N.........
Flashed modified update.zip from CWM and phone upgraded to version 15072013. To be strange it is showing v1.0 20130715 in build ie in about phone. All the applications were intact but lost root and also CWM recovery; then managed to root the phone and flash CWM with your fantastic guide.
After booting in CWM, wiped cache and dalvik cache(why? don't know). Phone is working nice. Thanks,
Click to expand...
Click to collapse
Nice...Yeah, people at Videocon forgot to change the version number i guess...and loss of root and cwm was due to restoring of system.img and recovery.img in the ROM file...so it's normal..
Besides one should always perform a clean install from CWM..i.e. Clear Data, Clear Cache, Clear Dalvik Cache, Format /system/ and then install ROMS..
And yes this ROM is a bit better then the one on phone..I received my phone today from service center and software was updated to this ROM..It felt much better .And the version was same , so this seems to be the latest ROM for A55 HD.. Enjoy
How to flash phone with sp flash tools
was trying to flash a recovery build on CWM site. I think it has spoiled baseband. No sim is getting detected. Any idea how to flash phone with SP tool? Don't have access to service station as am very far.
Edit: Managed to flash with SP tool. Used the files you have uploaded for SPFT. Selected all options and now phone is on and showing base band version, also sim are getting detected. The issue was preloader drivers for windows 8 which managed to install by disabling driver signature verification. Device rooted and installation of CWM through MUT was successful. Thanks.
Try this and this. Its as good as custom rom installation works very well with MTK6589
nanachitang420 said:
was trying to flash a recovery build on CWM site. I think it has spoiled baseband. No sim is getting detected. Any idea how to flash phone with SP tool? Don't have access to service station as am very far.
Edit: Managed to flash with SP tool. Used the files you have uploaded for SPFT. Selected all options and now phone is on and showing base band version, also sim are getting detected. The issue was preloader drivers for windows 8 which managed to install by disabling driver signature verification. Device rooted and installation of CWM through MUT was successful. Thanks.
Try this and this. Its as good as custom rom installation works very well with MTK6589
Click to expand...
Click to collapse
You must understand that the recovery partition is of 6 mb....and most likely the recovery you received from CWM online builder was more than 6 mb..hence your secro.img was also overwritten...hence the problems with baseband and imei....same thing happened with me 7 days back when I had to submit my phone to Service center. Unfortunately i didn't had the flash image then but it is good to know that it can also recover baseband and imei. And congrats for recovering your phone and I'm glad my contribution helps you...
Just remember one thing...if the boot, recovery,secro partitions are of more than 6mb then don't flash them as they would mess one thing or other...and hopefully you had disabled preloader in SPFT.....if not then from next time onwards please do it....because rarely you need to flash preloader...and a wrong flash can make your device a brick which can only be recovered by Test points.Hence never flash preloader until unless you know what you are doing.....And yes, I already use Gravity Box along with Xposed Framework...Great mod...Besides them I also use xhalofloatingwindow with bubble launcher and lwinrecent ...Both are xposed modules and work as expected.I also have init.d support which allows to make boot persistent changes on device....Along with that a few build.prop tweaks that take my ROM to the custom level...Let me know if you need any of this...
Please
Thanks for preloader advise. was not that much aware and will take care next time. Please share init.d support, build.prop tweaks and their usefulness.
For init.d, use term-init by ryuinferno.
http://forum.xda-developers.com/showthread.php?t=1933849
This is the link to the thread. Do not use zip-init or uni-init. Follow the guide on the thread. It works flawlessly.
Sent from my A55HD using Tapatalk
Which other phones has MTK6589 and same config ?
Tell me model number and brand, i will try to upload stock firmware.
it will help us built custom rom with custom features.
@anuj - Anyways if it brick again and need to send service center, please text me imei and location, i will make it done fast for you dear.:fingers-crossed:
Thank you Pratap bro. I'll let you know next time if I get to the point where I need to go to service center but I'm sure that with the ROM you provided I wouldn't need to go to one. And yes people you can ask for stock ROM from Pratap. He has excellent connections and can get you at least the Videocon ROM and may be others . Don't forget to thank him. Besides he is an excellent person who wouldn't shy away from helping you if he can. Ciao Pratap brother.
Sent from my A55HD using Tapatalk
Any new updates from Videocon for our A55HD?
File not found
File not found bro