X98 Air III M5C5 with clean stock ROM? - Teclast X98 Air 3G

I'm confused. I bought an M5C5 from Gearbest EU warehouse, which arrived today and it's sitting charging quite happily.
I was expecting to have to flash a custom ROM or manually debloat the thing. However out of the box it has a completely blank AOSP type build on it, just with the Google Play Store added.
Android 5.0, build number is V1.00_20151204, kernel version 3.10.2 (December 7th 2015 10:50:43 CST).
I see a couple of other reports of this around other forums. Does anyone know what's going on? More to the point, before I decide whether to flash a custom or not - is there any way of safely dumping this for others more knowledgeable than me to play about with?

I foolishly flashed a custom over the top of this. Other than being rooted, there's no benefit - in fact the stock is better and faster than the customs I've tried (pure Android launcher, no fluff with "reboot to Windows" or phone junk compiled in).
If you have this build, stick with it!

I read about this new stock version on my country's forums. Unfortunately nobody has dumped yet this version because I'm very interested.

Durete said:
I read about this new stock version on my country's forums. Unfortunately nobody has dumped yet this version because I'm very interested.
Click to expand...
Click to collapse
Yeah, I'm an idiot for not doing it. It looks easy to.

I'm pretty happy with sikke1's "Debloated" stock rom. You should try it. I don't like neither customized roms based in stock roms for different devices.

I'm using Mireks now. If someone dumps the build that seems to be showing up on new Air IIIs then I'm going straight back to that, it was perfect!

hordarian said:
I'm using Mireks now. If someone dumps the build that seems to be showing up on new Air IIIs then I'm going straight back to that, it was perfect!
Click to expand...
Click to collapse
I received my M5C5 with clean stock rom yesterday (also from Gearbest Europe store)
1.) I can try to backup this ROM, if you like, but you have to tell me how....
2.) My plan was to flash to mirek V7, but if I understand you correctly, it's better to stay on stock, right?
PS: In fact, the ROM looks ok, the only thing I'm really missing is root!
Till now I can't find a working instruction how to root this stock ROM....

heino69 said:
I received my M5C5 with clean stock rom yesterday (also from Gearbest Europe store)
1.) I can try to backup this ROM, if you like, but you have to tell me how....
2.) My plan was to flash to mirek V7, but if I understand you correctly, it's better to stay on stock, right?
PS: In fact, the ROM looks ok, the only thing I'm really missing is root!
Till now I can't find a working instruction how to root this stock ROM....
Click to expand...
Click to collapse
(1) It looks like there are a few people that would like the backup
Having not done a partition backup before some digging suggests it requires root or booting from a custom recovery.
This should allow you to root it: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096, it might allow a full backup to SD card as well.
(2) I'm always grateful to all of the ROM developers, but it seems in this case (maybe the first time ever!) the stock ROM is absolutely perfect stock Android! It is a better base for anyone to build a custom ROM from than any of the previous ones!

hordarian said:
This should allow you to root it: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096, it might allow a full backup to SD card as well.
Click to expand...
Click to collapse
I know this thread about rooting, but currently I'm waiting for feedback in another (German) forum about this rooting method, which maybe can brick the Air III...

I used that method to Root my Air III with Sikke1's "Debloated" Rom and to install Xposed.
I guess is pretty sure to use since the Root zip only add Supersu and binaries to /System.

I received my Air III M5C5 from Gearbest three weeks ago, but unfortunately it had the previous bloated Chinese ROM. Although I am very satisfied with Mirek v7, I will be very happy to test this one, if you are able to get it.

Durete said:
I used that method to Root my Air III with Sikke1's "Debloated" Rom and to install Xposed.
I guess is pretty sure to use since the Root zip only add Supersu and binaries to /System.
Click to expand...
Click to collapse
Right, the one who posted the problem stated that he followed the proposed steps (option 5 - CWM, and T4) but after installing the SU.zip the reboot failed....
I'm not sure if he did something wrong, I just want to be sure not to brick my Air III
If i succeed, what tool to use to make a full backup? Titanium backup pro?
---------- Post added at 02:12 PM ---------- Previous post was at 01:30 PM ----------
OK, I successfully rooted my device
If anyone is really interested to have the clean stock ROM, please help me how to make this backup...

I'm really interested, but not sure what should be the next step ...

This looks like a sensible guide: http://androidcreations.weebly.com/how-to-get-android-mounts-and-partition-images.html
And this: http://www.slatedroid.com/topic/7220-how-to-dumping-your-rom-by-adb-raw-nand-dump/
Get the Android SDK on your computer first. Looks like you'll need an SD card as well (there appear to be methods that don't require it but I'm not sure whether they work or not).
Let us know if you're struggling. I can probably put together exact commands for this device based on mine, I'm just distant from it at the moment so might take me a day or two.

Durete said:
I read about this new stock version on my country's forums. Unfortunately nobody has dumped yet this version because I'm very interested.
Click to expand...
Click to collapse
Same here!
I ordered 2 units, one came with an old Teclast ROM full of bloat (so I flashed Mireks v7 ROM) but the other one is clean and fast V1.00_20151204) AnTuTu score is 49887 compared to Mireks v7 rom 48547
Someone please send me some instructions on how to dump it and I will happily upload it somewhere! I would not mind sticking this new Teclast ROM on my other air iii

To do a backup. Assuming you're using Windows. You'll need a MicroSD card of a few GB
Get the latest Intel ADB driver and install it: https://software.intel.com/en-us/an...ion-instructions-for-intel-android-usb-driver
Enable USB debugging on your device (about device, hit build number 7 times to enable developer options, open developer options and tick USB debugging).
Connect device by USB.
Open a command prompt, run the following commands:
Code:
adb shell "dd if=/dev/block/by-name/boot | gzip > sdcard/boot.img.gz"
adb shell "dd if=/dev/block/by-name/system | gzip > sdcard/system.img.gz"
adb shell "dd if=/dev/block/by-name/recovery | gzip > sdcard/recovery.img.gz"
adb pull /sdcard/boot.img.gz
adb pull /sdcard/system.img.gz
adb pull /sdcard/recovery.img.gz
I'm not certain whether the device needs to be rooted first to do this, or whether it's all the required partitions.
Could also pull the entire flash down with the following (needs a substantial SD card!). Not sure this is necessary, and you should 100% do a full factory reset/wipe beforehand or you'll be giving easy access to any data you've got on the device.
Code:
adb shell "dd if=/dev/block/mmcblk0 | gzip > /sdcard/mmcblk0.img.gz"
adb pull /sdcard/mmcblk0.img.gz

hordarian said:
To do a backup. Assuming you're using Windows. You'll need a MicroSD card of a few GB
Get the latest Intel ADB driver and install it: https://software.intel.com/en-us/an...ion-instructions-for-intel-android-usb-driver
Enable USB debugging on your device (about device, hit build number 7 times to enable developer options, open developer options and tick USB debugging).
Connect device by USB.
Open a command prompt, run the following commands:
Code:
adb shell "dd if=/dev/block/by-name/boot | gzip > sdcard/boot.img.gz"
adb shell "dd if=/dev/block/by-name/system | gzip > sdcard/system.img.gz"
adb shell "dd if=/dev/block/by-name/recovery | gzip > sdcard/recovery.img.gz"
adb pull /sdcard/boot.img.gz
adb pull /sdcard/system.img.gz
adb pull /sdcard/recovery.img.gz
I'm not certain whether the device needs to be rooted first to do this, or whether it's all the required partitions.
Could also pull the entire flash down with the following (needs a substantial SD card!). Not sure this is necessary, and you should 100% do a full factory reset/wipe beforehand or you'll be giving easy access to any data you've got on the device.
Code:
adb shell "dd if=/dev/block/mmcblk0 | gzip > /sdcard/mmcblk0.img.gz"
adb pull /sdcard/mmcblk0.img.gz
Click to expand...
Click to collapse
Thanks Hordarian.
I will give this a go as soon as I can. I'll also upload whatever I'll dump to my google drive and share so you can have a look. Good suggestion to factory reset before I do the dump. The unit is only 3days old and the only thing installed is Antutu and I am logged on , so I will clear this first and then upload. If I do need to root first then I will do that too.
I'll try to do this on Tuesday.
Thanks for the instructions

Debloated GoogleNow custom roms VS New Stock Rom
Hello,
I too received X98 AIr III with new stock rom. I reflashed my tablet with sikke1 rom to solve the camera problem. (It looks like my x98 might have a defective camera......)
I rooted the sikke1 rom. It works great (well...except the camera).
Sorry. I did not make a back up of stock rom before I flashed.
I am looking forward to having a stock rom back even though I like both roms. Stock rom looked clean (small icons, play store only) and sikke1 rom has large icons (more visible).
Should I go back to stock rom when it is available? I cannot make a choice.....Hmm.

hordarian said:
To do a backup. Assuming you're using Windows. You'll need a MicroSD card of a few GB
Get the latest Intel ADB driver and install it: https://software.intel.com/en-us/an...ion-instructions-for-intel-android-usb-driver
Enable USB debugging on your device (about device, hit build number 7 times to enable developer options, open developer options and tick USB debugging).
Connect device by USB.
Open a command prompt, run the following commands:
Code:
adb shell "dd if=/dev/block/by-name/boot | gzip > sdcard/boot.img.gz"
adb shell "dd if=/dev/block/by-name/system | gzip > sdcard/system.img.gz"
adb shell "dd if=/dev/block/by-name/recovery | gzip > sdcard/recovery.img.gz"
adb pull /sdcard/boot.img.gz
adb pull /sdcard/system.img.gz
adb pull /sdcard/recovery.img.gz
I'm not certain whether the device needs to be rooted first to do this, or whether it's all the required partitions.
Could also pull the entire flash down with the following (needs a substantial SD card!). Not sure this is necessary, and you should 100% do a full factory reset/wipe beforehand or you'll be giving easy access to any data you've got on the device.
Code:
adb shell "dd if=/dev/block/mmcblk0 | gzip > /sdcard/mmcblk0.img.gz"
adb pull /sdcard/mmcblk0.img.gz
Click to expand...
Click to collapse
Gave Hordarians instructions a quick try... But I guess this (below) means that I need root as the very first command resulted in the below:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
dd: /dev/block/by-name/boot: Permission denied
---------- Post added at 10:42 PM ---------- Previous post was at 10:24 PM ----------
hordarian said:
To do a backup. Assuming you're using Windows. You'll need a MicroSD card of a few GB
Get the latest Intel ADB driver and install it: https://software.intel.com/en-us/an...ion-instructions-for-intel-android-usb-driver
Enable USB debugging on your device (about device, hit build number 7 times to enable developer options, open developer options and tick USB debugging).
Connect device by USB.
Open a command prompt, run the following commands:
Code:
adb shell "dd if=/dev/block/by-name/boot | gzip > sdcard/boot.img.gz"
adb shell "dd if=/dev/block/by-name/system | gzip > sdcard/system.img.gz"
adb shell "dd if=/dev/block/by-name/recovery | gzip > sdcard/recovery.img.gz"
adb pull /sdcard/boot.img.gz
adb pull /sdcard/system.img.gz
adb pull /sdcard/recovery.img.gz
I'm not certain whether the device needs to be rooted first to do this, or whether it's all the required partitions.
Could also pull the entire flash down with the following (needs a substantial SD card!). Not sure this is necessary, and you should 100% do a full factory reset/wipe beforehand or you'll be giving easy access to any data you've got on the device.
Code:
adb shell "dd if=/dev/block/mmcblk0 | gzip > /sdcard/mmcblk0.img.gz"
adb pull /sdcard/mmcblk0.img.gz
Click to expand...
Click to collapse
Thanks for those instructions Hordarian, but as mentioned, it does look like root is needed and this stock ROM does not have it... So, what is the best (easiest) way of rooting? Is it this:
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096

Root link for original rom
guvno said:
Gave Hordarians instructions a quick try... But I guess this (below) means that I need root as the very first command resulted in the below:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
dd: /dev/block/by-name/boot: Permission denied
---------- Post added at 10:42 PM ---------- Previous post was at 10:24 PM ----------
Thanks for those instructions Hordarian, but as mentioned, it does look like root is needed and this stock ROM does not have it... So, what is the best (easiest) way of rooting? Is it this:
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Click to expand...
Click to collapse
Yes. I was able to root the original rom in my tablet using that link. It was fairly easy.
http://forum.xda-developers.com/andr...p-cwm-t2975096

Related

[GUIDE] All Tattoo questions and answers see here (from A to Z)!

Hi,
this thread is meant as a starting point for every kind of questions. I will write everything I know into this thread and update it (hopefully) frequently
Here are the topics handled for now (if you have any other questions you want to have answered you can PM me, so I can try to handle it if I know the solution and add this to my to do list in point 5!!! ):
1. How can I root my phone
1.1 General information/Basic adb-commands
1.2 Do I have to create a goldcard?
1.3 Tools you need
1.4 The automated way
1.5 The manual way (recommended by the author)
1.6 Problems and (hopefully good) solutions
1.7 References
2. Flashing images/ROMs
2.1 What is a recovery image
2.2 What is a boot image
2.3 How to flash/tools needed
2.3.1 Creating a Goldcard
2.4 Where can I get an overview of the existing ROMs?
2.5 Problems during flashing and solutions
2.6 References
3. Information about the Tattoo/Useful stuff
3.1 How to install busybox?
3.2 Can it perform multitouch?
3.3 How to increase battery life?
3.4 Using own ringtones for calls/sms
3.5 How to disable data transfer with a custom ROM?
3.6 How to make the Tattoo ring louder?
3.7 How to replace the home screen?
3.8 Disabling xxx-synchronisation with Google-servers
3.9 Backing up apk's and data to your PC
3.10 How to enable more languages on my mobile?
3.11 How to manually delete system apks? Alternatively with GUI?
4. Dev-Goodies
4.1 Modifying update.zips and resigning them
4.2 Modifying resources in apk-files and resigning them
4.3 Installing apks via adb for getting exact error codes if installation fails
4.4 Everything related to ROM cooking
5. Things I will do better in this thread due to user request
Please note: I won't be giving tutorials about Android-apps usage beside the one mentioned in my tutorial!
Let's start now:
1. How can I root my phone?
1.1 General information/Basic adb-commands
Rooting a phone enables you to do things, which normally aren't possible for the average user like:
- Removing apps which were preinstalled by the provider (like Orange, Vodafone, etc.). My Tattoo had Vodafone apps for buying music and other sh*t, which was installed on the system partition (to which a "normal" user has no rights to write to, including deleting).
The Tattoo was successfully rooted by a bunch of guys here, namely -bm-, mainfram3 and Coburn64 (maybe, I don't remember quite correctly ). Also the Tattoo was the first phone having a security mechanism hindering a user to mount the filesystems as read/write, which had to be overridden by remapping the read only memory region to a read/write one. This is done by the module Tattoo-hack.ko, also made by mainfram3. He also created the first boot.img, which enabled su directly from adb and loading Tattoo-hack directly from boot on.
A few words about adb:
ADB is a tool for communicating from the PC with the mobile phone. For this a service is running on the phone enabling the communication via Terminal Emulator. Here are the most useful adb-commands:
Code:
adb push localFileFromPC /path/on/mobilephone
-> pushes a file "localFileFromPC" to a specified location on the phone
adb pull /path/to/file pathFromPC
-> receives a file from the phone and stores it to "pathFromPC"
adb remount
-> This is only possible in custom ROMs, remounts the file system to r/w automatically
adb shell "command"
-> executes "command" and returns to the computer shell
adb shell
-> opens a shell session on the phone (from here on you have to be very careful! Also you can execute now normal linux commands like rm, mv, ls, chmod and so on, but not cp (this can done through busybox)). You will have to use this more often, so get used to it ;)
1.2 Do I have to create a goldcard?
I read this question quite often. For rooting, you don't need it, but for SIM-locked phones you can't flash custom unbranded ROMs (I think).
A guide to create a goldcard follow this link: http://forum.xda-developers.com/showpost.php?p=5179788&postcount=1 (thanks to MiSSigNNo to this point)
1.3 Tools you need
A complete set of tools can be found here Feel free to mirror it:
http://rapidshare.com/files/403766494/Tattoo.rar.html
This package contains:
- adb binaries for Windows (sorry Linux users )
- su (Please note: use the su-binary attached in this post, not the one in the archive!!!!!)
- m7 exploit
- Amon_RA recovery.img
- mainfram3 boot.img
- flash_image binary
- tattoo-hack.ko
1.4 The automated way
This method was created by maverixx and can be found here. This basically consists of a package doing everything you need by itself. It roots the phone and flashes maverixx recovery.img, which (no offense) I don't like as much as I like Amon_RA's one!). Just click the batchfile and it does the rest (you have to connect your phone via USB to your PC though ).
If you want to use the automated way, but flashing Amon_RA's recovery, just replace the recovery.img from maverixx' package with the recovery.img provided in my archive file (see 1.3 for the link).
In my time here I noticed quite a few users experiencing problems either with a fully functional su or with the recovery image not flashing certain update.zip packages. It seems to be a matter of luck.
1.5 The manual way (recommended by the author)
I personally like what is done when and how, that's why I recommend the manual way. So let's get down to business Let's see if you know all the adb-commands I wrote here:
1. Let's say you have everything unpacked into C:\Tattoo
2. In your terminal (on your PC) type:
- adb shell "mkdir /data/local/bin" (if it returns an error it means that the directory already exists, just proceed)
- adb push m7 /data/local/bin/
- adb push su /data/local/bin/
- adb push flash_image /data/local/bin/
- adb push tattoo-hack.ko /data/local/bin/
- adb push recovery.img /sdcard
- adb push boot.img /sdcard
3. We have every needed file on the phone now. Type now (we are still in your terminal):
- adb shell
$ cd /data/local/bin
$ chmod 766 m7 (I don't retain this step as mandatory, so if this process fails, just proceed)
$ while ./m7 ; do : ; done
lots of text until you see something like "wrote shell code", press enter 2 or 3 times enter to see:
#
4. Then perform this:
- # export LD_LIBRARY_PATH=/system/lib
- # export PATH=/system/bin
- # insmod ./tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
- # cat ./su > /system/bin/su
- # chmod 4755 /system/bin/su
- # chmod 755 ./flash_image
Click to expand...
Click to collapse
Questions?
1.6 Problems and (hopefully good) solutions
Q: How do I execute my command line tool?
A: On your Windows host, go to Start->Run...->type "cmd"
Q: Where is my adb? When I type it in my shell it says that it was not found!
A: The adb binary is found in the archive I supplied above or in the Google SDK. As my archive-file is quite smaller than the Google SDK you should take mine. Let's suppose your adb binary is unpacked in C:\Tattoo, then type:
Code:
Your\Current\Location> cd C:\Tattoo
C:\Tattoo> adb <command>
Q: adb says "error: device not found" when I try to launch the shell on the phone!
A: Connect the phone with the usb cable and make sure the sd card is not mounted as drive on your PC!!!
Q: When I want to copy something the phone returns that "cp" is not found! Also when I try to move a file, it says "cross-link device".
A: Well, copying from one partition to another is only possible either via busybox or via
Code:
cat file > /location/filename
Example:
cp /data/su /system/bin
is realized by typing
cat /data/su > /system/bin/su
Also make sure that system is r/w!!!
Q: flash_image returns write errors when flashing recovery/boot image!
A:
For boot: Try to redo the flash procedure
For recovery: Note that you can't flash the same recovery.img as the one already installed, so install another recovery.img first (like maverixx) and then Amon_RA's again. If it still doesn't work reboot, remount the partitions r/w, insmod tattoo-hack.ko and retry flashing.
Q: How can I unroot my device?
A: Just delete su from /system/xbin and restore the old boot.img. Alternatively see here for retrieving a stock ROM to flash it on your phone.
PM me with more questions and I'll post them with the possible solution.
1.7 References
- Zecanilis EXCELLENT Root-Recovery-Flash images thread
- maverixx' One-click root method+recovery thread
- Coburn64's Newbie guide for manual rooting (recommended reading!)
2. Flashing images/ROMs
2.1 What is a recovery image
A recovery image is not only useful to flash custom ROMs on your device. It also enables you to backup your entire phone contents to restore it completely in case of a brick, if anything should happen...especially SIM-locked mobiles should be backed up as soon as possible. Also many recovery image modders add several non-standard features like mounting the SD card while in recovery mode or enabling adb support, etc.
2.2 What is a boot image
The boot image not only contains the kernel which brings up your Tattoos, it only can be modified to load up modules enabling ext2/3 support, loading camera, remapping read only code to an r/w area (tattoo-hack.ko), etc. Without a working boot.img, don't even bother trying to boot the phone (maybe if you do a logcat it returns something useful to solve this problem )
2.3 How to flash/tools needed
Execute steps 1 to 4 in topic 1.5 first!
5. Now comes the hard part:
- # ./flash_image boot /sdcard/boot.img
- # ./flash_image recovery /sdcard/recovery.img
it can be that flash_image reports errors in the last step (recovery.img step), but another user said it would be still working to boot to recovery...but to be sure (if you got the error!!!) flash maverixx recovery.img and then again the one I supplied in my archive (Amon_RA)
Reboot once and when you connect with adb to your phone you should see the difference
Click to expand...
Click to collapse
2.3.1 Creating a Goldcard
This is a post I took from MiSSigNNo, kudos to him:
Creating the Gold Card:
[...]
4. We need the android-sdk tools, we can find them here: http://developer.android.com/sdk/index.html download them, and unzip in a folder maybe in C:\androidtools
5. Go the the Command line (Start->Execute->write cmd and OK), and there you should find where you unzip the android-sdk tools, example cd c:\androidtools\tools
6. Run this command "adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid" if you had the microSD in the drive you will find a long number like:
532600bd227d9c0347329407514d5402
7. Go to this page to reverse it: http://hexrev.soaa.me/ and copy the code reversed:
In our example it will be: 00544d5107943247039c7d22bd002653
8. Go to this page to generate your GoldCard image: http://revskills.de/pages/goldcard.html
And put your reversed number and you email. You will receive an email with a file called "goldcard.img"
9. Now you need an Hex editor like HXD. Download it from: http://download.cnet.com/HxD-Hex-Edi...html?tag=mncol
10. Exactly the same as the instructions I pasted above:
11. Install and launch HxD Hex Editor program. (make sure you use "Run as Administrator" under Vista and win 7)
12. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK. (BEWARE, MUST BE UNDER PHYSICAL DISK NOT LOGICAL DISK, THIS MISTAKE MADE ME BIG PROBLEMS)
13. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
14. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
15. Click on the “removable disk” tab. Select offset (line) 00000000 till offset (line) 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
16. Click on File > Save. now you can exit the program. You now have a gold card.
[...]
Click to expand...
Click to collapse
2.4 Where can I get an overview of the existing ROMs?
Look it up here (Excellent work liderzre)
2.5 Problems during flashing and solutions
Q: HEEEEELLLPPP! flash_image says that it couldn't write to some memory addresses! What can I do?
A: Don't panic. First make sure to have loaded tattoo-hack.ko, remounted system and data to r/w and then try again with another recovery.img (either maverixx or Amon_RA). Flashing the same recovery.img again WON'T WORK!!!! That's why you have to take a little detour by first flashing another recovery image.
Q: How do I boot to recovery??
A: Type in your command line while the phone is plugged in:
Code:
adb shell "reboot recovery"
. If this doesn't work, turn off your phone, hold down the home-button and press the power-button. Then when the Tattoo logo can be seen, release the home button and the recovery screen should be seen
2.6 References
- Zecanilis EXCELLENT Root-Recovery-Flash images thread
- maverixx' One-click root method+recovery thread
3. Information about the Tattoo/Useful stuff
3.1 How to install busybox?
Load the busybox binary here (select the one with arm6 at the end). Put this binary onto your data or system partition (I suggest /system/xbin) and now there are two ways to install/enable it. See below
Method 1 (will extract EVERY FEATURE, but consumes A LOT of your disk space so be careful or switch to method 2)
Do this in your command line:
Code:
adb remount (make it r/w if not done already)
adb shell "mkdir /system/xbin" (create dir if it doesn't exist)
adb push busybox /system/xbin (please make sure to have busybox in the same directory as adb ;) )
adb shell
cd /system/xbin
./busybox --install
Method 2 (saves your precious disk space )
Do this in your command line
Code:
/system/xbin/busybox --install -s /system/xbin
3.2 Can it perform multitouch?
Nope, the Tattoo has a resistive touch screen, which is known to be NON-multitouch...newer generation or high-end phones usually have capacitative screens. My suggestion is not taking the Nexus One anymore, since their touch screen type supports only 2 fingers at once, while phones like the Samsung Galaxy S have a SUPER responsiveness and sensibility (and of course 10 fingers support).
3.3 How to increase battery life?
Okay, here are little tips how to increase battery life - mine holds 7 to 8 days and I surf, call ppl and sms almost every day:
1. Flash either fyodor 0.6.4.2 or Abyzou 2.1.9 - my favourite is fyodor ones (if I still would have a Tattoo, of course )
2. Download APNd roid from the market or here and disable your 3G Internet connection (for activating it, just start the program again!)
3. If you see that you have NO RECEPTION AT ALL in one place (at work for instance), turn off your phone as this will DRASTICALLY decrease battery life because the phone tries constantly to search for a network it can log on to.
4. Try to keep your phone in normal temperature areas (between 20 and 27 degrees celsius = 68 - 80.6 degrees fahrenheit)
5. Kill unneeded apps automatically (there are quite a few apps doing this)
3.4 Using own ringtones for calls/sms
Create a folder called "media" on the root of your SD card and a sub-folder called "audio" there you have to create one folder called "notifications" for SMS and "ringtones" for call sounds. Place every desired track into these folders and reboot your phone. You should see the entries now when choosing ringtones. Alternatively just load "Ringo Pro", a really powerful tool also able to display SMS pop-ups and much more.
3.5 How to disable data transfer with a custom ROM?
As already explained above, load APN droid from the market or here.
3.6 How to make the Tattoo ring louder?
There is a little app called "Louder Volume Hack" enabling your phone to ring much louder than normally. You can load it on any popular w*rez-site Unfortunately I cannot enter the link to the app here or PM it. Any questions requesting a link to this app will be deleted instantly, so don't bother trying and use Google. There are several buttons displayed, but for better visibility I suggest enabling the Widget and hacking the system there. Also please note that ROOT access is required!! Refer to section 1 to root your phone.
3.7 How to replace the home screen?
There are two ways to do it. Method 1 is the easier one, but runs the Google Launcher and the replacement laucher in parrallel, which implies more CPU usage and battery drain. Method 2 is the more brutal one, but enables you to run just one launcher.
Method 1:
Install the replacement home app and press the home button. A dialog should appear asking you which Home Launcher should be used.
Method 2:
Put your home replacement apk onto the root of your SD and make sure you have busybox installed and /system mounted as writeable. Rename the Home replacement apk to Launcher.apk and fire up adb shell:
Code:
mv /system/app/Launcher.apk /system/app/Launcher.apk.old && mv /system/app/Launcher.odex /system/app/Launcher.odex.old && cp /sdcard/Launcher.apk /system/app && chmod 755 /system/app/Launcher.apk
Should be a pretty generic approach
3.8 Disabling xxx-synchronisation with Google-servers
Go to settings, data synchonisation and disable the entries you don't want to have synch'ed with Google. Since it's long time ago since I did this (remember that I don't own a Tattoo anymore) the procedure can be slightly different from ROM to ROM.
3.9 Backing up apk's and data to your PC
By popular request, here a topic about how to backup apk's and their corresponding data manually (can be done separately, too if you want just one of the two). Doing it with the tar command HOPEFULLY preserves also all permissions!!! Check it:
Hit up adb shell and make sure have busybox:
Code:
for the apks
# tar -cvf /sdcard/dataAppsBackup.tar /data/app
for the data
# tar -cvf /sdcard/dataDataBAckup.tar /data/data
If you want to decompress these files again do:
Code:
# tar -xvf /sdcard/dataAppsBackup.tar -C /data
# tar -xvf /sdcard/dataDataBackup.tar -C /data
Note that these files won't be compressed! If you want to save some disk space on your SD then add the parameter 'z' (without the quotes) in the tar arguments (e.g. tar -cvfz for compressing and tar -xvfz for decompressing)
3.10 How to enable more languages on my mobile?
There is an app called MoreLocale in the market enabling you to select more languages. Download it, it's free
3.11 How to manually delete system apks? Alternatively with GUI?
For deleting manually you only need root-access. With GUI you need RootExplorer (buy it or do what you need to do to get this app-but with these features I would suggest to buy the app ).
Note: I do not take any responsibility if you delete the wrong apk and you lose any functionality of the phone. Do this only if you know what you're doing!
The manual way:
Connect the phone via USB, fire up adb shell and type:
Code:
insmod /LOCATION TO [URL="http://TATTOOHACK.KO/tattoo-hack.ko"]TATTOOHACK.KO/tattoo-hack.ko[/URL]
mount -o rw,remount /dev/block/mtdblock3 /system
cd /system/app
rm NAMEOFAPK.apk
The GUI way:
Install RootExplorer, open it, navigate to /system/app and press the little "Mount R/W" button at the top of the screen and begin deleting
4. Dev-Goodies
4.1 Modifying update.zips and resigning them
See this thread and get enlightened
4.2 Modifying resources in apk-files and resigning them
Same procedure as above:
1. Extract the file with WinRAR/WinZIP, delete the contents of META-INF and start modifying what you have to modify
2. Pack everything again into a ZIP file and sign it with the signapk.jar file (can be found somewhere in the forum or here). The syntax of how to use this can be found in the last link (yes, it's only 10 KB ).
4.3 Installing apks via adb for getting exact error codes if installation fails
Prerequisites: Either know the exact path to the apk or put it into the same directory as your adb executable and hit up your command line:
Code:
adb install /path/to/apk/file.apk
OR
adb install file.apk (implies that apk is located in same dir as adb)
4.4 Everything related to ROM cooking
Check this link (thanks to Decad3nce) and this one (thanks to mxlaser).
5. Things I will do better in this thread due to user request
- Nothing
The end for now.
Note: If you think that my thread is good, then please rate it with 5 stars
Changelog:
Version 1.0
- Initial draft
Version 1.1
- Added complete topic 1 now
- Fixed layout and some typos
Version 2.0
- Added complete topic 2 and half of 3
Version 2.1
- First prototype with all topics finished (will rework parts which are not quite understandable)
Version 2.2
- Added new question to 1.6
Version 2.3
- Added section 4.4 -> Everything related to ROM Cooking DUDEEEESSSSS
Version 2.4
- Added 3.11 How to manually delete system apks? Alternatively with GUI?
Version 2.5
- attached working su file - thanks to lovenemesis for this
Version 2.6
- added some mirrors for the Tattoo.rar archive - thanks to emb0re for providing some space
Version 3
- added topic about creating gold cards (2.3.1)
hi
very good initiative stuck
Great work
Very intuitive guide for beginner.
Though as an experienced and new android application developer, it really took me a whole afternoon to understand every step of the whole process. I am sure this guide would save many others wonderful Saturday afternoon.
Nice Work
Great Work From You Sir. This Will Be Useful for Beginners I Think This Will Save Lot Of Our Time's. And Mods Too
Thanks for the feedback...I hope that I can fill many topics tomorrow
P.S.: Indeed this is meant for the many unexperienced users who desperately want to flash custom ROMs but don't know how to do it...this also spares a lot senseless thread-posts I hope...^^
Dude
SSj Man Can You Add Tutorial Abt How to get the Apk file which i download from market in my mobile. if that is possible
3. We have every needed file on the phone now. Type now (we are still in your terminal):
- adb shell
$ cd /data/local/bin
$ while ./m7 ; do : ; done
lots of text until you see something like "wrote shell code", press enter 2 or 3 times enter to see:
#
Click to expand...
Click to collapse
For me I need to add execute permission for m7 before expolit, with
Code:
chmod 766 m7
.
jagan_3400 said:
SSj Man Can You Add Tutorial Abt How to get the Apk file which i download from market in my mobile. if that is possible
Click to expand...
Click to collapse
You mean getting the apk from your mobile on your PC for example?
lovenemesis said:
For me I need to add execute permission for m7 before expolit, with
Code:
chmod 766 m7
.
Click to expand...
Click to collapse
Hm, normally when you push the file via adb it will have user permissions, which includes execution...but I will add it to exclude any possible error...thanks for the info.
It might be worth to mention this in 3.1 Busybox installation:
Code:
adb push busybox /system/xbin/
I accidentallly use "adb push busybox /system/xbin" without the ending "/". Well, you know the rest part of the story...
Hmm, probably this one first, at least for the stock HTC ROM
Code:
adb shell "mkdir /system/xbin"
PS: Kind of weird for its name xbin, not the usual sbin on desktop linux. ;-)
TheSSJ said:
You mean getting the apk from your mobile on your PC for example?
Hm, normally when you push the file via adb it will have user permissions, which includes execution...but I will add it to exclude any possible error...thanks for the info.
Click to expand...
Click to collapse
Maybe it's because I am using a Fedora box, which the default permission for files in $HOME does not include execution.
lovenemesis said:
Hmm, probably this one first, at least for the stock HTC ROM
Code:
adb shell "mkdir /system/xbin"
PS: Kind of weird for its name xbin, not the usual sbin on desktop linux. ;-)
Click to expand...
Click to collapse
You're right, I added it already in the guide, thanks for the feedback. Well, /system/xbin isn't a "normal" directory indeed, but it was created for extra executables which normally aren't shipped in stock ROMs (like busybox).
4. Then perform this:
- # export LD_LIBRARY_PATH=/system/lib
- # export PATH=/system/bin
- # insmod ./tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
- # cat ./su > /system/bin/su
- # chmod 4755 /system/bin/su
Click to expand...
Click to collapse
I suppose after this step the stock ROM is rooted. Right?
But in Android Terminal Emulator gives me $ still. "su" reports an link_image error, which basically said about missing libbinder.so library.
Is it normal or I need to push an libbinder.so to /system/lib as well?
BTW: "adb shell " gives me # straightly.
Regards,
Hmm, I pushed another "su" binary to overwrite the one in Tattoo.rar. And now it works fine in Android Terminal Emulator.
Here is the su binary I use:
View attachment su.zip
Oops, Titanium Backup still refuses to work despite of working "su" binary.
What else should I do?
market not working
hi
i dont know why but the Market does not work for me can u give any solutions for the same im just not able to log in it keeps saying error i also tried with google mail and gmail id but no luck any suggestion pls
few questons kindly answer
hi
i have afew questions can u kindly answer
1. is wipe a must before flashing a new rom
i have flashed the Modoco rom and it was mentioned that this was not needed but i have read in many threads asking to do the same before flashing
2.to bring back contacts after flashing new rom can i use
a. backup pro or titanium backup
b. can i just use the out look sync and get back my contacts from my PC
3. if i restore the stock rom and latter on want to try one of the cooked roms do i need to do the rooting again ie does flashing stock rom remove the rooting
Note : i have been a WM user new to AM is why im asking such questions in the WM i have one app pim backup which would get back all my contacts in 1 min and when flashing any WM it will automatically wipe all the data from the phone this does not seem to be the case with AM is why i have asked above Questions
thanks in advance
lovenemesis said:
Oops, Titanium Backup still refuses to work despite of working "su" binary.
What else should I do?
Click to expand...
Click to collapse
Titanium Backup needs Busybox and su to work. If Titanium Backup tells you that it found BusyBox, then try to copy "su" to the following to locations:
/system/bin and /system/xbin
I think with the first it should work then.
haree said:
hi
i dont know why but the Market does not work for me can u give any solutions for the same im just not able to log in it keeps saying error i also tried with google mail and gmail id but no luck any suggestion pls
Click to expand...
Click to collapse
Do you use MoDaCo ROM or did u switch now to another? Normally the phone asks for log-in credentials when going online. When you enter them correctly, the login window should disappear and you should be able to access market...I know this sounds stupid, but check if you entered you PW correctly!
haree said:
hi
i have afew questions can u kindly answer
1. is wipe a must before flashing a new rom
i have flashed the Modoco rom and it was mentioned that this was not needed but i have read in many threads asking to do the same before flashing
2.to bring back contacts after flashing new rom can i use
a. backup pro or titanium backup
b. can i just use the out look sync and get back my contacts from my PC
3. if i restore the stock rom and latter on want to try one of the cooked roms do i need to do the rooting again ie does flashing stock rom remove the rooting
Note : i have been a WM user new to AM is why im asking such questions in the WM i have one app pim backup which would get back all my contacts in 1 min and when flashing any WM it will automatically wipe all the data from the phone this does not seem to be the case with AM is why i have asked above Questions
thanks in advance
Click to expand...
Click to collapse
1. As I told you via PM already: If the ROM is based on the same source ROM (HTC stock in your case) then a wipe is NOT required, but if you switch android version (AOSP, Vanilla, FroYo, Eclair) then you HAVE TO wipe.
2.
a) I had only problems with Titanium backup concerning restoring contacts. I would suggest using MyBackup Pro
b) Well, if you can sync to outlook, then I suppose yes, but I really doubt that these features are implemented in custom ROMs...
3. Well, if you mean restoring the NAND-backup and then flashing another cooked ROM (which are all rooted by default ), then no - you don't need to re-root. Only if you would flash the original/official HTC ROM which comes shipped as exe-file, but I don't see the sense in flashing this one...use your NAND-backups
TheSSJ said:
Titanium Backup needs Busybox and su to work. If Titanium Backup tells you that it found BusyBox, then try to copy "su" to the following to locations:
/system/bin and /system/xbin
I think with the first it should work then.
hi
thanks buddy for patiently answering all my Q
i got it now but i dont know why this Bl***dy market does not work what every i try ie when the net is on and ur browsing u see the E on ur phone screen and then the 2 white arrows flash this it self does not happen when i try to log in to market
just dont know what is wrong
right now im using Modoco and happy with it seems to be real fast and everything is working on this ROM
Click to expand...
Click to collapse

[Q] extracting firmware

hello
is there any way to extract the whole firmware from a i9000?
a friend of mine just bought a i9000 from the same carrier that i have.. and i want the original rom. is there any way to get it untouched (vanilla)??
Not really untouched, you'd always need root to grab the firmware, so that's flashing a different kernel or trying other ways to get (temporary) root.
But don't let that stop you, the kernel probably won't be any different than the standard Samsung one, so you can put it back later.
the thing is... i cant find the original kernel around, i have searched all over, and there is no where to be found. so.. if i change the kernel, and take it in for warranty related stuff the carrier people will notice that i have changed it.. and they'll say.. sorry you void the warranty!!
so... is there any way to extract a vanilla rom??
Use check fus downloader. Google it or look around xda. You will be able to get your ROM direct from Samsung.
Sent from my GT-I9000 using Tapatalk
Is it me or are you confusing kernel and ROM ? The kernel is the stuff that makes it boot and talk to the hardware and stuff, like a bios from a pc. The rom is the operating system which does everything else.
Can you post the kernel version ?
EDIT: Since you did not quote I am assuming you are replying to my post. If not please just ignore my bantering.
Bubble-be said:
Is it me or are you confusing kernel and ROM ? The kernel is the stuff that makes it boot and talk to the hardware and stuff, like a bios from a pc. The rom is the operating system which does everything else.
Can you post the kernel version ?
Click to expand...
Click to collapse
It's just you. I know what a kernel is, do you know what a rom is? The kernel is included with the rom. If you get the rom, you have the kernel.
Also, the kernel technically does not make your device boot. It is, however, used during the boot process to perform some hardware initialization (initializing IRQs, setting up the scheduler, starting the dynamic module loader).
It is nothing like a BOIS from a PC. This point is illustrated by the fact that a PC running linux requires both a BIOS and a kernel. They are mutually exclusive. The kernel is a part of the OS, the BIOS is a part of the device.
Like I said, get the ROM and you get the kernel. The kernel is simple to extract, and you also have the added bonus of having the complete, unadulterated rom should you need it in the future.
since i`m new to everything here can you help me with smth that is bothering me
i got a i9000 2 months ago and since then i`ve been messing around with rooting and flashing around without understanding o lot but i've been doing exactly what others say step by step
i like this galnet miui rom (the only one i've tried so far) but i have battery drain issues
can you tell me a good combination of kernel and/or bootloader with this galnet so i would not have a battery drain
now i'm using official 2.3.5 and i have a full day battery usage
but i like some features that galnet has
thanks in advance
xxbeanxx said:
EDIT: Since you did not quote I am assuming you are replying to my post. If not please just ignore my bantering.
It's just you. I know what a kernel is, do you know what a rom is? The kernel is included with the rom. If you get the rom, you have the kernel.
Also, the kernel technically does not make your device boot. It is, however, used during the boot process to perform some hardware initialization (initializing IRQs, setting up the scheduler, starting the dynamic module loader).
It is nothing like a BOIS from a PC. This point is illustrated by the fact that a PC running linux requires both a BIOS and a kernel. They are mutually exclusive. The kernel is a part of the OS, the BIOS is a part of the device.
Like I said, get the ROM and you get the kernel. The kernel is simple to extract, and you also have the added bonus of having the complete, unadulterated rom should you need it in the future.
Click to expand...
Click to collapse
xxbeanxx said:
EDIT: Since you did not quote I am assuming you are replying to my post. If not please just ignore my bantering.
Click to expand...
Click to collapse
I did not quote, but was answering to the OP.
Sorry if that was confusing.
It's just you. I know what a kernel is, do you know what a rom is? The kernel is included with the rom. If you get the rom, you have the kernel.
Click to expand...
Click to collapse
Well yes, but I can't imagine a provider customizing the kernel. They do however customize the rom to include their own bootscreen, apps, theme. My previous phone was that way for example. I looked long and hard for the original firmware. But unless you're with one of the really big providers (Orange or the like), the rom is not available on the interwebs.
Showing up at a provider's service center with a bog standard rom can look suspicious that way.
Also, the kernel technically does not make your device boot. It is, however, used during the boot process to perform some hardware initialization (initializing IRQs, setting up the scheduler, starting the dynamic module loader).
It is nothing like a BOIS from a PC. This point is illustrated by the fact that a PC running linux requires both a BIOS and a kernel. They are mutually exclusive. The kernel is a part of the OS, the BIOS is a part of the device.
Click to expand...
Click to collapse
Thanks for clearing that up. I was aware of most things, but decided to paint a simpler picture for the OP.
enushi2002 said:
...can you tell me a good combination of kernel and/or bootloader with this galnet so i would not have a battery drain
...
Click to expand...
Click to collapse
The bootloader has no affect on your battery life.
Also don't assume the kernel is the biggest contributing factor to your battery drain. It very well may be, but there are a lot of other things that could also cause it. It would be better to try to investigate the cause of your battery drain rather than just switching kernels to try to fix it.
To directly answer your question, no I can't tell you a good kernel to use with MIUI. I am running CM7.1 currently with stock kernel and get decent battery life.
Are you on 3G data often? CM (and thus MIUI) has trouble with 3G, causing bad battery drain (so called RIL bug).
---------- Post added at 09:34 AM ---------- Previous post was at 09:27 AM ----------
Bubble-be said:
...the rom is not available on the interwebs.
Showing up at a provider's service center with a bog standard rom can look suspicious that way.
Click to expand...
Click to collapse
If you can update your phone via KIES you can get your ROM via check fus downloader. The rom you download using this tool will be what KIES uses to update your phone. So it is not "bog standard," it is what your provider puts on your phone, complete with provider customizations. It is impossible for a service center to tell the difference.
I had CyanogenMod on my phone when the touchscreen malfunctioned. I downloaded my provider's latest rom using check fus downloader, flashed it with odin, performed a factory reset, and brought it back and they replaced it no questions asked. As far as they knew I had only ever used the "proper channels" (ie: kies) to update my phone.
xxbeanxx said:
Use check fus downloader. Google it or look around xda. You will be able to get your ROM direct from Samsung.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Hi, thanks, but it did not found it..
in the result box says
Product Code: GT-I9000HKTVMT
no firmware info retrieved for given data
the firmware info would be:
Product code: GT-I9000HKTVMT
PDA: I9000TUBJPA
CSC: I9000TVMTJP6
Phone: I9000TUBJPA
Is a froyo 2.2.1 for a galaxy I9000T from movistar venezuela
I guess i'll keep looking for it
francescopp said:
I guess i'll keep looking for it
Click to expand...
Click to collapse
Wow that's strange. Well anyway, you could try this..it won't work without root but if you don't mind rooting first you can do this to get your kernel, then unroot.
Code:
adb shell su -c "dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096"
If you want to backup your entire rom:
Code:
adb shell su -c "dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096"
adb shell su -c "dd if=/dev/block/bml2 of=/sdcard/pit.pit bs=4096"
adb shell su -c "dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096"
adb shell su -c "dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096"
adb shell su -c "dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096"
adb shell su -c "dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096"
To verify the dumps you can mount them in linux or use MagicISO in windows (the .rfs ones at least).
You can then turn these files into a full fledged rom with a bit of tinkering. This might be your only option.

[Q] : some changes failed. need to transfer new rom

I was trying to install bad seeds sense 6 and sadly did not back up and did not had any old rom as aback up. the rom installed ok but i got this at the end set_metadata_recursive: some changes failed . the phone just keeps rebooting to twrp. i tried to transfer another rom via adb but im not getting my commands right, any other way to add another rom. or way to update my twrp ? please help?
kmacho714 said:
I was trying to install bad seeds sense 6 and sadly did not back up and did not had any old rom as aback up. the rom installed ok but i got this at the end set_metadata_recursive: some changes failed . the phone just keeps rebooting to twrp. i tried to transfer another rom via adb but im not getting my commands right, any other way to add another rom. or way to update my twrp ? please help?
Click to expand...
Click to collapse
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
twrp sideload
tdhite said:
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
Click to expand...
Click to collapse
sorry but i feel so ignorant. i installed the drivers and have the rom ready, but how to i the phone to adb shell. do i go to mount on twrp or on the advance settings adb sideload? when i put adb shell in the command prompt but it says adb not recognized. i would really appreciate your help if you could help me with more detail if possible.
kmacho714 said:
sorry but i feel so ignorant. i installed the drivers and have the rom ready, but how to i the phone to adb shell. do i go to mount on twrp or on the advance settings adb sideload? when i put adb shell in the command prompt but it says adb not recognized. i would really appreciate your help if you could help me with more detail if possible.
Click to expand...
Click to collapse
Goodness -- I thought you were all setup for adb and understood this stuff.
Here's what you need to do *first*, then follow the instructions above after you get adb working. To "adb shell" in to the phone -- you will boot into TWRP, which starts the adb server on the phone. But you use your computer and a "command terminal" window. We have to have this one way or another, so you have to learn. You will plug in your USB cable to the phone and computer, then the commands will work -- yes, they will work with TWRP.
To setup the adb stuff, learn here: http://forum.xda-developers.com/showthread.php?t=2277892 and look for Question 8
adb
tdhite said:
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
Click to expand...
Click to collapse
do i need android sdk? and htc sync? i have the drivers i think? on my device managers it doesnt say adb . just device and on the info it says htc device
thank you
tdhite said:
Goodness -- I thought you were all setup for adb and understood this stuff.
Here's what you need to do *first*, then follow the instructions above after you get adb working. To "adb shell" in to the phone -- you will boot into TWRP, which starts the adb server on the phone. But you use your computer and a "command terminal" window. We have to have this one way or another, so you have to learn. You will plug in your USB cable to the phone and computer, then the commands will work -- yes, they will work with TWRP.
To setup the adb stuff, learn here: http://forum.xda-developers.com/showthread.php?t=2277892 and look for Question 8
Click to expand...
Click to collapse
thanks a lot! those commands work ! just needed to install the drivers . thanks! again

[GUIDE][UNLOCK BOOTLOADER]Guide to unlocking the bootloader on the L90 [ALL VARIANTS]

Code:
#include
/*
* Your warranty is now likely void.
*
* I am not responsible for bricked devices, dead SD cards,
* spontaneous combustion, or any other host of cosmic penalties
* which may befall you, your family, or your phone.
*
*/
Over the last few months development on the LG L90 has made some great strides, up to the point where we can actually install roms! In order to do this, however, you'll need an unlocked bootloader.
The problem that arises is that there are different models of the L90, being the D405, the D405n, the D410 and the D415. For most of the models the unlock process is very similar, but for the D415 another method is needed.
This guide is aimed at explaining the entire unlock process in a complete and simple way, so even if you have no experience flashing custom recoveries or roms at all, you should still be able to follow this guide. If you run into problems, please just post a reply or send me a PM and I'll do my best to help you.
First of all I'd like to note that I did not develop any of the bin files or apks in this guide, I'm only collecting all the unlock methods in one place for easy reference. Therefore I am not responsible for you bricking your device or causing any kind of damage to it. You follow this guide AT YOUR OWN RISK! That being said, let's get to the unlocking!
What you'll need to unlock the bootloader
1. A rooted LG L90
You can root the phone by going to https://towelroot.com in your mobile browser and tapping the lambda sign. Save and install the apk (make sure unknown sources are enabled in "menu > general > security"). Google will warn you about the app, this is because of the exploit which will enable the root access. Execute the program and tap "make it ra1n", then install supersu from the play store. Open supersu and choose to rebuild the binaries. This will fail, but after a reboot supersu should be installed and working properly.
UPDATE: If towelroot doesn't work for you, you've probably got the L90 with an updated firmware. In that case you can follow this guide by @gdjindal to obtain root access. Afterwards you can follow the rest of this guide again.
2. Have adb installed.
just download the Android sdk and install it or, if you don't care about the SDK itself, the minimal adb from the bottom of this post (thanks to @shinobisoft for the upload). Now add the C:/path_to_the_sdk/sdk/platform-tools to your windows PATH variable (Windows 7: right click my computer > properties > advanced system settings > environment variables) or the foler in which adb.exe is located if you downloaded the minimal adb..
On your phone go to "menu > general > about phone > software information" and tap build version a few times untill it says you're a developer, then go to "menu > general > developer options" and enable usb debugging. Connect the phone with your PC and choose to connect in software mode and install the drivers and tools. When you get a message on your phone that your PC want to access usb debugging make sure you check the checkbox and accept. Now open a cmd prompt and type "adb devices" without the quotes. If it shows a series of letters and numbers followed by device, you're good to go. If it says unauthorized, you haven't accepted the prompt on your phone yet. If your device doesn't show up at all you haven't installed the drivers correctly.
3. Find out which device and software version you're running.
Go to menu > general > about phone > Hardware information for your Model number. Mine is LG-D405n, so my model is D405n.
Go to menu > general > about phone > Software information for your Software version. Mine is V10b-EUR-XX, so I've got version v10b.
4.1 If your model number is D405, D405n or D410, you'll need a modified aboot.bin to unlock the bootloader.
Go to the bottom of this post and download the file with your model and software version. I used the L90_D405n_v10b_hack.zip. Extract the aboot.bin in the zip file to a folder on your PC.
4.2 If your model number is D415, you'll need another method to unlock the bootloader, which is explained in this thread made by @aSuperSaiyanG0D.
Unlocking the bootloader on the D405, D405n and D410
1. Open a cmd window an CD to the folder where you've saved the aboot.bin you've downloaded in step 4.1
2. Execute the following commands:
Code:
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Right after the su command, supersu will give you a root request on your phone that you'll have to accept!
This will also make a backup of your current aboot partition as stockaboot.bin on your external SD card. If you don't have an external SD card, this won't work and you'll have to use /storage/emulated/0 (this is a zero, not the letter o) instead of /storage/external_SD/ like this:
Code:
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin 5429599
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
3. That's basicly it, you can now install a custom recovery. I suggest downloading the latest TWRP (2.8.0.0 right now) from @shoxxy's thread, which can be found here. Just use ROM Toolbox to install it, choose rom installer, press settings > flash image and select the TWRP image from @shoxxy's thread. Afterwards you can boot to recovery using ROM Toolbox, or by shutting down the phone, holding volume down and power untill the lg logo shows, then releasing and immediately pressing those buttons again. You should get a screen asking to perform a factory reset. Choose yes twice (don't worry, it wont actually perform the reset) and TWRP should boot up. Now you can create backups and install custom roms too!
If you're a fan of cyanogenmod, you should visit @Quarx's thread, which can be found here. His CM11 is already mostly functional (right now on some models the front camera doesn't work and the ir blaster doesn't have any software, but most other functions actually do work very well, while it is faster than LG stock and gives almost twice the battery life), so if you like CM it's a thread worth keeping an eye on.
Flashing back the stock rom (in case of a brick)
If you've bricked your device, or want to revert to stock for any reason, you can follow this guide made by @gdjindal.
Post reserved
So, I did everything, but when I try to do the 4.2, I cant do it.. The reason why is because it says "No stat file"
Gabe.INc said:
So, I did everything, but when I try to do the 4.2, I cant do it.. The reason why is because it says "No stat file"
Click to expand...
Click to collapse
If you have a problem with step 4.2 only, I assume you have a D415 and you should actually ask this question in the thread that step 4.2 links to. Or isn't that what you meant?
EDIT: please note that step 4.2 is for the D415 ONLY.
Sorry, my bad, I though tha step 4.2 was the wole thing that comes next, my device is D405
Gabe.INc said:
Sorry, my bad, I though tha step 4.2 was the wole thing that comes next, my device is D405
Click to expand...
Click to collapse
No sweat If you've completed step 4.1, just head to step 1 of the next section and you should be good.
SubliemeSiem said:
No sweat If you've completed step 4.1, just head to step 1 of the next section and you should be good.
Click to expand...
Click to collapse
but thats the problem, I've donwloaded my file, and then, put it on a folder in my desktop.. Then what do I do?
Gabe.INc said:
but thats the problem, I've donwloaded my file, and then, put it on a folder in my desktop.. Then what do I do?
Click to expand...
Click to collapse
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Mind that I've only tested this using the external SD, but it should work both ways.
Error 1
SubliemeSiem said:
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
It give me this error, in both external and internal storage
Click to expand...
Click to collapse
Gabe.INc said:
SubliemeSiem said:
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
It give me this error, in both external and internal storage
Click to expand...
Click to collapse
That is stange, never had that error myself. In that case I would try another way to put the aboot.bin on the root of the SD card (google drive for instance) and continue from the adb shell part..
Click to expand...
Click to collapse
BTW: what's the output of
Code:
adb devices
?
SubliemeSiem said:
Gabe.INc said:
That is stange, never had that error myself. In that case I would try another way to put the aboot.bin on the root of the SD card (google drive for instance) and continue from the adb shell part..
Click to expand...
Click to collapse
Can't I just simply paste it on my SD card?
Edit: I think I found what my problem was, something in developer settings..
2nd Edit: Nop, it still gives the same read-only error..
3rd Edit: The output of adb devices is LGD410bc(..) Device
Click to expand...
Click to collapse
Gabe.INc said:
SubliemeSiem said:
Can't I just simply paste it on my SD card?
Edit: I think I found what my problem was, something in developer settings..
2nd Edit: Nop, it still gives the same read-only error..
3rd Edit: The output of adb devices is LGD410bc(..) Device
Click to expand...
Click to collapse
Strange, but yes, you can simply paste it on your SD card and continue from the "adb shell" line. You can also try
Code:
adb shell sysrw
before the push command to mount the filesystem as RW. If you do this, it is recommended to use
Code:
adb shell sync
adb shell sysro
after the psuh command (so you'll mount the filesystem as RO again).
Click to expand...
Click to collapse
SubliemeSiem said:
Gabe.INc said:
Strange, but yes, you can simply paste it on your SD card and continue from the "adb shell" line. You can also try
Code:
adb shell sysrw
before the push command to mount the filesystem as RW. If you do this, it is recommended to use
Code:
adb shell sync
adb shell sysro
after the psuh command (so you'll mount the filesystem as RO again).
Click to expand...
Click to collapse
It says, not found..
BTW: I flashed stock again..
Click to expand...
Click to collapse
Gabe.INc said:
It says, not found..
BTW: I flashed stock again..
Click to expand...
Click to collapse
Where did you get the not found message? And what do you mean you flashed stock again? If you couldn't execute the dd commands then your bootloader is still locked and all you've done so far is root the device..
UPDATE: I don't get a response, but it seems this user previously flashed the wrong aboot.bin (or did something else, unfortunately he's not being very clear on that) so please only follow this guide when you have a stock recovery + aboot partition. If you did try some things before, please flash the stock rom back first and then follow this guide.
Thats awesome! Thank you! :cyclops:
guilherme.fuzo said:
Thats awesome! Thank you! :cyclops:
Click to expand...
Click to collapse
No problem! Just let me know if you run into any problems so I can update the guide accordingly (and hit the thanks button if it worked of course).
SubliemeSiem said:
No problem! Just let me know if you run into any problems so I can update the guide accordingly (and hit the thanks button if it worked of course).
Click to expand...
Click to collapse
I found no problem, but anyway thanks dude! :laugh:
guilherme.fuzo said:
I found no problem, but anyway thanks dude! :laugh:
Click to expand...
Click to collapse
Then don't say thanks, but hit the thanks button on the first post!

can anyone help me root my coolpad defiant?

Hello guys im new to these forums an did not know where to post at, i got a coolpad defiant (Not the best phone) an i wanted to root it and was seeing if anyone here maybe able to help me out?? ive tried to use kingRoot but not luck on using that method if anyone got any suggestions id really like that, thanks again!
rebz408 said:
Hello guys im new to these forums an did not know where to post at, i got a coolpad defiant (Not the best phone) an i wanted to root it and was seeing if anyone here maybe able to help me out?? ive tried to use kingRoot but not luck on using that method if anyone got any suggestions id really like that, thanks again!
Click to expand...
Click to collapse
Any luck?
Thank you very much
Jayfreshh said:
Any luck?
Click to expand...
Click to collapse
Did you ever find anything for this device?
remarkablecow913 said:
Did you ever find anything for this device?
Click to expand...
Click to collapse
Nothing as yet still searching, need to do some work on the phone but nothing to start with ?
Jayfreshh said:
Nothing as yet still searching, need to do some work on the phone but nothing to start with ?
Click to expand...
Click to collapse
I know. I can't find Any resources for this phone. I might get brave And see if I can find twrp for same chipset and try.
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
remarkablecow913 said:
I know. I can't find Any resources for this phone. I might get brave And see if I can find twrp for same chipset and try.
Click to expand...
Click to collapse
Have you tried unlocking bootloader? That's probly most important. If it's locked there is no point tying
remarkablecow913 said:
I know. I can't find Any resources for this phone. I might get brave And see if I can find twrp for same chipset and try.
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
Have you tried unlocking bootloader? That's probly most important. If it's locked there is no point tying
Click to expand...
Click to collapse
Okay if anything works out when you try let me know
The bootloader can be opened in developer mode for this devise if I'm correct
You can unlock bootloader in developer options but from there. I'm stuck and really want to get root and see what "deleted" files I can recover from a factory reset. Anybody ever try twrp for same chipset like someone was talking about doing?
rebz408 said:
Hello guys im new to these forums an did not know where to post at, i got a coolpad defiant (Not the best phone) an i wanted to root it and was seeing if anyone here maybe able to help me out?? ive tried to use kingRoot but not luck on using that method if anyone got any suggestions id really like that, thanks again!
Click to expand...
Click to collapse
[Update Anyone?]
I picked up a Coolpad 3632a yesterday and I've been trying to ROOT it for quite a while nowl; trying Kingroot v5.3.7 without PC, and KingRoot 3.5 on PC both failed to ROOT. I've been out of the loop for quite a while regarding Android devices and OS - the last Android Phone i owned was the LG G3 if i remember correctly. According to the available info I've found searching for Rooting Options for the coolpad 3632a it all seemed almost %100 easily rootable with or without PC mainly using Kingroot.
If anyone was successful in rooting this device (Coolpad 3632a / Android 7.1.1) - please let me know, my main goal is to find a good custom ROM and load it replacing the Bloat/Malware filled phone!
Thanks again to anyone who has taken the time to read and respond with any news (good or bad) on getting this device successfully rooted.
-=Mac3lite=-
Bootloader Unlock = Not happening on this device. At least yet.
Development = Absolutely none. Means no TWRP/ROMS etc.
Root = Nothing as of 10/10/2018.
phonecapone said:
Bootloader Unlock = Not happening on this device. At least yet.
Development = Absolutely none. Means no TWRP/ROMS etc.
Root = Nothing as of 10/10/2018.
Click to expand...
Click to collapse
EDIT: I just obtained temporary root.. seeing if it sticks.
Root for Coolpad Devices
NOTE: I have not tried this on your device but I have tried it on my Coolpad Mega 2.5 D , Coolpad Mega 3 and Coolpad Note 5 lite. You might try to see if this works on your Coolpad Device.
Requirements :
A working ADB setup
Procedureownload the Given Zip File and Extract Them in a folder.
CONNECT YOUR DEVICE TO PC
ALLOW USB DEBUGGING IN DEVELOPER SETTINGS:
OPEN THE FOLDER WHERE YOU EXTRACTED THE FILES AND RUN CMD.BAT
COPY AND PASTE THESE CODES ONE BY ONE IN ADB ....
Or RUN THE SCRIPT IN THE GIVEN FILE
Quote:
adb wait-for-device
Quote:
adb install magisksu.apk
Quote:
adb install rootcheck.apk
Quote:
adb install root.apk
Quote:
adb shell monkey -p com.yulong.openrp -v 500
Quote:
adb reboot
WAIT TILL THE DEVICE BOOTS
OPEN MAGISK APP & COPY AND PASTE THIS CODE :
Quote:
adb shell mount -o remount,rw /system
NOW :
Quote:
adb push magisk /system/bin
IF SUCCESSFUL, TYPE:
Quote:
adb shell magisk su
RUN THIS COMMAND AFTER EVERY REBOOT TO AGAIN GET ROOT ;
Quote:
adb shell magisk su
OR
Update magisk for permanent root.
Download::::::::
https://drive.google.com/file/d/1e1atRg7PQ2JyI8W88g1E9L9NihdGEjqO/view?usp=drivesdk
Yeah that's already what I tried previous to your post. Had zero luck. =/ Also after that point forward for some reason when i try to fastboot i cannot issue any commands and it displays "Secure Phone" at the bottom left of the screen. Whether or not it was due to this I do not know for certain.
phonecapone said:
Yeah that's already what I tried previous to your post. Had zero luck. =/ Also after that point forward for some reason when i try to fastboot i cannot issue any commands and it displays "Secure Phone" at the bottom left of the screen. Whether or not it was due to this I do not know for certain.
Click to expand...
Click to collapse
Does fastboot detect your device ? Or just the commands fail even after detection ?
Also , when your phone boots , does MTKlogger automatically start ?
dwaipayan774 said:
Does fastboot detect your device ? Or just the commands fail even after detection ?
Also , when your phone boots , does MTKlogger automatically start ?
Click to expand...
Click to collapse
It gets detected just the commands fail. There is a white "Secure Phone" line of text across the bottom left. Im going to try loading an sdcard to see if it will auto update anything.
I can't even use Flash Programmer in QFIL or many other apps in QDLOADER 9008 mode. I know the firehose is the correct one yet it never wants to boot. I don't know why.
MTKLogger might have before unless i'm thinking of a different handset here. But as of the moment it doesn't.
No luck with the sdcard. I think it's about time to factory reset this device and put it up for sale. I'll post the firmware here shortly.
Here is the firmware - https://forum.xda-developers.com/android/general/rom-coolpad-defiant-3632a-stock-t3855692
Temporary Root
phonecapone said:
Bootloader Unlock = Not happening on this device. At least yet.
Development = Absolutely none. Means no TWRP/ROMS etc.
Root = Nothing as of 10/10/2018.
Click to expand...
Click to collapse
What did you do? I've been trying for months now.
dwaipayan774 said:
NOTE: I have not tried this on your device but I have tried it on my Coolpad Mega 2.5 D , Coolpad Mega 3 and Coolpad Note 5 lite. You might try to see if this works on your Coolpad Device.
Requirements :
A working ADB setup
Procedureownload the Given Zip File and Extract Them in a folder.
CONNECT YOUR DEVICE TO PC
ALLOW USB DEBUGGING IN DEVELOPER SETTINGS:
OPEN THE FOLDER WHERE YOU EXTRACTED THE FILES AND RUN CMD.BAT
COPY AND PASTE THESE CODES ONE BY ONE IN ADB ....
Or RUN THE SCRIPT IN THE GIVEN FILE
Quote:
adb wait-for-device
Quote:
adb install magisksu.apk
Quote:
adb install rootcheck.apk
Quote:
adb install root.apk
Quote:
adb shell monkey -p com.yulong.openrp -v 500
Quote:
adb reboot
WAIT TILL THE DEVICE BOOTS
OPEN MAGISK APP & COPY AND PASTE THIS CODE :
Quote:
adb shell mount -o remount,rw /system
NOW :
Quote:
adb push magisk /system/bin
IF SUCCESSFUL, TYPE:
Quote:
adb shell magisk su
RUN THIS COMMAND AFTER EVERY REBOOT TO AGAIN GET ROOT ;
Quote:
adb shell magisk su
OR
Update magisk for permanent root.
Download::::::::
https://drive.google.com/file/d/1e1atRg7PQ2JyI8W88g1E9L9NihdGEjqO/view?usp=drivesdk
Click to expand...
Click to collapse
Any chance on a repost of the file?
dwaipayan774 said:
Root for Coolpad Devices
NOTE: I have not tried this on your device but I have tried it on my Coolpad Mega 2.5 D , Coolpad Mega 3 and Coolpad Note 5 lite. You might try to see if this works on your Coolpad Device.
Requirements :
A working ADB setup
Procedureownload the Given Zip File and Extract Them in a folder.
CONNECT YOUR DEVICE TO PC
ALLOW USB DEBUGGING IN DEVELOPER SETTINGS:
OPEN THE FOLDER WHERE YOU EXTRACTED THE FILES AND RUN CMD.BAT
COPY AND PASTE THESE CODES ONE BY ONE IN ADB ....
Or RUN THE SCRIPT IN THE GIVEN FILE
Quote:
adb wait-for-device
Quote:
adb install magisksu.apk
Quote:
adb install rootcheck.apk
Quote:
adb install root.apk
Quote:
adb shell monkey -p com.yulong.openrp -v 500
Quote:
adb reboot
WAIT TILL THE DEVICE BOOTS
OPEN MAGISK APP & COPY AND PASTE THIS CODE :
Quote:
adb shell mount -o remount,rw /system
NOW :
Quote:
adb push magisk /system/bin
IF SUCCESSFUL, TYPE:
Quote:
adb shell magisk su
RUN THIS COMMAND AFTER EVERY REBOOT TO AGAIN GET ROOT ;
Quote:
adb shell magisk su
OR
Update magisk for permanent root.
Download::::::::
https://drive.google.com/file/d/1e1atRg7PQ2JyI8W88g1E9L9NihdGEjqO/view?usp=drivesdk
Click to expand...
Click to collapse
hey the link is dead. could you make a new link?

Categories

Resources