[Q] Custom recovery and Rom for Blu Star 4.0? - Android Q&A, Help & Troubleshooting

Hi guys, Anyone knows about custom rom or custom recovery for this device?

Custom recovery is easy with the right tools!
marcosek said:
Hi guys, Anyone knows about custom rom or custom recovery for this device?
Click to expand...
Click to collapse
You can make your own ClockWorkMod custom recovery for ANY phone as follows:
WHAT YOU NEED
* Your phone with USB Debugging enabled
* Root access (in other words, your phone must be rooted)
* Busybox installed on your phone
* MTK Droid Tools
* Your computer
HOW TO DO IT:
1. Down load MTK Droid Tools and install on your desktop (do people still have those)
2. Install the Flashify app on your phone (from the Play Store)
3. Open Flashify on your phone
4. Select the Backup/Restore option
5. Back up the current kernel to your SD card (name it it stock_boot.img)
6. Back up the current recovery to your SD card (name it it stock_recovery.img) & close the Flashify app
7. Copy the two files from your SD card (it's saved under Android>data>com.cgollner.flashify>files>flashify-backup) to your desktop NOW YOU HAVE BACKUPS OF YOUR STOCK BOOT AND RECOVERY IMAGES IN CASE YOU EVER NEED THEM IN FUTURE
8. Run your MTK Droid Tools as Administrator and connect your phone to the desktop via USB (you'll see details about your phone in Phone Information ... you can ignore this but it does confirm that MTK Droid Tools recognizes your phone)
9. Now select the tab called "root, backup, recovery"
10. Click on the "Recovery and Boot" button
11. MTK is going to ask you where is the BOOT image for your phone...just select the BOOT image from the folder to which you copied the BOOT image on your laptop
12. MTK is now going to create a CWM custom recovery for your phone. It stores this in its subfolder called "recovery"
13. Now just go to this recovery subfolder. You will see TWO files. Now you rename the one that has "_recovery_" in the name to cwm_recovery.img. DO NOT MAKE THE BONEHEADED MISTAKE of using the file that has "_BOOT_PATCHED_" in the name!
14. Copy the newly renamed cwm_recovery.img to your SD card on the phone
15. Close the MTK Droid Tools program...it's work is done
16. Reopen the Flashify app
17. Select the Flash option and choose the RECOVERY IMAGE from the list of options. DO NOT...I REPEAT...DO NOT SELECT THE boot image OPTION. YOU WILL SURELY BRICK YOUR PHONE AND YOU WILL NEED TO FLASH A SYSTEM BACK TO THE PHONE. Since you have no custom recovery yet, you will be in a very difficult spot! DO NOT DO NOT DO NOT flash anything to the boot partition!!!!
18. Now that you have selected RECOVERY IMAGE, you can now choose the cwm_recovery.img and let flashify do its thing.
19. Once Flashify is done flashing, it will give you the option to REBOOT...do that
20. Behold your new CWM custom recovery
A couple important notes:
* I'm not responsible if you do something boneheaded like flashing the cwm_recovery.img to your boot partition and muck up your phone. I've already warned you repeatedly NOT to do that. It's an amateur mistake (that I made once...LOL!) DO NOT MAKE THIS MISTAKE!
* You did not really need the stock_recovery.img file for anything. BUT I MADE YOU BACK IT UP JUST IN CASE (you can always flash your stock recovery back to the phone). SAVE YOUR STOCK RECOVER AND BOOT IMAGES.
* USE YOUR NEW CWM RECOVERY AND IMMEDIATELY BACKUP YOUR ENTIRE PHONE TO YOUR SD CARD AND PLACE A COPY SOMEWHERE ON YOUR DESKTOP! Now you have two copies. If you ever want to return your phone to stock, just restore your backup and reflash the stock recovery. Then UNROOT your phone. Now, you're completely stock.
* While you're at it, use MTK Droid Tools again and select the SCATTER FROM FILE (and save the map somewhere convenient).

Related

Can I not install custom ROMS?

I bought a used Hero that's already been rooted. I wanted to backup the ROM on there so I installed ROM Manager and it flashed my bootloader image.
Obviously now I don't have the proper recovery image, I have the ROM Manager recovery image. As far as I can tell this image doesn't allow me to do stuff like Clear Dalvik Cache, reset my apps and such.
It does allow me to install a custom ROM -- I installed VillainROM -- but it doesn't let me actually clear my data on my device. So Villain runs like laggy crap because I can't do a proper factory reset with the image. It also didn't delete any of my settings or apps.
Am I missing something or do I have to redo the root procedure to get the proper recovery image back?
scouzer said:
Am I missing something or do I have to redo the root procedure to get the proper recovery image back?
Click to expand...
Click to collapse
No no,... You should be ok to just reinstall the patched recovery.
Try following these instructions from BTDAG's [Guide] Newbie Guide to Install a Custom Rom [Updated 14/04]
Installing a recovery image:
1. On your phone, go to Settings > Applications - and make sure "Unknown Source" is ticked.
2. On your phone, go to Settings > SD card and phone storage - click Unmount SD card.
3. Then click Format SD card.
4. Plug the phone into the computer via USB, then pull down the notification bar and click on the SD card notification. Then click mount.
5. Download this APK and recovery image and save it to your computer:
http://zenthought.org/content/project/flashrec - FlashRec.apk
http://forum.xda-developers.com/showthread.php?t=561124 - Amon_Ra’s Hero Recovery Image
6. Copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
7. Unplug the phone from the computer once they are downloaded to the SD card.
8. Go to the Market and download ASTRO File Manager or any file manager program if you do not already have one.
9. Open the file manager and find the FlashRec apk file and click it and choose open app manager and then install it.
10. When it is installed click Open. Click on Backup Recovery Image and wait for it to finish. If you get "backup failed" response see the "Ib. Installing the correct HTC ROM" section for more details, if the backup is a success carry on.
11. Once done, click on the empty text box in the FlashRec program and type:
/sdcard/recovery-RA-hero-v1.6.2.img
(replace exact name as new versions come out)
Then click on the Flash Recovery Image button and wait for it to finish.
Click to expand...
Click to collapse

◉ First time Rooting : Please check my work...

Hello :
I am going to be flashing my droid phone for the first time (nOOb), and I want to make sure I will doing it correctly.
I have gathered what I believe to be the correct information, and have listed it below.
I am hoping someone can look at the steps to make sure everything is correct and in order.
If I am missing something, or if something does not look right, could you please correct, ammend, or add as necessary.
This would be a tremendous help to me, and I would greatly appreciate it.
Thank you.
1. Root phone using SuperOneClick v2.3.3
A. Install the USB driver for your phone onto your PC
B. Enable USB debugging mode on phone
C. Download and install Java SE developers kit
D. Download and install Android SDK developers kit
E. Connect phone to computer using USB
F. Download and install SuperOneClick v2.3.3
G. Make sure your SD card is NOT mounted
H. Press "Root"
I. Wait for "Success" confirmation
2. Install ClockworkMod Recovery via ROM manager
A. Download and install ClockworkMod ROM Manager
B. Once installed, open ROM Manager
C. Press "Flash ClockworkMod Recovery"
D. Reboot or Power Off
3. Perform a Nandroid backup (full system backup)
A. Make sure you have an install SD card and you have enough free space available on the SD card
B. Open ROM manager and hit reboot to recovery
C. A pop up will ask if you want to reboot into recovery, press OK
D. Phone will reboot and boot into ClockworkMod Recovery
E. Once in CWR, use volume up and down buttons to scroll up and down the menu list
F. Scroll down to "backup and restore"
G. Press "n" button to enter or go to nex sub-menu
H. Press "backup" to start the nandroid backup process
I. Once complete, you will be brought back to the main menu and it will read "Backup complete!"
J. Now scroll up or down to "reboot system now" and press "n" to execute.
K. Once booted and back to Home screen, open your favorite file browser
L. Make you way to your SD card: folder /clockworkmod/backup/(date of backup)
M. Check to see if you have files files: boot image, cache image, date image, nandroid check file, and system image. (note: Usually you will also see a recovery.img (image) file, which is the file that holds the backup for the recovery utility itself. You will see this files with most custom ROM packages.)
Are the above steps correct? Am I missing anything, or is something incorrect?
Thank you!
All is ok with the steps 2 and 3, but in the step 1 isn't necessary to install the Java SE Dev Kit or the Android SDK, SuperOneClick comes with all the necessary tools

.apk file to resolve "you must have ClockwordMod Recovery installed"

Even though clockwork ROM Manager is installed,
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
When I try to run it - it says: "you must have ClockwordMod Recovery installed before continuing! Install the recovery thropugh ROM Manager first"
Normally you would just download it but how is this done on a phone without internet connection, can I download the .apk file somewhere then move it to phone? Android phones are Motorola Cliq and CliqXT.
c627627 said:
Even though clockwork ROM Manager is installed,
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
When I try to run it - it says: "you must have ClockwordMod Recovery installed before continuing! Install the recovery thropugh ROM Manager first"
Normally you would just download it but how is this done on a phone without internet connection, can I download the .apk file somewhere then move it to phone? Android phones are Motorola Cliq and CliqXT.
Click to expand...
Click to collapse
ClockworkMod recovery is not an application (.apk file). It's an image file. You can get the images here: http://clockworkmod.com/rommanager.
Thank you. How do you install the capability to run the image recovery process by simply running it from the ClockwordMod App, not by manually rebooting?
In other words, on a phone with internet access, you simply "Install the recovery thropugh ROM Manager first".
But how do you install it manually without internet access. How do you install the image file you linked to?
c627627 said:
Thank you. How do you install the capability to run the image recovery process by simply running it from the ClockwordMod App, not by manually rebooting?
In other words, on a phone with internet access, you simply "Install the recovery thropugh ROM Manager first".
But how do you install it manually without internet access. How do you install the image file you linked to?
Click to expand...
Click to collapse
See here: http://wiki.cyanogenmod.com/wiki/Motorola_Cliq:_Full_Update_Guide and follow the "Installing a Custom Recovery Image" section. Change the names as needed.
I'm not sure we understand each other so let me try to clarify and by the way thanks for your help:
Goal:
1. From within running CynogenMod launch ROM Manager >
2. Manage and Restore Backups >
3. Select exiting backup > Restore > OK
It automatically reboots and does its thing.
So now, if you have a phone on which ROM Manager is not installed, you install it and launch it from already running CyanogenMod *however* you get this message:
"you must have ClockwordMod Recovery installed"
It then simply downloads something and from then on you are able to use the ROM Manager to restore existing backups not by custom rebooting but by simply running it from within a running CyanogenMod.
Isn't the image file you linked to for custom booting into the restore environment from which you run the restore? I am trying to "run" the restore by simply lunching the ROM Manager which then itself reboots and runs the restore automatically.
What is it exactly that is installed when you get this message so that I can install it on a phone without an internet connection.
I know how to custom boot by holding the button etc. I just want to not custom boot and have it launch automatically by simply using a shortcut and launching the restore process which itself reboots and does its thing.
c627627 said:
I'm not sure we understand each other so let me try to clarify and by the way thanks for your help:
Goal:
1. From within running CynogenMod launch ROM Manager >
2. Manage and Restore Backups >
3. Select exiting backup > Restore > OK
It automatically reboots and does its thing.
So now, if you have a phone on which ROM Manager is not installed, you install it and launch it from already running CyanogenMod *however* you get this message:
"you must have ClockwordMod Recovery installed"
It then simply downloads something and from then on you are able to use the ROM Manager to restore existing backups not by custom rebooting but by simply running it from within a running CyanogenMod.
Isn't the image file you linked to for custom booting into the restore environment from which you run the restore? I am trying to "run" the restore by simply lunching the ROM Manager which then itself reboots and runs the restore automatically.
What is it exactly that is installed when you get this message so that I can install it on a phone without an internet connection.
I know how to custom boot by holding the button etc. I just want to not custom boot and have it launch automatically by simply using a shortcut and launching the restore process which itself reboots and does its thing.
Click to expand...
Click to collapse
The image I linked to is the "thing" Rom Manager downloads when it gives that message (if you have an internet connection). Flashing that file and linking it to Rom Manager will remove that error.
Got it.
Selecting Flash ClockworkMod Recovery from ROM manager to try to use the img file you linked to results in an "error while downloading from server. Please make sure that you have a stable internet connection..."
So that does not work for the thread topic, which is doing this w/o internet connection.
Will try the Android SDK Tools method.
0. The Cliq XT is known as Zeppelin.
1. Install Motorola USB drivers:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
2. Install Java SE Runtime Environment (JRE): http://www.oracle.com/technetwork/java/javase/downloads/
3. Get Android SDK zip: http://developer.android.com/sdk/
4. Unzip it and start SDK Manager.exe and download Android SDK Tools.
5. Get ClockworkMod Recovery, for example:
http://download.clockworkmod.com/recoveries/recovery-clockwork-4.0.0.5-zeppelin.img
Copy recovery-clockwork-4.0.0.5-zeppelin.img to
Android SDK folder android-sdk-windows\platform-tools
7. Phone Settings > Applications > Unknown sources (select green check mark to activate it)
Settings > Applications > Development > Enable USB Debugging
Make sure the phone is rooted. Check if Superuser icon is in the drawer menu.
*** Connect the phone to computer but DO NOT enable USB Drive ***
8. Use DOS to navigate to the android-sdk-windows\platform-tools directory
for example, if the folder location is C:\android-sdk-windows\platform-tools
then in type this in DOS:
c:
cd android-sdk-windows\platform-tools
adb shell
su
***You must press on Allow on the phone when prompted***
cd /sdcard/
flash_image recovery recovery-clockwork-4.0.0.5-zeppelin.img

[Q] How to root Moto E (updated to 4.4.4) ?

I have a Motorola Moto E(XT1022). I bought it recently and just when I first started it, I got the 4.4.4 kitkat update and so I downloaded it right away. Then I realised one of the biggest problems of Moto E i.e. 2.2 gb storage. So i dug into find how to install apps on sd card and got to know that you have to root the phone. On xda, I found various ways to root but they were only for the 4.4.2 version of the phone and others were update to 4.4.4 on aldready rooted devices. Please tell me the way to root my device. Also as I am new to this, I dont understand any words like bootloader, fast recovery, etc. Please help me. Thank you in advance.
Edit: Can I use the way given by deej_roamer in his post here:http://forum.xda-developers.com/show....php?t=2755336
Edit: I am sorry to have posted this in the general section. I don't know how to move it now to the questions section. Sorry again.
Thank You DAVI FELICANO and deej_roamer for their help. I have now successfully rooted my phone. If someone else has a problem, go to Page 2 for the solution.
You can use the defalt method, dont need to change anything.
Who told you that you need root to move apps to sd card?
Once you insert sd card you will get an option in settings/apps to move apps to sd card for those that can be moved.
This is though limited to Apks only and data is still kept in internal sd card.
If this option is not enough for you then you can go the advanced wag by rooting and using gl2sd or link2sd like apps.
DAVI FELICIANO said:
You can use the defalt method, dont need to change anything.
Click to expand...
Click to collapse
You mean I can just follow the way to root if my device would have been running 4.4.2 kitkat (and as suggested by deej_roamer in his post here: http://forum.xda-developers.com/showthread.php?t=2755336 )
Thank you.
SArnab©® said:
Who told you that you need root to move apps to sd card?
Once you insert sd card you will get an option in settings/apps to move apps to sd card for those that can be moved.
This is though limited to Apks only and data is still kept in internal sd card.
If this option is not enough for you then you can go the advanced wag by rooting and using gl2sd or link2sd like apps.
Click to expand...
Click to collapse
I know friend. I was talking about games like asphalt 8 and dead trigger which have data of size 1.5 gb because of which I wanted to root my phone. Thank you for the advice.
SArnab©® said:
Who told you that you need root to move apps to sd card?
Once you insert sd card you will get an option in settings/apps to move apps to sd card for those that can be moved.
This is though limited to Apks only and data is still kept in internal sd card.
If this option is not enough for you then you can go the advanced wag by rooting and using gl2sd or link2sd like apps.
Click to expand...
Click to collapse
You can install only one game due to it's low internal memory. By one game I mean high graphics game. The obb file remains in the internal storage even after moving to SD card. I tried many things like making SD card default storage using SDK tools but to no Vail. Guess the only way now is to root it & use apps like gl2sd
Sent from my XT1022 using XDA Free mobile app
5zan said:
You can install only one game due to it's low internal memory. By one game I mean high graphics game. The obb file remains in the internal storage even after moving to SD card. I tried many things like making SD card default storage using SDK tools but to no Vail. Guess the only way now is to root it & use apps like gl2sd
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
If you read my post correctly then that's what I have written.
5zan said:
You can install only one gphone and due to it's low internal memory. By one game I mean high graphics game. The obb file remains in the internal storage even after moving to SD card. I tried many things like making SD card default storage using SDK tools but to no Vail. Guess the only way now is to root it & use apps like gl2sd
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
I know friend. Thats why in this post I asked how to root the phone and not how to install games on sd card. Thanks.
Harsh862 said:
You mean I can just follow the way to root if my device would have been running 4.4.2 kitkat (and as suggested by deej_roamer in his post here: http://forum.xda-developers.com/showthread.php?t=2755336 )
Thank you.
Click to expand...
Click to collapse
Yes this method work with all 4.x roms i made it in my 4.4.4
(Sorry my bad english)
Sent from my XT1025 using Tapatalk
DAVI FELICIANO said:
Yes this method work with all 4.x roms i made it in my 4.4.4
(Sorry my bad english)
Sent from my XT1025 using Tapatalk
Click to expand...
Click to collapse
Ok. Thank you friend. I will reply if I face any problem. Thank you again.
Any idea of rooting the device without unlocking BL...thnx in advance
Sent from my XT1022 using XDA Premium 4 mobile app
Thank You everyone for your help. I now have succesfully rooted my phone. Thanks a lot. I owe you all.
Harsh862 said:
Thank You everyone for your help. I now have succesfully rooted my phone. Thanks a lot. I owe you all.
Click to expand...
Click to collapse
Hi. i am in the same boat as you were. i have a moto e dual sim version running on 4.4.4 out of the box. i have asked around also but havent found a solution.
i have successfully unlocked the bootloader but i have tried n number of times to flash recovery but unsuccessful.
it just doesnt flash, i have tried official and unofficial TWRP and even CWM but i just simply get the recovery to stick.
Could you please tell me how you successfully flash recovery .
thanks in advance!!
shamps said:
Hi. i am in the same boat as you were. i have a moto e dual sim version running on 4.4.4 out of the box. i have asked around also but havent found a solution.
i have successfully unlocked the bootloader but i have tried n number of times to flash recovery but unsuccessful.
it just doesnt flash, i have tried official and unofficial TWRP and even CWM but i just simply get the recovery to stick.
Could you please tell me how you successfully flash recovery .
thanks in advance!!
Click to expand...
Click to collapse
I followed the thread by deej_roamer here http://forum.xda-developers.com/showthread.php?t=2755336
Try out my steps:
[Your phone battery must be at least 75%]
1. First download "Fastboot" from the thread. (Click on the "mfastboot-v2" link in the thread)
2. Next install it in a folder and remember that folder. Also, make sure you select the option of "Create shortcut on Desktop" during installation.
3. Next download CWM recovery from this thread - http://forum.xda-developers.com/moto-e/general/root-moto-e-rooting-flashing-recovery-t2802971 (Click on the "CWM 6.0.4.9 recovery For MOTO E" link in the thread)
4. Copy the "cwm6.0.4.9_recover.img" file to the installation folder of fastboot.
5. Next download SuperSU v2.02 from here - http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip (Click on "UPDATE-SuperSU-v2.02.zip" link)
6. Don't Extract Supersu zip file.
7. Connect phone to pc. Copy the zip file to your internal memory(the directory of int. memory is /sdcard) (The directory for ext. sd card is /storage/sdcard1).
8. Remove your phone from your pc.
9. Switch off your device.
10. Turn on your device by holding power off button and volume down button together for 6-7 seconds. Quickly connect your phone to your pc.
11. The bootloader must be showing usb connected.
12. Run fastboot from your desktop.
13. Now type this (without quotes) - "fastboot flash recovery cwm6.0.4.9_recovery.img"
14. Look at the screen of device. It must be showing "Mismatched partition size (recovery)". It is normal don't worry.
15. Press volume down once (recovery will be selected) and then volume up so that it goes into recovery.
16. It will show the bootloader unlocked warning. Don't worry about it.
17. Your phone should now be in CWM recovery.
18. Don't do anything except what I tell you.
19. In this menu movement is done by the volume rockers ans selection by power button.
20. Press volume down so that "install zip" is selected.
21. Press power button.
22. Select "choose zip from /sdcard". Press power button.
23. Find the SuperSU.zip file(It will probably be in the "0/" folder)
24. It will ask to confirm install. Select Yes.
25. SuperSU will be installed.
26. Select CWM reboot. When you select CWM reboot, it will display "root access possibly lost - Fix?". PLEASE Select "No".
27. Your phone will now reboot. (The bootloader unlocked warning will be shown and then the boot animation).
28. Open your menu(in the phone) and find SuperSu app (a # symbol will be there in its icon).
29. Disconnect your device from the pc.
CONGRATULATIONS YOU HAVE A ROOTED MOTO E.
If you ever wish to flash any other recovery (like twrp),
1. Copy the file to the fastboot installation folder in your pc.
2. Then reboot your device into bootloader and quickly connect it to your pc.
3. Run fastboot from your desktop and then type the following without quotes: "fastboot flash recovery cwm6.0.4.9_recovery.img"
4. Instead of writing "cwm6.0.4.9_recovery.img" write the complete file name including extension. For eg. if file name is "twrp_recovery_2" and has extension ".img" then write "fastboot flash recovery twrp_recovery_2.img"
I hope that this solved your problem brother.
Urgent help needed
Harsh862 said:
I have a Motorola Moto E(XT1022). I bought it recently and just when I first started it, I got the 4.4.4 kitkat update and so I downloaded it right away. Then I realised one of the biggest problems of Moto E i.e. 2.2 gb storage. So i dug into find how to install apps on sd card and got to know that you have to root the phone. On xda, I found various ways to root but they were only for the 4.4.2 version of the phone and others were update to 4.4.4 on aldready rooted devices. Please tell me the way to root my device. Also as I am new to this, I dont understand any words like bootloader, fast recovery, etc. Please help me. Thank you in advance.
Edit: Can I use the way given by deej_roamer in his post here:http://forum.xda-developers.com/show....php?t=2755336
Edit: I am sorry to have posted this in the general section. I don't know how to move it now to the questions section. Sorry again.
Click to expand...
Click to collapse
after unlocking moto e....at the time of flashing it gives me error like
error: cannot load 'recovery.img': No error
I have followed every step as mentioned by xda.......i have android 4.4.4 update may be thats why it is not rooting.....
please anyone give me solution....i cant root my phone
please reply as early as possible
thanks
kishorr said:
after unlocking moto e....at the time of flashing it gives me error like
error: cannot load 'recovery.img': No error
I have followed every step as mentioned by xda.......i have android 4.4.4 update may be thats why it is not rooting.....
please anyone give me solution....i cant root my phone
please reply as early as possible
thanks
Click to expand...
Click to collapse
I followed the thread by deej_roamer here http://forum.xda-developers.com/showthread.php?t=2755336
Try out my steps:
[Your phone battery must be at least 75%]
1. First download "Fastboot" from the thread. (Click on the "mfastboot-v2" link in the thread)
2. Next install it in a folder and remember that folder. Also, make sure you select the option of "Create shortcut on Desktop" during installation.
3. Next download CWM recovery from this thread - http://forum.xda-developers.com/moto-e/general/root-moto-e-rooting-flashing-recovery-t2802971 (Click on the "CWM 6.0.4.9 recovery For MOTO E" link in the thread)
4. Copy the "cwm6.0.4.9_recover.img" file to the installation folder of fastboot.
5. Next download SuperSU v2.02 from here - http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip (Click on "UPDATE-SuperSU-v2.02.zip" link)
6. Don't Extract Supersu zip file.
7. Connect phone to pc. Copy the zip file to your internal memory(the directory of int. memory is /sdcard) (The directory for ext. sd card is /storage/sdcard1).
8. Remove your phone from your pc.
9. Switch off your device.
10. Turn on your device by holding power off button and volume down button together for 6-7 seconds. Quickly connect your phone to your pc.
11. The bootloader must be showing usb connected.
12. Run fastboot from your desktop.
13. Now type this (without quotes) - "fastboot flash recovery cwm6.0.4.9_recovery.img"
14. Look at the screen of device. It must be showing "Mismatched partition size (recovery)". It is normal don't worry.
15. Press volume down once (recovery will be selected) and then volume up so that it goes into recovery.
16. It will show the bootloader unlocked warning. Don't worry about it.
17. Your phone should now be in CWM recovery.
18. Don't do anything except what I tell you.
19. In this menu movement is done by the volume rockers ans selection by power button.
20. Press volume down so that "install zip" is selected.
21. Press power button.
22. Select "choose zip from /sdcard". Press power button.
23. Find the SuperSU.zip file(It will probably be in the "0/" folder)
24. It will ask to confirm install. Select Yes.
25. SuperSU will be installed.
26. Select CWM reboot. When you select CWM reboot, it will display "root access possibly lost - Fix?". PLEASE Select "No".
27. Your phone will now reboot. (The bootloader unlocked warning will be shown and then the boot animation).
28. Open your menu(in the phone) and find SuperSu app (a # symbol will be there in its icon).
29. Disconnect your device from the pc.
CONGRATULATIONS YOU HAVE A ROOTED MOTO E.
If you ever wish to flash any other recovery (like twrp),
1. Copy the file to the fastboot installation folder in your pc.
2. Then reboot your device into bootloader and quickly connect it to your pc.
3. Run fastboot from your desktop and then type the following without quotes: "fastboot flash recovery cwm6.0.4.9_recovery.img"
4. Instead of writing "cwm6.0.4.9_recovery.img" write the complete file name including extension. For eg. if file name is "twrp_recovery_2" and has extension ".img" then write "fastboot flash recovery twrp_recovery_2.img"
I hope that this solved your problem brother.
problem successfully resolved
Harsh862 said:
I followed the thread by deej_roamer here http://forum.xda-developers.com/showthread.php?t=2755336
Try out my steps:
[Your phone battery must be at least 75%]
1. First download "Fastboot" from the thread. (Click on the "mfastboot-v2" link in the thread)
2. Next install it in a folder and remember that folder. Also, make sure you select the option of "Create shortcut on Desktop" during installation.
3. Next download CWM recovery from this thread - http://forum.xda-developers.com/moto-e/general/root-moto-e-rooting-flashing-recovery-t2802971 (Click on the "CWM 6.0.4.9 recovery For MOTO E" link in the thread)
4. Copy the "cwm6.0.4.9_recover.img" file to the installation folder of fastboot.
5. Next download SuperSU v2.02 from here - http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip (Click on "UPDATE-SuperSU-v2.02.zip" link)
6. Don't Extract Supersu zip file.
7. Connect phone to pc. Copy the zip file to your internal memory(the directory of int. memory is /sdcard) (The directory for ext. sd card is /storage/sdcard1).
8. Remove your phone from your pc.
9. Switch off your device.
10. Turn on your device by holding power off button and volume down button together for 6-7 seconds. Quickly connect your phone to your pc.
11. The bootloader must be showing usb connected.
12. Run fastboot from your desktop.
13. Now type this (without quotes) - "fastboot flash recovery cwm6.0.4.9_recovery.img"
14. Look at the screen of device. It must be showing "Mismatched partition size (recovery)". It is normal don't worry.
15. Press volume down once (recovery will be selected) and then volume up so that it goes into recovery.
16. It will show the bootloader unlocked warning. Don't worry about it.
17. Your phone should now be in CWM recovery.
18. Don't do anything except what I tell you.
19. In this menu movement is done by the volume rockers ans selection by power button.
20. Press volume down so that "install zip" is selected.
21. Press power button.
22. Select "choose zip from /sdcard". Press power button.
23. Find the SuperSU.zip file(It will probably be in the "0/" folder)
24. It will ask to confirm install. Select Yes.
25. SuperSU will be installed.
26. Select CWM reboot. When you select CWM reboot, it will display "root access possibly lost - Fix?". PLEASE Select "No".
27. Your phone will now reboot. (The bootloader unlocked warning will be shown and then the boot animation).
28. Open your menu(in the phone) and find SuperSu app (a # symbol will be there in its icon).
29. Disconnect your device from the pc.
CONGRATULATIONS YOU HAVE A ROOTED MOTO E.
If you ever wish to flash any other recovery (like twrp),
1. Copy the file to the fastboot installation folder in your pc.
2. Then reboot your device into bootloader and quickly connect it to your pc.
3. Run fastboot from your desktop and then type the following without quotes: "fastboot flash recovery cwm6.0.4.9_recovery.img"
4. Instead of writing "cwm6.0.4.9_recovery.img" write the complete file name including extension. For eg. if file name is "twrp_recovery_2" and has extension ".img" then write "fastboot flash recovery twrp_recovery_2.img"
I hope that this solved your problem brother.
Click to expand...
Click to collapse
Thanks harsh862....it really helped a lot..,. Really thanks
shamps said:
Hi. i am in the same boat as you were. i have a moto e dual sim version running on 4.4.4 out of the box. i have asked around also but havent found a solution.
i have successfully unlocked the bootloader but i have tried n number of times to flash recovery but unsuccessful.
it just doesnt flash, i have tried official and unofficial TWRP and even CWM but i just simply get the recovery to stick.
Could you please tell me how you successfully flash recovery .
thanks in advance!!
Click to expand...
Click to collapse
kishorr said:
after unlocking moto e....at the time of flashing it gives me error like
error: cannot load 'recovery.img': No error
I have followed every step as mentioned by xda.......i have android 4.4.4 update may be thats why it is not rooting.....
please anyone give me solution....i cant root my phone
please reply as early as possible
thanks
Click to expand...
Click to collapse
Is your recovery.img placed in the "C:\Program Files (x86)\Minimal ADB and Fastboot"?
It need to placed in it or you'll get an error.
Boot loader is LOCKED !! cannot be unlocked !! so no root for me ?

Fuhu Nabi 2 won't start or let me select even Recovery Kernel

Hi Guys,
I'm hoping someone can help me here with unbricking my daughters Nabi 2 tablet.
The long story short is that I've tried to update to the latest OTA with TWRP 2.3.3.0 (Nabi 1.9.37) and gapps installed in the past (in order to have google play services).
After downloading the OTA and successfull file verification it booted into TWRP mode and this is when things went wrong...
As I wasn't sure about how to even leave the TWRP mode I have hit few things by accident (I think one of them asked me if I want to wipe my ROM and I said YES + when I was after that trying to reboot the tablet it gave me a warning saying something like "you have no OS installed - are you sure to reboot?).
Now, of course due to my stupid actions it doesn't work - stuck on Nabi boot logo and when I try to pres Volume+ and Power together it gives me the screen with 4 options to choose from (Boot Normally, Fastboot Protocol, Recovery Kernel, Forced Recovery) but I still can't select/move the highlighted item. All what I'm able to do now is to power it off by holding the power button pressed for couple seconds.
Based on your experience here - is there anything that can be done or is it a "real brick" and we need to buy something new for her?
Thank you for any suggestions.
Hi,
I managed to boot into TWRP somehow...
Could someone please direct me how I can re-flash it with a Nabi 2 UK OS (and where I can source the file from if possible at all)?
Cheers,
T1000
termostat1000 said:
Hi,
I managed to boot into TWRP somehow...
Could someone please direct me how I can re-flash it with a Nabi 2 UK OS (and where I can source the file from if possible at all)?
Cheers,
T1000
Click to expand...
Click to collapse
Try sections 9 and 10. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Hi,
Using NabiLab I managed to load stock 1.9.37 through TWRP.
At the moment tablet will start, let me through the initial setup wizard and go into normal mode from when it was new (no Google services available).
When I try to install gapps (TWRP mode) using NabiLab it goes into endless boot loop showing just a splash screen of the screen lock and reloads again.
I tried also bringing it more to factory condition but it is not recognised in NabiLab when android is fully booted (even though PC can see it). I tried different drivers but without too much luck. When in TWRP mode it comes up as Alcatel ADB Device and when adroid is booted it comes up as a storage device rather than ADB.
I feel I'm pretty close but I need just a hint how to solve it finally without bricking it for real...
Cheers
T
termostat1000 said:
Hi,
Using NabiLab I managed to load stock 1.9.37 through TWRP.
At the moment tablet will start, let me through the initial setup wizard and go into normal mode from when it was new (no Google services available).
When I try to install gapps (TWRP mode) using NabiLab it goes into endless boot loop showing just a splash screen of the screen lock and reloads again.
I tried also bringing it more to factory condition but it is not recognised in NabiLab when android is fully booted (even though PC can see it). I tried different drivers but without too much luck. When in TWRP mode it comes up as Alcatel ADB Device and when adroid is booted it comes up as a storage device rather than ADB.
I feel I'm pretty close but I need just a hint how to solve it finally without bricking it for real...
Cheers
T
Click to expand...
Click to collapse
Pretty hard to brick a Nabi2.
Why did you choose 1.9.37? Isn't the latest 2.3.2 and already has Gapps?
When in Android do you have ADB turned on in Developer options?
Is this the procedure you used?
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Restore tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
aicjofs said:
Pretty hard to brick a Nabi2.
Why did you choose 1.9.37? Isn't the latest 2.3.2 and already has Gapps?
When in Android do you have ADB turned on in Developer options?
Is this the procedure you used?
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Restore tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
Click to expand...
Click to collapse
Hi aicjofs,
I followed the steps above except step c which I haven't done.
So it looked good with the NabiLab built in 1.9.37 and it seemed to load fine with my TWRP 2.3.3.0 but it was hgoing into this endless boot loop after trying to install gapps. BTW I went for 1.9.37 as it came with NabiLab and turned right.
After your reply I've donwloaded the 232UK stock rom and bootloader. Copied both onto SD card - at that stage it would let me do a restore directly from the SD card so I've copied the 232UK rom into internal memory. Restore process went OK and at the end I've installed its dedicated bootloader...
Right now the situation is that I can only boot into TWRP but restore doesn't show any available roms (both internal or external memory) even though there is backup folder on the SD card.
What worries me the most is when I go to advanced / file manager / sdcard (internal memory) in TWRP mode it doesn't show any files or folders there. When I try to dipslpay tablet information in NabiLab it shows the external SD card properties properly (capacity/free space) but on the internal memory it says "Size df:KB Free can'tKB used find".
Does it mean it has wiped all the internal memory down to zero? Would this be the reason for recovery no being able to identify the roms on external SD card too?
Looking at the log in TWRP mode it is filled with entries like
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Can't open /cache/recovery/last_install
E:Can't open (No such file or directory)
What a pain is this thing, honestly...
termostat1000 said:
Hi aicjofs,
I followed the steps above except step c which I haven't done.
So it looked good with the NabiLab built in 1.9.37 and it seemed to load fine with my TWRP 2.3.3.0 but it was hgoing into this endless boot loop after trying to install gapps. BTW I went for 1.9.37 as it came with NabiLab and turned right.
After your reply I've donwloaded the 232UK stock rom and bootloader. Copied both onto SD card - at that stage it would let me do a restore directly from the SD card so I've copied the 232UK rom into internal memory. Restore process went OK and at the end I've installed its dedicated bootloader...
Right now the situation is that I can only boot into TWRP but restore doesn't show any available roms (both internal or external memory) even though there is backup folder on the SD card.
What worries me the most is when I go to advanced / file manager / sdcard (internal memory) in TWRP mode it doesn't show any files or folders there. When I try to dipslpay tablet information in NabiLab it shows the external SD card properties properly (capacity/free space) but on the internal memory it says "Size df:KB Free can'tKB used find".
Does it mean it has wiped all the internal memory down to zero? Would this be the reason for recovery no being able to identify the roms on external SD card too?
Looking at the log in TWRP mode it is filled with entries like
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Can't open /cache/recovery/last_install
E:Can't open (No such file or directory)
What a pain is this thing, honestly...
Click to expand...
Click to collapse
My fault. I forgot to tell you once you update the bootloader you need to use TWRP for Jellybean, you are still using TWRP for Ice Cream Sandwich .
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
At that point you can try to restore the 2.3.2 ROM again. Or try the 2.2 ROM http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
aicjofs said:
My fault. I forgot to tell you once you update the bootloader you need to use TWRP for Jellybean, you are still using TWRP for Ice Cream Sandwich .
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
At that point you can try to restore the 2.3.2 ROM again. Or try the 2.2 ROM http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
Click to expand...
Click to collapse
Forgive me please but I'm not entirely sure how to load this TWRP 2.8.5 for JellyBean on it with TWRP 2.3.3.0 in place..
Cheers
termostat1000 said:
Forgive me please but I'm not entirely sure how to load this TWRP 2.8.5 for JellyBean on it with TWRP 2.3.3.0 in place..
Cheers
Click to expand...
Click to collapse
You will need to use fastboot to load it. If you have a nabilab folder it already has fastboot available. So using the procedure below you couldn't download the ZIP file I linked in post above. Extract the from the zip the recovery.img or twrp-recovery.img and put it in the nabilab folder. (Im puling the procedure from http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 )
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
aicjofs said:
You will need to use fastboot to load it. If you have a nabilab folder it already has fastboot available. So using the procedure below you couldn't download the ZIP file I linked in post above. Extract the from the zip the recovery.img or twrp-recovery.img and put it in the nabilab folder. (Im puling the procedure from http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 )
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
Click to expand...
Click to collapse
Hi,
Thank you very much for your help but it clearly looks that this is way beyond my knowledge on how to use all of these fastboot, command, adb and so on...
I regret I ever touched the thing at all.
So there is absolutely no easy way - command line is a must from where I am right now?
termostat1000 said:
Hi,
Thank you very much for your help but it clearly looks that this is way beyond my knowledge on how to use all of these fastboot, command, adb and so on...
I regret I ever touched the thing at all.
So there is absolutely no easy way - command line is a must from where I am right now?
Click to expand...
Click to collapse
Its not a must but easiest to try and walk you through. Which version of Nabilab are you using? You could move some files around and still use Nabilab. Up to you which way to go forward. I'll try and help.
aicjofs said:
Its not a must but easiest to try and walk you through. Which version of Nabilab are you using? You could move some files around and still use Nabilab. Up to you which way to go forward. I'll try and help.
Click to expand...
Click to collapse
Hi,
I'm not so much afraid of copy/paste for cmd... the biggest fear is that I don't know anything about ADB, fasboot etc. So when your instruction in previous post says use ADB and I purely don't know what it means.
I think if the option is there I'd like to ask if you could help with restoring it with Nabilab.
Thanks a million for your help!
T
termostat1000 said:
Hi,
I'm not so much afraid of copy/paste for cmd... the biggest fear is that I don't know anything about ADB, fasboot etc. So when your instruction in previous post says use ADB and I purely don't know what it means.
I think if the option is there I'd like to ask if you could help with restoring it with Nabilab.
Thanks a million for your help!
T
Click to expand...
Click to collapse
Which version of Nabilab are you using? Is it the commandline version. Black window, where you have to use keyboard to make selections?
aicjofs said:
Which version of Nabilab are you using? Is it the commandline version. Black window, where you have to use keyboard to make selections?
Click to expand...
Click to collapse
Hi,
I'm using Nabilab ver 2 - black windows with keyboard made selections.
termostat1000 said:
Hi,
I'm using Nabilab ver 2 - black windows with keyboard made selections.
Click to expand...
Click to collapse
Find the Nabilab folder on your computer. Open the "recovery" folder. Then open the "stock" folder. Inside it there is recovery.img file. Rename it to recoverystock.img.
You downloaded the twrp-recovery-JBNV7AUS.zip from a few posts back. Extract the twrp-recovery.img file and put it in the stock folder. Now rename the twrp-recovery.img file to recovery.img.
Now boot the tablet to TWRP recovery(the one that isn't working) and run Nabilab. Select 4 Install recoveries. Then 4 instal stock recovery. Then reboot in to recovery and see if you have the 2.8.5 recovery
aicjofs said:
Find the Nabilab folder on your computer. Open the "recovery" folder. Then open the "stock" folder. Inside it there is recovery.img file. Rename it to recoverystock.img.
You downloaded the twrp-recovery-JBNV7AUS.zip from a few posts back. Extract the twrp-recovery.img file and put it in the stock folder. Now rename the twrp-recovery.img file to recovery.img.
Now boot the tablet to TWRP recovery(the one that isn't working) and run Nabilab. Select 4 Install recoveries. Then 4 instal stock recovery. Then reboot in to recovery and see if you have the 2.8.5 recovery
Click to expand...
Click to collapse
Great!
Your trick worked fine and now I can see TWRP 2.8.5.0 and I have problems with drivers - keeps failing to recognize the tablet.
I'll work on the driver issue or is there something I should know about it with TWRP 2.8.5.0 lodaed?
What is my next step from here as Android is still stuck on Nabi logo (no motion) and I'm afraid to do anything in case I create even bigger mess than I already have
I also noticed when I try to shut it down from inside TWRP it asks me a question if I want to root the tablet (Install super SU) - is it something I should do and at what stage?
Thanks!
T
termostat1000 said:
Great!
Your trick worked fine and now I can see TWRP 2.8.5.0 and I have problems with drivers - keeps failing to recognize the tablet.
I'll work on the driver issue or is there something I should know about it with TWRP 2.8.5.0 lodaed?
What is my next step from here as Android is still stuck on Nabi logo (no motion) and I'm afraid to do anything in case I create even bigger mess than I already have
I also noticed when I try to shut it down from inside TWRP it asks me a question if I want to root the tablet (Install super SU) - is it something I should do and at what stage?
Thanks!
T
Click to expand...
Click to collapse
If you can see the files again now with the correct TWRP. You can try to restore the 2.3.2 ROM again. Or maybe try the procedure from post #5 with the 2.2 ROM I linked to in post #7. You don't have to do the bootloader install anymore so skip that step. Installing root doesn't matter, you can choose to install or not.
aicjofs said:
If you can see the files again now with the correct TWRP. You can try to restore the 2.3.2 ROM again. Or maybe try the procedure from post #5 with the 2.2 ROM I linked to in post #7. You don't have to do the bootloader install anymore so skip that step. Installing root doesn't matter, you can choose to install or not.
Click to expand...
Click to collapse
You're a STAR!
All happy working as new with 232UK ROM and bootloader loaded with your instructions.
I'd never get this sorted without your specialized help.
If I only could I'd send you something just to say Thank You...
T - Happy Dad of Amelia
termostat1000 said:
You're a STAR!
All happy working as new with 232UK ROM and bootloader loaded with your instructions.
I'd never get this sorted without your specialized help.
If I only could I'd send you something just to say Thank You...
T - Happy Dad of Amelia
Click to expand...
Click to collapse
Your thanks is enough Glad we got it sorted and a happy kid!

Categories

Resources