{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Clockwork-mod recovery for Motorola XT530/531 and XT532.
Code:
You've already messed up with your phone.
Now if something happens don't point your finger to me.
All I can do is to laugh at you, as loud as possible.
So always keep in mind that you do changes by your choice.
Thank YOU
After 7amdoun's successful finish on fixing bootmenu bugs, I proudly present the easiest way to have bootmenu on these phones.
First of all check out that you have all the things required :
1. A Motorola XT530/XT531 or XT532.
2. Must be rooted.
3. If you don't know how to root. Check out here [Thanks to 008Rohit]
4. A PC.
If you are done with above things you can proceed further.
There are two ways to get bootmenu on your device
First
Steps are very simple :
1. Just download "Bootmenu_v2.0.2.zip" and extract it.
2. Double Click "Bootmenu Installer.bat"
3. And follow the onscreen instructions.
Second:
[Special thanks to andrewidya for making the .apk]
Either refer to the installation video made by andrewidya
OR
This is easier way, you ought to have busybox installed:
1. Download the "Recovery Installer_1.0.apk" file from the attachment.
2. Install it on your phone.
3. Open "Recovery Installer" from App drawer
4. Tap "Install Recovery"
5. You've CWM installed.
You are DONE
Congratulations, You are now having Custom Recovery in your phone.
Using Bootmenu:
Turn Off your phone.
Switch on the phone. While you see the "M" logo the soft buttons leds will light up.
Be quick enough to press the Volume down(-) button as you see the leds being lighted.
Click to expand...
Click to collapse
Touch will not work in bootmenu.
Use volume keys to navigate and power key to select.
Special Thanks and credits to:
Gentrylamp for creating bootmenu.
7amdoun for his great knowledge and fixing all the bugs in bootmenu.
andrewidya for making the installation simple with a simple .apk.
Mazen.kh for everything he did.
Mr.Indigo for giving us hopes.
And all other members whom I forgot to mention here.
Click to expand...
Click to collapse
If you face any problem you can ask me anytime.
Wait... Where are you going? Downloading ...??
Please don't forget the Thanks button.
And please go and thank other members also, it wouldn't have been possible without them.[/B]
Change log:
Code:
Bootmenu 1.1.5 : Was only available for testing.
Bootmenu 2.0 with CWM 6.
Bootmenu 2.0 with CWM 6 Backup bug fixed (Thanks to 7amdoun)
Bootmenu 2.0 with CWM 6 Restore bug fixed.
Bootmenu 2.0.2 with CWM 5 Most of the bugs fixed.
Made Installing the bootmenu simpler than ever with Installer script v1.0.
Installer script v1.0.2 with no requirement of busybox or Pimp My Rom.
Installer script v2.0.0. Removed bug of contradiction with other apps.
Apk made by andrewidya for simpler installation
CWM 6 flashable available in attachment
CWM recovery for fire xt
Hi, I did everythng as mentioned but aftr reboot i didnt get any recovery mode instead normal screen turned up and phone wrkd as normal..
plz suggest wat to do..
Recheck from up to down.
And please redownload the the attachment that 97bootmenu had some mistake before
Hey aweosomeabhijeet,
Can you develop a cwm for Motorola Defy Mini XT320 as I don't know how to port it.
rootdefyxt320 said:
Hey aweosomeabhijeet,
Can you develop a cwm for Motorola Defy Mini XT320 as I don't know how to port it.
Click to expand...
Click to collapse
Give your recovery dump.
Or you can do it on your own it's too simple.
1. Dump your recovery
2. Go to builder.clockworkmod.com
3. upload the img there.
Have some tea or coffee and it will get ready soon.
Download the files and you are done.
CWM recovery for fire xt
I falashed my phone with XT531 SBF from Brazil, will dat make any difference?? my phone is shown as XT531 in info..
varun1989 said:
I falashed my phone with XT531 SBF from Brazil, will dat make any difference?? my phone is shown as XT531 in info..
Click to expand...
Click to collapse
Only that service center people will not accept it if you are not from brazil. And network switching might have problems.
Sent from my XT530 using xda app-developers app
can u upgrade kernal or not
Here's a slightly improved bootmenu (with one important variable fix for the XT530).
Try selecting 2nd-init in bootmenu and tell me what happens.
BTW, are you able to unmount /system partition once you load CWM?
7amdoun said:
Here's a slightly improved bootmenu (with one important variable fix for the XT530).
Try selecting 2nd-init in bootmenu and tell me what happens.
BTW, are you able to unmount /system partition once you load CWM?
Click to expand...
Click to collapse
I didn't tried but was able to flash zip(s).(see the video)
I think while flashing it did unmounting /system
Sent from my XT530 using xda app-developers app
yup tried it 2 times but phone starts normally
aweosomeabhijeet said:
I didn't tried but was able to flash zip(s).(see the video)
I think while flashing it did unmounting /system
Sent from my XT530 using xda app-developers app
Click to expand...
Click to collapse
There is a manual option somewhere in CWM to unmount /system. Try it and see if it works.
Also, using the new bootmenu I uploaded, try selecting 2ni-init and see if phone boots normally (without ADB).
7amdoun said:
There is a manual option somewhere in CWM to unmount /system. Try it and see if it works.
Also, using the new bootmenu I uploaded, try selecting 2ni-init and see if phone boots normally ie. into OS instead of bootmenu.
Click to expand...
Click to collapse
I also tried it before . It didn't worked. The phone gets stucks at bootlogo
Error ! unmounting /system
BTW, andrewidya figured out how to get the normal OS to boot without ADB , he needs some time.
And he is building installer script for bootmenu
Edit : Why people are not able to boot in bootmenu? Have I done something wrong?
vishal.kulkarni30 said:
yup tried it 2 times but phone starts normally
Click to expand...
Click to collapse
Did you set the permissions correctly?
one doubt!
aweosomeabhijeet said:
Hey Guys
All your wait is over.
Here I'll tell you how to get CWM for Moto Fire XT.
Disclaimer : I'm not responsible for any damage to your phone. I have tried it and finished successfully.
Try only if you know little bit about android.
Required things
1. Rooted Fire XT
2. Pc
Download these things on your phone:
1. Terminal emulator
2. Busybox(Open it and install)
3. Root browser
4. Pimp my Rom
You can find all of them in the Play Store.
If you have done with it download the attachment.
Now main work.
It is not easy though but I think everyone can do it.
Steps:
1. Extract the attachment and copy it to your sdcard
2. Mount /system as RW.
3. Open Root Browser and copy bootmenu folder from sdcard/XT530 and paste it in /system.
4. Open /system/bin and locate to logwrapper
5. Rename it as logwrapper.bin
6. Open Terminal Emulator and type:
Code:
su
ln -s /system/bootmenu/binary/bootmenu /system/bin/logwrapper
sync
exit
exit
7. Open Pimp My Rom and Add universal init.d support.
8. Copy /sdcard/XT530/97bootmenu and paste it in /system/etc/init.d .
9. Change permissions of 97bootmenu to rwx r-- r--
10 . Reboot your phone.
Now your phone will start at bootmenu.
Select Recovery>Custom Recovery
PS: If you want to get back the phone to boot normally. Just connect it to PC, open CMD and type
cd path-to-adb.exe
adb shell
rm -R /system/etc/init.d/97bootmenu
exit
adb reboot
I succeeded here's the video:
http://youtu.be/OyHwMqkBArk
Sorry for poor camera quality.
Thanks to all the members.
Special Thanks to:
Gentrylamp for creating bootmenu.
7amdoun for his great knowledge and modding bootmenu for XT530.
andrewidya for correcting me at every point.
Mazen.kh for everything he did.
Mr.Indigo for giving us hopes.
And all other members whom I forgot to mention here.
If you face any problem you can ask me anytime.
Now I'm building a custom Rom and will finish soon.
Give your ideas to make it look better.
Wait... Where are you going? Downloading ...??
Please don't forget the Thanks button.
And please go and thank other members also, it wouldn't be possible without them.
Click to expand...
Click to collapse
after d last step when i rebooted...my mob booted as normal...it didnt show any recovery mode...
Ok everybody I think 97bootmenu is the problem.
Solution :
Create 97bootmenu manually.
Steps:
1.Open /system/etc/init.d
2. Create a file, name it 97bootmenu.
3. Open the file as text
Type:
Code:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
4. repair permissions.
5. Restart your phone and tell me the situation.
how!?
i tried ... same situation. .
krishnak1 said:
i tried ... same situation. .
Click to expand...
Click to collapse
Okk I will figure out what's the problem?
And will release it correctly soon.
CONFIRMED WORKING ON XT535 currently backing up Via CWM. Backup complete. Problems are: have no backlight in CWM. when scrolling down with the volume keys the text moves across to the middle. Many thanks guys! info: /system/ is not manually unmountable in CWM, and selecting 2nd init on recovery, the phone hangs at the boot. Be sure to check correct permissions mine didnt work the first time because of perms on 97bootmenu
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Cool.
To Everybody
Don't forget to change the permissions please.
Related
http://forum.xda-developers.com/showpost.php?p=6763690&postcount=1246
This is a remake of the original post by Koush. Much thanks to him and everyone for the work on root'ing. The original post has not been updated in recent days so I started a new thread with new instructions.
OLD METHOD
G1 RC*/CRC*/DRC* (phone is OFF)
ON YOUR PC
1. Download the DREAIMG-RC*.zip
US-DREA100 http://android.lucidrem.us/_fd.php?file=files/howto-root/DREAIMG-RC29.zip
EU-DREA110 http://android.lucidrem.us/_fd.php?file=files/howto-root/DREAIMG-RC7.zip 2. Extract DREAIMG.nbh to SD FAT32
3. Download the recover_testkeys.img
http://android.lucidrem.us/_fd.php?file=files/howto-root/recovery_testkeys.img 4. Copy recovery_testkeys.img to SD FAT32
5. Download the TheOfficial TMO_OTA_DRC83/92
US http://android.lucidrem.us/_fd.php?file=files/enomther/USA/DRC83/update.zip
EU http://android.lucidrem.us/_fd.php?file=files/enomther/EUR/DRC92/update.zip 6. Copy update.zip to SD FAT32
ON YOUR G1
1. Put SD in the G1 - Hold CAMERA + POWER
2. Press POWER to INSTALL
3. When COMPLETE Click TRACKBALL
4. Hold GREEN + MENU + RED -> REBOOT
5. GoTo Home -> Apps -> Market -> Telnet -> INSTALL
6. GoTo Home -> Type [enter]telnetd[enter]
7. GoTo Home -> Apps -> Telnet -> Connect
8. Type id[enter] -> "uid=0(root) gid=0(root)"
9. Type mount -o rw,remount /dev/block/mtdblock3 /system[enter]
10. Type dd if=/system/bin/sh of=/system/bin/su[enter]
11. Type chmod 4755 /system/bin/su
12. GoTo Home -> Apps -> Market -> Terminal Emulator -> INSTALL -> RUN
13. Type su[enter] -> #
14. Type cat /sdcard/recovery_testkeys.img > /system/recovery.img[enter]
15. Type flash_image recovery /system/recovery.img[enter]
16. Press POWER -> OFF
17. Hold HOME + POWER -> Hold ALT + S -> INSTALL
18. Hold HOME + BACK -> REBOOT
You can download the text file here:
http://android.lucidrem.us/files/howto-root.txt
NEW METHOD - (does not work on v1.6/DRC*) - Wow. I am reposting this info from another source:
This is an automatic root process. Load a new recovery image and load a ROM with some simple clicks.
1. Download these to the SD:
http://android.lucidrem.us/_fd.php?file=files/howto-root/flashrec-20090904.apk
http://android.lucidrem.us/_fd.php?file=files/howto-root/recovery-RA-dream-v1.4.0.img
USA http://android.lucidrem.us/_fd.php?file=files/enomther/USA/DRC83/update.zip
EUR http://android.lucidrem.us/_fd.php?file=files/enomther/EUR/DRC92/update.zip 2. Use ASTRO to install the APK file. -> Run the program.
3. Click to BackUp your current recovery.
4. Type "/sdcard/recovery-RA-dream-v1.4.0.img" into the text box. -> Click "Flash Custom Recovery Image" (unless you want Cyan)
5. Boot into the recovery screen and flash the new update.zip file.
You now have root access and you did not have to wipe.
Now you will be able to reboot into the recovery screen and flash any ROM.
Try it. You'll like it. Works on G1 and myTouch.
GET ASTRO HERE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sources:
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
http://forum.xda-developers.com/showthread.php?t=553537
Creator - Zinx Verituse:
http://zenthought.org/content/project/flashrec
http://code.google.com/p/flashrec/
...but is it -too- simple?
Nice job
5. Download the TMO_OTA_CRC1
US http://android.lucidrem.us/_fd.php?f...RC1/update.zip
EUR http://android.lucidrem.us/_fd.php?f...RC1/update.zip
ERROR: download file NOT SPECIFIED. USE _fd.php?file=filepath
these links don't work for me. Are there any mirrors for these?
Fixed Hyperlink
fragske said:
5. Download the TMO_OTA_CRC1
US http://android.lucidrem.us/_fd.php?f...RC1/update.zip
EUR http://android.lucidrem.us/_fd.php?f...RC1/update.zip
ERROR: download file NOT SPECIFIED. USE _fd.php?file=filepath
these links don't work for me. Are there any mirrors for these?
Click to expand...
Click to collapse
my apologies .. i mistyped the link .. fixed now
Touch Screen Root Process
Wow. I am reposting this info from another source:
This is an automatic root process. Load a new recovery image and load a ROM with some simple clicks.
http://android.lucidrem.us/_fd.php?file=files/howto-root/recovery-rav1.2.1g.img
http://android.lucidrem.us/_fd.php?file=files/howto-root/flashrec-20090815.apk
Download these two files to the phone. Install the APK with ASTRO. Flash the custom image by typing it into the text box. Done. Now you will be able to reboot into the recovery screen and flash any ROM. Try it. You'll like it. Works on G1 and myTouch.
Sources:
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
http://forum.xda-developers.com/showthread.php?t=553537
How do I know if I have root?
I tried the new method, and everything seemed to go through without glitches. Is there any way I can verify that I have gained root access?
Thanks.
sevakm said:
I tried the new method, and everything seemed to go through without glitches. Is there any way I can verify that I have gained root access?
Thanks.
Click to expand...
Click to collapse
Type su in Terminal Emulator. If you get a # then you have root. Anything else then no.
LucidREM, fantastic work. I think people need this tut because they have a hard time reading the originals. And my thoughts the gods should be pleased
It wouldnt let me install the flash recovery apk. I followed the directions to the letter.
ThR1LL said:
Type su in Terminal Emulator. If you get a # then you have root. Anything else then no.
Click to expand...
Click to collapse
Thanks. It works!
Also thanks a lot to LucidREM for posting this. I kept trying to do it the old way, but without any success.
ASTRO
jacknmary said:
It wouldnt let me install the flash recovery apk. I followed the directions to the letter.
Click to expand...
Click to collapse
what was the response when it was installing? how did you attempt the install?
Can I use...
Cyanogen's 1.4 img instead...
Or at the very least... reflash to cyanogen's 1.4 img after I follow the "new" method in the first post?
Thanks,
Adam
Recovery Image
djfreaq said:
Cyanogen's 1.4 img instead...
Or at the very least... reflash to cyanogen's 1.4 img after I follow the "new" method in the first post?
Thanks,
Adam
Click to expand...
Click to collapse
absolutely .. the cyan 1.4 is actually the default recovery in the APK that you download .. however .. it is not 100% compatible with all phones .. the newer recovery image from RA is good for G1 and myTouch as well .. the recovery is actually very nice and you should still be able to use cyan's ROM with a different recovery image
LucidREM said:
absolutely .. the cyan 1.4 is actually the default recovery in the APK that you download .. however .. it is not 100% compatible with all phones .. the newer recovery image from RA is good for G1 and myTouch as well .. the recovery is actually very nice and you should still be able to use cyan's ROM with a different recovery image
Click to expand...
Click to collapse
Fantastic. Music to my ears.
I've been a little more cautious recently, since my late G1 met it's demise... I somehow managed to fry the boot-loader. It's actually hilarious reading other posts on here because some people are so adamant about how it's impossible to brick the G1... well trust me. I did.
Anyway, thanks Lucid, I'll be trying your little method when my phone arrives Friday.
OH and just to double check. No need to revert to RC29 to make this work? I can have any factory-tmobile-out-of-the-box ROM on my phone and the NEW method will do the trick?
Again,
Thanks
Still not working.
Build Number:
1.56.73.2 PLAT-1.0_gms-135348 CL#11526 release-keys, so it's none of those two versions , and as I said before, not even the boot screen isn't the same ( Camera button+power)
Hope this helps, and i get a solution to my problem :-<
Found the topic that's dedicated to this version of the dream thanks anyway.
jacknmary said:
It wouldnt let me install the flash recovery apk. I followed the directions to the letter.
Click to expand...
Click to collapse
Go to Setting -> Applications -> allow unknown sources
This is sort of a given considering you're installing an apk from an untrusted source (ie, not the Market).
Woks For Me!!!
Worked flawlessly... Now to find a Rom... Thanks A Lot!!!
Noob question...my G1 is already rooted, I want to install the cyanogenMod...how do I do that?
obliquefx said:
Noob question...my G1 is already rooted, I want to install the cyanogenMod...how do I do that?
Click to expand...
Click to collapse
if you have root you can just flash cyan's file to the phone .. boot into the recovery screen and ALT+S
Do you think you could make a guide on how to flash hero using the one click root method.
This thread is for discussion for the development of this device. All interested devs are very welcome to join and help.
I started working on this device since I got it day 1 on March 11, 2013. Slowly, I progressed to every step in learning more about this device. Since then, many have joined finding ways to make this device better.
UPDATE:
This thread is old and very few to none uses this device anymore. I will leave this thread here for your reference.
All of the developments of this device will still be posted here so always keep in touch with this thread for great news.
Cheers! :good:
Unbrick theory...
trying the one touch upgrade utility. it wipes all data in phone and installs a fresh and latest ROM for the device. i guess this will also fix a bricked device somehow.
after this i will try to root it again using MTK tools and ap flash tools with a different idea in my mind... hope it works this time...
[EDIT] UNBRICK METHOD CONFIRMED WORKING!!!
One touch Upgrade
Hello there I'm a total noob in rooting and unlocking bootloads. I just got the same phone as my first android phone and wondered how to root it and I end up here. Now I'm asking how did you get the one touch upgrade software. I've searched the whole alcatel website but I keep getting on the FAQ page. Would you be so kind to put up the link for the software because I kinda bricked my phone here. I was also wondering what speed did you use during your Bin4ry script root attempt? Normal or Special? Keep doing a good job. Thanks for having the time to look for ways to root this phone.
sabinbp said:
Hello there I'm a total noob in rooting and unlocking bootloads. I just got the same phone as my first android phone and wondered how to root it and I end up here. Now I'm asking how did you get the one touch upgrade software. I've searched the whole alcatel website but I keep getting on the FAQ page. Would you be so kind to put up the link for the software because I kinda bricked my phone here. I was also wondering what speed did you use during your Bin4ry script root attempt? Normal or Special? Keep doing a good job. Thanks for having the time to look for ways to root this phone.
Click to expand...
Click to collapse
I tried the normal mode as Bin4ry said that the others might brick the phone it it wasn't the right model. did you brick it using the srcipt? any way. still trying to root it and finding help from rua1 that has a great knowledge in MTK phones...
here's the link of the upgrade utiliuty... just install it and choose alcatel 4030 (if your phone is s'pop) then power of the phone remove the battery and follow the instructions on PC and wait till it says plug the phone while powered off.. plug the usb (without battery) then wait for it to detect the device. when it loads, put the battery back and wait for it to download the firmware.. it will take hours to download it.. it's about 2+gigs... good luck on unbricking.. hope it works...
Phone unbricked
Many thanks for the software. My phone is now back to stock rom. for the Bin4ry I also tried Normal because I thought it was for tabs only. So MTK is the only course of action? Any news on fixing the 2 point horizontal bug? and the alcatel FAQ says there's this TCL calibration that you can activate to you know "calibrate" the touch screen. Do you also get the problem where in the stock alarm app alarms but you can't dismiss it ( I set it to crazy mode ) where you need to press 3 buttons to dismiss but still won't stop I really need to pull the battery out. Help please Thanks in advance.
sabinbp said:
Many thanks for the software. My phone is now back to stock rom. for the Bin4ry I also tried Normal because I thought it was for tabs only. So MTK is the only course of action? Any news on fixing the 2 point horizontal bug? and the alcatel FAQ says there's this TCL calibration that you can activate to you know "calibrate" the touch screen. Do you also get the problem where in the stock alarm app alarms but you can't dismiss it ( I set it to crazy mode ) where you need to press 3 buttons to dismiss but still won't stop I really need to pull the battery out. Help please Thanks in advance.
Click to expand...
Click to collapse
Great. So my theory really worked. Glad you unbricked it. I'm getting closer to rooting it. Just having problems flashing the cwm. Ones I managed to flash it, rooting may be successful. I use Mtk tools and flash tools and get help from rua1. Didn't use my alarm before so i'm not sure about the bug. Maybe you don't have to set it in crazy mode..
I tried to set the alarm in crazy mode and everything works fine. Just dismiss, unlock, and tap the three buttons with numbers and your done..
Rooted, finally!!
I finally rooted the alcatel spop. I will make a guide maybe later how I did it...
[GUIDE]How to flash CWM recovery and root Alcatel One Touch S'POP 4030
How to flash CWM recovery and root Alcatel One Touch S'POP 4030X(Glory 2)
Disclaimer: Your warranty is now void. You do this in your own risk. I do not take any responsibility to your device. This will definitely brick your device which is normal but follow the right instructions to make it work again.
Credits: This is tuts would not be possible without the help from the creator of MTKdroid tools, rua1 from XDA Developers. Thank the guy for his wonderful tool. If you wanna know how I did it, go to his thread right here. I also wanna acknowledge The Solutor and rimmon1971's efforts for porting the TWRP to our device. You can find The Solutor's work here.
Requirements:
1. A windows based PC
2. MTK Droid Root & Tools & SP Flash Tool
3. Universal ADB driver
4. One Touch Upgrade S
5. Root script
6. Patience
7. Most important! Use your brain!
Important!
To make this work without errors, don't use other drivers available in the web. Just install One Touch Upgrade S first. It will install the USB VCOM preloader driver. It will be needed by the SPFT to detect the phone. Use the provided ADB driver for the MT65xx_android_phone. If ever you get stucked in an error and your device wont boot anymore, just use One Touch Upgrade and your phone will be as good as new...
Guide: CWM/TWRP recovery
1. Download MTK Droid Root & Tools & SP Flash Tools, ADB Drivers, One Touch Upgrade S, and the Root script. Extract them anywhere in your computer.
2.Install ADB driver.This step is now optional to get adb working. You can now skip to step 5 if you just want to get rooted with CWM/TWRP recovery installed.. In your phone, go to Settings>Development. Set to on and check USB debugging.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Connect device to PC. Driver will fail to install (thats normal). Install UniversalAdbDriverSetup6.msi
Note: in Windows 8, this will pop-up. do this:
4. After installing the Universal ADB driver, go to device manager of your computer. Follow the images as descirbed.
ADB commands should work now (if you have ADB installed) and you won't have any problems about MTK droid tool not detecting phone.
5. Be sure that you have already installed One Touch Upgrade S before this step. Open SP Flash tool and select the scatter file by clicking on the Scatter-loading button.
6. UNCHECK BOOT and leave RECOVERY checked. Disregard what is on the photo. There's are reports that the latest firmwares are incompatible with the uploaded patched boot.img.
Note: By default, the CWM recovery will be selected in the SP Flash tool. If you want the fully working TWRP-recovery (I recomment this because CWM recovery is not fully functional), just click RECOVERY and replace it with this file.
7. Click Download button. Click yes on the download warning. Turn off phone, remove battery and connect the phone (without battery) and wait until SP Flash tool detects the phone and watch as it flash the image.
8. If everything passes without errors, unplug the phone, reinsert battery and boot to recovery by pressing power + volume up.
9. You should boot in CWM/TWRP recovery. We are ready to flash the Superuser app to gain root.
Guide: Superuser
You can use mtk droid root and tools here. Just plug in phone to pc while still in CWM recovery. Run mtk tools, wait to detect phone, click superuser, then build.prop, then delete china. Your done. Or use the guide below if you have problems with it.
Using CWM recovery to flash superSU
1. While still on CWM recovery, plug the phone into PC again.
2. Navigate using volume up and down buttons. Press Power button to select and Back soft key to go back.
3. Select mounts and storage>mount USB storage.
4. Copy the root-glory-2-4030E.zip to your sdcard.
5. After copying, select unmount and go back.
6. Select install zip from sdcard>choose zip from sdcard>root-glory-2-4030E.zip and select yes - Install root-glory-2-4030E.zip
7. It will flash the app to the system including all needed binaries. I also included the fix-permissions banary which is missing from the ROM.
8. Reboot the phone and wait. It will boot normally and no data will be lost. You will see superuser app in your app drawer. You are now rooted!:thumbsup:
Using TWRP recovery to flash superSU
1. While still on TWRP recovery,Connect the device to PC.
2. Tap mount in the screen then Mount USB storage.
3. Copy the root-glory-2-4030E.zip to your sdcard.
4. Press back on your device softkeys.
5. Tap install and select root-glory-2-4030E.zip
6. Wipe to confirm flash.
7. Reboot>System.
8 You're done.
Screenshots:
Guide to Unroot
Requirements:
1. Windows Based PC
2. SP flash tool (included in OT-4030 ROOT&CWM RECOVERY)
3. Stock recovery.img
4. Unroot script (Unroot-glory-4030E.zip)
Urooting
1. Copy Unroot-glory-4030E.zip to the root of sdcard.
2. Reboot to CWM recovery.
3. Select install zip from sdcard>choose zip from sdcard>Unroot-glory-4030E.zip and select yes - Install Unroot-glory-4030E.zip
4. On your PC, Open SP flashtool and select the scatterfile.
5. Remove check on BOOTIMG and click RECOVERY and select the stock recovery.img. Click download button and disregard download warning by clicking yes.
6.Connect the phone to pc without battery. After the download finished dialog, your done!
Links:
OT-4030 ROOT&CWM RECOVERY
Universal ADB driver
One Touch Upgrade S
Root script
Unroot script
Stock recovery.img
Mirror to all files
TWRP-recovery
I get this error after #3 of CWM recovery installation:
warfab said:
I get this error after #3 of CWM recovery installation:
Click to expand...
Click to collapse
Please attach log...
cyberangel22k said:
Please attach log...
Click to expand...
Click to collapse
Here are my logs...
Guide updated!
added some more steps for error 4050...
Anyone still getting errors, I will help today. you can send a PM on my personal G+ so I can answer quickly to your concerns...
boot_logo changed!
tried to change the boot logo and it worked! thanks to balamu96m for his guide.
This is my new boot logo
bootanimation problem!
I changed my bootanimation and tried if it works using these commands which i normally do with my past android devices.
Code:
adb shell bootanimation
the animation works fine but when i hit:
Code:
adb reboot
the animation showed was just android mask or android shine which shows when you don't have bootanimation.zip inside /data/local or /system/media. it's like a default bootanimation.
so once I booted, I tried again
Code:
adb shell bootanimation
the bootanimation works but when I reboot, it's back to default.
I tried replacing back the original bootanimation.zip but it still the defaut bootanimation. It's very weird. I haven't encountered this before...
cyberangel22k said:
Anyone still getting errors, I will help today. you can send a PM on my personal G+ so I can answer quickly to your concerns...
Click to expand...
Click to collapse
Me and many others are still waiting for your help at symbianize...
can't access symbianize since saturday
Dito muna kayo magpost ng mga tanong.. humihingi din ako ng tulong kay rua1 re: sa error 4050.
fixed!
cyberangel22k said:
I changed my bootanimation and tried if it works using these commands which i normally do with my past android devices.
Code:
adb shell bootanimation
the animation works fine but when i hit:
Code:
adb reboot
the animation showed was just android mask or android shine which shows when you don't have bootanimation.zip inside /data/local or /system/media. it's like a default bootanimation.
so once I booted, I tried again
Code:
adb shell bootanimation
the bootanimation works but when I reboot, it's back to default.
I tried replacing back the original bootanimation.zip but it still the defaut bootanimation. It's very weird. I haven't encountered this before...
Click to expand...
Click to collapse
Found out the cause of this issue. The stock ROM has no fix_permissions binary. So I pushed the binary and tried to fix perm again and now custom bootanimation.zip works!
4050 fix
to get past the 4050 error update the SPFlash Tool to this one http://forum.xda-developers.com/showthread.php?t=1982576
To those having problems with MTKDroid not detecting their phone download and install PDANet for Windows (any version would suffice)
just rooted my phone \^0^/
How to Root.
Please do consider pressing thanks. Thank You.
WARNING: Here's the classic: Do With Your Own Risk.
NOTE:
METHOD1: If this is your first time EVER to root.
METHOD2: If you already have CWM.
METHOD1:
This is the easiest f*cking way EVER! to root since my 1st time on developing. RECOMMENDED for total NOOBS
Credits to Mr. Andrew Casal
Originally Created By: alephzain @ http://forum.xda-developers.com/showthread.php?t=2130276
1. download Framaroot and install it on your phone.
2. Open it and choose Superuser or SuperSU (SuperSU recommended but not required, you can choose whatever you want) then press Gandalf.
3. Reboot and Enjoy a rooted phone. Now wasn't that oh so easy!?
METHOD2:
1. download my RootStock and copy it to your sd card.
2. enter CWM and flash it like any other rom.
3. reboot and enjoy!
This is the work of annson24(annson08). Please, for Christ's sake, don't steal my work, especially Mr. Vipul Verma. Give proper credits to me, better if you press thank too if anyone wants to remake the tut.
Installing CWM Recovery.
DWYOR.
For now, only chinese version is all we have but the devs are working on translating it to english.
UPDATE: We now have a working english CWM, thanks to Lava XOLO devs.
Installation
NOTE:
METHOD1a: If this is your first time flashing CWM.
METHOD1b: If this is your first time flashing CWM. <~ EASIER METHOD, REQUIRES PC
METHOD2: If you have already flashed Chinese CWM before.
(WARNING: Procede to method 2 if this is your first time flashing CWM)
METHOD1a
Need a Rooted Phone. Root procedure HERE.
1. Download a28.img and copy it to your sd card.
2. Install terminal emulator from Play Store. It's free.
3. Open Terminal Emulator and type the following. Be sure to grant Superuser Permission.
Code:
su
[Press Enter]
dd if=/sdcard/a28.img of=/dev/block/mmcblk0p16
[Press Enter]
4. You now have English CWM Recovery v6.0.1.2. You can enter the recovery by turning off your phone, hold vol.down+power button, release after the phone vibrates or power up.
Enjoy!
Video tutorial by Mr. Keiven Adrian Docos Busita again. Thanks for this awesome video.
METHOD1b
(Thank you sir Andrew Casal for the info)
1. Download a28.img
2. Download Universal Android AIO Flasher Tool
3. Turn off phone
4. hold vol.UP+power button, Download mode should come up
5. Connect phone to PC
6. Open Universal Android AIO Flasher Tool
7. Under "Fastboot Flasher (NANDroid Restorer)" Select Recovery
8. Click "Select File" button then locate the "a28.img".
9. tick/check the checkbox "Erase".
10. Click "Flash".
11. Reboot phone to recovery (NOTE: power button doesn't work on download mode, remove battery first the insert it again and hold vol.DOWN+power button, once the BURST page comes up, release your hold..)
12. You now have English CWM Recovery v6.0.1.2.
Enjoy!
METHOD2
1. Download this flashable zip file
http://d-h.st/3Eb
2. Flash it like any other rom (no need to wipe data)
3. Reboot.
4. You now have English CWM Recovery v6.0.1.2.
How to Change Bootanimation.
STILL DWYOR
Update: Video tutorial by Mr. Keiven Adrian Docos Busita. Watch it Here. Thanks Keiven.
First of all I will start this thread at changing the bootanimation since it's this thread's first purpose. Rooting, build.prop, init.d, scripts are to follow if ever i feel like adding them. Rooting on the other hand will be added for sure because we need a rooted device to change bootanimation.
Requirements:
1. Cherry Mobule Burst/Lava Xolo A500 (Duh!)
2. Root permission (Guide on rooting at OP)
3. Root Explorer
4. Good Understanding.
Procedures:
Step 1
Install Root Explorer an open it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2
Browse for /system folder, open it up and browse for /media folder open that up too and you should find:
/audio
/video
bootanimation.zip
shutdownanimation.zip
turnoff.mp3 (not sure what's its real name, I forgot, I deleted mine)
turnon.mp3 (not sure what's its real name, I forgot, I deleted mine)
Step 3
Download custom bootanimation you want, any size will fit.
Step 4
Delete(not recommended) or backup(recommended) your stock bootanimation.zip to your PC or micro sd, and copy your downloaded bootanimation.zip to that folder (/system/media).
Note: You can also delete the shutdownanimation.zip to skip shutdown animation.
Step 5
Reboot and Enjoy.
Note: The "BURST" that comes out during turn on cannot be replaced because it's a bootsplash and can only be tweaked inside boot.img which is where our kernel lies. Custom ROM is the only way to replace that. If someone have already replaced that, you can freely share it here.
General Note: If root explorer displays this: "bootanimation.zip cannot be moved/deleted because the file system is read-only." tick first the [Mount R/W] Button on the upper right until it becomes [Mount R/O].
Available ROMs for our device.
Unofficial ICS Stock Rom for Cherry Mobile Burst. Procedures present @ Origina Thread.
AndroTronic Credits to Mr. Jov1N. Original thread HERE.
DWYOR.
Need CWM.
1. Download rom located at the original thread. I won't be mirroring the download to respect the creator.
2. Download THIS. <~~~ it's a fix for lcd density and boot.img, for the rom to fully work on our device.
3. copy both files on your SD card.
4. Enter CWM by pressing vol.down+power button simultaneously. The phone must first be off (duh!)
5. Wipe Data. (Important!)
6. Install the rom.
7. Install the fix.
8. Reboot and enjoy.
MIUI by Mr. Jov1N again.
http://forum.xda-developers.com/showpost.php?p=39960803&postcount=21
Procedure of installing, same as AndroTronic but without the fix.
NOTE: need the cherry burst boot.img to work, replace first before installing. I'll elaborate the procedure later.
Re: [Guide]Rooting, CWM, Bootanimations, mod, etc. for Cherry Mobile Burst/Lava Xolo
This CWM is not quite working.
The partition table is a bit different
kank_fraud said:
This CWM is not quite working.
The partition table is a bit different
Click to expand...
Click to collapse
It's working just fine sir, everyone on our facebook pages are already using it.
Very Useful
Did you modify anything to work properly
Cuz as far as I can see, it works only with the sdcard
it cannot see the emmc and one more partition.
The partition table is a bit different
I corrected and am using it.
Well if you did, well n good
I did post in a couple of sites
dude, bakit iba yung mga pictures ng CWM sa actual na gamit ko ngayon?
annson08 said:
Installing Custom Rom.
DWYOR.
AndroTronic Credits to Mr. Jov1N. Original thread HERE.
Need CWM.
1. Download rom located at the original thread. I won't be mirroring the download to respect the creator.
2. Download THIS. <~~~ it's a fix for lcd density and boot.img, for the rom to fully work on our device.
3. copy both files on your SD card.
4. Enter CWM by pressing vol.down+power button simultaneously. The phone must first be off (duh!)
5. Wipe Data. (Important!)
6. Install the rom.
7. Install the fix.
8. Reboot and enjoy.
NOTE: I'll be providing a slightly slimmed version of the rom for better responsiveness and with the fix already in it.
MIUI by Mr. Jov1N again.
http://forum.xda-developers.com/showpost.php?p=39960803&postcount=21
Procedure of installing, same as AndroTronic but without the fix.
NOTE: need the cherry burst boot.img to work, replace first before installing. I'll elaborate the procedure later.
Click to expand...
Click to collapse
How to Install the fix??
same with me cwm is not permanent
kank_fraud said:
Did you modify anything to work properly
Cuz as far as I can see, it works only with the sdcard
it cannot see the emmc and one more partition.
The partition table is a bit different
I corrected and am using it.
Well if you did, well n good
I did post in a couple of sites
Click to expand...
Click to collapse
Kank, as you can see we now have english cwm, but the table is still messed up, how'd you managed to fix yours?
Well sorry for the extremely late reply
Been out of station and will again soon
well i have flashed the CWM, the latest one, and its perfect.
Before flashing I even checked the partition table and its perfect.
Nothing needs to be changed.
Only thing, emmc support is not there in this one, but otherwise its perfect.
BTW I am talking abt the XOLO A500 not the CM Burst
CM Burst has a slight different partiton
When you flash the cwm select reboot system now
It'll say the system may flash back stock recovery . Do you want to prevent this from happening select yes
sent from my super advanced mini fridge
annson08 said:
How to Change Bootanimation.
STILL DWYOR
Update: Video tutorial by Mr. Keiven Adrian Docos Busita. Watch it Here. Thanks Keiven.
First of all I will start this thread at changing the bootanimation since it's this thread's first purpose. Rooting, build.prop, init.d, scripts are to follow if ever i feel like adding them. Rooting on the other hand will be added for sure because we need a rooted device to change bootanimation.
Requirements:
1. Cherry Mobule Burst/Lava Xolo A500 (Duh!)
2. Root permission (Guide on rooting at OP)
3. Root Explorer
4. Good Understanding.
Procedures:
Step 1
Install Root Explorer an open it.
Step 2
Browse for /system folder, open it up and browse for /media folder open that up too and you should find:
/audio
/video
bootanimation.zip
shutdownanimation.zip
turnoff.mp3 (not sure what's its real name, I forgot, I deleted mine)
turnon.mp3 (not sure what's its real name, I forgot, I deleted mine)
Step 3
Download custom bootanimation you want, any size will fit.
Step 4
Delete(not recommended) or backup(recommended) your stock bootanimation.zip to your PC or micro sd, and copy your downloaded bootanimation.zip to that folder (/system/media).
Note: You can also delete the shutdownanimation.zip to skip shutdown animation.
Step 5
Reboot and Enjoy.
Note: The "BURST" that comes out during turn on cannot be replaced because it's a bootsplash and can only be tweaked inside boot.img which is where our kernel lies. Custom ROM is the only way to replace that. If someone have already replaced that, you can freely share it here.
General Note: If root explorer displays this: "bootanimation.zip cannot be moved/deleted because the file system is read-only." tick first the [Mount R/W] Button on the upper right until it becomes [Mount R/O].
Click to expand...
Click to collapse
Thxxx for the tutorial... Successfully changed the bootanimation
professor_proton said:
When you flash the cwm select reboot system now
It'll say the system may flash back stock recovery . Do you want to prevent this from happening select yes
sent from my super advanced mini fridge
Click to expand...
Click to collapse
select yes sir so it wouldn't bother you anymore
Sagarvaghela said:
Thxxx for the tutorial... Successfully changed the bootanimation
Click to expand...
Click to collapse
anytime sir.
please reupload the fix for androtronic. the link is down. t.i.a
this was not a MIUI in http://forum.xda-developers.com/showpost.php?p=39960803&postcount=21.
Nandroid Backup Not completed
Hey i installed english clockworkmod recovery in xolo a500 & when i run backup all it only make backup of 27 mb....dont know the problem...plz help me
itsgauravjain22 said:
Hey i installed english clockworkmod recovery in xolo a500 & when i run backup all it only make backup of 27 mb....dont know the problem...plz help me
Click to expand...
Click to collapse
Select the default backup format to tar . Might help you.
Sent from my A500 using XDA Premium 4 mobile app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
omap4boot for P940 (Prada 3.0)
This is a modified version of the omap4boot work done by wkpark (http://forum.xda-developers.com/showthread.php?t=1971014).
This version is designed especially for the P940 to allow fastboot access. A (signed) Clockworkmod recovery is included. This allows you to easily root the device from the recovery and/or flash custom roms.
No need for installing any LG driver/tool crap for rooting.
Furthermore this version works for both Windows and Linux (drivers for Windows included).
Download builds
How this works
Download and extract omap4boot-for_prada.tar.gz
(Windows only) Pull the battery and attach an usb cable to your device. In device manager an OMAP4430 device will show up briefly. Hurry up and right-click > update driver software and install the drivers from the usb_drv_windows directory included in the archive.
Execute start_fastboot.bat (Windows) or start_fastboot.sh (Linux)
Follow the instructions shown.
(optional) Boot into recovery by holding CAMERA + VOLUME DOWN + POWER and do stuff: root your installed rom via a special update.zip tailored for the p940 (http://milaq.net/downloads/android/p940/p940_root_stock_su3.1.3.zip), install a custom rom, etc.
Celebrate
CAUTION: Use this with care! Don't do anything else in fastboot, except you know what you are doing. With this your device is practically unbrickable but you can erase partitions the device needs to work properly. You have been warned.
And as always: I take no responsibility whatsoever for raging, screaming, crying, frustration, failing, confusion, dead kittens, etc.
Changelog
Click to expand...
Click to collapse
1.3 - Initial release
Thanks/Credits
Click to expand...
Click to collapse
wkpark - for his tremendous work on everything various LG devices (you rock)
swetland - maker and creator of the original omap4boot
some dude at LG - for leaking the signing keys for the bootloader
Let me know if i omitted you and i will add you here asap.
IRC channel
Click to expand...
Click to collapse
Visit us in #cyanogenmod-dev on freenode
Is it normal that there are no files in "usb_drv_windows\amd64\" directory?
Is it normal that omap device appears only for few(1-2) seconds and then disappear? or this is my device problem, maybe to small power from usb port?
Ygrek-Ix said:
Is it normal that there are no files in "usb_drv_windows\amd64\" directory?
Click to expand...
Click to collapse
yeah, whoops, missed a few.
i fixed the archive - just redownload it.
Ygrek-Ix said:
Is it normal that omap device appears only for few(1-2) seconds and then disappear?
Click to expand...
Click to collapse
yes, that's normal. you have to be very quick. but once they're installed there is no need to do it again.
or just use linux, no driver installation required there.
milaq said:
yeah, whoops, missed a few.
i fixed the archive - just redownload it.
yes, that's normal. you have to be very quick. but once they're installed there is no need to do it again.
or just use linux, no driver installation required there.
Click to expand...
Click to collapse
Hi, I have a bit of trouble with P940, could you please help me XDA?
I can connect when I start-fastboot.bat, however when I choose that I want to install custom recovery, the script hangs on waiting for device.
Prada shows fastboot v 0.5. I tried all the circusy things with drivers, now I am using fresh WIN7x64 install and with cables. Any help? (I have fresh V20D, but also ADB is not working - it stops on device (num) offline.)
you probably need to install fastboot drivers. use the generic ones from the android-sdk.
if you are booted into fastboot and are connected via usb your device should show up in the device manager as "lg p2 device" or such
milaq said:
you probably need to install fastboot drivers. use the generic ones from the android-sdk.
if you are booted into fastboot and are connected via usb your device should show up in the device manager as "lg p2 device" or such
Click to expand...
Click to collapse
after 42 reboot it cought up and installed recovery! Thanks a lot. Now just realize root through cwm...
Maybe a stupid question. Can I use this way to root an stock 4.04 p940 and have then root rights and cwm? And is cwm then always accessible via the phone key combination on the phone to flash your custom roms, make nandroids...
I'm familiar with S1 and S2 but the P940 sounds always way more complicated for me and it is my daughters phone. She will kill me if I would damage it Actually she has often trouble with no network and with SMS so I thought this wat to root and got cwm + using milaq's 10.1 ROM could be a good solution. I also need to know if the Prada look and feel will stay in 10.1 then.
Sent from my GT-I9100 using xda premium
olarf said:
Can I use this way to root an stock 4.04 p940 and have then root rights and cwm? And is cwm then always accessible via the phone key combination on the phone to flash your custom roms, make nandroids...
Click to expand...
Click to collapse
yip, this will enable you to flash an - already included - recovery. you can then root the installed stock rom via the generic superuser package quoted in OP or flash custom roms, etc.
olarf said:
She will kill me if I would damage it Actually she has often trouble with no network and with SMS so I thought this wat to root and got cwm + using milaq's 10.1 ROM could be a good solution.
Click to expand...
Click to collapse
if you keep to the description and only flash the recovery and leave all other partitions alone, you are safe to do so. but be sure you have read everyting in the OP and are aware of any potential risk, although the p940 is practically unbrickable (if you dont do anything real fuzzy).
olarf said:
I also need to know if the Prada look and feel will stay in 10.1 then.
Click to expand...
Click to collapse
better off in the respective thread but nevertheless: you wont have the prada ui but stock aosp resp. cm flavour. but you can use the inbuilt theme function to make it look like the prada ui (black/white).
cheers
Many thanks !!! So if my daughter agree, I will give it a try
Sent from my GT-I9100 using xda premium
I give it a try today, works fine! Thanks!
Sent from my GT-I9100 using xda premium
Ja, Finally, my LG P940 has one recovery and real fastboot. Danke milaq
Dear Milaq,
After backed-up and restore, I saw clockworkmod work incorrect, because Prada has 2 partition involve system
_for mounting at /system
_for moutong at /system/app
Clockworkmod defaut mount 1 partition at /system, it doesnt mount partition at /system/app. So, backup will not work properly when I restore.
Please fix it
killed said:
Dear Milaq,
After backed-up and restore, I saw clockworkmod work incorrect, because Prada has 2 partition involve system
_for mounting at /system
_for moutong at /system/app
Clockworkmod defaut mount 1 partition at /system, it doesnt mount partition at /system/app. So, backup will not work properly when I restore.
Please fix it
Click to expand...
Click to collapse
wrong thread and already discussed.
see http://forum.xda-developers.com/showthread.php?t=1859662
Just a tip I forget to share. While flashing on win7 64bit I stuck in the fast boot screen. As solution I open the device manager again and let the device reload the driver. Once this was done the process immediately continue until the end with no more problems.
Sent from my GT-I9100 using xda premium
Installed stock ICS V20D, then CWM via fastboot with no problems but rooting (installing a flashable zip with su, busybox and superuser.apk) does not seem to work...
Looks like a custom bootloader might be needed....
Therefore the walhalla method included some patched bin (a piece of ROM)
because lg decided to have a system2 partition mounted to /system/app.
su package installed just fine but the superuser.apk doesnt get used because of the mounts. try "su" in a shell and you will see that rooting went just fine. you can then manually push superuser.apk to /system/app
milaq said:
because lg decided to have a system2 partition mounted to /system/app.
su package installed just fine but the superuser.apk doesnt get used because of the mounts. try "su" in a shell and you will see that rooting went just fine. you can then manually push superuser.apk to /system/app
Click to expand...
Click to collapse
Does manually mean copy/paste with root browser, using adb/ fastboot command ??
Root checker says I'm rooted but some apps like Root Browser and Root App Delete say I do not have a proper root access
Maybe it's sth to do with permissions ? Also I noticed busybox is missing ..
I used Superuser by Koush flashable .zip
Geezer said:
Does manually mean copy/paste with root browser, using adb/ fastboot command ??
Root checker says I'm rooted but some apps like Root Browser and Root App Delete say I do not have a proper root access
Maybe it's sth to do with permissions ? Also I noticed busybox is missing ..
I used Superuser by Koush flashable .zip
Click to expand...
Click to collapse
Well, for me root access worked fine after
1. flashing the rooting update.zip, which was posted by milaq in the first post and
2. flashing the Superuser-3.1.3-arm-signed.zip (http://androidsu.com/superuser/)
So maybe something of these two zips is unnecessary, but at least it is simple and should work
i just wanna ask,, will this work to stock gingerbread? or should i update first to icecreamsandwich?
This is a very nice budget tablet from Tablet Express. I found mine on eBay for $93.00, new + free shipping, and have been very pleased with it. I love that it came with Developer Options already on, had USB Debugging enabled right out of the box, and has a screen protector installed by the manufacturer. Add the fact that the bootloader isn't even locked, and you really can't go wrong with this device.
I used the AIO TWRP Compiler script by @yuweng, to build this recovery, it's a very efficient tool to work with and he put a lot of work into it. Many, many thanks there!!
Well, enough rambling, lets get started...
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!! (Or ask for help, there's a lot of friendly people around here)
Verify Partition Scheme
Over the past few months, it seems some devices have different names for the partition scheme, either "nand" or "mmcblk". So, the first step will be to check which type you have before installing TWRP and rooting the device. Here's how you check:
1) Connect the device to your PC, and open a terminal
2) Type the following:
Code:
# to make sure the device is recognized:
adb devices
# result should be:
List of devices attached
00000000000000000000 device
# Now type:
adb shell
# followed by:
ls -al /dev/block/by-name
# First Line should be 1 of the 2:
# This is a "mmcblk" device
lrwxrwxrwx root root 2016-07-20 00:08 UDISK -> /dev/block/mmcblk0p1
# This is a "nand" device
lrwxrwxrwx root root 2016-07-20 00:36 UDISK -> /dev/block/nandk
Once you know which device type you have, follow the below directions accordingly.
Root (Works for Android 4.4.4 and 5.1.1)
Rooting the device is easy, there are two methods that I know work:
1) Install TWRP, then flash Chainfires current SuperSu zip, find it Here (<-- recommend method)
2) Using Kingo Root for PC, find it Here (Use the Root Again option)
Install TWRP
You should already have ADB installed on your PC, or BusyBox and Terminal Emulator installed on your tablet, I will not cover installation of either of those. And you should know which type of mount partitions your device is using. To get the TWRP recovery on your device, you have a few options:
1) Use ADB to "push" the image (Android 4.4.4 and 5.1.1)
2) Use the included shell script, via BusyBox and Terminal Emulator (Android 5.1.1 and the device must already be rooted to use this option)
Download the appropriate zip for your device, located below, under Downloads, and extract it to a convenient location on your PC. If using your Tablet, the shell scripts and TWRP image must be in the root directory ( / ) to work properly.
Using ADB (Android 5.1.1) on "nand" partitions
Put the X10_twrp3.0.2.img file in the same directory as your working ADB, then enter the following:
Code:
adb push X10_twrp3.0.2.img /dev/block/nandf
#After it finishes:
adb reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That was easy, yes?
Using ADB (Android 5.1.1) on "mmcblk" partitions
Put the X10_twrp3.0.2.img file in the same directory as your working ADB, then enter the following:
Code:
adb push x10_twrp_mmc.img /dev/block/mmcblk0p9
#After it finishes:
adb reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That was easy, yes?
Using ADB (Android 4.4.4)*As of now, KK uses "nand" ONLY
This is the only way I could get it to work right on KitKat, sorry, no Terminal Emulator for this one...
Put the X10_twrp2.8.7.0.img file in the same directory as your working ADB, then enter the following, one line at a time:
Code:
adb push X10_twrp2.8.7.0.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/X10_twrp2.8.7.0.img of=/dev/block/nandf
#After it finishes:
reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That wasn't too bad, was it?
Using Terminal Emulator (Android 5.1.1 using "nand" ONLY)
Put the X10_twrp3.0.2.img and twrp.sh files in the root ( / ) folder of your tablet, then open the Terminal Emulator, enter the following, one line at a time:
Code:
su
sh twrp.sh
The script will tell you when it's done, now, power off the tablet. Boot into recovery by pressing and holding the Volume Down and Power Buttons. When the Dragon Touch logo appears, release the Power Button but continue to hold Volume Down until TWRP boots.
I hope you enjoy my work, and keep in mind that I like to keep things up to date, when a new version of TWRP comes out, I'll build it and post it here.
Downloads
X10 TWRP for "nand" devices
X10 TWRP for "mmcblk" devices
~ Also see Extras Section Below ~
Credits
@yuweng (bunch of help there)
@MSF Jarvis
@trillwizzard (for mmc fix)
@amw2320 (for modified firmware)
TeamWin
Extras
Themes for TWRP
TWRP 3.x Themes for Tablets (Landscape Devices)
Factory Firmware
TabletExpress.com
Modified Firmware
X10-V2-5.1-amw-TWRP_SuperSU.img (Created by: @amw2320, has TWRP (nand) and SuperSu already installed)
Using PhoenixUSBPro
My "short" guide on using the PhoenixUSBPro tool can be found here
X10 Device Tree (For Android 5.1.1)
GitHub
Change Log
Change Log (Newest First)
Added modified stock firmware (8-20-16)
Added info about devices using "mmcblk" instead of "nand", provided TWRP for each (7-23-16)
Added TWRP 2.8.7.0 for KitKat (Android 4.4.4) users and flash instructions (5-19-16)
@NepoRood, great work! One suggestion, instead if using the PRODUCT_COPY_FILES, you can simply add DEVICE_RAMDISK_(DIRS|FOLDERS) += rootdir
I am sure the flag has dir rather than folder in its name, but you can easily confirm that from the thread and you have to use an absolute path for folder name, so include the device/vendor/codename also, before rootdir.
MSF Jarvis said:
One suggestion, instead if using the PRODUCT_COPY_FILES, you can simply add DEVICE_RAMDISK_(DIRS|FOLDERS) += rootdir
Click to expand...
Click to collapse
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
NepoRood said:
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
Click to expand...
Click to collapse
That's what I'm here for, no?
Great job tested with backup and cache cleaning and it worked great now I just need to find a custom rom any of you know of any?
Sent from my SM-G530T1 using Tapatalk
Franzferdinan51 said:
Great job tested with backup and cache cleaning and it worked great now I just need to find a custom rom any of you know of any?
Sent from my SM-G530T1 using Tapatalk
Click to expand...
Click to collapse
Unfortunately, no, I've never had any luck building a ROM. However, I'm going to give it a shot with this tab (I might as well try, lol) IF, I come up with anything, it will be posted here.
NepoRood said:
Unfortunately, no, I've never had any luck building a ROM. However, I'm going to give it a shot with this tab (I might as well try, lol) IF, I come up with anything, it will be posted here.
Click to expand...
Click to collapse
I can lend you my Jenkins server if that's what is bothering you. I'll even fix errors occasionally when I get time
MSF Jarvis said:
I can lend you my Jenkins server if that's what is bothering you. I'll even fix errors occasionally when I get time
Click to expand...
Click to collapse
Thank you for the offer my friend!
I've only tried to build for one device, well 2 actually, both RCA (MT8127), both failed miserably. Even though I got a "successful" build (ie: no errors/make completed) CM12.1 wouldn't boot. Come to find out, the zip and system.img had limited files, I can't remember which, but not enough for a complete rom
So, I decided to learn everything I could about building TWRP (thanks for your help with that too )
I'll pull all the vendor blobs from the X10 and try to put together the device tree for rom building and get back to you.
Thanks Again,
Nepo
marshmallow
you think this tablet is able to be upgraded to marshmallow?
i found a rom for 6.0.1 that has the same processor A83T
it has the same processor so do you think it would flash?
Thanks!
the firmware is
A83T_N106_N1061L6BC_20160309
NepoRood said:
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
Click to expand...
Click to collapse
The flag is actually this
Code:
RECOVERY_RAMDISK_DIRS += device/<vendor>/<codename>/ramdisk
As seen in this reverted commit
stickz42o said:
the firmware is
A83T_N106_N1061L6BC_20160309
Click to expand...
Click to collapse
I think it may work, post a link and I'll test it. Or, you can try it and let us know if it works. Do you have the current firmware already? If not, get it here
PS, you can also use Phoenix Card to boot from External SD just to test
Ahhh Please Help?
@NepoRood
All images from TabletExpress Dragon Touch X10 10'' Android 5.1.
X10-HT-PW-V1-AL-5.1-A83T_N106_N1061L2BC_20151126
X10-HT-PW-V1-AL-4.4-20151104
X10-HT-PW-V2-AL-5.1-20150115
X10-HT-PW-V2-AL-4.4-20160116
A83T_N106_N1061L6BC_20160309-ok NOT WORKING. RED/WHITE BOOT SCREEN.
I have downloaded and flashed all these images and I cannot get TWRP to work? I have installed Via Adb and Terminal, but it will not flash the recovery.
All I get is the factory recovery. I can confirm it pushed it to device, but will not work.
Can someone else verify.
Regards
Paxster
For Users: The Best and Easy App to use is the PhoenixSuit (Just Google lol)
I'm using this one:
Paxster said:
X10-HT-PW-V2-AL-5.1-20150115
Click to expand...
Click to collapse
If all you have is 3e recovery, then you're doing something wrong somewhere. Make sure the TWRP image is in the proper directory.
PC: should be in the same folder as your adb.exe file
Tablet: should be in root directory, which is just a backslash " / "
Please let me know how it goes
NepoRood said:
I think it may work, post a link and I'll test it. Or, you can try it and let us know if it works. Do you have the current firmware already? If not, get it
PS, you can also use Phoenix Card[/URL] to boot from External SD just to test
Click to expand...
Click to collapse
I am going to try it tonight. I didn't know about the phoenixcard boot to test it. I will try that method and post my results if someone doesn't beat me to it
thanks for the info about the phoenixcard
I can't post a link till 10 posts for the firmware btw :/ i'll try to message it to you.
NepoRood said:
I'm using this one:
If all you have is 3e recovery, then you're doing something wrong somewhere. Make sure the TWRP image is in the proper directory.
PC: should be in the same folder as your adb.exe file
Tablet: should be in root directory, which is just a backslash " / "
Please let me know how it goes
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes Recovery is in the same Dir as ADB. It confirms being sent in the Adb Window to my booted Tablet.
Also if I use a Terminal app, it is also confirmed as being flashed, but I still get a 3e recovery? So strange.
Its driving me nuts lol..
Q:Should it work with any V5.1 Android Firm? I am using X10-HT-PW-V2-AL-5.1-20150115 from tabletexpress.
Can you confirm what version yours is working on please.
UPDATE... 5 Hours later.. I managed to flash the TWRP on Android V4.4 using Rashr. and when in recovery the screen is corrupted, unable to use? and Twrp is in Landscape mode. Shall try this method on V5.1.
Regards
Paxster
PS: @stickz42o A83T_N106_N1061L6BC_20160309 Does not work. I posted above.. Red/White Stuck Boot.
@NepoRood
Ok.. I used RASHR to install TWRP. A lot less hassle for people i recon matey. Plus it worked.....ADB refused to install lol...
It works ok on the Android V5,1, (X10-HT-PW-V2-AL-5.1-20150115) but unable to backup any partitions. The Twrp Log reports Unable to mount or find the partitions?
Plus you cannot boot the tablet again after rebooting out of twrp hehe..
Here is a Log File after Flashing a Image from PhoenixUSBPro. The Partitions are there View attachment PAXSTER.LOG So maybe TWRP does not know where they are ekk? Maybe it will help from the log file to sort his out? Im new to creating a Twrp File.
Regards
Paxster
Paxster said:
@NepoRood
Ok.. I used RASHR to install TWRP. A lot less hassle for people i recon matey. Plus it worked.....ADB refused to install lol...
It works ok on the Android V5,1, (X10-HT-PW-V2-AL-5.1-20150115) but unable to backup any partitions. The Twrp Log reports Unable to mount or find the partitions?
Plus you cannot boot the tablet again after rebooting out of twrp hehe..
Here is a Log File after Flashing a Image from PhoenixUSBPro. The Partitions are there View attachment 3747215 So maybe TWRP does not know where they are ekk? Maybe it will help from the log file to sort his out? Im new to creating a Twrp File.
Regards
Paxster
Click to expand...
Click to collapse
When building, I ran into problems of only TWRP booting, turns out it was an init.rc and recovery.fstab issue. But, I had that fixed for the final release I'm using the exact same firmware as you are, and TWRP works perfectly.
Could you attach your TWRP log?