So, once my Rezound started prompting me for the OTA update, I decided I would unfreeze the apps I had so it could update no problem. Attempting to do so with Gemini App Manager was a failure as at first it couldn't get root and then after I updated it I can no longer un-freeze apps without 'donating'. So I just decided to let my phone do it's thing and see what would happen. It downloads, when the phone resets it comes up to System Recovery. Down at the bottom is displays the following :
RA Revamped
Build : RA-VIGOR-v3.15-getitnowmarketing
Finding update package...
Opening update package...
Installing update...
wrong taskid 221384E:Error in /cache/fumo/OTAPkg.zip
(Status 1)
Installation aborted.
If I reboot the system the phone works fine until it starts trying to force me to do the update again, then it's the same thing again. How can I resolve this and just install the damn update?
ebrammer252 said:
So, once my Rezound started prompting me for the OTA update, I decided I would unfreeze the apps I had so it could update no problem. Attempting to do so with Gemini App Manager was a failure as at first it couldn't get root and then after I updated it I can no longer un-freeze apps without 'donating'. So I just decided to let my phone do it's thing and see what would happen. It downloads, when the phone resets it comes up to System Recovery. Down at the bottom is displays the following :
RA Revamped
Build : RA-VIGOR-v3.15-getitnowmarketing
Finding update package...
Opening update package...
Installing update...
wrong taskid 221384E:Error in /cache/fumo/OTAPkg.zip
(Status 1)
Installation aborted.
If I reboot the system the phone works fine until it starts trying to force me to do the update again, then it's the same thing again. How can I resolve this and just install the damn update?
Click to expand...
Click to collapse
Well, I factory reset the phone, re-rooted it. I have root again, all apps are intact, but the update still will not take. Same issue, same error message.
The OTA will not flash unless your are completely stock. You have a custom recovery, so it isn't going to work unless you flash the stock recovery and are COMPLETELY stock.
I also had a similar issue. I had an issue with update 8 working for it had some random restarts and WiFi didn't work but update 6 was fine. Regardless what you do for this, and you're in recovery, simply go to flash a zip file and navigate to the ota-update folder and then downloads and you can select your zip file there. Just confirm it with the power button and away the install goes. Hopefully this helps and its your issue.
Sent from my ADR6425LVW using xda app-developers app
kpritchard said:
I also had a similar issue. I had an issue with update 8 working for it had some random restarts and WiFi didn't work but update 6 was fine. Regardless what you do for this, and you're in recovery, simply go to flash a zip file and navigate to the ota-update folder and then downloads and you can select your zip file there. Just confirm it with the power button and away the install goes. Hopefully this helps and its your issue.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Well, I think I bricked it. I had a firmware.zip and I installed it and now it's dead.
Booting up normally it just hangs at the 4G LTE screen and never goes anywhere.
Booting into recovery everything seems normal until I try to do anything.
For instance :
Wipe -> Wipe ALL data/factory reset =
Formatting DATA...
Formatting SDCARD:.android_secure...
Formatting INTERNALSD:.android_secure...
E:Can't mount /dev/block/mmcblk0p37 (or /dev/block/mmcblk0p38)
(Invalid Argument)
Error mounting /internal_sdcard/.android_secure!
Skipping format...
Formatting CACHE...
Skipping format of /sd-ext.
Userdata wipe complete!
Many of the other "wipe commands" yield the same result.
I downloaded PH98IMG_ICS_3.14.605.12.zip from shipped-roms.com and tried to install it,
I get :
Install.....
Finding......
Opening.......
E:Can't open /sdcard/PH98IMG.zip
(bad)
Installation aborted.
What the hell did I do wrong and how do I fix it?
Related
So i've posted pieces of this in other threads assuming i knew what the problem was, but nobody has been able to help me so far so i'm posting the whole saga anew.
First off, my phone:
LazyPanda S-OFF
HBOOT:1.12.111
RADIO-1.12.11.0809
I was running MeanRom 4.8 with TWRP 2.3.0.1
Like so many others i tried to OTA update just to get stuck at the recovery screen on reboot. I then found out that i had no ROM installed. I tried to wipe (cache, dalvik, system, etc) and flash a new ROM but i kept getting FAIL messages in TWRP.
"Formatting and mounting partition...
e:error in /sdcard/meanrom-ics-v49-jewel-ltevo.zip
(status 1)
error flashing zip '/sdcard/meanrom-ics-v49-jewel-ltevo.zip'
updating partition details"
I figured it might be a botched DL so i did it manually, MD5 checked out after copying to the mounted device. Attempted to flash the clean DL and i got the same error message. I nandroid restored an old stock rooted ROM I had and it installed just fine. After booting up to the system ROM for the first time I immediately got an "Internal storage is low" error. Checked and after a clean restore (no apps installed, fresh out of the box...) i only have ~200MB free in the app storage section (out of 1.92GB). I can't fathom what's taking up all the other space, nothing seems to be there. Because of this i can't install Titanium, Rom Toolbox, or anything else that may be remotely useful. I tried fixing permissions and re-wiping, re-restoring and i got the same thing.
I tried to flash the TWRP 2.2.2.0 image from recovery thinking this was the problem and got this message:
"updating partition details
E:unable to open ums lunfile 'sys/class/android_usb/android/f_mass_sto.....
Formatting cache...done
Formatting Data... done
Using rm -rf on .android_secure
Updating partition details
E:unable to open ums lunfile 'sys/class/android_usb/android/f_mass_sto.....
E:unable to open zip file."
And THEN i tried to ABD flash the TWRP image through fastboot with "fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img" then 'fastboot flash boot openrecovery-twrp-2.2.2.0-jewel.img' and got this error:
"FAILED (remote partition is not allowed to be flushed!)"
So, i'm stuck with a device that loads a stock ROM, cant flash a new recovery or ROM, and cant' install anything useful because it's full after a restore. Does anyone have any suggestions how to clean/resore my partitions through ADB or a script? Your advice is much appreciated.
I can't help, but I suspect you'd have better luck posting this in the TWRP thread.
I'm wondering if fastboot erase cache would help here. I've seen that command used I think to clean a partition, but it may have been for something else. Sorry, this is a bit over my head. Hope you get help.
hurled from my AOKP'd Evo LTE. Enjoy.
You might have to re lock and run the RUU and then unlock and flash twrp, 2.3 has issues with the partitions for some reason so stick to 2.2
Try updating to the latest twrp. The latest is 2.3.1.0 not 2.3.0.1.
2.3.0.1 had issues which you can read about here
http://www.pocketables.com/2012/10/...for-htc-evo-4g-lte-fixes-rom-flash-death.html
It's been updated already? Cool
om4 said:
It's been updated already? Cool
Click to expand...
Click to collapse
Yeah, it fixes the mounting of the sdcards and the flashing rom problem
You may also want to get the 1.12.2222 hboot from the unlimited site. It has fastboot commands enabled.
I noticed you tried flashing TWRP to both the recovery and boot partitions...Do you get the same error when you flash to just recovery? TWRP should not be on boot.
Sent from my EVO LTE
Sorry to be the millionth person asking this, but I have nothing frozen, or uninstalled. I got this Phone with 2.3.5 Gingerbread I rooted it and played with it for a month then reverted it and then did a factory reset. Months and months later it finally OTA updated from Gingerbread (Stock) to Ice Cream Sandwich (Stock) Now that Jellybean is finally here, the OTA doesn’t work on my phone. For the past couple days I’ve been trying everything I could think of.
1.) I downloaded and installed update via Wifi, after the download completes, phone reboots, ¼ of the way through the droid falls over with no error, reboots again with a message dialog saying the update failed
2.) I downloaded and installed update via 4G, after the download completes, phone reboots, ¼ of the way through the droid falls over with no error, reboots again with a message dialog saying the update failed
3.) I did a factory reset from Settings | Privacy afterwards I download and installed update , after the download completes, phone reboots, ¼ of the way through the droid falls over with no error, reboots again with a message dialog saying the update failed
4.) I powered the phone off, start up in recovery, wipe cache partition, reboot again and do a factory reset again from Settings | Privacy afterwards I download and installed update , after the download completes, phone reboots, ¼ of the way through the droid falls over with no error, reboots again with a message dialog saying the update failed
5.) I powered the phone off, start up in recovery, wipe cache partition, and do a wipe data/factory reset, afterwards I download and installed update , after the download completes, phone reboots, ¼ of the way through the droid falls over with no error, reboots again with a message dialog saying the update failed
6.) I downloaded Blur_Version.6.16.211.X1912.Verizon.en.US.zip copied it to the SD card, rebooted into recovery and it failed yet again but at least this time I’ve got some info.
Install /sdcard/data …
Finding update package…
Opening update package…
Verifying update package…
Installing update…
Verifying current syste,…
Assert failed: apply_patch_check (“/system/build.prop”.
“8a12ff99c4109090ae956402167a1b33ecf58591”. “51834b29
73d2872c752bb7b089bb19bfadca8e7a”)
E: Error in /tmp/sideload/package.zip
(Status 7)
Install aborted.
Try to use option #1 on this: http://www.droidrzr.com/index.php/t...-razr-maxx-only/page__pid__104361#entry104361
Then try to update to JB via Recovery
Gus194 said:
Try to use option #1 on this: http://www.droidrzr.com/index.php/t...-razr-maxx-only/page__pid__104361#entry104361
Then try to update to JB via Recovery
Click to expand...
Click to collapse
Yea, I used Matt's 1.82 ulitity to install stock ICS when I had the same problm, after that the OTA went righ through with no problems.
I just flashed CM10.1 (23/03/2013) using CWM v6.0.3.0, followed trough every step of the tutorial, the ROM runs just fine but I just can't install gapps. (Trying gapps-jb-20130301-signed.zp)
Here's what i get:
- Finding update package...
- Opening update package...
- Installing update...
- Installing Google Apps for Android 4.2.2..
- Mouting system...
- Copying files...
- Fixing Permissions...
- Unmounting system...
- Installation complete!
Install from sdcard complete.
Then I wipe Dalvik cache, wipe data/factory reset and reboot.
And then... Nothing! It's just not showing up. Can anyone help me out? Am I doing something wrong?
PS.: I also getting that yellow warning sign once i downgraded to CWM v6.0.2.9, as CM10.1 tutorial asked. Any thoughts?
fbodra said:
I just flashed CM10.1 (23/03/2013) using CWM v6.0.3.0, followed trough every step of the tutorial, the ROM runs just fine but I just can't install gapps. (Trying gapps-jb-20130301-signed.zp)
Here's what i get:
- Finding update package...
- Opening update package...
- Installing update...
- Installing Google Apps for Android 4.2.2..
- Mouting system...
- Copying files...
- Fixing Permissions...
- Unmounting system...
- Installation complete!
Install from sdcard complete.
Then I wipe Dalvik cache, wipe data/factory reset and reboot.
And then... Nothing! It's just not showing up. Can anyone help me out? Am I doing something wrong?
PS.: I also getting that yellow warning sign once i downgraded to CWM v6.0.2.9, as CM10.1 tutorial asked. Any thoughts?
Click to expand...
Click to collapse
after installing the Gapps package do not wipe data/factory reset ma8, just wipe Cache/dalvik and then reboot phone
Got an improvement but not quite there yet. Tried to install an older version of gapps (for 4.0 android) and got a message when rebooting ("Unfortuantely, the process com.google.process.gapps has stopped)
Then it got locked on that messagind (it kept looping it around).
So then I went back to CWM and reinstalled updated gapps. Now I got the same message, but the phone booted. I successfully logged in to google account, but every time I reboot my phone I get that same message again.
One more thing. CWM 10.1 don't roll down status bar with updates and I just don't have a lock screen.
Any thoughts?
fbodra said:
Got an improvement but not quite there yet. Tried to install an older version of gapps (for 4.0 android) and got a message when rebooting ("Unfortuantely, the process com.google.process.gapps has stopped)
Then it got locked on that messagind (it kept looping it around).
So then I went back to CWM and reinstalled updated gapps. Now I got the same message, but the phone booted. I successfully logged in to google account, but every time I reboot my phone I get that same message again.
One more thing. CWM 10.1 don't roll down status bar with updates and I just don't have a lock screen.
Any thoughts?
Click to expand...
Click to collapse
all i would suggest is go for a fresh install of Rom and gapps and see. also try to check the MD5 of the dwnld'd zip file does match the one on the dwnld link
Sun90 said:
all i would suggest is go for a fresh install of Rom and gapps and see. also try to check the MD5 of the dwnld'd zip file does match the one on the dwnld link
Click to expand...
Click to collapse
If he doesn't want to follow your advice from your first post, it's his own fault
Sun90 said:
after installing the Gapps package do not wipe data/factory reset ma8, just wipe Cache/dalvik and then reboot phone
Click to expand...
Click to collapse
Thanks I did that, got the Play app working all right, but I only get that one. No navigator, no gmail, no anything else.
Download by yourself
I have a Samsung Galaxy Ace GT-S5830i which is rooted but on stock rom. I recently installed a live wallpaper "Exodus live wallpaper" from the play store and after going through the options it provided my phone just shutdown. I tried turning it back on and it started boot looping. I had a nandroid backup ready from CWM recovery but that would stop at data saying "Error while restoring /data!". I found this a bit odd so I factory reset it but with no luck. The next step I thought would be to flash back the stock using Odin. Again, no luck. After it says successful it reboots the phone which goes straight into recovery saying:
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
Reebooting...
and boot loop again.
I've tried re-partitioning, wiping cache, wiping dalvik cache, factory resets, formatting everything, using adb but with no luck (couldn't get root), tried restoring previous backups, trying different roms and copying the files directly to the directories using a root file manager.
I am now exhausted after 4 days of near sleepless nights trying to fix it and with nothing to show for it :crying: .
Please Help!!!!!
You haven't look into FAQ!
faq was one of the first things i checked and i've tried repartitioning with pit and i still get the same
lew101 said:
faq was one of the first things i checked and i've tried repartitioning with pit and i still get the same
Click to expand...
Click to collapse
Use CWM to format everything except sdcard
Then flash firmware with Odin 3.07 with pit file and after flashing, go to recovery and wipe data
Try this and report. I've been in the situation and dozens more. We can always find a way out
iamareebjamal said:
Use CWM to format everything except sdcard
Then flash firmware with Odin 3.07 with pit file and after flashing, go to recovery and wipe data
Try this and report. I've been in the situation and dozens more. We can always find a way out
Click to expand...
Click to collapse
Just tried it. On leaving recovery after flash it was still showing:
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
and it still boot loops
lew101 said:
Just tried it. On leaving recovery after flash it was still showing:
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
and it still boot loops
Click to expand...
Click to collapse
Flash a stock rom which is splitted into 4 parts ie including bootloader file using Odin v1.87.
Sent from my GT-S5830i using xda app-developers app
andy.acei said:
Flash a stock rom which is splitted into 4 parts ie including bootloader file using Odin v1.87.
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
still doing the same thing
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
and still boot looping :crying:
P.S. sorry about the late reply
lew101 said:
still doing the same thing
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
and still boot looping :crying:
P.S. sorry about the late reply
Click to expand...
Click to collapse
UPDATE
I've used Aroma file manager to see if I can find these files and they are exactly where they should be with read/write permissions for root and system (rw-rw-r--) so I have no idea why recovery can't open them.
also is there any way to force android to read them or to copy "recovery_kernal_log.txt" manually?
I'm thinking of taking it to samsung for repairs as nothing has worked so far so if anyone has some additional advice please post it before thursday 15th of august
First clear cache data from stock recovery. Than use cwm format system and data then enter download mode and use odin with pit file. U must use your country spesific firmware. If problem persists after all you may have a faulty phone.
Ps: take out sd card after odin flashes successfully in case problem related to sd card.
:: Freedom... ::
ChelebiTech said:
First clear cache data from stock recovery. Than use cwm format system and data then enter download mode and use odin with pit file. U must use your country spesific firmware. If problem persists after all you may have a faulty phone.
Ps: take out sd card after odin flashes successfully in case problem related to sd card.
:: Freedom... ::
Click to expand...
Click to collapse
Looks like I have a faulty phone then.
I wonder how that would have happened from using the live wallpaper as it was perfectly fine before that.
lew101 said:
Looks like I have a faulty phone then.
I wonder how that would have happened from using the live wallpaper as it was perfectly fine before that.
Click to expand...
Click to collapse
Probably its the last drop makes phone dead! Usually high powered magnets or heat may cause the error. If you use your phone while charging it gets really hot. Hope phone service can repair it.
:: Freedom... ::
same issue
Hi everyone, im having the same problem with my samsung galaxy ace gt5830i, after installing a playstore app, the phone just freezed and now its looping at start, the same error messege
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
also tryed flashing, and re - installing with odin, but nothing works, its a failure in the phone? isnt there is a way to install the bios firmware again?
sorry for my writing , my english is not very good, thanks to anyone who can guive an answer.
Radnico9 said:
Hi everyone, im having the same problem with my samsung galaxy ace gt5830i, after installing a playstore app, the phone just freezed and now its looping at start, the same error messege
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
also tryed flashing, and re - installing with odin, but nothing works, its a failure in the phone? isnt there is a way to install the bios firmware again?
sorry for my writing , my english is not very good, thanks to anyone who can guive an answer.
Click to expand...
Click to collapse
Just goto CWM wipe data/cache goto mount and storage do format system and data
And then Goto samsung's stock recovery Do wipe data / cache and then Flash Stock ROM That's it if
the problem is still so again do wipe/data in stock recovery
Sent from my Ace-i
I fixed it
lew101 said:
I have a Samsung Galaxy Ace GT-S5830i which is rooted but on stock rom. I recently installed a live wallpaper "Exodus live wallpaper" from the play store and after going through the options it provided my phone just shutdown. I tried turning it back on and it started boot looping. I had a nandroid backup ready from CWM recovery but that would stop at data saying "Error while restoring /data!". I found this a bit odd so I factory reset it but with no luck. The next step I thought would be to flash back the stock using Odin. Again, no luck. After it says successful it reboots the phone which goes straight into recovery saying:
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
Reebooting...
and boot loop again.
I've tried re-partitioning, wiping cache, wiping dalvik cache, factory resets, formatting everything, using adb but with no luck (couldn't get root), tried restoring previous backups, trying different roms and copying the files directly to the directories using a root file manager.
I am now exhausted after 4 days of near sleepless nights trying to fix it and with nothing to show for it :crying: .
Please Help!!!!!
Click to expand...
Click to collapse
Hello,
Well i have the same phone as you and have just fixed my boot loop well today i have found how to do it first turn on your phone until you get the boot loop then remove the back of your phone then remove your battery and place it back in and then put your back of your phone back on and the hold power home and volume up until it says the first words of load ing up (Samsung Galaxy Ace GT-S5830i) then let go. when it turns up with the red writing press volume down until you get to factory reset then press power wait until it resets then press volume up until you get to reboot then press power wait until it reboots GIVE IT TIME IT WILL BOOT LOOP BUT THEN LOAD go through with it all sign in with you google account wait until it loads up your phone and there
hell
i have also same problem just some different, my cell phone can,t access boot
Please Help!!!!![/QUOTE]
i was also facing the same problem
lew101 said:
I have a Samsung Galaxy Ace GT-S5830i which is rooted but on stock rom. I recently installed a live wallpaper "Exodus live wallpaper" from the play store and after going through the options it provided my phone just shutdown. I tried turning it back on and it started boot looping. I had a nandroid backup ready from CWM recovery but that would stop at data saying "Error while restoring /data!". I found this a bit odd so I factory reset it but with no luck. The next step I thought would be to flash back the stock using Odin. Again, no luck. After it says successful it reboots the phone which goes straight into recovery saying:
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
Reebooting...
and boot loop again.
I've tried re-partitioning, wiping cache, wiping dalvik cache, factory resets, formatting everything, using adb but with no luck (couldn't get root), tried restoring previous backups, trying different roms and copying the files directly to the directories using a root file manager.
I am now exhausted after 4 days of near sleepless nights trying to fix it and with nothing to show for it :crying: .
Please Help!!!!!
Click to expand...
Click to collapse
if your are still faceing this problem ..here is my skype ID :dotusman...i will tell you the whole procedure to update your firmware.and im sure it will fixed it..soryy for my english..
lew101 said:
I have a Samsung Galaxy Ace GT-S5830i which is rooted but on stock rom. I recently installed a live wallpaper "Exodus live wallpaper" from the play store and after going through the options it provided my phone just shutdown. I tried turning it back on and it started boot looping. I had a nandroid backup ready from CWM recovery but that would stop at data saying "Error while restoring /data!". I found this a bit odd so I factory reset it but with no luck. The next step I thought would be to flash back the stock using Odin. Again, no luck. After it says successful it reboots the phone which goes straight into recovery saying:
E:Can't open /data/log/recovery_log.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernal_log.txt
Reebooting...
and boot loop again.
I've tried re-partitioning, wiping cache, wiping dalvik cache, factory resets, formatting everything, using adb but with no luck (couldn't get root), tried restoring previous backups, trying different roms and copying the files directly to the directories using a root file manager.
I am now exhausted after 4 days of near sleepless nights trying to fix it and with nothing to show for it :crying: .
Please Help!!!!!
Click to expand...
Click to collapse
Follow every word given http://forum.xda-developers.com/showthread.php?t=1840645 and use the files downloaded from that thread . It will work[emoji2] [emoji2]
In the end i had to take it back to where i purchased the phone originally and they replaced free of charge.
help
Hey can I ask? How much did you pay for to fix your phone? We have the same phone and we have the same problem. im just playing modded game and it restarts and saying cant open copykernel file etc...
please help me ! I've try to reflash it . And its not fix. Ive been searching for almost two weeks . But I cant see other solution for how to fix it . Please help me.
Thank you.
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