I did a factory wipe, then went to install energy's custom rom, it gave an error that system is already unmounted, and gave an error (status 1), now it will restart the phone each time i try to enter recovery, but by this time, all of the original rom is gone. I still got access to adb/fastboot. How to install everything back to stock again?
I had a somewhat similar problem, if you want to revert to stock, download the stock firmware here, then relock your bootloader with the command "fastboot oem lock", and then reinstall the stock firmware with hboot.
mcs117 said:
I did a factory wipe, then went to install energy's custom rom, it gave an error that system is already unmounted, and gave an error (status 1), now it will restart the phone each time i try to enter recovery, but by this time, all of the original rom is gone. I still got access to adb/fastboot. How to install everything back to stock again?
Click to expand...
Click to collapse
Back to stock or back to rooted stock?
What recovery are you using?
Did you try an ruu file? (may format internal sdcard)
Did you try to wipe each partition from recovery?
Did you try a restore?
Related
I unlocked my bootloader and flashed a custom recovery for the first time yesterday (TWRP). I also flashed a ROM (Fresh by flipz) and that's when I noticed that some apps would simply refused to install. They would not install from my Titanium Backup of them and they wouldn't install from the market either (giving a vague "could not install to phone storage or sd card" error message).
I didn't know which to blame, the custom recovery or the custom ROM, so I started by flashing back to stock recovery (while keeping the custom ROM) but the apps still wouldn't install. So then I flashed back to the stock ROM as well, and the apps still wouldn't install! Finally, I relocked the phone and RUU'ed back to stock and now the apps install just fine.
Was HTC Dev's unlock really to blame for that or am I missing something?
I've had similar issues before if I did not perform a full data wipe and system wipe before flashing a new rom. If I simply went back into recovery and did a full wipe (cache/dalvik/data/system) and reflashed, it solved the problem.
I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
geon106 said:
I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
Click to expand...
Click to collapse
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
McJesus15 said:
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
Click to expand...
Click to collapse
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
geon106 said:
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
Click to expand...
Click to collapse
IT LIVES!!!
Don't know how I did it, but I managed to get TWRP installed on it. Using Fastboot somehow or ADB. It booted into TWRP and mounted external SD card, then flashed an official JB ROM(the Prime was on ICS before) and it has now booted up fine
I will now try and re-flash a custom ROM again(a different one) using TWRP but it is all looking superb
I was worried i'd have to claim on the extended insurance I took out with the retailer
Hello, my phone was running slowly so I decided to go back to a previous backup and run very few apps. I restore a Nandroid backup and when I did the phone told me an update was available, I tried to install it but it just kept restarting to recovery and I had to reboot into System manually and it never applied the update.
Someone told me I needed a stock recovery, I thought Well, since I'm flashing something, why not flash a JB file too? I went and downloaded a JB rom, flashed that and the recovery but it didn't boot (probably because my hboot is 1.20) so I tried a different rom, basically I tried different combinations but somehow nothing seemed to work, and now I can't boot my phone. I've read that you can brick your phone if you wipe the EMMC, I don't remember doing that but I tried so many things that I might have wiped it without noticing. Is there a way to verify the EMMC? I can boot into recovery with fastboot, but when I install any rom, it just doesn't boot, it gets stuck in the first HTC screen with the HTC logo and those red letters I got after rooting (this rom is property of HTC...don't distribute outside without written permission...etc etc).
So, do you think this can be an EMMC problem, or just a kernel problem? I tried flashing the boot.img from my Nandroid backup (actually it was called boot.emmc.win but I renamed it to boot.img following some instructions I found online) but even with the Nandroid backup that worked before the phone would not start.
If this is indeed an EMMC problem, is there a way to fix it?
Thank you very much.
You also restored your nandroid backup from stock? As your hboot is 1.20 (which is quite old btw), you cannot flash JB kernels to boot partition so JB ROMs won't work without a workaround. So try to completely restore your stock nandroid backup or else you could try running a RUU if your CID is compatible.
dansou901 said:
You also restored your nandroid backup from stock? As your hboot is 1.20 (which is quite old btw), you cannot flash JB kernels to boot partition so JB ROMs won't work without a workaround. So try to completely restore your stock nandroid backup or else you could try running a RUU if your CID is compatible.
Click to expand...
Click to collapse
Yes I read that you need at least hboot 1.25 to flash JB, that's why after flashing JB and seeing it wasn't starting, I tried to go back to my old ICS backup, but none of them work now, I have a Nandroid backup that was working before,here's what I'm trying to do:
1. Flash my old boot.emmc.win changing the name to boot.img and running "fastboot flash boot boot.img"
2. boot into TWRP-2.4.3.0 and do a Factory Reset, followed by a Restore of my backup, which restores System, Data and Boot, and gives me a "Restore Complete - Successful" message.
3. Install SuperSU right before rebooting
4. Reboot
After that the phone just gets stuck on the first HTC screen, the one with the red letters. I don't know much about android, but I think I'm following all the steps correctly, to restore my old Nandroid backup. Or am I doing something wrong?
My CID is ORANG309, I got a 4.0.1 RUU (at least that's what the person said) and I'm going to try to recover that one. It's not a ZIP file, it's a folder with files inside, so i'll probably have to restore it as a normal Nandroid.
Try flashing the system partition as well before restoring your backup.
dansou901 said:
Try flashing the system partition as well before restoring your backup.
Click to expand...
Click to collapse
You mean formatting the /system partition? I try that too, but it doesn't seem to work. Now that I was into TWRP, I saw the Wipe buttons and there is one called "Wipe internal storage" that I might have pressed before, it kinda rings a bell. So assuming I did press it, does that wipe the EMMC? Is there a way to recover it?
I've been trying to flash using Dumlock because it doesn't seem to work from the normal recovery. Here's then what I do.
1. Boot into normal TWRP recovery.
2. Click Advanced -> HTC Dumlock
3. Inside, I click "Reflash recovery" which supposedly reflashes the recovery into boot.
3. Tap "Reboot" and "System". This should reboot into the Recovery in the boot partition, but it gets stuck in a reboot loop.
So I can't boot into the recovery that should be in the boot part. And now when I enter into normal recovery, whenever I restore a Nandroid, right after doing it if I choose "Reboot", it says "No OS Installed!"
camilou said:
I've been trying to flash using Dumlock because it doesn't seem to work from the normal recovery. Here's then what I do.
1. Boot into normal TWRP recovery.
2. Click Advanced -> HTC Dumlock
3. Inside, I click "Reflash recovery" which supposedly reflashes the recovery into boot.
3. Tap "Reboot" and "System". This should reboot into the Recovery in the boot partition, but it gets stuck in a reboot loop.
So I can't boot into the recovery that should be in the boot part. And now when I enter into normal recovery, whenever I restore a Nandroid, right after doing it if I choose "Reboot", it says "No OS Installed!"
Click to expand...
Click to collapse
I don't know wat you are doing but just restore your nandroid backup in recovery and flash boot with fastboot
GtrCraft said:
I don't know wat you are doing but just restore your nandroid backup in recovery and flash boot with fastboot
Click to expand...
Click to collapse
Yeah, that doesn't work. I restore the Nandroid and then when I go to reboot, TWRP says "No OS Installed! Are you sure you wish to reboot"
Update: Using my old Nandroid, I tried this:
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash recovery recovery.img
All of them worked, except for the "data", but the phone does not work. Tried doing the same, then flashing data from inside of TWRP recovery, same thing. Phone is stuck on the HTC screen and it doesn't work.
Any ideas?
Tried Dumlock, but it doesn't seem to be writing the Recovery image to boot. I even went and copied a recovery.img file into "/sdcard/twrp/dumlock/<device>/boot/boot.img" and from the TWRP Dumlock menu, tried to "Restore original boot" to see if Dumlock would assume that "boot.img" was the file to flash into the recovery, but when I restart it's just the HTC screen. I'm using TWRP 2.4, and renamed TWRP 2.6 as "boot.img" because the difference in version number would let me know from where was the recovery being booted, but I can't flash into twrp 2.6, aka the fake boot.img.
Tried downloading some RUUs for Spain, but the recovery process failed.
So is it safe to assume that this phone is bricked? I have S-ON, like all other Desire X devices (I think) so can you brick a phone with S-ON? Is there a way to restore the original stock rom? Or at least a way that I can remove the red letters on the boot animation, the ones that say "This build is for development purposes" so that I can take it to the store and hopefully they won't notice that my bootloader is unlocked and maybe they will fix it under the warranty?
thanks
Nevermind, I flashed a ICS Nandroid with the adequate recovery (nexusrecovery) and it works now
ics nandroid
camilou said:
Nevermind, I flashed a ICS Nandroid with the adequate recovery (nexusrecovery) and it works now
Click to expand...
Click to collapse
Are you using htc desire S I'm also stuck at the HTC screen, I did HTCdev unlocking. On the recovery mode it shows unlocked, but I did not notice that S-ON was still on. Where can I find an ICS Nandroid of htc desire s? Thanks
Take a look at the HTC Desire S forum, this one is just for HTC Desire S. if you don't find it, ask there...
Hello,
I have a Kobo 10HD and rooted and installed CWM v6.0.5.1. I made a backup before and then installed Titanium Backup update.zip. Installation of that zip caused a bootloop (back to CWM). No problem, I thought, I can just restore the backup I made. No dice. I tried to restore the backup and still bootlooping. I even tried to installed the stock ROM ZIP and it fails with the message: (from recovery.log):
nv_copy_blob_file: couldn't get the device path
script aborted (no error message)
script aborted (no error message)I:Legacy property environment disabled.
E:Error in /data/media/0/macallan-ota-932.zip
(Status 7)
Installation aborted.
I have read that some people have had success installing this zip using stock recovery, but I have no idea how to get stock recovery.
Also, I noticed using adb shell that CWM does actually put all the files back into system and other areas during the restore. Upon reboot, and subsequent bootloop, the system files are gone. It must have something to do with an automatic script that is running after restore.
SOLVED!
zhzhou said:
Hello,
I have a Kobo 10HD and rooted and installed CWM v6.0.5.1. I made a backup before and then installed Titanium Backup update.zip. Installation of that zip caused a bootloop (back to CWM). No problem, I thought, I can just restore the backup I made. No dice. I tried to restore the backup and still bootlooping. I even tried to installed the stock ROM ZIP and it fails with the message: (from recovery.log):
nv_copy_blob_file: couldn't get the device path
script aborted (no error message)
script aborted (no error message)I:Legacy property environment disabled.
E:Error in /data/media/0/macallan-ota-932.zip
(Status 7)
Installation aborted.
I have read that some people have had success installing this zip using stock recovery, but I have no idea how to get stock recovery.
Also, I noticed using adb shell that CWM does actually put all the files back into system and other areas during the restore. Upon reboot, and subsequent bootloop, the system files are gone. It must have something to do with an automatic script that is running after restore.
Click to expand...
Click to collapse
After a few more hours of fiddling, I was able to get the device back up. I wiped absolutely everything manually with CWM (format /X) instead of Wipe/Factory Reset. The factory reset was not clearing the SD card, but format/data and /data/media cleared it. I then applied the stock zip that is available via adb sideload. Installation failed with the same error, but I rebooted with the adb reboot command. The device booted back into Kobo stock requiring several updates. It actually got stuck repeating one update several times until I booted back into stock recovery and cleared data and did a factory reset. The update applied correctly and then another upgrade came (a total of three upgrades). I rooted again and we are back in business.
For some reason, I think the key step was manually wiping /data/media. I'm not exactly sure why this would cause a bootloop for CWM restore. Anyway, I hope this helps someone else who may run into a similar issue.
Hi zhzhou!
Just a quick question:
do you happen to remember if stock recovery for Kobo was CWM? I'm in process of restoring stock ROM +recovery and little bet surprised to see CWM after flashing stock recovery
Thanks a lot!
zhzhou said:
After a few more hours of fiddling, I was able to get the device back up. I wiped absolutely everything manually with CWM (format /X) instead of Wipe/Factory Reset. The factory reset was not clearing the SD card, but format/data and /data/media cleared it. I then applied the stock zip that is available via adb sideload. Installation failed with the same error, but I rebooted with the adb reboot command. The device booted back into Kobo stock requiring several updates. It actually got stuck repeating one update several times until I booted back into stock recovery and cleared data and did a factory reset. The update applied correctly and then another upgrade came (a total of three upgrades). I rooted again and we are back in business.
For some reason, I think the key step was manually wiping /data/media. I'm not exactly sure why this would cause a bootloop for CWM restore. Anyway, I hope this helps someone else who may run into a similar issue.
Click to expand...
Click to collapse
Stock was definitely not CWM. It was a long time ago and I no longer have the device, but I think CWM was still present after restoring stock. I think you'll need fastboot if you want to flash the stock recovery image back on. But why do that? TWRP is now available for the device.
Thanks for quick reply! I had CM on it but had some artifact issues so wanted to revert to full stock, even recovery
zhzhou said:
Stock was definitely not CWM. It was a long time ago and I no longer have the device, but I think CWM was still present after restoring stock. I think you'll need fastboot if you want to flash the stock recovery image back on. But why do that? TWRP is now available for the device.
Click to expand...
Click to collapse
hey guys just looking for some help. ive been modding and flashing phones from 2014, but its always gone really smoothly, so my diagnostic ability is lacking.
it started with flashing twrp. my bootloader is unlocked, usb debugging on, device is showing in adb and fastboot, and i can flash twrp without any issues. hoowever when i go to boot twrp, only the stock recovery boots. i tried to flash twrp using the XiaoMiTool v2, but the same thing happened. i eventually got around this by just booting twrp instead of trying to flash it. so i got in, took a full back-up and started installing a custom rom.
the first one i tried was ParanoidAndroid Quartz. i wiped cache, dalvik and storage then transferred it to my phone, tried to flash and got "zip verification failed". so i turn off zip verification and tried again. it flashed perfectly with zero errors. however, when i reboot the phone it would only boot to stock recovery and not twrp (expected) or the new rom. i tried that a few times, then tried LineageOS, and MSM Xtended 10. all of them had the same issue, the flashed without a hitch, then wouldnt boot.
i also tried flashing a new fw-vendor and it just straight up failed. Then i decided to cut my losses and restore my twrp backup, and that came back with the error, "extractTarFork() process ended with error: 255"
Software before i began these attempts was completely stock, so i dont know what is going wrong, but as of now, my phone is bricked, i cant install a new rom or restore my back-up.
any help is appreciated guys. thanks
You can figure out this problem with
1 Copy backup folder to computer
2- Format Data - Yes , Wipe Everything
3- Install ROM that you have installed before and boot
4- Go to TWRP, format data yes reboot recovery
5- Paste backup folder to internal storage and restore