So guys i have lenovo S860 2GB EU version rooted with TWRP 2.7.1.0 from lenovo-forums.ru.All good until i decided that i will put some music on it>connect to pc transfer around 3 gb music then HOT UNPLUG/will never do that again../ from pc and decide to reboot into recovery and make backup.When i rebooted it said no OS found.From TWRP i tried factory reset>the output is unable to mount cache,data,system,preload.So i guess that my partitions are corrupted.Please help me to fix them.I have one week older twrp backup and if i figure out how to fix corrupted partitions i think i can use it.So what to do next?I red about some FASTBOOT/ADB commands,but it's for different devices...
Flash ROM
phiratio said:
So guys i have lenovo S860 2GB EU version rooted with TWRP 2.7.1.0 from lenovo-forums.ru.All good until i decided that i will put some music on it>connect to pc transfer around 3 gb music then HOT UNPLUG/will never do that again../ from pc and decide to reboot into recovery and make backup.When i rebooted it said no OS found.From TWRP i tried factory reset>the output is unable to mount cache,data,system,preload.So i guess that my partitions are corrupted.Please help me to fix them.I have one week older twrp backup and if i figure out how to fix corrupted partitions i think i can use it.So what to do next?I red about some FASTBOOT/ADB commands,but it's for different devices...
Click to expand...
Click to collapse
Flash new ROm using SP FLash Tool or change ur recovery...use latest TWRP 2.8.4.0
have the same problem for lenovo a328. how to fix this? i think i accidentally wiped partition using samsung a7 ROM for a328.
phiratio said:
So guys i have lenovo S860 2GB EU version rooted with TWRP 2.7.1.0 from lenovo-forums.ru.All good until i decided that i will put some music on it>connect to pc transfer around 3 gb music then HOT UNPLUG/will never do that again../ from pc and decide to reboot into recovery and make backup.When i rebooted it said no OS found.From TWRP i tried factory reset>the output is unable to mount cache,data,system,preload.So i guess that my partitions are corrupted.Please help me to fix them.I have one week older twrp backup and if i figure out how to fix corrupted partitions i think i can use it.So what to do next?I red about some FASTBOOT/ADB commands,but it's for different devices...
Click to expand...
Click to collapse
i am in a similar situation. I soft bricked while looking at some priv-aps and rebooted and stuck. I had made a backup on the 31st last month so i was able to recover unfortunately i had made some important changes earlier yesterday and needed to get that back. I made a backup even tho i was unable to boot and from there i am attempting to just restore the data partition and hopefully i can restore the lost changes. I also found you can extract the twrp recovery files on a PC by changing the name of the files to .tar and unzipping them. Hope this helps
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!
I have a Nabi 2 UK for my son and had GAPPS installed but stayed on the 1.9.37 version as the OAT would not work.
I now see that I can get the tablet up to 4.1 and get GAPPS as well but I seem to be defeated at the last step every turn but the 'dead' android on it's back.
I don't have the original back up to start from.
I've gone to the 1937 stock image and via TWRP, the OAT'ed to 2.1, but the second 2.3 update fails with the dead android
I've tried 2311 which also fails in the same way.
I've seen some conversations on these boards but the file outlined are often out of bandwith and I can't comment on the threads to ask for help.
So now I'm back to 1.9.37 but I also can't seem to reinstate GAPP using Nabi Labs tools I as it braks the nabi mode and the tablet won't work.
All in all this is turing out to be a massive waste of time. Any suggestions how I can salavge this?
Cheers
Fulhair
Fulhair said:
I have a Nabi 2 UK for my son and had GAPPS installed but stayed on the 1.9.37 version as the OAT would not work.
I now see that I can get the tablet up to 4.1 and get GAPPS as well but I seem to be defeated at the last step every turn but the 'dead' android on it's back.
I don't have the original back up to start from.
I've gone to the 1937 stock image and via TWRP, the OAT'ed to 2.1, but the second 2.3 update fails with the dead android
I've tried 2311 which also fails in the same way.
I've seen some conversations on these boards but the file outlined are often out of bandwith and I can't comment on the threads to ask for help.
So now I'm back to 1.9.37 but I also can't seem to reinstate GAPP using Nabi Labs tools I as it braks the nabi mode and the tablet won't work.
All in all this is turing out to be a massive waste of time. Any suggestions how I can salavge this?
Cheers
Fulhair
Click to expand...
Click to collapse
Hi.
I had a similar issue (US ROM though). I had dead Android guys, messages in TWRP that I didn't have an operating system installed and all kinds of other issues. I really thought that I had bricked the Nabi as I was up against a wall and nothing I was finding online was working.
I have posted this before elsewhere -- this is what I did to get out of it:
I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
You may need to alter some of this since you are in the UK though.. but the main suggestion is to put whatever copy of the ROM onto an SD card (remember to follow the correct directory format for either ICS or JB) and then restore via TWRP to get you running.
2girlzdad said:
Hi.
I had a similar issue (US ROM though). I had dead Android guys, messages in TWRP that I didn't have an operating system installed and all kinds of other issues. I really thought that I had bricked the Nabi as I was up against a well and nothing I was finding online was working.
I have posted this before elsewhere -- this is what I did to get out of it:
I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
You may need to alter some of this since you are in the UK though.. but the main suggestion is to put whatever copy of the ROM onto an SD card (remember to follow the correct directory format for either ICS or JB) and then restore via TWRP to get you running.
Click to expand...
Click to collapse
Thanks for the outline. Sorry if I'm being a bit dim but how do I get the 2.6.3.0 TWRP onto it?
I've got the NaviLabs GUI and TWRP'd up to v 2.6.1.0 but need to get the Jelly Bean version.
I've tried the zip install with twrp-recovery-JBNV7AUS-263 but it just breaks TWRP and won't boot.
Thanks again.
Fulhair said:
Thanks for the outline. Sorry if I'm being a bit dim but how do I get the 2.6.3.0 TWRP onto it?
I've got the NaviLabs GUI and TWRP'd up to v 2.6.1.0 but need to get the Jelly Bean version.
I've tried the zip install with twrp-recovery-JBNV7AUS-263 but it just breaks TWRP and won't boot.
Thanks again.
Click to expand...
Click to collapse
Get whatever TWRP you want
http://forum.xda-developers.com/showpost.php?p=48891386&postcount=76
Follow this http://forum.xda-developers.com/showpost.php?p=49956448&postcount=49 to put that recovery in Nabilabgui except use
For XP
C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx\nabixxxx\2\recovery\new
or Vista/7/8
C:\Users\username\appdata\local\apps\2.0\xxx\xxx\n abixxx\2\recovery\new
The post is for the JR I think the above will be right for the Nabi2, I'm mobile so I can't check.
aicjofs said:
Get whatever TWRP you want
http://forum.xda-developers.com/showpost.php?p=48891386&postcount=76
Follow this http://forum.xda-developers.com/showpost.php?p=49956448&postcount=49 to put that recovery in Nabilabgui except use
For XP
C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx\nabixxxx\2\recovery\new
or Vista/7/8
C:\Users\username\appdata\local\apps\2.0\xxx\xxx\n abixxx\2\recovery\new
The post is for the JR I think the above will be right for the Nabi2, I'm mobile so I can't check.
Click to expand...
Click to collapse
Good advice. Thanks for the TWRP instructions,
I can now get the TWRP v2.6.3.0 on, but only the ICS version will boot, The Jelly bean install won't bring up the TWRP screens. I've even tried updating to 2311 from the ICS version and then trying to update to the TWRP JB version with no joy.
Now I can't even get the nabi to connect to the usb in Nabi Lab GUI This is doing my head in!!!
Fulhair said:
Good advice. Thanks for the TWRP instructions,
I can now get the TWRP v2.6.3.0 on, but only the ICS version will boot, The Jelly bean install won't bring up the TWRP screens. I've even tried updating to 2311 from the ICS version and then trying to update to the TWRP JB version with no joy.
Now I can't even get the nabi to connect to the usb in Nabi Lab GUI This is doing my head in!!!
Click to expand...
Click to collapse
If going to 2311 you need to update bootloader. That is in the addonfix zip. Then JB twrp should work.
aicjofs said:
If going to 2311 you need to update bootloader. That is in the addonfix zip. Then JB twrp should work.
Click to expand...
Click to collapse
Okay, so I managed to get back to TWRP 2.6.3.0 under ICS. I then install the 2311 rom, which succeeds. As per instructions, before I reboot I go back and try to install the addon zip in TWRP.
But I get an error
'E:Error executing updater binary in zip '/external_sdcard/addonzip'
Error flashing zip '/external_sdcard/addonzip'.
I'm not sure if the error is something with TWRP or the addon.zip.
One of the microsd I have won't show the addonzip and none of the other TWRP recovery roms..and yes I have checked the directory structure.
Any ideas?
Thanks
Fulhair said:
Okay, so I managed to get back to TWRP 2.6.3.0 under ICS. I then install the 2311 rom, which succeeds. As per instructions, before I reboot I go back and try to install the addon zip in TWRP.
But I get an error
'E:Error executing updater binary in zip '/external_sdcard/addonzip'
Error flashing zip '/external_sdcard/addonzip'.
I'm not sure if the error is something with TWRP or the addon.zip.
One of the microsd I have won't show the addonzip and none of the other TWRP recovery roms..and yes I have checked the directory structure.
Any ideas?
Thanks
Click to expand...
Click to collapse
Okay, I abandoned the addon.zip and went back to 2.1.27 rom and OAT over to get to the last update which failed.
Then installed the OAT2.zip via TWRP and bingo! Now working on Jelly Bean with Google Play - okay it's now the US version but it works
I would caution that the zip install had to be installed on the internal SD not the external one.
But otherwise a BIG thank you to all for building the tools to let me do the update and for your support.
Cheers:highfive:
hi all,
I'm doing formatting to empty up my nephew's FUHU NABI 2, while in TWRP mode, I did Wipe/Format Data. After that the Nabi could not able to load into android anymore, it keep stucking at logo screen,
When I start in TWRP mode, there's an error occured said that:"No OS installed"
could any one can help me to solve this case, I would appreciated.
thank you,
priest1506 said:
hi all,
I'm doing formatting to empty up my nephew's FUHU NABI 2, while in TWRP mode, I did Wipe/Format Data. After that the Nabi could not able to load into android anymore, it keep stucking at logo screen,
When I start in TWRP mode, there's an error occured said that:"No OS installed"
could any one can help me to solve this case, I would appreciated.
thank you,
Click to expand...
Click to collapse
i don't know about this device
but try to help you
try this link
http://forum.xda-developers.com/wiki/Fuhu_nabi_2
priest1506 said:
hi all,
I'm doing formatting to empty up my nephew's FUHU NABI 2, while in TWRP mode, I did Wipe/Format Data. After that the Nabi could not able to load into android anymore, it keep stucking at logo screen,
When I start in TWRP mode, there's an error occured said that:"No OS installed"
could any one can help me to solve this case, I would appreciated.
thank you,
Click to expand...
Click to collapse
what version of the OS are you running ICS or JB?
I'd say download whatever version ROM you are running (ICS or JB) and put it onto an SD card in a "backup" folder formatted for the OS you have and then do a restore from TWRP.
I had a similar issue -- I think when I was installing the JB version of TWRP I also tried to change the screen lock image not realizing that the process had changed for JB. I had a complete mess and I also had the NO OS INSTALLED messages at one point..
What I did (note I had Jellybean on my Nabis, so this is biased towards working with JB):
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
Hello,
I searched in many threads as I could and although I learned that mediatek phones were virtually "unbrikable", I'm afraid it keeps getting worse and won't do more without your expertise.
So a few days ago I was wiping my phone to install another rom and besides wiping data and cache, I also made the huge mistake of wiping SYSTEM... My phone now just boots into recovery and nothing else.
I have an Efox Smart e4, equals to no.1 s6 and hdc galaxy s4 according to other posts here. MTK 6589, 1gb internal, 1,84gb internal sd.
The first custom rom that i installed was Essefour no.1 s6 by iceman and also the touch recovery. The rom performed great but I wanted to solve the issue that the phone kept switching between sd external and internal randomly. Also, I wanted to merge the internal memory with the internal sd so I was gonna try another rom. With this problem, was even trying the stock rom but to no avail.
When I try to install the Smart e4 factory rom for cwm and I get status 7.
E:Resource type (image) failed to load
Installing /sdcard/SMART-E4_V1.0_V01_2013-10-29_CWM.zip
Checking for MD5 file
Skipping MD5 check: no MD5 file found.
... Writing boot...
assert failed: write_raw_image("/tmp/boot.img", "boot")
Error in /sdcard/SMART-E4_V1.0_V01_2013-10-29_CWM.zip
(Status 7)
Click to expand...
Click to collapse
Other roms it just fails.
Right now, my computer windows 8.1 x64 can't identify correctly my phone, only access the sd. So can't do any adb push. In download mode it identifies as lenovo composite interface?? and cdc serial, the last I can't install. In other modes, I get gt-9500 but with the yellow triangle.
I would really really appreciate any help, thanks!
Might try to just edit the updater-script and remove the asserts.
Reference this for more info: http://forum.xda-developers.com/showthread.php?t=2522762
But I think your issue is that since you wiped the system, there's no /tmp folder to store the boot.img. However, if the last rom and this rom can use the same kernel (boot.img) then removing the assert for the boot.img install might do it since wiping the system does not affect the kernel.
What happened to the other rom you know is working somewhat? Can you just reflash that?
Otherwise, you'll just have to find the official way to flash with the scatter file and all that.
I searched for that updater and there are no lines for assert on the stock rom. Also inside the main zip, there are zips for system, boot, recovery and logo...
I'm trying to install the stock rom to play it safe since it was the same that came with the phone. The previous rom I talked about, I deleted it and now the phone isn't recognized on the computer..
Since I don't know if they have the same kernels, is it safe to try and reinstall the custom rom?
As of using scatter and such, maybe I need other pc to get the drivers running again.
Will let you know
I got it!!
The zip from the stock rom wouldn't let me install the kernel (boot). Managed to install only the rom, and as you said the kernel wasn't the same.
Eventually I reinstalled the custom rom and afterwards flashed a completely different rom via spflash tools since it connected successfully to my computer this time.
As I'm already restoring apps and data, I think everything is working properly.
Once more, thank you very much
Hi,
I have a samsung S3 and I want to update it to lollipop or above as my nexus 5 has started randomly rebooting and I need a phone to use whilst I sort a replacement.
I have been following this guide: wccftech.com/install-aosp-android-5-1-1-lollipop-on-galaxy-s3/ as I'm a bit of a noob when it comes to this custom rom business.
I have rooted the device and installed clockworkmod recovery v6.0.1.2. and copied over the rom and the gapps file to my phone.
I then booted into recovery mode and made a backup of the current setup.
I then did the factory reset and the cache wipe(s) and installed the new zip for lollipop and then the gapps.
This is where I received an error "E: Error in /sdcard/0/0/0/Download/gapps-lp-20150314.zip (status 7) installation aborted".
I figured that I should restore to my backup now but when I press it, the app says that files can't be found.
I can see that the files that I backed up do exist but they appear to have been dumped inside a new directory called /0/0/0 (I think this has got three levels because I've tried this a few times).
Now I can't boot into an OS to get any other roms on the phone and I can't edit the files on there (I googled and saw a possible fix for the gapp status 7) and I can't get clockworkmod to recognise an external SD card so I can copy over a new rom or file to try (I have googled and it's suggested the FAT32 is the format for this phone and my size of SD card (16GB)).
Can anyone offer me some advice on how to get out of this situation?
Thanks
Sounds like you're at a place where you should start exploring using your computer instead of a recovery in order to fix your system.
I recommend using the PC software Odin and installing a stock ROM of your device. (Or perhaps using fastboot)
There's plenty of guides on how to use Odin both here on XDA and on the rest of the internet if you just look around a bit
EDIT: This link contains a (possible) fix for your problem.
http://forum.xda-developers.com/showthread.php?t=2522762
Don't use cwm as it is an outdated recovery. Use twrp instead.
Sgt.Mindfudge said:
Sounds like you're at a place where you should start exploring using your computer instead of a recovery in order to fix your system.
I recommend using the PC software Odin and installing a stock ROM of your device. (Or perhaps using fastboot)
There's plenty of guides on how to use Odin both here on XDA and on the rest of the internet if you just look around a bit
EDIT: This link contains a (possible) fix for your problem.
http://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
I had a look at the link you suggested and it's one of the suggestions that had come up whilst I was googling for a fix. Unfortunately, I don't have any way to get the updated script onto the phone as the phone isn't picked up by my pc whilst it's in this state, and I can't get the recovery tool to recognise the sd card so I can't put it on there either.
I'll take a look at the stock rom or fastboot option and see if I can get back into the phone. Maybe then I can apply the fix in the suggested post.
Thanks
audit13 said:
Don't use cwm as it is an outdated recovery. Use twrp instead.
Click to expand...
Click to collapse
I'll see if I can install twrp through odin.
Thanks for your help
If the phone works in download mode, try to flash a stock rom too.
Update - fixed
Hi all, just wanted to let you know that I fixed the device with the combined advice from here:
I installed TWRP after holding the volume down + power + home buttons and then pressing volume up when the message appears (I can't remember what this mode is called). I then flashed the device with the TWRP image.
After this I rebooted into the TWRP recovery mode (Volume up + home + power and then release power button when the samsung logo appears).
At this point, the device appeared on my windows machine so I could upload a new image to the internal memory.
I decided to copy on CM13 and GApps.
I then wiped the cache, system, data, and davik cache using TWRP, then I installed CM13 and GApps.
After a reboot the device came back up as a new install.
Hopefully that information may be useful to somebody.
Thanks for all your help