[T311] Unable to install stock firmware after installing cm12 - Galaxy Tab 3 Q&A, Help & Troubleshooting

I install cm12 on my tab but before I had taken the nandorid backup
And I have done this so many time "installed cm12" again revert back to "stock 4.4.2 using backup" again and again in last 2 months like(~ 20 times)
But now dont now what happend whenever I restore in twrp it it gives an error
(20mb) <some path >recovery.Img.win size is larger than <some path>mpblock(8mb)
(something like this error)
Then I try with Odin its also giving me error when it trying to flash recovery.IMG and am getting fail msg every time
Someone please help me out

hardythaker said:
I install cm12 on my tab but before I had taken the nandorid backup
And I have done this so many time "installed cm12" again revert back to "stock 4.4.2 using backup" again and again in last 2 months like(~ 20 times)
But now dont now what happend whenever I restore in twrp it it gives an error
(20mb) <some path >recovery.Img.win size is larger than <some path>mpblock(8mb)
(something like this error)
Then I try with Odin its also giving me error when it trying to flash recovery.IMG and am getting fail msg every time
Someone please help me out
Click to expand...
Click to collapse
There is no reason to ever include recovery in your backup. Do a restore and uncheck the recovery option.

Related

[Q] CWM v6.0.4.3 N7100 problem in supporting Stock 4.3 ROM restoration

I have an International version of Note 2 (N7100) rooted with CWM recovery 6.0.4.3 (touch) installed.
In order to analyze the wakelock problem (most of the time, the CPU is at 200Mhz rather than deep sleep when it is not used. Also "battery info" tells me the battery was mostly used by "Android OS"), I have to factory reset the device and flash to the stock 4.3 ROM. I monitored the newly setup phone for a day before I rooted it and install CWM recovery 6.0.4.3 for full system backup.
Happily used the phone for a week. After my son played with it for an afternoon, the wakelock problem comes back. Not sure what settings did he changed or apps he installed. So I go ahead backup the current rom and restore the phone from the previous backups.
Here was what I have done:
1. Boot into Clockworkmod recovery
2. Clear all partition / factory reset
3. Select Backup and restore.
4. Select the backup directory that I want to restore from (the one without wakelock problem)
5. Wait for the restoration process to finish
6. System reboots.
After system rebooted, it kept popping up "unfortunately com.google.process.gapps has stopped". The device was not usable, because the message will pop up again once I click OK to dismiss it. I then tried the following, but none of them works.
1. Restore from different backups
2. Enable "download service" from application manager. (It was not disabled)
3. Reset all apps settings from "Application manager" (menu)
Trying option 2 and 3 was a pain as the popup messages was blocking the screen, I have to be really quick to dismiss the message box and touch on the command.
BTW, the CWM recovery touch was installed from Odin, not from ROM manager. I experience the following problems:
1. Issue with "backup current ROM" command from "ROM manager". It cannot find /ex_sdcard when it goes to recovery.
2. It cannot find dalvik partition to wipe.
3. Backup to zip command does not work. It does backup the files and at the end it said the backup file is in /storage/sdcard/clockworkmod/image.zip. But I cannot find the zip file any where, including the external sd card.
Here is what I did to restore my phone to previous state with stock ROM:
1. Use Odin to flash the stock rom (samsung 4.3 for N7100), which will restore the stock recovery instead of the CWM recovery.
2. Reboot the device.
3. Use Odin to flash CWM recovery.
4. Reboot the device.
5. Go into recovery and restore only the /data partition.
6. Wipe /cache.
7. Reboot the device
8. Boot back to recovery and root the device.
Now I have the phone at my previous state.
Does it mean CWM recovery will not work with stock ROMs ? or I did something wrong.
Also, I still have not find out what was the cause for the wakelock problem in "Android OS". I have two backups where one has the problem and one does not. I have tried untar them and compare them with WinMerge, but there were a lots of files to go through.
fatice said:
I have an International version of Note 2 (N7100) rooted with CWM recovery 6.0.4.3 (touch) installed.
In order to analyze the wakelock problem (most of the time, the CPU is at 200Mhz rather than deep sleep when it is not used. Also "battery info" tells me the battery was mostly used by "Android OS"), I have to factory reset the device and flash to the stock 4.3 ROM. I monitored the newly setup phone for a day before I rooted it and install CWM recovery 6.0.4.3 for full system backup.
Happily used the phone for a week. After my son played with it for an afternoon, the wakelock problem comes back. Not sure what settings did he changed or apps he installed. So I go ahead backup the current rom and restore the phone from the previous backups.
Here was what I have done:
1. Boot into Clockworkmod recovery
2. Clear all partition / factory reset
3. Select Backup and restore.
4. Select the backup directory that I want to restore from (the one without wakelock problem)
5. Wait for the restoration process to finish
6. System reboots.
After system rebooted, it kept popping up "unfortunately com.google.process.gapps has stopped". The device was not usable, because the message will pop up again once I click OK to dismiss it. I then tried the following, but none of them works.
1. Restore from different backups
2. Enable "download service" from application manager. (It was not disabled)
3. Reset all apps settings from "Application manager" (menu)
Trying option 2 and 3 was a pain as the popup messages was blocking the screen, I have to be really quick to dismiss the message box and touch on the command.
BTW, the CWM recovery touch was installed from Odin, not from ROM manager. I experience the following problems:
1. Issue with "backup current ROM" command from "ROM manager". It cannot find /ex_sdcard when it goes to recovery.
2. It cannot find dalvik partition to wipe.
3. Backup to zip command does not work. It does backup the files and at the end it said the backup file is in /storage/sdcard/clockworkmod/image.zip. But I cannot find the zip file any where, including the external sd card.
Here is what I did to restore my phone to previous state with stock ROM:
1. Use Odin to flash the stock rom (samsung 4.3 for N7100), which will restore the stock recovery instead of the CWM recovery.
2. Reboot the device.
3. Use Odin to flash CWM recovery.
4. Reboot the device.
5. Go into recovery and restore only the /data partition.
6. Wipe /cache.
7. Reboot the device
8. Boot back to recovery and root the device.
Now I have the phone at my previous state.
Does it mean CWM recovery will not work with stock ROMs ? or I did something wrong.
Also, I still have not find out what was the cause for the wakelock problem in "Android OS". I have two backups where one has the problem and one does not. I have tried untar them and compare them with WinMerge, but there were a lots of files to go through.
Click to expand...
Click to collapse
I did not find the problem with restoration using CWM, but did find out what causes the wakelock: "Automatic call recorder Pro".
Disable the auto start function and battery drains is back to 1% per hour during standby.
fatice said:
I have an International version of Note 2 (N7100) rooted with CWM recovery 6.0.4.3 (touch) installed.
In order to analyze the wakelock problem (most of the time, the CPU is at 200Mhz rather than deep sleep when it is not used. Also "battery info" tells me the battery was mostly used by "Android OS"), I have to factory reset the device and flash to the stock 4.3 ROM. I monitored the newly setup phone for a day before I rooted it and install CWM recovery 6.0.4.3 for full system backup.
Happily used the phone for a week. After my son played with it for an afternoon, the wakelock problem comes back. Not sure what settings did he changed or apps he installed. So I go ahead backup the current rom and restore the phone from the previous backups.
Here was what I have done:
1. Boot into Clockworkmod recovery
2. Clear all partition / factory reset
3. Select Backup and restore.
4. Select the backup directory that I want to restore from (the one without wakelock problem)
5. Wait for the restoration process to finish
6. System reboots.
After system rebooted, it kept popping up "unfortunately com.google.process.gapps has stopped". The device was not usable, because the message will pop up again once I click OK to dismiss it. I then tried the following, but none of them works.
1. Restore from different backups
2. Enable "download service" from application manager. (It was not disabled)
3. Reset all apps settings from "Application manager" (menu)
Trying option 2 and 3 was a pain as the popup messages was blocking the screen, I have to be really quick to dismiss the message box and touch on the command.
BTW, the CWM recovery touch was installed from Odin, not from ROM manager. I experience the following problems:
1. Issue with "backup current ROM" command from "ROM manager". It cannot find /ex_sdcard when it goes to recovery.
2. It cannot find dalvik partition to wipe.
3. Backup to zip command does not work. It does backup the files and at the end it said the backup file is in /storage/sdcard/clockworkmod/image.zip. But I cannot find the zip file any where, including the external sd card.
Here is what I did to restore my phone to previous state with stock ROM:
1. Use Odin to flash the stock rom (samsung 4.3 for N7100), which will restore the stock recovery instead of the CWM recovery.
2. Reboot the device.
3. Use Odin to flash CWM recovery.
4. Reboot the device.
5. Go into recovery and restore only the /data partition.
6. Wipe /cache.
7. Reboot the device
8. Boot back to recovery and root the device.
Now I have the phone at my previous state.
Does it mean CWM recovery will not work with stock ROMs ? or I did something wrong.
Also, I still have not find out what was the cause for the wakelock problem in "Android OS". I have two backups where one has the problem and one does not. I have tried untar them and compare them with WinMerge, but there were a lots of files to go through.
Click to expand...
Click to collapse
I have to say, I did encounter the replication of the same exact problem. It kept popping up "unfortunately com.google.process.gapps has stopped". I was using the same CWM recovery 6.0.4.3 for my N7100 using stock android 4.3.
Try to do so many things but fail to get rid of the pop up. At the end, I ended up having to flash rom using Odin.
Anyway, I think, there's some bug with CWM recovery 6.0.4.3 that caused the error to happen. I managed to use TRWP 2.6.3.1 without any problem to restore after that.
Regards,
Had exactly same problem, i downgraded cwm from 6.0.4.6 to 6.0.4.4 by using odin
Than restore works fine no problems with services.
Note 3 sm-n900w8
warlab said:
Had exactly same problem, i downgraded cwm from 6.0.4.6 to 6.0.4.4 by using odin
Than restore works fine no problems with services.
Note 3 sm-n900w8
Click to expand...
Click to collapse
Hi.
How did you downgraded CWM using odin? I am stuck in the same problem.
Khizer Jalal
khizerjalal said:
Hi.
How did you downgraded CWM using odin? I am stuck in the same problem.
Khizer Jalal
Click to expand...
Click to collapse
Download image and overwrite existing one
Now i see that i have entered the rooting world in it's darkest time
I had the exact same problem of yours with CWM 6.0.4.3 and and the exact same problem with titanium backup(when i restore APP DATA for almost all apps they crash and keep popping messages). so there was no restore feature for me for long time
BUT TB restoring of App data is fixed when i updated TB to latest version and the CWM nandroid after-restore problem is fixed when yesterday i upgraded to philz 6.46.3, the restored ROM works flawlessly.
Now I think(not sure) what was going on is related to something called "FIX Permissions" or in other words when we restore system + data things get messed up that each app can't find it's own DATA folder causing it to crash. CWM and titanium backup didn't use to fix that mess but now they do so these problems won't occur anymore.

[Q] Kernel Panic Upload Mode

Hey guys, I went to root my Note 3 this morning and have run into some trouble. I used Odin to push TWRP, and TWRP to install my SU.zip. upon rebooting from TWRP the phone was acting a little strange, I downloaded Root checker but it was never able to verify root priveledges, it said the system was running slow. So I rebooted the phone. On boot up it now goes into Kernel Panic Upload mode with the following:
Kernel Panic!
KRAIT INFO
PC is at adreno_init+0x130/0x2d4
LRis at adreno_init+0x130/0x2d4
Panic caller : die+0x1d8/0x240
Panic Msg : Fatal exception
Thread : SurfaceFlinger:458
Speed_bin : 0x1
Wait...
Done!
Thankfully I can still get into recovery mode, however whether flashing a new rom or restoring my back up, I still am not able to boot because of the Panic Mode. I've tride installing 2 different ROMS and got this message last I tried:
Creating Symlink...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sd/Liquid-Kitkat-v3.0-NIGHTLY-hltetmo.zip'
Error flashing zip 'external_sd/
updating partition details...
Failed
I'm at work right now so I don't have access to Odin at the moment but was thinking I would try to push a stock back when I have a chance. Do you guys have any ideas?
macfable said:
Hey guys, I went to root my Note 3 this morning and have run into some trouble. I used Odin to push TWRP, and TWRP to install my SU.zip. upon rebooting from TWRP the phone was acting a little strange, I downloaded Root checker but it was never able to verify root priveledges, it said the system was running slow. So I rebooted the phone. On boot up it now goes into Kernel Panic Upload mode with the following:
Kernel Panic!
KRAIT INFO
PC is at adreno_init+0x130/0x2d4
LRis at adreno_init+0x130/0x2d4
Panic caller : die+0x1d8/0x240
Panic Msg : Fatal exception
Thread : SurfaceFlinger:458
Speed_bin : 0x1
Wait...
Done!
Thankfully I can still get into recovery mode, however whether flashing a new rom or restoring my back up, I still am not able to boot because of the Panic Mode. I've tride installing 2 different ROMS and got this message last I tried:
Creating Symlink...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sd/Liquid-Kitkat-v3.0-NIGHTLY-hltetmo.zip'
Error flashing zip 'external_sd/
updating partition details...
Failed
I'm at work right now so I don't have access to Odin at the moment but was thinking I would try to push a stock back when I have a chance. Do you guys have any ideas?
Click to expand...
Click to collapse
Well not that it matters that much but thought i'd post that going back to stock via odin worked in case any one else runs into this issue.

[Q] Please help. I have bricked my N5110

i followed a guide from techbeasts.com
using ODIN to push "CF-Auto-Root-konawifi-konawifixx-gtn5110"
then with ODIN i pushed "RECOVERY_GT-N5110-CivZ_rev1.1-PhilZ_5-ODIN.tar"
then i downloaded a rom and through the CWM recovery i chose "clean for new rom" or something along those lines
trying to install several different roms keeps giving me a "status 7". i tried multiple recovery versions of CWM, and 1 TWRP.
now the backup i MOVED to an external SD wont flash back, it gives me a md5 mismatch error.
please help!!!
right before i get the "status 7" error it says:
set_metadata_recursive: some changes failed
i was able to get my old back up to work when i went to restore.
THIS IS WHY ITS IMPORTANT TO BACK UP YOUR RESTORE FILE TO AN *EXTERNAL SD CARD*
i broke in to the back up file and cleaned out the "nandroid.md5" with a text editor, tried the restore and it worked!

system partition size reduced, Please somebody solve my issue

Honorable forum members,
i can't explain my problem more detailed than this and attached logs and screenshots
I am having a problem with my redmi 1s since 4 days (reporting daily to everybody and every thread i know, Now i came to some conclusion *from my point of view*) i.e., System partition size reduced ( due to "My fault" of trying to expand system storage). Now i can't flash any custom rom on my phone. (Except CM11). I'm getting an error, i.e.,
1. strucks at - "Patching system image unconditionally"
2. and some times it gives me an error "E/system unable mount" and breaks operation here.
I was using CM14.1 official rom till 12th of this month ( So no need to doubt about proper installing of custom rom). As i'm unable to install any custom rom on my phone (tried CM12,13,14,14.1, RR, AICP). Then i tried MIUI. Surprisingly I can install MIUI from recovery (works well) but not from fastboot (by fastboot, after installation strucks at Mi Logo, wiping cache and dalvik cache doesn't work too). ***Another big wonder is that i'm able to install CM11 (works well but not used gapps)***. I think my phone no longer upgrades from Kitkat. Is it true?
Then after several research and several suggestions from some honorable forum members i found that (may be) the problem is with system partition. i.e., My system partition size decreased. It was my fault. I tried to increase my system partition to install aroma gapps (in the need of OK Google voice recognition from any screen and due to some google apps were creating a lot of cache) using a thread on increasing system partition size from our forum (not to specify). Then i realized that i'm not the one who can modify anything on somebody Else's rom- as after receiving a update, it took one after another all the google apps from me.
Then i used revert back flash file from the same thread, but it took something extra along with my some of my phones original system partition size. Tried restoring backup but not worked.
While installing custom rom it strucks at " patching system image unconditionally" (waited every time at least an hour), as i'm not being able to do anything, so i restart my phone. Then when i try again it gives me an error "E/System unable to mount". Then if i try to wipe or resize or repair nothing works gives same error. But if i format using f2fs and then again using ext4, then i can mount system partition in MOUNT in twrp (also tried Philz recovery and CM recovery- same issue). After Mounting when i try to install again it strucks at " patching system image unconditionally". So same cycle continues. But when i try to insatll MIUI or CM11 it works fine -after mounting system partiton ( not even takes command i.e., " patching system image unconditionally" in terminal).
Also i tried to flash the rom using adb sideload strucks at 45%, checked the rom file whether corrupted by extracting and for exact rom redownloaded. But there is no improvement.
Maybe Because of this I'm not being able to flash any custom rom on my device anymore. I've took some recovery log files and some screenshots from recovery of my phone. Here below i'm attaching them.
Finally i would like to inform you that
i) i'm using latest recovery- twrp 3.0.2-1,
ii)and latest firmware- v8.1.2.0. (used whichever firmware required for every rom).
iii) Now i'm using global stable MIUI v8.1.2.0
So now i request you all to please help me in installing a custom rom on my Redmi 1s.
I have updated the tutorial with the solution for your problem follow this link
http://forum.xda-developers.com/redmi-1s/general/tut-repartition-redmi-1s-to-increase-t3506904

Unable to restore backup

I am using orangefox recovery, make backup with miui 11 stock rom.
While play around with custom rom, and wanna restore backup to get few apps item, it's error in wiping vendor
My error message while restoring vendor
"e2fsdroid -e -S /file_contexts -a /vendor /dev/block/mmcblk0p62 process ended with error : 1"
"Unable to wipe vendor"
I tried to restore all items, and restore vendor last. It worked fine in restoring, but my phone can't boot. It show fastboot mode.
Any ideas what happen ?
Read around on internet, some said u need to disable lock screen before backup ?
me too. I stuck at mi logo
If you'll get ever some weird error in OrangeFox Recovery just simple reboot it to recovery again. In menu you have that option. Than try again...
Some super tip: DONT EVER TRY TO FLASH MIUI ROM/FIRMWARE UNDER RECOVERY!!!! Use MI FLASH TOOL!!! You can brick device like you two did . Dowload fastboot MIUI ROM and flash it.
Dont restore apps from backup lool. Use app like Titanium backup to backup/restore your apps+data.
Good luck

Categories

Resources