Related
I rooted and installed clockwordmod recovery using the information on this forum, now I want to revert to stock recovery. I followed the instructions on this page
showthread.php?t=731989
Click to expand...
Click to collapse
and did a master clear and the regular flashing process. Everything seems to be working fine except when I reboot into recovery mode and select reinstall all packages i get this error:
e: can't open /sdcard/update.zip.
Click to expand...
Click to collapse
I tried two different Odin packages I897UCJF6 and I897UCJF1, both give me the same issue.
I think my only option is to use a nandroid backup from a fresh install, can anyone send me a link to one please.
If you did a master clear it deleted everything on your /sdcard volume... so of course it isn't finding an update.zip package there =P
if your recovery is black screen w blue letters, That is samsung recovery.
Zilch25 said:
If you did a master clear it deleted everything on your /sdcard volume... so of course it isn't finding an update.zip package there =P
Click to expand...
Click to collapse
I dont think theres supposed to be an update.zip on the factory device, besides odin is supposed to be a complete image
Sent from my SAMSUNG-SGH-I897 using XDA App
iamamp3pimp said:
if your recovery is black screen w blue letters, That is samsung recovery.
Click to expand...
Click to collapse
I can get to samsung recovery, but when I click reinstall packages it fails if there isn't an update.zip file in the /sdcard directory.
I poked around the clockworkmod update.zip and found out it deletes the /cache/recovery/update.zip and installs a modified /sbin/recovery; among other things, but I think those are the files that are most important to me right now, are those files not restored by Odin?
btw I'm new to android but I'm a linux admin and programmer so I have a basic understanding of how this works, now to just dig deeper and find out where it's going wrong.
Odin will wipe everything on your NAND clean, this does not include the /sdcard area (internal Sdcard)
Doing a master clear wipes everything including your internal sd (so if you had already had a clockwork backup it would have gotten wiped as well)
Rom Manager/Clockwork creates a folder on your /sdcard called /sdcard/clockwork, and within that folder all of your images are stored. Clockwork uses and update.zip file to install itself on boot up (through stock recovery)
I'm not entirely sure what answer you're looking for though, so I figured I'd just lay out a few facts in hopes that one of them might help
Thanks for the reply, I know the basics of how clockworkmod/nand work. What I'm trying to do is restore my phone to factory condition, Odin restores everything except the recovery manager, for some reason I'm stuck with the modified recovery that needs an update.zip. Before I made any changes, when my phone was new, if I booted into recovery and selected reinstall packages it would run the default att/samsung recovery program and reinstall default packages(as far as I can remember, please tell me if I'm just imagining this, ive been flashing and reflashing my phone countless times so I could be really confused), thats what I wan't to happen, now it just gives me the error:
e: can't open /sdcard/update.zip.
Click to expand...
Click to collapse
I don't recall my stock phone doing that, otherwise I wouldn't of had to return my first phone , black screened it on the first day I had it lol.
tbae2 said:
I don't recall my stock phone doing that, otherwise I wouldn't of had to return my first phone , black screened it on the first day I had it lol.
Click to expand...
Click to collapse
lol thanks, do you mean that it didn't try to reinstall the packages?
And could someone else with a stock AT&T Captivate please confirm, I'm not ready to admit that I've gone completely crazy....
Just so I understand. You go to recovery and it tries to install an update.zip without you doing anything? This isn't normal.
I'd do another odin and a master clear. That really should do it.
gunnyman said:
Just so I understand. You go to recovery and it tries to install an update.zip without you doing anything? This isn't normal.
I'd do another odin and a master clear. That really should do it.
Click to expand...
Click to collapse
No, he is saying that when he first got the phone it used to reinstall the stock packages when he selected reinstall packages. Now it doesn't and instead just says it can't find update.zip. He just wants to make sure that on a stock recovery it's not supposed to install anything when he selects reinstall packages.
If you did a master clear and have not manually put an update.zip file back into the root of the sdcard, then you will always get that message because the file does not exist. If you ran the 1 click odin and restored the phone, then you are back to stock. No further actions necessary.
Sent from my SAMSUNG-SGH-I897 using XDA App
gunnyman said:
Just so I understand. You go to recovery and it tries to install an update.zip without you doing anything? This isn't normal.
I'd do another odin and a master clear. That really should do it.
Click to expand...
Click to collapse
I've done a few master clears using odin. It's not trying to install an update.zip without me doing anything, the way I remember it on the stock phone when you select reinstall packages it will reinstall the default att packages, am I wrong about this?
kaiserman023 said:
I've done a few master clears using odin. It's not trying to install an update.zip without me doing anything, the way I remember it on the stock phone when you select reinstall packages it will reinstall the default att packages, am I wrong about this?
Click to expand...
Click to collapse
You are wrong about this. Selecting reinstall packages tells the phone to look for an update.zip file.
alphadog00 said:
You are wrong about this. Selecting reinstall packages tells the phone to look for an update.zip file.
Click to expand...
Click to collapse
Solved. Thankyou
Turns out there was nothing wrong with the phone just me, I've been trying to fix something that isn't broken!!!
alphadog00 said:
You are wrong about this. Selecting reinstall packages tells the phone to look for an update.zip file.
Click to expand...
Click to collapse
this......
Lol Jeez with all the hard issues we get around here it's the simple questions that confuse the crap out of us
Thread moved to Q&A.
Need serious help.
I flashed dirty unicorns and data and sms wasn't working so I tried to restore my phone but TWRP didn't see anything to restore. So desperately, i saw that it still saw my ViperRom zip so i flashed that and now I'm stuck in the splash screen. I tried to get the phone back to recovery with the toolkit and it doesn't see my phone.
TheSignor said:
Need serious help.
I flashed dirty unicorns and data and sms wasn't working so I tried to restore my phone but TWRP didn't see anything to restore. So desperately, i saw that it still saw my ViperRom zip so i flashed that and now I'm stuck in the splash screen. I tried to get the phone back to recovery with the toolkit and it doesn't see my phone.
Click to expand...
Click to collapse
more info:
I just tried the button combo light trick and was able to enter recovery. but alas I am at a loss what to do now. I still can't see my backups. I'm now doing a standard wipe and reinstalling ViperRom. Please God let this work.
update: Phone is alive.......but, i'm stuck on EVDO and Goomanager doesn't seem to see any of my original stuff. I'm aware this is the 4.2.2 thing but I am not really educated on how to deal with that.
TheSignor said:
more info:
I just tried the button combo light trick and was able to enter recovery. but alas I am at a loss what to do now. I still can't see my backups. I'm now doing a standard wipe and reinstalling ViperRom. Please God let this work.
update: Phone is alive.......but, i'm stuck on EVDO and Goomanager doesn't seem to see any of my original stuff. I'm aware this is the 4.2.2 thing but I am not really educated on how to deal with that.
Click to expand...
Click to collapse
Look here Q14
bigdaddy619 said:
Look here Q14
Click to expand...
Click to collapse
Thanks. Only one question though. I just finished copying my restore from the 0 folder and pasted it, now TWRP can see it and is finally willing to restore. Will the restore solve this issue just as easily or is it that as soon as you flash a 4.2.2 is your system forever changed without this fix? I only ask because I don't want to flash that zip and create a new issue if the restore will quite literally send me back in time to before I even flashed 4.2.2.
TheSignor said:
Thanks. Only one question though. I just finished copying my restore from the 0 folder and pasted it, now TWRP can see it and is finally willing to restore. Will the restore solve this issue just as easily or is it that as soon as you flash a 4.2.2 is your system forever changed without this fix? I only ask because I don't want to flash that zip and create a new issue if the restore will quite literally send me back in time to before I even flashed 4.2.2.
Click to expand...
Click to collapse
TBH I only use sense roms ask your question in the 4.2.2 > 4.1.2 thread
So I rooted, and I was playing with my build.prop file to try and get Google Wallet working. It never did, so I restored my old build.prop to go back to normal. However, my edited build.prop keeps restoring itself somehow after a reboot. I've tried different editors, I've tried pushing the file via ADB, editing via ADB, nothing seems to work. I've seen a few other people with random other phones having this issue, and the answer is always 'just flash another ROM!'. Well, that isn't an answer, esp since we can't flash ROMs yet. Anyone have any idea how to either fix this or flash back to 100% stock on a Verizon XT1060? Thanks!
You are rooted, so make sure you are booted into "recovery" so you have system write access. Then restore your unedited build.prop and reboot.
You can also flash back to 100% stock firmware using RSDLite and the VZW software.
rmead01 said:
You are rooted, so make sure you are booted into "recovery" so you have system write access. Then restore your unedited build.prop and reboot.
You can also flash back to 100% stock firmware using RSDLite and the VZW software.
Click to expand...
Click to collapse
Thanks. I tried using the Verizon dump, but I'm on a Linux box. Using fastboot to flash took everything but the system.img which failed. I'll just wait until I get home to use a Windows box to run RSDLite. Much appreciated.
Isn't it strange that I can edit it just fine from Root Explorer the first time, but not a second time though?
icase81 said:
Thanks. I tried using the Verizon dump, but I'm on a Linux box. Using fastboot to flash took everything but the system.img which failed. I'll just wait until I get home to use a Windows box to run RSDLite. Much appreciated.
Isn't it strange that I can edit it just fine from Root Explorer the first time, but not a second time though?
Click to expand...
Click to collapse
Well, what I mean was that when you root the phone, /system is only readable. In order for it to be writeable you need to boot into recovery. That is where you have a copy of the OS that has a writable /system. So I would boot to recovery, make your build.prop changes, then reboot into the standard mode. That should save the build.prop from the previous bootup when you were able to right it. This would also explain why root explorer could write it the first time (in recovery) and maybe why it couldn't the second time (not in recovery)
I haven't tried using fastboot at all with the phone, but I've use RSDLite to restore my ATT phone twice no with no issues.
rmead01 said:
Well, what I mean was that when you root the phone, /system is only readable. In order for it to be writeable you need to boot into recovery. That is where you have a copy of the OS that has a writable /system. So I would boot to recovery, make your build.prop changes, then reboot into the standard mode. That should save the build.prop from the previous bootup when you were able to right it. This would also explain why root explorer could write it the first time (in recovery) and maybe why it couldn't the second time (not in recovery)
I haven't tried using fastboot at all with the phone, but I've use RSDLite to restore my ATT phone twice no with no issues.
Click to expand...
Click to collapse
I would like to add that by boot into recovery they don't mean the same thing as every other android root. You aren't going into recovery and flashing thing like normal. You reboot you phone into "recovery mode" which is the same as normally booting your phone but you have read/write access to the system files.
Same issue here. Bootloader unlocked and rooted with supersu.zip. Editors can only modify the build prop once per editor. Weird.
Sent from my XT1056 using XDA Premium 4 mobile app
magui43212 said:
Same issue here. Bootloader unlocked and rooted with supersu.zip. Editors can only modify the build prop once per editor. Weird.
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, Root Explorer will create a backup. I delete build.prop, rename build.prop.bak to build.prop, reboot, its like I never did anything at all and this thing still thinks is an L710 Sprint Galaxy S3
icase81 said:
Yeah, Root Explorer will create a backup. I delete build.prop, rename build.prop.bak to build.prop, reboot, its like I never did anything at all and this thing still thinks is an L710 Sprint Galaxy S3
Click to expand...
Click to collapse
So what the phone does is it automatically restore build prop backups every reboot? That seems weird.
Sent from my XT1056 using XDA Premium 4 mobile app
magui43212 said:
So what the phone does is it automatically restore build prop backups every reboot? That seems weird.
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Exactly. And it restores my build.prop.bak file too, which was created by root explorer. I tried using other apps to edit, tried to do it with ADB, it does it no matter what. I think I'm just gonna RSD-Lite it back to factory and go from there.
Hi all,
I decided to post here because i'm new and I don't have permission to post in the proper thread. Anyway I'm trying to install the new rom 31.0 over my current on 12.1. It installs successfully but then I get stuck on the htc logo boot screen and yes I did the wipe data/cache thing. Can anyone help with this?
Much appreciated.
Did you update the kernel to a newer kernel? Also I would do a full wipe and then install. The two versions you are working with are very different.
spriggan17 said:
Hi all,
I decided to post here because i'm new and I don't have permission to post in the proper thread. Anyway I'm trying to install the new rom 31.0 over my current on 12.1. It installs successfully but then I get stuck on the htc logo boot screen and yes I did the wipe data/cache thing. Can anyone help with this?
Much appreciated.
Click to expand...
Click to collapse
did you confirm the MD5 sum? For ARHD 31.0 it's: 601F92B13104A373868C6C1E05972CF9
if it's not, then it's a bad download and you should download again.
EDIT: you should also select WIPE in Aroma installer!
Bootloops happen. Do a factory reset and flash again.
postfatal said:
Bootloops happen. Do a factory reset and flash again.
Click to expand...
Click to collapse
Will a factory reset erase my nandroid backup and if so how do I get the img file onto my computer?
spriggan17 said:
Will a factory reset erase my nandroid backup and if so how do I get the img file onto my computer?
Click to expand...
Click to collapse
If you don't have a functioning ROM, you'll have to enter custom recovery, adb works there. then you'll have to use "adb pull" commands to get stuff off your internal storage to your PC.
I think there's also an application called "Android Commander" which is basically a graphical file manager that acts as a front-end to adb.
nkk71 said:
If you don't have a functioning ROM, you'll have to enter custom recovery, adb works there. then you'll have to use "adb pull" commands to get stuff off your internal storage to your PC.
I think there's also an application called "Android Commander" which is basically a graphical file manager that acts as a front-end to adb.
Click to expand...
Click to collapse
I have a functioning ROM, I'm currently on Android Revolution 12.1. I just couldn't install their latest version (31.0) over my current one even after doing the data wipe both in recovery and AROMA. I re-downloaded the file and checkd the MD5 which seems to pass so I will try to install this new DL when I get home from work.
Thanks for the input guys and I'll keep you posted.
spriggan17 said:
I have a functioning ROM, I'm currently on Android Revolution 12.1. I just couldn't install their latest version (31.0) over my current one even after doing the data wipe both in recovery and AROMA. I re-downloaded the file and checkd the MD5 which seems to pass so I will try to install this new DL when I get home from work.
Thanks for the input guys and I'll keep you posted.
Click to expand...
Click to collapse
I would still recommend backing up everything to your PC, you MAY have to eventually wipe that. It's always a good idea to keep a backup of everything on your PC (or at least on a USB stick if you have an OTG).
Also remember that most likely your nandroids are in /data/media/... (which will not show up using MTP) as opposed to /data/media/0/... (which does show up on MTP), so if you want to keep them, either move them from /data/media/... to /data/media/0/... EDIT: you need a root-enabled file explorer on your phone to see /data/media/...
or use adb pull to get them off your phone.
Good luck, and remember to hit the thanks button if we helped
nkk71 said:
I would still recommend backing up everything to your PC, you MAY have to eventually wipe that. It's always a good idea to keep a backup of everything on your PC (or at least on a USB stick if you have an OTG).
Also remember that most likely your nandroids are in /data/media/... (which will not show up using MTP) as opposed to /data/media/0/... (which does show up on MTP), so if you want to keep them, either move them from /data/media/... to /data/media/0/... EDIT: you need a root-enabled file explorer on your phone to see /data/media/...
or use adb pull to get them off your phone.
Good luck, and remember to hit the thanks button if we helped
Click to expand...
Click to collapse
I got it working with a new download and clean install, but I seem to be missing the LTE icon?
spriggan17 said:
I got it working with a new download and clean install, but I seem to be missing the LTE icon?
Click to expand...
Click to collapse
It should be there, what carrier are you on, and did you select "international" in Aroma? Could also be CID related.
OK. So I soft bricked my phone earlier, and just restored by flashing the RUU. Now that I'm trying to root back, I'm noticing that my file system is totally different from what it used to be. TWRP actually says no OS is installed, but the stock version of 4.4.2 is most certainly there and boots just fine. How can I rectify this?
UPDATED: There was actually no problem with the file system. It appears I likely had a bad download of TWRP so it wasn't recognizing the mount points.
MarkBell said:
OK. So I soft bricked my phone earlier, and just restored by flashing the RUU. Now that I'm trying to root back, I'm noticing that my file system is totally different from what it used to be. TWRP actually says no OS is installed, but the stock version of 4.4.2 is most certainly there and boots just fine. How can I rectify this?
Click to expand...
Click to collapse
What version of TWRP do you have installed? 2.7.1.1 wipes OS version from bootloader, but that doesn't affect anything. If you want OS to be shown flash TWRP 2.6.3.3. It's the most stable recovery and you won't have problems flashing ROMs with it. On the other hand, if your phone works fine, leave it as it is
Powered by non removable 2300 mAh battery
donkeykong1 said:
What version of TWRP do you have installed? 2.7.1.1 wipes OS version from bootloader, but that doesn't affect anything. If you want OS to be shown flash TWRP 2.6.3.3. It's the most stable recovery and you won't have problems flashing ROMs with it. On the other hand, if your phone works fine, leave it as it is
Powered by non removable 2300 mAh battery
Click to expand...
Click to collapse
It was actually tdhite's 2.7.1.3 that I flashed that really screwed up my phone.
I was using 2.7.1.1 fine before. I flashed back to 2.7.1.1 after getting my phone working again with the RUU. I have a full backup of my rooted phone saved to my computer and would love to be able to restore it back through TWRP. But the actual filing system in ES File Explorer looks different.
In TWRP, I can't even get to SuperSU to become root because of the way the file system is so different.
When I was soft bricked, I may have played around in the Mount function of TWRP and screwed it up that way.
MarkBell said:
It was actually tdhite's 2.7.1.3 that I flashed that really screwed up my phone.
I was using 2.7.1.1 fine before. I flashed back to 2.7.1.1 after getting my phone working again with the RUU. I have a full backup of my rooted phone saved to my computer and would love to be able to restore it back through TWRP. But the actual filing system in ES File Explorer looks different.
In TWRP, I can't even get to SuperSU to become root because of the way the file system is so different.
When I was soft bricked, I may have played around in the Mount function of TWRP and screwed it up that way.
Click to expand...
Click to collapse
I wanted to add, the only partition showing as mounted in TWRP is the Data. Can't mount cache or system. Going to restore shows my internal storage at 37 MB. Going to file manager shows I am in the folder "/." In this folder are a boot, cache, data, deve, etc, license, proc, recovery, res, root, sbin, sdcard, supersu, sys, system, tmp, usb-otg, default.prop, file_contexts, fstab.goldfish, fstab.qcom, init, init.rc, init.recovery.qcom.rc, property_contexts, seapp_contexts, sepolicy, ueventd.goldfish.rc, ueventd.rc. Most of these have nothing in them. SuperSu does have a Superuser.apk inside, but its not the SuperSu file I downloaded from Chainfire's page, and with only Data being mounted I'm afraid to flash the default one.
The other funny thing is that when I go to reboot system in TWRP, it says that no OS is installed, but like I said, the stock system boots just fine. I believe everything on my phone is installed to Data.
MarkBell said:
It was actually tdhite's 2.7.1.3 that I flashed that really screwed up my phone.
I was using 2.7.1.1 fine before. I flashed back to 2.7.1.1 after getting my phone working again with the RUU. I have a full backup of my rooted phone saved to my computer and would love to be able to restore it back through TWRP. But the actual filing system in ES File Explorer looks different.
In TWRP, I can't even get to SuperSU to become root because of the way the file system is so different.
When I was soft bricked, I may have played around in the Mount function of TWRP and screwed it up that way.
Click to expand...
Click to collapse
The file system has not changed since 4.1.2 to 4.2.2
was your old system 4.1.2 ?
You should also make it Clear you Have a Sprint HTC One
clsA said:
The file system has not changed since 4.1.2 to 4.2.2
was your old system 4.1.2 ?
You should also make it Clear you Have a Sprint HTC One
Click to expand...
Click to collapse
Yes. It's the Sprint HTC One m7. This is the most bizarre problem I have come across. And I was successfully rooted (SuperSU) with TWRP 2.7.1.1 installed prior to installing TDHITE's 2.7.1.3, which really seemed to mess things up for some reason. I used liquidsmooth custom rom, but ended up going back to the stock ROM and using Xposed framework because I do like a lot of the stock features, but I loved being able to tweak them with Xposed. Now I'm stuck on stock with a weird looking file system.
MarkBell said:
Yes. It's the Sprint HTC One m7. This is the most bizarre problem I have come across. And I was successfully rooted (SuperSU) with TWRP 2.7.1.1 installed prior to installing TDHITE's 2.7.1.3, which really seemed to mess things up for some reason. I used liquidsmooth custom rom, but ended up going back to the stock ROM and using Xposed framework because I do like a lot of the stock features, but I loved being able to tweak them with Xposed. Now I'm stuck on stock with a weird looking file system.
Click to expand...
Click to collapse
Flash recovery from here >> http://techerrata.com/browse/twrp2/m7wls
Start it choose wipe, choose format data, Reboot recovery
choose wipe / factory reset, reboot recovery
push/sideload this rom to your phone and flash it
http://forum.xda-developers.com/sprint-htc-one/development/rom-sense-6-4-4-3-stock-t2848102
Dude, we could really do some serious damage to your phone. As clsA said, you really should make it clear that it's Sprint version. Did you by any chance flash something that's not for Sprint phones? That could screw up your system.
Powered by non removable 2300 mAh battery
Is this possibly just a problem with TWRP? I actually notice in ES File Explorer that things arent' too different after all. I've got a / (Device) folder and a "0" folder which is my internal storage. It's just stuff isn't showing right in TWRP I guess, and TWRP seems to only be mounting my data partition.
MarkBell said:
Is this possibly just a problem with TWRP? I actually notice in ES File Explorer that things arent' too different after all. I've got a / (Device) folder and a "0" folder which is my internal storage. It's just stuff isn't showing right in TWRP I guess, and TWRP seems to only be mounting my data partition.
Click to expand...
Click to collapse
Go back to post 7 and do what I ask
clsA said:
Flash recovery from here >> http://techerrata.com/browse/twrp2/m7wls
Start it choose wipe, choose format data, Reboot recovery
choose wipe / factory reset, reboot recovery
push/sideload this rom to your phone and flash it
http://forum.xda-developers.com/sprint-htc-one/development/rom-sense-6-4-4-3-stock-t2848102
Click to expand...
Click to collapse
This did it. Maybe I just had a bad TWRP image flashed before? Thanks for your help!
MarkBell said:
This did it. Maybe I just had a bad TWRP image flashed before? Thanks for your help!
Click to expand...
Click to collapse
Flashing that TWRP is what got it working. I didn't follow any of the other steps. Thanks so much! Now to load my backup and restore! Thank you. Thank you. Thank you! Making a stock backup first of course. I love these forums. Seriously. Anything is possible with the fine people of XDA.
MarkBell said:
Flashing that TWRP is what got it working. I didn't follow any of the other steps. Thanks so much! Now to load my backup and restore! Thank you. Thank you. Thank you! Making a stock backup first of course.
Click to expand...
Click to collapse
Go back and hit the thanks button, it helps so others know my reputation. and you can edit your first post title to include [solved]
clsA said:
Go back and hit the thanks button, it helps so others know my reputation. and you can edit your first post title to include [solved]
Click to expand...
Click to collapse
I did the thanks, but I can't seem to edit the title of my first post. Title box doesn't show up when I hit edit.
MarkBell said:
I did the thanks, but I can't seem to edit the title of my first post. Title box doesn't show up when I hit edit.
Click to expand...
Click to collapse
Advanced Edit
clsA said:
Go back and hit the thanks button, it helps so others know my reputation. and you can edit your first post title to include [solved]
Click to expand...
Click to collapse
Your reputation is one of the highest here :good: :good:
MarkBell said:
I did the thanks, but I can't seem to edit the title of my first post. Title box doesn't show up when I hit edit.
Click to expand...
Click to collapse
to edit the main thread title to include [SOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title)