[Q] Unable to boot into CWM with Sanei n10 tablet. - Android Q&A, Help & Troubleshooting

Hey guys,
I have a bit of a head scratcher. I am currently trying to flash my new Sanei n10 tablet with CM10 and it is proving much more difficult than I first imagined.
My main problem seems to be that the device just does not want to boot in CWM. I have installed the latest version of CWM (found here) via the Terminal Emulator but it doesn't boot into CWM Recovery, but rather just boots normally. I have also tried using the hard keys to boot into it but all that does is boot me into the default android system recovery (3e) which is useless as it will only update from verified roms.
The device is rooted and I have ROM Manager installed. I have given Terminal Emulator superuser permissions... It just doesn't seem to want to boot into CWM Recovery. I have tried using both ROM Manager as well as NOVO7 Tools to boot into it but I get the same results (device just reboots normally)
I think that it might be something to do with the stock ICS 4.0.4 that came with the device.that is causing me so much hastle, but I was hoping someone out there might have experienced a similar issue or can offer some insight to where I am going wrong.
Thanks in advance!
M

msm1003 said:
Hey guys,
I have a bit of a head scratcher. I am currently trying to flash my new Sanei n10 tablet with CM10 and it is proving much more difficult than I first imagined.
My main problem seems to be that the device just does not want to boot in CWM. I have installed the latest version of CWM (found here) via the Terminal Emulator but it doesn't boot into CWM Recovery, but rather just boots normally. I have also tried using the hard keys to boot into it but all that does is boot me into the default android system recovery (3e) which is useless as it will only update from verified roms.
The device is rooted and I have ROM Manager installed. I have given Terminal Emulator superuser permissions... It just doesn't seem to want to boot into CWM Recovery. I have tried using both ROM Manager as well as NOVO7 Tools to boot into it but I get the same results (device just reboots normally)
I think that it might be something to do with the stock ICS 4.0.4 that came with the device.that is causing me so much hastle, but I was hoping someone out there might have experienced a similar issue or can offer some insight to where I am going wrong.
Thanks in advance!
M
Click to expand...
Click to collapse
here
1. Download the latest ClockWorkMod for Allwinner A10 tablets from here:
http://forum.xda-developers.com/show....php?t=1802268
2. Put all three files in the ZIP inside the root of a MicroSD card and insert it in the tablet
3. Check from the Terminal app inside the tablet to see if the MicroSD card is mounted in /sdcard (just type "ls /sdcard").
4. If the "ls" command doesn't show anything (that's what happened in my case), then you must modify the "install-recovery.sh" file and replace all instances of "/sdcard" with "/mnt/extsd".
5. With the proper "install-recovery.sh" file, run the commands specified in the above xda link (in my case the card is in "/mnt/extsd" instead of "/mnt/sdcard" as the original example shows):
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
6. The tablet will then reboot to CWM recovery. Then follow the regular steps to install Cyanogenmod (wipe plus install ROM + GApps + Compatibility). This time the Recovery menu won't care about the files being unsigned and will install them right away!

Related

[Q] How do I restore a borked bootloader ?

Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
obarthelemy said:
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
Click to expand...
Click to collapse
If you can still use ADB your tablets bootloader is likely not messed up, it sounds like you booted the tablet into fastboot mode not recovery. To get into recovery you can enter it by holding a key combination the most common combination is holding volume up plus the power button at the same time. If that doesn't work from ADB you should be able to get into recovery by running the command:
Code:
adb reboot recovery
Also ROM manger doesn't always work right with every device so I would recommend just uninstalling ROM Manager for now. If it is booting fine into bare ICS then your tablet should be ok, if your looking for Google Apps for ICS they can be found here http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip. Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
obarthelemy said:
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
Click to expand...
Click to collapse
obarthelemy said:
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
Click to expand...
Click to collapse
obarthelemy said:
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
Click to expand...
Click to collapse
The recovery you are referring to is to the standard Android 3e recovery it is included in every version of Android, and will always be like that unless you install a custom recovery such as CWMR and or TWRP. As a general rule you should never install a custom ROM without having a custom recovery image installed first, essentially all the stock 3e recovery is good for is installing OTA updates and preforming a basic factory reset of your phone. You should try and fix your recovery before going any-further, you can sign the un-signed zip by using this tool. Overall, I would focus on trying to fix the recovery to prevent any further damage to your tablet and so that way you have a simple way to recover from anything that might go wrong when flashing ROMs, mods, and other zip files.
issue with the uImage linked
The uImage linked on the download pages for the CM10 and CM9 version ends in ".*"
I have no clue what the normal extension should be; replacing that *.zip doesn't work. Is the file bad, or am I just too clueless about what to do with it ?
Ok so the question is:
1- which "recovery mode" file should I install on my tablet, especially since the mod author's ones seem flaky
2- how do I do that via ADB since my tablet no longer seems to have a working "recovery mode".
I'm sorry to hassle you with those questions... I've looked around, I can't find info nor files I'm confident about ?

[Q] "Bricked" Allwinner A10 cmp741e Tablet, ADB works but lacks system/bin/sh

[Q] "Bricked" Allwinner A10 cmp741e Tablet, ADB works but lacks system/bin/sh
Hey guys, Please help me out. I am so close to getting the tablet to boot into android OS again but I made a silly mistake and I am not sure what to do now. I am a noob and have tried everything. Your help is greatly and desperately appreciated.
I have the Craig 7" tablet, model CMP741e, processor AllWinner A10.
What happened: I formatted my /system and rebooted, so /system was totally empty. My device will only boot to the splash screen and cannot get to the booting animation. Problem is, there is no hardware key combos to boot into recovery again.
Recovery was installed with this script:
Code:
cat /sdcard/recovery.img > /dev/block/nandg
One could boot into recovery with this script AFTER booting into android OS:
Code:
echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot
I cannot boot into recovery through ADB with the above script because the device does not have /system/bin/sh. Whenever I tried the above command to boot into recovery, it tells me that /system/bin/sh is not found.
I proceeded to adb push the entire /system directory from a nandroid backup into the tablet. HOWEVER, I made a silly mistake of pushing a bogus file named "bin" into the /system directory of the device. Now when I tried to push /system/bin/sh into the device, adb tells me that /system/bin is not a directory ( because there is a file named "bin" within the /system directory of the device).
I tried removing the "bin" file from the /system directory of the device but didn't work. "adb rm" did not work, and "adb shell rm" did not work either because adb tells me again that /system/bin/sh is not found.
For now I am looking for a solution to:
1) boot into recovery again
or
2) delete the "bin" file from the /system directory of the device, so I can push my /system/bin folder into the device.
or
3) anything to get my device to boot into android OS again
Any, any advice would be appreciated. Thank you guys.
why don't you try restoring the firmware by booting off a sdcard as described on the manufacturer page in engrish http://www.craigelectronics.com/site/pdetails.php?id=414
---------- Post added at 03:21 PM ---------- Previous post was at 03:18 PM ----------
were you able to update the os at all? for reference my came out of the box with:
Android cersion 4.0.3
Kernel version 3.0.3+ [email protected] #11
Build number CMP741E_0626_v2.0
i'm gonna try flashing the update and see if its newer or worse
do not flash using stock from craigs website! It will make your unit hang on the Android screen. Looks like the OP figured out how to get his unit back with touch controls based on his post on the androidtablets forrum (search for cmp741e nandroid backup)
I have the same issue, but waiting for him to spell out the steps (seems like a few other people are also waiting on him to respond in that thread).
im in the same boat, i flash the stupid rom on the craig site...ive been able to get cwm on in various stages after flashing another slightly compatible rom using the same dumb phoenix tool but no support for touch so im still trying to figure how to get this **** to work right again and hopefully flash some cm9 or cm10 on it
heres my next try that i hope will work
http://www.androidtablets.net/forum...1e-complete-nandroid-backup-4.html#post269539
have you found a cm that would be compatible with the craig tab? I have been trying to find one and stopped looking as of late
t0mmyr said:
im in the same boat, i flash the stupid rom on the craig site...ive been able to get cwm on in various stages after flashing another slightly compatible rom using the same dumb phoenix tool but no support for touch so im still trying to figure how to get this **** to work right again and hopefully flash some cm9 or cm10 on it
heres my next try that i hope will work
http://www.androidtablets.net/forum...1e-complete-nandroid-backup-4.html#post269539
Click to expand...
Click to collapse
Re: [Q] "Bricked" Allwinner A10 cmp741e Tablet, ADB works but lacks system/bin/sh
I got a cm10 that boots but touch screen doesn't work so I didn't get past the first screen after the boot animation. I can't confirm if anything else didn't work but if I could find a compatibility zip for this device I would cross my fingers that it would work
Sent from my SPH-D710 using xda premium
Have you try to boot from SD card? Not sure if it will work for your devise but you are not loosing anything to try...
http://forum.xda-developers.com/showthread.php?t=1605664
Craig CMP741e is stuck in boot loop on the Android logo.
When I try to install or mount using adb cmd I get read only errors and I have tried almost everything to recover/reset the tablet. i opened it unplugged it, tried reset pinhole, hold vol+ power buttons, and phonixcard does not work.
I am able to get this tablet recognized with using the Android SDK bundle, but I do not how to use it really...I appreciate some help on how to do a hard reset or factory reset. i hear theres no key combo for this...i recorded whats going on inside during start up using andriod debug monitor... can i use that to somehow fix it?
delete the spaces in link.. its legit no spam its my problem i need a solution too, plz help
. you tube. com/ watch? v= Rcy kDInH sYE

Help booting TWRP

I rooted my Nook using the method here. I then downloaded Goo Manager though the app store and installed TWRP recovery. If I choose "reboot recovery" in Goo Manager, it will grant SU access and reboot, however it will not boot in to TWRP. it will just reboot the Nook normally. Then I powered down normally and now my Nook won't boot at all! It just shows the splash screen and shuts off or bootloops if i plug it in. What's up?
Edit: I tried doing the root method over again to unbrick it. I could boot in to recovery but the tablet still won't boot after I flash.
Unfortunately I can't help you. Just give my view that whenever I have tried TWRP there has been issues. EIther "not just doing the job" which is annoying but not much more. But also getting stuck in bootloop. When that happened to me I stumbled on the repart.im recover image that put my Tablet back to "out of the box" condition. I ran it and after that I have used CWM without issues.
Hopefully someone will come along with a better answer to you.
asawi said:
Unfortunately I can't help you. Just give my view that whenever I have tried TWRP there has been issues. EIther "not just doing the job" which is annoying but not much more. But also getting stuck in bootloop. When that happened to me I stumbled on the repart.im recover image that put my Tablet back to "out of the box" condition. I ran it and after that I have used CWM without issues.
Hopefully someone will come along with a better answer to you.
Click to expand...
Click to collapse
How did you flash CWM? I can't find any flashable files anywhere. Did you do it through Rom Manager or something like that or did you download a file and flash it through a bootable SD recovery?
Back when I origianlly did it I did it like I outline in this post (under C): http://forum.xda-developers.com/showthread.php?t=2081981
Nowadays I do it differently though, but that process should still work.
GooManager does not flash the right recovery image for some root methods. The Nook Tablet one has acclaim in the name, and when I rooted mine, I realized it tried to flash a build for blaze. I just booted from a CWM SD to install my ROMs, and then flashed TWRP to internal using fastboot.
alevineman said:
GooManager does not flash the right recovery image for some root methods. The Nook Tablet one has acclaim in the name, and when I rooted mine, I realized it tried to flash a build for blaze. I just booted from a CWM SD to install my ROMs, and then flashed TWRP to internal using fastboot.
Click to expand...
Click to collapse
Where did you get the TWRP to flash and what is fastboot?
Snakebear said:
Where did you get the TWRP to flash and what is fastboot?
Click to expand...
Click to collapse
Fastboot is a tool in the Android SDK that can do a lot, including flashing a recovery.
Steps to use
Make a Ubuntu 13.04 virtual machine
Open Terminal
Put in : "sudo apt-get install android-tools-fastboot"
Install CyanoBoot if not already
When booting Press n in cyanoboot
Choose start fastboot using buttons
Plug into computer and hook up to VM
Download TWRP internal 2.4.3.0 from iamafanof.wordpress.com
Open terminal
Type cd Downloads
Type ls
Look for a file that starts with twrp
Type fastboot flash recovery then type the file name of the twrp file
Done
Snakebear said:
How did you flash CWM? I can't find any flashable files anywhere. Did you do it through Rom Manager or something like that or did you download a file and flash it through a bootable SD recovery?
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showpost.php?p=40998406&postcount=3.
my nook tablet stopped in read forever.
my nook tablet stopped in read forever.
volume buttons not working
needs twrp recovery
any help?

Fire 6 Freezes and is useless

A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
ganiman said:
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
Click to expand...
Click to collapse
Your understanding of TWRP is right. Basically, we dd the twrp image with OS 4.5.3 bootloaders (the only bootloaders that will boot unsigned recovery) and then before leaving TWRP flash back (almost) current bootloaders and recovery.
You should be able to adb-sideload the OS 5.1.2 update to fix the freeze. Was device rooted before it updated? Do you know what OS it was on? If you have adb access while device is frozen, run these commands for current OS info:
adb shell getprop ro.build.version.fireos
adb shell getprop ro.build.version.number
No CM12 available. Mostly-working CM11 is here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138
BTW, I assume you tried wiping cache and/or factory reset in recovery. If not, I'd do that first.

How to use magisk to twrp from 2.3.5 gingerbread without a computer?

How to use magisk to twrp from 2.3.5 gingerbread without a computer?
@Didgeridoohan
Do you think its possible to flash twrp from a terminal emulator? Or what are my options?
If you really can't get a hold of a computer you might be lucky with an app like Franco Kernel Manager, Flashify, etc. Problem is that most apps likely won't support or be compatible with that ancient version of Android or whatever root you currently have installed. And, you're also risking bricking your device if you don't have access to a computer...
I really think your best bet is to somehow get access to a computer. Friend/school/work/something...
If you can't install stuff on that borrowed computer you could create a bootable USB with a Linux distro and run everything from there. Linux Mint is quite user friendly, they've got good documentation on how to get things running with a Live Boot USB, and it's not too hard to get adb & fastboot up and running.
Ill try and get a hold of a computer because nothing seems to work on 2.3.5
@Didgeridoohan
I had rooted using framaroot but after a factory reset it wont install supersu or superuser to my app drawer, can you give me a suggestion? Btw im using my xbox one to type this.
@chris1892006
don't waste your time with this: Magisk works only on Android 5.0 and above.
jwoegerbauer said:
@chris1892006
don't waste your time with this: Magisk works only on Android 5.0 and above.
Click to expand...
Click to collapse
thanks so do u know if its possiblle to flash a twrp.zip using terminal on 2.3.5?
chris1892006 said:
thanks so do u know if its possiblle to flash a twrp.zip using terminal on 2.3.5?
Click to expand...
Click to collapse
Is it so hard to read posts carefully?
I found this https://www.youtube.com/watch?v=-YAKGRblIuw
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p9
What part of the command do i change for a yp-g70 venturi? Also can i extract my twrp 2.8.0.0.zip and get the .img out of it or can i flash the .zip?
This what i used to flash cwm/ entropys daily driver kernel
https://forum.xda-developers.com/showthread.php?t=1445840
su
dd if=/sdcard/zImage of=/dev/block/mmcblk0p11
Well i got cwm installed! Now i just need to flash twrp and then a rom
chris1892006 said:
... Now i just need to flash twrp and then a rom
Click to expand...
Click to collapse
Notice, that for Lollipop and up to get it running smoothly, you need a device with minimum 2GB RAM and at least 2GHz dual core processor - what since Android 4.4+ must be a ARMv7 one.
jwoegerbauer said:
Notice, that for Lollipop and up to get it running smoothly, you need a device with minimum 2GB RAM and at least 2GHz dual core processor - what since Android 4.4+ must be a ARMv7 one.
Click to expand...
Click to collapse
Thanks i had 4.4.4 up and running but tried flashing 5.1.1 lollipop on cwm and it corrupted the bootloader. Now i cant get into recovery because twrp wouldnt flash over cwm, i tried to flash twrp 2.8.0.0 & it succeeded yet didnt work after a reboot, why? I read the op but i still cant figure out why it didnt work after a reboot? Still remained cwm.
https://forum.xda-developers.com/galaxy-player/development/recovery-twrp-v2-8-0-0-t2867742
http://www.meticulus.co.vu/p/yp-g70.html
@Didgeridoohan
How do i flash twrp over cwm?
Hey... Look at that, you had some progress. Nice.
I've never used CWM, so I wouldn't know.... Sorry.
@chris1892006
Have you backed up stock recovery IMG through e.g. Flashify app before installing a custom recovery by means of CWM ? Do remember that restoring a backup will essentially wipe any changes made after that backup.
If so then
1. you can restore or flash stock recovery IMG through Fastboot to get CWM out of your system.
2. you can install through TWRP any custom recovery IMG of your choice.
jwoegerbauer said:
@chris1892006
Have you backed up stock recovery IMG through e.g. Flashify app before installing a custom recovery by means of CWM ? Do remember that restoring a backup will essentially wipe any changes made after that backup.
If so then
1. you can restore or flash stock recovery IMG through Fastboot to get CWM out of your system.
2. you can install through TWRP any custom recovery IMG of your choice.
Click to expand...
Click to collapse
thanks only problem is they only make a .zip for twrp for my device... I don't know how to flash it.
That's a really old android version, I'm not sure if it's possible. If you don't have access to a PC, try to ask a friend if they could do it for you, just to be safe. Trying to modify stuff within android, especially on such an old version, with probably unsupported software could result in a bricked device.
Thanks but I finally got TWRP and Lollipop 5.1.1 installed it took an ADB Sideload from a PC to sideload the twrp.zip file for my device and now I'm up and running and very happy to say the very least. Sure I bricked it 3 times in the process but was always able to recover using ODIN and having the proper files on hand.
Now im having an issue with xda on the device where the xda app wont let me sign in and the browser will sign me in but go right back to the sign in page again, idk how to fix it?
I install a dalvik cache wiper with root required and it corrupted the recovery again. So I figured out the exact steps to get this device working perfectly again. Firstly the twrp folder on the external sd card has to be renamed TWRP because it has extra strange characters after the TWRP. Now we know how to restore our backup, we can start by ODIN back to stock, then Framaroot v1.4.1 root the device then download entropys daily driver kernel cwm, the flash it via terminal emulator, reboot, then you have to install meticulous carbon 4.4.4 to fix the partitions and update the cwm to adb sideload the twrp. So you can then flash Meticulus Carbon 5.1.1 and both updates and 5.1.1 pico gapps. Good to go. Meticulus made the kernel overclock to 1.7ghz and it runs pretty darn good honestly. I modded the build.prop vm dalvik heap limit to 384m from 128m to get some extra performance out of it.

Categories

Resources