I have a ATT atrix rooted in 1.5.7.
My webtop is full open too with the script of Sogarth.
The phone ask me to update in 1.8.3 if i do, i can root with Gingerbreak after the installation of the update but i don't loose anything else? the faculty too use the webtop without hdmi?
Or before the update is better for me to uninstall the script of Sogarth and try to restore the original files dockApp and PortalApp?
I sorry if the reponse is already here but i can't find anywhere...
Thanks for the information.
Sent from my MB860 using XDA App
I have the updated cwm unlocked fresh sbf1.83. I can get to apply update but no file to flash says says up date zip not found. I can see it in atro manager though. How do I flash it.
Scott4006 said:
I have the updated cwm unlocked fresh sbf1.83. I can get to apply update but no file to flash says says up date zip not found. I can see it in atro manager though. How do I flash it.
Click to expand...
Click to collapse
You have to "Install Zip from SD card"... then use the menus to navigate to where you stored it.
no such line on cwm 0630-1029
I do not have that option it was on the old cwm but cant seem to find in on the new one? only have update zip wipe cach and reset
You need to update to the newer CWM. If you haven't unlocked you can get it in this thread; http://forum.xda-developers.com/showthread.php?t=1019143&highlight=cmw+recovery
If you've already unlocked you'd want the latest/greatest available here: http://forum.xda-developers.com/showthread.php?t=1138541&highlight=cmw+recovery
I have the newest installed from 6/30
Sent from my MB860 using XDA App
No option list to choose zip from sd card is listed
Sent from my MB860 using XDA App
Try renaming it to update.zip, because when you choose get to apply update its searching for a file named update.zip.
Plus the new CWM supports internal SD card.
Fixed Thank You
I had to reflash 2 in order to bring all the options up.
what is this new update and should I except it? I see now..I'm running flipz and its old build....
Sent from my EVO using xda premium
No
darrick913 said:
what is this new update and should I except it?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
If you plan on rooting your phone. DO NOT UPDATE It will change your hboot of the phone. HTC did this to the evo 3d and screwed up the phone. If you want the updates without the changed hboot. Root your phone and the devs have made a flashable zip that has all the good updates and no hboot change.
No do not ota. Download this:
http://d-h.st/elt
Rename it to PJ75IMG.zip
Place it on sdcard - not in any folders, in the main directory
Reboot into bootloader and say yes to update
Rename or remove it from sd card
My brother's DX2 is stock 2.3.5, unrooted.
It has been going slow, and recently the mic stopped working in calls.
I figure it's probably time to do a reflash of either the stock rom, or a stable cm, or perhaps eclipse rom.
the problem is it's not rooted, and I want to backup the apps and app data. Is there any way to do this? I hear to root 2.3.5 you must restore to 2.3.4, erasing everything, then use root keeper, and update again. So what should I do?
Take a look at this:
http://android.appstorm.net/how-to/...-back-up-your-android-device-without-rooting/
2.3.5 is rootable
Sent from my DROID X2 using xda app-developers app
Nevermind found a 2.3.5 root method: http://forum.xda-developers.com/showthread.php?t=1818758
:laugh:
It's rooted.. but does anyone know if the Internal sdcard gets wiped when you sfb/wipe data/flash rom?
mvmacd said:
Nevermind found a 2.3.5 root method: http://forum.xda-developers.com/showthread.php?t=1818758
:laugh:
It's rooted.. but does anyone know if the Internal sdcard gets wiped when you sfb/wipe data/flash rom?
Click to expand...
Click to collapse
The internal SD card does not get wiped.
Well if you wipe data it does....
Hello,
I've managed to get my build.prop in a state where I can't update (I assume it's the build prop). I've tried the backups I have, but none of them are working. I'm currently on 4.1.1 and I was hoping someone has backup.
Thanks in advance!
for clarity: Verizon Galaxy Note II 4.1.1 Stock ROM, Stock Recovery, Rooted
The Failing update is update_SCH-I605_LL4_to_MC3 which fails with code 402
Download the stock ROM in Development and pull it from there
Sent from my SCH-I605 using xda app-developers app
Bfitz26 said:
Download the stock ROM in Development and pull it from there
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I Downloaded the image and extracted it, now I have a "system.img" file which I assume contains the files but what do I do with it? I tried mounting/extracting and nothing worked.
Trevski13 said:
I Downloaded the image and extracted it, now I have a "system.img" file which I assume contains the files but what do I do with it? I tried mounting/extracting and nothing worked.
Click to expand...
Click to collapse
Download the recovery flashable stock rom, the zip file, and extract it from that using 7zip.
Sent from my SCH-I605 using XDA Premium HD app
Trevski13 said:
I Downloaded the image and extracted it, now I have a "system.img" file which I assume contains the files but what do I do with it? I tried mounting/extracting and nothing worked.
Click to expand...
Click to collapse
Using ES File explorer. Setup up your root explorer. and change permissions by using tools to System R/W.
Use ES File explorer to open the stock download and navigate to system/build.prop Copy it. Go back to your system and Rename the one there to build.bak. Then paste the new one there. This way you have the original saved if it turns out not to be the build.prop. My guess is. If you are on a rooted, stock rom like you said. The build.prop's are going to be identical. Thinking the culprit might be whatever you are trying to Odin is bad.
dragonstalker said:
Using ES File explorer. Setup up your root explorer. and change permissions by using tools to System R/W.
Use ES File explorer to open the stock download and navigate to system/build.prop Copy it. Go back to your system and Rename the one there to build.bak. Then paste the new one there. This way you have the original saved if it turns out not to be the build.prop. My guess is. If you are on a rooted, stock rom like you said. The build.prop's are going to be identical. Thinking the culprit might be whatever you are trying to Odin is bad.
Click to expand...
Click to collapse
I didn't know you could explore .img files with a root explorer, of course I have never tried either.
Sent from my SCH-I605 using XDA Premium HD app
So I pulled the build.prop from a stock image, but it turned out it perfectly matched one of my backups. (I had three backups, factory, factory that I played with, and OTA Stock). So in the end that didn't solve my core issue. At this point should I make a new thread with a more appropriate title or just continue this one?
shangrila500 said:
I didn't know you could explore .img files with a root explorer, of course I have never tried either.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Actually you can't... I ended up using "Android ICS JB EXT4 imagefile unpacker" for windows, which worked nicely.
Trevski13 said:
The Failing update is update_SCH-I605_LL4_to_MC3 which fails with code 402
Click to expand...
Click to collapse
I would say just continue this thread.
I just re-read your original post. Are you trying to update from 4.1.1 to 4.1.2 via the OTA? If so, build.prop isn't your issue.
jcollier said:
I would say just continue this thread.
I just re-read your original post. Are you trying to update from 4.1.1 to 4.1.2 via the OTA? If so, build.prop isn't your issue.
Click to expand...
Click to collapse
alright, detail time!
I'm currently on 4.1.1 (I've applied one update after I bought it on release day)
I have an ota update (to what I assume is 4.1.2)
stock everything, locked boot-loader, but rooted (used Exynos Abuse)
using SuperSU
my phone lists update_SCH-I605_LL4_to_MC3 which fails to install with error code 402
my device status IS "modified" but it appears to be related to the SD card as it is "normal" when I remove it (apparently a known issue)
normally when I get an update I do the following:
1. restore build.prop
2. remove busybox
3. remove/disable any other apps that may have played with files that I think could cause issues
4. double check my root backup (Voodoo)
5. temp unroot
6. update
7. restore root
8. enjoy
this method usually works without issues :/
and the reason I suspected build.prop in the first place is that restoring it allowed me to update on another device.
I'd really rather not have to flash it back to stock, but if it's my only option, I will. So any ideas that don't involve wiping everything would be wonderful!
Trevski13 said:
alright, detail time!
I'm currently on 4.1.1 (I've applied one update after I bought it on release day)
I have an ota update (to what I assume is 4.1.2)
stock everything, locked boot-loader, but rooted (used Exynos Abuse)
using SuperSU
my phone lists update_SCH-I605_LL4_to_MC3 which fails to install with error code 402
my device status IS "modified" but it appears to be related to the SD card as it is "normal" when I remove it (apparently a known issue)
normally when I get an update I do the following:
1. restore build.prop
2. remove busybox
3. remove/disable any other apps that may have played with files that I think could cause issues
4. double check my root backup (Voodoo)
5. temp unroot
6. update
7. restore root
8. enjoy
this method usually works without issues :/
and the reason I suspected build.prop in the first place is that restoring it allowed me to update on another device.
I'd really rather not have to flash it back to stock, but if it's my only option, I will. So any ideas that don't involve wiping everything would be wonderful!
Click to expand...
Click to collapse
Really the only thing I have seen to update is to go completely back to stock.
But why do you want to do this so badly? Why not just unlock and flash the new update rom Beans provided? Thats certainly the easiest way to do it in my opinion, since you're having all these issues, and it leaves you unlocked in case you don't like one of the future updates or if you want to test out AOSP.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Really the only thing I have seen to update is to go completely back to stock.
But why do you want to do this so badly? Why not just unlock and flash the new update rom Beans provided? Thats certainly the easiest way to do it in my opinion, since you're having all these issues, and it leaves you unlocked in case you don't like one of the future updates or if you want to test out AOSP.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I rely on my phone a lot and so even the short amount of time it would take me to fix a soft brick, or reconfigure a wiped device would be a problem. I'm not worried about bricking it, I'm worried about the time it takes to fix it. I soft bricked my old X2, and it was a real inconvenience (granted that was the first time I'd ever had to fix something like that) and I had to restore my Transformer Infinity back to stock to fix lag and glitching issues. (which lead to a whole partial root fiasco). So It's not that I can't fix the problems, it's that it takes time I don't have, and disrupts my life. If I had another 4g phone (because switching between 3g and 4g is a pain on Verizon) that I could switch to if I messed up and didn't have time to fix it, I'd totally start messing with custom roms, unlocking, and all that fun stuff, but I don't
Trevski13 said:
I rely on my phone a lot and so even the short amount of time it would take me to fix a soft brick, or reconfigure a wiped device would be a problem. I'm not worried about bricking it, I'm worried about the time it takes to fix it. I soft bricked my old X2, and it was a real inconvenience (granted that was the first time I'd ever had to fix something like that) and I had to restore my Transformer Infinity back to stock to fix lag and glitching issues. (which lead to a whole partial root fiasco). So It's not that I can't fix the problems, it's that it takes time I don't have, and disrupts my life. If I had another 4g phone (because switching between 3g and 4g is a pain on Verizon) that I could switch to if I messed up and didn't have time to fix it, I'd totally start messing with custom roms, unlocking, and all that fun stuff, but I don't
Click to expand...
Click to collapse
Well unlocking would let you go ahead and update and until you wanted to flash roms you wouldnt have to except for that first flash of the new update, which is what a stock update does.
The reason I say this is some people have had this problem and when they finally do get the update to work it soft bricks them. This is rare but it has happened. In the end for me it is just easier to unlock so I can play around when I want to and when I dont I can stay on stock.
Sent from my SCH-I605 using XDA Premium HD app