I have an Asus Padfone 2 A68 JP version upgraded to Kitkat 4.4.2 via asus.com :highfive:
I am unhappy with the upgrade :crying: to my personal experience, the ZenUI interface is not very appealing
1st, it is not user friendly looking for apps, customizing desktop apps and widgets are not that special :fingers-crossed:
2nd, battery drains a lot faster that it used to be
3rd, wifi is problematic, can't make my phone connect to Google Play Store when phone is connected to my laptop, it says no internet when in fact it is :crying:
Can anyone please advise how can a Padfone 2 upgraded to Kitkat be downgraded? I tried the normal way, copying the JP_PadFone2-user-10_4_17_7-UpdateLauncher.zip file on to sd folder Asus\Update, phone notification appears saying there is an update available, but installation fails, obviously because of newer system and read-only files existing.
My Padfone 2 Kitkat is towel-rooted. I only use stock recovery, no CWM or TWRP, not yet. I will try to be cautious this time :angel: I just got back my A66 Padfone 1 from Taiwan for service repair, because it was bricked while I was installing CWM/TWRP.
Any expert advise is highly appreciated. Thanks
you still having a issue ?
try that method
Download original firmware asus webiste. (android 4.1)
unzip it once .
file called 10.............ota.user.zip (at least with ppadfone infinity)
put it on your sd card
if you done disconnect from computer
then it should be a triangle in notification bar upgrade found or something like that if not restart phone and then it should be there.
press ok and wait phone to upgrade/dowgrade.
I hope it wortks.
I have a WW ROM but basically facing the same problem. Still looking for help...
I've spent 2 days researching and trying stuff out until today. I have finally downgraded my Padfone 2 from Android 4.4.2 (KOT49H.WW_PadFone-11.8.4.12-20140804 te) to Android 4.1.1 (GuerillaROM-v1.6_OFFICIAL912014).
GuerillaROM looks just like PF2's stock 4.1.1 and it's awesome for me because 4.4.2 was... aesthetically unappealing.
Anyhow, this is my story, don't know if it will work for you, but it worked for me.
- in step 2 I accidentally erased my files, so... back your files up on a PC.
Don't hold me responsible for anything that happens to your phone, do stuff on your own risk. Guys who do this stuff (not me) have made these procedures as simple as they could, so that the end users (we) could **** our phones up as little as possible. These procedures have minimal risk, but the risk is still there.
1. UnLock (unlock Bootloader)
- got from Asus.com (http://support.asus.com/Download.aspx?SLanguage=en&m=PadFone+2&p=29&s=1)
(OS: Android --> Utilities --> "Unlock Device App: Unlock boot loader")
- worked now. Didn't work a year ago, don't know why
2. Followed directions from theunlockr.com (http://theunlockr.com/2013/06/09/how-to-root-the-asus-padfone-2/)
- has done me a factory reset (all data wiped) on 4.4.2 + installed SU
- Root Checker: Failed
- Root Checker is an app from Play Store
- stopped at step III 8 because Root Checker didn't verify
- don't know if matters, but I installed
drivers for bootloader from Asus.com (http://support.asus.com/Download.aspx?SLanguage=en&m=PadFone+2&p=29&s=1)
OS: Other --> USB
2a. I also downloaded adb (http://forum.xda-developers.com/showthread.php?t=2588979)
but turns out I didn't need it.
3. went to hexamob.com, found "Android Rooting Method: Towelroot"
- http://hexamob.com/how-to-root/android-rooting-method-towelroot/
- followed that
4. Made it ra1n b^.^d
5. Root Checker: Pass
6. Installed TWRP Manager
- from Play Store
7. Installed TWRP recovery 2.6.3.0
- the later ones didn't work
- the earlier ones messed with SU
- try for yourself
8. Got SuperSU (#) from Play Store
9. Updated it for TWRP/CWM
- (reboot - running open recovery script)
10. Installed GuerillaMOD
- followed from xda
- http://forum.xda-developers.com/showthread.php?t=2268613
11. White ASUS logo freeze (like xda said it could)
12. After 2 or 3 forced reboots
magically unfroze after awhile (~2mins)
- don't ask me how or why
- don't count on it magically unfreezing (there's a solution for that freeze on that thread (in the FAQ))
-------------------------------------------------------------------------------------
wannab.phd said:
I've spent 2 days researching and trying stuff out until today. I have finally downgraded my Padfone 2 from Android 4.4.2 (KOT49H.WW_PadFone-11.8.4.12-20140804 te) to Android 4.1.1 (GuerillaROM-v1.6_OFFICIAL912014).
GuerillaROM looks just like PF2's stock 4.1.1 and it's awesome for me because 4.4.2 was... aesthetically unappealing.
Anyhow, this is my story, don't know if it will work for you, but it worked for me.
- in step 2 I accidentally erased my files, so... back your files up on a PC.
Don't hold me responsible for anything that happens to your phone, do stuff on your own risk. Guys who do this stuff (not me) have made these procedures as simple as they could, so that the end users (we) could **** our phones up as little as possible. These procedures have minimal risk, but the risk is still there.
1. UnLock (unlock Bootloader)
- got from Asus.com (http://support.asus.com/Download.aspx?SLanguage=en&m=PadFone+2&p=29&s=1)
(OS: Android --> Utilities --> "Unlock Device App: Unlock boot loader")
- worked now. Didn't work a year ago, don't know why
2. Followed directions from theunlockr.com (http://theunlockr.com/2013/06/09/how-to-root-the-asus-padfone-2/)
- has done me a factory reset (all data wiped) on 4.4.2 + installed SU
- Root Checker: Failed
- Root Checker is an app from Play Store
- stopped at step III 8 because Root Checker didn't verify
- don't know if matters, but I installed
drivers for bootloader from Asus.com (http://support.asus.com/Download.aspx?SLanguage=en&m=PadFone+2&p=29&s=1)
OS: Other --> USB
2a. I also downloaded adb (http://forum.xda-developers.com/showthread.php?t=2588979)
but turns out I didn't need it.
3. went to hexamob.com, found "Android Rooting Method: Towelroot"
- http://hexamob.com/how-to-root/android-rooting-method-towelroot/
- followed that
4. Made it ra1n b^.^d
5. Root Checker: Pass
6. Installed TWRP Manager
- from Play Store
7. Installed TWRP recovery 2.6.3.0
- the later ones didn't work
- the earlier ones messed with SU
- try for yourself
8. Got SuperSU (#) from Play Store
9. Updated it for TWRP/CWM
- (reboot - running open recovery script)
10. Installed GuerillaMOD
- followed from xda
- http://forum.xda-developers.com/showthread.php?t=2268613
11. White ASUS logo freeze (like xda said it could)
12. After 2 or 3 forced reboots
magically unfroze after awhile (~2mins)
- don't ask me how or why
- don't count on it magically unfreezing (there's a solution for that freeze on that thread (in the FAQ))
-------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Thanks. mate, very nice work. I will try your guide as soon as I have the chance, although not too soon because at present my phone is linked to many of my online bank requisites.
Your share is well appreciated.
explorer2612 said:
Thanks. mate, very nice work. I will try your guide as soon as I have the chance, although not too soon because at present my phone is linked to many of my online bank requisites.
Your share is well appreciated.
Click to expand...
Click to collapse
hello can you please put a link to download : JP_PadFone2-user-10_4_17_7 (stock rom the official one ) and thanks
wasim74 said:
hello can you please put a link to download : JP_PadFone2-user-10_4_17_7 (stock rom the official one ) and thanks
Click to expand...
Click to collapse
asus.com/Tablets_Mobile/PadFone_2_A68/HelpDesk_Download/
Under OS select Android and then under Firmware find what you need.
Need your help please
wannab.phd said:
asus.com/Tablets_Mobile/PadFone_2_A68/HelpDesk_Download/
Under OS select Android and then under Firmware find what you need.
Click to expand...
Click to collapse
I HAVE ASUS PADFONE 2 suddenly WHEN I WAS SEARCHING ON GOOGLE ITS SHOW ME ( unfortunately google app has stopped ) AND STOCK THERE SO I DID RESET AFTER THAT THE PHONE ITS STOCK ON BOOTING UP ASUS LOGO AND AFTER 15 MINT ITS PASS THE BOOT LOGO AND ITS SHOW ME ON THE TOP ( ENCRYPTION UNSUCCESSFUL ) AND ON THE BOTTOM ( RESET PHONE ) BUT WHEN I HIT ON RESET PHONE IT DOES NOT DOING ANYTHING THE PHONE ITS ( UNROOTED ) AND IT WAS RUNNING ANDROID JELLY JEAN ( 4.1) AND I CAN GET INTO STOCK RECOVERY AND I DID WIPE DATA/ FACTORY RESET AND WIPE CACHE PARTITION BUT STILL STOCK ON BOOT LOGO AND NOT BOOTING NORMALLY AFTER I USED ( ADB BOOT LOADER ) AND TRIED TO FLASH A NEW FIRMWARE BY USING ( CWM RECOVERY6.0.2.9 ) I DIDNT FLASH THE CWM RECOVERY JUST USED THE IMG RECOVERY TO FLASH THE FIRMWARE ( INSTALL ZIP FROM SIDELOAD ) AND I SENT THE FIRMWARE TO MY PHONE BUT THE CWM RECOVERY COULDN'T FLASH IT ( UNSUCCESSFUL ) BECAUSE CWM RECOVERY ITS GAVE ME EVERY TIME ( E: CANT MOUNT ) ANYTHING I DID WITH CWM RECOVERY IT DOES NOT WORK SO I NEED YOUR HELP GUYS PLEASE ANYBODY CAN HELP ME WITH THAT I WILL BE APPRECIATED AND THANK YOU PLEASE HELP NOTE : I DONT KNOW WHAT IS THE BUILD NUMBER ON MY PHONE BUT I BOUGHT IT FROM TAIWAN .... HEY GUYS CHECK THE PICS PLEASE WHICH I POSTED AND THANKS
EDIT : I WAS USED CWM:6.0.2.9 I TRIED OVER 20 TIMES WITHOUT ANY SUCCEED (UNSUCCESSFUL) AS SHOWN IN THE PICTURES WHICH I POSTED ALREADY I TRIED ALL THESE ROMS : TW_A68-11.8.4.12-0-ota-user.zip ,TW_A68-11.8.4.6-0-ota-user.zip,WW_A68-11.8.4.23-0-ota-user.zip,CHT_A68-11.8.3.3-0-ota-user.zip,CN_A68-10.4.17.7-0-ota-user.zip,HK_A68-10.4.17.7-0-ota-user.zip,TW_A68-11.8.4.23-0-ota-user.zip ,,, I TRIED ALL THESE ROMS BECAUSE I DONT KNOW WHAT IT WAS MY ( BUILD NUMBER ) I CANT REMEMBER I JUST KNOW IT WAS JELLY BEAN 4.1 AND MY PADFONE 2 MODEL A68 IT WAS NOT ROOTED IT HAS STUCK FIRMWARE AND HAS ( LOCKED BOOTLOADER ) AND I TRIED TOO : adb push firmware.zip /data/media for example :adb push TW_A68-11.8.4.23-0-ota-user.zip /data/media and i pushed already to my external storage because there is no memory card on this phone (sdcard) using the stock recovery and when i tried to install the update from the /data/media it shows : install update and after 15 mint it gave me installation aborted and i wanna tell you something else the CWM RECOVERY WHEN I USED IT I DIDNT FLASH IT I JUST BOOT LIKE TESTED :fastboot boot recover.img because i dont know if i can flash it or not because my phone its ( not rooted ) ,,, I TRIED ALL THE TW : ROMS WHICH I SENT IT TO YOU ALREADY ABOVE AND I DOWNLOAD THESE ROMS FROM ASUS WEBSITE FIRMWARES ,, AND I SENT THE ROMS USING THE SIDELOAD TO MY PHONE AND IM NOT FLASHING THE CWM ON MY PHONE BECUSE MY PHONE ITS NOT ROOTED AND THE BOOTLOADER ITS LOCKED I JUST LET CWM TO BOOT ON MY PHONE NOT FLASH IT AND WHEN I TRIED TO INSTALL THE UPDATE USING CWM ITS GAVE ME ( INSTALLATION ABORTED ) STATUS 7 ERROR ,,,, i tried fastboot and sideload i have no problem with that i can send the roms to my phone but the problem my phone cant flash it ,,,, just to let you know when i used the cwm 6.0.2.9 i cant do wipe -factory reset or wipe cashe its gave me e: cnt mount but on stock recovery i can do wipe cashe and factory reset but it take too long to do that ,,,,,,, i have problem with flashing the recovery { fastboot flash recovery recovery.img } i dont know why and i tried to just boot the recovery img for test : fastboot boot boot recovery.img i tried it with twrp and its show me just the picture TEAM WIN BUT ITS NOT FUNCTIONAL ,,, HELP PLEASE:crying
My problem provided with pictures REALLY NEED ANY HELP
wasim74 said:
i have asus padfone 2 suddenly when i was searching on google its show me ( unfortunately google app has stopped ) and stock there so i did reset after that the phone its stock on booting up asus logo and after 15 mint its pass the boot logo and its show me on the top ( encryption unsuccessful ) and on the bottom ( reset phone ) but when i hit on reset phone it does not doing anything the phone its ( unrooted ) and it was running android jelly jean ( 4.1) and i can get into stock recovery and i did wipe data/ factory reset and wipe cache partition but still stock on boot logo and not booting normally after i used ( adb boot loader ) and tried to flash a new firmware by using ( cwm recovery6.0.2.9 ) i didnt flash the cwm recovery just used the img recovery to flash the firmware ( install zip from sideload ) and i sent the firmware to my phone but the cwm recovery couldn't flash it ( unsuccessful ) because cwm recovery its gave me every time ( e: Cant mount ) anything i did with cwm recovery it does not work so i need your help guys please anybody can help me with that i will be appreciated and thank you please help note : I dont know what is the build number on my phone but i bought it from taiwan .... Hey guys check the pics please which i posted and thanks
edit : I was used cwm:6.0.2.9 i tried over 20 times without any succeed (unsuccessful) as shown in the pictures which i posted already i tried all these roms : Tw_a68-11.8.4.12-0-ota-user.zip ,tw_a68-11.8.4.6-0-ota-user.zip,ww_a68-11.8.4.23-0-ota-user.zip,cht_a68-11.8.3.3-0-ota-user.zip,cn_a68-10.4.17.7-0-ota-user.zip,hk_a68-10.4.17.7-0-ota-user.zip,tw_a68-11.8.4.23-0-ota-user.zip ,,, i tried all these roms because i dont know what it was my ( build number ) i cant remember i just know it was jelly bean 4.1 and my padfone 2 model a68 it was not rooted it has stuck firmware and has ( locked bootloader ) and i tried too : Adb push firmware.zip /data/media for example :adb push tw_a68-11.8.4.23-0-ota-user.zip /data/media and i pushed already to my external storage because there is no memory card on this phone (sdcard) using the stock recovery and when i tried to install the update from the /data/media it shows : Install update and after 15 mint it gave me installation aborted and i wanna tell you something else the cwm recovery when i used it i didnt flash it i just boot like tested :fastboot boot recover.img because i dont know if i can flash it or not because my phone its ( not rooted ) ,,, i tried all the tw : Roms which i sent it to you already above and i download these roms from asus website firmwares ,, and i sent the roms using the sideload to my phone and im not flashing the cwm on my phone becuse my phone its not rooted and the bootloader its locked i just let cwm to boot on my phone not flash it and when i tried to install the update using cwm its gave me ( installation aborted ) status 7 error ,,,, i tried fastboot and sideload i have no problem with that i can send the roms to my phone but the problem my phone cant flash it ,,,, just to let you know when i used the cwm 6.0.2.9 i cant do wipe -factory reset or wipe cashe its gave me e: Cnt mount but on stock recovery i can do wipe cashe and factory reset but it take too long to do that ,,,,,,, i have problem with flashing the recovery { fastboot flash recovery recovery.img } i dont know why and i tried to just boot the recovery img for test : Fastboot boot boot recovery.img i tried it with twrp and its show me just the picture team win but its not functional ,,, help please:crying
Click to expand...
Click to collapse
i wish you can help me with what i have to do i tried too many things without any succeed
HELP
wasim74 said:
i wish you can help me with what i have to do i tried too many things without any succeed
Click to expand...
Click to collapse
another picture shown my bootloader information
Hi all, I need downgrade my Asus a68 from 4.4. to 4.1. Please someone help me 4.1 firmwares. Thanks
Mickey Mouse said:
Hi all, I need downgrade my Asus a68 from 4.4. to 4.1. Please someone help me 4.1 firmwares. Thanks
Click to expand...
Click to collapse
Follow this post.
Hi! Sorry for my English, Russian I am writing to you through Google translator)))
problem as follows:
It was a piercing VVE 442? after about half a year longer to work on their own touch-sensitive keys below the screen (back, home, and applications).
to reset to the factory did not help, did hard reset did not help,
He rolled to vve411. everything worked, I decided to put back the WWE 442, okay flashed, but the buttons again have earned, had to revert to 411. 442 would be desirable but for some reason he is not working or rather not work touch-sensitive buttons, and tried to put other regions but to no avail. help vchem washes be the problem?
Related
Hi Android experts!
I need some assistance fixing a problem I caused & am now stuck in a recovery boot loop.
- bought a Thomson QM734-8G tablet (Allwinner A13b clone), running Jellybean 4.2.2;
- PC interface worked fine in MTP and large storage modes;
- setup Android SDK & Java JDK on PC and communicate with tablet via ADB;
All OK so far
After a couple of days, I decided to replace stock recovery with ClockworkMod Recovery, so I could start messing about with the tablet.
I found the CWM 6.0.2.8 mod supposed to work with these tablets and, following instructions, determined it was indeed running on sun5i hardware and had 10 partitions (nandj) and downloaded the appropriate version.
I used ADB sideload to install CWM and everything appeared to work OK ... until I rebooted and found myself stuck in a never-ending cycle of CWM-based recovery bootloop
All I get is the CWM recovery console, with a few lines of error & the tablet will go no further.
E:can't mount /cache/recovery/command
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
Also, pretty much none of the CWM functions work properly and nothing will mount through the 'Mounts and Storage' section, although sideload mode still seems to work.
Attempts to use ADB sideload to install a different CWM or other recovery image have all failed, and LiveSuit and PhoenixSuit both have issues detecting the tablet (despite trying various versions of each & following instructions precisely), so I can't flash a replacement ROM to fix things.
At the moment, I just want to rip CWM out and go back to factory recovery mode and have a working tablet again!
Any suggestions on how to resolve this problem would be greatly appreciated
P.S. I think the Bootloader is locked and the tablet is unrooted. Superuser or SuperSU don't want to install properly. However, using ADB, it looks like I can get root access in shell (#).
Oh No!
I have the same problem! I was trying to sort the tablet out for a friends kid as it was acting up, tried to root using the Allwinner A13 generic android tablet 4.0.4 root method
but now I am stuck in a bootloop like you..
I have seen one other post about this from Jan 2013 and nobody has replied to it...I am imagining probably not many people have this tablet and basically, there is no solution...:crying:
I have a Samsung Galaxy S i9000 and it was simple to reinstall everything through CWM..On a Samsung Galaxy Young recently, it wasn't as easy as that but I made it through..but there doesn't seem to be download mode neither kernels for this device (since I guess it's not popular)..I hope we haven't ended up with a brick!! :crying::crying::crying:
Success! I have managed to sort it out y using LiveSuit 1.09 and Manta ROM 4.2.2
I think the problem either was that I was pressing + instead of - to enter adb recovery mode, thou I think it didn't make a difference perhaps...but I think the real problem was not finding the right ROM and Live Suit combo. Sometimes I would get a 0x162 error which is meant to mean an incompatible ROM (thou it did this on ROM that was advertised as stock!)
I think this Manta ROM works for a lot of people however, you may have problems with the touchscreen drivers for which you can have a look at [MOD] FaaastJB v2.5 A13 Allwinner with Jelly Bean 4.2.2 by Toxicro for trying the various touchscreen drivers. It worked for with no probs so I don't need to mess around with them but they are easy enought to install. Just click the run.bat file (usually) and it should do everything for u.
Good Luck!
bootloop allways STuck in cwm mode after inSTALL CWM RECOVERY
was trying to install CWM RECOVERY on my A13 tablet n now i think its BRICKED!!!
every time i turn it on it goes back to the stupid recovery mode n hangs there.can't use volume keys to navigate so i can format it coz its just stuck!
LIVESUIT pack freezes is soon as i plug in the tablet!!!!! HAIMDALL & ODIN can't find the device!!!
am out of options.....if someone knows the solution to this problem then PLEASE HELP ME.
thanx in advance
rusman_id said:
was trying to install CWM RECOVERY on my A13 tablet n now i think its BRICKED!!!
every time i turn it on it goes back to the stupid recovery mode n hangs there.can't use volume keys to navigate so i can format it coz its just stuck!
LIVESUIT pack freezes is soon as i plug in the tablet!!!!! HAIMDALL & ODIN can't find the device!!!
am out of options.....if someone knows the solution to this problem then PLEASE HELP ME.
thanx in advance
Click to expand...
Click to collapse
i have the same problem too with my A13 device when i tried to upgrade the CMW, i installed wrong CMW, i forgot to look for the partition. and now i can't boot in bootloader using ADB, i also can't use fastboot... i try to flash with livesuit but only 3% in flashing and not continued. i hope somebody help to this problem.. thanks in advance..
generic a13 tablet jb 4.2.2 cwm boot loop
i have a zeepad 7.0 (generic a13 allwinner) I have managed to root it. when trying to install cwm 6.0.2.8 I get cwm boot loop. I followed instructions to the T. used correct version for my device. but still seem to get boot loop with can't load cache errors. is there any way to fix this issue. or another way I can install custom rom without cwm? it is already running jb 4.2.2 just looking for a rom with improvements.
gonzo2fast69 said:
i have a zeepad 7.0 (generic a13 allwinner) I have managed to root it. when trying to install cwm 6.0.2.8 I get cwm boot loop. I followed instructions to the T. used correct version for my device. but still seem to get boot loop with can't load cache errors. is there any way to fix this issue. or another way I can install custom rom without cwm? it is already running jb 4.2.2 just looking for a rom with improvements.
Click to expand...
Click to collapse
What you are describing is basically the same flawed procedure I found myself in initially.
DO NOT INSTALL ANY NEW CWM FROM A CWM FLASH LIKE IN OTHER ANDROID DEVICES!!!
99% of the time it does not work and deletes your partition information and messes up your tablet. The ONLY way to rescue it is to find the ORIGINAL ROM for your tablet (or one that is compatible). This will take LOTS of trial and error if you can't find the exact one and have to try to install other A13 tablet ROMS through LiveSuit
LIVESUIT IS THE ONLY WAY TO UPDATE ROMS ON A10/A13 DEVICES NOT THROUGH CWM LIKE OTHER ANDROID PHONES!
HERE is the firmware and instructions for flashing your Zeepad 7.0 back to the stock ROM.
The hardest part is to get it into the FLASH MODE - which when activated, NOTHING will come up on the screen but it will be recognised by LiveSuit.
To get into FLASH MODE:
FIRST - load the ROM into LIVESUIT and get to the bit where it asks about connecting into FLASH MODE
Turn the tablet off/press the reset button on the back with a pointed object
Immediately HOLD the VOLUME + (If any boot screen shows up then you have to start again)
Whilst holding the VOLUME +, plug in the USB cable and then HOLD the POWER KEY
Now let go of the POWER KEY for a second then PRESS IT QUICKLY 10 TIMES
Livesuit should now disappear on the PC and a dialog box will come up about doing a full or normal format (For CWM corruption it is best to do a FULL)
Livesuit will disappear to the taskbar so click it and see if it is flashing. If there is an 0x164 (i think but not sure that is the exact one) error then that means that the ROM WAS INCORRECT (even though you may say you have gotten it from the manufacturers website and it is meant to be the correct one - You have to basically find another that works)
IF THE VERSION OF LIVESUIT DOESN'T RESULT IN A SUCCESSFUL FLASH THEN TRY ANOTHER! THERE ARE ABOUT 3 VERSIONS AND PROBABLY MORE - v1.07, v1.09, v1.11. SOME VERSIONS HAVE SOME ISSUES BUT MAY BE MORE SUITABLE FOR YOUR TABLET. THE MOST STABLE SEEMS TO BE V1.09 BUT TRY THEM ALL TO SEE WHICH ONE WORKS OR NOT.
I hope that helps and if you are really stuck then I recommend you join TechKnow forums as they are way more helpful and specialised than XDA for A13 tablets.
thanks for the advice. I can install stock firmware no problem just looking for something better.
Ah..well then forget CyanogenMod as it not officially supported for this tablet and thus things won't be working 100%. The 2 main ROMs that most people are using for A13 are CookedROM & FaaastJB.
I can recommend both, perhaps FaaastJB has more features but CookedROM is better supported as the creator is one of the mods on TechKnow and gets back to u about ur problems within a day or two with detailed advice. The only issue with these is that the touchscreen drivers don't work out of the vox and u need to patch ones specific to ur tablet to make it work. Sometimes the TS does work but it may be offset or inverted so u have to play around with editing config files out of specific patches with tools provided. In my experience, I had 2 apparent exact ta let's but only 1 would work with any TS patch. The other never worked no matter what I tried, from creating my own patches to extracting drivers from the stock ROM & editing manually - a big learnjng curve and if u have no technical knowledge if how computer languages work then everything will look like gobbledygook and be very time consuming. I preferred the look of Faaast JB but of wouldn't install right so I had to stick with cookedrom in 1 tablet and a stock ROM that I nodded slightly for the other as it wouldn take anything else. These tablets can be really troublesome!
I recommended u install Uberizer as its a huge toolbox of useful stuff for ur A13 and it is recommended to backup ur working stock ROM using it before trying any modifications. U should also get a printout/screen grab of the working ROMs drivers in order to know what TS patches u need for the custom ROMs.there is a world of information on TechKnow forums about this..I can't really help more than this since I do not own an A13 tablet anymore.
D0MINO said:
Ah..well then forget CyanogenMod as it not officially supported for this tablet and thus things won't be working 100%. The 2 main ROMs that most people are using for A13 are CookedROM & FaaastJB.
I can recommend both, perhaps FaaastJB has more features but CookedROM is better supported as the creator is one of the mods on TechKnow and gets back to u about ur problems within a day or two with detailed advice. The only issue with these is that the touchscreen drivers don't work out of the vox and u need to patch ones specific to ur tablet to make it work. Sometimes the TS does work but it may be offset or inverted so u have to play around with editing config files out of specific patches with tools provided. In my experience, I had 2 apparent exact ta let's but only 1 would work with any TS patch. The other never worked no matter what I tried, from creating my own patches to extracting drivers from the stock ROM & editing manually - a big learnjng curve and if u have no technical knowledge if how computer languages work then everything will look like gobbledygook and be very time consuming. I preferred the look of Faaast JB but of wouldn't install right so I had to stick with cookedrom in 1 tablet and a stock ROM that I nodded slightly for the other as it wouldn take anything else. These tablets can be really troublesome!
I recommended u install Uberizer as its a huge toolbox of useful stuff for ur A13 and it is recommended to backup ur working stock ROM using it before trying any modifications. U should also get a printout/screen grab of the working ROMs drivers in order to know what TS patches u need for the custom ROMs.there is a world of information on TechKnow forums about this..I can't really help more than this since I do not own an A13 tablet anymore.
Click to expand...
Click to collapse
I have the stock rom and can flash it back no problem. I have tried all versions of faaastjb but could not get it to install through livesuit. keep getting error message upgrade fails 0x162. I don't know what that means. I will try cooked rom and see if any luck. as far messing with rom drivers I have no clue in that department. guess its time to learn if I want to keep messing with these tablets lol.
gonzo2fast69 said:
I have the stock rom and can flash it back no problem. I have tried all versions of faaastjb but could not get it to install through livesuit. keep getting error message upgrade fails 0x162. I don't know what that means. I will try cooked rom and see if any luck. as far messing with rom drivers I have no clue in that department. guess its time to learn if I want to keep messing with these tablets lol.
Click to expand...
Click to collapse
0x162 means that the ROM is not compatible with your tablet and will never flash. It may flash using other versions of Livesuit or even with the 'only try in a last case scenario' Phoenixcard software..but I have (fortunately) never had to use that. Despite the A13 tablets being 'unbrickable', I read that Phoenixcard CAN brick ur phone although I came across people who had tried it after Livesuit fails and had no problems.
If FaaastJB doesn't work then I highly recommend CookedROM. If that doesn't work then I have no idea what to suggest except Phoenixcard - if you are prepared to accept the risk that it may get bricked. You could also try a search on TechKnow for your particular tablet, post under the FaaastJB/CookedROM posts or create a new thread in the forums (but I think you will get a similar response to this).
D0MINO said:
0x162 means that the ROM is not compatible with your tablet and will never flash. It may flash using other versions of Livesuit or even with the 'only try in a last case scenario' Phoenixcard software..but I have (fortunately) never had to use that. Despite the A13 tablets being 'unbrickable', I read that Phoenixcard CAN brick ur phone although I came across people who had tried it after Livesuit fails and had no problems.
If FaaastJB doesn't work then I highly recommend CookedROM. If that doesn't work then I have no idea what to suggest except Phoenixcard - if you are prepared to accept the risk that it may get bricked. You could also try a search on TechKnow for your particular tablet, post under the FaaastJB/CookedROM posts or create a new thread in the forums (but I think you will get a similar response to this).
Click to expand...
Click to collapse
i have tried every program and only img file that will work is the stock img. guess that's all that's meant to be for it. oh well that's what I get for getting cheap tablets get what you pay for.
i had same problem with my ampe a85 (alwinner a13) .i used livesuit..it was sucess...it will not work if u have used any softwre for rooting like kingo one click root.so try on another system,it will not work on windows 8 too.
gonzo2fast69 said:
i have tried every program and only img file that will work is the stock img. guess that's all that's meant to be for it. oh well that's what I get for getting cheap tablets get what you pay for.
Click to expand...
Click to collapse
Yes unfortunately these tablets are designed with many different configurations by different companies so finding a ROM that matches can prove hit and miss. You may even have 2 of the same tablet bought at the same time from the same company and only one of them works with a ROM or particular touchscreen driver and the other doesn't. I had this problem and could not solve it despite getting the actual hardware configuration from the Android system itself. As you say, you get what you pay for with these tablets.
when you flash a incorrect recovery it will load an incorrect kernel. doing a cat /proc/partitions from the recovery you can notice the kernel see a different partition layout.
on mine original kernel has nanda to nandj so 10 partitions.
the incorrect recovery show nanda to nandg.
when you exit from recovery the recovery executable write somewhere to make a clean boot, but it write it on a wrong partition, so this is cause the bootloop
to recover the situation one has to find a working recovery for the device and the correct number of the ORIGINAL PARTITIONS from here (http://forum.xda-developers.com/showthread.php?t=2189640) then overwrite the bad recovery using dd
1st) start an adb shell and find what is the recovery partition as the bad kernel see it, recovery partition usually is 32mb
my bad recovery seen the recovery partition as nande (while i knew my original recovery was on nandg)
2nd) adb push the correct recovery on the / (adb push recovery.img /)
3th) from the adb shell, dd if=/recovery.img of=/dev/block/nande
4th) reboot
it will start again on the recovery, but this time with the correct partition layout, when you choose reboot it will restart as usual.
Hi I Also have this issue on my tablet
trying to use this thread http://forum.xda-developers.com/showthread.php?t=2189640 to install cwm I ended up having CWM Bootloop mine's also allwinner a13b running 4.2.2 JB, will I be able to fix this using the Faastjb rom? but its only working on A13 and not for A13b??
shutt1e said:
when you flash a incorrect recovery it will load an incorrect kernel. doing a cat /proc/partitions from the recovery you can notice the kernel see a different partition layout.
on mine original kernel has nanda to nandj so 10 partitions.
the incorrect recovery show nanda to nandg.
when you exit from recovery the recovery executable write somewhere to make a clean boot, but it write it on a wrong partition, so this is cause the bootloop
to recover the situation one has to find a working recovery for the device and the correct number of the ORIGINAL PARTITIONS from here (http://forum.xda-developers.com/showthread.php?t=2189640) then overwrite the bad recovery using dd
1st) start an adb shell and find what is the recovery partition as the bad kernel see it, recovery partition usually is 32mb
my bad recovery seen the recovery partition as nande (while i knew my original recovery was on nandg)
2nd) adb push the correct recovery on the / (adb push recovery.img /)
3th) from the adb shell, dd if=/recovery.img of=/dev/block/nande
4th) reboot
it will start again on the recovery, but this time with the correct partition layout, when you choose reboot it will restart as usual.
Click to expand...
Click to collapse
Sir will this work with an allwinner a13b processor with 10partitions, running jb 4.2.2??
NotthedroidIwaslookingfor said:
Hi Android experts!
I need some assistance fixing a problem I caused & am now stuck in a recovery boot loop.
- bought a Thomson QM734-8G tablet (Allwinner A13b clone), running Jellybean 4.2.2;
- PC interface worked fine in MTP and large storage modes;
- setup Android SDK & Java JDK on PC and communicate with tablet via ADB;
All OK so far
After a couple of days, I decided to replace stock recovery with ClockworkMod Recovery, so I could start messing about with the tablet.
I found the CWM 6.0.2.8 mod supposed to work with these tablets and, following instructions, determined it was indeed running on sun5i hardware and had 10 partitions (nandj) and downloaded the appropriate version.
I used ADB sideload to install CWM and everything appeared to work OK ... until I rebooted and found myself stuck in a never-ending cycle of CWM-based recovery bootloop
All I get is the CWM recovery console, with a few lines of error & the tablet will go no further.
E:can't mount /cache/recovery/command
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
Also, pretty much none of the CWM functions work properly and nothing will mount through the 'Mounts and Storage' section, although sideload mode still seems to work.
Attempts to use ADB sideload to install a different CWM or other recovery image have all failed, and LiveSuit and PhoenixSuit both have issues detecting the tablet (despite trying various versions of each & following instructions precisely), so I can't flash a replacement ROM to fix things.
At the moment, I just want to rip CWM out and go back to factory recovery mode and have a working tablet again!
Any suggestions on how to resolve this problem would be greatly appreciated
P.S. I think the Bootloader is locked and the tablet is unrooted. Superuser or SuperSU don't want to install properly. However, using ADB, it looks like I can get root access in shell (#).
Click to expand...
Click to collapse
same problem with
ubislate 7c+
no solutions
i try lots of from here but nothing..........
aasifnasim said:
same problem with
ubislate 7c+
no solutions
i try lots of from here but nothing..........
Click to expand...
Click to collapse
ive modded cwm recovery for the a13 10 partitions just tested on my tablet works find all partitions mount and no boot loop if any one wants it let me know icould probably mod the other partitions but would need a rom dump to do it
Hey guys,
If you want to end the bootloop, the only solution is to flash it with a working rom.
now for the reason of this bootloop:
i hope you all are using cwm 6.0.*.*... Just download the zip according to your partitions and hardware.
Then from your running android device copy the nand.ko file.
it can be found in modules folder
then extract the downloaded cwm zip file adn then the recovery.img and go to the system folder and replace the nand.ko file with yours.
then install the recovery using adb and bingo you're done!
Hello guys, i'm new on the world of Android and i need a little help. I'm newbie but i learn fast.
I got a new phone with android 4.4.2 China honor 3 (fake), after uninstalling some China app the operation system started to stuck at logo at the start.
So to solve the problem i red that i could restore the old OS using ROM file. The factory where i bought the phone sent me the official ROM file for my phone.
Now i entered on Recovery mode, first i did "wipe data/factory reset", then with ADB i loaded the file .zip "adb sideload update.zip". But how the file is uploaded it says "Installation aborted", without any error.
So now i need your help how can i restore this system... I tried also to buy an SD card 8 gb and upload the file on the SD, but same error.
Thank you for your help!
Bump! Need help guys
SUMMARY:
I unistalled wrongly MIUI (MiHome app) and the phone stopped working correctly.
Phone is a fake honor 3c with MTK 65xx processor.
1 - Phone doesnt load the main theme, after the android logo i see a black page. (i see the top bar where there are wifi, time etc)
2 - The phone is not rooted. (i think)
3 - I can enter in Restore Mode and Factory Mode.
4 - I got the official ROM file. (the factory gave me it)
5 - All file zip (that i try to use in recovery from SD or ADB) give me "Installation aborted" without any error.
6 - I haven't USB DEBUG enabled, and i can't enable it cause i can't load the Operation system.
Stuck on BootLoop
I am currently facing the same Issue i changed the system/framework (of the CHERRY MOBILE JELLY) with the folder of the SamsungS5 system/framework
cause I was thinking that it'll worked too after changing the system/media of my phone
PLEASE HELP
GUYS
Download and flash the stock ROM with SP flash tools....to will solve all the problems...
the best place to go for any rom for china phones is needrom just google it. I had a jiake v8 phone and this was the only place where i was able to find rom for my phone. good luck ....
I face the same prob!
I have a canvas 2.2 a114 which I bought a few days back . I had been using it very smoothly(not rooted and is new). But suddenly it started to reboot and was stuck at the canvas logo. I have the rom file, but it simply says "Installaton aborted when I load the zip file. help plz! Thanx.
guys the best way to do this is to go to youtube. Find how to port rom to mtk devices or china phones there are plenty of videos. It will be much easier for you to do something when you see how someone is doing it and then you do it for yourself. I have a jiake v8 pphone and this is what i did is not that easy to explain much easier to see.
you can try reflashing the stock rom (You May not lose data) or you can install the stock recovery
Fixed
BrendanWk said:
you can try reflashing the stock rom (You May not lose data) or you can install the stock recovery
Click to expand...
Click to collapse
I was fed up at last and i sent it off to micromax center. They said it was a software prob.
---------- Post added at 09:55 AM ---------- Previous post was at 09:47 AM ----------
Guys I finally figured out (I am new to the android family) that i should install a custom recoery inorder to flash roms. I cant flash roms in stock recovery.
Hi,
Last night my lenovo tab 2 a 7-10 got an update, i downloaded the update and proceed to restart and install it, the update failed at around 90% and the tab rebooted, its now stuck at recovery, factor reset/wiping cache did not help, im unable to flash a rom as SP Flash tools cant detect it even after installing all the necessary drivers and also when i press the volume down button when connecting to my PC, is it possible to flash a stock rom via recovery? if so, can anyone send me the link for the stock rom, should be a zip file i think? i have already download a stock rom from "forum.mytabletguru.com" but its in rar format and i cant flash it using SP flash tools as already mentioned before, thanks in advance
PS: im not an advanced user, so using ADB is out of the question, the tab is not rooted and lenovo service center is like a 100 miles away so its not an option
Edit: i was able to download the latest lollipop rom T2-A7-10F_S000044_ROW_TO_T2-A7-10F_S000054_150801_ROW_WC69.zip and successfully updated via recovery
same goes here bro..im also stucked ,but mine was rooted ,now its showing error ,i tried wipedata/factory reset ,,,not worked
same here.
hasi6764 said:
same goes here bro..im also stucked ,but mine was rooted ,now its showing error ,i tried wipedata/factory reset ,,,not worked
Click to expand...
Click to collapse
remedialguns said:
same here.
Click to expand...
Click to collapse
I have successfully flashed the stock lollipop rom, the steps are simple, download the rom, copy to ext sd card, boot into stock recovery, install from sd card and choose stock rom.zip, took about 10 minutes and drained a lot of battery, so i advice you to charge your tab before doing so.
Stock Rom link:
https://yadi.sk/d/E5xmV2lOiXPgc
Edit: this will remove root access
Bricked lenovo tab 2 A7 10f
Bricked lenovo tab 2 A7 10f
install vcom drivers
tool : SP FLASH TOOL
stock rom kitkat - lollipop
It doesn't work
Help me....
tablet not turn
tablet does not enter - recovery
Phone: LG Aristo MS210 (Metro PCS)
Bootloader: TWRP 3.0.3.0
So let me explain. I was just figuring out how to root the LG Aristo since I had never done it with a custom ROM. Yes, true story. Anyway, I was happy I got it working perfectly until I rebooted my phone. When I rebooted it, SuperSU was gone. I tried going to the play store and redownloading it, but I got an error code -504, and the thing is, I couldn't download any apps. ANY. I decided to look the error code up and I can't find anything on it. I tried multiple times doing multiple different things. From factory resetting, reflashing SuperSU, to factory resetting and then flashing SuperSU, wiping dalvik-cache along with everything except for system. It didn't work and I thought I could get it working.. Well... this next part I really messed up on. I decided to wipe everything. I selected all options and slid the cursor and it failed. The wipe failed. It said "E: /sdcard1 unable to partition" or something like that. I noticed that when I was wiping earlier the internal storage was also called that, and the funny thing is I have no microSD card in my phone. So. :/
Now when I boot I'm stuck on the LG splash screen and nothing else happens. I tried recovery mode (without ADB) with the power button + vol down key as I read here: (I'd post link but I'm a new member) that's how you get into recovery/factory reset. I'd use ADB to get into recovery, but since I just wiped the system, I don't have USB debugging enabled. I tried anyway and I gotta say this is my worst nightmare as I'm too young to get a job, (15 yrs. old) so I can't get a phone. :/ Oh, and if this can be useful: I know it connects to my PC over USB because I hear the sound it makes when a new device is connected. Is there any way I can use that to unbrick it?
EDIT 9/10/2017 9:31 PM (Eastern Time): I managed to get into twrp. I'm currently looking online for how to flash android 7.0 nougat (OS it originally had)
RyokoOnXDA said:
Phone: LG Aristo MS210 (Metro PCS)
Bootloader: TWRP 3.0.3.0
So let me explain. I was just figuring out how to root the LG Aristo since I had never done it with a custom ROM. Yes, true story. Anyway, I was happy I got it working perfectly until I rebooted my phone. When I rebooted it, SuperSU was gone. I tried going to the play store and redownloading it, but I got an error code -504, and the thing is, I couldn't download any apps. ANY. I decided to look the error code up and I can't find anything on it. I tried multiple times doing multiple different things. From factory resetting, reflashing SuperSU, to factory resetting and then flashing SuperSU, wiping dalvik-cache along with everything except for system. It didn't work and I thought I could get it working.. Well... this next part I really messed up on. I decided to wipe everything. I selected all options and slid the cursor and it failed. The wipe failed. It said "E: /sdcard1 unable to partition" or something like that. I noticed that when I was wiping earlier the internal storage was also called that, and the funny thing is I have no microSD card in my phone. So. :/
Now when I boot I'm stuck on the LG splash screen and nothing else happens. I tried recovery mode (without ADB) with the power button + vol down key as I read here: (I'd post link but I'm a new member) that's how you get into recovery/factory reset. I'd use ADB to get into recovery, but since I just wiped the system, I don't have USB debugging enabled. I tried anyway and I gotta say this is my worst nightmare as I'm too young to get a job, (15 yrs. old) so I can't get a phone. :/ Oh, and if this can be useful: I know it connects to my PC over USB because I hear the sound it makes when a new device is connected. Is there any way I can use that to unbrick it?
EDIT 9/10/2017 9:31 PM: I managed to get into twrp. I'm currently looking online for how to flash android 7.0 nougat (OS it originally had)
Click to expand...
Click to collapse
Hi,
Well the only way to fix this is that u need to be able to boot into recovery.
If u tried booting into recovery by holding the power and vol+/- and u end up booting to the boot logo, then recovery is also wiped.
In this case, u will need to check if u have access to fastboot. If so then obtain the twrp recovery for ur device and flash it then tried booting into recovery using the appropriate keys.
When I get time, I will research ur device for any recovery tool and stuff.
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
Hi,
Well the only way to fix this is that u need to be able to boot into recovery.
If u tried booting into recovery by holding the power and vol+/- and u end up booting to the boot logo, then recovery is also wiped.
In this case, u will need to check if u have access to fastboot. If so then obtain the twrp recovery for ur device and flash it then tried booting into recovery using the appropriate keys.
When I get time, I will research ur device for any recovery tool and stuff.
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
I managed to get into recovery. I don't know how to flash Android 7.0 for my Aristo, though.. so I'm researching it.
EDIT: Got a ROM flashed. Everything working now.
please help me this is between live and death. I bought a coolpad 8715 but the android version doesn't work with Playstore and everything about it is in Chinese, I try to change the language to English but the apps are still written in China. please how can I install another OS on it that support Playstore. I downloaded the firmware ( 8715_4.4.016.P1.8715.CPB ) which is in CPB format and i try to extract it to change application and some settings, after extraction I found some files but I don't know which one to edit or how to. The help I needed is that, how to edit my firmware .....CPB file after extraction and pack it back as .......CPB file so that I can use it to flash my coolpad 8715. Or is their any OS or ROM I can use like KitKat, lollipop, marshmallow miui etc. I try to update the phone with wireless hotspot, not working. I also try to install KitKat 4.4.2 Custom ROM through the phone recovery mode which is in China, but showing verification failed and signature error. please help me what can I do, am ready to take any ricks.
King smus said:
please help me this is between live and death. I bought a coolpad 8715 but the android version doesn't work with Playstore and everything about it is in Chinese, I try to change the language to English but the apps are still written in China. please how can I install another OS on it that support Playstore. I downloaded the firmware ( 8715_4.4.016.P1.8715.CPB ) which is in CPB format and i try to extract it to change application and some settings, after extraction I found some files but I don't know which one to edit or how to. The help I needed is that, how to edit my firmware .....CPB file after extraction and pack it back as .......CPB file so that I can use it to flash my coolpad 8715. Or is their any OS or ROM I can use like KitKat, lollipop, marshmallow miui etc. I try to update the phone with wireless hotspot, not working. I also try to install KitKat 4.4.2 Custom ROM through the phone recovery mode which is in China, but showing verification failed and signature error. please help me what can I do, am ready to take any ricks.
Click to expand...
Click to collapse
Sent from my LGE LM-X220 using XDA Labs
Dear All,
Good morning
I am in a big trouble and hope you expert member can get me out of that. Another thing is I am very new to rooting and all the like stuff and whatever I done below on the basis of you tube tutorials.
Now I explain my problem:-
Model No:- Samsung J5 (j500f)
Android Version:- 6.0.1
I rooted my phone through TWRP. It worked fine. Thereafter I installed “Xposed Zip” from a link found from Google through TWRP. From here all my problems get started.
After reboot it stucks on bootloop. After reading some online stuff I tried to flash a stock rom (android 6.0.1) from the link given below:-
https://forum.xda-developers.com/galaxy-j/development/rom-stock-marshmallow-v0-1-t3404440
I downloaded the zip file and transfer the same to internal memory. I wipe the data (system and cache) and installed the zip file through TWRP. But after reboot now every time the phone goes straight to TWRP recovery.
I taken the phone to mobile repair center but the person there says that even after installing stock rom the problem persists.
I have not tried anything after that.
The following messages occur left top of TWRP recovery:-
“Recovery is not seandroid enforcing
Set warranty bit:- Recovery”
Further when I click the 4 horizontal bars (sorry for vague description) the following message is showing:-
Updating partition details….
…done
Full SELnux support is present.
Running boot script….
Done.
MTP Enabled
Please help as I fear to lose my phone.
Thanks in advance!
Plz help. I am without phone. Plz Plz Plz