I have got an Olipad (clone of Malata zpad T2 or not?)with Tap UI 1.2.4222 and my problem is that everytime I try to istall a rom (1.2 branch) I always am unable to perform system.img download , I get always the error message "Nverror 0x12002" (bad data). All commads issued before dowloading system.img are successfully. I tried again and again but always the same error.
I have also a rom that should return me to original stock so eventually I modified its .cfg for istalling Clockwork 3.0.2.8 instead of original recovery and NOT install system.img, this worked fine and now I can enter the clockwork recovery. Then I wrote a .bat for downloading only system.img but still the same error . I tried not only the stock rom but a lot of rom for 1.2, same result. The only rom that successufully download the system is the one in the "format tool" of XDA, unfortunatenly this rom seems to be of 1.1. branch because I get "magic values mismatch"
Is it possible my internal rom is someway damaged? if not anyone know what is the problem?
thanks
Ok, none has idea.
maybe the usb cable?
Have you repartitioned using cwm?
Yes I have repartitioned by mean of cwm and wiped all. Now the situation is that, after a lot of failed tentatives, I eventually succeded in flashing the stock rom, then I backed it up by cwm. After that I tried again to flash the same stock rom in the same way I did before and again I got Nverror0x120002 (also with other roms), but this time I had the back up and used cwm to restore the system. So I suppose may the usb cable (is made by nokia) that has some problems, it worked only one time.
Related
Hey everybody!
I have some serious issues here.... Today I wanted to flash my TF101G (german version) from the HC to the ICS version of the Revolver Rom. Of course I made a backup as usual before getting to work. I also flashed to the newest version of CWM recovery, as recommended.
Unfortunately it seems that something went wrong.... During start-up the ASUS splashscreen appears but nothing else happens (bootloop?). At first I though that doesn't matter, because I could just restore the previous backup. But when I got into CWM recovery, I had to find out that this new fancy touch crap version is not able to access the external sd-card of my Transformer! So I'm not able to restore anything or install any ZIPs...
Next thing I tried was to flash either the ROM or the recovery (downgrade for sd-card access) via NVFlash. So I installed the driver, got into APX mode, but nothing happens. Well actually not nothing but instead, depending on which batchfiles I use, it either just kicks me out of APX mode (driver is not shown in the devicemanager anymore) or I get the error message "bla bla bla... command send failed (usb write failed)"
And now I ran out of ideas....
Can you still get into clockworkmod recovery touch? If you can try using the ADB from there to 'adb push rom.zip filepath/filepath' to get it onto your Internal SD and then reflash from there. I just use cwm 3.2, it's rock stable and never gives me issues, and after reading all of the issues with new versions and lack of ext SD support I refuse to update.
Darth Valda said:
Hey everybody!
I have some serious issues here.... Today I wanted to flash my TF101G (german version) from the HC to the ICS version of the Revolver Rom. Of course I made a backup as usual before getting to work. I also flashed to the newest version of CWM recovery, as recommended.
Unfortunately it seems that something went wrong.... During start-up the ASUS splashscreen appears but nothing else happens (bootloop?). At first I though that doesn't matter, because I could just restore the previous backup. But when I got into CWM recovery, I had to find out that this new fancy touch crap version is not able to access the external sd-card of my Transformer! So I'm not able to restore anything or install any ZIPs...
Next thing I tried was to flash either the ROM or the recovery (downgrade for sd-card access) via NVFlash. So I installed the driver, got into APX mode, but nothing happens. Well actually not nothing but instead, depending on which batchfiles I use, it either just kicks me out of APX mode (driver is not shown in the devicemanager anymore) or I get the error message "bla bla bla... command send failed (usb write failed)"
And now I ran out of ideas....
Click to expand...
Click to collapse
You 101G is NOT nvflash compatible. You don't have SBK v1.
The only thing you can try is ADB push the necessary files to the internal sd storage.
I couldn't connect my device via ADB before, but after trying a few things it works now.....
But ADB really gave me a hard time! In the beginning I pushed some testfiles. First they were pushed but somehow they did not appear in specific folders on the sd-card in CWM. Others just gave me the message "protocol error".
After restarting the deamon and remounting the sd-card I was finally able to push an older version of CWM and the ROM file. Then I just wanted to restore my old backup via CWM, but I ended up hanging at the ASUS splashscreen again. Only reflashing the ROM itself solved it in the end.
THX
Darth Valda said:
I couldn't connect my device via ADB before, but after trying a few things it works now.....
But ADB really gave me a hard time! In the beginning I pushed some testfiles. First they were pushed but somehow they did not appear in specific folders on the sd-card in CWM. Others just gave me the message "protocol error".
After restarting the deamon and remounting the sd-card I was finally able to push an older version of CWM and the ROM file. Then I just wanted to restore my old backup via CWM, but I ended up hanging at the ASUS splashscreen again. Only reflashing the ROM itself solved it in the end.
THX
Click to expand...
Click to collapse
Good to hear you got it working. Just a little FYI for the future.
Nandroid restore does not restore the kernel so next time just flash the ROM before or after the nandroid restore. That should put the correct kernel in place for it to boot up.
Did you try reflashing an earlier kernel? Those backups haven't been designed to store/restore kernel data (for us anyway). I think I had a similar experience, back when I was trying early AOSP ICS.
Hey! Thanks for the heads up, everybody!
I always thought that the nandroid backup restores everything (e.g. ROM, settings, base, kernel, etc.). That explains why the restore after the screwed up update to ICS didn't work anymore and why I got stucked in a bootloop again.
So even that seems not to be the last line of defense if you brick your device....
Hello,
I have a P3113 that I have previously rooted under 4.0.4, flashed with the french 4.1.1 via mobile odin, and now am trying to flash CWM on it so I can install CM10. I've since factory reset it, so I was hoping to be able to flash straight from CWM (as the CM instructions say), but it appears I don't have CWM anymore and instead have "Android system recovery <3e>". I've tried copying cwm zip files over to the SD card and then updating from those within system recovery, but it always says "E:signature verification failed."
What should I try next?
Thanks in advance!
Hello,i accidentally deleted my operating system,i tried everything to flash a new one ,every custom roms out there.
The TWRP version is 2.5.0.0
Everytime i execute the ZIP files from TWRP errors appear :
Error flashing zip '/sdcard/BackToBasicsV2.zip'
Error executing updater binary in zip : 'sdcard/BackToBasics'
Could you provide me a working tutorial?I tried every tutorial from here and nothing worked,i don't know what to do anymore.
I had a similar problem in which I accidentally pressed factory reset in bootloader instead of recovery (WHY ARE THEY SO CLOSE?!). Anyway, I ended up having to factory reset from recovery and wipe everything on my phone, then I adb pushed a rom to my phone and it finally let me flash it. Although I recommend waiting until someone else posts something as this is more of a "last resort" lol
S1mpleR said:
Hello,i accidentally deleted my operating system,i tried everything to flash a new one ,every custom roms out there.
The TWRP version is 2.5.0.0
Everytime i execute the ZIP files from TWRP errors appear :
Error flashing zip '/sdcard/BackToBasicsV2.zip'
Error executing updater binary in zip : 'sdcard/BackToBasics'
Could you provide me a working tutorial?I tried every tutorial from here and nothing worked,i don't know what to do anymore.
Click to expand...
Click to collapse
Connect your phone to your PC find it in devices and format it... Download twrp 2.3.3 recovery image and install it with fast boot.. Then paste a ROM to your SD card and flash away NP...don't forget the boot.IMG when flashing your new ROM it will have to be flashed with fast boot also..
Sent from my One S using xda premium
Still not working,anyone please,any other ideas?
I have a rooted (Superuser 3.1.3) TF101 with TWRP 2.7.0.1. I HAD Katkiss 4.3 installed. One day the tablet locked up and then starting bootlooping. I went into recovery, wiped everything, did factory reset, format /system.
Then I tried to reflash Katkiss 4.3_020, it failed with "set_perm: some changes failed". I then tried katkiss 4.4.2_023c - it failed with a similar error message. Tried flashing stock (US_epad-user-9.2.1.27) - same thing. The first part of the error message for all three ROMs is the same set_perm failure. The next couple of lines gives different error messages depending on the ROM. Generally something like: "E: error executing updater binary in zip".
Now I have a tablet with no ROM on it (when I tried to boot it hangs at the ASUS screen). I can get into the TWRP recovery menu just fine - I can flash other things like superuser or gapps without error. But any ROM I try to flash gives the set_perm error.
Any thoughts?
Chris
Try using Easyflasher to flash a different version of TWRP in case recovery is the problem, TWRP builds newer than 2.3.2.3 are not official builds, they have been continued by another member here once the project was abandoned by the original team
http://forum.xda-developers.com/showthread.php?t=1688012
Use Easyflasher to flash TWRP again - then try flashing KatKiss #23
Thanks but...
Easyflasher doesn't seem to work for me anymore (odd because it is what I first used to root/update my TF101). It runs and declares success - but nothing gets pushed to my device. Tried both SBK1 and SBK2. Using universal naked 0.72 and 0.73 on win7 64 bit.
I tried to find an older version of TWRP like you suggested - but I couldn't. Seems they want you to use "goo manager" from the play store... which doesn't work for me since I can't boot... And the goo website doesn't list an older TWRP for my device.
In any case, the latest TWRP seems to work in every other respect. I read somewhere that superuser can set an "immutable" bit that can survive a wipe? If true - could that be my permissions problem?
Chris
stuck on load screen
*Detection* said:
Try using Easyflasher to flash a different version of TWRP in case recovery is the problem, TWRP builds newer than 2.3.2.3 are not official builds, they have been continued by another member here once the project was abandoned by the original team
http://forum.xda-developers.com/showthread.php?t=1688012
Use Easyflasher to flash TWRP again - then try flashing KatKiss #23
Click to expand...
Click to collapse
I'm new as one can get at this and likely deserve any hammering I may get....TF1010 B70, CWM 5.8.3.4, I know I missed a step somewhere. I can't recover to 4.3 as the back up was bad, not recognized by any computer, loops to recovery and holding power and vol dn the booting to the linuz get me a long (14 hrs) flashing KatKiss boot screen.
I've tried Easyflasher aswell with no results, Please, any hope for this thing, Thanks in advance!
Sounds like your problem is a bit different - can you get into your bootloader? After voldown+power you should see some small text in the upper left of the screen then immediately hit vol up.... From there you should be able to reflash any ROM...
ldwhyte said:
I'm new as one can get at this and likely deserve any hammering I may get....TF1010 B70, CWM 5.8.3.4, I know I missed a step somewhere. I can't recover to 4.3 as the back up was bad, not recognized by any computer, loops to recovery and holding power and vol dn the booting to the linuz get me a long (14 hrs) flashing KatKiss boot screen.
I've tried Easyflasher aswell with no results, Please, any hope for this thing, Thanks in advance!
Click to expand...
Click to collapse
ChrisG12 said:
Sounds like your problem is a bit different - can you get into your bootloader? After voldown+power you should see some small text in the upper left of the screen then immediately hit vol up.... From there you should be able to reflash any ROM...
Click to expand...
Click to collapse
Thanks for your reply, when I do use that button combo, it goes into the ClockworkMod Recovery v5.8.3.4, the native one seems to be gone.
Is that a bad thing? Once in ClockworkMod - you can install a new ROM (such as KatKiss or even go back to stock). Just find the right zip file on the web, copy to your sdcard and then in clockwork select that zip file to install.... Or am I missing something?
ldwhyte said:
Thanks for your reply, when I do use that button combo, it goes into the ClockworkMod Recovery v5.8.3.4, the native one seems to be gone.
Click to expand...
Click to collapse
Ok - back to my problem - I installed a new recovery and get the same error. The two recoveries I have tried are TWRP (2.3 and 2.7.0.1) and cwm-6.0.2.1-notouch-hybrid. Both seem to work fine (and I had no trouble previously with my device running TWRP and Katkiss 4.3).
After a crash I needed to reinstall a ROM. I've copied four ROMs to my sdcard (Katkiss 4.3, Katkiss 4.4.2, Omni 4.4.2, and stock asus). I've tried all 4 ROMs with both recoveries. I get the same error when I try to install the zips. Usually it is "set_perm: some changes failed". Though stock asus zip fails with a different message "Assert failed: package_extract_file(“blob”, “/tmp/blob”)".
Any ideas on what is keeping a recovery from installing the zip? Note they can install other zips fine (i.e. other recoveries, superuser, gapps, etc.). But not the ROM.
ChrisG12 said:
Is that a bad thing? Once in ClockworkMod - you can install a new ROM (such as KatKiss or even go back to stock). Just find the right zip file on the web, copy to your sdcard and then in clockwork select that zip file to install.... Or am I missing something?
Click to expand...
Click to collapse
No it's not, but I can't get anything onto the SD card, only the ext card and I CWM will not mount it to flash from. if I'm missing something and I sure I am, Im greatful for any help, and thanks again..
Samsung Galaxy Tab 2
GT-P5110
Android version: 4.2.2.
Hi there, I have a rooted device running on CyanogenMod 10.1.3-p5110, with a custom recovery CWM 6.0.2.7
After 3 years (or so) of smooth operation it started to slow down and getting unstable from time to time, so I decided to factory reset.
I did the factory reset from CWM following the regular regular instructions, however after reset completion the devices booted back to the original CM10, with all the original data (nothing was cleaned at all or reset). I tried several times from - cleaning cache, date, system, dalvik cache, factory reset ... still the same result.
I also tried to replace the CWM with TWRP (GT-P5110_TWRP_3.0.0-0.tar.md5) - same result, it shows success but if I restart to recovery, it goes to CWM 6.0.2.7
If I boot into recovery (CWM) and flash any rom, it shows success and then reboots (guess what) into the original CM 10 like nothing happened.
I tried to flash the stock firmware using Odin. I got an original firmware "P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5" from a reliable source (sammobile)
Model:GT-P5110, Model name:GT-P5110, Country:Czech Republic, Version:Android 4.2.2, Changelist:1709803, Build date:Wed, 18 Sep 2013 06:13:11 +0000, Security Patch Level: N/A, Product code:XEZ, PDA: P5110XXDMI1, CSC5110OXXDMJ1
Every time I flash the original stock rom with Odin, the ID:COM box in Odin goes green and everything looks just fine but after reboot the tablet restarts to the original CM10. I was using Odin3-v1.85, as well as newer versions of the tool - namely Odin3_v3.07, Odin3_v3.11.1, all with the same result.
I even tried form very scratch - repartitioning the device using a .pit file "signed_espresso_20120220_16G.pit", flashing stock using Odin, same result.
I also tried flashing rom Heimdall Suite - same result
I have no problem to connect to the device using ADB shell and communicate with the device ...
However, I am not any Android guru, so I cannot "decode" what I get.
To me it seems like I somehow messed up my partitions or mounts and thats the reason for the strange behaviour.
So now I am stuck in strange state, which I cannot call a bootloop ... seems like I am running some sort of cached system or someting and I am unable to get out of with any standard tool available. As I said ... device is rooted, running CWM and I can boot to any mode I want ... download, recovery, system.
Any help will be more than appreciated.
You could have an faulty emmc firmware or your emmc reached end of life.
You are from europe? I know someone who can fix it for you.
You can also read the faq on my github userpage for more information about your bug.
kozyn said:
Samsung Galaxy Tab 2
GT-P5110
Android version: 4.2.2.
Hi there, I have a rooted device running on CyanogenMod 10.1.3-p5110, with a custom recovery CWM 6.0.2.7
After 3 years (or so) of smooth operation it started to slow down and getting unstable from time to time, so I decided to factory reset.
I did the factory reset from CWM following the regular regular instructions, however after reset completion the devices booted back to the original CM10, with all the original data (nothing was cleaned at all or reset). I tried several times from - cleaning cache, date, system, dalvik cache, factory reset ... still the same result.
I also tried to replace the CWM with TWRP (GT-P5110_TWRP_3.0.0-0.tar.md5) - same result, it shows success but if I restart to recovery, it goes to CWM 6.0.2.7
If I boot into recovery (CWM) and flash any rom, it shows success and then reboots (guess what) into the original CM 10 like nothing happened.
I tried to flash the stock firmware using Odin. I got an original firmware "P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5" from a reliable source (sammobile)
Model:GT-P5110, Model name:GT-P5110, Country:Czech Republic, Version:Android 4.2.2, Changelist:1709803, Build date:Wed, 18 Sep 2013 06:13:11 +0000, Security Patch Level: N/A, Product code:XEZ, PDA: P5110XXDMI1, CSC5110OXXDMJ1
Every time I flash the original stock rom with Odin, the ID:COM box in Odin goes green and everything looks just fine but after reboot the tablet restarts to the original CM10. I was using Odin3-v1.85, as well as newer versions of the tool - namely Odin3_v3.07, Odin3_v3.11.1, all with the same result.
I even tried form very scratch - repartitioning the device using a .pit file "signed_espresso_20120220_16G.pit", flashing stock using Odin, same result.
I also tried flashing rom Heimdall Suite - same result
I have no problem to connect to the device using ADB shell and communicate with the device ...
However, I am not any Android guru, so I cannot "decode" what I get.
To me it seems like I somehow messed up my partitions or mounts and thats the reason for the strange behaviour.
So now I am stuck in strange state, which I cannot call a bootloop ... seems like I am running some sort of cached system or someting and I am unable to get out of with any standard tool available. As I said ... device is rooted, running CWM and I can boot to any mode I want ... download, recovery, system.
Any help will be more than appreciated.
Click to expand...
Click to collapse
Once I had same problem with Motorola xoom and guess what was realy the problem. It was the external SD memory remove it then flash the stock rom.. If problem persists see with Andi
Thank you for your response. To me it also seems like faulty emmc. I have check the frequently asked questions on your blog and the description there exactly matches with what I'm experiencing on my device. Yes I am from Europe, Czech Republic. I have already tried to get in touch with two people who have the proper tooling to flash the firmware (JTAG). Hope I get some response fast and the solution is going to work. Still if you have someone in the CZ that you can recommend I'm grateful for any advice.
@zidane: All of the above steps where performed without external SD card.
kozyn said:
@zidane: All of the above steps where performed without external SD card.
Click to expand...
Click to collapse
Don't lose hope Try latest recovery 3.0.2.5 and the cm13 22/9 by Andi (made specially for certain cases like yours the files are in his folder the link in his signature ) if nothing happens then I guess dev Andi will be glad to help you fix your Emmc. contact him to provide you with the contacts..
Good luck
zidane01 said:
Don't lose hope Try latest recovery 3.0.2.5 and the cm13 22/9 by Andi (made specially for certain cases like yours the files are in his folder the link in his signature ) if nothing happens then I guess dev Andi will be glad to help you fix your Emmc. contact him to provide you with the contacts..
Good luck
Click to expand...
Click to collapse
@zidane01: thanx for cheerin' up
I have tried to replace my CWM 6.0.2.7 with TWRP 3.0.2.5, 3.0.2.6. from a .zip file using current recovery. Result is the same as described - after I reboot to recovery (using advanced option in CWM) it boots back to the original CWM 6.0.2.7. Flashing latest CM13 (as of 27/9/2016, downloaded from Andi's site) from CWM 6.0.2.7 ends with error. The tablet seems like READ ONLY not matter what I do. Maybe I am doing something wrong. I can describe the procedure step by step in detail, if you wish.
kozyn said:
@zidane01: thanx for cheerin' up
I have tried to replace my CWM 6.0.2.7 with TWRP 3.0.2.5, 3.0.2.6. from a .zip file using current recovery. Result is the same as described - after I reboot to recovery (using advanced option in CWM) it boots back to the original CWM 6.0.2.7. Flashing latest CM13 (as of 27/9/2016, downloaded from Andi's site) from CWM 6.0.2.7 ends with error. The tablet seems like READ ONLY not matter what I do. Maybe I am doing something wrong. I can describe the procedure step by step in detail, if you wish.
Click to expand...
Click to collapse
sounds like that you have a faulty emmc. same what android-andi said.
@kozyn Hi buddy.. have the same thing on a p5110 -- emmc is in read only mode and I can't seem to PM Andi for some contacts.
Can you help me recover this galaxy tab2 pls? Appreciate your time