[Q] How to upgrade stock ROM/Firmware with rooted/CWM Phone? - Android Q&A, Help & Troubleshooting

Hello,
I have rooted the Galaxy Notes SGH-i317M, and install the CWM recovery.
The question is how can I do the stock update, for custom ROM it's look easy just ue CWM. I tried to search for the answers for the last few days, but nothings is conclusive?
1. I have tried with ODIN Mobile, while it was able to keep the root (with everroot), it lost the CWM (it sent back to stock recovery), so I have to reinstall it
2. With Desktop ODIN, then the root and CWM is gone, so have to reinstall it (both ODIN and CWM) and restore apps/data though a backup (like titanium backup)
And a side question is there a site that I can download the OTA update or I have to wait it push to the phone and don't install it, and follow this procedure?
Download the OTA package
Open it on your computer, and delete the recovery folder from inside the .zip file
Place the zip file on the root of your SD card
Unless you're able to mount the system and edit file permissions while in recovery, install OTA Rootkeeper from the market and run it
Reboot into CWM and make a backup
Flash the OTA package you put in your sdcard folder in step 3
Reboot, rerun OTA Rootkeeper, or chmod 4755 /system/bin/su while in recovery then reboot
Click to expand...
Click to collapse
Thanks

Related

[Q] clockworkmod recovery help

After flashing clockworkmod recovery via rom explorer my phone will not boot into clockworkmod recovery- only the stock android recovery mode. I did notice that the clockworkmod "recovery-update.zip" file contains files that *look* like they want to be in the root directory (ie /sbin/*), but some of these files do not exist in my root directory. I'm guessing maybe that rom manager did not successfully extract the contents of this zip file? Should I manually copy the contents of this zip file over to my root directory?
When you boot into recovery from ROM Manager..you may need to hit "reinstall packages" a couple of times
yup
Thanks, that did it.

Failed Update 3/29/12 (Red Exclamation) Fix[[All Firmware]]

WARNING
If your bootloader is unlocked and you flashed a custom recovery, YOU WILL BRICK YOUR DEVICE BY ATTEMPTING THE STEPS BELOW!
Description
This method will allow you to apply any ICS or Honeycomb update to your tablet, no matter what the SKU of the update. This makes it possible to switch SKU's (eg. from WW to US) or to downgrade from ICS to Honeycomb. This means non US tablets can install the 9.4.2.13 US version or downgrade to 9.4.2.11 or even Honeycomb if experiencing problems.
Requirements
root access
ADB access
Disclaimer
While this process appears to work on everyone's device, you have to assume all risks due to unforeseen circumstances and need to understand there is a risk of bricking your tablet during the update. Although someone else was successful in downgrading from ICS to Honeycomb, there has been a report of a TFP bootlooping. Everyone else has been successful in downgrading from ICS 9.4.2.13 to ICS 9.4.2.11.
UPDATE: 2 reports so far of tablets bootlooping after downgrading to Honeycomb.
Notes
It's possible OTA updates will not apply when switching SKUs. However, you can always switch back to the proper SKU once an update is available. The Honeycomb update may wipe all data so ensure a full backup of apps & data is performed (eg. by using Titanium Backup) It's not recommended to restore "system" data using Titanium Backup when changing between Android versions When downgrading to a previous version of ICS, "Launcher" will force close requiring to wipe Launcher data in the Apps menu. Voodoo Rootkeeper may not be able to restore root after updating to 9.4.2.13. The "blob" file is contained within a ZIP file contained within the downloaded ZIP file.
Instructions
1. Download one of the updates (eg. US_epaduser9_4_2_13UpdateLauncher.zip) from here: http://support.asus.com/download.asp...2&hashedid=n/a (older firmwares are available at the end of this post) 2. Extract files from within zip 3. Extract files again from the extracted zip 4. Copy extracted "blob" file to root of folder of the removable Micro SD card or some other folder 5. Through ADB shell or Terminal Emulator, run the following: (May take from 5 to 20 minutes) Code: su dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
If copying the "blob" file to the SD card in the keyboard dock, use: dd if=/Removable/SD/blob of=/dev/block/mmcblk0p4 If copying it to the internal memory, use: dd if=/sdcard/blob of=/dev/block/mmcblk0p4
6. Reboot only if the following is displayed: Note: This may take up to 10 min so be patient
1068769+1 records in 1068769+1 records out 547210197 bytes transferred in 153.991 secs (3553520 bytes/sec)
7. Update process will automatically launch 8. OPTIONAL: Once booted up, root device by using Mempodroid Root or some other method that supports the new version.
8. Now install new firmware. Go to Settings-About Tablet-system firmware
Older Firmwares
8.8.3.33 US: http://dl.dropbox.com/u/8822437/Upda...er8_8_3_33.zip
we already have this In developement section. its been there for the longest time now. good info though
demandarin said:
we already have this In developement section. its been there for the longest time now. good info though
Click to expand...
Click to collapse
I know just reposted it for those that don't visit the forum often
It worked.....yes
So I have WW version and was rooted and tried to OTA update to 4.2.2 and got the red triangle.
After much looking on these threads and help from a user I proceeded to do the dplpkgfile method, copy file and command etc to cache and cache/recovery. temp unroot and tried recovery.
It still wouldnt work so did a factory reset and still no go.
Even tried manually installing firmware by placing it on an sd card, that failed as did renaming the firmware on the sd card and trying recovery
So I am at a loss.. I havent modified build.prop or frozen any apps.. Don't know what else I can try to get this thing to update.. Should I try to do full unroot with Super SU?
Appreciate any help
Cheers

[Q] accidentally move a file (services.jar) from system folder in the root folder

hello guys.
i have root my huawei ascend y300. I accidentally move a file (services.jar) from system folder in the root folder on my sd card. after that my phone restart and stuck on bootanimation. ive tried to reset and wipe cache but it doesnt work. Is there any way to put that file back in my root folder back. i dont have twrp or clockworkmod on my phone. please help.....
ErsaF said:
hello guys.
i have root my huawei ascend y300. I accidentally move a file (services.jar) from system folder in the root folder on my sd card. after that my phone restart and stuck on bootanimation. ive tried to reset and wipe cache but it doesnt work. Is there any way to put that file back in my root folder back. i dont have twrp or clockworkmod on my phone. please help.....
Click to expand...
Click to collapse
If you can find one from a your rom on this site you could push through adb.. but if you can't then no.. With no custom recovery or back up of that file there is no way..
Do you have a way of refreshing your stock rom? If so do that
Sent from my SCH-I605 using xda app-developers app
Yep, your choices are custom recovery (which also requires you to unlock your bootloader), and you can make a flashable zip with the services.jar file you need or reflash the entire stock rom. Lesson learned: don't make changes to the system without having a custom recovery and a backup.
Restore to stock guide: http://www.modaco.com/topic/366519-need-flashing-tool-for-g510y300/#entry2174570
Link for official stock rom from Huawei: http://download-c.huawei.com/downlo...loadId=18269&version=25763&siteCode=worldwide
Drivers: https://files.dc-unlocker.com/backend/r.php/public/EF65FFC8D36E40118BE98BC29A9C1216

Removing TWRP, or stock android ROM

Im giving my HTC Desire 610 to a family member, but want to remove everything from the phone. i have unrooted the phone, and tried to update to the newest android, but when the phone reboots, it comes up with TWRP. Is there a way to remove TWRP, and replace it with just the stock recovery, and so everything would be as if it was fresh out of the box?
Well, first, re-root it. Then download the stock recovery.img file and download flashify, install the stock recovery.img through flashify. Then, delete the supersu ask from your system apps folder and/ or your data apps using a file explorer, then in a file explorer again go to system/ xbin and delete the su file, and then you will have uninstalled twrp and root
MGfusion said:
Well, first, re-root it. Then download the stock recovery.img file and download flashify, install the stock recovery.img through flashify. Then, delete the supersu ask from your system apps folder and/ or your data apps using a file explorer, then in a file explorer again go to system/ xbin and delete the su file, and then you will have uninstalled twrp and root
Click to expand...
Click to collapse
and relock bootloader. But even than, i thing firmware update will not working, because bootloader is "tempered".

Cyanogenmod error 7, tried solutions but I'm not getting anywhere, help a noob please

UPDATE 6/19
So I installed CM12 12 or 13 require 23C, 24B, or 35 (TWRP 2.8. has those versions mentioned in the fail error script)
I kept getting the boot error and so I started over and flashed KDZ's in order from 10 to 23c
With the 23c you can use the one click program to root but also have the bootloader that CM12 OR CM13 needs
After root the error code did not show up
After bustbox the error did not show up
I used TWRP manager app to install 4 different TWRPs, all gave a boot code error and would reboot to CM or stock but obviously something was wrong
So then after research I found others that had trouble and used Autorec to solve the issue
Autorec:
http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
UPDATE 6/15 - Bootloader error?
It says:
SECURE BOOTING ERROR!
ERROR 1003
So I updated to 24B and I have CM 12.1 running. I did notice a boot error "error 1003" right before TWRP opened to install the ROM and just before the cyanogenmod boot screen popped up - Is that going to be okay, everything seems to be working fine?
How I got the ROM installed
1.) Flashed 24B using KDZ flash tool and file
2.) Root - Only king root from here worked (click unknown sources, also Google stopped the install so I had to out it in airplane mode and open the apk): http://forum.xda-developers.com/lg-g...3129197/page84
3.) Installed busy box, TWRP, SuperSU asked to update the binary.
4.) Download cm 12.1 files tot the TWRP backup files
5.) Reboot into TWRP recovery
6.) backed up phone so you don’t have to get root again
7.) wipe - factory reset - wipe dalvic and cache again
8.) Installed CM 12.1 and rebooted system
Original issue: Failed ROM flash on 12B and TWRP3.0
See recovery log below
The only thing I can think if now is that I need to use a .tot and not the kdz files to get to 100% stock, I'm not saving the files correctly, or I need an older version of TWRP with 10b and 12b?
I'm on 12B and my wife's is 10b and recieving the same error
I downloaded the zip files from Cyanogen's website and copied them via ESexplorer root to the external and internal SD cards
rooted, busybox, TWRP 3.0 (newest on the list)
I followed their install directions but was unsure how to copy the zip file using adb so I just downloaded them to the phone and copied them into folders using root explorer in esexplorer to get the files into hidden folders including TWRP and BACKUPS folders and a couple others just to try (I think this is my issue, how to I copy them to the root SD card) ESexplorer asked for SuperSU rights though)
opened TWRP via the app and manual through the factory reset/yes routes
backed up everything
wipe, factory reset, wipe dalvic/cache and cache again
I tried to install the zip from external and internal SD cards
The errors are
update process ended with error 7: Error installing zip file '/sdcard/cm12.1-rest of file name here.zip"
update process ended with error 7: Error installing zip file 'external_sd/TWRP/"file"
cyanogen mod says to save to /sdcard or adb push to /sdcard/ so it looks like I am in the right folder based on the error's path
I have also saved the zip files in the EXT SD TWRP/BACKUPS folder which conatin my backup from today. They are not in their own folder just files in the BACKUPS folder
UPDATES:
UPdated to 12B using KDZ flash not the .tot, rooted, busybox, TWRP = No change
Manually opened TWRP using the buttons/factory reset/yes and not rebooted from the app = No change
updated SuperSU = No change
100% battery = No change
log says:
couldn't find any tzdata when looking for localtime!
couldn't find any tzdata when looking for GMT!
couldn't find any tzdata when looking for posixrules!
stewbuntu said:
See recovery log below
The only thing I can think if now is that I need to use a .tot and not the kdz files to get to 100% stock, I'm not saving the files correctly, or I need an older version of TWRP with 10b and 12b?
I'm on 12B and my wife's is 10b and recieving the same error
I downloaded the zip files from Cyanogen's website and copied them via ESexplorer root to the external and internal SD cards
rooted, busybox, TWRP 3.0 (newest on the list)
I followed their install directions but was unsure how to copy the zip file using adb so I just downloaded them to the phone and copied them into folders using root explorer in esexplorer to get the files into hidden folders including TWRP and BACKUPS folders and a couple others just to try (I think this is my issue, how to I copy them to the root SD card) ESexplorer asked for SuperSU rights though)
opened TWRP via the app and manual through the factory reset/yes routes
backed up everything
wipe, factory reset, wipe dalvic/cache and cache again
I tried to install the zip from external and internal SD cards
The errors are
update process ended with error 7: Error installing zip file '/sdcard/cm12.1-rest of file name here.zip"
update process ended with error 7: Error installing zip file 'external_sd/TWRP/"file"
cyanogen mod says to save to /sdcard or adb push to /sdcard/ so it looks like I am in the right folder based on the error's path
I have also saved the zip files in the EXT SD TWRP/BACKUPS folder which conatin my backup from today. They are not in their own folder just files in the BACKUPS folder
UPDATES:
UPdated to 12B using KDZ flash not the .tot, rooted, busybox, TWRP = No change
Manually opened TWRP using the buttons/factory reset/yes and not rebooted from the app = No change
updated SuperSU = No change
100% battery = No change
log says:
couldn't find any tzdata when looking for localtime!
couldn't find any tzdata when looking for GMT!
couldn't find any tzdata when looking for posixrules!
Click to expand...
Click to collapse
If you want to install CM13 you need to be on 24B or 35B for the bootstack.
RedWingsFanEd said:
If you want to install CM13 you need to be on 24B or 35B for the bootstack.
Click to expand...
Click to collapse
I was just trying 12.1 for stability, for now
Should I try and go to 24B with TWRP 3.0 and see if that works?
UPDATE
TWRP 2.8 failed and said that CM12 also wanted the bootloader for 23C or greater. I read somewhere that TWRP 3.0 is the cause of the boot error 1003 when flashing CM so I'll try TWRP 2.8
So I updated and I have CM 12.1 running. I did notice a boot error 1003 right before TWRP opened to install the ROM and just before the CM boot screen popped up - Is that going to be okay? I have been running with no issues for half a day now.
I was able to update SuperSU
How I got the ROM installed
1.) Flashed 24B using KDZ flash tool and file
2.) Root - Only king root from here worked (click unknown sources, also Google stopped the install so I had to put the phone in airplane mode and open the apk): http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197/page84
3.) Installed busy box, TWRP, SuperSU asked to update the binary.
4.) Download CM12 or CM 13 files to the TWRP backup files folder
5.) Reboot into TWRP recovery via app
6.) backed up phone so you don’t have to get root again
7.) wipe - factory reset, wipe dalvic and cache again
8.) Installed Cyanogenmod 12.1 and rebooted system

Categories

Resources